Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 21 Aug 2013 21:36:54 +0000 (UTC)
From: "Sudha Ponnaganti (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12633172.1361358236661.12970.1377121014266@arcas>
In-Reply-To: <JIRA.12633172.1361358236661@arcas>
References: <JIRA.12633172.1361358236661@arcas>
Subject: [jira] [Closed] (CLOUDSTACK-1340) Make new systemvm appliance
 compatible to 4.0 systemvm template
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudha Ponnaganti closed CLOUDSTACK-1340.
----------------------------------------

    
> Make new systemvm appliance compatible to 4.0 systemvm template
> ---------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1340
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1340
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.2.0
>
>
> With CLOUDSTACK-1066 we worked on a new cooler way of generating systemvm appliances and exporting them for various hypervisors, even got a jenkins job to automate that for master (http://jenkins.cloudstack.org/job/build-systemvm-master/).
> The issue is to fix the definitions and postinstall scripts etc. to make sure these appliances are actually usable with KVM, Xen and VMWare. The task is to make them compatible and replace-able wrt 4.0 systemvm template.

--
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