...
- Mike Elliott config work -
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-460 - Mike presented to Arch subcommittee and the PTL coordinators meet on monday
- Presentation of config separation - the large tarball in the config container
- Give application teams access to the config - so we have 1 copy
- Work with teams on what is the config and config mechanism
- Q: Viswanath Kumar Skand Priya - we can have config ecosystems (dev/prod/stg) - yes
- Will use helm directly instead of the sh/bash wrapper we currently use
- Could use same doc like git symlink for config
- Working with Linux Foundation to see if the above is possible - for now we keep the config in OOM and the teams own/modify/commit changes (sort of how AAI currently does) - need to discuss with app teams
- Q: Hong Chen - onboarding template? good question - this is available via parameterization of the config
- Q: CI/CD question - yes we can be used for CI and CD
- Existing running CD pocs (run on daily docker merges + current hourly OOM config) - Integration and OOM teams below
- (official LF POC)
- https://jenkins.onap.org/view/External%20Labs/
- (Older reference POC)
- http://jenkins.onap.info/job/oom-cd/
- Working with OPNFV as well on their AUTO project (they have a rich CD ecosystem)
- The intent of the env files that mike has shown - is to target a particular deployment (all the way from a component developer to a full prod deployment)
- For the config question (distributed vs centralized) - we will be centralized for now - future plan is to be distributed (pending change control maturity)
- Music project integration with OOM - tasks Viswanath Kumar Skand Priya
...