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 B737D1023F for ; Sat, 15 Nov 2014 00:52:28 +0000 (UTC) Received: (qmail 67770 invoked by uid 500); 15 Nov 2014 00:52:23 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 67717 invoked by uid 500); 15 Nov 2014 00:52:23 -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 67706 invoked by uid 99); 15 Nov 2014 00:52:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Nov 2014 00:52:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mike.tutkowski@solidfire.com designates 209.85.218.42 as permitted sender) Received: from [209.85.218.42] (HELO mail-oi0-f42.google.com) (209.85.218.42) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Nov 2014 00:51:57 +0000 Received: by mail-oi0-f42.google.com with SMTP id v63so3621500oia.15 for ; Fri, 14 Nov 2014 16:50:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=P28kEc+s39aOEjHBHaxQQKaR0VHm++Dj8J/KwR2CzmE=; b=e8egcYkG9cC9aD9m54S4y+YAIxvc6NEEgB1ASUkr0kyGsEQw4qRUlkW84GNdHR4t+L /8l2aYbIJy7PZ6iUK3Kk342rDk7A3ofBufM82eJWQBFWL3CdltkjrYz9m7gxYg3ik4PS xXEbx4AqthoLBFS3nGiEkcxa4NmGaMPHyqxaFwWA19+yLQQYt8GrbiArdp/MRuvJxCyH fzhmS1LnTz7EBu9ia9MPsmHfH4++uaHRjKWIPnChZxMqnPi9dLpwP5q/6KXJukUHgWu3 Le/Lrly/5SnYVC6TiK10jushLNDJ+ErEsvbkzCmrcO4Ya5sWJ+ZYFREU7j0+EZ+UFyeQ szYQ== X-Gm-Message-State: ALoCoQnhzQLi5DdLEYw50Iy0XR3ElexatxYPnt+5drpW8HWzvdmU05jcJUm+BHo0pG+AnluVsMVE MIME-Version: 1.0 X-Received: by 10.182.142.10 with SMTP id rs10mr10645848obb.36.1416012625473; Fri, 14 Nov 2014 16:50:25 -0800 (PST) Received: by 10.182.24.106 with HTTP; Fri, 14 Nov 2014 16:50:25 -0800 (PST) In-Reply-To: References: Date: Fri, 14 Nov 2014 17:50:25 -0700 Message-ID: Subject: Re: Refreshing Templates From: Mike Tutkowski To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=001a11c2df348a05790507db2164 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2df348a05790507db2164 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Michael, I would encourage you to create a JIRA enhancement ticket for the use case of modifying a template (unless anyone knows why that would not be a viable solution). https://issues.apache.org/jira/browse/CLOUDSTACK/?selectedTab=3Dcom.atlassi= an.jira.jira-projects-plugin:summary-panel The only thing that comes to mind is that it would be hard to know who is running with the old versus the new template (unless we started keeping track of that info, too). Thanks, Mike On Fri, Nov 14, 2014 at 5:31 PM, Michael Phillips wrote: > That seems like the only method I have found as well. Only problem with > that is I have a 3rd party software that integrates with CS and it uses C= S > to provision vm's etc. Deleting and re-uploading the template seems to > break my 3rd party app because although the new template is named the sam= e, > it must have a new UUID or GUID. > Wonder if it would be possible to just replace the templates .vmdk file. > Forgot to mention that this is a vmware template. > > > Date: Fri, 14 Nov 2014 17:21:30 -0700 > > Subject: Re: Refreshing Templates > > From: mike.tutkowski@solidfire.com > > To: dev@cloudstack.apache.org > > > > I'm thinking you have to delete the old one and replace it with a new > one. > > > > On Fri, Nov 14, 2014 at 5:01 PM, Michael Phillips < > mphilli7823@hotmail.com> > > wrote: > > > > > What is the best way to refresh a template in cloudstack? > > > Reasons one may want to refresh a template is to deploy the template > with > > > the latest patches, software etc. > > > > > > > > > > > > > > > > -- > > *Mike Tutkowski* > > *Senior CloudStack Developer, SolidFire Inc.* > > e: mike.tutkowski@solidfire.com > > o: 303.746.7302 > > Advancing the way the world uses the cloud > > *=E2=84=A2* > --=20 *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *=E2=84=A2* --001a11c2df348a05790507db2164--