* Update charm-swift-storage from branch 'master'
to 72e22a94ed4966ff6fb2fba41bac1b204dbd4c14
- Mock datetime instead of redefining standard library
This fixes up the test to mock the datetime calls specifically in
the test that needs to mock them, rather than the prior approach
which was redefining the behavior of the standard library function
globally.
Closes-Bug: #2045588
Change-Id: I9c585c91c5527a61e4a8dbcba0a8a01108cd9b2e
* Update charm-swift-storage from branch 'master'
to ca420eccbb9e1cd51379b27ac684ef6e94d380e7
- 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: Ib1586a486a7a01023bd59bfa70016481ad5f89dc
* Update charm-swift-storage from branch 'master'
to 955f7e710c62bf079838322439ae474279567ab2
- 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: I3ca0e47cc8cd0bc8475c0c4b0ef8d013d52401ed
* Update charm-swift-storage from branch 'master'
to 8045849848a5aa3c2ed5192710f0602d97d90fa2
- 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
* update charmcraft_channel to 2.x/stable
Change-Id: I3dd29fd9d9e5e7057dc50b03a4a3945d1c7178d2
* Update charm-swift-storage from branch 'master'
to 20a5dc391fe2a1becbeb46d6b6a25f1819317075
- Add docs key and point at Discourse
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: Ia0081ac92bcadf638df084e385cc3c0e7af4ecf7
* Update charm-swift-storage from branch 'master'
to 51bfe2adca5b2076ab5a55b192a044c3f7d155ae
- Merge "Add package-upgrade action"
- Add package-upgrade action
The package-upgrade action performs package upgrades for the current
OpenStack release.
The code path used is similar to the openstack-upgrade action, with the
difference being that package-upgrade will not execute if an openstack
upgrade is available (based on the openstack-origin setting).
This change includes a charm-helpers sync.
Change-Id: I0c7184bba29731354e52dc28e3a4dd6f282fa843
* Update charm-swift-storage from branch 'master'
to eb1980f0e3ef5d2b38db7c098255af7b2880f0cd
- Merge "conntrack: set sane sysctl defaults"
- conntrack: set sane sysctl defaults
swift-storage is often deployed alongside nova-compute where it
inherits some sane defaults for sysctl values, specifically around
conntrack configuration.
If its deployed standalone it does not recieve the same tuning,
but its very much applicable as access between swift-storage nodes
for rsync traffic is firewall limited so makes a high demand
on conntrack on the server.
Lift and shift the defaults from the nova-compute charm.
Change-Id: Iedd27a51ff93fd1670a418e1434c94875fe21643
Closes-Bug: 1879121
* Update charm-swift-storage from branch 'master'
to 93a1214feb1fde7874e3012678956ab820362cd4
- 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: Ie8a668f3ad032af939e87dba1cda18e30a2b13ff
* Update charm-swift-storage from branch 'master'
to 2f0f5f10ff3e10ed639fc5a99d51527e0d4cc13f
- Merge "Add Kinetic and Zed support"
- 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
Change-Id: I93da9ce52bed2b3e8a467491d2a61bfd2ed4ea7d
Depends-On: https://review.opendev.org/c/openstack/charm-swift-proxy/+/847513
* Update charm-swift-storage from branch 'master'
to 98c67e4d92cd4a9dbae16e8f7f6ff1d6e1bd186d
- Changes to the default inode size
As per the bug report, the xfs-inode-size default value is in contradiction with the current upstream advice.
This patch removes the default value and accept the filesystem defaults for mkfs.xfs inode sizes.
Closes-Bug: #1879423
Change-Id: I9effc6052524ead9817454912284e3c48ce55901
* Update charm-swift-storage from branch 'master'
to c40f1d531b6c801652941cf6c47425eef95c8567
- 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
- charmhelpers sync
Change-Id: Ie37826e7803659f2f40eaac5f8d539cce5ef145b
* Update charm-swift-storage from branch 'master'
to 26e45baa263f944fee02b700bb0df1f0ef8eb1c2
- 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.
Change-Id: I3559219e8d723dcf23fe107e7585b6f005053224
* Update charm-swift-storage from branch 'master'
to a5b484a2537ffe46a215952de13195f52603090e
- Merge "Update Makefile to reference Zaza and Python3"
- Update Makefile to reference Zaza and Python3
Change-Id: I0ab3e8abd4732ef2ccbcaeae58341796210a3af3
* Update charm-swift-storage from branch 'master'
to 90fa306577a0501439f68a8d228763b135c2163d
- Fix yaml.safe_load() and allow py35 tests to complete
Change-Id: Id1aa21f4b6de67a6e03ced2352b45d1080e7760c
* Update charm-swift-storage from branch 'master'
to e0ed80527facf7285ebb496157abe9dbf2b524f0
- Disable local overlay for the CMR bundles.
Closes-Bug: #1945786
Change-Id: I93ab6d1c19e34fd5001de1dcde978f74793f74ae
* Update charm-swift-storage from branch 'master'
to 2adc1dcdef9ceee715dc1c0413c8f7369e4c1cb9
- 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: Ia16e1d4dc68783577858815c86ae0cb2ffcc9134
* Update charm-swift-storage from branch 'master'
to 8a7bde93a1e69da31c2c062b78aaf4f86b26ec96
- Add impish to metadata.yaml
Change-Id: I9d657f34ee567149a7f0b504776cb40cd1629221
* Update charm-swift-storage from branch 'master'
to a173cc6a5bc7ace9adeef29ff60a07d6c5f5eb66
- Test bundles for focal-wallaby and hirsute-wallaby
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Libraries sync.
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I33460b286d635ed000c94e1d8e8f55ad4ff7dd83
* Update charm-swift-storage from branch 'master'
to 4990afb93700194e54e84122fdcc4372db4574e1
- 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: Id214883525ba3db9001f367cea3379ee3ffbd003
* Update charm-swift-storage from branch 'master'
to d82f0a4370f9a41ddb3ad22c9ca89ae65606ad7e
- 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: Id5ec1154770c87e18bb2a4244b22354c9d0edfc0
* Update charm-swift-storage from branch 'master'
to 9e0b2b4fb021c6f561a1492f90c0745bad3345fa
- 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: I4e72dafd2ab198846cb376097dd8a2b7438dedd9
* Update charm-swift-storage from branch 'master'
to 6beb4e5cc62b9ac33cb8449ea5cdf0303424e7e7
- Do not duplicate names for CMR jobs
Change-Id: I7e9d216684d467499059480b3190d70e03c27215
* Update charm-swift-storage from branch 'master'
to 689f3b7dadc0310fd594ebc448f2bda507791463
- 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: I6d15bbd54d384f3a658eb72418a2895bf9631927
* Update charm-swift-storage from branch 'master'
to 5048027372f34c5b4973caeafa4b36f52a3474b2
- 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-storage from branch 'master'
to fda297cf24681b0686d415ba096806a2232fe65f
- Merge "Fix swift replication errors"
- Fix swift replication errors
There are several errors related to the swift replication service.
The swift storage charm is not properly restarting the services
after configuration changes, the correct object_lockup_timeout
value (that per the behaviour observerd in our environments must
be greater than object_rsync_timeout) and we also needed to fix
the object replicator config file to honor the
object-handoffs-first configuration.
This patch along with the swift proxy-change should fix the
currently known replication problems.
Closes-bug: #1903762
Depends-on: I87eb23de94e3f2f5b06d44df1f8bd9d2324456a0
Change-Id: I87eb23de94e3f2f5b06d44df1f8bd9d2324c8470
* Update charm-swift-storage from branch 'master'
to 19d501090261b4e005696990267144a2491929dc
- 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: Icfa65b0e02060e63fa90a57cd95da1dcac729c06
* Update charm-swift-storage from branch 'master'
to 61d3a4d9aeab893b1dad890db7c67813aaa9bfad
- 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: I4a1e9239e40d27d48e48b9e5241240eff9689a3d
* Update charm-swift-storage from branch 'master'
to 250f901cb7bdd8278cb02642e1f410ee913f4717
- 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: Ic9c930a58afa9e1e849e61581b9cca588cc48529
* Update charm-swift-storage from branch 'master'
to 216ba766e71a3a5f9dfb2d4d998a701ac00b0923
- Remove Disco and Eoan bits
Change-Id: I6d7c6e27fa746fa502b5d5efabe36cb029df78f5
* Update charm-swift-storage from branch 'master'
- Add swift 2.26.0 version for victoria
Cherry-pick from 21f9f239c4
Change-Id: I84ada78c1f94974d1899a38c437073a17d5960ab
* Update charm-swift-storage from branch 'master'
- Batch update to land Ubuntu Groovy support into the charms
Cherry-Pick from 09752a1527
Change-Id: Idab61ae33fef40f065b22dc1bed460a73c6d58db
* Update charm-swift-storage 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: I28bc6125b817c2f1608157509c27d54dab9541a5
* Update charm-swift-storage from branch 'master'
- Monitor Swift Object/Container/Account API availability
As per the bug report, it's not enough to simply monitor that the
appropriate process is alive; there have been instances of the process
being alive but the port/API being unavailable.
This patch adds monitoring for Object/Container/Account API
availability.
I've tested the fix in my small test environment and I can confirm
it's working.
For reference, the following branch/commit was used as a functional
test (later rejected with the aim of moving the checks to Mojo):
https://github.com/openstack-charmers/zaza-openstack-tests/pull/395
Change-Id: I60c5b74279f71ca8f8bc769c93af2eab1f59e002
Closes-Bug: #1854299
* Update charm-swift-storage from branch 'master'
- Merge "Ensure lockup_timeout is never < 2*rsync_timeout"
- Ensure lockup_timeout is never < 2*rsync_timeout
Change-Id: Id0afc210b7be8ac7c740753ef06b51db0bae410c
Closes-Bug: 1888725
* Update charm-swift-storage from branch 'master'
- Merge "Add config option for fallocate_reserve"
- Add config option for fallocate_reserve
In order to prevent disks from filling up, add the option to configure
fallocate_reserve parameter in account-server.conf,
container-server.conf, and object-server.conf, as described in
https://docs.openstack.org/swift/latest/admin_guide.html#preventing-disk-full-scenarios
This change adds the config option file-allocation-reserve with a
default of 0.
Change-Id: Ib396a151250bb8d1733f9b5b9cab7eb506c9f6c6
Closes-Bug: 1872069
* Update charm-swift-storage from branch 'master'
- Add monitoring for object-replicator logs disappearing
As noted in lp#1691570, there is an issue with storage I/O during
coro-thread cleanup that affects the swift-object-replicator's ability
to complete replication successfully. This is most easily witnessed by
the lack of the every 5 minute replicated percentage complete messages
that should come from the swift-object-replicator daemon to syslog.
This patch monitors for and alerts on the condition of the "replicated"
line missing from syslog within the past 15 minutes.
Change-Id: Ieb15da3f3f67fa9bcad03151e36c70faae4c36c9
Closes-Bug: 1691570
* Update charm-swift-storage from branch 'master'
- Merge "Sync charm-helpers for Victoria/Groovy updates"
- Sync charm-helpers for Victoria/Groovy updates
This sync picks up the release and version details for Victoria/Groovy.
Change-Id: I62c72464c2dd792d6323adbf5627406e38ae5559