Versions Compared

Old Version 55

changes.mady.by.user Jon Taylor

Saved on

compared with

New Version 56

changes.mady.by.user Kang Xi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

      • Modeling
        To be discussed

      • SDC
        Add logic to use the new modeling when designing the service, and then distribute the resulting artifacts.

      • CLAMP
        Framework for policy design and distribution 

      • SO
        Add logic to understand the new artifacts; orchestrate/manage changes according to it.

      • SDNC
        Add logic to create the chaining, configuration, healing, etc.

      • DCAE
        Support statistics collection and receipt of events as per the new model; monitor connectivity and livelihood of the BRG_Emulator.

      • APPC, VF-C, and DCAE
        Support more complex control loops.

      • A&AI
        Support the new data model.

      • Policy
        Support new policy related to the service + the connectivity to the BRG_Emulator.

      • VNF SDK
        Support the ONAP VNF guidelines (blend from ECOMP and OPEN-O)

      • Integration
        Integrate, produce test cases, run the tests, verify the use case with the selected VNFs

Work Commitment:


Work ItemONAP Member
Modeling

Amdocs, AT&T

SDCAmdocs, AT&T
SOAT&T
SDNCAmdocs, AT&T
DCAEAT&T
APPCAmdocs, AT&T
A&AIAmdocs
PolicyAT&T
Multi-VIMWind River

VPP Based VNFs

BRG_Emulator, VBNG, vG_MUX, vG

Intel
Integration

Amdocs,

Integration Team (question)

Use Case Subcommittee

Amdocs, AT&T, Intel, Orange, Wind River, more ?

Deliverables: Service definition, service detailed requirements, ONAP flow diagrams, service(s) model(s)


Note: Work commitment items indicate which ONAP Members have expressed interest and commitment to working on individual items. More than one ONAP Member is welcomed to provide support and work on each of the items.

...

      • Jun 28, 2017 Meeting: Use Case Walk Through
        - Recorded meeting: https://zoom.us/recording/play/DgJBQbqOZaSKHxmOmlDXcU9_zTKNrRAa9Y3TTkCw3T9Hi-ekUBGVmf-ev8uU_TP9
        - Yoav walked through the use case flows so that people from different project can understand the details and subsequently identify impact/requirements/issues related to their respective projects.

      • Jun 30, 2017 Meeting: Closed Loop Control

        - Recorded meeting: https://zoom.us/recording/play/KG9scmJ1aaeV8ozDWaVhK9wPifYkCaF9qodXsyVOhM8z8Ld9PiKFD3K0IU2zl_rz
        - Yoav presented the flow on automatic reboot/restart.
        - One question was whether we want to restart VNF or VM. The answer is to restart VM.
        - Data collection vG_MUX --> DCAE: What needs to be worked out is the VES version and payload to be supported by vG_MUX. DCAE would like to have sample data from the VNF. Yoav will bring these requirements to Danny Lin.
        - Events DCAE --> Policy: The content of the events should be well defined.
        - Control Policy --> APPC: The detailed interface definition needs to be worked out.
        - Mapping from VNF ID to VM ID: The current flow shows that APPC will query AAI to perform the mapping. Further discussion is needed to decide where to do it: APPC or Policy.


      • Jun 30, 2017 Meeting: Design Time
        - Recorded meeting: https://zoom.us/recording/play/T7E79ekw4OaHRZCIf4dXF0Cq0PNVkA9bgyYsG2HKZqDhHCMFVGi6_gA3m_y5HSC0
        - Yoav presented the VNF onboarding process
        - VxLAN is preferred for the tunnels between BRG and vG MUX. Tunnels from different home networks will share the same VNI but are differentiated using the BRG IP addresses.
        - Ron Shacham explained that CLAMP will create a blutprint template that will be used to instantiate a DCAE instance for the use case. CLAMP is not responsible for the development of the DCAE analytics program.
        - It is determined that the infrastructure service and per customer service should be created individually.
        - Yang Xu from Integration pointed out that VNF address assignment/management (including OAM IP and port IP) needs further discussions. Yoav will update the use case architecture diagram to include OAM IP addresses.
        - It is realized that service design is complicated and needs more discussions. Yoav will follow up on these topic and schedule meetings.
        - Micheal Lando mentioned that a new version of SDC is being set up in AT&T. Daniel will check whether the community can get access to it.


      • Jul 6, 2017 Meeting: Design Time

        - Recorded meeting is here. 
        - Brian Freeman explained that APPC should query AAI to get the VM ID and then perform VM restart.
        - Currently that APPC polls to get the state after sending out restart command. There were discussions on using callback to get state change. Brian suggested that it be put in R2.
        - Discussed the mapping between VxLAN tunnel and the VLAN between vG_MUX and vG1.

      • Jul 9: closed loop diagram updated reflecting the discussion

      • Jul 12: Important Questions
        Discussed a the list of important questions. Refer this page: Use Case Related Important Questions and Answers

      • Jul 13: Service Model
        - Recorded meeting: https://zoom.us/recording/play/hjKRZEbaAk2H2VRnGwKqjb--HEd4mGig96F7t7TSEHUOiPtl8Zh4Cl5UbB2L-zTg
        - Gil Bullard presented the first version of service model. He will update his slides based on the discussions and then post them here.