2017 DCAE

Meeting summary with OOM on integration and deployment
Dev status.
CICD integration status.
Testing status.
Call for volunteer for helping Documentation Project for readthedocs (http://onap.readthedocs.io/en/latest/index.html)
Planning for September F2F
Alok Gupta presentation on vendor spec yaml use in SA

Materials

Beijing Release possible topics
1. Multi-site deployment of DCAE
2. Data storage and API
  1. Support for PostgreSQL within a container
  2. Support for additional DBs within container
3. VES extension for accommodating more information on the payload and support A&AI enrichment
4. “Reconfiguration” and “reuse” of components for new close loops
5. More harmonization with other components
  1. e.g. Consul use with MSB
6. More collectors
  1. SNMP Polling
  2. Ceilometer
7. More analytics
  1. CDAP Pipelining
8. Collectd (* parallel activities in MultiVIM project)
Alok presentation: ONAP SA Dsicussion 2.pdf

08/30/2017 OOM-DCAE Meeting on Deployment Strategy

Summary:

"While the discussion on longer term strategy will continue, the teams have converged on a short-term solution for R1. The high level description is as follows.

The teams will begin to “containerize” the bootstraping script (under project ccsdk/utils) that DCAEGEN2 uses for standing up its Cloudify Manager.

Next both teams will work together on enhancing this container so that it becomes the “command station” that will be able to call the Cloudify Manager with a sequence of blueprints to complete the deployment of the DCAEGEN2 system.

How APIs are exposed and configured are also discussed under the above umbrella understanding of how DCAEGEN2 will be stood up.

DCAEGEN2 will expose two APIs to the rest of the ONAP system, the VES collector API and the Deployment Handler API. A number of options were discussed for how to expose including DNS based solution, and MSB based solution.

DCAEGEN2 will also expect the knowledge of APIs exposed by other ONAP components, such as DMaaP Message Router, A&AI and Policy. Previously DCAE was expecting to use well-known URLs. Now other possibilities are opened such as having OOM inject such parameters into the “command station” container which will then write into DCAE Consul as KV for its components to read.

The two teams will work closely to implement this solution for R1."

Recording: OOM-DCAE-20170830.mp4

08/24/2017 DCAE Weekly Meeting

Agenda