Re: Infrastructure for Jenkins

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/12/2012 08:51 AM, Mike Burns wrote: > On Thu, 2012-07-12 at 17:57 +0300, Itamar Heim wrote: >> On 07/12/2012 05:55 PM, Eyal Edri wrote: >>> >>> ----- Original Message ----- >>>> From: "Karsten 'quaid' Wade" <kwade(a)redhat.com&gt; To: >>>> infra(a)ovirt.org Sent: Thursday, July 12, 2012 5:31:41 PM >>>> Subject: Re: Infrastructure for Jenkins >>>> > On 07/12/2012 05:57 AM, Jabs, Joachim wrote: >>>>>> Hi Guys, >>>>>> >>>>>> >>>>>> >>>>>> as previously offered: >>>>>> >>>>>> >>>>>> >>>>>> Im willing to provide you guys infrastructure for >>>>>> Jenkins. Im currently trying out getting oVirt running on >>>>>> a cluster (we have 192 Cores and 3TB RAM aviable) for >>>>>> providing help with problems around ovirt that might >>>>>> arise. >>>>>> >>>>>> The Cluster is not commercially used (Not right now) and >>>>>> for me its also a good opportunity to learn about ovirt >>>>>> and also about hosting VM related infrastructure. This >>>>>> will also be a test for stability and maintainability >>>>>> around the hardware used. >>>>>> >>>>>> >>>>>> >>>>>> If you guys sum up what you need, I think I might be able >>>>>> to do something for you there. If you have any questions >>>>>> regarding the offer, just ask. > Hey, thanks for following. This is a great offer, +1 from me. > > Ewoud, Eyal (& others?) - what does Joachim need to do? Is this a > good place to start? -- >>>> This is an excellent offer and opportunity. Since we're >>>> talking about VMs, we can start with basic hardware spec and >>>> increase it after we'll see the bottle necks in real time. >>>> >>>> I would start with 3 VMs each running 16GB RAM, 200GB DISK, >>>> 32 GB SWAP, each with 4/8 cores each. >>>> >>>> Itamar, mburns -> any recommendation on how many VMs per >>>> hardware node should we use? >>>> >>> considering the workload, i'd start with not overcomitting >>> resources, and later analyzing behavior >> Agree with Itamar. I'd also consider having a vm or 2 that are >> running various target distros where we can build packages for >> different distros. +1 Robert - are you interested in working on the package autobuild for RHEL & rebuilds?

I figure we have the Fedora expertise already. Anyone know enough to get the Debian/Ubuntu packages building? (Maybe even automate populating an Ubuntu PPA?) Same questions for OpenSUSE.

We have a classic chicken-and-egg problem with being of interest to the OpenSUSE. Debian, Ubuntu, etc. communities - we need builds to generate the interest of people who would want to maintain the packages in their downstream distro repo.

>> Also, 200GB disk seems a bit excessive to me. Since this is >> running on oVirt, maybe a thin provisioned disk would be a good >> choice. The slaves generally don't need as much disk. Let's keep iterating on the content on http://ovirt.org/wiki/Jenkins, not just the service minimums, but cleaning the setup steps, etc. - - Karsten - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra