chmod +x start.sh for nova-compute/nova-compute

start.sh must be executable

Change-Id: I552b151069d4baee66b058671486846f2dc08c13
chmod +x nova-compute/nova-libvirt/start.sh

start.sh must be executable

Change-Id: I2de86343d194af5c3783d2169192f158fdada178
Modify start.sh for nova-compute/nova-compute

This should get us a working nova-compute.  Once rabbitmq is operational
we can further debug and implement this container.

Change-Id: I0768b9f33bc43748f4e08da0edc111d669895cc8
Change sdake/image to kollaglue/image

Had my personal repo checked in.  Assuming we want kollaglue for repo-based
files :)

Change-Id: I5ccdba8c3d3301c8140c5143aea3db5ebfa6db76
Updated base image in Dockerfile and changed CMD to reference correct file

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
Merge "Updated base image in Dockerfile and changed CMD to reference correct file"
Reorganize k8s structure

All services go to TLD/k8s/service
All pods go to TLD/k8s/pod

Change-Id: Iad2977a9f0cd5f430c4e0a566846bf4681618379
fix issues with glance scripts

- glance was using wrong var name for admin_password
- also missing "\" in several places, breaking multi-line crudini
  commands.
- glance was using wrong tenant name
- in the registry container, glance-manage appears to reference
  glance-api.conf
- the glance.json config file was not spawning a registry container
wait for required services before trying to use them

Change-Id: Ic54e945ee6fe469eb5de127b4d8bab9696896511
hautoproxy changes for keystone

Change-Id: I908c53b62fff91b3ec7312175be14c709a1d6fd0
hautoproxy changes for glance

Change-Id: Icd8db3969a4c2be10c31fbd02524691f996d8614
use my namespace for images

Change-Id: I3d88f5fabedf5fdabe84c33d37d7106c527b0bb6
added keystone replicationcontroller

Change-Id: I2c6f3921e66589fdc3a51e4fb57b005c10a2ae89