Open Stack

I wish everything was so simple in distributed systems (like openstack) but there are real boundaries and limits to doing something like a "kill -9" correctly while retaining the consistency of the resources in your cloud (any inconsistency costs someone $$$).

Sent from my really tiny device...

> On Oct 28, 2013, at 8:11 AM, "Chris Friesen" <chris.friesen at windriver.com> wrote:
> 
> Yes, exactly this.  If my compute node crashes and is unavailable I should still be able to delete the instance.
> 
> Heck, I should be able to create an instance and delete it while it's still in the building stage.
> 
> It's like a "kill -9" in posix...the underlying system should clean up underneath it.  And yes, just like the process kill there may be side effects like corrupt file systems on cinder volumes.
> 
> Chris
> 
>> On 10/28/2013 08:10 AM, Day, Phil wrote:
>> I’d disagree that that – from a user perspective they should always be
>> able to delete an Instance regardless of its state, and the delete
>> should always work (or at least always appear to work to the user so
>> that it no longer counts against their quota, and they are no longer
>> charged for it)
>> 
>> *From:*Abhishek Lahiri [mailto:aviostack at gmail.com]
>> *Sent:* 26 October 2013 17:10
>> *To:* OpenStack Development Mailing List
>> *Cc:* OpenStack Development Mailing List
>> *Subject:* Re: [openstack-dev] [nova] Thoughs please on how to address a
>> problem with mutliple deletes leading to a nova-compute thread pool problem
>> 
>> Deletes should only be allowed when the vm is in a power off state. This
>> will allow consistent state transition.
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev