History

David Ames 8a254c07e9 Update peers with API addresses Use default_update_peers which will publish admin, internal and public addresses to peers. Change-Id: Iaa3fc3f2401981f6f0a2130a277a6da7439cff52 Closes-Bug: #1858132 (cherry picked from commit `b4166e949c`)		2020-04-01 16:53:46 +01:00
..
lib	Add the ussuri major package version	2020-01-30 18:29:24 +00:00
reactive	Update peers with API addresses	2020-04-01 16:53:46 +01:00
templates/train	Initial Commit	2019-10-15 18:13:51 +00:00
tests	Updates for stable branch creation	2020-02-17 15:55:48 +00:00
HACKING.md	Initial Commit	2019-10-15 18:13:51 +00:00
README.md	Initial Commit	2019-10-15 18:13:51 +00:00
copyright	Initial Commit	2019-10-15 18:13:51 +00:00
layer.yaml	Initial Commit	2019-10-15 18:13:51 +00:00
metadata.yaml	Initial Commit	2019-10-15 18:13:51 +00:00
test-requirements.txt	Initial Commit	2019-10-15 18:13:51 +00:00
tox.ini	Initial Commit	2019-10-15 18:13:51 +00:00
wheelhouse.txt	Updates for stable branch creation	2020-02-17 15:55:48 +00:00

README.md

Overview

This charm provides the Placement service for an OpenStack Cloud.

OpenStack Train or later is required.

Usage

As of Train, the placement API is managed by this charm and is no longer managed by the nova-cloud-controller charm.

Placement relies on mysql, keystone, and nova-cloud-controller charms:

juju deploy --series bionic --config openstack-origin=cloud:bionic-train cs:placement
juju add-relation placement mysql
juju add-relation placement keystone
juju add-relation placement nova-cloud-controller

If upgrading nova-cloud-controller to Train, the upgrade requires some coordination to transition to the new API endpoints. Prior to upgrading nova-cloud-controller to Train, the placement charm must be deployed for Train and related to the Stein-based nova-cloud-controller. It is important that nova-cloud-controller is paused while the API transition occurs (pause prior to adding relations for the placement charm) as the placement charm will migrate existing placement tables from the nova_api database to a new placement database. Once the new placement endpoints are registered, nova-cloud-controller can be resumed. After all of the steps have completed, nova-cloud-controller can then be upgraded to Train. Here's an example of the steps that were just described:

juju deploy --series bionic --config openstack-origin=cloud:bionic-train cs:placement
juju run-action nova-cloud-controller/0 pause
juju add-relation placement mysql
juju add-relation placement keystone
juju add-relation placement nova-cloud-controller
openstack endpoint list # ensure placement endpoints are listening on new placment IP address
juju run-action nova-cloud-controller/0 resume
juju config nova-cloud-controller openstack-origin=cloud:bionic-train

Bugs

Please report bugs on Launchpad.

For general questions please refer to the OpenStack Charm Guide.