linux/meta-cloud-services.git/meta-openstack-compute-deploy, branch thud

layer.conf: Add thud to LAYERSERIES_COMPAT

2018-10-10T03:22:57+00:00

Since `9ec5a8a layer.conf: Drop sumo from LAYERSERIES_CORENAMES' and `9867924 layer.conf: Add thud to LAYERSERIES_CORENAMES' applied in oe-core, add thud to LAYERSERIES_COMPAT Signed-off-by: Hongxu Jia Signed-off-by: Bruce Ashfield

*/layer.conf: Update LAYERDEPENDS

2018-10-10T03:22:57+00:00

The ruby layer is no longer in meta-openembedded, remove references to that from the README. Implement the LAYERDEPENDS for each of the layers so that the layerindex will populate properly. Signed-off-by: Mark Hatle Signed-off-by: Bruce Ashfield

Add LAYERSERIES_COMPAT

2018-05-22T02:10:00+00:00

Signed-off-by: Jeremy Puhlman Signed-off-by: Bruce Ashfield

conf/layer.conf: remove bbclass from BBFILES

2018-01-18T15:47:29+00:00

Add bbclass to BBFILES doesn't make any sense. Signed-off-by: Robert Yang Signed-off-by: Bruce Ashfield

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

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-compute-deploy: initial creation

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

Add a nested layer that contains the configuration and appends necessary to deploy a compute node. Signed-off-by: Bruce Ashfield