Remove all data containers from the repository except the one image
we intend to reuse for each data container. Adjust compose files to
remove all references to the unique data containers which serve no
purpose other then to take up extra resources.
Needs VOLUME in data containers exported in the compose files.
Change-Id: Id7746110946ef9836180cf57302aaf827e7e5405
Partially-Implements: blueprint one-data-container
This converts all MD formatted docs that were renamed to RST to
preserve git history into actual RST documentation. Some minor
edits were made but in general the purpose of this patch is to
*only* convert the documentation not rework the documentation.
I do plan on reworking the documentation in further patch sets.
All links were tested and a test rendering is available:
http://github.com/sdake/kolla
Change-Id: I3df430b14df1ede15407c7f4ba7afcbdc6f9d757
Sphinx and OpenStack documentation standards require the use of
RST formatted documentation. In order to get out docs integrated
into docs.openstack.org, the following steps must be taken:
1. we need to first convert the documentation to RST
2. sphinx support must be added to the repository
3. project-config must be updated with a publish-docs job
The ability to pubish to docs.openstack.org is a privilege only
available to Big Tent projects. As a result, we should be taking
advantage of this to help spread the word on our implementation.
Note the documentation was converted with a tool called pandoc
the syntax of which was:
pandoc -f markdown -t rst file.md > z
mv z file.rst
In order for git to preserve history the files have to be git mv'ed
in one commit followed by the pandoc operation in a separate commit.
Change-Id: Iba2a70b989e8305da03e8204a9b130d457b00cf0
* Both api and engine start up without error, but can't test properly
until Horizon is fixed (bug #1482196)
* These are source installs are there no RPMs available for Murano
that I can find.
* Also requires a plugin for horizon that will be made as a
separate commit
Co-Authored-By: Mick Thompson <michael.a.thompson@oracle.com>
Implements: blueprint enable-murano-container
Change-Id: Ia46985b21bb5f6d7690501e7199800c8c7fcb51f
Renamed kolla script to kolla-compose
Update change in the dev guide also
Change-Id: I6cae3d13752ecb4bb3deeb91c5e0f827fde80c2a
Implements: blueprint kolla-compose-script
Added the compose yaml file
Added the genenv
Added fixes to run the containter
Change-Id: Ied3ea92e495fc0fc0274a0da736394d2ab52a754
Partially Implements: blueprint ceilometer-container
Due to a revert in the Docker code, thin neutron containers do not work
at this time. The neutron plugin agents do not need to exist in the same
container as the other agents however. This allows for using either
linuxbridge or openvswitch
The docker commit that did the revert:
ff770d33cd
Closes-Bug: 1469307
Change-Id: Idf79c31c74c34b93f5a9bac49730aca49bbdb861
Key difference here is the ip_wrapper.py file. This file and docker 1.7
allow for the network namespaces to be created in the host mount
namespace and propogated into the containers.
Co-Authored-By: Paul Bourke <paul.bourke@oracle.com>
Change-Id: I73bcd1c97bbaf742af883dbf281a8d76aff8aebf
This commit adds a few dependencies (that are actually packaging errors)
present in all of the containers, as well as specifically in
heat-engine. Some of the environment variables were not set correctly in
the heat-api-cfn container. The environment variables have also been
correctly added to the genenv script.
Also removed duplicated compose file data already present in
heat-api-engine.
Closes-Bug: #1461872
Change-Id: I9631d1bc6ea42425272570a9dda8cbf5edcef4f3
This patch adds the docker-compose files, updates the docs,
and adds cinder to the start command.
Implements: blueprint container-set-storage-operation
Change-Id: I5386851e2247c00696704dc26a8a286451d4bf59
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
Glance images were originally intended to be stored on the host (see
container Dockerfile) but the compose file was not doing this. The
right thing is to use a data container for image content.
Closes-bug: #1465401
Change-Id: I02d2aab2913356939d98b8c18f9e788ae6d901af
Co-Authored-By: Ryan Hallisey <rhallise@redhat.com>
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
Previously, the keystone compose yml was referencing juno instead
of kilo when all other services are using kilo. This patch upates
the yml to use the keystone image with the kilo tag.
Change-Id: Ib4f551ad303bd44f0a5c45fc9d5f7d53f376caf7
All VNC-specific configuration bits are moved from nova-api-base to
nova-compute and the new nova-novncproxy and nova-consoleauth
containers. The compose specification has been updated to reflect this.
A future patch will make the desired backend configurable (spice/vnc).
Change-Id: I8b64abf125fd1ecd7d3463515e3717dd9bd60420
Blueprint: novnc-container
This represents making build-docker-images --release build
with the icehouse tag and causes docker-compsoe to pull from
the icehouse tag.
Partially-implements: blueprint port-kilo
Change-Id: I66b2c39abc55c0f47152dd90e696fc46b9c58f50
Add Heat-api-cfn for wait conditions
Magnum needs wait conditions in order to operate properly. heat-api-cfn
is where wait conditions connect.
Change-Id: I56742dd96e4607dc0042d0cef4e18c922f9ed736
Implements: blueprint container-heat-api-cfn
Fix issues reported in https://review.openstack.org/#/c/177681/3, and
simplify detection of cirros images in glance.
Only add developer's SSH key to nova if ~/.ssh/id_rsa.pub exists and is
readable.
Change-Id: I5936c6db399d63902d460b0d3c959619073cc3cc
Configure nova networking and nova quotas to allow 40 m1.small
instances to run. Checks for keystone credentials set. May only
be run once.
Change-Id: I36e01d42ec283651babbb59268452a65e644626e
Nova uses a data container. Data containers are expected to
use the VOLUME keyword and then use volumes_from to access
those volumes. Throwing in a bindmount to the host filesystem
results in unpredicble behavior, usually in the form of files
being stored on the host filesystem that should be persisted
in the compute data volume.
Change-Id: I60a7873995c9397368ed4df61d5a6d4e8250f3c2
This is supposed to prevent proliferation of scripts in "tools"
directory and reduce code duplication.
This first patch replaces tools/{start,stop,pull,status} scripts and
more commands are to be added in the future.
Change-Id: I3d99cf5033be8631d8e6f32a4c34d3b5ffcae7e8
Previously, compose would generate an error because the
neutron-agents.yml file was missing a space for the restart policy
line.
Change-Id: Ib17c4c726dcfcda780a242ebe22474e9252cac8a
Previously, the agents ran in seperate containers. Since some of
the agents create and use network namespaces, runnning them in
seperate containers has become a challenge. This patch adds
neutron agent support in a single container.
Partially Implements: blueprint compute-operation-neutron
Change-Id: If4f893abd50d90b58e8435ec2659870dce36951c
We have to overlay the /lib/modules folder from the host to properly
`modprobe` from within a container. We don't have to give it write
permissions however, so the docker-compose volume is mounted in as 'ro'
Change-Id: I95101136dad56e9331d8b92cd394495f7bd0576a
If a system is rebooted with kolla running, all the services will
continually restart. There appears to be some locking problem in
docker which will result in docker imploding. One problem is a
key dependency, mariadb, is never started on a reboot because it is
missing restart: always. Also restart the mariadb data container
until it returns success.
Change-Id: I599d28548ff041712d54a702c80fe36c321adf7f
Previously, nova enabled_apis was hard coded and metdata_host
was using PUBLIC_IP param instead of exposing an individual
param.
Extending these params and creating a separate compose yml that
includes compute/libvirt/network/api is required to support
nova network multi_host.
Additional details can be found here:
http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html
Change-Id: I5d417a0ee460f8ad9b2982fe83d63ab57013918e
A data container is meant to operate without bindmounts.
Change-Id: I2624a63fd75db7ed8050054c17e19885f8a7ac8a
Co-Authored-By: Daneyon Hansen (danehans@cisco.com)