Remove whitespace errors in mariadb JSON

JSON should not introduce whitespace errors

Change-Id: I02cc56c6205a411a3f042b65ccfb9624795c13d2
Updating the README to show starting services
before pods

Change-Id: I30681d64a186e597cdd6691b4c807fea7b6c531c
Merge "Updating the README to show starting services before pods"
fix issues with build-docker-image

- fix typo in --namespace option

    build-docker-image had a missing '$' in the code that handled the
    --namespace option.

- force builds to kollaglue namespace with 'latest' tag to use
  the --release flag

- build IMAGE after config and options processing to permit overriding
  PREFIX in .buildconf

Change-Id: Icf70b33080ef19643f133f2b6f60087c524bd4fb
add openssl to base image

we use openssl in many of our start scripts for password generation, so
openssl should probably be part of the base image.

Change-Id: I893adfa3b7d17249b6814fc161e6f3f1696d8cd6
Merge "Remove whitespace errors in mariadb JSON"
Merge "fix issues with build-docker-image"
renamed keystone services

This renames the keystone services so that they are named by function,
rather than port number (which would be confusing if they were running
on a different port).

Change-Id: Ibb0263a133c28a104563df431870a9effe584012
remove "master" from mariadb k8s configs

Labelling things foo-master crept into this repository from the
kubernetes guestbook example (which has redis-master and redis-slaves).
We're not running clustered software at the moment so these labels are
unnecessary.

Change-Id: Ibf4cb2b005cc57bcb11e298dd5109cfe309c9ec3
use "crux" for creating users/endpoints

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
added hautoproxy auto-configuring haproxy

Change-Id: Ic923c6a772f1bdf36b97b05a1d04de9e5b841ddd
hautoproxy testing with keystone

Change-Id: I908c53b62fff91b3ec7312175be14c709a1d6fd0
hautoproxy changes for glance

Change-Id: I757a7f1fef6843aa8d07f83d1c29caf3ec86db84
wait for required services before trying to use them

Change-Id: Ic54e945ee6fe469eb5de127b4d8bab9696896511
glance was using wrong var name for admin_password

also missing "\" in several places, breaking multi-line crudini
commands.

Change-Id: I81ce37eb983dc946a71867656818e907ecfae203
glance was using wrong tenant name

Change-Id: I280d1db3ed576988f2bf29ea665e1922a37f8752
both config files should be populated

in the registry container, glance-manage appears to reference
glance-api.conf

Change-Id: I8c08d0b267568bdbfb1398d1c8a21d984ce98b38
replace endpoints on start

Change-Id: If83b589717a8327ba2191ba0584d36bf9e88dc75