Charm Layer - OpenStack base layer
Go to file
Liam Young 7fa96de883 Add generic action code.
Add generic action code that utilises charms_openstack.bus.discover()
so that the top level charm does not need to make any changes to
inherit generic actions.

Change-Id: I8b3422b915e2477d936e5cdd2d883c6815487577
2018-09-20 13:00:04 +00:00
actions Add generic action code. 2018-09-20 13:00:04 +00:00
exec.d/openstack Ensure git is installed for all reactive openstack charms 2018-05-10 12:36:36 +01:00
reactive fix a typo in layer_openstack.py 2018-05-24 16:02:13 +08:00
templates Merge "Support service_domain for reactive charm" 2018-07-12 16:08:19 +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
.zuul.yaml import zuul job settings from project-config 2018-09-11 13:15:14 -04:00
LICENSE Rework licensing, update README a bit 2016-07-01 10:04:45 +01:00
README.md Update readme doc 2017-08-28 21:20:46 +00:00
actions.yaml Add generic action code. 2018-09-20 13:00:04 +00:00
config.yaml Add use-internal-endpoints option 2017-09-05 11:35:39 +01: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 Add generic action code. 2018-09-20 13:00:04 +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: