openstack/tripleo-image-elements
Code Issues Proposed changes
544d57e22d
tripleo-image-elements/elements/boot-stack
History
Ghe Rivero 64dcd93e99 Remove all first-boot.d references 
first-boot.d has been deprecated for two releases so is about
time to remove any references to it.

Change-Id: Id8415447592be9fb3fd009dc528aed3c42b6095d
2014-10-08 08:02:07 +00:00
..
bin Run migrations from only the bootstrap host 2014-07-18 12:27:36 -07:00
install.d Move python-netaddr install to network-utils 2014-07-01 14:04:46 +00:00
os-apply-config/root Use keystone.host in stackrc 2014-07-22 14:26:09 -04:00
os-refresh-config Switch from upstart to os-refresh-config for MySQL server-id's 2014-06-23 21:19:45 +01:00
element-deps Update bootstack to use sysctl-set-value. 2014-06-04 14:37:37 -04:00
README.md Remove all first-boot.d references 2014-10-08 08:02:07 +00:00

README.md

A self-contained one-node openstack.

Description

This element contains nova, glance, and keystone services.

When building an image containing boot-stack be sure to add either nova-kvm or nova-baremetal to enabled the appropriate hypervisor.

The seed-stack-config element can be used to configure boot-stack in the absence of Heat.

Basic Usage

See this doc for basic usage instructions: http://docs.openstack.org/developer/tripleo-incubator/devtest.html

Credentials

OpenStack credentials are installed to /root/stackrc in the boot-stack machine, for automation needing them w/in the instance. Credentials are set from metadata, so consult config.json or your heat parameters.

Utilities

The following utilities are available in the running boot-stack machine:

reset-db - Clear all openstack databases.

boot-stack-logs - Start a screen session which tails important logs.

Configuration

For setting up keystone, controller-address can be set to an explicit address that will be used to control the endpoints for the initial cloud. If it is not set, the default is to try and determine the address from the default network interface configuration.

Here is an example of its usage in Heat Metadata:

controller-address:
  Fn::GetAtt: [ ControllerResource, PublicIp ]

Note that if you are feeding this Metadata to ControllerResource it will not be fed into the process until the Heat Metadata is refreshed, since the initial Metadata copy will have '0.0.0.0' (as we don't know the address until after we create a server record).

Some configuration is tied into the neutron-openvswitch-agent - see the README.md there as well.