glance keystone password cannot be generated during container boot
because we need the same value in both the -api and -registry
containers.
Change-Id: I4099ca19bd7433ff2a75ffba3a1597eff0be2ce4
Cause keystone start script to exit on any errors (permitting kubernetes
to reschedule the pod).
Closes-bug: 1379057
Change-Id: Ide2eac6495250c8cba91cf9b7409dcb313f6f74b
This adds a /opt/kolla/kolla-common.sh to the base image as a place to
put commonly used functions. The goal is to avoid code duplication
across all the images created from this base image.
Change-Id: Ib670fe369bb8048aa69979b74a984fa4ddaae7d9
make sure that DB_ROOT_PASSWORD is in quotes to prevent errors from
shell metacharacters in the password.
Change-Id: I586ba7bb1d518d4ebfef257f92d315684843dd9b
our Dockerfile was missing "yum clean all", causing a large yum cache to
get baked into the image.
Change-Id: Ib9942a12b8a14c7e04cf8ae3184cdefcdc5a4652
- update keystone endpoints/user on boot (to avoid problems caused by,
e.g., a stale password or invalid endpoint urls)
- require GLANCE_DB_PASSWORD and GLANCE_KEYSTONE_PASSWORD in the
environment, since we start multiple containers
Change-Id: I31214b81280ed34409f92e79003c1116d5737d2e
Previously, the glance-api start script would use the container
IP instead of the proxy IP for the public url when creating the
keystone endpoint. This causes keystone to provide an unreachable
IP within the public url and other OS services are unable to
connect to the public url.
Change-Id: I44befc84a90f59d535a951ee81aaff0fa1ba952d
Previously the glance-base script did not configure the registry
host IP. This causes API to try connecting to registry on
localhost. Since registry is bound to MY_IP, api is unable to
connect to registry. This change adds support for the glance-base
script to configure the registry_host parameter in api.conf to
MY_IP.
Change-Id: I1c711ff8aa95abec5ca306f03bd7e0a3883ca578
- run "yum update" after installing RDO repository (to ensure we get any
package updates from this repository)
- "yum clean" after the "yum update" to prevent yum cache from being
baked into the image
Change-Id: Id897fd85214855bb08f7e16da4bbdf07b821d991
when booting the keystone container with an existing database, make sure
to update credentials for admin user and replace existing keystone
endpoint in the service catalog.
Change-Id: I2c66d75210ef7ba5a96077eea15a8c564e99f662
The image location for rabbitmq was incorrectly pointing at Lars
private repository. Change it to point to the global kollaglue repo.
Change-Id: Ib4fd84db9410fa7057730ff74be2acc0babfa438
Also, fixed up environment variable to use RABBITMQ_NODE_PORT, which is
what RabbitMQ expects (http://www.rabbitmq.com/configure.html).
Implements: blueprint kube-rabbitmq-container
Change-Id: Iacc2ea5d3c4a002e6920ed17cb21733a0cbd8d21
This should get us a working nova-compute. Once rabbitmq is operational
we can further debug and implement this container.
Change-Id: I0768b9f33bc43748f4e08da0edc111d669895cc8
