Return-Path: 
 <cloudstack-dev-return-25192-apmail-incubator-cloudstack-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 017E8E905
	for <apmail-incubator-cloudstack-dev-archive@minotaur.apache.org>;
 Wed, 27 Feb 2013 11:53:20 +0000 (UTC)
Received: (qmail 77967 invoked by uid 500); 27 Feb 2013 11:53:19 -0000
Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org
Received: (qmail 77927 invoked by uid 500); 27 Feb 2013 11:53:19 -0000
Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cloudstack-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cloudstack-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cloudstack-dev@incubator.apache.org>
List-Id: <cloudstack-dev.incubator.apache.org>
Reply-To: cloudstack-dev@incubator.apache.org
Delivered-To: mailing list cloudstack-dev@incubator.apache.org
Received: (qmail 77906 invoked by uid 99); 27 Feb 2013 11:53:18 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 11:53:18 +0000
X-ASF-Spam-Status: No, hits=-0.5 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of rohityadav89@gmail.com
 designates 74.125.83.44 as permitted sender)
Received: from [74.125.83.44] (HELO mail-ee0-f44.google.com) (74.125.83.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 11:53:14 +0000
Received: by mail-ee0-f44.google.com with SMTP id l10so405834eei.3
        for <cloudstack-dev@incubator.apache.org>;
 Wed, 27 Feb 2013 03:52:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type;
        bh=7fxJ+V18qq0VpVXZBK0VB6Nk32HsMQYy0/tVaZvOjaM=;
        b=wjoMLr/3mp0XcthGZnEpf+xRa5wtqd0wCwePk9WFEf4BFgnunEAcCUljAmT4u9uNgO
         XQSdX3hIfeXPSXw3xA1ojgX9FRSSwSYPdW8TAaAJRsV9RLr0u2zJdZRovuCIexN8fzqL
         a1DnuDoOwRV7oa3IA/f9PBCZQTEiXlD1asMaJvXmMB4BOCBASasLWqNputuhPlGIc5Yu
         RgcLwihPiO5q2ca1c/efGFwYEgVzwSfhqxpC+TBOWmdBUZJhHBU8PvGXs+rc9dPhjV55
         z4clTAQVz3gIipuLa2ocMVq0kVvdtcGYWep/ohYJWqEmy+/7Q2w/BgX0r81KiqGhANi2
         14WQ==
X-Received: by 10.14.0.135 with SMTP id 7mr5667479eeb.5.1361965973371; Wed, 27
 Feb 2013 03:52:53 -0800 (PST)
MIME-Version: 1.0
Sender: rohityadav89@gmail.com
Received: by 10.223.155.141 with HTTP; Wed, 27 Feb 2013 03:52:33 -0800 (PST)
In-Reply-To: <CD52E574.9C6F%chiradeep.vittal@citrix.com>
References: 
 <CANLSSBUa6+jyVhCS7+-tt7g1DqkYkwBSTeGUJCnk1NdU8xBDuQ@mail.gmail.com>
 <CD52E574.9C6F%chiradeep.vittal@citrix.com>
From: Rohit Yadav <bhaisaab@apache.org>
Date: Wed, 27 Feb 2013 17:22:33 +0530
X-Google-Sender-Auth: y040zZjecvJ9_L6Eb2oUE59CSRk
Message-ID: 
 <CANLSSBXtKHJQ-sqYt4ypuMnGb5XDd6uGznKk9TEndSVLWJwKtQ@mail.gmail.com>
Subject: Re: What are the System VM Templates for ASF 4.1 Release?
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

On Wed, Feb 27, 2013 at 11:53 AM, Chiradeep Vittal
<Chiradeep.Vittal@citrix.com> wrote:
> Another work-around may be to not require new systemvms unless the ipv6
> feature is required in which case:
> A. We provide the bits of the systemvm of whatever Sheng's been testing
> with (with the caveat that it is under development/beta)
> B. Write a patch for cloud-early-config (or ssh in after VR is created) to
> apt-get update + apt-get install <ipv6 packages>

Yes, we can do either of those and also give option for people to
build their own or get from the jenkins job [1] if they want ipv6
features.

Nonetheless, let's test/fix the systemvm; I've few questions for
Sheng, Chiradeep:

- Do we need to install xe-guest-utilities, pv drivers for windows? I
cannot locate a publicly available latest version for debian:
http://downloads.xen.org/XCP/debian/xs-tools-5.9.960.iso I can make it
build and install if needed. Also, do we need any other host
additions?
- Pl. some recent commits and check any packages that needs to be
installed/removed and configuration fixing that needs to be done.
Comparing the new and old scripts can help:
tools/appliance/definitions/systemvmtemplate/postinstall.sh  and
patches/systemvm/debian/buildsystemvm.sh
- Chiradeep instead of wget-ing only few scripts, I'm copying all the
configs from latest source tarball from master, signature is also
fixed. The same was done in the old script, pl. check if that needs
any correction.
- There are some grub cmdline and inittab related fixed on old script,
inittab fix has been moved, don't know what to do about the grub
cmdline fix.
- acpid fix moved from old script, pl. check if that needs any correction

Lastly , I need help as I've no idea what really goes into building
systemvm, I can only refer to the
scripts/systemvm/debian/buildsystemvm.sh

Regards.

>
> On 2/26/13 10:15 PM, "Rohit Yadav" <bhaisaab@apache.org> wrote:
>
>>On Wed, Feb 27, 2013 at 3:45 AM, Sheng Yang <sheng@yasker.org> wrote:
>>> When I first report the bug
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-1066
>>>
>>> I've set the target for 4.1 because of ipv6 need.
>>>
>>> When Rohit fixed it, it was changed to 4.2, sorry I didn't aware of
>>>that.
>>
>>Yes Sheng is correct, I was responsible for that because the
>>feature/code to create systemvms was not even started and since I
>>started working on it after the code freeze, I moved the version to
>>4.2
>>It was only recently when I found out that ipv6 is going to make it in
>>4.1, in that case the feature is code complete [1] and we've an
>>automated jenkins job. The only problems are:
>>
>>- Code syncing: I did not cherry-pick the code to 4.1
>>- Testing: We need to test against 4.1 branch that the
>>appliance/template really works [2]
>>
>>I'm sorry Sheng if ipv6 won't make in 4.1 because of this. But I would
>>try my best to test/fix the template for Xen at least before 28/2, I
>>really want to see your feature go in 4.1
>>Since, 4.1 is frozen, community would have to make an exception to at
>>least allow the new systemvms templates (if not the code) to be used
>>in case it works fine for all three (kvm, xen and vmware) and we could
>>still fix/test ahead of time, we still have few more weeks before the
>>release; otherwise we can always use the same old template.
>>
>>Comments, suggestions, especially from Chip and ppmc?
>>
>>Regards.
>>
>>
>>[1] https://issues.apache.org/jira/browse/CLOUDSTACK-1066
>>[2] https://issues.apache.org/jira/browse/CLOUDSTACK-1340
>>
>>>
>>> --Sheng
>>>
>>> On Tue, Feb 26, 2013 at 2:12 PM, Chip Childers
>>> <chip.childers@sungard.com> wrote:
>>>> On Tue, Feb 26, 2013 at 02:07:37PM -0800, Chandan Purushothama wrote:
>>>>> Building System VM Template is a 4.2 feature
>>>>>https://issues.apache.org/jira/browse/CLOUDSTACK-1340.  The system VM
>>>>>Templates posted by Rohit is for the Master branch
>>>>>http://jenkins.cloudstack.org/view/master/job/build-systemvm-master/las
>>>>>tSuccessfulBuild/artifact/tools/appliance/dist/ . I am referring to
>>>>>the ASF 4.1 Release System VM Templates in my question.
>>>>
>>>> So in that case, I guess the only system VMs we have to use now are the
>>>> same ones we used for 4.0 (which were inherited from Citrix pre-ASF).
>