Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of rohityadav89@gmail.com
 designates 74.125.83.42 as permitted sender)
MIME-Version: 1.0
Sender: rohityadav89@gmail.com
In-Reply-To: 
 <CA+2rt42h-ToJEOqEr9=vhN+AgDjD_LXnk899OFhOy32WCErsnA@mail.gmail.com>
References: 
 <25171B03A3D9E24AADC227668ADE91C9011311B87685@SJCPMAILBOX01.citrite.net>
 <61AE1E2837A06D4A8E98B796183842D4012B07A3C0B4@SJCPMAILBOX01.citrite.net>
 <20130226215430.GR81779@USLT-205755.sungardas.corp>
 <D2EE6B3265AD864EB3EA4F5C670D256F32267E@EXDFO01L-CRP-06.webmdhealth.net>
 <25171B03A3D9E24AADC227668ADE91C9011311B87746@SJCPMAILBOX01.citrite.net>
 <20130226221255.GU81779@USLT-205755.sungardas.corp>
 <CA+2rt42h-ToJEOqEr9=vhN+AgDjD_LXnk899OFhOy32WCErsnA@mail.gmail.com>
From: Rohit Yadav <bhaisaab@apache.org>
Date: Wed, 27 Feb 2013 11:45:26 +0530
Message-ID: 
 <CANLSSBUa6+jyVhCS7+-tt7g1DqkYkwBSTeGUJCnk1NdU8xBDuQ@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
Content-Transfer-Encoding: quoted-printable

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 fo=
r the Master branch http://jenkins.cloudstack.org/view/master/job/build-sys=
temvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/ . I am refe=
rring 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).