Vladimir Kozhukalov 1a885ddd1f Update deployment documentation

Recently we updated our test jobs so that all of them
use the `deploy-env` Ansible role which utilizes the
Kubeadm to deploy the test Kubernetes cluster.

The role works for both multi-node and single-node
environments. Although the deployment of Kubernetes itself
is out of scope of Openstack-Helm, we recommen using this
role to deploy test and development Kubernetes clusters.
So at the moment there is no need to provide
different sets of tools single-node and multi-node test envs.
Now this is a matter of the Ansible inventory file.

Also the deployment procedure of OpenStack on top of Kubernetes
using Helm is the same for multi-node and single-node clusters
because it only relies on the Kubernetes API.

We will be improving the `deploy-env` role even futher and
we will be cleaning up the deployment scripts and the documentation
so to provide a clear experience for the Openstack-Helm users.

Change-Id: I70236c4a2b870b52d2b01f65b1ef9b9518646964

2023-10-23 19:10:30 -05:00

3.3 KiB

Raw Blame History

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.

Versions supported

The table below shows the combinations of the Openstack/Platform/Kubernetes versions that are tested and proved to work.

Openstack version	Host OS	Image OS	Kubernetes version
Victoria	Ubuntu Focal	Ubuntu Focal	>=1.24,<=1.26
Wallaby	Ubuntu Focal	Ubuntu Focal	>=1.24,<=1.26
Xena	Ubuntu Focal	Ubuntu Focal	>=1.24,<=1.26
Yoga	Ubuntu Focal	Ubuntu Focal	>=1.24,<=1.26
Zed	Ubuntu Focal	Ubuntu Focal	>=1.24,<=1.26
Zed	Ubuntu Jammy	Ubuntu Jammy	>=1.24,<=1.26
2023.1 (Antelope)	Ubuntu Focal	Ubuntu Focal	>=1.24,<=1.26
2023.1 (Antelope)	Ubuntu Jammy	Ubuntu Jammy	>=1.24,<=1.26
2023.2 (Bobcat)	Ubuntu Jammy	Ubuntu Jammy	>=1.24,<=1.26

Communication

Join us on IRC: #openstack-helm on oftc
Join us on Slack (this is preferable way of communication): #openstack-helm
Join us on Openstack-discuss mailing list (use subject prefix [openstack-helm])

The list of Openstack-Helm core team members is available here openstack-helm-core.

Storyboard

You found an issue and want to make sure we are aware of it? You can do so on our Storyboard.

Bugs should be filed as stories in Storyboard, not GitHub.

Please be as much specific as possible while describing an issue. Usually having more context in the bug description means less efforts for a developer to reproduce the bug and understand how to fix it.

Also before filing a bug to the Openstack-Helm Storyboard please try to identify if the issue is indeed related to the deployment process and not to the deployable software.

3.3 KiB Raw Blame History