openstack/devstack-plugin-ceph - devstack-plugin-ceph - OpenDev: Free Software Needs Free Tools

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>

This reverts commit 863a01b032.
Partial revert only for the pin to focal, leaves the broken other jobs
commented out.
Update paste-deploy workaround to be used always.
Add qemu-block-extra and podman deps to the debs list.
Running on the newer ceph and distro causes some quite different
performance characteristics that cause tests that used to pass to fail
more often. This includes some performance optimizations to help
reduce the memory footprint, as well as depends on changes to
tempest tests to improve the reliability of those tests by enabling
validation via SSH.
This also moves the cephadm job to be the voting/gating job as that
seems to be the clear consensus about "the future" of how we deploy
ceph for testing.
Depends-On: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/881764
Co-Authored-By: Dan Smith <dms@danplanet.com>
Change-Id: I899822fec863f43cd6c58b25cf4688c6a3ac1e9b

The cephfs-nfs job was turned off [1] for perma-failing.
This commit adds the original non-voting job back into the
check queue and fixes some installation issues:
1) use ceph "quincy" release: Ceph Pacific's end of life
 is 2023年06月01日 [2]. The manila community thinks deployers
 are more likely to use quincy with the 2023.2 (bobcat)
 release of OpenStack.
2) run the job with centos-stream-9: There are no packages
 currently available for Jammy Jellyfish on download.ceph.com [3].
 The OS shouldn't really matter for this CI job that is meant to
 test feature functionality provided by manila. At this time, we'd
 like to stick with builds provided by the ceph community instead
 of the distro since it may take a while to get bugfixes into distro
 builds.
3) The install script uses "nfs-ganesha" builds for ubuntu and
 centos hosted by the nfs-ganesha community [4]. We will not rely on
 the ceph community to provide the latest builds for
 nfs-ganesha any longer.
This commit also cleans up the unnecessary condition in the
ceph script file pertaining to configuring ceph packages for
Jammy Jellyfish. This step wasn't doing anything.
Ubuntu packages don't work at the moment and that requires some more
investigation.
[1] Id2ae61979505de5efb47ce90a2bac8aac2fc5484
[2] https://docs.ceph.com/en/latest/releases/
[3] https://www.spinics.net/lists/ceph-users/msg74312.html
[4] https://download.nfs-ganesha.org/
Change-Id: I40dfecfbbe21b2f4b3e4efd903980b5b146c4202
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

As per the community wide goal to migrate the CI/CD from
Ubuntu Focal to Ubuntu jammy, we need to merge the devstack, tox base
jobs to jammy on Nov 18. But ceph jobs are failing on Ubuntu Jammy.
To move ahead to merge the base job patches we need to pin the
ceph jobs nodeset to Focal until this is fixed for Jammy.
Since the devstack-plugin-ceph-tempest-py3 is currently permanently
failing, although this patch is a no-op, make it non-voting. Also don't
run 100% failing non-voting jobs until they are fixed.
Needed-By: https://review.opendev.org/c/openstack/devstack/+/860795
Related-bug: #1996628
Change-Id: Id2ae61979505de5efb47ce90a2bac8aac2fc5484

Ubuntu 22.04 does provide Ceph Quincy (17.2.*) out of the box, thus
there's no urgent need to have comunity repos and we can simply rely
on distro-provided ones. We can remove logic once community publish
Ceph packages for Ubuntu Jammy (22.04).
Change-Id: I169971ef77f11ceb01a5db87441051dcb33555f7

CephFS driver supports snapshots, therefore the snapshot_support
extra spec for the cephfsnfstype we create should be True.
Change-Id: I97b58697f27824a97cfd31ed21d79916b9e270cc

As part of change I1826f2970528928a31b32a664013380e38bbd7c9
we added a configuration option to the manila cephfs nfs driver
when deployed using cephadm.
We also need this option set here to get the m-shr service
to pick the right helper when deploying with DevStack
Change-Id: If99714e07f4b75c76db29a660ad8d1e93f7055e5

We should be using a standard port for NFS
Most frequently used ports for NFS are 111 and 2049.
Change-Id: I78503c7780feebdc51ab32973b5cb7b8cea30272

Latest Ceph stable version is Quincy. This patch set
sets Quincy as default for the cephadm deploy.
This change won't have an impact in the script being
currently used in our CI.
Change-Id: I2d87ec0e93853cd0852944b30a87f6127f491550

The configuration that we are using by default that
sets pg_num and pgp_num values in bootstrap_ceph
breaks devstack-plugin-ceph when using the latest Ceph version (quincy).
This patch sets removes the config for pg_num and pgp_num,
so we delegate to Ceph the pools autoscaling.
Closes-Bug: #1983107
Change-Id: Iecd949ef2258ae8a6ded596219bb993aeff20de5

UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I71bfcf0576eda9f72d963c4f5d92464c5a04734e

It's not a required configuration item; and its not required
with cephadm deployed NFS-Ganesha daemon/s.
Change-Id: I54380f1cb905dfa5ab287ba423561aa75bc1d2f4
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Add the option to deploy the Ceph cluster
with the cephadm tool.
Depends-On: I799521f008123b8e42b2021c1c11d374b834bec3
Co-Authored-By: Francesco Pantano <fpantano@redhat.com>
Change-Id: Id2a704b136b9e47b7b88ef586282cb5d0f754cf1

This patch adds a new VAR for when the user wants to set the minimum
client version used in a Manila/Glance/Nova/Cinder test job in addition
to using devstack.
A new configuration option, CEPH_MIN_ CLIENT _VERSION, has been
introduced to specify a Ceph-minium client version that allows proper
handling when deleting images and snapshots with dependencies, etc. The
default value is null.
Co-Author-By: Sofia Enriquez <lsofia.enriquez@gmail.com>
Change-Id: Id8e581893ee4b373b268acc7c59b670985cedc2f

The parent jobs of the basic tempest jobs defined here enabled
horizon since the merge of tempest-horizon into tempest (see
Id2ced856a41548a0b49e594ee5fed6ed28785f24).
But horizon is not really needed here, as the default list of
tests does not incldue any horizon test. Disabling it helps
freeing up a bit of resources for the job and also helps
the ongoing effort of testing FIPS, which would otherwise
require a patched django at this point.
Change-Id: I05ea7f675aafb85eb54427ca95167b4c8f0eabdf

Recently cinder has utilized clone v2 support of Ceph for its
RBD backend, since then if you attempt to delete an image from
glance that has a dependent volume, all future uses of that
image will fail in error state. Despite the fact that image
itself is still inside of Ceph/Glance. This issue is reproducible
if you are using ceph client version greater than 'luminous'
To resolve this issue glance RBD driver now checks whether original
image has any dependency before deleting/removing it's snapshot and
returns 409 response if it has any dependency. To check this
dependency glance osd needs 'read' access to cinder and nova
side RBD pool.
This change allows glance keyring/osd a read access on cinder and nova
side RBD pool.
Related-Bug: #1954883
Change-Id: I2e6221e6de23920998bb5f32b2323704b3c89f74

this change ensure that python3-logutils is removed so that
that it can be installed by pip later.
Before today in passing build, there were no python3-logutils pulled by neutron deps so
it was not installed or tried to uninstall so all good
- https://zuul.openstack.org/build/590c5996ca1b402486bfe1c7e1d08535/log/job-output.txt
But from today (10th Dec), python3-logutils pulled by neutron deps and failure started
- https://zuul.opendev.org/t/openstack/build/722c6caf8e454849b897a43bcf617dd2/log/job-output.txt#9419
The root cause of why this issue started happening today is not known. May be its
pecan===1.4.1 ? I8ee467bbb363f428a005f92554812bfdae95881a making it install but there
is no change for logutils as deps in pecan previous version 1.3.3 also[1]). Or it may
be cpeh/ubuntu packaging.
But it is clear that python3-logutils is coming from somewhere and causing gate blocker
in Nova gate, let's remove it and later we can find the root cause if anyone need this
package for their ceph job.
[1] https://github.com/pecan/pecan/blob/1.3.3/requirements.txt#L5
Closes-bug: #1954427
Change-Id: Icb63649b252fd6eb229adeae454b5ec3c6b79cad

Few URLs from some ganesha repositories were not corresponding
to actual valid URLs, where packages could be searched in
the repository.
These broken URLs have now been fixed.
Change-Id: If27b488cfec29731b74e7db774c4811b0e34c14e

As devstack-plugin-ceph is branched, we moved stable branch
jobs definition in their respective branch
- https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/786308
- https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/786309
- https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/786310
- https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/786311
But we did not cleanup the master version of job definition so that we
do not need to do it for future stable branches. When stable/xena is cut
from master the ./.zuul.yaml version of jobs in stable/xena has the stable
branches variant which is being picked up by zuul for stable branch gate
instead of their own version defined in their stable branch.
- https://zuul.opendev.org/t/openstack/build/bc088154e50440fe9a2cacf52426748a/log/zuul-info/inventory.yaml#241
And it started failing ceph job when ceph version was update for master and
same is being picked by stable branch testin so due to above branch matching
logic.
To avoid this in future when we will have stable/yoga or so we need to cleanup
this in master. Master repo will only keep the master version of jobs and no
stable branch jobs.
Other stable/rocky and older jobs will be moved to stable/stein so that we have
them there if anyone cut the branch.
Closes-Bug: #1945358
Change-Id: I7061f8d1491ff957452c9c777e40186a4e9c324e

Move tempest py3 jobs to latest released stable Ceph, which is
Pacific.
Change-Id: I6cd5424f023d2a895f8ed259d21944490bc1de5f

When we deploy devstack, we need to initialize the RBD pool.
Not doing so means that functionality like rbd trash purge
scheduling will not work correctly.
Ref: https://docs.ceph.com/en/latest/start/quick-rbd/
Change-Id: I5b0b3b83fb7ef805929fdcd106a5c8a988b05ec4

Remove the need of using FORCE_CEPH_INSTALL=yes
for CentOS8 Stream
Change-Id: I76c2c3805a8f606dca69a0f12aca226680fda573

Seems a trace from older code. It doesn't make
much sense to allow all Fedora versions that
matches f[0-9][0-9] and then check for specific
Fedora versions in the following lines.
Remove this check and just allow some specific
versions
Change-Id: Ie14a453f96689f574f1b388ab8f6e5467a59b7f7

Change-Id: I66b8412e61cec0b77ea63e4551ba3f082892bd38

This will change the version of Ceph from Octopus to Pacific and,
with it, the version of Ganesha from v3.3 to v3.5 which is the
version shipped into the Ceph Pacific container.
Change-Id: I1b31ef9dd13e1d56284f8d9f8be03e3fee0eb0a7

devstack-plugin-ceph is now branched;
these test hooks were maintained to
support legacy style zuul jobs; All
manila zuul jobs were ported to native
zuulv3 style jobs in the victoria cycle
and no longer rely on these files;
so we can remove these test hook files
from all three releases (victoria, wallaby,
xena/trunk).
Change-Id: I81e838bf13cb32503ee2b8becd06daea5ab01dfa
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

This changeset adds a config option (TEST_MASTER)
to toggle testing with the current Ceph master.
The builds are retrieved from Shaman, which is the
platform used by the Ceph community to submit their
latest builds.
The main goal of this change is to use this on our CI
and be able to catch bugs in OpenStack services that use
Ceph as a backend more quickly. Because of this, the
required non-voting job is also added.
Change-Id: Ibe26f89e7be3061cdb7acb441727efb2c396e29e

The patch bumps min version of tox to 3.18.0 python in order to
replace tox's whitelist_externals by allowlist_externals option:
https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020年07月23日
Change-Id: I4bc8f70dd208e39c41d68bb82cf54ccaea9f6ebf

devstack-plugin-ceph is now branched and each branch
will maintain the respective branch specific code and
testing.
Change-Id: I9edf3ff59055e1ce6cd1630ea8e747ff5b498f02

The risk of breaking the gates by forgetting to run the jobs
against the old branches is too high
(it has happened with https://review.opendev.org/778960/ for example)
Related-Bug: #1921897
Change-Id: Ieab4e0ee482604802485cdf573c31e3c373a8553

In some jobs, we run tests that use "rbd map".
On older kernels, this will not work if newer
RBD features are used. (Specifically, fast-diff
on bionic.)
On older distros, enable fewer features by default.
Closes-Bug: #1921897
Change-Id: Iff1c5210b0279379eb9612b206bdf456dd6f132e

Change-Id: I59c8692ed7dab123c5bfce9e7e28646b4800846f

This change introduces a multinode ceph job based on
tempest-multinode-full-py3 to be used to provide live migration and
other multinode coverage initially in the openstack/nova project.
As this job uses ceph for both Nova ephemeral
([libvirt]/imagebackend=rbd) and Cinder volume storage the live block
migration tests are skipped.
Change-Id: I9ffdff44a3ad42ebdf26ab72e24dfe3b12b1ef8b

This change stops configure_ceph_nova from creating the vms pool when
CEPH_REMOTE=true as this suggests that it has already been created by
the controller that has CEPH_REMOTE=false set.
Change-Id: Iaad67025a23bf29e29011c6e78662692af2b564a

The typical Cinder deployment should have
more than just "layering" enabled.
Enable fast-diff, which requires exclusive-lock
and object-map.
Previously, there was code that tried to enable
exclusive-lock when CEPH_ISCSI is enabled, but this
code would not work reliably, since it was doing
addition instead of bitwise-or. Just remove it
since exclusive-lock will be enabled by default.
Change-Id: Idad98cfebf5e3b265316f2b6a3c201b472faa32c

Update the list of tested stable branches (excluding stein which is EM).
The nodesets for the stable branches are now pinned because
their testing environment are well defined and won't change.
Also, remove the -py3 suffix: those jobs are all -py3 based
(the suffix was mostly requires in the transitional time
between py2 and py3).
Change-Id: I48f8574960df51fc47f80fa17091fd13ec71aa99

Consume packages from download.ceph.com for ceph octopus
Our focal fossa based CI jobs are getting octopus from
ubuntu ppas instead of getting the packages from
download.ceph.com.
This happens because, even though we were defaulting to
nautilus, ubuntu got the later version available
(in this case, the packages in ubuntu ppas).
Also, remove CEPH_STABLE_RELEASE env var, unify to CEPH_RELEASE
Stable branches CI versioning is done in the jobs definition now
Change-Id: I1edd5a50079f325fa143a7e0d51b3aa3bb5ed45d