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-13 Thread Thomas Goirand
On 12/05/2014 03:04 AM, Gaudenz Steinlin wrote: > OK I tested keystone on unstable now and this works as it should. It's > definitely an improvement over the current unit file which does not work > at all. I did not go down the route to do a full openstack installation > but I also installed nova a

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-12 Thread Thomas Goirand
On 12/06/2014 12:14 AM, Gaudenz Steinlin wrote: > The init system (every init system, not just systemd) would then start > the nova-compute service with this command: > nova-compute --config /etc/openstack/openstack.conf --config > /etc/nova/nova.conf --config /etc/nova/nova-compute.conf After a

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-05 Thread Thomas Goirand
On 12/05/2014 03:04 AM, Gaudenz Steinlin wrote: > OK I tested keystone on unstable now and this works as it should. It's > definitely an improvement over the current unit file which does not work > at all. Cool, thanks for your time! > One thing I noticed is that all services are disabled by defa

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: [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: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created

2014-11-27 Thread Thomas Goirand
On 11/27/2014 10:07 AM, Mikaël Cluseau wrote: > 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

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-26 Thread Thomas Goirand
On 11/24/2014 04:48 PM, Gaudenz Steinlin wrote: > Thomas Goirand writes: > >> On 11/24/2014 01:52 AM, Gaudenz Steinlin wrote: >>> Why do you set PIDFile at all? IMO pidfiles are unnecessary when the >>> daemons managed by systemd run in the foreground and thus there is no >>> need for a pidfile a