cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <Chiradeep.Vit...@citrix.com>
Subject Re: System VM template caching
Date Wed, 09 Oct 2013 18:15:57 GMT
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Releas
e_Notes/upgrade-instructions.html


On 10/9/13 10:11 AM, "kelcey@backbonetechnology.com"
<kelcey@backbonetechnology.com> wrote:

>We tested deleting the template on primary storage, and it failed to
>regenerate.
>
>What is the documented method for registering the new template, can you
>link to it?
>
>It seems many of us failed to find any documentation about updating the
>template period, not just in the 4.2 release doc under upgrades from 4.1
>
>Thanks.
>
>Sent from my HTC
>
>----- Reply message -----
>From: "Ahmad Emneina" <aemneina@gmail.com>
>To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
>Subject: System VM template caching
>Date: Wed, Oct 9, 2013 9:48 AM
>
>there might be a more sound way than swapping the template on secondary
>storage and hacking the db. I figure one should be able to register the
>template, via the documented route... wait for download to succeed,
>upgrade
>the binary bits. then when the system vm's fail to launch. delete the
>cached template on primary storage. That should be enough to trigger a new
>system vm propagated to the primary storage. I find it hard to believe
>this
>passed QA...
>
>
>On Wed, Oct 9, 2013 at 9:39 AM, kelcey@backbonetechnology.com <
>kelcey@backbonetechnology.com> wrote:
>
>> This process you mention for registering as a user VM I can't find in
>>the
>> upgrade guide. Do you have a link?
>>
>> The work around works because CloudStack defaults to re-download the
>> system template is it is in NOT_DOWNLOADED status. How ever the database
>> never gets updated for the life of the build.
>>
>> CS is designed it seems to only ever have a single unaltered template_id
>> '3' record. And I guess the template download script just overwrites the
>> sane GUID filename.
>>
>> Seems like a solution that could be handled in a better way.
>>
>> Either way, this is what has been working for us in the community.
>>
>> Sent from my HTC
>>
>> ----- Reply message -----
>> From: "Sebastien Goasguen" <runseb@gmail.com>
>> To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
>> Cc: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
>> Subject: System VM template caching
>> Date: Wed, Oct 9, 2013 9:30 AM
>>
>> Are you sure about this ? I thought we needed to register them as user
>>vm
>> and that the upgrade would convert them to systemVM automatically
>>
>> -Sebastien
>>
>> On 9 Oct 2013, at 17:22, "kelcey@backbonetechnology.com"<
>> kelcey@backbonetechnology.com> wrote:
>>
>> > I was able to create a work around and several community builders
>>tested
>> it out for me and it works.
>> >
>> > I will not submit to docs as it's a hack, but I have updated the JIRA
>> ticket.
>> >
>> > Work around can be found at:
>> >
>> >
>> 
>>http://cloud.kelceydamage.com/cloudfire/blog/2013/10/08/conquering-the-cl
>>oudstack-4-2-dragon-kvm/
>> >
>> > Thanks,
>> >
>> > -Kelcey
>> >
>> > Sent from my HTC
>> >
>> > ----- Reply message -----
>> > From: "Soheil Eizadi" <seizadi@infoblox.com>
>> > To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
>> > Subject: System VM template caching
>> > Date: Tue, Oct 8, 2013 9:49 PM
>> >
>> > This seems similar to a problem I had on 4.3 Master with System VM
>> creation. If it is the same problem you can check from API command
>> ListTemplateCommand(), from CloudMonkey and see if it returns a bogus
>> cached value. Then you know it is the same problem.
>> > -Soheil
>> >
>> >
>> 
>>http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201309.mbox/%3C67
>>17EC2E5A665A40A5AF626D7D4FA90625E2E487@x2008mb1.infoblox.com%3E
>> >
>> > ________________________________________
>> > From: Kelcey Jamison Damage [kelcey@backbonetechnology.com]
>> > Sent: Tuesday, October 08, 2013 12:19 PM
>> > To: Cloud Dev
>> > Subject: [ACS 4.2][Upgrade Issue] System VM template caching
>> >
>> > Hi,
>> >
>> > Several of us in the community have found that with the 4.2 upgrade,
>> when we download and install the latest system VM template, CloudStack
>> refuses to use this template for new system VM creation. CloudStack
>>appears
>> to be usin a cached or master-clone variant of the old template.
>> >
>> > This is causing may KVM+ 4.2 users to have broken clouds, A bug report
>> has been filed: https://issues.apache.org/jira/browse/CLOUDSTACK-4826
>> >
>> > My question is: Does anyone know where this cached template is stored?
>> when CloudStack goes to make a new system VM, where does it look first
>>for
>> the template? We have observed through testing that this is no secondary
>> storage.
>> >
>> > Thanks in advance.
>> >
>> > Kelcey Damage | Infrastructure Systems Architect
>> > Strategy | Automation | Cloud Computing | Technology Development
>> >
>> > Backbone Technology, Inc
>> > 604-331-1152 ext. 114


Mime
View raw message