Charm Layer - OpenStack base layer
Go to file
Nguyen Van Duc 4185336cf6 Add py36 testenv
Python 3.6 is installed by default in Ubuntu 18.04 LTS.
Therefore, according to Transition Plan [1],
it'll be handy to have py36 testenv.

For more details, please check Python2 Deprecation Timeline [2]
and Python3-first Goal - Completion Criteria [3].

[1] https://wiki.ubuntu.com/Python/Python36Transition
[2] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html
[3] https://review.openstack.org/#/c/575933/8/goals/stein/python3-first.rst@42

Change-Id: I9ef19ce60935999b386165f51a83b6be9714266e
2018-07-12 16:15:21 +07:00
exec.d/openstack Ensure git is installed for all reactive openstack charms 2018-05-10 12:36:36 +01:00
reactive Move application version set to charms.openstack 2017-09-06 17:43:05 +01:00
templates Enable proxy header parsing 2018-06-28 13:10:00 +09: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 Update readme doc 2017-08-28 21:20:46 +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 py36 testenv 2018-07-12 16:15:21 +07: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: