* Update charm-swift-proxy from branch 'master'
to 3dadc053a4e53b4a539725de0863f7f0a5382731
- Updates for caracal testing support
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: I2dbb764d39c8fc95ec9bf4acb621d02f6174940a
* Update charm-swift-proxy from branch 'master'
to 4ebb43d731da8a048e1ac7cc9fc8b33468cb7e76
- Enable swift payload upgrades for wallaby+
Sync charm-helpers to pick up fix for openstack_upgrade_available
that enables successful payload upgrades. This will need backporting
to stable/wallaby.
https://github.com/openstack-charmers/zaza/pull/619
Closes-Bug: #2040606
Change-Id: Ib5f446d617c11c9c9046c33335c1099b21b5166e
* Update charm-swift-proxy from branch 'master'
to 89d7e78998c0e67b83748fe700f0188c76f69393
- Improve platform mocking
Patch out charmhelpers.osplatform.get_platform() and
charmhelpers.core.host.lsb_release() globally in the unit tests to
insulate the unit tests from the platform that the unit tests are being
run on.
Change-Id: Ic558fa7bab80b0dabc3e5a06d7494e2688c027b3
* Update charm-swift-proxy from branch 'master'
to fb1a1bbcf787ed89fcd6684d456da63aaf48822d
- Ensure get_requests_for_local_unit doesn't fail on incomplete relation
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
[1] https://github.com/juju/charm-helpers/pull/824
Closes-Bug: #2028683
Change-Id: Ie197482fcba7cadd27ea74f22e2a6e2c97eaddac
* Update charm-swift-proxy from branch 'master'
to 4e5659b51bfb7204dc9de0d14e21b7e5cb10b1d5
- Add 2023.2 Bobcat support
* sync charm-helpers to classic charms
* change openstack-origin/source default to bobcat
* add mantic to metadata series
* align testing with bobcat
* add new bobcat bundles
* add bobcat bundles to tests.yaml
* add bobcat tests to osci.yaml
* update build-on and run-on bases
* drop kinetic
Change-Id: I0f57eb5912bbb21e29f2f4b72dd137342c1cf3fe
* Update charm-swift-proxy from branch 'master'
to 4d176e13303b2d35be4f8fbca3bf0f25cff80415
- Enable jammy-antelope voting and drop kinetic-zed tests
* 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
* Update charm-swift-proxy from branch 'master'
to c29a1c7b8e953b2055763c16d04786b800300f9d
- Add support for HAProxy L7 checks
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
* Update charm-swift-proxy from branch 'master'
to 745a89a7c1b1837b72bf36bf9ff2024d40de8fac
- Add Kinetic and Zed support
* 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 charm-swift-proxy from branch 'master'
to fa61a4e59bf35d276b07c243a811b4f934fc244b
- Pin tempest for different python versions
Change-Id: I2d0d6ee83aacc4e0ab109384496fa23211a31cda
* Update charm-swift-proxy from branch 'master'
to 9d55ad9570e8888454b0f1807cde3136f324695f
- Trivial grammar fix in README.md
A minor grammatical error is fixed under Usage > Configuration > replicas in the README.md file.
Closes-Bug: #1979029
Change-Id: Ice371e667979217eb22a82a8722e2e234ca4f762
* Update charm-swift-proxy from branch 'master'
to dde918015e2c1c3bfab0f68246b0bb439dd22a97
- Merge "Add new version template: yoga"
- Add new version template: yoga
Closes-Bug: #1960866
Change-Id: I90769c16ca05c725c212255da5cb04a5e36bdcda
* Update charm-swift-proxy from branch 'master'
to 5a4e378361b47a535ed09411fac194763df00592
- Use python3-jinja2 for py3.
Change-Id: Ic00d65bee184b20fe98de7ce237df5fcba961622
* Update charm-swift-proxy from branch 'master'
to 913c50116a333bd89a6f1fba01cb4b065440498a
- Updates to enable jammy and finalise charmcraft builds
- 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
Change-Id: I2bd113d92c603c429ba7323a713bb901ce0f4978
* Update charm-swift-proxy from branch 'master'
to 733f8d979130014d3ada09586aa6f5541e4ce39f
- Migrate charm to charmhub latest/edge track
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>
* Update charm-swift-proxy from branch 'master'
to 50417cdb32449fb070d781dc980d344c5280af31
- Use unittest.mock instead of mock
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I8757d430ab233f4a21d1d599f1a7a9a0dc68d7ef
* Update charm-swift-proxy from branch 'master'
to d92cf5756ed7ee7364e7b12061b69d51aa5bc684
- Fixed removing multiple devices
Added a confirmation flag for swift-ring-builder command when multiple devices are found to be removed.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/656
Closes-Bug: #1937289
Change-Id: Ieeb326e7d9af21a77954e95e909d6fcf20a3092c
* Update charm-swift-proxy from branch 'master'
to fb8ed49ae43da5969f59ce14a2a23a716d655e80
- Disable local overlay for the CMR bundles.
Closes-Bug: #1945786
Change-Id: I58774e4d757ea2fb4533dc7ed284f4119c92f010
* Update charm-swift-proxy from branch 'master'
to 82d8f3693c87eb6935edab803d946d88a5a19cdd
- Replace reference to 'juju set' with 'juju config'.
Change-Id: I906f43b8222baabc2f95a3076ef7329a136102d1
* Update charm-swift-proxy from branch 'master'
to cc6bac5758fe889e05763772a2f13bdb7e5cf5cb
- Sync release-tools
In order to fix ResolutionImpossible on tox invocation.
https://github.com/openstack-charmers/release-tools/issues/151https://github.com/openstack-charmers/release-tools/pull/152
Also remove unused applications from bundles for focal-ussuri+ as zaza
is now more aggressive at checking for applications that have no units
during deployment.
Change-Id: I0b30a731751960782569f4f2a443a07f3fc07d91
* Update charm-swift-proxy from branch 'master'
to a513ec881c823afbd7179bce9f4147303ada0241
- Add impish to metadata.yaml
Change-Id: I8db38c02c33ae61c39f84d9a138450f402c8a8da
* Update charm-swift-proxy from branch 'master'
to b086bc94b94f969aff5f5c6470bfd8ba1ee1efc5
- Test bundles for focal-wallaby and hirsute-wallaby
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>
* Update charm-swift-proxy from branch 'master'
to 54583248b9510ba0d17313dea044b402953f4e94
- Bump default swift partition power
The partition power is used to build the swift rings. The total
number of partitions in the cluster will be 2^partition-power.
The recommend number of partitions of a cluster is a minimum of 100
per disk. Given that 2^8 is only 256, this number will lead to a sub-
optimal configuration even on test deployments, not to say on production
where disks can surpass the hundreds, and this will lead to a very
unbalanced cluster.
Closes-bug: #1931286
Change-Id: Ifdf2b96f27f18bc64549c40d8fa47474f8eb59c8
* Update charm-swift-proxy from branch 'master'
to a8d77d22fed0a9b715ddb4e8a289602f16c0d946
- Updates to flip all libraries back to master
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ifad219bd1826fcd7129f687bf2739e217b960930
* Update charm-swift-proxy from branch 'master'
to 4a1166dfd316969fa4b3001a033be21d9620991e
- 21.04 sync - add 'hirsute' in UBUNTU_RELEASES
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: Iaa9a59f43531c6f0f03a73e003646ada7fdc7419
* Update charm-swift-proxy from branch 'master'
to be941c5270e07111a2e78bfa2863497791da85d0
- 21.04 libraries freeze for charms on master branch
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: Id08d92c4d80284c290747cb68da06a0fadd1dca6
* Update charm-swift-proxy from branch 'master'
to 3e56f32d5599a798a0aac81382a83b24ac48f480
- Merge "Add new osci.yaml"
- Add new osci.yaml
This change is preparatory to migration Ubuntu OpenStack CI
from Jenkins to Zuul
Change-Id: Id44d2037d5743bc882388141d726194c51d82fbf
* Update charm-swift-proxy from branch 'master'
to fb6bdd4d0fcc103d66c03c97210cfb1f854436ac
- Add hirsute and remove trusty from metadata.yaml
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I5a1053d6da7284b8edc98c76ca7fe1cdfa720b8f
* Update charm-swift-proxy from branch 'master'
to cf2a573fc2fc6616ed5dfc6e275e41a4d01cdfd8
- Merge "Fix swift port replication configuration"
- Fix swift port replication configuration
Port replication configs are not being set into the ring files.
When replication port configs
(account|container|object)-server-port-rep, are changed in the
swift-storage charm, swift-storage changes the related configs in
the config files, but that does not update the rings.
This patch adds a function that runs in every config-change
triggered from the swift-storage nodes and make sure any replication
config is written to the ring and distributed to all nodes.
Partial-bug: #1903762
Change-Id: I87eb23de94e3f2f5b06d44df1f8bd9d2324456a0
* Update charm-swift-proxy from branch 'master'
to dee0aa7c2ee6a825c6fb464f319100267fefd22c
- Hotfix charmhelpers sync for local_address() fix
The network-get --primary-address juju-info fails on pre-2.8.?
versions of juju. This results in a NoNetworkBinding error.
Fallback to unit_get() if that occurs for local_address().
Change-Id: I1faf793d433e1a0c61b8ad8efd1291cd77133ff6
* Update charm-swift-proxy from branch 'master'
to 772013e6b8315f0f99a9c14ab6a63a536bac22b6
- Updates for testing period for 20.01 release
Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I9b82fbd56bd64fa758dd069b984ba12ec6f6ce34
* Update charm-swift-proxy from branch 'master'
to e4457aa89a79930a5b23072ac69b8366bd46a1f1
- Merge "Updates for testing period for 20.01 release"
- Updates for testing period for 20.01 release
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I838600e41e6c4216551ccd51019e3a0a959a3e2c
* Update charm-swift-proxy from branch 'master'
to a215ecbd051e87b346c9c5dcb96d46255cac5c27
- Remove Disco and Eoan bits
Change-Id: If6fcf45531bccb5e17df7609f7bd19c926a28185
* Update charm-swift-proxy from branch 'master'
to 21a7a023b4fb5e72332959050d7452c46315b049
- Add leader hooks
The charm makes use of leader db and checks whether a unit is the
leader but the symlinks to enable leader settings are missing.
Change-Id: I0e19ec42a928466580aaad18a7278108d1060158
Closes-Bug: #1478713
* Update charm-swift-proxy from branch 'master'
- Add swift 2.26.0 version for victoria
Cherry-pick from 21f9f239c4
Change-Id: I2315608f10f6dd03397f5abc5999b5fb30fde611
* Update charm-swift-proxy from branch 'master'
- Batch update to land Ubuntu Groovy support into the charms
Cherry-Pick from 09752a1527
Change-Id: Iceafc2191b62db7bf0e50c16311e0e039f794c30
* Update charm-swift-proxy from branch 'master'
- Sync libraries & common files prior to freeze
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I452af2fa5a833c435b913571fd059282bbe0a1a6
* Update charm-swift-proxy from branch 'master'
- Alter handling of identity-service relation data
This patchset changes the handling of the identity-service relation data
from "the last connected charm in the relation-list is the data to use"
to "merge non None data from all relations, with the last one winning."
This is to handle the change in how keystone now sets relation data on
the identity-service relation: only the leader actually sets the
relation data. This means that the consuming charm only 'sees' relation
data from leader, with no keys from the non-leaders.
charms.reactive handles this by merging data from all the relations.
This change exhibits the same behaviour.
Change-Id: Ic77c0127ab9903c1596d2be882735acec3d2e2f9
Closes-Bug: #1889930
Alex Kavanagh