078a496937
If a Helm upgrade is performed on the OpenStack Umbrella chart using the exact same configuration as the first release, then it's expected for no DaemonSets, Deployments, or StatefulSets to be updated. This did not work as expected. A few changes were required to support this desired behavior: 1. Update glance's configmap-etc.yaml to trim whitespace and convert YAML comment to Helm template comment. Before this change, Helm rendered the template with the YAML comment and a newline for the install phase. On upgrades, Helm rendered the template without the YAML comment and newline causing the hash of configmap-etc to change, thus causing the glance-api Deployment to update. 2. Update openstack.sh script to create a randomly generated memcache secret for glance. Without this change, the glance-api deployment changes each time since Helm randomly generates a new memcache secret if not provided. This behavior is enforced via a new test script, validate-umbrella-upgrade-no-side-effects.sh. The following jobs are always recreated due to hooks: - keystone-bootstrap - keystone-credential-setup - keystone-db-init - keystone-db-sync - keystone-domain-manage - keystone-fernet-setup - keystone-rabbit-init - rabbitmq-cluster-wait Some Jobs are created via CronJobs and could be created during validation. So far, heat-engine-cleaner has been seen, but others could be caught too. So the validation script ignores these pod changes by ignoring if Jobs were recreated. Plus Jobs being recreated should not impact the OpenStack deployment. Change-Id: Iffaa346d814b8d0a3e2292849943219f70d50a23 |
||
|---|---|---|
| aodh | ||
| barbican | ||
| ceilometer | ||
| cinder | ||
| cyborg | ||
| designate | ||
| doc | ||
| glance | ||
| heat | ||
| horizon | ||
| ironic | ||
| keystone | ||
| magnum | ||
| masakari | ||
| mistral | ||
| neutron | ||
| nova | ||
| octavia | ||
| openstack | ||
| placement | ||
| rally | ||
| releasenotes | ||
| senlin | ||
| tempest | ||
| tests | ||
| tools | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| Makefile | ||
| README.rst | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
| yamllint-templates.conf | ||
| yamllint.conf | ||
OpenStack-Helm
Mission
The goal of OpenStack-Helm is to provide a collection of Helm charts that simply, resiliently, and flexibly deploy OpenStack and related services on Kubernetes.
Communication
- Join us on IRC: #openstack-helm on oftc
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on oftc
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Storyboard
Bugs and enhancements are tracked via OpenStack-Helm's Storyboard.
Installation and Development
Please review our documentation. For quick installation, evaluation, and convenience, we have a kubeadm based all-in-one solution that runs in a Docker container. The Kubeadm-AIO set up can be found here.
This project is under active development. We encourage anyone interested in OpenStack-Helm to review our Installation documentation. Feel free to ask questions or check out our current Storyboard backlog.
To evaluate a multinode installation, follow the Bare Metal install guide.
Repository
Developers wishing to work on the OpenStack-Helm project should always base their work on the latest code, available from the OpenStack-Helm git repository.
Contributing
We welcome contributions. Check out this document if you would like to get involved.