Notes
- AAI issue on friday fixed the release-1.1.0 build
- F2F meeting - some of the team are still coming in...
- F2F award for Innovation Project to OOM
- F2F 8 meetings - all a lot participation - will post presentations, check recordings - michael to fill out
- F2F breakout with DCAE , ATT, Cloudify for 2 hours - to go over possible common layer to two options - the original current production level Kubernetes standard and or a Tosca based option for implementation that has mixed deployment optionsalternative technology options as required.
- The goal is to have a single set of configuration - Ideally components own their config
- Logging: Luke Q: Helm 2.5+ tpl use - can Tosca use this with out helm - Cloudify Tosca solution has a helm plugin via their own extended Tosca spec.
- A) Borislav: review possible proposal to read in a common parameters file into helm during deployment
- Luke Q: any config values left as not templated? Need to discuss whether all in OOM or referenced
- Observation that forked config could be an issue - need to discuss with Architecture meeting
- Investigate moving baseline helm 2.7.2 from existing 2.3.0 on both server/client for Beijing - need to do extensive testing on the master branch - need to fix both
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-486 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-441 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-429 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-510 - Document helm config more clearly on the wiki/RTD
- DCAE team will discuss their development environment option for a reduced CDAP footprint with us - will post page, links - michaellinks
- Work closely with Jing Wang - follow DCAE mS Deployment (Standalone instantiation)
- DCAE R2 requirements - their config and runtime policy options, their HA solution for Consul and Postgres
- Open-O: Work with Chengli Wang