These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal. They do NOT lock the charms
down, and don't change the testing branches to stable branches.
Change-Id: Id88fe1d5e3b177099966c659d11b96e6d1fb4c4f
openstack-dashboard exposes the hostnames (and IP addresses) that can be
used by users to load Horizon. There are 3 possible sources, they are
juju units ingress-address, os-public-hostname and vip config options
Closes-Bug: #2030094
Change-Id: I5eb524c6258f72980ef43175f2bed21d7ca078be
This patch adds kinetic to the metadata.yaml and ensures
that a run-on base for 22.10 is added in the
charmcraft.yaml
Change-Id: Ib0157b2ab640aac2441eeb08524367129d84db8e
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: I2cb698f719106e54b06009f24ea47259419e9cad
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
- Fix mocking on unit tests for install.real hook
Change-Id: I7bf692965341c0cc1c84c7d3c77cce63a6cb6cbc
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: Ie287d7462b5e2cfcb1f91f25117eb61d93f59a1f
Homer[1] is static web server and provides one stop shop UI,
which a single URL and be able to click on a link to get to
the LMA stack and other sites (like MAAS, other support portal).
The application is registered to Homer dashboard via application-dashboard
relation.
By adding registration relation in openstack-dashboard charm,
we can register Horizon in Homer dashboard after creating relation
between openstack-dashboard charm and Homer charm
[1]. https://github.com/bastienwirtz/homer
Closes-Bug: 1945725
Change-Id: Ieeacd8f1dda7e88a1f3f7b332163b2b42f1fee41
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I615caee631ac7ee785b84cdc9b18d2d9a7f1a0d1
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: I4a42144ff3f1cf01d6ea26fec80980d27a6bd64f
Add bionic-ussuri and focal-ussuri (with mysql8 support) bundles.
Also, for focal, switch the install and upgrade-charm hooks to install
python3 modules rather than python2 modules.
Change-Id: I75dbf72eb4c2d7d2986730e0ada9a6c359f825d3
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I709e8a00a82e0561e81dac481f75cd5c8a249ce5
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I47ea16ef504c5d06205d119a726fd7b9f64963b8
Add support for the dashboard to request and receive certificates
via the certificates relation, currently implemented by vault.
The first request to the dashboard can take sometime to return
so increase the timeout.
Change-Id: I173523ddbe3269e3fcdae49062cdb34e78786e44
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
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I1e0b7d0d0994fd229c15cf8c456b2b82bc4041e8
* add support for relating with subordinate charms providing Service
Provider functionality via apache2 authentication modules;
* retrieve protocol, identity provider and user-facing name info from
keystone service provider charm subordinates;
* provide trusted dashboard information to keystone charm
Change-Id: I15ca0dd1616ec12c7ad47dc05961b51bb45bb770
This binding is required so that the DNS-HA code can find the
address to use for the hostname specified by os-public-hostname.
This also deprecates the os-internal-hostname and os-admin-hostname
options, as there is no binding to use them with.
Change-Id: I57609c5ab641e2ae6377c6fbad5c9e7b8cf6495c
Closes-Bug: #1742548
Bionic, being the next LTS, is important to enable for dev
and test as early as possible ahead of 18.02.
Zesty goes EOL in Jan 2018. The next stable charms release (18.02)
will not provide Zesty series support, as it was an interim
(non-LTS) release.
Change-Id: If96d593120b3b334819fca892042ec17c7403dd6
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
Change-Id: Ie85a1357f75d51af07c20028cd69f5cf9c0598f1
The charm store does not yet recognize this series, and errors
when it exists, thereby preventing push/release of dev charms
into the charm store.
Revisit after the following is resolved:
- https://github.com/juju/charmstore/issues/695
Change-Id: Ic697b0605aa84dbeeb652eb3428a88548ff76728
This optimizes the publication process to the charm store, and
ensures that the charm code and version is consistent across all
supported Ubuntu series.
Change-Id: I9157fa5c67e437b407db4bc1d7e47c320eb98665
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