This addresses the questions:
- Why doesn't the charm let me use an erasure coded pool as the default?
- How do I use the secondary erasure coded pool once it is configured?
Change-Id: Ia885ce41043a4cb04a6d92993474c44e9b994c55
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: I4b117272f68a27732809d0dddc31ac9cf69c60d9
- update bundles to include UCA pocket tests
- update test configuration
- update metadata to include lunar
- update snapcraft to allow run-on for lunar
Change-Id: I351ec2e549ef9ce1b25d4a57643c5f2e5e151d66
Add 22.10 run-on base and add kinetic to metadata.yaml.
Additional changes:
* change CHARMCRAFT_* vars to CRAFT_* and add entrypoint
* pin tox < 4.0.0 for now
* switch to charmcraft pack
* add standard bindep.txt
* switch charm-tools to 2.8.4 to remove py310 ruamel requirement
* use charmcraft_channel 2.0/stable
Change-Id: I549e8382e4c079eb9eefec13f2a72e994e2b86f0
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
Change-Id: I1bbdebb22fcd6cac4ceae74d90d70a8d94f3c769
* 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
* drop bluestore model alias to simplify osci.yaml
Change-Id: I1df6bb74fd96d934aa97cce18307a3227b165882
For the case in container, it is not necessary to install ntp.
For the bare metal, we now expect operators to use a subordinate
ntp charm instead. Therefore, we remove ntp installation in
ceph-fs.
Closes-Bug: #1935013
Change-Id: I48f1a6a1ee6153bbc86cc9acf9302d8eb9d7db43
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
hisute-wallaby test is disabled (moved to dev) due to [1].
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I108ce673e31500d1e3c2b2d9f0530bae6ece486a
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I89267c171f245fbc92ad67545e97d99f48f798e2
* 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
* Manual fix to build.lock to work around bug [1]
[1] https://github.com/juju/charm-tools/issues/603
Change-Id: I6be25d404436647a19e18231ccd0985dd49bb858
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ide508d37e11b37d2c4d19942fbeef9655390fae9
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: Ife8c24cefab36793f2e3f0b08e6a828504d4380f
This updates the README for erasure coded
Ceph pools for the case of CephFS.
The new text should be as similar as possible
for all the charms that support configuration
options for EC pools. See the below review for
the first of these charms whose README has been
updated.
https://review.opendev.org/#/c/749824/
Other minor improvements.
Change-Id: Ic6543e3241048591818358c972eadecd6ceab50c
Ceph Bluestore Compression is a post-deploy configurable option
and allowing to update the broker request is required. Drop code
that gates the sending of pool broker request, the original issue
has been fixed in the interface code and it is now safe to call
multiple times.
Fold Erasure Coding test into regular bundles from Mimic and up
to allow testing both EC and BlueStore Compression at the same
time without test bundle explosion.
Unpin flake8
Change-Id: I9b529e61a8832a62f4db12cab8f352d468c8a3ad
When using erasure coding three pools are needed. One metadata
pool which is replicated, one default data pool which is replicated
and one erasure coded pool.
Add an additional ec-pool-weight option to allow the erasure coded
pool usage to be modelled within the deployment.
The consumer of the share will need to use xattrs to ensure that
the hierarchy of directories and files are stored in EC pool while
leaving the default replicated data pool for file backtraces.
Depends-On: Ib19e545fc676fa9e986f3fddcfb92cf99e778a3f
Depends-On: I48348ab2b6c8952c5e22008a074a60c1f35be952
Change-Id: I1af386d5e1d031f2f0387c7381af683f948172d9
Closes-Bug: #1895154
Update descriptions and align metadata-pool configuration option
with codebase. Metadata pools are used by CephFS for both replicated
and erasure-coded data pools.
Change-Id: Iee6ee64e7bd672f9932037bf91670d8f59083aa4
Add support for erasure coded pools.
1) Pool name of replicated and EC pools can now be set via
pool-name config option.
2) Weight of replicated and EC pools can now be set via
ceph-pool-weight config option.
3) Charm no longer uses initialize_mds from the ceph-mds
interface. This moves the charm inline with ceph-client
charms where the charm explicitly creates the pools they
need.
4) Metadata pool name format is preserved with an underscore
rather than a hyphen.
Change-Id: I97641c6daeeb2a1a65b081201772c89f6a7f539c
The ceph-mds interface has been updated to work in the same way
as the ceph-client interface. This requires some minor updates to
the charm so pools are requested when the ceph cluster is first
available and the service is configured once the pools have been
confirmed to exist.
Depends-On: I9f438bb678da1b69d8161390aad2cf58907bc1b5
Change-Id: I83148f73c7f0465ecfadaa9df92e4a53e30813de
This improvement is part of a wave of polish
in preparation for the launch of the Ceph product.
Add Configuration, Actions, and Bugs sections.
In config.yaml, modernise example values for 'source'
and use consistent words with the ceph-osd, ceph-mon,
and ceph-fs charms.
Change-Id: Iaf45df89db4b471c6379e09881758dae4b723783
- 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: I9912fe43e6db71ed81e47175f9f790ed550c9c31
Move helpers as-is from reactive handler module to charm class.
Set default of ``source`` configuration option to 'distro' to be
in line with other reactive charms and the expectations of the
``openstack.utils.get_source_and_pgp_key`` function.
Unpin flake8.
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/313
Depends-On: I6fbde855ba8f83ef5e265bd5b5dfb0d01eae830b
Change-Id: I2d8e8b244db935673406d2cce9ef34e7252cb50b
Closes-Bug: #1879072
This adds bundles for:
* bionic-ussuri
* focal-ussuri
And adds a force option of the focal-ussuri bundle as it is not yet
officially supported by Juju.
Change-Id: Ic0f82df6f1dc76cdba21f23e8b04ff9e12f32181
Samuel Walladge