| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Kubernetes currently creates FOO_SERVICE_HOST and FOO_SERVICE_PORT env
vars as part of starting the containers. However this is not done when
starting them with plain docker.
Defaulting variables to their common version if they're not already set
allows the usage of --link in plain 'docker run' to wire together
containers.
Co-Authored-By: Charles Crouch <ccrouch@redhat.com>
Change-Id: I91098ff987b18646d901ac63a3a644fbb68fc857
|
|
PUBLIC_IP is more descriptive that MY_IP, it should be used consistently
across Kolla.
Change-Id: Iff6ae903e794ec84a40a300b36512422b7a81f71
|
|
This allows Kubernetes to reschedule the container in case a required
variable is missing, for example when the Kubernetes pod is started
before the service.
Additionally, define the KEYSTONE_ADMIN_SERVICE_HOST and
KEYSTONE_PUBLIC_SERVICE_HOST variables to their common version if not
already set to allow usage outside of Kubernetes with docker link
feature.
Change-Id: Ie0966c18076a770e4031bbf5f777dd1be0ba20bc
Closes-Bug: 1398632
|
|
Remove individual MAINTAINER information from Dockerfiles.
Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334
|
|
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 keystone start script to exit on any errors (permitting kubernetes
to reschedule the pod).
Closes-bug: 1379057
Change-Id: Ide2eac6495250c8cba91cf9b7409dcb313f6f74b
|
|
make sure that DB_ROOT_PASSWORD is in quotes to prevent errors from
shell metacharacters in the password.
Change-Id: I586ba7bb1d518d4ebfef257f92d315684843dd9b
|
|
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
|
|
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 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
|
|
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
|
|
|
|
|
|
The JSON doesn't parse correctly
Change-Id: Ie68ad1cdfb80b9f3c15e9d93476f7c53cc0a0858
|
|
This patch does a service and endpoint create so that each separate service
can find keystone. This patch also makes the sleeping a bit more logical
although there are TODOs in this area to remove the sleep operations.
Change-Id: Icfee464f9473686da89bfa8b2106172cbfd4c1a8
Closes-Bug: #1376975
|
|
- fully qualify base image (fedora-rdo-base ->
kollaglue/fedora-rdo-base)
- EXPOSE keystone service ports
Change-Id: I3b848dc1743d577ea84be868b04a41383115592b
|
|
Fix a race condition between MariaDB service start and Keystone.
Change-Id: I31384204eca9c7201eb102ec0359b390e88b96ba
|
|
Change-Id: Ic5fe761906e0ea6964c072ae510f7e62706c286b
|
|
|
|
Need PKI setup for keystone to operate.
|
|
|
|
Presently these are pulled from a closed location inside a firewall. Instead
pull them from the public docker registry.
|
|
We want all log output to go to stderr so it can be debugged later.
|
|
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.
|
|
|
|
|
|
the keystone commands will fail if the keystone principals already
exist
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|