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: Ic2ed85c2c4465179cf3a7c7e7d78c16a699147a1
Add new config option: `scheduler-default-filters`.
This is unset by default, so manila retains the default value for
scheduler_default_filters.
Closes-Bug: #1998200
Change-Id: I82eddf8f54d954f6d930265ec8612398f4cc90a0
When the remote plugin was developed it made the assumption that the
`enabled_share_backends` included the remote backends. This assumption
is wrong, and it should only contain the locally defined drivers; i.e.
ones that have a [driver] section in the manila.conf file. The cephfsnfs
driver doesn't have a local configuration as the share-server is runs on
the manila-ganesha unit and so shouldn't be local.
This patch splits the config in local/remote and then uses the local and
remote config in the correct places.
Closes-Bug: #2012457
Change-Id: I436452208aaeaf08d1655da4fccbd7a89549b404
* 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: I57df3d1f01049a9b4b12c970cf83abffb7b4ed64
To ensure that it works, this change also updates the functional
test bundles to include manila-netapp and manila-netapp-dhss in
the gate.
This change also picks up a drive-by change to fix a tox
dependency change.
Closes-Bug: #1996962
Change-Id: Ic5a2b2fcced129220b70a16539b41813b0feb3be
* 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
Depends-On: https://review.opendev.org/c/openstack/charm-manila/+/858765
Change-Id: I4cae0a313230a8617beac36a2dbfe0c019c5e0de
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.
Switch to using a binary build which allows pip's dependency
resolution to work.
This patch also updates manila.py to align with
charm-interface-keystone commit
9ad5cade97e14b672ac859d34040353c3a40c7aa.
This patch also drops the impish bundle.
Change-Id: Ib3aea3fb26aa3e6282989b2758bdf4913ef58c28
As per the bug report, add config-flag paramiter to config.yaml to add desired
options to the DEFAULT section of manila.conf
Closes-Bug: #1952320
Change-Id: If1a314119c59212f4fb885ef9af411d1ab05b1e2
- 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: Icced48103310c873574b47d2900066bd05c5a2dd
This is a work-around for a package bug. The policy.json file
was deprecated in the wallaby release in favor of using a
policy.yaml file to override the default policy in code.
Therefore the policy.json file is not needed.
Closes-Bug: #1952763
Change-Id: I4b424869a23f28e8eb66ef6bfc42603b863afc40
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: I7e48c6515f48e77a4045bc5f899e8ca963e1671a
* 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: Iaea730e035c4671d83fa65c7d74a2b31f59680cd
Changes project_domain_id and user_domain_id to *_name in manila-plugin endpoint
Closes-Bug: #1911424
Change-Id: Ia289d4899e3e802197853a61e8e36b7ad87d0fd8
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ia3cc21f2c3165fe013cf311ba15348245cb1a6af
* 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: I2a20459c7aee21bc1c2df77b1868b65029329982
At the moment, the enabled backends' names list is written in the config file
as a space-separated list.
When using multi-backend, the current Manila charm crashes because the config
`enabled_share_backends` needs to a comma-separated list of backend names instead:
https://docs.openstack.org/manila/victoria/admin/shared-file-systems-multi-backend.html
Change-Id: I881d12ad4cea044e232b9f997a4dfc4b2f38e9c8
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I623bdfe6496404b4c10d51d398fdd6564078115d
When tls settings change, the endpoints need to be updated on the
identity-service relation in order for keystone to update the service
catalog with the new endpoints. This change follows the behavior of
other reactive charms and performs this update within the handlers
code.
Func-Test-Pr: https://github.com/openstack-charmers/zaza/pull/424
Change-Id: I201fc382f044111e6f28a13c64a55e2f79c1d6aa
Closes-Bug: #1901589
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: I21ce3edf5412e22970c0f34d6c28d179352add19
- 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
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/355
Change-Id: Ia2fbdac07df0a430741be69d02942c899bb89e45
The charm currently provides the ``manila-api.conf`` in the
pike templates folder, but attempts to use it for all
supported releases.
Move the template to the earliest supported release to avoid
hook errors.
Change-Id: I16135e6535f8cabe9caa6693a6ee8a228dcb4b65
Closes-Bug: #1879337
An indirect requirement of enabling HA with Manila
is migrating from directly using WSGI to using
mod-wsgi with Apache.
Change-Id: I1f501283db3db1338d47a89a7688cf5035d08a7a
Closes-Bug: #1867358
Use default_update_peers which will publish admin, internal and public
addresses to peers.
Change-Id: Ic9b25431c1f5574bad855731d0210a9dbedacfc7
Closes-Bug: #1858132
Alex Kavanagh