openstack/kolla.git/docker/keystone/start.sh, branch kilo-eol

Change the default shell to bash

2015-04-27T05:26:37+00:00

Unify the shell to bash in all Kolla scripts. Change-Id: Ib9591b2f8f344eb88455c5e9b7ecf2164fb5960a Implements: blueprint use-bash-shell

Allow check_for_* functions to be consumed by wait_for

2015-04-01T07:39:44+00:00

In order for the `check_for_*` functions to be consumed by `wait_for`, they should notify of their success but not exit. As a consequence, the previous behavior is restored by the fail_unless_* companion functions. With this change, it is now possible to do: wait_for 30 1 check_for_os_service_running keystone Change-Id: I16ddf8913027030c3ccb5487713d172904508fd6

Merge "Don't kill keystone, but instead wait for it to finish at the end"

2015-03-21T03:19:48+00:00

Don't kill keystone, but instead wait for it to finish at the end

2015-03-20T17:48:32+00:00

use the bash wait builtin to wait for the keystone process to exit. Change-Id: I03057e7925e7e41120c163c0be22ade75050d9f1

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

Add a "admin" user via crux to keystone container

2015-03-18T19:48:05+00:00

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

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

Cleanup required variables checks for all containers

2015-01-19T07:29:59+00:00

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

Merge "Prefer the use PUBLIC_IP over MY_IP"

2014-12-26T07:01:12+00:00

Enable usage of containers outside of Kubernetes

2014-12-17T04:50:03+00:00

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