[Starlingx-discuss] [Containers] Background info on helm charts

[Arevalo, Mario Alfredo C]

Hi Frank, 

Thank you for the information, however my doubts are oriented more to the work-flow
than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the
last week, nevertheless, the starlingx work-flow includes some parts which I have not digested
completely yet. Don Penny have helped me sending useful information related to this (Thanks for that),
the interaction between OpenStack/loci system and python/wheels. However I have some gaps,
for example, as staring point I have to create the docker image which will be consumed by the
chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines
in the build-tools/README which makes reference to a exposed service that is not specified [2,3].
For that reason I asked for a little more detailed information about the work-flow during our meeting today.

Thanks for your attention.

Best regards.
Mario.

[1] https://github.com/MarioCarrilloA/chart-playground
[2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4
[3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9







From: Miller, Frank [Frank.Miller at windriver.com]

Sent: Monday, January 28, 2019 11:19 AM

To: Arevalo, Mario Alfredo C

Cc: Saul Wold; starlingx-discuss at lists.starlingx.io

Subject: [Containers] Background info on helm charts







Mario:
 
On the containers community call this morning we took an action to identify information about helm charts.  Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below.
 
Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference.  2 good examples are:
·        
Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults.  We have added StarlingX specific overrides which are generated from code we added [6].
·        
Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8]
 
Frank
 
[1]

https://docs.helm.sh/developing_charts/ 
[2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221
[3]  https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ 
[4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29
[5] Cinder helm chart in upstream openstack-helm:

https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder 
[6] StarlingX cinder overrides: See cinder.py in

https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm

[7] Helm chart for nova_api_proxy:

https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy

[8] nova_api_proxy override code: See nova_api_proxy.py 
in 
https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm