Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7CB1E991 for ; Thu, 17 Jan 2013 09:58:03 +0000 (UTC) Received: (qmail 69353 invoked by uid 500); 17 Jan 2013 09:58:03 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 69180 invoked by uid 500); 17 Jan 2013 09:58:03 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 69168 invoked by uid 99); 17 Jan 2013 09:58:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 09:58:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of stan.ieugen@gmail.com designates 209.85.212.180 as permitted sender) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 09:57:58 +0000 Received: by mail-wi0-f180.google.com with SMTP id hj13so2115400wib.7 for ; Thu, 17 Jan 2013 01:57:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=gzZkX45W9OyqMqZxbi13biKO5ncL+UUVxWhdrUFHyds=; b=I5oPx+fH49EsiKIBjFlXnqhdQmeJ4OzYWZmhZPvTq32VrjNQkOJdGoh/UoS31drOiV 5K2PCk3V8b7TsprmRcj77j5Xxqr3nii4z+nzV/BBjfjtKhZu9cnsxR5g+UY/ZS8tK8RJ v9vZcx3SO2StXmqe1TOwMPoc8830papC8I/bXVuBZcuvV7q5XwLSI1tR6NIekiGkQ1j4 JXSl++WcGXSdxmVOwsBES3H0UfMw0rGKY+2Uhn5UjeYEjN8gpfU+AEPssHhcfy9ndRR4 DJ5uYZw4LNVrcaZLtM/Q6hCvgVHHZISOYmssjNtxtvd/OJXfu9QswjBQYlScT4mINrvI aqBA== MIME-Version: 1.0 X-Received: by 10.194.108.229 with SMTP id hn5mr7274175wjb.8.1358416657624; Thu, 17 Jan 2013 01:57:37 -0800 (PST) Received: by 10.216.2.83 with HTTP; Thu, 17 Jan 2013 01:57:37 -0800 (PST) In-Reply-To: References: Date: Thu, 17 Jan 2013 11:57:37 +0200 Message-ID: Subject: Re: force expunge From: Ioan Eugen Stan To: cloudstack-users@incubator.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org 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 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 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 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 >>> 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