summaryrefslogtreecommitdiff
path: root/docker
AgeCommit message (Collapse)AuthorFilesLines
2014-10-07Validate JSONChmouel Boudjnah5-220/+242
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
2014-10-07Merge "added hautoproxy auto-configuring haproxy"Jenkins4-0/+100
2014-10-07Merge "use "crux" for creating users/endpoints"Jenkins2-41/+37
2014-10-06Merge "Remove whitespace errors in mariadb JSON"Jenkins1-1/+0
2014-10-06added hautoproxy auto-configuring haproxyLars Kellogg-Stedman4-0/+100
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
2014-10-06use "crux" for creating users/endpointsLars Kellogg-Stedman2-41/+37
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
2014-10-05add openssl to base imageLars Kellogg-Stedman1-0/+1
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
2014-10-04introduce a new build mechanismLars Kellogg-Stedman44-136/+20
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
2014-10-03Merge "Updates to glance start scripts, db and user/role creation - adding ↵Jenkins2-26/+26
db sync and db creation as utf8 - fixing user and role creation"
2014-10-03Updates to glance start scripts, db and user/role creationDan Radez2-26/+26
- adding db sync and db creation as utf8 - fixing user and role creation Partial-blueprint: kube-glance-container Change-Id: I15be99f26483e490fccc23d029f39645c13c724b
2014-10-03Merge "Only push with the build script with -p"Jenkins1-2/+22
2014-10-03Only push with the build script with -pChmouel Boudjnah1-2/+22
Not everyone have access to kube/ docker namespace, so let just push it only when specified with -p Change-Id: I49b2b04f8db8ff7ba7c9f6b6dc9b2ec8c30a95c8
2014-10-03Remove whitespace errors in mariadb JSONSteven Dake1-1/+0
JSON should not introduce whitespace errors Change-Id: I02cc56c6205a411a3f042b65ccfb9624795c13d2
2014-10-03Merge "Keystone: Do a service and endpoint create"Jenkins1-6/+25
2014-10-03Merge "Swift: Remove trailing JSON commas that don't parse"Jenkins1-6/+6
2014-10-03Merge "Heat: Remove JSON trailing commas that don't parse"Jenkins1-4/+4
2014-10-03Merge "rabbitmq: remove trailing commas in tabs so JSON parses"Jenkins1-1/+1
2014-10-03Merge "glance: remove JSON trailing commas that don't parse"Jenkins1-3/+3
2014-10-03Merge "Keystone: remove extra commas and tabs in JSON"Jenkins1-8/+6
2014-10-03Merge "Initial libvirt and nova-compute structure"Jenkins15-1/+152
2014-10-03Merge "fix mariadb Dockerfile"Jenkins1-2/+4
2014-10-03Swift: Remove trailing JSON commas that don't parseSteven Dake1-6/+6
Change-Id: Ic7eaf187e7f0fa9481c432a8b32971a470e75bf0
2014-10-03Heat: Remove JSON trailing commas that don't parseSteven Dake1-4/+4
Change-Id: Ia642716f30ea4bd098e5c67e522bbfd01fd6cf7a
2014-10-03rabbitmq: remove trailing commas in tabs so JSON parsesSteven Dake1-1/+1
Change-Id: I91bb3cab059220a6677e28e928b5805410ce5f5c
2014-10-03glance: remove JSON trailing commas that don't parseSteven Dake1-3/+3
Change-Id: Ie5d7f5342284997e878803b273f0796421ae6bb2
2014-10-03Keystone: remove extra commas and tabs in JSONSteven Dake1-8/+6
The JSON doesn't parse correctly Change-Id: Ie68ad1cdfb80b9f3c15e9d93476f7c53cc0a0858
2014-10-03Merge "Using new fedora base image from kollaglue"Jenkins2-5/+21
2014-10-03Merge "fix keystone dockerfile"Jenkins1-2/+4
2014-10-03Using new fedora base image from kollaglueLars Kellogg-Stedman2-5/+21
Change-Id: I388113e5a9c748054a099ef1a3063863120e9a99
2014-10-03Keystone: Do a service and endpoint createSteven Dake1-6/+25
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
2014-10-02Initial libvirt and nova-compute structureSteven Dake15-1/+152
This lays the groundwork for the docker compute container. The compute node is composed of libvirt container and a nove-compute container. We are going to have to sort out how to get k8s to schedule this pod 1 per node. Change-Id: I1e06e4b5f5bde83b582edfc1094084a4ee353371 Partial-blueprint: kube-libvirt-container Partial-blueprint: kube-nova-container
2014-10-02mariadb: Set container port in pod to 3306Steven Dake1-1/+4
container port for pod should be set Change-Id: I04144487f8803b1f83d59bdc978c4f6dfa431d0d
2014-10-02fix mariadb DockerfileLars Kellogg-Stedman1-2/+4
- fix base image - expose ports - new mariadb packages log to /var/log/mariadb Change-Id: I60adc956c82c352f91f718a3a2d5a4a86dd00293
2014-10-02fix keystone dockerfileLars Kellogg-Stedman1-2/+4
- fully qualify base image (fedora-rdo-base -> kollaglue/fedora-rdo-base) - EXPOSE keystone service ports Change-Id: I3b848dc1743d577ea84be868b04a41383115592b
2014-10-02Restart container until mariadb is availableSteven Dake1-0/+5
Fix a race condition between MariaDB service start and Keystone. Change-Id: I31384204eca9c7201eb102ec0359b390e88b96ba
2014-10-02Change "redhat" to "kolla" in the keystone authenticationSteven Dake1-1/+1
Change-Id: Ic5fe761906e0ea6964c072ae510f7e62706c286b
2014-09-30updating build and start scripts for glanceDan Radez11-21/+50
2014-09-27Use pki_setup to set up keystone properlySteven Dake1-1/+3
2014-09-27Setup pki_setup on initial setup of keystoneSteven Dake2-2/+3
Need PKI setup for keystone to operate.
2014-09-27Point to fedora-rdo-* for image namesSteven Dake2-2/+2
2014-09-27Pull mariadb and keystone images from the kollaglue organizationSteven Dake2-2/+2
Presently these are pulled from a closed location inside a firewall. Instead pull them from the public docker registry.
2014-09-27Make keystone use stderrSteven Dake1-0/+2
We want all log output to go to stderr so it can be debugged later.
2014-09-25Adds the push step for each repo to the master buildSteven Dake1-1/+3
Push for each built image
2014-09-25Add a push script for each of the separate daemonsSteven Dake16-0/+32
This pushes to the docker registry.
2014-09-25Make build tools build with kollaglue loginSteven Dake16-16/+16
Build with kollaglue login. Then we can upload all images under that user namespace.
2014-09-22Merge branch 'master' of https://github.com/jlabocki/superhappyfunshowrthallisey1-1/+1
2014-09-22Merge branch 'master' of https://github.com/jlabocki/superhappyfunshowrthallisey1-0/+0
2014-09-22Merge branch 'master' of https://github.com/jlabocki/superhappyfunshowrthallisey1-0/+0
2014-09-22Configure cinder to use keystonerthallisey2-30/+35
2014-09-22Exec rabbitmq using entrypoint; Expose RabbitMQ portBrent Holden1-0/+0
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-06 00:06:11 +0000