Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3FAB718320 for ; Thu, 15 Oct 2015 15:49:31 +0000 (UTC) Received: (qmail 78335 invoked by uid 500); 15 Oct 2015 15:49:27 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 78284 invoked by uid 500); 15 Oct 2015 15:49:27 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 78267 invoked by uid 99); 15 Oct 2015 15:49:27 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2015 15:49:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 17632C084E for ; Thu, 15 Oct 2015 15:49:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.198 X-Spam-Level: ** X-Spam-Status: No, score=2.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Vk5pOdOVox7M for ; Thu, 15 Oct 2015 15:49:26 +0000 (UTC) Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com [209.85.220.175]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id D72C2439E9 for ; Thu, 15 Oct 2015 15:49:25 +0000 (UTC) Received: by qkas79 with SMTP id s79so40926234qka.0 for ; Thu, 15 Oct 2015 08:49:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rbIFFte/ugLZOkVKoJpFo52fK/6d1410q8XEaNiUENs=; b=ML620pcmtx8oZaVGAF45n44BrDIo4n1m8rlMu8d8bS0BuGejoYg06C9bvo8CQClx5O uD2ZTEEscUre+q9sQwP9uZtxvQr3lkIVKH0uhej3Bl0NxTH3StPsyRRRsrrIdrBLnmiv rqW1BemmU4hiVGml1dashASd0aBDZRC/fNC2Oas6Bvb27h7kOo929GGEDjSPbdwX1Dau K23nOJXPLU7hjUPmpGbXCvWnBYUNqYQuYFz2slNIObGioZbNwM8NpB+nE0RG54N2OIhn NngNttRiKy3C1phlj5Rl9+syCSCBubqKhNuGbk45U+S+LAVKYQVSvFx+7F7XQ5CHo+CF 9naw== MIME-Version: 1.0 X-Received: by 10.55.195.71 with SMTP id a68mr13141126qkj.15.1444924165617; Thu, 15 Oct 2015 08:49:25 -0700 (PDT) Received: by 10.140.17.68 with HTTP; Thu, 15 Oct 2015 08:49:25 -0700 (PDT) In-Reply-To: References: <561EC00B.50201@gmail.com> Date: Thu, 15 Oct 2015 17:49:25 +0200 Message-ID: Subject: Re: List disk offerings cmd From: Wei ZHOU To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=001a113c92169e7e8f0522269fc2 --001a113c92169e7e8f0522269fc2 Content-Type: text/plain; charset=UTF-8 Patrick, My mistake. There is not a way to enable/disable a service/disk offering (yes for network offerings). It might be useful for some users. You can create a ticket on JIRA. -Wei 2015-10-15 15:40 GMT+02:00 Patrick Dube : > Thanks Wei. But is there actually a way to disable/enable disk offerings? > There seems to be nothing via the API. > > If there isn't, I will create an issue and work on it. > > Cheers, > > Patrick > > On Thu, Oct 15, 2015 at 2:40 AM Wei ZHOU wrote: > > > Hi Patrick, > > > > If you remove/expunge a resource (instance,volume,offering, tempalte, > etc), > > it means the resource will not be used any more. > > Hence, cloudstack will not list this kind of resources in the API > response. > > > > If you want to disable offering temporarily, you can disable/enable it. > If > > the offerings is removed by mistake, you need to modify the database > > manually: Update disk_offering set removed=NULL where id=XXX > > for vms, you can destroy/recover them. > > > > -Wei > > > > 2015-10-14 23:05 GMT+02:00 Patrick Dube : > > > > > Thanks ilya. Yeah, I can still see them in the db, but I was wondering > if > > > they weren't exposed for a specific reason. I think it would be useful > to > > > either be able to see deleted disk/service offerings or to be able to > > > disable them, like with network offerings, and filter them that way. > > > Opinions? > > > > > > Cheers, > > > > > > Patrick > > > > > > > > > On Wed, Oct 14, 2015 at 4:50 PM ilya > > wrote: > > > > > > > Patrick > > > > > > > > As you may know, nothing is deleted in cloudstack db (for the most > > > > part), hence records are still accessible via direct db query. > > > > > > > > I'm not aware of any API call that would show Deleted disk offerings, > > > > though, but should not be too hard to implement.. > > > > > > > > Regards > > > > ilya > > > > > > > > On 10/14/15 10:41 AM, Patrick Dube wrote: > > > > > Is there any way to list all disk offerings (via the API), even > those > > > > that > > > > > were deleted? > > > > > If not, is there any particular reason why? > > > > > > > > > > Thanks, > > > > > > > > > > Patrick > > > > > > > > > > > > > > > --001a113c92169e7e8f0522269fc2--