I've been chasing quite a few bugs in the TripleO automated bring-up
lately that have to do with failures because either there are no valid
hosts ready to have servers scheduled, or there are hosts listed and
enabled, but they can't bind to the network because for whatever reason
the L2 agent has
On 12/12/2013 12:02 PM, Clint Byrum wrote:
I've been chasing quite a few bugs in the TripleO automated bring-up
lately that have to do with failures because either there are no valid
hosts ready to have servers scheduled, or there are hosts listed and
enabled, but they can't bind to the
On 12/12/2013 11:02 AM, Clint Byrum wrote:
So I'm asking, is there a standard way to determine whether or not a
nova-compute is definitely ready to have things scheduled on it? This
can be via an API, or even by observing something on the nova-compute
host itself. I just need a definitive
On 12/12/13 17:19, Chris Friesen wrote:
On 12/12/2013 11:02 AM, Clint Byrum wrote:
So I'm asking, is there a standard way to determine whether or not a
nova-compute is definitely ready to have things scheduled on it? This
can be via an API, or even by observing something on the nova-compute
Excerpts from Chris Friesen's message of 2013-12-12 09:19:42 -0800:
On 12/12/2013 11:02 AM, Clint Byrum wrote:
So I'm asking, is there a standard way to determine whether or not a
nova-compute is definitely ready to have things scheduled on it? This
can be via an API, or even by observing
Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800:
On 12/12/2013 12:02 PM, Clint Byrum wrote:
I've been chasing quite a few bugs in the TripleO automated bring-up
lately that have to do with failures because either there are no valid
hosts ready to have servers scheduled,
On 12/12/2013 12:36 PM, Clint Byrum wrote:
Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800:
On 12/12/2013 12:02 PM, Clint Byrum wrote:
I've been chasing quite a few bugs in the TripleO automated bring-up
lately that have to do with failures because either there are no valid
On Dec 12, 2013, at 11:44 AM, Jay Pipes jaypi...@gmail.com wrote:
On 12/12/2013 12:36 PM, Clint Byrum wrote:
Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800:
On 12/12/2013 12:02 PM, Clint Byrum wrote:
I've been chasing quite a few bugs in the TripleO automated bring-up
On 12/12/2013 12:53 PM, Kyle Mestery wrote:
On Dec 12, 2013, at 11:44 AM, Jay Pipes jaypi...@gmail.com wrote:
On 12/12/2013 12:36 PM, Clint Byrum wrote:
Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800:
On 12/12/2013 12:02 PM, Clint Byrum wrote:
I've been chasing quite a
Excerpts from Kyle Mestery's message of 2013-12-12 09:53:57 -0800:
On Dec 12, 2013, at 11:44 AM, Jay Pipes jaypi...@gmail.com wrote:
On 12/12/2013 12:36 PM, Clint Byrum wrote:
Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800:
On 12/12/2013 12:02 PM, Clint Byrum wrote:
On 12/12/2013 12:35 PM, Clint Byrum wrote:
Excerpts from Chris Friesen's message of 2013-12-12 09:19:42 -0800:
On 12/12/2013 11:02 AM, Clint Byrum wrote:
So I'm asking, is there a standard way to determine whether or not a
nova-compute is definitely ready to have things scheduled on it? This
On 12/12/2013 01:36 PM, Clint Byrum wrote:
Excerpts from Kyle Mestery's message of 2013-12-12 09:53:57 -0800:
On Dec 12, 2013, at 11:44 AM, Jay Pipes jaypi...@gmail.com wrote:
On 12/12/2013 12:36 PM, Clint Byrum wrote:
Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800:
On
Maybe time to revive something like:
https://review.openstack.org/#/c/12759/
From experience, all sites (and those internal to yahoo) provide a /status
(or equivalent) that is used for all sorts of things (from basic
load-balancing up/down) to other things like actually introspecting the
state
13 matches
Mail list logo
