Configuration files for kayobe
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul b549d2c092 Merge "Update git.openstack.org to opendev.org" 6 days ago
etc/kayobe Synchronise with Kayobe 3 months ago
zuul.d Add Zuul configuration 1 year ago
.gitignore Add tox.ini with pep8 environment that runs yamllint 1 year ago
.gitreview Update git.openstack.org to opendev.org 3 weeks ago
.yamllint Add tox.ini with pep8 environment that runs yamllint 1 year ago
LICENSE Add Apache2 license 2 years ago
README.rst Update git.openstack.org to opendev.org 3 weeks ago
kayobe-env Update kayobe-env for new recommended directory structure 1 year ago
setup.cfg Change openstack-dev to openstack-discuss 5 months ago
setup.py Add tox.ini with pep8 environment that runs yamllint 1 year ago
test-requirements.txt Add tox.ini with pep8 environment that runs yamllint 1 year ago
tox.ini Update git.openstack.org to opendev.org 3 weeks ago

README.rst

Kayobe Configuration

This repository provides configuration for the kayobe project. It is intended to encourage version control of site configuration.

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.