On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch wrote:
A few inline comments and a general point
How do we handle scenarios like volumes when we have a per-component
janitor rather than a single co-ordinator ?
To be clean,
1. nova should shutdown the instance
2. nova should
Wondering if heat should be performing this orchestration.
Would provide for a more pluggable front end to the action set.
-matt
On Feb 25, 2015 2:37 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell tim.b...@cern.ch wrote:
A few inline comments and a
On 2/2/15, 15:41, Morgan Fainberg morgan.fainb...@gmail.com wrote:
On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com)
wrote:
On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg
morgan.fainb...@gmail.com wrote:
I think the simple answer is yes. We (keystone) should emit
On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
I think the simple answer is yes. We (keystone) should emit
notifications. And yes other projects should listen.
The only thing really in discussion should be:
1: soft delete or hard delete? Does the service
On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com) wrote:
On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
I think the simple answer is yes. We (keystone) should emit notifications.
And yes other projects should listen.
The only thing really
On Mon, Feb 02, 2015 at 11:46:53AM -0600, Matt Riedemann wrote:
This came up in the operators mailing list back in June [1] but given the
subject probably didn't get much attention.
Basically there is a really old bug [2] from Grizzly that is still a problem
and affects multiple projects. A
I think the simple answer is yes. We (keystone) should emit notifications.
And yes other projects should listen.
The only thing really in discussion should be:
1: soft delete or hard delete? Does the service mark it as orphaned, or just
delete (leave this to nova, cinder, etc to discuss)
2:
