Open Stack

Thanks, Jay. I agree with your comments about Essex. The problem is that 
I have cleaned up after a number of operational problems in a cluster 
that has been up for 3 months. It is hard to reproduce these problems 
when the mean time to failure is so long, and real investigation can be 
dangerous when there are real users. One thing I have done in past 
projects is to have an email address where people are encouraged to 
report 'incidents' like this. Investigation and creation of a proper bug 
report can be dangerous and/or a lot of work but we could encourage 
operators of real systems to just email these problems even if they 
don't have time to investigate. That could help find problems that are 
appearing in the field but don't get picked up in unit tests and such. I 
will file a bug about the bad state.


  -David




On 3/20/2012 11:29 AM, Jay Pipes wrote:
> Also, it seems that deleted instances are never removed from the
>> database. Is that a bug?
>
> No, it's not a bug. But was is a bug is ACTIVE status instances that 
> are deleted.
>
> Another issue right now is that Essex has moved on and much of the 
> code involved in this stuff is substantially different in trunk. We 
> first need to identify whether this issue exists in trunk today, and 
> if so, patch trunk and then backport a patch to Diablo...
>
> Best,
> -jay
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp