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 D812817E1F for ; Thu, 15 Oct 2015 13:56:42 +0000 (UTC) Received: (qmail 75266 invoked by uid 500); 15 Oct 2015 13:56:42 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 75208 invoked by uid 500); 15 Oct 2015 13:56:42 -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 75182 invoked by uid 99); 15 Oct 2015 13:56:42 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2015 13:56:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AD6FA1809D7 for ; Thu, 15 Oct 2015 13:56:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.148 X-Spam-Level: *** X-Spam-Status: No, score=3.148 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id mERGhSxgXs4O for ; Thu, 15 Oct 2015 13:56:28 +0000 (UTC) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 356B22AB5D for ; Thu, 15 Oct 2015 13:40:47 +0000 (UTC) Received: by ioii196 with SMTP id i196so89480491ioi.3 for ; Thu, 15 Oct 2015 06:40:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=rCU3aWfeIfeoBGmNqJgktTAQ3bquyT9em7Oz6DAwFBk=; b=IlOG/G4gQ/wVTOrcHm03HJlr5edoIp5q8Whw3JxLQsE/K0ld4Ynyj1uobJarUdlIlz IF5+rGjvmfXjf3xvNHwFis+AJ3nImxXN1C72LP3Ja2hRRALL4x6/JPnajWh0snfX/jf9 Z6OHoZaindipNyrqSWzm3XshkUzXGawdtO9g2YFKnMz8kEOMxUArUK7tDmPwHO3sLCJp 9ewSycM6qbaRsSd830c9PSp9aZuN5rx7ennp1SANCUol2IF4Qht7VQMkJvLQ6SSY8zM1 bvIghAcSlLB6ocxtJL28cCGu6IrVRF9bH7Oy0ZduTWWUkX/3gEydvfhSaCmWvC/eg6xe kszA== X-Received: by 10.107.129.218 with SMTP id l87mr7228527ioi.181.1444916446169; Thu, 15 Oct 2015 06:40:46 -0700 (PDT) MIME-Version: 1.0 References: <561EC00B.50201@gmail.com> In-Reply-To: From: Patrick Dube Date: Thu, 15 Oct 2015 13:40:36 +0000 Message-ID: Subject: Re: List disk offerings cmd To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=001a113f933681113c052224d3f4 --001a113f933681113c052224d3f4 Content-Type: text/plain; charset=UTF-8 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 > > > > > > > > > > --001a113f933681113c052224d3f4--