Re: [ovirt-devel] What does your oVirt development environment look like?

From: "Adam Litke" <alitke(a)redhat.com&gt; To: "Yair Zaslavsky" <yzaslavs(a)redhat.com&gt; Cc: devel(a)ovirt.org Sent: Friday, August 15, 2014 11:17:05 PM Subject: Re: [ovirt-devel] What does your oVirt development environment look like? On 15/08/14 15:57 -0400, Yair Zaslavsky wrote: > > >----- Original Message ----- >> From: "ybronhei" <ybronhei(a)redhat.com&gt; >> To: "Adam Litke" <alitke(a)redhat.com&gt;, devel(a)ovirt.org >> Sent: Friday, August 15, 2014 7:36:23 PM >> Subject: Re: [ovirt-devel] What does your oVirt development environment >> look like? >> >> On 08/15/2014 09:32 AM, Adam Litke wrote: >> > Ever since starting to work on oVirt around 3 years ago I've been >> > striving for the perfect development and test environment. I was >> > inspired by Yaniv's recent deep dive on Foreman integration and >> > thought I'd ask people to share their setups and any tips and tricks >> > so we can all become better, more efficient developers. >> > >> > My setup consists of my main work laptop and two mini-Dell servers. I >> > run the engine on my laptop and I serve NFS and iSCSI (using >> > targetcli) from this system as well. I use the ethernet port on the >> > laptop to connect it to a subnet with the two Dell systems. >> > >> > Some goals for my setup are: >> > - Easy provisioning of the virt-hosts so I can quickly test on Fedora >> > and CentOS without spending lots of time reinstalling >> > - Ability to test block and nfs storage >> > - Automation of test scenarios involving engine and hosts >> > >> > To help me reach these goals I've deployed cobbler on my laptop and it >> > does a pretty good job at managing PXE boot configurations for my >> > hosts (and VMs) so they can be automatically intalled as needed. >> > After viewing Yaniv's presentation, it seems that Forman/Puppet are >> > the way of the future but it does seem a bit more involved to set up. >> > I am definitely curious if others are using Foreman in their personal >> > dev/test environment and can offer some insight on how that is working >> > out. >> > >> > Thanks, and I look forward to reading about more of your setups! If >> > we get enough of these, maybe this could make a good section of the >> > wiki. >> > >> Heppy to hear :) for those who missed - >> https://www.youtube.com/watch?v=gozX891kYAY >> >> each one has its own needs and goals I guess, but if you say it might >> help, I'll never say no for sharing :P >> I have 3 dells under my desk, I compile the engine a lot and its heavy >> for my laptop. So I clone my local working directory and build it on the >> strongest mini-dell using local jenkins server >> (http://www.ovirt.org/Local_Jenkins_For_The_People). The other 2 I use >> as hypervisor when needed. provision them is done by me manually :/.. >> cobbler pxe boot could help with already defined image.. Other then >> that, I have nfs mount for storage and few vms for compilation and small >> tests > >Haven't used "Jenkins for the people" for quite some time, it's >awesome though. Yaniv, does your Jenkins build all your local >branches? I don't have much to share, my environment is even >simpler. I am sure it's a common knowledge but still a reminder >(even if a new developer can benefit from it, it will be good) - you >can create a database schema per each branch you work on, and if >needed to switch between branches, you don't have to destroy your >current database. Quite helpful, I must say , for someone who works >100% on engine related stuff. Thanks for sharing... How do you manage your multiple db schemas? Just with the engine-backup and engine-restore commands?