openstack
/
tripleo-image-elements
Code Issues Proposed changes
tripleo-image-elements/elements/boot-stack
History
Derek Higgins 17ba310156 Fix path to neutron dsn. 
The correct path is neutron.ovs_db as is also used in ml2_conf.ini.
The incorrect path has work up to now because the default alternative,
just happens to match whats in the heat template.

Change-Id: I8ffe1eb481f615b0fbe127cd8107f1e70794c839
 		2015-04-30 14:45:41 +01:00
..
bin Fix path to neutron dsn. 2015-04-30 14:45:41 +01:00
install.d Migrate to package-installs scripts 2014-11-05 01:38:05 -08:00
os-apply-config/root Enforce owner readonly permissions on stackrc 2015-04-21 12:14:16 +01:00
os-refresh-config Switch from upstart to os-refresh-config for MySQL server-id's 2014-06-23 21:19:45 +01:00
README.md Remove all first-boot.d references 2014-10-08 08:02:07 +00:00
element-deps Migrate to package-installs scripts 2014-11-05 01:38:05 -08: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.