Agenda:
- DCAE Transformation to support Helm: Vijay Venkatesh Kumar
- new top level component "dcaegen2-services" into OOM main chart
- open questions:
- why not onboarding these charts as service from ONAP ?
- if not, we may have some security issues
- proposal add in platform ONAP part a registry and allow user to use a different if not willing to use it
- continuation of discussion next week
Documentation:Eric DebeauAndreas Geissler Sofia Wallin- they couln't join
- helm "official" repository: Sylvain Desbureaux
- try to create a 7.0.0 release
- for Guilin MR, create 7.0.1 charts
- move master to 8.0.0
- review process: Jan Malkiewicz
- multiple commits for one feature is OK but
- use relationship
- all commits must not break gating
- we can have one commit (not there to be merged) which would trigger the feature
- adding a "fix" commit later
- discussion are always open
- multiple commits for one feature is OK but
2 Comments
Vijay Venkatesh Kumar
Hi Sylvain Desbureaux - Thanks for the time on OOM meeting today. Following was the slide presented; will be great if you can look into it and advise feasibility/scope of these OOM specific items for H release (or beyond).
As noted these features are required for dynamic DCAE MS migration to helm which is targetted in I release, hence will be good to get-started platform feature/support work in H release even if under minimal scope.
BtwDamian Nowak /Nokia presented a demo on multicloud k8s plugin on dcae meeting today - looks like it could address requirement #1 (and probably #2). If there is possibility to get that under OOM (platform) scope - that could be an option. We can certainly continue discussion on the next OOM meeting.
Sylvain Desbureaux
Hi Vijay Venkatesh Kumar , no problem, I'll take a look (and Krzysztof Opasiak I believe) so we can progress next week!