openstack/kolla.git/docker/keystone/Dockerfile, branch master

Restructure builds to allow more flexibility

2015-05-15T06:32:22+00:00

As a restructure, nothing is changed from the original behaviour and naming despite the file structure changing. The symlinks to build had to be updated generating lots of "deleted" and "new_file". The new structure is: docker/${base_distro}/${type}/${container} base_distro == centos, ubuntu, fedora, etc type == source, binary, rdo type rdo is a symlink to binary for backwards compatibility Two new flags are added to the build-all script to support the ability to support different base distros and a flag to support binary or source containers. There are several added folders that are empty to hold the directory structure for future containers of these types. To use a prefix other than centos-rdo- you can set PREFIX in the toplevel directory .buildconf file Change-Id: Ifc7bac0d827470f506c8b5c004a833da9ce13b90

Port to icehouse

2015-05-06T16:58:43+00:00

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

Replace ; with && in Dockerfile

2015-03-27T23:52:48+00:00

When using ';' this can allow the previous command to fail and while the docker build proceeds without realizing a command failed. Switching to '&&' allows the exit code to make it to the docker build command and the build to fail appropriately. Change-Id: Idd0991ed4549542bb10d27da1a0a025d0503b6c1

Fixes Keystone openrc and sets / for scripts

2015-03-20T07:18:21+00:00

Previously, the keydtone openrc file was not using the proper auth url, whcih was broken with too many double ticks. Also changed the auth port from public to admin since keystone user is an admin tenant. Changed DIR for scripts to align with the rest of the project. Change-Id: Iadde3239227e65ecca479b16a7b7db51d3a579c8

Implements: blueprint container-set-api-control

2015-03-13T17:10:16+00:00

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

Allow changing base image

2015-03-02T05:08:06+00:00

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 Change-Id: I3964cd2292789ea883a1f2d2738a5731a4fff49b

Make keystone work with CentOS 7 image

2015-02-24T09:28:30+00:00

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

Update MAINTAINER in Dockerfiles to Kolla Project

2014-10-22T15:11:31+00:00

Remove individual MAINTAINER information from Dockerfiles. Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334

added simple health check scripts

2014-10-13T20:43:13+00:00

add /check.sh to keystone and glance-api images that can be used to verify proper functionality of the container. Change-Id: I0a878678fb8e9427d8e99af4896cbc679d3490a4

use "crux" for creating users/endpoints

2014-10-06T17:26:34+00:00

this patch introduces the "crux" [1] tool for creating keystone users, services, and endpoints in an idempotent fashion. E.g., to create a user that doesn't exist: $ crux user-create -n lars -t lars -p secret creating new tenant created tenant lars (d74cec5023c4428da533066bb11943db) creating new user lars created user lars (adf2c2d92e894a3d90a403c5885f192e) And performing the same operation a second time: $ crux user-create -n lars -t lars -p secret using existing tenant lars (d74cec5023c4428da533066bb11943db) using existing user lars (adf2c2d92e894a3d90a403c5885f192e) The behavior is similar for creating keystone endpoints. [1]: https://github.com/larsks/crux Change-Id: I694e0c1bdcdde595e1af2ee8ef5d0f239a9ad4cd