...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | BeijingCasablanca |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Huawei, ZTE, China Mobile, AMDOCS, Intel, Orange, Coriant, Bell Canada, Tech Mahindra, Brocade |
...
The SDN-C project provides a global network controller, built on the Common Controller SDK, which manages, assigns and provisions network resources. As a "global" controller, the SDN-C project is intended to run as one logical instance per enterprise, with potentially multiple geographically diverse virtual machines / docker containers in clusters to provide high availability. The project also will support the ability to invoke other local SDN controllers, including third party SDN controllers.
In the Beijing Casablanca release, the SDN-C project will be used to manage, assign and provision network resources for the Beijing Casablanca release use cases, listed in the Use Cases section below.
...
- Virtual Domain Name Server (vDNS)
- Virtual Firewall (vFW)
- Virtual Voice over LTE (vVoLTE)
- Virtual Customer Premise Equipment (vCPE)
- CCVPN *** New in Casablanca
Minimum Viable Product
The Minimum Viable Product for Beijing is the set of capabilities needed to support the use cases listed above.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sdnc and issuetype in (story) and status!=CLOSED SDNC AND issuetype = Story AND fixVersion = "Casablanca Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Subcomponents of each ONAP project may be found on the Resources and Repositories (Deprecated) page on this wiki. Please see the SDN-C section of that page for subcomponent list of SDN-C.
...
List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| Functional requirements are incompletely defined | Functional requirements that are not sufficiently defined for sizing by 16/18 21 will not accepted into Beijing release | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.