Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-28 Thread Jay Pipes
On 12/24/2015 02:30 PM, Clint Byrum wrote: This is entirely philosophical, but we should think about when it is appropriate to adopt which mode of operation. There are basically two ways being discussed: 1) Fail fast. 2) Retry forever. Fail fast pros- Immediate feedback for problems, no

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-28 Thread Fox, Kevin M
: Re: [openstack-dev] Nova scheduler startup when database is not available On 12/24/2015 02:30 PM, Clint Byrum wrote: > This is entirely philosophical, but we should think about when it is > appropriate to adopt which mode of operation. > > There are basically two ways being disc

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-28 Thread Jay Pipes
On 12/23/2015 08:35 PM, Morgan Fainberg wrote: On Wed, Dec 23, 2015 at 10:32 AM, Jay Pipes > wrote: On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: I've been looking into the startup constraints involved when launching

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-28 Thread Clint Byrum
Excerpts from Jay Pipes's message of 2015-12-28 09:45:39 -0800: > On 12/24/2015 02:30 PM, Clint Byrum wrote: > > This is entirely philosophical, but we should think about when it is > > appropriate to adopt which mode of operation. > > > > There are basically two ways being discussed: > > > > 1)

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-24 Thread Clint Byrum
Excerpts from Jay Pipes's message of 2015-12-23 10:32:27 -0800: > On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: > > I've been looking into the startup constraints involved when launching > > Nova services with systemd using Type=notify (which causes systemd to > > wait for an explicit

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-24 Thread Sylvain Bauza
Le 24/12/2015 02:35, Morgan Fainberg a écrit : On Wed, Dec 23, 2015 at 10:32 AM, Jay Pipes > wrote: On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: I've been looking into the startup constraints involved when

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-23 Thread Jay Pipes
On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: I've been looking into the startup constraints involved when launching Nova services with systemd using Type=notify (which causes systemd to wait for an explicit notification from the service before considering it to be "started". Some

[openstack-dev] Nova scheduler startup when database is not available

2015-12-23 Thread Lars Kellogg-Stedman
I've been looking into the startup constraints involved when launching Nova services with systemd using Type=notify (which causes systemd to wait for an explicit notification from the service before considering it to be "started". Some services (e.g., nova-conductor) will happily "start" even if

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-23 Thread Mike Bayer
On 12/23/2015 01:32 PM, Jay Pipes wrote: > On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: >> I've been looking into the startup constraints involved when launching >> Nova services with systemd using Type=notify (which causes systemd to >> wait for an explicit notification from the service

Re: [openstack-dev] Nova scheduler startup when database is not available

2015-12-23 Thread Morgan Fainberg
On Wed, Dec 23, 2015 at 10:32 AM, Jay Pipes wrote: > On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote: > >> I've been looking into the startup constraints involved when launching >> Nova services with systemd using Type=notify (which causes systemd to >> wait for an