Deployment of containerised OpenStack to bare metal using kolla and bifrost
e748c1d591
This bug was previously fixed but the fix did not cover all cases. This issue is still present if an IP address other than 127.0.0.1 or the admin IP address (but not the internal API IP address, which is correct) is in /etc/hosts. For example, in CI we often see 127.0.1.1. This change removes all entries from /etc/hosts for the host's current hostname, other than the internal API IP address. It also adds a call to rabbitmqctl status to verify that the change has worked. Related: We ought to improve the kolla ansible prechecks to catch the case when there is more than one IP address mapping for the host's current hostname. Change-Id: I2cb9928e04005c6961f3de7c571c9a06361c4f23 Story: 2003496 Task: 24773 |
||
|---|---|---|
| .github | ||
| ansible | ||
| dev | ||
| doc | ||
| etc/kayobe | ||
| kayobe | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| tools | ||
| zuul.d | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .travis.yml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| requirements.yml | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| Vagrantfile | ||
Kayobe
Kayobe enables deployment of containerised OpenStack to bare metal.
Containers offer a compelling solution for isolating OpenStack services, but running the control plane on an orchestrator such as Kubernetes or Docker Swarm adds significant complexity and operational overheads.
The hosts in an OpenStack control plane must somehow be provisioned, but deploying a secondary OpenStack cloud to do this seems like overkill.
Kayobe stands on the shoulders of giants:
- OpenStack bifrost discovers and provisions the cloud
- OpenStack kolla builds container images for OpenStack services
- OpenStack kolla-ansible delivers painless deployment and upgrade of containerised OpenStack services
To this solid base, kayobe adds:
- Configuration of cloud host OS & flexible networking
- Management of physical network devices
- A friendly openstack-like CLI
All this and more, automated from top to bottom using Ansible.
- Free software: Apache license
- Documentation: https://kayobe.readthedocs.io/en/latest/
- Source: https://git.openstack.org/cgit/openstack/kayobe
- Bugs: https://storyboard.openstack.org/
- Release Notes: https://docs.openstack.org/releasenotes/kayobe
- IRC: #openstack-kayobe
Features
- Heavily automated using Ansible
- kayobe Command Line Interface (CLI) for cloud operators
- Deployment of a seed VM used to manage the OpenStack control plane
- Configuration of physical network infrastructure
- Discovery, introspection and provisioning of control plane hardware using OpenStack bifrost
- Deployment of an OpenStack control plane using OpenStack kolla-ansible
- Discovery, introspection and provisioning of bare metal compute hosts using OpenStack ironic and ironic inspector
- Virtualised compute using OpenStack nova
- Containerised workloads on bare metal using OpenStack magnum
- Big data on bare metal using OpenStack sahara
In the near future we aim to add support for the following:
- Control plane and workload monitoring and log aggregation using OpenStack monasca