aboutsummaryrefslogtreecommitdiffstats
path: root/meta-openstack-compute-deploy/classes
AgeCommit message (Collapse)Author
2014-03-15OpenStack: Fix postgresql file permissionsAmy Fong
- 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 <Amy.Fong@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2013-10-03openstack: create simple deployment frameworkBruce Ashfield
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 <bruce.ashfield@windriver.com>
2013-10-03meta-openstack-compute-deploy: initial creationBruce Ashfield
Add a nested layer that contains the configuration and appends necessary to deploy a compute node. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>