switch swift to use systemd init

Patch attached

The attachment "lp1827340.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

I don't see the point in enabling Upstart (or sysv init.d jobs) at this point - unless I really don't understand how this will be used Upstart jobs won't do anything on modern releases of Ubuntu.

Instead perhaps using similar systemd jobs that Debian has -https://packages.debian.org/sid/all/swift-container/filelist

I agree that it reveals a deeper issue. Would you suggest to remove all old Upstart / System V files (for all Swift services) and replace them with Systemd files?

Yea, I'd be for going systemd unit files only. They will always take precedence on 18.04+, so might as well only provide them.

Hi Bryan,

I'm attaching an updated patch, however, as this is the first time I'm creating a patch for ubuntu package, I am not sure whether everything is correct. Please have a look and let me know if anything has to be changed.

Regards

Tytus

Hi Tytus,

I did a once over and it looks good to me. I'm far from an expert though. I think they use git-ubuntu for this, but I'd check with one of the maintainers.

Thanks,
Bryan

Hi Mathew,

Is there any chance to move this forward?

Thanks

Hello,

generally, changes like this should be done in Debian first, however the 'cloud' packages can sometimes be special.

@corey.bryant, do you have an opinion on changing the swift sysv init scripts over to normal systemd services (meaning, @tkurek doing the work with me assisting him)? If you're ok with that, would you prefer it go into Debian first, or just carry it in Ubuntu (I assume Debian first, but just checking).

@tkurek, assuming Corey doesn't object to the systemd service change in general, and prefers it in Debian, there are generally two ways to get changes into Debian, either open a bug with the debdiff attached, or open a Debian Salsa merge request.

The Debian swift bug trackers shows no bugs currently:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=swift
but you could open one with the debdiff fairly easily, by using the 'submittodebian' script from the ubuntu-dev-tools package. Its manpage is not super descriptive, but essentially you just need to run the script from the package source you want to patch. If you have questions about its usage let me know.

Alternately (or additionaly) you can try opening a salsa merge request:
https://salsa.debian.org/openstack-team/services/swift
you will need to create a 'guest' salsa account, and after that it's basically the same process as github/gitlab.

I've subscribed to this bug so let me know if I can help with any further steps in the process.

Hi Tytus and Dan,

Thanks for the patches Tytus. Always appreciate contributions!

Generally for the core openstack packages they don't follow the normal sync from debian flow for a number of reasons and the packages tend to differ quite a bit.

The swift package in Debian has already moved to systemd though, and they went with a generated approach. To see what they did, pull-debian-source swift and take a look at the debian/*init.in files and debian/rules override_dh_installinit, override_dh_installsystemd.

I'll need to dig in deeper to understand if one approach is any better than the other.

I'd like to make the switch one way or the other, but I'm not sure that I want to do it at this point in the Focal cycle. I would prefer early G cycle.

Thanks,
Corey

Dan / Corey,

Thank you very much for looking into it. I don't think it's a priority any more, but still worth finalising and merging. Unfortunately, I have no more time to drive it, so I will have to leave it in your hands.

Thank you

Tytus

> The swift package in Debian has already moved to systemd though, and they
> went with a generated approach. To see what they did, pull-debian-source
> swift and take a look at the debian/*init.in files and debian/rules
> override_dh_installinit, override_dh_installsystemd.

oh wow, it looks like Debian has included a script to generate systemd service files since 2016:

https://salsa.debian.org/openstack-team/services/swift/-/commits/debian/ussuri/debian/gen-init

that generator approach isn't one I have seen before.

In any case, thanks for looking at this in the G cycle Corey!

By the way, just in the mean time there is an init script for swift-container-sharder in Ussuri.

I'm going to change the topic of this bug to focus on switch to systemd init.

This bug was fixed in the package swift - 2.25.0-0ubuntu3

---------------
swift (2.25.0-0ubuntu3) groovy; urgency=medium

  * d/t/swift-daemons: Update to give systemd units time to restart.

 -- Chris MacNaughton <email address hidden> Thu, 25 Jun 2020 11:30:03 +0000