| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Introduce image openstack-image-aio, integrating both compute and controller functionality
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
| |
|
|
|
|
|
|
|
|
| |
- 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>
|
| |
|
|
| |
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
| |
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
| |
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 <bruce.ashfield@windriver.com>
|
| |
|
|
| |
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
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 <bruce.ashfield@windriver.com>
|
