| Age | Commit message (Collapse) | Author | Files | Lines |
|
modify glance and keystone images to log to stdout/stderr, so that logs
can be recovered using "docker logs".
Change-Id: I18470c13142ceaf2f10c32e10f5e835ddaf58550
|
|
add /check.sh to keystone and glance-api images that can be used to
verify proper functionality of the container.
Change-Id: I0a878678fb8e9427d8e99af4896cbc679d3490a4
|
|
|
|
|
|
|
|
cause glance start.sh scripts to exit on any errors (allowing kubernetes
to reschedule the pod).
Change-Id: Ibebbf47758a1dfc241cb04cdb12e44af77f92b55
|
|
- 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
|
|
- 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
|
|
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
|
|
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
|
|
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
|
|
- adding db sync and db creation as utf8
- fixing user and role creation
Partial-blueprint: kube-glance-container
Change-Id: I15be99f26483e490fccc23d029f39645c13c724b
|
|
|
|
This pushes to the docker registry.
|
|
Build with kollaglue login. Then we can upload all images under
that user namespace.
|
|
Build all docker images one at a time or with one top level call
|
|
Previously images were based from RHEL OSP + RDO Icehouse. This presents
a problem in that internal urls are used to access the rhel7 repositories.
For new contributors, we need something that can be accessed without special
rhel7 permissions.
mariadb and rabbitmq can from fedora
cinder, glance, keystone can from fedora-rdo-base
This patch also uses the RDO repositories from upstream. This patch also
udpates the base fedora image with latest bits.
|
|
|