cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ioan Eugen Stan <stan.ieu...@gmail.com>
Subject Re: force expunge
Date Thu, 17 Jan 2013 09:57:37 GMT
Thank you Chris,

Please accept my sincerest apologies for this mistake. My eyes fooled me.

Best regards,

On Thu, Jan 17, 2013 at 11:55 AM, Ioan Eugen Stan <stan.ieugen@gmail.com> wrote:
> Hello Nick,
>
> Thanks for the advice. I think it might work. There is a problem
> though, jclouds does not support Projects API yet as it lacks support
> for some CloudStack 3.x features. I'll go for a hack and sleep until
> the machines are expunged and look for a way to bump jclouds
> CloudStack support. I would love to work on jclouds support for
> CloudStack.
>
> Cheers,
>
> On Thu, Jan 17, 2013 at 2:22 AM, Chris Sears <chris.x.sears@sungard.com> wrote:
>> I'm not sure if this would work, but you could try creating the VMs and
>> networks as part of a project, and then deleting the project.
>>
>>
>> On Wed, Jan 16, 2013 at 5:16 PM, Ioan Eugen Stan <stan.ieugen@gmail.com>wrote:
>>
>>> Hello Nick,
>>>
>>> Thanks for the quick answer. I was hoping for a miracle :) but I guess
>>> there is no forceExpunge flag that I can set. So the only thing left
>>> to do is wait for the expunge job to finish. I wonder if there are any
>>> plans to implement such a feature.
>>>
>>> Cheers,
>>>
>>> On Thu, Jan 17, 2013 at 12:07 AM, Nik Martin <nik.martin@nfinausa.com>
>>> wrote:
>>> > There is a global setting in the CS UI that sets the time for the expunge
>>> > task to run. it runs on a schedule. Set the VM expunge timeout to 60 and
>>> it
>>> > will rn once a minute.
>>> >
>>> > Regards,
>>> >
>>> > Nik
>>> >
>>> > Nik Martin
>>> > +1.251.243.0043 x1003
>>> > Relentless Reliability
>>> >
>>> >
>>> >
>>> > On Wed, 16 Jan 2013, Ioan Eugen Stan wrote:
>>> >
>>> >> Hello,
>>> >>
>>> >> I'm working on the CloudStack driver for Axembrl Provisionr [1] and
>>> >> I'm having some issues with expunge. I can't delete a network before
>>> >> all VM's that use it are destroyed and expunged. Expunging takes
>>> >> forever and the delete network API call is executed before so I end
>>> >> not cleaning up ok.
>>> >>
>>> >> In a live test [2], I'm creating via jclouds API a network, register
a
>>> >> ssh key and create a VM. Then I destroy them in reverse, but I don't
>>> >> wait for the VM to be expunged and this makes impossible the network
>>> >> deletion. I'm leaking networks, which is not nice. Instructions to run
>>> >> the live tests are here [3]
>>> >>
>>> >> What is the best strategy in this case? Is there any way that I can
>>> >> speed up/force expunging - API call, cloud configuration?
>>> >>
>>> >> Thanks,
>>> >>
>>> >> [1] https://github.com/axemblr/axemblr-provisionr/
>>> >> [2]
>>> >>
>>> https://github.com/ieugen/axemblr-provisionr/blob/run-instance/providers/cloudstack/src/test/java/com/axemblr/provisionr/cloudstack/activities/CreateGatewayLiveTest.java
>>> >> [3] end of README: https://github.com/ieugen/axemblr-provisionr
>>> >> --
>>> >> Ioan Eugen Stan / CTO / http://axemblr.com
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Ioan Eugen Stan / CTO / http://axemblr.com
>>>
>>>
>
>
>
> --
> Ioan Eugen Stan / CTO / http://axemblr.com



-- 
Ioan Eugen Stan / CTO / http://axemblr.com

Mime
View raw message