2024cc361e
For recent releases we use 32GB nodes for compute-kit jobs. The number of such nodes is extremely limited. So we'd better use multinode nodesets for compute-kit jobs. We deploy K8s using kubeadm and then we set labels to the K8s nodes so charts can use these labels for node selectors. We deploy L3 agent only on the node where we run test scripts. This is because we want test virual router to be always created on this node. Otherwise the L2 overlay needs to be created to emulate provider network (will be implemented later). Glance is deployed w/o backend storage (will be fixed later). Change-Id: Id2eb639fb67d41006940a7d7b45a865b2f1124f7
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 @ 1500 UTC], #openstack-helm in IRC (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 minikube based all-in-one solution that runs in a Docker container. The 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.