linux/meta-cloud-services.git/meta-openstack-controller-deploy, branch icehouse

OpenStack: all-in-one node

2014-04-15T23:49:52+00:00

Introduce image openstack-image-aio, integrating both compute and controller functionality Signed-off-by: Amy Fong

OpenStack: Fix postgresql file permissions

2014-03-15T04:42:00+00:00

- make database directory to be configurable, defaulting to /var/lib/postgres/data - modify init scripts to create database's data directory if it doesn't exist Signed-off-by: Amy Fong Signed-off-by: Bruce Ashfield

meta-openstack-deploy: rename quantum bbappends to neutron

2013-11-25T20:25:35+00:00

Signed-off-by: Bruce Ashfield

meta-openstack-*-deploy: add bbclass patterns

2013-10-04T17:16:33+00:00

Signed-off-by: Bruce Ashfield

quantum: update configuration and deployment options

2013-10-03T05:16:44+00:00

Replace the controller and compute specific deployment classes with the central "hosts" class, and change the configuration file update routines to use the new values and externally visible IPs. Signed-off-by: Bruce Ashfield

cirros: stash and squash

2013-10-03T05:16:44+00:00

Signed-off-by: Bruce Ashfield

openstack-controller-deploy: cirros simple guest support

2013-10-03T05:15:42+00:00

It is often desireable to test a OpenStack controller and compute node pair with a small, well known image. The cirros simple cloud image fits this bill. To enable the inclusion of this image, add: IMAGE_INSTALL_append = " cirros-guest-image" to local.conf (or relevant configuration file). Once the build completes, the cirros image can be found in /root/images/ Signed-off-by: Bruce Ashfield

openstack: create simple deployment framework

2013-10-03T05:15:42+00:00

To facilitate the creation of a simple OpenStack configuration with a single control and compute node, several things should be known at build time (since in this simple configuration, we are not using dhcp, or other name resolution techniques): - The IP of control node - The IP of the compute node - The IP of the node being built From these values, the OpenStack components and support applications (databases, access control, etc) are configured, as well as simple name resolution generated at build time. A single "hosts" bbclass should be provided with the following values: COMPUTE_IP ?= "192.168.7.4" COMPUTE_HOST ?= "compute" CONTROLLER_IP ?= "192.168.7.2" CONTROLLER_HOST ?= "controller" MY_IP ?= "${CONTROLLER_IP}" MY_HOST ?= "${CONTROLLER_HOST}" The above example is for a control node, using the runqemu default addresses. The openstack-base.bbclass is responsible for generating /etc/hosts and /etc/hostname. Any image type that requires these values at boot tiem, should inherit this class to allow its rootfs post population hooks to run and generate the required configuration. Signed-off-by: Bruce Ashfield

meta-openstack-controller-deploy: initial creation

2013-10-03T05:15:42+00:00

Creating a layer than when added to a build, modifies configuration via appends and classes to create a configured control node. Signed-off-by: Bruce Ashfield