lp://staging/charms/openstack-dashboard
- Get this branch:
- bzr branch lp://staging/charms/openstack-dashboard
Branch merges
Branch information
- Owner:
- OpenStack Charmers
- Status:
- Mature
Recent revisions
- 137. By David Ames
-
Updates for stable branch creation for 16.07
Set defaultbranch for git review/gerrit.
Switch amulet tests to stable.
Switch to using stable charm-helpers branch.Change-Id: I089ed79baa8c8d
e58011fd938182c 65b3812deab - 136. By Liam Young
-
Pre 1607 release charm-helpers sync
Sync charmhelpers to pick up bug fixes for 1607 release
Change-Id: I998eefb64c9484
1863e32722fa653 2244142ef8a - 135. By Ryan Beisner
-
Use bundletester for amulet test execution
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.Rename amulet tests inline with gate-*, dev-* and dfs-*
naming standards.Update README to refer to functional testing section of the charm
guide.Change-Id: I649729447605b3
8a257c403dceb6c 6a8dfe9f582 - 134. By David Ames
-
Install python dependencies early for CH ip.py
When using charmhelpers.
contrib. network. ip apt install was quietly
failing. Install python dependencies in the early install hook
(before install.real).Charm-helpers sync to bring in apt_install with fatal=True
Change-Id: I4156e9fdacebd3
54cb637b591184a f340cc5fc96
Partial-Bug: 1601972 - 133. By David Ames
-
Pre-release charm-helpers sync
To begin release testing get each charm up to date with lp:charm-helpers
Change-Id: Ief766432d92440
a06162793c0cc34 eb4b54e3c5d - 132. By Corey Bryant
-
Various deploy from source changes and c-h sync
* openstack-origin is no longer required when using openstack-
origin- git.
* Drop kilo from openstack-origin- git default values because upper
constraints doesn't work in kilo for openstack-dashboard and glance.
* Add flag to allow for disabling upper constraints when using
openstack-origin- git with user-specified git repositories. Change-Id: I1a020dcb03716f
543d4b5edb20180 9544365eab2 - 131. By James Page
-
Resync charmhelpers for licensing change
The charm-helpers project have re-licensed to Apache 2.0
inline with the agreed licensing approach to intefaces,
layers and charms generally.Resync helpers to bring charmhelpers inline with charm
codebase.Change-Id: Ib8d567d1449f16
0e3b2af8afd7b39 f217c1d98f5 - 130. By James Page
-
Re-license charm as Apache-2.0
All contributors to this charm have agreed to the switch
from GPL v3 to Apache 2.0; switch to Apache-2.0 license
as agreed so we can move forward with official project status.Change-Id: I5e55c2dc9e9f91
1c8113fab09c6f8 c89c86ec94a - 129. By Liam Young
-
Add support for Keystone API version 3
This change enables the charm to configure the Openstack Dashboard
to support Keystone v3 integration. Mitaka is the earliest release
to support Dashboard and v3 integration so v3 integration should
only be enabled on Mitaka or above.A new identity policy template now ships with the charm which is
specifically for v3 integration.Both the local settings file and the new v3 policy file need the
admin domain id. This is now passed to the charm from Keystone via
the identity service relation.The openstack-dashboard package uses
django.contrib. sessions. backends. signed_ cookies for session
management but cookies are not large enough to store domain scoped
tokens so a different session management engine is needed. This patch
adds the option to relate the charm to a database backend. If the
relation is present then the charm uses the
django.contrib. sessions. backends. cached_ db session engine. This
stores the session information in the database and also caches the
session information locally using memcache.For details on Dashboard and v3 integration see
https://wiki.openstack .org/wiki/ Horizon/ DomainWorkFlow Change-Id: I24f514e2981175
2d7c0c5347a1157 d9778297738
Partial-Bug: 1595685
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)