...
APPC will contribute partially to the following use cases as part of the functional requirements.
- Scaling Use Case -
- APPC will support retrieving the data to be configured from AAI. This however has a dependency on SO to pass the
vf-module-idof the vDNS that was instantiated.. - Discussions around how Controller Type will be handled are still too vague and unclear, so no commitment can be made to support this. APPC will continue to support APPC and SDNC via the Client Library as was done in Beijing.
- APPC will support retrieving the data to be configured from AAI. This however has a dependency on SO to pass the
Minimum Viable Product
Same as was defined for Casablanca, but with the adding of increasing better performance for starting application, geo-redundancy etc. For details, please see above on S3P section
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
- TBD
Minimum Viable Product
Same as was defined for Casablanca, but with the adding of increasing better performance for starting application, geo-redundancy etc. For details, please see above on S3P section
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Epics
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=appc and issuetype in (epic) and fixVersion = "Dublin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
Jira server ONAP JIRA columns key,summary,type,created,updated, Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=appc and issuetype in (epicstory) and fixVersion = "Dublin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Longer term roadmap
The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make
Longer term roadmap
The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that on-boarding any new VNF/VNFC is just a matter of configuration and data. Longer term items include:
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
List the other ONAP projects you depend on.
APPC depends on the the following components as part of the general ONAP architecture:
- SDC: Rest based interface exposed by SDC. APPC receives notifications from SDC on VNF information. SDC team provides an SDC Listener, which is used by APPC. (Currently we have no use case for this, although supported)
- AAI: APPC retrieves and updates VNF data from/to AAI.
- DMaaP: Message bus for communication with other components in the solution (SDC, DCAE, MSO, Portal, OOM)
- CCSDK - APPC currently gets ODL & DB package from CCSDK; CCSDK and APPC currently must align on ODL version.
- AAF - AAF is used for ODL API authorization
- MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stage. Support of MultiVIM is limited to the Generic_Restart action only.
For the Casablanca release, APPC has dependencies on the following three projects for specific deliverables:
in the centralized page.
ONAP Dependencies
List the other ONAP projects you depend on.
APPC depends on the the following components as part of the general ONAP architecture:
- SDC: Rest based interface exposed by SDC. APPC receives notifications from SDC on VNF information. SDC team provides an SDC Listener, which is used by APPC. (Currently we have no use case for this, although supported)
- AAI: APPC retrieves and updates VNF data from/to AAI.
- DMaaP: Message bus for communication with other components in the solution (SDC, DCAE, MSO, Portal, OOM)
- CCSDK - APPC currently gets ODL & DB package from CCSDK; CCSDK and APPC currently must align on ODL version.
- AAF - AAF is used for ODL API authorization
- MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stage. Support of MultiVIM is limited to the Generic_Restart action only
- CCSDK - - Oxygen ODL & MariaDB plus Galera
- SO - for scale out scenario to deliver the correct data to retrieve AAI information
- AAI - for named query to return the applicable data (Action: Need to discuss with AAI if they will provide named query or expand name query provided in Amsterdam.
Architecture
High level architecture diagram
...