
During the Queens cycle, Cinder introduced the ability to specify the backup driver via class name and deprecated backup driver initialization using the module name. (Id6bee9e7d0da8ead224a04f86fe79ddfb5b286cf) Legacy support for initialization by module name was dropped in Stein. (I3ada2dee1857074746b1893b82dd5f6641c6e579) This change will support both methods of initialization and leave the driver defaults enabled for module based initialization (valid through Rocky images). This change has been tested using the OSH default Cinder (Ocata) images and StarlingX images based on master (Train). Change-Id: Iec7bc6f4dd089aaa08ca652bebd9a10ef49da556 Signed-off-by: Robert Church <robert.church@windriver.com>
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 Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
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.