Versions Compared

Old Version 145

changes.mady.by.user Manoop Talasila

Saved on

compared with

New Version Current

changes.mady.by.user Viswanath Kumar Skand Priya

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.

...

titleTopic Template - Cut&Paste as needed

Topic/Question Name

...

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.

Info
titleTopic Template - Cut&Paste as needed

Topic/Question Name

  • Description: Description of the topic and the objective/outcome desired at the end of the discussion.
  • Topic Leader: The person that is knowledgeable enough to lead and moderate this discussion.
  • 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.
    • First Last email
    • First Last email
    • etc.

INSTRUCTIONS:  Please edit the section below and add any topics (using the template) that you would like to lead and/or attend. List the topic, and your name. If there is a topic that you would like discuss, but you do not feel that you can lead it, please list the topic below and indicate that you are "Interested in Attending", then indicate TBD as the "Topic Leader"

To getstarted wehave provided a few suggested topics based upon inputthisfar.

...

TOPICS


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.
  • First Last  email
  • First Last  email
  • etc.

INSTRUCTIONS:  Please edit the section below and add any topics (using the template) that you would like to lead and/or attend. List the topic, and your name. If there is a topic that you would like discuss, but you do not feel that you can lead it, please list the topic below and indicate that you are "Interested in Attending", then indicate TBD as the "Topic Leader"

To get started we have provided a few suggested topics based upon input this far.

TOPICS

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 Agenda)

  • Description: Discuss 2 versioning proposals for Amsterdam
    • 1. We try to keep the version numbers all in sync and in sync with the release number which will require “down versioning” 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

Modeling subcommittee specification coordination

