...
- Update / Progress
- Michael O'Brien - (deprecated as of 20170508) - use obrienlabs discussed with the Policy team.
- Policy team using Vagrant
- They need ONAP 1.1.1 to work. Team agreed that making 1.1 working in Kubernetes is the top priority
- DCAE Gen 2 dependency
- AT&T has code available for DCAE gen 2.
- Should be available in a few weeks
- It was agreed that the OOM team will require to make DCAE work on OOM, and then work on DCAEg2 when ready
- Borislav Glozman has committed code for config management
- Commits have been done more than a week ago. Need committers to review and approve
- Mandeep KhindaMike Elliott agreed to review by EOW
- Michael O'Brien - (deprecated as of 20170508) - use obrienlabs has started contributing to the code but is not currently a committer.
- Add to committer list
- Michael O'Brien - (deprecated as of 20170508) - use obrienlabs discussed with the Policy team.
- TOSCA based orchestration demo
- Arthur Berezin presented concepts
- Cloudify provides a consistent TOSCA model for app deployment
- How does it integrate with Openshift or rancher? Answer: the operator will be allowed to chose options. Provides the flexibility of deployment.
- Team agreed that the deployment mechanism must be a choice for the operator - nothing forced by the OOM platform.
- Q: It seems you are wrapping a 50 lines file in a 500 lines file. Why? A: To provide consistent app descriptors across deployment mechanisms (openstack, bare metal, K8S, etc).
- Need to understand between K8S and Cloudify. Are we preventing K8S to perform its job by adding Cloudify on top? A: Cloudify is decoupled from K8S. We are delegating a portion of the orchestration to K8S. Cloudify is adding value on top of K8S, and letting K8S do what it does best: container orchestration.
- Goal of Cloudify is really to use a TOSCA based approach to deploying applications.
- John Ng presented the AT&T progress on Cloudify
- AT&T needs to bring the code upstream earlier
- @john
- M2 functionality freeze
- Next objectives
- Team agreed that making 1.1 working in Kubernetes is the top priority
- Fix the ZOOM meeting for next meeting.
- Arthur Berezin will share blueprint as seed code.
- Need to allow people to push code that is not working
- Team agreed that we should use an Upstream first approach to OOM. Same concept should be applied to ONAP wide. David S to bring issue to TSC tomorrow.
- John Ng will reach out to internal AT&T team members to see how soon the code can be uptreamed. The idea is to make sure we create a community around OOM.