OOM Meeting notes - 2017-08-30

OOM Status / Readiness for Code freeze
- MVP on target for Amsterdam code freeze
- Most components in integraqtion testing phase
- Still need to work on Policy, Portal (new CLI container), Logging
- New components such as VF-C, CLAMP, etc will need to be addressed
OOM Plans for Amsterdam:
- How to deploy ONAP for Amdsterdam with some components on OOM and some components on HEAT (eg. DCAE)?
  - We need to have 1 operational manager for all components for Amsterdam
  - DCAE Gen 2 is different - they have an independent DCAE environment and is not built as the rest of ONAP (own cloudify, own consul, etc)
  - How will it integrate to MSB? The likelihood that it integrates to MSB is low - DCAE is a self-managed platform
  - Proposal #1 for Amsterdam:
    - Startup DCAE gen2 controller from OOM.
    - That controller would take over the deployment of DCAE gen2 with all VMs independently of what is happening of OOM
  - Proposal #2 for Amsterdam
    - Re-use the controller of DCAE gen2 and bring it "as part of OOM"
Cloudify
- Code upstreamed for K8S provisioning; wiki created;
Next steps