summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2014-10-16introduce scheduler to common configurationLars Kellogg-Stedman1-36/+2
Change-Id: I56156ed59b6678180bcb5d1bdd00233d8f339643
2014-10-16introduce conductor to common configurationLars Kellogg-Stedman1-28/+5
- source in common configuration script - actually sync the database Change-Id: I61d50edb0b44a71800e172c4777d3b40026e8521
2014-10-16Nova has an undeclared dependency on python-cinderclientLars Kellogg-Stedman1-0/+1
Nova imports python-cinderclinet, which is not present by just installing python-nova-api. Hard yum-install it until upstream fixes packaging. Change-Id: I3187721d3eda7ce81da9540469fcc93b93560d3b
2014-10-16have start.sh source in common configuration scriptLars Kellogg-Stedman1-23/+15
Change-Id: I90fcd6ed43ce6c2b224eb43492586c8f4231ceda
2014-10-16fix nova-controller podLars Kellogg-Stedman1-13/+6
remove nova-controller image, which is not meant to be started directly. add required NEUTRON_SHARED_SECRET environment variable. Change-Id: Id671c5473db8e6e222b16ccdfd9eaedc872c60fa
2014-10-16changes to base nova configurationLars Kellogg-Stedman3-38/+89
- correct typos/syntax errors in configuration scripts - make config script consistent with other images - do not create keystone entries in base image script Change-Id: I42986fe1b9c80c5b0735fd70294bce1a6223a3ca
2014-10-15Merge "Add nova-libvirt to started services"Jenkins1-1/+2
2014-10-15Merge "Add replication controllers to start and stop scripts"Jenkins4-0/+21
2014-10-15Add nova-libvirt to started servicesSteven Dake1-1/+2
nova-libvirt was not in the list of started services, so its port was not available prior to this change. Change-Id: I59cedb68ff87a9a54e93c85e60f748e5cc161a4c
2014-10-15Add replication controllers to start and stop scriptsSteven Dake4-0/+21
replicaton controllers are now automatically started by the start scripts and killed by the stop script Change-Id: I15d15ff9b1b640bd0f8cace872a827ecfe476ca3
2014-10-14modify tox config to use new validation codeLars Kellogg-Stedman2-2/+3
this patch modifies tox.ini to perform both the JSON and YAML validation checks. Change-Id: Ie8db699f19dc7698407bab1e3d51dcb6184cfad2
2014-10-14Merge "Expose ports needed by the nova-controller"Jenkins1-0/+2
2014-10-14Merge "Have qemu uri point to correct place"Jenkins1-2/+3
2014-10-14Merge "nova-compute-service doesn't expose a port"Jenkins1-5/+0
2014-10-14Merge "add better validation checks (part 1)"Jenkins6-33/+131
2014-10-14Merge "Start nova-controller services and pods"Jenkins2-0/+4
2014-10-14Merge "Nova-controller needs a start script"Jenkins1-0/+36
2014-10-14add better validation checks (part 1)Lars Kellogg-Stedman6-33/+131
This patch adds a script for validating YAML files, and replaces the existing JSON checks with one largely identical to the YAML check. This also provides a script that can be installed as a pre-commit hook that will perform this checks when you commit changes. You can install the hook by running tools/pre-commit-hook --install. Change-Id: Ib4742a9db062362cfa61d669c691151bc1ca376c
2014-10-14Merge "Config will be done by the controller"Jenkins1-2/+0
2014-10-14Convert nova-compute-replication to yamlSteven Dake2-66/+37
Yaml is the future - json is the past \o/ Change-Id: I36a9cbf8db034d1e8deba040a22e556d791c65ed
2014-10-14Expose ports needed by the nova-controllerRyan Hallisey1-0/+2
The nova-controller will be using ports 8773, 8774, and 8775. Therefore, Docker needs to be made aware of this. Change-Id: Ia53dd50bdce4b328c246bad5399ab7ff44750d58
2014-10-14nova-compute-service doesn't expose a portSteven Dake1-5/+0
AFAIK the service files are only for services with ports exposed. Since nova-compute doesn't expose a port, kubecfg returns an error when attempting to register it: F1014 17:06:34.329482 32317 kubecfg.go:395] Got request error: service "novacompute" is invalid: port: invalid value '0' Change-Id: I4d9f8d50d538f42d520f3d9437ab32aa6a226d2b
2014-10-14Start nova-controller services and podsSteven Dake2-0/+4
Start all of the nova-controller services and pods with the start-all-pods and start-all-services startup scripts Change-Id: I47fe15d67ef177fbecf342357bff44cf2fdb5d9e
2014-10-14Have qemu uri point to correct placeSteven Dake1-2/+3
Prevoiusly the connection uri was using an undefined variable. Now it will use NOVA_LIBVIRT_SERVICE. Change-Id: Ia5ceb3428fa7aeb8dd1dd7b500c63119856977f2
2014-10-14do not perform database or keystone setup in nova-computeLars Kellogg-Stedman1-41/+37
- do not perform database or keystone initialization in nova-compute image (these should happen in the controller images). - fix incorrect nova.conf path - configure keystone_authtoken correct NB: This still won't result in a working image, because it does not configure the RPC settings yet. That will be for a subsequent patch. Change-Id: Icbd66104ef817d360c46003b29fff63f66ace8d2
2014-10-14Merge "Add kube services"Jenkins3-0/+21
2014-10-14Add kube servicesRyan Hallisey3-0/+21
Add kubernetes services so that the nova controller can use the ports 8773, 8774, and 8775, which correspond with nova-api, nova-ec2-api, and metadata-api. Change-Id: Idb083e2e0745c6587f9fa4f01a068727a435c2c6
2014-10-14Update nova-controller's container portsRyan Hallisey1-7/+3
The previous values were just stand in values. The new ports support nova-api, ec2 api, and metadata api. Change-Id: I330575d9b53b69bcacc61061b271252e61e64d4b
2014-10-14Nova-controller needs a start scriptRyan Hallisey1-0/+36
The nova-controller is going to make all the configurations so it needs a script to setup nova.conf. The config data is stored locally in nova.conf and will be read in and executed by line. Change-Id: Id501212671201ca68cd08018ce024db284dd8c54
2014-10-14Config will be done by the controllerRyan Hallisey1-2/+0
Remove config setup in nova-conductor. Change-Id: I0740e6a69601ab4a39c20a3287792013355a9262
2014-10-14Merge "Nova-api should not set up the database"Jenkins1-9/+0
2014-10-14Merge "batch operations in nova-compute dockerfile"Jenkins1-14/+15
2014-10-14Merge "Nova-controller config setup"Jenkins2-0/+75
2014-10-13Minor fixes for the nova-controller DockerfileRyan Hallisey1-4/+5
Instead of multiple install commands, add multiple packages into a single install. Change-Id: Id27cb53da76df50bf2500eb2d6de18c7401e5c6c
2014-10-13Nova-api should not set up the databaseRyan Hallisey1-9/+0
Instead, nova-conductor will setup the database. Change-Id: I91a46aa9bc3fc99fe58053b239929c8121864283
2014-10-13Nova-controller config setupRyan Hallisey2-0/+75
Configurations will exist in nova.conf. They will be read in and set by the start script. The mysql configuration will be made by nova-conductor. Change-Id: I1709ff6620b19ef5dbcf5efe8b72c329acf96123
2014-10-13batch operations in nova-compute dockerfileLars Kellogg-Stedman1-14/+15
- batch yum operations to the build goes faster - yum clean after install to remove yum cache and make final image smaller Change-Id: I62246a6329a6b2ab6ab4fee6f72652a805f1e72e
2014-10-13fix nova-base dockerfileLars Kellogg-Stedman1-5/+3
- use correct namespace for base image - mariadb and openstack-utils are installed by fedora-rdo-base Change-Id: I9c8bccab10f8b9dc66340fb94d45c90d1a39fea9
2014-10-13log to stdout/stderrLars Kellogg-Stedman2-4/+6
modify glance and keystone images to log to stdout/stderr, so that logs can be recovered using "docker logs". Change-Id: I18470c13142ceaf2f10c32e10f5e835ddaf58550
2014-10-13add kubernetes volumes to glance podLars Kellogg-Stedman2-26/+43
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
2014-10-13arrange for image storage on a volumeLars Kellogg-Stedman1-0/+2
Change-Id: I0dcbe6fd4c1d3ac9b79fc205df2013f62ff5a546
2014-10-13added simple health check scriptsLars Kellogg-Stedman6-6/+46
add /check.sh to keystone and glance-api images that can be used to verify proper functionality of the container. Change-Id: I0a878678fb8e9427d8e99af4896cbc679d3490a4
2014-10-13keystone pod needs KEYSTONE_DB_PASSWORDLars Kellogg-Stedman1-0/+2
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
2014-10-13glance images need keystone passwordLars Kellogg-Stedman1-0/+4
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
2014-10-13Merge "glance: cleanup; use kolla-common; exit on errors"Jenkins4-61/+33
2014-10-13Merge "keystone: exit on errors; cleanup"Jenkins1-29/+18
2014-10-13Merge "rabbitmq: exit on errors"Jenkins1-0/+2
2014-10-13Merge "add kolla-common shell library to base image"Jenkins2-1/+78
2014-10-13Merge "properly quote password in keystone start script"Jenkins1-1/+1
2014-10-13Merge "include mariadb and crux in base image"Jenkins1-0/+2
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-08 23:10:21 +0000