When using custom themes, some strict structure should be
used in order for it to work correctly.
Closes-bug: #1897805
Change-Id: I535478b06f8789f245b6c9fc523806c02c47a369
Former instruction leads to "ambiguous relation: could
refer to websso-trusted-dashboard or identity-service"
Change-Id: Ida997cad090f1acc82bdb75dd21c7593570b1400
The appendix in the deploy-guide has recently been
refreshed. This is the last of the nine charms that
support overrides to receive a streamlining in order
to cut down on duplication.
Included some missing information.
Made formatting improvements.
Added a Bugs section.
Change-Id: I094a4a6aac2f8611c304d349b27942169162a777
Adds a setting custom-theme which operats similar to ubuntu-theme and
default-theme. The provided resource is placed in the themes folder and
apache is setup to serve static content for the theme. This leaves the
default theme untouched allowing the custom theme to override files
based on the built in horizon theme capabilities. For details on theming
capabilities see:
https://docs.openstack.org/horizon/latest/configuration/themes.html
gnuoy: retry logic for unrelated test updated after a number of CI
failures.
Closes-Bug: #1778284
Change-Id: I91ad19e8aad5c0e0773d42fa4f085cbcecb82458
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: I24f514e29811752d7c0c5347a1157d9778297738
Partial-Bug: 1595685
Implement DNS high availability. Pass the correct information to
hacluster to register a DNS entry with MAAS 2.0 or greater rather
than using a virtual IP.
Charm-helpers sync to bring in DNS HA helpers
Change-Id: Iec7b94b2e97d770dfc4b6f4f0c52983e39078b98
openstack-origin-git currently only supports YAML that specifies
the git repositories to deploy from.
This adds support for default openstack-origin-git values. The
default values supported are: icehouse, kilo, liberty, mitaka,
and master. For example: openstack-origin-git=master.
Change-Id: I70ff0d4d0b8f511153261452ce2f10f3876474af
Rodrigo Barbieri