On Wed, Feb 27, 2013 at 11:53 AM, Chiradeep Vittal <chiradeep.vit...@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" <bhais...@apache.org> wrote: > >>On Wed, Feb 27, 2013 at 3:45 AM, Sheng Yang <sh...@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.child...@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). >
