openstack team mailing list archive

[Naveed Massjouni <naveedm9@xxxxxxxxx>]

Awesome authors indeed! Thanks.
-Naveed

On Thu, Jan 26, 2012 at 6:31 PM, Vishvananda Ishaya
<vishvananda@xxxxxxxxx> wrote:
> looks like the awesome authors of devstack are now handling this for you:
>
> https://github.com/openstack-dev/devstack/blob/master/stack.sh#L931
>
> So the instances are destroyed on the second run.
>
> Vish
>
> On Jan 26, 2012, at 3:14 PM, Naveed Massjouni wrote:
>
> That's easy enough, thanks. Sometimes I forget to delete all my
> instances before blowing away screen and running ./stack.sh. Just
> curious, what happens to all those vm's? Am I building up an army of
> zombie vm's that are taking up resources? Or do they disappear into
> the ether?
> -Naveed
>
> On Thu, Jan 26, 2012 at 5:53 PM, Vishvananda Ishaya
> <vishvananda@xxxxxxxxx> wrote:
>
> There is another thread on this, but the quick answer is;
>
> killall screen
>
> ./stack.sh
>
>
> You should generally make sure that you have terminated all instances and
> deleted all volumes in advance or you could run into issues.  It is always
> safer to start from a clean vm, but the above should work in most cases
>
>
> If you would also like to grab new code:
>
> killall screen
>
> cd devstack
>
> git pull
>
> RECLONE=yes ./stack.sh
>
>
> Vish
>
>
> On Jan 26, 2012, at 12:58 PM, Naveed Massjouni wrote:
>
>
> I would like to know the proper way to blow away a stack and create a
>
> fresh stack with devstack. Currently, I hit ctrl-c and ctrl-d a bunch
>
> of times to close all the windows in the screen session. Then I run
>
> ./stack.sh again. Is this the best way? Is this documented somewhere?
>
> Thanks,
>
> Naveed
>
>
> _______________________________________________
>
> Mailing list: https://launchpad.net/~openstack
>
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>
> Unsubscribe : https://launchpad.net/~openstack
>
> More help   : https://help.launchpad.net/ListHelp
>
>
>