Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
- Pin everything in wheelhouse.txt for bionic and focal support.
This will need updating when the charm channels are created.
Change-Id: Ieb8cae3653380b7364bdbc128216bd27f924293a
The tvault-contego.conf and tvault-object-store.conf files have jinja
templating to remove whitespace before and after the endif control
segments, which lead to invalid ini style config files. Correct the
white space removal directives.
Closes-Bug: 1949608
Change-Id: Id6634fb3825b9d6b9e003f8c477e21d798dfe046
* 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: I3f5192f348164fdaed124519704fcb2f00871ab8
Add update-trilio action which can be run after a Trilio
upgrade.
Trilio sometimes updates packages in package repositiories that
require DB migrations or config file changes. Since these package
updates are not applied by the charm as they would be by changing the
openstack-origin or triliovault-pkg-source the charm has no event to
react to to automatically perform the post package upgrade actions.
This change adds an action `update-trilio` which can
be run to apply the changes.
Change-Id: I4c12bc9ff9b8b20a5ddc16a040f70b87f4cac30b
Remove the experimental status from the S3 options. Update the
README documentation to provide information on configuring the
appropriate backend to use for NFS or S3 storage.
This change is mainly copied from the corresponding change to
trilio-wlm ( I7836754529a8b5d067a86077e1e004fa2f53ec6e ). Bug
1933809 *1 is tracking the consolidation of duplicate code.
*1 https://bugs.launchpad.net/charm-trilio-data-mover/+bug/1933809
Change-Id: I868240fee4f5e767c9dac2d41ddc128bc307e4ae
This patch allows an s3 backend to be used to store Trilio artefacts.
Connection auth and endpoint are set via the s3 charm config options.
To use an s3 backend the backup-target-type should be set to
'experimental-s3'.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/516
Change-Id: I1dab03d25e6e583d88d69ea15e5b5119151c9676
There was a new relation introduced in the 4.1 release.
All the Trilio charm READMEs will need to be updated for
MySQL8 soon.
Change-Id: Iaf06af27a1cef780983ec75e4c136c6aaf2a00ea
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: Ia30cf05bbbdfa28fbb87d0b0435c33a540796c99
The linked bug indicates that the charm fails to install on Focal which
needs python3. This fix ensures that the Rocky onwards charm support is
python3.
Change-Id: I54db2f0f2f5b720b9d6e3695f0d84947c667aab5
Closes-Bug: #1914452
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I86d0ce48deb00c9274471e7df6c6849d3c25f065
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: I98b6c3292cf1e5f694882ce3c77b81e24062d519
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
* 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: If0a78625ddbe903d45b7cd017bb0d00da110e4c6
Rebuild to pickup changes to charms.openstack classes to support
use of nfs-shares configuration options containing multiple
comma separated nfs shares.
Update description of action to reflect this change.
Change-Id: If03387fa06ecf546a640b20415497800f7ef7d9d
Closes-Bug: 1894817
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/410
Ensure that a change to the triliovault-pkg-source option forces
an upgrade of any previously installed packages.
Refactor codebase to use TrilioVault plugin classes from
charms.openstack.
Change-Id: I0c1e7880bb08997275efa28c7cc53a1e3a573259
Closes-Bug: 1879904
- 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: I96cecf7c9ef7efe02bcfa03054ec485f13f06a70
Mark python version option as deprecated as it has no effect.
Drop Trilio package source from bundles.
Set correct default in charm for trilio-pkg-source.
Change-Id: I0ca5bb22938db99dd4c486807aafe59ce4b7e5f5
The data-mover service requires direct access to the ceph cluster
in order to snapshot volumes etc.
Add support for the ceph-client interface; configuration and keyring
are writen to a charm specific location to avoid interference with
any other ceph services that may be deployed in the same unit.
TrilioVault requires some slight specialised ceph keyring and conf
placement - see code for notes.
Change-Id: If6998d668fc3e7bd164069ba01a157e136133706
Liam Young