cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandan Purushothama (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-216) Templates' Source Location Information present on "template_host_ref" and "vm_template" tables should refer to Apache System Template Locations
Date Thu, 21 Mar 2013 22:01:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609562#comment-13609562
] 

Chandan Purushothama commented on CLOUDSTACK-216:
-------------------------------------------------

The email thread below refers that the project still relies on Citrix to host them. Hence
Can this ticket be moved to the next release?

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com] 
Sent: Wednesday, February 27, 2013 8:10 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: What are the System VM Templates for ASF 4.1 Release?

On Tue, Feb 26, 2013 at 02:14:20PM -0800, Will Chan wrote:
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.childers@sungard.com]
> > Sent: Tuesday, February 26, 2013 1:55 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: What are the System VM Templates for ASF 4.1 Release?
> > 
> > 
> > The problem right now, is that IPv6 requires the new system vm (I 
> > think), but we have not fully tested the new system VM build process.
> > 
> 
> Ok, I'm a bit confused.  Currently, it looks like we have 3 options?
> 
> 1. Use the current 4.0 template, but that means we remove ipv6 support for 4.1 ACS.

This one is possible, and I wouldn't argue against it.  But I think option 3 is more interesting.

> 2. Potentially delay 4.1 so we can incorporate the new system VM build process.  

I'm -1 to this.  I don't think we should delay for this, as the new build process is basically
a "new feature" (stretching the definition of feature to include major changes).

> 3. Figure out a way to generate the 4.1 template using the old way of generating the
current 4.0 template.  I assume this option is an absolute no-go.

Why?  Honestly, we don't actually "ship" the system VMs.  The project still relies on Citrix
to host them from the orig submission timeframe.

Could we have someone add ipv6 to them and post an updated version?
We've update our DB init scripts to point to the new location.

> 
> QA is currently blocked on what to test and they cannot possibly have the time to test
4.1 with a 4.0 template and 4.1 template.  
>
> Will
> 

                
> Templates' Source Location Information present on "template_host_ref" and "vm_template"
tables should refer to Apache System Template Locations 
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-216
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-216
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: pre-4.0.0
>            Reporter: Chandan Purushothama
>            Assignee: Hugo Trippaers
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Currently the information present in "template_host_ref" and "vm_template" tables is
not referring to System VM Template Locations on ASF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message