Charm Layer - OpenStack base layer
Go to file
Doug Hellmann 9a3807eeb3 fix tox python3 overrides
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.

We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.

We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.

Change-Id: I360fc2d49b9e737fd36442ac291a1f532f98b3e7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-09-26 18:39:32 -04: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 Remove the 'debug' action 2018-09-20 15:40:58 +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 fix tox python3 overrides 2018-09-26 18:39:32 -04: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: