From jboggs at redhat.com Tue Oct 4 19:05:13 2011 From: jboggs at redhat.com (Joey Boggs) Date: Tue, 04 Oct 2011 15:05:13 -0400 Subject: [node-devel] Fedora 16 Current Node Status Message-ID: <4E8B58E9.3090802@redhat.com> The last official release was Fedora 14 based. Currently we're working through a couple issues with moving to Fedora 16. Systemd - issues with systemd startup that affect the installer/ setup portions of the boot process, these appear to have been solved now At this point normal installation and configurations tests are being ran to determine any bugs and items that have broken or since been deprecated after Fedora 14. Installation so far appears normal with only one cosmetic bug so far: - Scrollbar characters are set as "?" (locale/language issue) After Reboot - grub installation is broken(grub menu has unreadable characters for title/kernel/initrd lines) and error 15 file not found for vmlinuz0, even when autocompleted on grub cli). Suspect this is something with it still using legacy grub and just needs to be updated for grub2. From mburns at redhat.com Tue Oct 11 20:45:23 2011 From: mburns at redhat.com (Mike Burns) Date: Tue, 11 Oct 2011 16:45:23 -0400 Subject: [node-devel] Automation Plans for ovirt-node Message-ID: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> I've been working on plans for automating ovirt-node builds and testing. I've added a page to the ovirt.org wiki to track my plans and status of where we're at. http://ovirt.org/wiki/Node_Automation Comments and suggestions are welcome. Thanks Mike From simonjin at linux.vnet.ibm.com Thu Oct 13 02:44:21 2011 From: simonjin at linux.vnet.ibm.com (simonjin) Date: Wed, 12 Oct 2011 22:44:21 -0400 Subject: [node-devel] Automation Plans for ovirt-node In-Reply-To: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> References: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> Message-ID: <4E965085.6090708@linux.vnet.ibm.com> On 10/11/2011 04:45 PM, Mike Burns wrote: > I've been working on plans for automating ovirt-node builds and testing. > I've added a page to the ovirt.org wiki to track my plans and status of > where we're at. > > http://ovirt.org/wiki/Node_Automation > > Comments and suggestions are welcome. > This is really great news, automation build&test&release is really needed in Node project. spin up a VM for each build process is a great idea, snapshot could be used for VM's sanity. As for tools, for i know Buildbot(http://trac.buildbot.net/) can cover all the goals you described, it's a very mature tools for continuous integration, used by lot of large community, like Mozilla.org, and it's wrote by Python. BR, -Yuntong > Thanks > > Mike > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simonjin at linux.vnet.ibm.com Thu Oct 13 06:37:43 2011 From: simonjin at linux.vnet.ibm.com (simonjin) Date: Thu, 13 Oct 2011 02:37:43 -0400 Subject: [node-devel] Automation Plans for ovirt-node In-Reply-To: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> References: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> Message-ID: <4E968737.4040701@linux.vnet.ibm.com> On 10/11/2011 04:45 PM, Mike Burns wrote: > http://ovirt.org/wiki/Node_Automation > > Comments and suggestions are welcome. Another thing about automatic test, Node image can't be tested on a VM since kvm doesn't support nest VMs, in this case , lots of physic machines needed for testing, and each testing process will be really time&resource consuming because it involves image installation process, how do we deal with this ? -Yuntong From mburns at redhat.com Thu Oct 13 11:00:02 2011 From: mburns at redhat.com (Mike Burns) Date: Thu, 13 Oct 2011 07:00:02 -0400 Subject: [node-devel] Automation Plans for ovirt-node In-Reply-To: <4E965085.6090708@linux.vnet.ibm.com> References: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> <4E965085.6090708@linux.vnet.ibm.com> Message-ID: <1318503602.3759.17.camel@beelzebub.mburnsfire.net> On Wed, 2011-10-12 at 22:44 -0400, simonjin wrote: > On 10/11/2011 04:45 PM, Mike Burns wrote: > > I've been working on plans for automating ovirt-node builds and testing. > > I've added a page to the ovirt.org wiki to track my plans and status of > > where we're at. > > > > http://ovirt.org/wiki/Node_Automation > > > > Comments and suggestions are welcome. > > > This is really great news, automation build&test&release is really > needed in Node project. I agree, though I don't know that we'd take the step to do automatic releases. I think I'd still want some hands on testing before releasing. > spin up a VM for each build process is a great idea, snapshot could be > used for VM's sanity. > As for tools, for i know Buildbot(http://trac.buildbot.net/) can cover > all the goals you described, > it's a very mature tools for continuous integration, used by lot of > large community, like Mozilla.org, and it's wrote by Python. I looked at buildbot a year or so ago and it does do a lot of what we're looking for. I haven't done a POC or anything with it however. I'm currently working with Jenkins (http://jenkins-ci.org) to see if it can cover what we need. I think I'm leaning more toward Jenkins at the moment since I know that the Engine and VDSM projects both use Jenkins already. It's also in the works for a public instance to be setup on ovirt.org. Makes more sense to me to use what is already in use and being deployed rather than deploy something else as well. Mike > > BR, > -Yuntong > > Thanks > > > > Mike > > > > _______________________________________________ > > node-devel mailing list > > node-devel at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/node-devel > > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mburns at redhat.com Thu Oct 13 11:05:27 2011 From: mburns at redhat.com (Mike Burns) Date: Thu, 13 Oct 2011 07:05:27 -0400 Subject: [node-devel] Automation Plans for ovirt-node In-Reply-To: <4E968737.4040701@linux.vnet.ibm.com> References: <1318365924.2849.29.camel@mburns-laptop.usersys.redhat.com> <4E968737.4040701@linux.vnet.ibm.com> Message-ID: <1318503927.3759.22.camel@beelzebub.mburnsfire.net> On Thu, 2011-10-13 at 02:37 -0400, simonjin wrote: > On 10/11/2011 04:45 PM, Mike Burns wrote: > > http://ovirt.org/wiki/Node_Automation > > > > Comments and suggestions are welcome. > Another thing about automatic test, Node image can't be tested on a VM > since kvm doesn't support nest VMs, in this case , lots of physic > machines needed for testing, and each testing process will be really > time&resource consuming because it involves image installation process, > how do we deal with this ? Yes, this is a problem that I'm not 100% sure how to solve at the moment. A lot of the answer might depend on how the infrastructure group of ovirt.org decides to provide resources. A large portion of the tests we want to do can be run with the ovirt-node iso running in a vm. They *might* even be doable in a nested vm using emulation, though I'd rather avoid that path if possible. I think that right now, we can't really make a call on how to do this testing until the oVirt.org infrastructure team and board figure out how we're going to make resources like this available. Mike > > -Yuntong > > > _______________________________________________ > node-devel mailing list > node-devel at ovirt.org > http://lists.ovirt.org/mailman/listinfo/node-devel From mburns at redhat.com Thu Oct 13 14:16:01 2011 From: mburns at redhat.com (Mike Burns) Date: Thu, 13 Oct 2011 10:16:01 -0400 Subject: [node-devel] [PATCH node] fix uninstall wiping of boot disks Message-ID: <1318515361-26854-1-git-send-email-mburns@redhat.com> calling function get_root_disk when function is actually get_root_device rhbz#738182 Signed-off-by: Mike Burns --- scripts/ovirt-early | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 28ebd05..6c22054 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@ -679,7 +679,7 @@ start_ovirt_early () { oldIFS=$IFS log "Found uninstall arg, wiping mbr from init disks" IFS=$SEP - for init_disk in $init $init_app $(get_boot_disk); do + for init_disk in $init $init_app $(get_boot_device); do echo "Wiping $init_disk" wipe_mbr "$init_disk" done -- 1.7.4.4