openstack/tripleo-image-elements
Code Issues Proposed changes
fe3f62ff65
tripleo-image-elements/elements/boot-stack
History
Robert Collins c1a9714574 Run neutron-db-manage on reset-db. 
This is not documented in any of the manuals but is showing up in
upgrade wiki pages.

Change-Id: I4999bff2bf348551f419f03bc2815c589026eea6
2014-02-24 19:21:48 +13:00
..
bin Run neutron-db-manage on reset-db. 2014-02-24 19:21:48 +13:00
install.d Enable mysqld service in mysql element 2014-01-03 06:54:55 +00:00
os-apply-config/root Remove stale comments 2013-11-01 11:30:52 +00:00
os-refresh-config Moving iptables rules to the relevant elements 2014-01-28 06:31:54 -05:00
element-deps Remove rabbitmq-server from boot-stack's element-deps 2014-02-10 16:52:26 -08:00
README.md Clarify that boot-stack isn't only for baremetal 2013-11-25 10:56:45 +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

First Boot

Upon first boot, scripts will be automatically run to perform the following:

  • database initialization
  • service restarts
  • default keystone accounts

The output of the first-boot scripts can be viewed in /var/log/first-boot.d.log. The file /opt/stack/boot-stack/boot-stack.ok will be touched upon the scripts' completion.

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).