openstack
/
charm-placement
Code Issues Proposed changes
charm-placement/src
History
Liam Young 03e2f648f9 Pass certs interface to configure_tls 
If the certificates interface is present then it should be passed
to configure_tls otherwise it is ignored.

Change-Id: I3ba5432d3fd4f9481dadb49586a7bab938a0c4ff
Closes-Bug: 1896227
(cherry picked from commit fda2c40cc4)
 		2020-09-21 15:03:42 +03:00
..
files Release sync for 20.08 2020-07-27 20:58:45 +01:00
lib Add victoria package version 2020-07-13 18:38:37 +00:00
reactive Pass certs interface to configure_tls 2020-09-21 15:03:42 +03:00
templates/train Initial Commit 2019-10-15 18:13:51 +00:00
tests Updates for stable branch creation 2020-08-13 11:39:50 +01: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
icon.svg Remove inherited configuration options invalid for charm 2020-05-18 10:03:08 +02:00
layer.yaml Revert part of "Remove inherited configuration ..." 2020-07-21 14:23:52 +01:00
metadata.yaml Updates for 20.08 cycle start for groovy and libs 2020-06-02 14:36:29 +01:00
test-requirements.txt Release sync for 20.08 2020-07-27 20:58:45 +01:00
tox.ini Release sync for 20.08 2020-07-27 20:58:45 +01:00
wheelhouse.txt Updates for stable branch creation 2020-08-13 11:39:50 +01: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.