* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
Change-Id: I4623910b60e39fa957cac71ad9519fdfda231e2a
This change add several configuration options to enable HTTP checks
to the HAProxy configuration, instead of the default TCP connection
checks.
Closes-Bug: #1880610
Change-Id: Ie1f53d38c1c45ce3b2ddf5041eaa04a7f3139066
* 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
* add domain/project to auth section of yoga proxy-server.conf
Change-Id: I93da9ce52bed2b3e8a467491d2a61bfd2ed4ea7d
Closes-Bug: #1988491
Update to classic charms to build using charmcraft in CI
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Bundle fix needed since z-o-t:
2bb4271530
Change-Id: I0067ff7941037b7e87dbfc1fb92b48bb380bb22d
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Change-Id: I97b20f0f8eaae99b2ca75e283f4a2c29be871198
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
This patchset implements policy overrides for swift-proxy. It uses
the code in charmhelpers.
Closed-Bug: #1741723
Change-Id: Ic51ee5d181558b63dfd968c5b0c7d40760a5ac59
Upstream removed the api_version configuration option and started
to expect the version to be encoded in the Keystone URL at Rocky.
Add S3 API functional test.
Remove invalid configuration items in the s3token section.
Remove configuration templates for OpenStack versions prior to
Mitaka.
Change-Id: Ia3306441222f7c078d460c659701a57a5944c928
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/194
Closes-Bug: #1867373
This patch also updates the smoke test to run bionic-train.
Also drop tests/basic_deployment.py as it is no longer used.
This should have been dropped in the transition to zaza.
Change-Id: I74594019743b83190d7d55d8eb7aeed7e8c40d04
This patchset adds a template for the 'dispersion.conf' file which is
used for swift cluster health monitoring.
Change-Id: I348ded9f94f2bcb7a680b2c2280ff163cde65c46
Closes-Bug: 1328064
Drop service check for ``glance-registry``. The service is
removed as of Stein, and it really is not this charm functional
tests job of checking this anyway. Any such detail should
be deferred to the ``charm-glance`` functional tests.
Change-Id: Ibc0a6302f154b3c7c6366921fd0245a43b647dc6
Swift support is in-tree for Swift since OpenStack Rocky, and
the swift-plugin-s3 package has been removed from the archive at
Cosmic so drop installation at Rocky.
Add new template for Rocky to use the in-tree s3api and s3token
middleware.
Enable cosmic test to validate changes.
Change-Id: Ie5447dc44203c1ea2ad27e6d71248ba59d7549d0
Closes-Bug: 1805597
Re-align pipeline with default example pipeline; this includes
adding the following new middleware:
- copy
- ratelimit
- symlink
Re-work SLO middleware configuration to avoid duplicated section.
Re-order middleware inline with documentation avoiding authentication
issues when using DLO/SLO features.
Drop proxy-server.conf validation; its brittle and function should be
validated by other tests anyway.
Change-Id: Ic9df7c12ee0bb402245ad2e64da0d905fe68890c
Closes-Bug: 1794255
Add a tactical change which is already merged into charm-helpers.
This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.
Reference:
4835c6c167
Change-Id: I4dfe997fab2c07530c47c8f6a0d8b62af56ef584
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: Ie9ebf332035e7dd2391e9c41cfba922b28a48518
Adds new template for Queens that correctly configures
swift3, s3token and proxy pipeline.
Also fixes amulet tests that are currently failing due
to vdb being already mounted in guest and templates
that fail py3.5 due to jinja syntax.
Change-Id: I8ed8a12d2d6adc1f1f3158808101b123ec6bd20d
Closes-Bug: #1775260
Switch to using automatic keystone v2/v3 version detection
using new amulet charmhelpers in functional tests.
Enable xenial/queens amulet test as part of extended tests.
Change-Id: I4de220d3561bf065a3f1f64455cda22a7a807c1a
Depends-On: Ie6e2733f34de10a4d34b18dbf1fd9ba623af0e18
Depends-On: Ibcc36ca22d72d310921f840e6081608be1fbc7e1
From Kilo onwards the swift-proxy charm is
misconfiguring the swift3 middleware such that
the api is unable to respond to any requests.
We fix this by providing working config for
Kilo onwards.
NOTE: see LP for full explanation but due to
problems with package version mismatches in the
UCA this patch only fixes Trusty Kilo, (L is
EOL) and Xenial Mitaka.
Change-Id: Ice5690e7f06ffc78dd20b53b67dffc6bd72b2613
Closes-Bug: 1738063
The default HAProxy timeout values are fairly strict. On a busy cloud
it is common to exceed one or more of these timeouts. The only
indication that HAProxy has exceeded a timeout and dropped the
connection is errors such as "BadStatusLine" or "EOF." These can be
very difficult to diagnose when intermittent.
This charm-helpers sync pulls in the change to update the default
timeout values to more real world settings. These values have been
extensively tested in ServerStack. Configured values will not be
overridden.
Partial Bug: #1736171
Change-Id: I0aefed05d7b06162d21bb5ded216fc32935ef52e