Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-14 Thread Mikaël Cluseau
On 12/13/2014 05:29 AM, Thomas Goirand wrote: Let's work on this after the freeze, indeed! Great, I'll help then :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-05 Thread Mikaël Cluseau
Hi, On 12/06/2014 03:14 AM, Gaudenz Steinlin wrote: I'm not sure if I understand your concerns. I think it is the difference between * having one distribution-managed configuration file per daemon (like in /usr/share//.conf) containing the default log file, meaning 58 configuration fil

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-04 Thread Mikaël Cluseau
On 12/05/2014 06:04 AM, Gaudenz Steinlin wrote: One thing I noticed is that all services are disabled by default even though they were configured through debconf and should be ready to use. Is this intentional as an off by default behavior or is this a bug. How is this handled with sysvinit? Fo

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-04 Thread Mikaël Cluseau
On 12/05/2014 01:01 AM, Thomas Goirand wrote: Then later we can test that... though the build is for Wheezy, so I'm not sure if that's so relevant. Is systemd working well in Wheezy? I've been using systemd in wheezy for over a year now. It's working well, especially if you use wheezy-backport

Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-03 Thread Mikaël Cluseau
On 12/04/2014 03:52 AM, Thomas Goirand wrote: Let's see what the release team says. Thanks Thomas. Aside from this, I took a look at how they did in Fedora. Here is their unit file: [Unit] Description=OpenStack Identity Service (code-named Keystone) After=syslog.target network.target [Servi

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-02 Thread Mikaël Cluseau
stack-pkg-tools and used to rebuild test packages? I think this needs thorough testing if it's to be proposed for jessie. As I said at the beginning, yes. Here the complete patch for the immediate review: ± git log -1 --stat -p commit 8b3217905de88f2037f0bbc6eac46dca776c8f48 Author: Mik

Bug#770706: [PKG-Openstack-devel] Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-12-01 Thread Mikaël Cluseau
Hi, On 12/02/2014 01:52 AM, Gaudenz Steinlin wrote: So only new changes which fix (RC) bugs are allowed and the changes should be as minimal as possible to fix the bug. Since I already posted patches for a minimal set of code changes with a minimal set of feature changes, I can now move on mo

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-30 Thread Mikaël Cluseau
Hi Gaudenz, thank you for your comments. As I tried to explain first, I wanted to make the smallest possible step that could possibly work because, from what I understood, once we get in the freeze phase, users can take the current state as a feature (ie, on the python-django-pyscss package,

Bug#770706: Info received ([PKG-Openstack-devel] Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created)

2014-11-29 Thread Mikaël Cluseau
Sorry, I forgot to change the WorkingDirectory to fully comply with the start-stop-daemon line. The patch for the unit file should be: diff --git a/init-template/pkgos-gen-systemd-unit b/init-template/pkgos-gen-systemd-unit index b97e2a9..8700b6c 100755 --- a/init-template/pkgos-gen-systemd-un

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-29 Thread Mikaël Cluseau
Hi all, I tried to minimize the changes to get close to a unit file in the systemd spirit, while still using on the init-script to keep same features as before. The patch below reflect the following actions: 1. don't auto-create the /var/*/${PROJECT_NAME} folder if not root, as it will fail

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-27 Thread Mikaël Cluseau
On 11/27/2014 06:08 PM, Gaudenz Steinlin wrote: I think we can agree that *if* we implement the systemd fully *then* pid-files become useless. As you say it would be the best way, I would like to (try to) spend a significant time to implement the systemd way this week-end. Just... I don't want t

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-26 Thread Mikaël Cluseau
The quick-fix of tmpfiles.d is what I did first and will (probably) work. But, if I assemble this On 11/27/2014 11:10 AM, Thomas Goirand wrote: >Do we agree that with systemd the pid-file logic becomes useless Unfortunately, no, I don't agree. Not with the (poor) way we've designed things in o

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-26 Thread Mikaël Cluseau
On 11/27/2014 09:23 AM, Stig Sandbeck Mathisen wrote: Note: The proposed solution in that bug will not work for services sharing the same runtime directory. The services will delete each others runtime directory and pid files. Do we agree that with systemd the pid-file logic becomes useless, an

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-23 Thread Mikaël Cluseau
On 24/11/2014 10:20, Thomas Goirand wrote: Yes it is. And that's a general issue with all OpenStack packages in Sid/Jessie right now. We need to fix all of this before the 5th of December deadline. I will try to help. I didn't knew if the intention was to keep a "simple" compatibility for sys

Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-23 Thread Mikaël Cluseau
Hi, isn't it a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767711 ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767711: openstack-pkg-tools: systemd start fails a fresh install

2014-11-10 Thread Mikaël Cluseau
Hi Thomas, On 11/11/2014 10:36 AM, Thomas Goirand wrote: I have uploaded version 19 of openstack-pkg-tools, which fixes the issue. The way to fix it is to do: RuntimeDirectory=${PROJECT_NAME} as per the systemd manpages, and per what the guys in #debian-systemd adviced. Systemd is awesome: o

Bug#767711: openstack-pkg-tools: systemd start fails a fresh install

2014-11-01 Thread Mikaël Cluseau
On 11/02/2014 12:54 PM, Mikael Cluseau wrote: +RuntimeDirectory=/var/run/${PROJECT_NAME} This is not ok, systemd says its invalid. It needs to be : +RuntimeDirectory=/run/${PROJECT_NAME} -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Tr