DRAFT PROPOSAL FOR COMMENTS
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | R1 Amsterdam |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Chinamobile, JIO, VMVare |
Scope
What is this release trying to address?
...
- Cloudify-manager (blueprints/plugins)
- Consuls
- cdapbroker
- deployment-handler
- servicechange-handler
- inventory-api
- policy-handler
- configbinding
- registrator
- ves
- Postgres
Below is the interaction/flow between these components.
ONAP Dependencies
List the other ONAP projects your depends on.
VNF’s – The VNF’s – The VNF supporting the R1 usecase should comply with VES specification or be able to send SNMP Traps to DCAE
Policy Policy – For sending dynamic configuration and rules for analytics into DCAE. Policy-hander also uses policy-engine client-lib provided in PolicyEngine-0.9.win32.tar file.
CLAMP – CLAMP – For create/update DCAE collector, analytic and micro service configuration Policies.
DMAAP - DMAAP – We are dependent on Dmaap for pub/sub of events/Control Loop messages (to Policy and APP-C)
OOM OOM – For instantiating the DCAE controller
CCSDK CCSDK – For deploying database as a service for DCAE.
MSB - Integration MSB – Integration with MSB (stretch)
Multi-VM - VIM – Integration with Mutli-VM VIM project to leverage infrastructure api (stretch)
...
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.DCAE Platform consist of many sub-components. Given below is the interaction/flow between various DCAE components and external application.
API Incoming Dependencies
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
| DMAAP | DMaaP Message Router is a reliable, high-volume pub/sub messaging service with a RESTful HTTP API. | Date for which the API is reviewed and agreed | To fill out |
| Data Movement as a Platform Message Router |
API Outgoing Dependencies
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
Deployment handler | Deployment handler provides the following API to allow client systems to request installations of components via blueprint, request uninstallation of previously-deployed components, and get status on installation and uninstallation operations. Because installation and uninstallation operations can be long-running, the API is asynchronous. Client systems can poll for results. {Serverroot}/ à [GET] (provides server info) {Serverroot}/dcae-deployments/{deployment_id} à [PUT, DELETE] {Serverroot}/dcae-deployments/{deployment_id}/operation/{op_id} à [GET] | TBD | TBD |
|
Cloudify Manager plugins | Plugins are executed during the installation and uninstallation processes and may make calls to external APIs to create, configure, start, stop, and destroy components OpenStack API for infrastructure API |
|
|
|
VESCollector API for VNF | VESCollector provides following URI structure for events to be published http(s)://{Domain}:{Port}/{optionalRoutingtPath}/eventListener/v{apiversion}/ |
|
|
|
Policy API for DCAE-Policy Hander |
DCAE Policy-handler invokes only calls POST /getConfig (policyName value varies by scope, by policy_id) https://<PDPServer Location>:<port>/pdp/api/getConfig |
|
|
|
SDC API to SCH | SCH uses SDC external API to grab the entire service model and grab artifacts /asdc/v1/catalog/services/<service uuid>/metadata |
|
|
|
Third Party Products Dependencies
...
| Name | Description | Version | |||
|---|---|---|---|---|---|
Cloudify | TOSCA-based cloud orchestration software platform | 3.4.0 (4.0.x) | |||
Consul | Distributed service discovery and KV store | 0.8.3 | |||
| Ubuntu | OS | 16.04 | |||
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
...
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
New onboarding documentation would be provided for users to be able to onboard new mS into DCAE platform
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
...