This is available in all supported Cinder branches.
Change-Id: I988d599425d4733e5e40e8b9126454ebcfdcdf0c
Signed-off-by: Eric Harney <eharney@redhat.com>
Replace debian-bookworm with debian-trixie for the base job in order
to use a newer version of qemu that has patch [0] that addresses an
issue where test_boot_cloned_encrypted_volume fails when run on a
fast machine.
The default python in debain-trixie is Python 3.13, which is a supported
python version for the Gazpacho development cycle [1].
Also, updated the package prereq file for some necessary packages that
aren't included by default in trixie.
[0] https://lists.gnu.org/archive/html/qemu-devel/2025-01/msg01071.html
[1] https://governance.openstack.org/tc/reference/runtimes/2026.1.html
Related-bug: #2121941
Change-Id: I0db46ae97e61186f7bc2e0c940cf27278d742146
Signed-off-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
Tentacle is the last Ceph release [1] and this patch bumps
devstack-plugin-ceph to deploy this version.
[1] https://docs.ceph.com/en/tentacle/
Change-Id: Id303b97d4ad6bcf1da9f0c39a113bba24a60481e
Signed-off-by: Francesco Pantano <fpantano@redhat.com>
This change updates the nodeset for the ceph jobs to use
debian 12 to avoid ubuntu packaging issues on noble.
Related-Bug: #2116852
Change-Id: I5f119862ed240c71cdd817466df5764271df656b
Signed-off-by: Sean Mooney <work@seanmooney.info>
It is possible to setup one way or two way replication between pools.
rbd-mirror daemon is responsible for pulling image updates from the
remote peer cluster and applying them to the image within the local
cluster. This patch allows to enable this daemon as part of the
deployment, but the actual configuration between sites remains out
of scope for the deployment script.
This work aims to support [1].
[1] https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/948293
Change-Id: Id1a66c244b9be33b6df63e6504500c77d59a1b9d
Signed-off-by: Francesco Pantano <fpantano@redhat.com>
Ceph Squid was released on 2024-09-26. It's the
latest supported release, and EOL is planned in
2026-09. [1]
This roughly corresponds to the support timeline
for OpenStack 2025.1 ("Epoxy") and 2025.2 ("Flamingo")[2].
We could plan to change the default version tested
again when Ceph's Tentacle release arrives (estimated: late '25).
[1] https://docs.ceph.com/en/latest/releases/#active-releases
[2] https://releases.openstack.org/
Depends-On: I11a3c8f573e5540840a23459d698197a9c3a8f4c
Change-Id: If6009392198b1d9e9c35e4fabae344a550a07796
Still seeing oom-killer trigger in Cinder Ceph CI
jobs with ceph-osd being a top memory consumer.
It appears to default to trying to use 4GB of memory,
change this to 2GB to see if it helps.
Increases the job timeout to 3h for a bit more
headroom since jobs are regularly taking more than 2h
to complete.
Change-Id: I71a46a452914256f36299623a29ed7eebf8e61d2
When the Ceph ingress IP is not set, devstack is currently failing
to install with CephFS NFS. When it attempts to create the NFS
cluster, it fails because the VIP value is not set.
The VIP should be the same as the ceph ingress IP, but it is only
being set in the manila job definitions, so if you don't provide
it in the local.conf file manually, the value will be empty.
This change fixes it by defaulting the ceph ingress IP to the
host IP in case it wasn't provided in the local.conf.
Change-Id: Ib2db0faa5381da9e3d391ff0f887eb92dff9c295
Signed-off-by: Carlos Eduardo <ces.eduardo98@gmail.com>
This mode of deployment isn't supported by the Ceph
community, and was always a chimera that we were
feeding/maintaining.
Ceph's tool of choice to bootstrap and install a ceph
cluster is by using the Ceph Orchestrator (via the
cephadm tool).
We're also cleaning up the old/unused and poorly tested
"CONTAINERIZED_CEPH". When using ceph orchestrator,
ceph daemons are run within podman containers on the
devstack host.
Change-Id: I5f75cb829383d7acd536e24c70cc4418d93c13bc
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
These tests are failing at the moment; I noticed
they're being skipped elsewhere pending investigation.
Change-Id: Ib0328fe8d69204c1213c2c07bc1648bcfd236a31
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
We're going to drop support for installing ceph
via packages or container images. This repository
will only support cephadm going forward.
Change-Id: Ic4f4c151854424ad9e5e01f9618a94508e977d51
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Manila supports using a standalone NFS-Ganesha server
as well as a ceph orchestrator deployed NFS-Ganesha cluster
("ceph nfs service"). We've only ever allowed using
ceph orch deployed NFS with ceph orch deployed clusters
through this devstack plugin. With this change,
the plugin can optionally deploy a standalone
NFS-Ganesha service with a ceph orch deployed
ceph cluster. This will greatly simplify testing when we sunset
the package based installation/deployment of ceph.
Depends-On: I2198eee3892b2bb0eb835ec66e21b708152b33a9
Change-Id: If983bb5d5a5fc0c16c1cead84b5fa30ea961d21b
Implements: bp/cephadm-deploy
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
During the devstack setup, if you have set `CEPHADM_DEPLOY=True`,
we are not considering cephfsnative as the default driver, even
though it was the expected behavior before.
If we do not set this flag and it is not set in the local.conf,
the devstack setup fails.
That is fixed by enforcing `cephfsnative` as the default value for
the Ceph backend. In case users want to deploy devstack with Ceph
NFS, they can continue using the same workflow (setting
`MANILA_CEPH_DRIVER=cephfsnfs`).
Change-Id: I51660fa2466fff873f2230e683661b53874bf862
Signed-off-by: Carlos Eduardo <ces.eduardo98@gmail.com>
devstack-plugin-ceph-tempest-py3 is timeout consistently and
one of the reason can be it run the slow marked tests also.
All integrated jobs runs slow marked tests in separate job.
Skipping the slow tests in this job and devstack-plugin-ceph-multinode-tempest-py3
already cover them so no need to add a separate job.
Change-Id: I0a80a107dfbe9690bc173a8a2ed872de53dcf995
Fixes ingress deamon, for 18.0+ Ceph versions
by setting correct VIP.
Ingress daemon was added in Caracal, and when
backported to Bobcat encountered CI failures.
In this patch I've added verbose MDS logging
capabilities, and fixed the failures that were
present in Bobcat stable CI, cephfs-nfs-cephadm
job. History is in patchset 908940.
Resubmititng starting at master to backport
to stable branches in the correct order.
Depends-On: I5b7fd5b2b557203189c25fa2a988d790e7fda3eb
Change-Id: Ia1671de5c770d1cf5a3cd58e05fe5204f5bbc3c6
This job is non-voting against the manila repos currently.
We've observed sporadic failures in data intensive scenario
tests. There are a number of manila tests that write a few
gigabytes of data onto mounted shares. While we've tried
to optimize test concurrency and the kind of data being written,
sometimes, things seem to fall over and a test case runs into
a generic I/O error. So maybe more work is necessary to
get this job to be stable; but that work may not be in this
devstack plugin repository.
Change-Id: Id89f161ba6dd5b5fbb5b82042a3e94c92797a881
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
download.ceph.com used to maintain named versions of ceph
releases, which were hardlinked folders corresponding
to the latest minor release from a stable branch; we've noticed
that these folders can be deleted. Let's instead look for
cephadm under the corresponding numeric release tag folder.
Change-Id: Ic39b48fb2dd48f47d5b3c6165e4f4c6b1c47cc7d
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
For releases older than reef (e.g., octopus, pacific), packages are not
always available under the el9 subdirectory.
This patch introduces a switch case to make sure we're able to match the
right version of cephadm.
Change-Id: I0ee37b832f1ea47961528f074f2d42492b0ac755
Ceph release tags adhere to a versioning scheme x.y.z [1], where:
- x = major release number (e.g.: quincy is 17, reef is 18)
- y = 1 or 2, where 1 is an release candidate, and 2 is a stable release
- z = patch/updates
We shouldn't hardcode a patch version in the default container
image we're fetching in our jobs, unless absolutely necessary
for some bugfix/feature that we rely on.
[1] https://docs.ceph.com/en/latest/releases/general/
Related-Bug: #1989273
Change-Id: Iea541d2edefc871bcac2d965997c88462fcbe521
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Reverting a bad rebase to fix cephadm binary source
Also adds catatonit to rpms file to fix CI issues
Change-Id: Ie1b1dc0ef2508eae38ae7954fb0bb62653780644
Add podman ceph-common and jq as part of preinstall dependency.
Add REMOTE_CEPH capabilities to CEPHADM deployment.
Removed set_min_client only if cinder is enabled, this should be set
in any case.
Get FSID from ceph.conf in /etc/ceph to avoid unnecessary override.
Part of an effort to test multinode deployments with cephadm.
Needed-By: I5162815b66d3f3e8cf8c1e246b61b0ea06c1a270
Change-Id: I84249ae268dfe00a112c67e5170b679acb318a25
Following up on the usage of inclusive jargon [1] and to ensure
consistency in code, there is a need to replace deprecated term
tempest_test_blacklist with a new term tempest_test_exclude_list.
[1] https://review.opendev.org/c/openstack/tempest/+/768583
Change-Id: I1692876c9d42b3ac857fdb61dcdc2caa61cd349d
We are about to drop Fedora support as the latest image in upstream
has been transitioned to EOL. Centos 9 Stream has evolved as replacement
platform for new features. Review which deletes nodeset from devstack:
https://review.opendev.org/c/openstack/devstack/+/885467
Change-Id: I3b1bece44b9ad2f4bf4d822f261b141ddf3031fd
The current code only adds the service secret to libvirt when Ceph has
been enabled in Nova, but it should also be enabled if it has only been
enabled in Cinder.
This patch changes devstack/plugin.sh to write the service secret to
libvirt whenever Nova or Cinder is using Ceph.
This would be the counterpart of the code we already have in
_undefine_virsh_secret where we are already checking if it's enabled in
either of the services to remove the secret.
Change-Id: I1067d52b7a435fcef7996eea6479d598be842dca
Affects only the package based install script.
Pacific is going to be EOL'ed soon [1], we do not
expect folks to deploy the next version of OpenStack
(2023.2/Bobcat) with Ceph Pacific; moreover, all our
CI jobs are using Quincy by default, and the cephadm
script uses quincy by default.
[1] https://docs.ceph.com/en/latest/releases/index.html#active-releases
Change-Id: I6abdb1241e99d76bcee35b331e1059c4fe48296b
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
On the multinode job we need to enable validation like the base job
and also disable block migration for live migration that we get from
our parent job.
Change-Id: I076527536e19f7fa2c0cd177bebb1df22db51a0a
