...
Provide required ONAP Commands to operate the ONAP from Linux Operating system console & Docker to perform the different use cases identified for the release Amesterdam.
Minimum Viable Product
Create the OPEN CLI framework and provide
Provide required Linux Console commands for ONAP 1.0 and docker environment
Run time environment with docker
Standardise open-cli-schema 1.0
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.
...
Longer term roadmap
As CLI plays a major role is critical in devops environment, in future, CLI will be extended to use in VNF boot scripts, ONAP components integrations, OOM and Integration projects to make the ONAP integration point smoother and easier.
...
- AAF/Portal project
- for Authentication and authorization
- MSB/A&AI project
- for service discovery
- Integration project
- for creating the docker scripts,
- Integration scripts
- Jenkins and sonar integration
- To provide the require CLI for Following projects
- SO
- Policy
- Controllers (APPC/SDNC/VFC/Multi-VIM)
Architecture
High level architecture diagram
...
API Incoming Dependencies
List Following table shows the API this release is expecting from other releases.list of API depends by CLI framework
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| AAF/Portal user API | For user authentication and authorization, CLI uses AAF/Portal user API | Date for which the API is reviewed and agreed TBD : after discussion with respective team | TBD : after discussion with respective team | Link toward the detailed API description TBD : after discussion with respective team |
| MSB/A&AI | For service discovery, currently CLI framework supports MSB and i am not sure whether this feature will be part of A&AI in release A? | - do - | - do - | - do - |
NOTE: To provide the required commands for each of the ONAP services, this project will depends on the REST API provided by every other services such as SO, AAI, DCAE, policy and SDC
CLI Outgoing Dependencies
...
| API Name | CLI Description | CLI Definition Date | CLI Delivery date | CLI Definition link |
|---|---|---|---|---|
| To fill out onap <command> | TBD by M2High level description of the CLI | M2 (as per the release plan) | M2 (as per the release plan) | Link toward the detailed CPI description |
...
| Name | Description | Version |
|---|---|---|
| Docker | Docker container for CLI | Aligned with existing Docker version of ONAP |
| Ubuntu | For running CLI manually | 14.04 / 16.04 32-bit/64-bit |
| Open JDK | For Java RTE | 1.8 |
Testing and Integration Plans
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| AAF availability | CLI is depending on the AAF for user authorization as AAF is approved project. In the mean time, it would try to use Portal API for the same. | - |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...