| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Loosely followed this document for setting up Heat:
http://docs.openstack.org/icehouse/install-guide/install/yum/content/heat-install.html
Some gotchas:
- crux doesn't require escaping parenthesis for endpoint creation like
keystone client
- heat icehouse packages are configured for qpid, so kombu had to be
specified specifically
This firewall reference was handy for port information:
http://docs.openstack.org/trunk/config-reference/content/firewalls-default-ports.html
Implements: blueprint kube-heat-container
Change-Id: Ie4291a6c4c2b85a23a71fc0a003d9160bf0a32b8
|
|
Previously, the k8s neutron pod was pulling the image from
danehans instead of kollaglue. Additionally, the formatting was
incorrect causing kube not to pull the image at all.
Change-Id: I6f787a432ffb9cae404f915ac5228ddcb88e877c
|
|
|
|
This was replaced by glance-pod.yaml.
Change-Id: I9249ae2721e375096fc42e1e8462a024c314118e
|
|
Not sure if mucking with iptables is safe, but appears required.
Change-Id: I766b0e61e247c47b4449c1ed2c204ddb8919a87d
|
|
Previously Kolla did not support Neutron. This patch provides
initial Neutron support by implementing neutron-server
functionality. It also creates a neutron-base image that
provides common config and packages for all Neutron-based
services.
Partially Implements: Blueprint Kubernetes Neutron Container
Change-Id: I2399a1331992fae0f387f01e5b5c1c1d34f0637d
|
|
remove nova-controller image, which is not meant to be started directly.
add required NEUTRON_SHARED_SECRET environment variable.
Change-Id: Id671c5473db8e6e222b16ccdfd9eaedc872c60fa
|
|
The previous values were just stand in values. The new
ports support nova-api, ec2 api, and metadata api.
Change-Id: I330575d9b53b69bcacc61061b271252e61e64d4b
|
|
Use kubernetes volumes for data storage rather than placing data
directly on the container filesystem. That provides a starting point
for thinking about persistent data -- one could replace the emptyDir
source with an explicit path via hostDir, and then you would have
storage that would persist over a container delete/re-create.
Change-Id: Ifade1cb2ba546e5e0207c3d8c84965dc2195716b
|
|
if we want to be able to run multiple keystone container instances, the
password cannot be generated as part of the container boot process; it
must be passed it as part of the pod template.
Change-Id: Idd1b50b6bdb3788eec316bf22fb954f5ecbaa4be
|
|
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
|
|
Change-Id: I7edbd3a59007d9e2f7f5ab5e4c020eeb58d03dd3
|
|
- 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
|
|
The image location for rabbitmq was incorrectly pointing at Lars
private repository. Change it to point to the global kollaglue repo.
Change-Id: Ib4fd84db9410fa7057730ff74be2acc0babfa438
|
|
All services go to TLD/k8s/service
All pods go to TLD/k8s/pod
Change-Id: Iad2977a9f0cd5f430c4e0a566846bf4681618379
|