Minutes :: Infra team meeting 2012-07-17
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-14.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-14.00.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-14.00.log.html ============== #ovirt Meeting ============== Meeting started by quaid at 14:00:06 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-14.00.log.html . Meeting summary - --------------- * oVirt Infra weekly meeting (quaid, 14:00:15) * Roll call & howdy (quaid, 14:00:33) * Agenda (quaid, 14:03:13) * LINK: http://wiki.ovirt.org/wiki/Infrastructure_team_meetings#2012-07-17 (quaid, 14:03:19) * Welcome new maintainers (quaid, 14:06:29) * How to handle donated hardware/VM hosts (quaid, 14:13:41) * ACTION: eedri to test running jenkins job in parallel on different nodes (eedri1, 14:26:51) * AGREED: Start new Jenkins VMs with basic config and see where the bottlenecks are (quaid, 14:36:57) * ACTION: Getting Puppet running is a top priority (quaid, 14:39:17) * ACTION: Research for service provider for a baremetal host for automation tests and possible Jenkins VM slaves if room (quaid, 14:40:43) * ACTION: quaid to get puppet.ovirt.org DNS (quaid, 14:43:26) * ACTION: Ask on Board and arch@ mailing lists for a baremetal host for automation tests (quaid, 14:47:40) * ACTION: eedri1 bring discussion to infra@ about how to do distributed Jenkins (quaid, 14:57:45) * ACTION: quaid to get eedri1 sudo on linode01.ovirt.org (quaid, 15:06:17) * ACTION: eedri to set up nighly jenkins job to collect lastest stable rpms from all ovirt projects and copy to ovirt.org/$JENKINS_HOME/rpms/$project (eedri1, 15:16:17) * ACTION: discuss on infra@ about security concerns when allowing gerrit patch jobs on jenkins (quaid, 15:23:28) * ACTION: finalize rpms directory structure on ovirt.org, to match Jenkiins/script needs/expectations (quaid, 15:24:14) * ACTION: discuss on infra@ how to distribute builds - baremetal, VMS, etc. (quaid, 15:28:20) * ACTION: may still need a dedicated baremetal host somewhere; quaid is asking around about budget, others can help define what we need & research hosting providers (quaid, 15:29:21) Meeting ended at 15:30:40 UTC. Action Items - ------------ * eedri to test running jenkins job in parallel on different nodes * Getting Puppet running is a top priority * Research for service provider for a baremetal host for automation tests and possible Jenkins VM slaves if room * quaid to get puppet.ovirt.org DNS * Ask on Board and arch@ mailing lists for a baremetal host for automation tests * eedri1 bring discussion to infra@ about how to do distributed Jenkins * quaid to get eedri1 sudo on linode01.ovirt.org * eedri to set up nighly jenkins job to collect lastest stable rpms from all ovirt projects and copy to ovirt.org/$JENKINS_HOME/rpms/$project * discuss on infra@ about security concerns when allowing gerrit patch jobs on jenkins * finalize rpms directory structure on ovirt.org, to match Jenkiins/script needs/expectations * discuss on infra@ how to distribute builds - baremetal, VMS, etc. * may still need a dedicated baremetal host somewhere; quaid is asking around about budget, others can help define what we need & research hosting providers Action Items, by person - ----------------------- * eedri1 * eedri1 bring discussion to infra@ about how to do distributed Jenkins * quaid to get eedri1 sudo on linode01.ovirt.org * quaid * quaid to get puppet.ovirt.org DNS * quaid to get eedri1 sudo on linode01.ovirt.org * may still need a dedicated baremetal host somewhere; quaid is asking around about budget, others can help define what we need & research hosting providers * **UNASSIGNED** * eedri to test running jenkins job in parallel on different nodes * Getting Puppet running is a top priority * Research for service provider for a baremetal host for automation tests and possible Jenkins VM slaves if room * Ask on Board and arch@ mailing lists for a baremetal host for automation tests * eedri to set up nighly jenkins job to collect lastest stable rpms from all ovirt projects and copy to ovirt.org/$JENKINS_HOME/rpms/$project * discuss on infra@ about security concerns when allowing gerrit patch jobs on jenkins * finalize rpms directory structure on ovirt.org, to match Jenkiins/script needs/expectations * discuss on infra@ how to distribute builds - baremetal, VMS, etc. People Present (lines said) - --------------------------- * eedri1 (124) * quaid (104) * mburns (54) * RobertM (49) * adamw (8) * ovirtbot (7) * mgoldboi (7) * gestahlt (4) * tjikkun_work (4) * ewoud (2) * ofrenkel (2) * hitvx (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot - -- Karsten 'quaid' Wade ..... http://iquaid.org ..... gpg key: AD0E0C41 http://Fairy-TaleFarm.com .......................... Urban homestead http://MicahForCouncil.org ................ Your advocate on council http://SantaCruzPedicab.com .......... Sensible local transportation -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFQBYXI2ZIOBq0ODEERAop7AJ9eDZ2JUxyZHuveVnxyT/E+wUr2+wCgy2PL Z387maqgT18Fgi8EO5KQtpw= =CLPl -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/17/2012 02:29 PM, Itamar Heim wrote:
On 07/17/2012 06:33 PM, Karsten (quaid) Wade wrote:
* ACTION: quaid to get puppet.ovirt.org DNS (quaid, 14:43:26)
do we want puppet directly, or via something like foreman?
It sounds like we have Puppet expertise in the group, I don't know if anyone knows about Foreman. Looks inclusive, might be a new skill someone wants to tackle. http://theforeman.org/ I presume we could start using Puppet right away, based on existing skills, and transition that work in to Foreman later? Part of this is we want to be sanely rolling out new hosts, and can do that immediately with our Puppet experience. My only concern would be if ramp-up time for Foreman delayed that too long. But if ramp-up is quick or things can be done in parallel, it definitely sounds interesting. - - Karsten - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFQBen52ZIOBq0ODEERAsyOAJ9Cf9ZDdXQFz1O956xtXct531Wg+ACeN5qH 6RTLN2KB3FIxGI266GGWMyU= =Qfg0 -----END PGP SIGNATURE-----
On Tue, Jul 17, 2012 at 03:40:57PM -0700, Karsten 'quaid' Wade wrote:
On 07/17/2012 02:29 PM, Itamar Heim wrote:
On 07/17/2012 06:33 PM, Karsten (quaid) Wade wrote:
* ACTION: quaid to get puppet.ovirt.org DNS (quaid, 14:43:26)
do we want puppet directly, or via something like foreman?
It sounds like we have Puppet expertise in the group, I don't know if anyone knows about Foreman. Looks inclusive, might be a new skill someone wants to tackle.
I presume we could start using Puppet right away, based on existing skills, and transition that work in to Foreman later?
Part of this is we want to be sanely rolling out new hosts, and can do that immediately with our Puppet experience. My only concern would be if ramp-up time for Foreman delayed that too long. But if ramp-up is quick or things can be done in parallel, it definitely sounds interesting.
I have experience with both puppet and foreman. Foreman is a very nice tool. Foreman is basically a nice frontend for puppet combined with deployment. Since we have a diverse environment where we mostly can't directly deploy I think we should just start with puppet for now. Transitioning will be relative easy anyway.
On 07/18/2012 05:54 AM, Ewoud Kohl van Wijngaarden wrote:
On 07/17/2012 02:29 PM, Itamar Heim wrote:
On 07/17/2012 06:33 PM, Karsten (quaid) Wade wrote:
* ACTION: quaid to get puppet.ovirt.org DNS (quaid, 14:43:26) do we want puppet directly, or via something like foreman? It sounds like we have Puppet expertise in the group, I don't know if anyone knows about Foreman. Looks inclusive, might be a new skill someone wants to tackle.
I presume we could start using Puppet right away, based on existing skills, and transition that work in to Foreman later?
Part of this is we want to be sanely rolling out new hosts, and can do that immediately with our Puppet experience. My only concern would be if ramp-up time for Foreman delayed that too long. But if ramp-up is quick or things can be done in parallel, it definitely sounds interesting. I have experience with both puppet and foreman. Foreman is a very nice tool. Foreman is basically a nice frontend for puppet combined with deployment. Since we have a diverse environment where we mostly can't
On Tue, Jul 17, 2012 at 03:40:57PM -0700, Karsten 'quaid' Wade wrote: directly deploy I think we should just start with puppet for now. Transitioning will be relative easy anyway. "Transitioning will be relative easy anyway." Sold me on Puppet only +1.
Thanks Robert
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Karsten (quaid) Wade" <quaid@iquaid.org> Cc: "infra" <infra@ovirt.org>, "Ohad Levy" <ohadlevy@redhat.com>, "Eyal Edri" <eedri@redhat.com> Sent: Wednesday, July 18, 2012 12:29:17 AM Subject: Re: Minutes :: Infra team meeting 2012-07-17
On 07/17/2012 06:33 PM, Karsten (quaid) Wade wrote:
* ACTION: quaid to get puppet.ovirt.org DNS (quaid, 14:43:26)
do we want puppet directly, or via something like foreman?
Foreman is great and would benefit the team, but it might be too complex and time consuming to maintain at first. And probably no one (besides myself) if familiar with it inside the infra team, so we'll have difficulties adding new people to maintain it. We can start with installing a puppet-master and later add it to a foreman server. (unless it's easier to install foreman + puppet as a bundle (single installer), maybe ohad can shed some light on it.. ) Eyal.
On 07/18/2012 10:57 AM, Eyal Edri wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Karsten (quaid) Wade" <quaid@iquaid.org> Cc: "infra" <infra@ovirt.org>, "Ohad Levy" <ohadlevy@redhat.com>, "Eyal Edri" <eedri@redhat.com> Sent: Wednesday, July 18, 2012 12:29:17 AM Subject: Re: Minutes :: Infra team meeting 2012-07-17
On 07/17/2012 06:33 PM, Karsten (quaid) Wade wrote:
* ACTION: quaid to get puppet.ovirt.org DNS (quaid, 14:43:26)
do we want puppet directly, or via something like foreman?
Foreman is great and would benefit the team, but it might be too complex and time consuming to maintain at first. And probably no one (besides myself) if familiar with it inside the infra team, so we'll have difficulties adding new people to maintain it. We can start with installing a puppet-master and later add it to a foreman server.
(unless it's easier to install foreman + puppet as a bundle (single installer), maybe ohad can shed some light on it.. )
we have a fully automated installer for foreman + puppet master, see https://github.com/theforeman/foreman-installer#readme This should help you to deploy your infra with no effort, and I would recommend using it as a starting point regardless if you use foreman or not. in anycase, using foreman just for reporting requires very little effort, and would probably make sense too. I'll be happy to try and help out in case you decide to deploy it. Ohad
participants (7)
-
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Itamar Heim -
Karsten 'quaid' Wade -
Karsten (quaid) Wade -
Ohad Levy -
Robert Middleswarth