| Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
All services go to TLD/k8s/service
All pods go to TLD/k8s/pod
Change-Id: Iad2977a9f0cd5f430c4e0a566846bf4681618379
|
|
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
|
|
Had my personal repo checked in. Assuming we want kollaglue for repo-based
files :)
Change-Id: I5ccdba8c3d3301c8140c5143aea3db5ebfa6db76
|
|
This should get us a working nova-compute. Once rabbitmq is operational
we can further debug and implement this container.
Change-Id: I0768b9f33bc43748f4e08da0edc111d669895cc8
|
|
start.sh must be executable
Change-Id: I2de86343d194af5c3783d2169192f158fdada178
|
|
start.sh must be executable
Change-Id: I552b151069d4baee66b058671486846f2dc08c13
|
|
|
|
|
|
|
|
|
|
|
|
Get a working Dockerfile
Sort out start.sh to run libvirt in a container
Change-Id: Iaafe807b1631ad59fea200a02e46a8cabd6791ca
|
|
Several things were done incorrectly in previous pod. Fix that.
Change-Id: I7387964979b4ceef4dfda2349023aa0267320349
|
|
Add service files for libvirtd and nova-compute
Change-Id: I94c5cad75605104f57859e23341ba106a3250fc8
|
|
- 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
Change-Id: I280d1db3ed576988f2bf29ea665e1922a37f8752
|
|
because we don't need fedora-rdo-fedora-rdo-base.
Change-Id: I75ac2aa6904ad27b500c7fb1e48897939530cb09
|
|
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
|
|
Partial-blueprint: kube-nova-container
Change-Id: Ib48e6318ae458bf03510725a220332d1920cbeae
|
|
This patch updates all the json files that reference the mariadb service
variables to ues the new names.
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: I229d04c89aa13cb6cc2e1c33a0a7b21e1c6e9caa
|
|
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
|
|
Let's get that quickly so we can add a gate. There was some respacing
along the way (used http://jsonlint.com)
Change-Id: Id18b9f9757306cf3f06e6221a21a9f600db1bd2e
|
|
|
|
|
|
|
|
This image configures haproxy to forward connections for all available
kubernetes services. It is meant to be run alongside other contains in
a kubernetes pod to provide access to "remote" services at a consistent
address so that keystone api endpoints can be configured in a sane
fashion.
Change-Id: Ic923c6a772f1bdf36b97b05a1d04de9e5b841ddd
|
|
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
|
|
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
|
|
This patch replaces the collection of individual "build" scripts with a
single script (tools/build-docker-image), made available as "build"
inside each image directory.
The build-docker-image script will, by default, build images tagged with
the current commit id in order to prevent developers from accidentally
stepping on each other or on release images.
Documentation in docs/image-building.md describes the script in more
detail.
Change-Id: I444d5c2256a85223f8750a0904cb4b07f18ab67f
|
|
db sync and db creation as utf8 - fixing user and role creation"
|
|
- adding db sync and db creation as utf8
- fixing user and role creation
Partial-blueprint: kube-glance-container
Change-Id: I15be99f26483e490fccc23d029f39645c13c724b
|
|
|
|
Not everyone have access to kube/ docker namespace, so let just push it
only when specified with -p
Change-Id: I49b2b04f8db8ff7ba7c9f6b6dc9b2ec8c30a95c8
|
|
JSON should not introduce whitespace errors
Change-Id: I02cc56c6205a411a3f042b65ccfb9624795c13d2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: Ic7eaf187e7f0fa9481c432a8b32971a470e75bf0
|
|
Change-Id: Ia642716f30ea4bd098e5c67e522bbfd01fd6cf7a
|
|
Change-Id: I91bb3cab059220a6677e28e928b5805410ce5f5c
|
|
Change-Id: Ie5d7f5342284997e878803b273f0796421ae6bb2
|
|
The JSON doesn't parse correctly
Change-Id: Ie68ad1cdfb80b9f3c15e9d93476f7c53cc0a0858
|
|
|
|
|