feat(openstack): convert our openstack prereqs to a helm chart

Convert our OpenStack prerequisites to a helm chart so we can make it
easier to modify parts of these configs and add more in the future.
This builds on the ideas in #531.

Author: cardoe

apps/site/openstack.yaml

@@ -3,5 +3,10 @@ component: openstack
 sources:
   - ref: understack
     path: 'components/openstack'
+    helm:
+      releaseName: openstack
+      valueFiles:
+        - $deploy/{{.name}}/helm-configs/openstack.yaml
+      ignoreMissingValueFiles: true
   - ref: deploy
     path: '{{.name}}/manifests/openstack'

components/openstack/.gitignore

@@ -0,0 +1 @@
+charts/

components/openstack/Chart.yaml

@@ -0,0 +1,24 @@
+apiVersion: v2
+name: openstack
+description: UnderStack resources for OpenStack Helm
+
+# A chart can be either an 'application' or a 'library' chart.
+#
+# Application charts are a collection of templates that can be packaged into versioned archives
+# to be deployed.
+#
+# Library charts provide useful utilities or functions for the chart developer. They're included as
+# a dependency of application charts to inject those utilities and functions into the rendering
+# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+type: application
+
+# This is the chart version. This version number should be incremented each time you make changes
+# to the chart and its templates, including the app version.
+# Versions are expected to follow Semantic Versioning (https://semver.org/)
+version: 0.1.0
+
+# This is the version number of the application being deployed. This version number should be
+# incremented each time you make changes to the application. Versions are not expected to
+# follow Semantic Versioning. They should reflect the version the application is using.
+# It is recommended to use it with quotes.
+appVersion: "1.16.0"

components/openstack/README.md

@@ -1,3 +1,5 @@
 # OpenStack
 
-These contain the pre-req components for deploying OpenStack.
+This is a Helm chart where UnderStack creates all the prerequisites
+for deploying OpenStack Helm. In some cases service/component level
+objects (like Keystone Users) are defined here to avoid duplication.