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
Updates references to Launchpad to now point to Storyboard, since OSH has
migrated to that platform. "Report a bug" type references are updated to
point straight to the OSH project proper in Storyboard, while general backlog
type references are updated to point to the OSH Project Group.
Change-Id: I63e290f34763847e71e14e4471e7ee9460d8cff9
Task: 21684
Story: 2002199
Vladimir Kozhukalov