A&AI Question- AAF & MSB Interaction (Day2 - Alt-Conference Bridge #1 1:30 PM )

A&AI & VF-C Discussion (Day 3 - Main Conf. Bridge)

A&AI Question- AAF & MSB Interaction

...


OOM & MSB Interaction(Day 1 - Alt-Conference Bridge #1 02:00 PM)

  • Description: 

    According to the conclusion of service registry discussionbetween MSB and OOM,  OOM and MSB manage the process and service separately at different levels and these two projects need to cooperate to use the Consul as the service registry to provide the service endpointsinfo for MSB. So MSB can leverage this info for service routing/load balancing, etc.  https://lists.onap.org/pipermail/onap-discuss/2017-June/001241.html

    Need to understand the current OOM process level registration info and how to combine process and service level registration info and save it toConsulcatalog.

  • Topic Leader: Former user (Deleted)
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)

...

...

A&AI & VF-C Discussion

SDC Questions (Day 3- Main Conf. Bridge)

OOM & MSB Interaction

...

According to the conclusion of service registry discussion between MSB and OOM,  OOM and MSB manage the process and service separately at different levels and these two projects need to cooperate to use the Consul as the service registry to provide the service endpoints info for MSB. So MSB can leverage this info for service routing/load balancing, etc.  https://lists.onap.org/pipermail/onap-discuss/2017-June/001241.html

Need to understand the current OOM process level registration info and how to combine process and service level registration info and save it to Consul catalog.

...

SDC Questions


Holmes Question on DCAE?Day3: Alt-Conference Bridge #1 2:00PM?

  • Description: 
    • A couple of meetings have been held to help all relevant teams to get to know what to do and how to do them. But almost all meetings are based on abstract samples or workflows. The Holmes team has shared a concrete rule example withrelevant teams. I'm not sure whether the example helped in understanding the mechanism of Holmes. If any questions remain, we want to make some further clarification as per the questions raised in the coming couple of days. Meanwhile, we're expecting concrete samples from the components which we are going to be interactwith. Hopefully, I wish Policy, CLAMP and especially DCAE could share some details (concrete examples) with us during the virtual F2F meeting. We are eager to have a working example of the DCAE operation and flows so that Holmes can effectively integrate Holmes event/alarm correlation functionality into DCAE for Amsterdam.
    • We have to get a consensus on the deadline to provide API docs to each other so that we could start developing as soon as we can. At the moment, even if we want to get started, we don't know how.
    • We have to discuss about the workflow for delpoying Holmes independently. Through all the meetings we've had, we are now aware of the workflow of how to integrate Holmes with DCAE and how to collaborate with all the relevant conponents. It's time for us to figure out a breakthrough point for Holmes to be deployed in the standalone mode. We'll try our best to find a scheme to reuse the existing interfaces as many as possible so that we could avoid replications in API development.
  • Topic Leader: Guangrong Fu
  • Volunteer Note Taker: First Last  email
  • Link to data Source 
  • Estimated Duration: 2 hours
  • Interested In Attending: We would like to invite SDC, VF-C and other related projects to join in this topic.

Holmes Question on DCAE

...

  • A couple of meetings have been held to help all relevant teams to get to know what to do and how to do them. But almost all meetings are based on abstract samples or workflows. The Holmes team has shared a concrete rule example with relevant teams. I'm not sure whether the example helped in understanding the mechanism of Holmes. If any questions remain, we want to make some further clarification as per the questions raised in the coming couple of days. Meanwhile, we're expecting concrete samples from the components which we are going to be interact with. Hopefully, I wish Policy, CLAMP and especially DCAE could share some details (concrete examples) with us during the virtual F2F meeting. We are eager to have a working example of the DCAE operation and flows so that Holmes can effectively integrate Holmes event/alarm correlation functionality into DCAE for Amsterdam.
  • We have to get a consensus on the deadline to provide API docs to each other so that we could start developing as soon as we can. At the moment, even if we want to get started, we don't know how.
  • We have to discuss about the workflow for delpoying Holmes independently. Through all the meetings we've had, we are now aware of the workflow of how to integrate Holmes with DCAE and how to collaborate with all the relevant conponents. It's time for us to figure out a breakthrough point for Holmes to be deployed in the standalone mode. We'll try our best to find a scheme to reuse the existing interfaces as many as possible so that we could avoid replications in API development.

...

Work Flow Discussion

  • Description:In the SO or controllers projects of ONAP,  there are many opensource party workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, etc. Most of those workflow engines now bind to the project.  Workflow engines self are independant fucntion and can be decoupled with the specific project logic functions. Could the projects make them as micro service? If some projects use the same one,  the WFE instance could be shared among them.
  • Topic Leader: 
  • Volunteer Note Taker: 
  • Duration: 3 hours
  • Interested In Attending: 

Work Flow Discussion

Validation of Dependency Graph (Day 1 - Main Conf. Bridge)


E2E

Test Cases (Day 1 - Main Conf. Bridge)

Validation of Dependency Graph (Day 1 Agenda)

Release Status, Release Process and Scrum Board Usage (Day 1 - Main Conf. Bridge)

  • Description: This session will cover 3 main topics:
        1. Where do we stand in regards to Amsterdam Release Planning
        2. From a process perspective, what are the next milestones, and what is expected from each team
        3. How do we provide adequate transparency across teams by using Scrum Board

E2E Test Cases (Day 1 Agenda)

Demo Ownership & Planning

Release Status, Release Process and Scrum Board Usage (Day 1 Agenda)

  • Description: This session will cover 3 main topics:
        1. Where do we stand in regards to Amsterdam Release Planning
        2. From a process perspective, what are the next milestones, and what is expected from each team
        3. How do we provide adequate transparency across teams by using Scrum Board


Use case subcomittee meeting (Day 3- Main Conf. Bridge)

Demo Ownership & Planning

Open Lab subcommittee meeting

Use case subcomittee meeting 

Open Lab subcommittee meeting

VoLTE Use Case Control Loop Automation 

...

  • Examples of DCAE template, CLAMP/Cloudify Blueprint, Config Policy, Operational Policy and related files needed to be designed and used in the control loop. If a series of practical examples can be provided, like all related examples of the vFW demo, which is better for us to understand.
  • Developer guidelines to design the control loop to achieve the requirement of VoLTE. Demo of the entire process, e.g. create, deploy, etc., which is a better way help us to learn, if it can be provided.
  • The solution of Holmes deployment, integrated with DCAE or others, e.g. workflow, DCAE Template, API, etc.
  • The solution of design, creating and distributing Holmes rules, e.g. refer to Policy, or other solutions, etc.
  • The requirement of Policy to invoke the API of VF-C.
  • The API document of VES collector in DCAE is used by VF-C to report VNF FCAPS data.

...

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

VNFRQTS - Guidelines & Requirements/chapter structure of the documents

  • Description: The ONAP VNFRQTS are supposed to be an integrated set of deliverable documentation. An agreed document outline structure permits the sections of the documents to be developed independently. Initial proposal based on chapters from some of the seed documents. Another proposal was to structure chapters towards intended users of the VNF Requirements documents - based, e.g. on the VNFRQTS JIRA epics. 
  • Topic Leader: Wenyao Guan, Steven Wright
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 0.5 hour
  • Link to data Source (if applicable) VNF Document Outlines
  • 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.

VNFRQTS - Use Cases & Test Case Descriptions/chapter structure of the documents

  • Description: The ONAP VNFRQTS are supposed to be an integrated set of deliverable documentation. An agreed document outline structure, and templates permits the sections of the documents to be developed independently. Initial proposal proposals based on chapters from some of the seed documentsprevious types of documents in the industry. Another proposal was to structure chapters towards intended users of the VNF Requirements these documents - based, e.g. on the VNFRQTS JIRA epics, or other ONAP projects as users of these document types. 
  • Topic Leader: Wenyao Guan , Steven Wright
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 1 hour for Guidelines (Hope Time Slot :July 26, Wednesday UTC 12:00)
  • Link to data Source (if applicable) VNF Document Outlines
  • 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.

VNFRQTS - Use Cases & Test Case Descriptions/chapter structure of the documents

...

Developer's Typical Setup (Day 3 - Main Conf. Bridge)

Developer's Typical Setup

Security

...

  • Vulnerability sub-committee, PTLs be prepare to help if needed
  • CII badging program
  • Vulnerability scanning
  • Feedback from the community
  • For this 30 mins should be enough
  • (stretch, as an extra topic, deepdive of the CII badging program from David Wheeler)

...

Security (Day 1 - Main Conf. Bridge)

  • Description: Update from Security sub-committee.
    • Vulnerability sub-committee, PTLs be prepare to help if needed
    • CII badging program
    • Vulnerability scanning
    • Feedback from the community
    • For this 30 mins should be enough
    • (stretch, as an extra topic, deepdive of the CII badging program from David Wheeler)
  • Topic Leader: Stephen Terrill (and security sub-committee).
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source -
  • 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.

OOM and Integration / Release

  • Description: Integration / Release depends on OOM for packaging and distribution. In this session, we will discuss:
    •  How Release could leverage OOM and also what we could use for R1.
    • Format for R1 distribution, docker images or/and others?
    • Configuration Management
    • others?
  • Topic Leader: TBD
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source -
  • 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.
  • Description: Integration / Release depends on OOM for packaging and distribution. In this session, we will discuss:
    •  How Release could leverage OOM and also what we could use for R1.
    • Format for R1 distribution, docker images or/and others?
    • others?
  • Topic Leader: TBD

OOM and Integration / Release

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

VoLTE Service Design and Instantiation 

  • 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

Architecture for Amsterdam and Beijing (Day 2-  Main Conf. Bridge)

  • Description: Present the latest architecture from the ARC subcommittee and begin project-by-project flow walk-throughs

  • Topic Leader: Chris Donley
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:

...

  • 1 hour
  • 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.

Architecture for Amsterdam and Beijing (Day 1 Agenda)