Charm Layer - OpenStack base layer
Go to file
Alex Kavanagh 4f8408e47d Rework the default handlers into layer-openstack-*
Due to commit 95493a4 in charms.reactive, the default handlers in
charms.openstack broke.  This is because charms.reactive no longer will
run handlers that are not in the hooks/ or reactive/ directory tree; the
default handlers in charms.openstack are in the library code, which is
pip installed into the module packages.

This patch, and related patches in charms.openstack and
layer-openstack-api enable the default handlers to function again.  Note
that from a charm author perspective, the API to default handlers is
identical.  This is merely an implementation change.

Change-Id: I7feb7aed219728efd57b5878bb6a5ff9e204c52a
Partial-Bug: #1707685
2017-08-01 12:24:44 +01:00
reactive Rework the default handlers into layer-openstack-* 2017-08-01 12:24:44 +01:00
templates Update/add templates for deploying Memcache 2017-01-04 14:59:37 +00:00
.gitignore Add basic tox targets 2016-07-01 10:29:08 +01:00
.gitreview Add gitreview file for migration to openstack 2016-07-01 12:00:04 +01:00
LICENSE Rework licensing, update README a bit 2016-07-01 10:04:45 +01:00
README.md Fixed broken link 2016-07-06 10:44:07 +02:00
config.yaml Move logging options into base 2015-12-14 15:52:49 +00:00
layer.yaml Add basic tox targets 2016-07-01 10:29:08 +01:00
metadata.yaml Update/add templates for deploying Memcache 2017-01-04 14:59:37 +00:00
requirements.txt Add basic tox targets 2016-07-01 10:29:08 +01:00
test-requirements.txt Tidy/Fix Apache template 2016-07-13 08:29:24 +00:00
tox.ini Tidy/Fix Apache template 2016-07-13 08:29:24 +00:00
wheelhouse.txt Update location for charms.openstack 2016-06-28 09:56:41 +01:00

README.md

Overview

This layer provides the base OpenStack configuration options and dependencies for authoring OpenStack Charms. Typically you won't use this layer directly the openstack-api or openstack-principle layers which consume this layer are probably more interesting as layers to directly use.

Where is the code?

The code for this module is held in the charms.openstack module which is developed at the following location: