[Bug 2100625] Re: [SRU] ceph 17.2.9

[Matthew Ruffell]

Hi everyone,

I was talking to Dan Hill today, and we noticed that ceph-exporter exists in
plucky and questing and not in noble or jammy:

$ rmadison ceph-exporter
 ceph-exporter | 19.2.1-0ubuntu1 | plucky/universe   | amd64, arm64, ppc64el, riscv64, s390x
 ceph-exporter | 19.2.1-0ubuntu3 | questing/universe | amd64, arm64, ppc64el, riscv64, s390x
 
It seems that this package was introduced in oracular:

https://launchpad.net/ubuntu/+source/ceph/19.2.0~is.really.19.1.0-0ubuntu1

    - d/p/patch-out-exporter.patch: Drop, enable exporter.
    - d/control,ceph-exporter.install: Enable ceph-exporter binary
      package.
    - d/p/ceph-exporter-systemd.patch: Cherry pick commit for ceph-
      exporter systemd configuration.

Dan Hill and I talked about the different exporters in use over the years
including their pros and cons.

* Digital ocean implementation (external), can overrun the MGR causing outages 
to the manager, can cause cluster instability, not ideal.
* Then was moved inside the manager, in the mgr-module prometheus. Solved 
manager overload issues. However, When there is control plane failure, metrics 
stop working, no good.
* Then was moved? to a separate binary / systemd service called ceph-exporter
which when run, disables the mgr-module prometheus. Best solution.

I talked this over with Dan H, and also Christopher Halse Rogers during our SRU
shift. We both came to the same conclusion that ceph-exporter should probably
be fully enabled with proper debian packaging and a systemd service if we are
going to make it work properly.

So, here is what we are going to do.

For noble 19.2.3 and jammy 17.2.9, we will add the debian/control entries for
ceph-exporter, add d/ceph-exporter.install and then likely look at if
d/p/ceph-exporter-systemd.patch is necessary.

Christopher and I rejected 17.2.9 for the time being, and we will enable the
exporter properly in a new upload.

Dan Hill and I will work on the packaging for 19.2.3 tomorrow morning. From
there, lets try and get this uploaded soon.

Luciano, if you don't want this to happen or think it is a bad idea, let us
know.

Thanks,
Matthew

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/2100625

Title:
  [SRU] ceph 17.2.9

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive yoga series:
  Triaged
Status in ceph package in Ubuntu:
  Invalid
Status in ceph source package in Focal:
  Invalid
Status in ceph source package in Jammy:
  In Progress

Bug description:
  [Impact]
  This release fixes several bugs. We would like to make sure all of our users have access to these improvements.

  The update contains the following package updates:

     * ceph 17.2.9
     * Race condition prevention when printing Inode in ll_sync_inode (by Ponnuvel Palaniyappan)

  [Test Case]
  The following SRU process was followed:

  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  OpenStack-Updates/

  In order to avoid regression of existing users, the OpenStack team
  will run their continuous integration test against the packages that
  are in -proposed. A successful run of all available tests will be
  required before the proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary
  of the executed tests. The OpenStack team members will not mark
  ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the aforementioned tests will be attached to this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2100625/+subscriptions