Versions Compared

Old Version 214

changes.mady.by.user Guangrong Fu

Saved on

compared with

New Version 215

changes.mady.by.user Dana Bobko

Saved on

Key

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

The July Virtual Developers Event is for ONAP developers, by ONAP developers. Your contributions and needs are what will drive the agenda for all of these sessions.  To build the agenda for the we are soliciting Topics for discussion from the community.  Ideally these are questions that you need a deeper understanding of in order to make progress or deep-dive information sharing in a particular area.

...

VID: Virtual Infrastructure Deployment introduction

  • Description: The Virtual Infrastructure Deployment (VID) application allows infrastructure service deployment operators to instantiate service instances and their constituent parts for distributed service models required.
    in this session we would like to introduce the ONAP community to VID capabilities and road map. we invite the community to join us.
  • Topic Leader: TBD.
  • Volunteer Note Taker: Amichai Hemli 
  • Estimated Duration: 1 hr
  • Link to data Source (if applicable)
  • Interested In Attending: 


Portal App Implementation and OnBoarding

  • Description: Introducing Portal SDK and its Platform Onboarding Requirements. Below topics are discussed (30mins each):
    1. How to build the Portal SDK based application?
    2. How to on-board the SDK based application onto Portal platform?
  • Topic Leader: Sunder Tatta.
  • Volunteer Note Taker: Leimeng Shi
  • Estimated Duration: 60 min
  • Link to data Source (if applicable)
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.


Release Versioning (Day 1- Main Conf. Bridge)

  • Description: Discuss 2versioning proposals for Amsterdam
    • 1. We try to keep the version numbers all in sync and in sync with the release number which will require “downversioning” some of the code with all the problems that will cause with dependencies and artifact caching. It will also be difficult to maintain as we are applying patches after the Amsterdam release is out (a patch to one component would trigger a version update to all other components).

    • 2. We allow each repo to manage there own version number and then the Amsterdam release is just really a collection of artifacts with different version numbers properly tagged/referenced.

  • Topic Leader:Oliver Spatscheck
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.

Modeling subcommittee specification coordination

...

VoLTE Use Case Control Loop Automation (Day 2- Main Conf. Bridge)

VNFRQTS - Guidelines & Requirements/chapter structure of the documents

...

VoLTE Service Design and Instantiation (Day 2 - Main Conf. Bridge)

  • Description: Discuss the details of service design and instantiation for VoLTE use case:
      1. VNF template format (TOSCA/HEAT)
      2. vEPC and vIMS VNFs onboarding
      3. Network service design for data center interconnect network (underlay and overlay), and network between 2 VNFs
      4. SDC output artifacts (content and format)
      5. VoLTE service instantiation

...

...