The only files in the docker image directories that differ majorly between
distros are the Dockerfiles (e.g. different package manager mechanisms,
different repo sources, etc).
The supporting files such as the start.sh/check.sh and config files should
largely stay the same between base images.
This change moves these files up into a "common" directory, and symlinks them
in the same way that the build script is managed. This means when adding a new
base distro only new Dockerfiles need to be created. Also, if a distro does
happen to require a vastly different start.sh script for example, one can
choose to simply not symlink to the common and instead drop in a custom one.
Implements: blueprint refactor-base-image-layout
Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284
This changes are providing support for galera cluster. It's important for
project to has got support for database cluster as a one of the steps to
providing High Avability(HA) in Kolla project
Change-Id: If51bb88ab05972d3b8aa8abbbbd2a5480213a10e
Implemented: blueprint galera-container
Cinder is going to be split up into four containers.
- cinder-api
- cinder-scheduler
- cinder-volume
- cinder-backup
Co-Authored-By: Daneyon Hansen <danehans@cisco.com>
Co-Authored-By: Ian Main <imain@redhat.com>
Implements: blueprint cinder-container
Closes-bug: #1460136
Change-Id: I688471151ffa54d547b9aa0f2f2e2ea7f68f288d
Previously, a spec did not exist to define how Kolla will support
highly available OpenStack services.
Change-Id: I8fcc60f26d2cb98179be6b520c13abb22a372ecf
This specification outlines some of the design goals and practices to
be used to implement an Ansible multi-node deployment tool. The goals
of this work are simplicity, optimizing deployment time, and Operator
flexibility.
The long term objective is for Kolla to become the de-facto solution
for deploying OpenStack in containers.
Partially Implements: blueprint ansible-multi
Co-Authored-By: Sam Yaple <sam@yaple.net>
Change-Id: I8c5d8b7e69c4ed54624061428e2fbde6af6a1815
The containers don't work, but alteast they will pass the gate ;)
Change-Id: Ic921f982122889d354cfee47772421d147d9ec57
Partially-implements: blueprint bashate-gate
Make get-image.sh bashate compliant by creating a file in /tmp
for the ifcfg temporary file and using the --upload command instead
of the --runcommand operation.
Change-Id: I4782140e227105f9aa07fb3967665eaaaeeb0cab
Partially-implements: blueprint bashate-gate
This moves a few things around. Namely centos/fedora-rdo-base becomes
centos/rdo/base
fedora/rdo/base
I have also separated out RHEL.
Moves the current scripts in "base" to a "common" folder common to all
images and then recreates the appropriate links to allow all the
containers to build the same way they did before.
This removes all .buildconfs in the system (though they are still usable)
Partially Implements: blueprint refactor-base-image-layout
Co-Authored-By: Martin André <martin.andre@kvhasia.com>
Change-Id: Id63eac1eb9893ceb775c28bf22842dede85c214a
This is a complete DNS solution, with hidden master and bind9 slave.
It lacks the designate-sink service, because there is no true specification
to implement that. It listens for Nova/Neutron events and creates records
though adding those to just 1 domain isn't helping much in an environment
with multiple tenants.
Change-Id: I500fb6058b118d25a4ccfd1d3479830c36af7e2a
Blueprint: designate-container
