Previously glance was not using keystone for authentication. This resulted
in --is-public true failing when doing image-create.
Co-Authored-By: Lars Stedman (larsks@redhat.com)
Change-Id: I54273115242ee169201643fe0ad559392650c883
The hostname command is required to allow mariadb to access
the network properly. Without it, in some cases mariadb cannot
execute name service resolution.
Change-Id: Ia215585faad23012143b63c4d82acd6ba69f59b7
The keystone container was changed to only add a keystone user. The rest
of the infrastructure in Kolla expects the name "admin" from a "can I
use a client to access the APIs perspective." As a result, we need a user
for keystone and a user for admin which this patch adds.
Change-Id: I3a3e938f946df1fd5982e89397ef61368f1f3674
This affects both fedora and the centos base images.
Wait_for will be intregrated into kolla-common.
Co-authored by: Charles Crouch <charcrou@cisco.com>
Change-Id: Ide2304b787d4c3bf6fb3949f09e2cf1f450c2173
Libvirt contains a package that sets the permissions of KVM.
If the host does not have libvirt installed the permissions
will never be set and nova boot will fail.
Change-Id: Ie5509199391db55e0984d59a6623f021f3ae46c1
Adds Keystone Container-Set support
Previously, Keystone containers were configured for use in a
Kubernetes environment. This patch removed k8s dependencies and
adds container set functionality.
Change-Id: I131ce205857110bbee49fe81a4a005f9e273ce09
This patch overlaps a little bit with https://review.openstack.org/#/c/162358/.
There were some additional glance config that needs to be added to run without
kubernetes.
Co-authored by: Charles Crouch (charcrou@cisco.com)
Change-Id: I1aab2f6e4a80aaf1e6c4b7fe330bcf9a7740fdc6
By changing the PREFIX variable in the .buildconf one is now able to
build docker images from different bases.
For example, add the following line to your .buildconf file to build
CentOS based images:
PREFIX=centos-rdo-
Default base image is Fedora. For now only RH family is supported.
Additionally, changing the namespace either with the NAMESPACE variable
in .buildconf or via --namespace commandline option now changes the
source namespace as well from the default kollaglue one.
Implements: blueprint multi-baseos
Co-Authored-By: Steven Dake <stdake@cisco.com>
Change-Id: I3964cd2292789ea883a1f2d2738a5731a4fff49b
This imports sdakes' nova-docker codebase to show that atomic upgrades
work atleast with nova networking. This has many corrections.
For more details read:
http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-compute-nodes/
Implements-blueprint: blueprint libvirt-container
Partially-implements; blueprint container-set-compute-operation-nova
Change-Id: I858ea113c5656b6da5d2fd13502fecdbd085c8da
All base images should have a .buildconf that blanks the PREFIX variable
otherwise the buildscript prepends the prefix to its name, for example
centos-rdo-centos-rdo instead of simply centos-rdo.
Change-Id: I48209e708094ae28681a874bf12a0206c524b639
These tags don't belong in docker files. Instead we should put them
in the build system since the build system will be creating a custom
From line in the Dockerfile.
Partially-implements: blueprint multi-baseos
Change-Id: I68d0a0e572e35f39dbe21f7c536d7ac4ca885da3
Keystone relies on crux. Crux is now installed in the base images, so
individual images don't need to install crux.
Partially-implements: blueprint multi-baseos
Change-Id: Id9ed5fb8bc74de6a36f28a6b2bc8ba055c31a32e
Swift containers were pulling in fedora-rdo-base when they should have been
pulling in fedora-rdo-swift-base.
Partially-implements: blueprint multi-baseos
Change-Id: Ic0d03cbca5790aa3002110ba40a802957a481496
The operation is meant to clean the cache, but instead the agents
are running "yum install yum" which is incorrect.
Change-Id: I8e207e93bb10361a7afbbfd02ab11d12ad1cd77c
Previously, the rabbit container was configured for use in
a k8s cluster. This patch updates the container to run with fig
instead of k8s.
Change-Id: Ie04f2f16771c0f733b7b09b7747325bf0d7fb1a9
This patch provides an initial implementation of docker-compose
(i.e. fig). docker-compose runs in a container. The container is
only instantiated when invoked to manage a container set
(i.e. docker-compose up) and then stopped when the command is
finished executing.
Change-Id: I797f06bed773192129b57aae9824d4f97c70b3ab
Ideally we want to support Fedora and CentOS as a base operating
system type. The build scripts will rewrite the Dockerfile build
scripts to pull in the correct base OS.
Change-Id: Ia41e21811caa3a1989c79cc42ce6615eec0c977b
Partially-implements: blueprint multi-baseos
When nova-api start and the nova database hasn't yet been created, it
would create it itself, preventing the migration in nova-conductor to
run and making it unable to start. This commit ensures that nova-api
container will not try to steal nova-conductor's job of creating the
nova database.
Nova-scheduler reacts differently to the missing database and simply
exits with a backtrace. This commit also prevents nova-scheduler to
start when the nova database cannot be found.
Change-Id: Ib6f7521151815faa7a26ec1d170df5a1cdb7fd63
Related-Bug: #1335804
The script wasn't reporting any errors due to a typo.
Also fix MAINTAINER field for ceilometer-collector image.
Change-Id: Idf1e2746ae395bb05ee679ca71a10a3f103ebfa8
This allows Kubernetes to reschedule containers in case a required
variable is missing, for example when the Kubernetes pod is started
before the service.
The checks were cleaned using the following method:
* remove duplicates
* remove check for variables that get a default value in the same file
* check for all variables used in the file
* check for required services when it is obvious.
Change-Id: Ib7e0530c410c61f828d36efe8925a20dc9781eab
This prevents unexpected breakage on new Fedora release.
Fedora 20 is the last release known to work. Images based on Fedora 21
are currently broken as they lack required packages such as iproute.
Support for Fedora 21 is on the way and will follow soon once all images
have been verified.
Change-Id: I849732147302eaf00d864d6b5093ff6ac006f496
Kubernetes currently creates FOO_SERVICE_HOST and FOO_SERVICE_PORT env
vars as part of starting the containers. However this is not done when
starting them with plain docker.
Defaulting variables to their common version if they're not already set
allows the usage of --link in plain 'docker run' to wire together
containers.
Co-Authored-By: Charles Crouch <ccrouch@redhat.com>
Change-Id: I91098ff987b18646d901ac63a3a644fbb68fc857
This variable is never defined anywhere, and it is not one of the
variable automatically exported by k8s or docker.
It should be KEYSTONE_PUBLIC_SERVICE_HOST instead.
Change-Id: Ib65b0189d0a767212fbb7eff4ce81717d492c3e2
Introduce a generic check_for_os_service function that exits unless it
receives a successful response from the corresponding OpenStack service.
Additionally use the local keyword to not leak local variables, and fix
check for non-existing NEUTRON_API_SERVICE_HOST variable in
check_for_neutron().
Change-Id: I67dff2b16a99bc44e928cd6a679dff8cc6a99b39
Remove redundant checks for MARIADB_SERVICE_HOST and DB_ROOT_PASSWORD
that are performed in `check_for_db`, and add missing check for
GLANCE_DB_USER.
Change-Id: Ie8194ce76274a9356dcc0b51353873d8a632c66a
