You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Kickoff Materials

VZDeploymentOptions.pptx

Meeting Information

Doodle Poll for weekly meeting is at https://doodle.com/poll/r9cknpnd2rp9xuzv.

The consensus seems to be for 9am ET on Monday (12 votes) or Tuesday (11 votes) vs any of the 6pm ET times.  Therefore I am scheduling for Mondays at 9am ET.

Assumptions

Objectives

  • Examine orchestration scenarios in order to determine if new architectural requirements are necessary
  • Develop recommendations for composition of the ONAP Service DM (How does the ETSI NFV SOL001 Network Service Descriptor supported?)
  • Develop recommendations for interfaces between the orchestration elements (OSS, SO, VF-C, VNFM, NFVO)
  • Develop recommendations for how ONAP controllers work with external orchestration elements (NFVO, VNFM, EMS)
  • Develop recommendations for how external Service Assurance interacts with DCAE and Policy
  • Develop recommendations on breaking ONAP into more modular consumable pieces (Margaret)

Tasks

To Do's

  • Recommendation on whether an ONAP should support an E2E Service  that is composed of xNFs that are orchestrated by separate orchestrators (SO,  SO + external VNFM, VF-C, external NFVO) for next Arch meeting (Nov 13)
  •  Mapping of SOL005 APIs to ONAP NBI
  • Develop scenarios with stories about how ONAP could be used in near term brownfield  legacy environment Fernando Oliveira
  • Develop scenarios with stories about how a legacy environment could migrate off of a brownfield legacy environment towards a ONAP native model Fernando Oliveira
  • Describe how ONAP DCAE could be integrated with legacy Service Assurance platform Fernando Oliveira
  • Describe how legacy inventory system would interact with ONAP A&AI


Contributions...

Recording of call 11/12/2018: double_click_to_convert_01.zoom


  • No labels