NFV

  • 1.  System Updates In Regards To NFV/SDN

    Posted Dec 04, 2017 16:11
    Is there any procedure in place to ensure the customers and the NFV/SDN management team follow a relevant maintenance plan in order to maintain the performance of the service?

    ------------------------------
    elisabeth equilbey
    Verizon Communications
    ------------------------------


  • 2.  RE: System Updates In Regards To NFV/SDN

    TM Forum Member
    Posted Dec 05, 2017 09:51

    Elizabeth , Rather a broad question but will try to provide some input to start the dialog. What we have done in the ZOOM project is to identify the different stakeholder involved in managing a (network) resource and have developed a number of User Stories in TR 229 and TR 229A.

    From this analysis we concluded there were three value streams, stakeholder groups, and associated processes concerned with managing hybrid physical and virtualised resources.

    1. Those focused on providing zero-touch tenant services to end customers.
    2. Those related to managing how the tenant services are delivered and the Lifecyle management of the componenst used to support them.
    3. Enterprise processes related to Security and risk management

    The basic plot above is described in TR262 Management Platform Blueprint and application to Hybrid Infrastructure R17.5.0 the ZOOM team site for TM Forum members. Earlier version available on the Tm forum web site

    Wrt to your query

    " … procedure in place to ensure the customers and the NFV/SDN management team follow a relevant maintenance plan"

    For customers we are using a combination of:

    • Intent based network services which are associated with a Customer SLA and reporting to the customer (Preferred approach).
    • Detailed management of the customer/ tenant service using FCAPS like assurance processes: Alarms trouble ticket etc.

    For the NFV/SDN management team (internal operations and planning) we are proposing for item 2 above

    1. An autonomic computing Closed control loop approach to capacity management ( based on feedback from cloud providers) and self healing (leveraging ETSI MANO results) Described in TR 262 and supporting documents. This is needed to handle volume and velocity of change.
    2. Rapid onboarding commercial and technical onboarding automation using the basic plot TR269_Onboarding_Automation_and_Package_Metadata_R17.0.0 available at www.tmforum.org) and detailed proposals proposed in TR1141 /A/B and proposals to extended TOSCA profiles to cover a broader range of component metadata.
    3. A Joint agile Development approach for linking supplier and operator DevOps environment to handle incremental update / maintenance of the virtualized components documented in: IG1137A_Development_Deployment_in_Context_of_Value_Fabric_Joint_Agile_Delivery_R17.0.0 which is being uplifted in R17-5 to IG1137B Joint Agile Delivery (JAD) Service Assurance R17.5.0

    Items 2 and 3 above set out the context for maintenance plans between the operator and the suppliers. Item 1 addresses customer involvement.

    Most of these techniques have been demonstrated practically in Catalyst PoC demos over the last 3 years so we are quite confident about the approach.



    ------------------------------
    Dave Milham
    TM Forum Chief Architect
    ------------------------------