Minutes :: Infra weekly sync :: 20121126
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA5EC8749940004E757F83E0B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-11-26-15.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-11-26-15.00.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-11-26-15.00.log.h= tml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D #ovirt: oVirt Infra weekly =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Meeting started by quaid at 15:00:17 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-11-26-15.00.log.html . Meeting summary --------------- * Agenda (quaid, 15:02:24) * MediaWiki & www (quaid, 15:04:16) * Remaining problem of a mod_rewrite rule to get the logo visible (quaid, 15:05:04) * LINK: http://fpaste.org/NEgP/ (quaid, 15:07:42) * LINK: http://wiki-ovirt.rhcloud.com/skins/common/images/oVirt-logo.png (quaid, 15:08:06) * process to transfer sites should take 45 to 90 minutes (quaid, 15:12:57) * ACTION: quaid to arrange DNS cutover timing based on the idea that we'll have this working within 2 days (quaid, 15:13:18) * need to make sure wiki images are showing up in pages (quaid, 15:19:45) * MediaWiki backup script (quaid, 15:19:56) * I forgot to remove this topic but I think we're covered with this because we'll need a new backup procedure for the new OpenShift based tool (quaid, 15:20:32) * of course if I write that script it may have the same problem, so I'll be coming back later for help on that :) (quaid, 15:20:48) * Hosting (quaid, 15:20:56) * My Red Hat IT contact told me last week he is provisioning two servers at RackSpace for us, bare metal to use as we wish (quaid, 15:21:23) * RackSpace servers should be available this week or next, depending on how fast the paper churns (quaid, 15:21:44) * We're also proceeding with plans for Alter Way work, and may start installing & such but not switchover data until paper churns there (quaid, 15:23:28) * ACTION: quaid to tell people status of 'broken' script & to please hang on (quaid, 15:25:06) * Trac review (quaid, 15:27:15) * I'm moving this topic to the end of the meeting, as it's a bit of administrivia that we don't need to do in the middle - often it's covered by other open items anyway, so putting it at the end will make it faster (quaid, 15:27:43) * ACTION: quaid to move this topic to the end of the agenda permanently (quaid, 15:27:55) * Puppet (quaid, 15:28:30) * ewoud has a proof of concept (POC) Foreman install running: (quaid, 15:30:45) * LINK: https://foreman.ekohl.nl (quaid, 15:30:57) * ewoud is working on the initial Puppet manifests (quaid, 15:31:25) * ACTION: quaid, dcaro, dneary will help ewoud with Puppet manifests (quaid, 15:34:06) * Puppet manifest discussion to happen on infra@ovirt.org ASAP (quaid, 15:34:51) * Jenkins (quaid, 15:39:54) * jenkins.ovirt.org updated to latest for security fix (quaid, 15:41:06) * ACTION: we should consider using openid auth in new jenkins server (eedri, 15:43:04) * we've been adding new power users, who offest the load on the Infra tream by enabling people with experience to enhance sub projects in Jenkins (quaid, 15:43:18) * IDEA: we should consider using openid auth in new Jenkins server (quaid, 15:43:40) * ACTION: eedri will work on OpenID for Jenkins (quaid, 15:45:32) * ACTION: oVirt Infra to make a Foreman feature request to have OpenID (quaid, 15:46:30) * ACTION: quaid to look in to MediaWiki and OpenID (quaid, 15:46:39) * Puppet/Foreman (quaid, 15:48:47) * AGREED: using foreman rpms deployments is better than using the foreman git repo (quaid, 16:01:53) * Gerrit (quaid, 16:02:06) * I think the Infra git repo is available, but I haven't put anything in it (quaid, 16:02:26) * Process for bringing in new people to INfra (quaid, 16:04:15) * we need a discussion on list where everyone can be involved (quaid, 16:04:32) * ACTION: quaid to start new thread ASAP (quaid, 16:04:51) * Trac review (quaid, 16:06:02) * LINK: https://fedorahosted.org/ovirt/report/1 (quaid, 16:06:11) * LINK: https://fedorahosted.org/ovirt/ticket/10 (quaid, 16:06:47) * renaming of mailing list arch > devel is happening after the www/wiki transfer is all worked out, priority-wise (quaid, 16:07:16) * ACTION: quaid needs to put together a migration plan, so people are warned to fix mail filter rules, etc. (quaid, 16:07:37) * LINK: https://fedorahosted.org/ovirt/ticket/11 (quaid, 16:07:55) * slow mailing list show resolve when we move it to Alter Way, leaving this open for now so we can be sure it is better (quaid, 16:08:11) * LINK: https://fedorahosted.org/ovirt/ticket/13 (quaid, 16:08:46) * Is this an Infra task? (quaid, 16:09:06) * ACTION: quaid to find out if this is an Infra ticket or now (quaid, 16:09:15) * LINK: https://fedorahosted.org/ovirt/ticket/5 (quaid, 16:09:43) * We'll need to have a how to file a ticket process in place one before doing all the hosting switching (quaid, 16:10:18) * ACTION: quaid to takeover this ticket (quaid, 16:10:53) * LINK: https://fedorahosted.org/ovirt/ticket/12 (quaid, 16:11:20) * ACTION: quaid to revive the thread on this, get it fixed or lined up to change with new hosting (quaid, 16:11:59) Meeting ended at 16:14:54 UTC. Action Items ------------ * quaid to arrange DNS cutover timing based on the idea that we'll have this working within 2 days * quaid to tell people status of 'broken' script & to please hang on * quaid to move this topic to the end of the agenda permanently * quaid, dcaro, dneary will help ewoud with Puppet manifests * we should consider using openid auth in new jenkins server * eedri will work on OpenID for Jenkins * oVirt Infra to make a Foreman feature request to have OpenID * quaid to look in to MediaWiki and OpenID * quaid to start new thread ASAP * quaid needs to put together a migration plan, so people are warned to fix mail filter rules, etc. * quaid to find out if this is an Infra ticket or now * quaid to takeover this ticket * quaid to revive the thread on this, get it fixed or lined up to change with new hosting Action Items, by person ----------------------- * dcaro * quaid, dcaro, dneary will help ewoud with Puppet manifests * dneary * quaid, dcaro, dneary will help ewoud with Puppet manifests * eedri * eedri will work on OpenID for Jenkins * ewoud * quaid, dcaro, dneary will help ewoud with Puppet manifests * quaid * quaid to arrange DNS cutover timing based on the idea that we'll have this working within 2 days * quaid to tell people status of 'broken' script & to please hang on * quaid to move this topic to the end of the agenda permanently * quaid, dcaro, dneary will help ewoud with Puppet manifests * quaid to look in to MediaWiki and OpenID * quaid to start new thread ASAP * quaid needs to put together a migration plan, so people are warned to fix mail filter rules, etc. * quaid to find out if this is an Infra ticket or now * quaid to takeover this ticket * quaid to revive the thread on this, get it fixed or lined up to change with new hosting * **UNASSIGNED** * we should consider using openid auth in new jenkins server * oVirt Infra to make a Foreman feature request to have OpenID People Present (lines said) --------------------------- * quaid (140) * eedri (30) * ewoud (28) * dneary (21) * dcaro (7) * garrett_ (5) * ovirtbot (5) * karimb (4) * ohadlevy (3) * sgordon (1) * adrian15 (1) * Rydekull (1) Generated by `MeetBot`_ 0.1.4 =2E. _`MeetBot`: http://wiki.debian.org/MeetBot --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigA5EC8749940004E757F83E0B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iD8DBQFQs5ZL2ZIOBq0ODEERAgk6AJ404KpaLEaqYlU4Msn09oUvrp5MOQCfdEKk CYGE8jUnPkOK/Rb18MJeYVo= =F44F -----END PGP SIGNATURE----- --------------enigA5EC8749940004E757F83E0B--
On 11/26/2012 11:18 AM, Karsten 'quaid' Wade wrote: ...
* Hosting (quaid, 15:20:56) * My Red Hat IT contact told me last week he is provisioning two servers at RackSpace for us, bare metal to use as we wish (quaid, 15:21:23)
are these physical machines or VMs? if VMs, do they support nested virt?
* Gerrit (quaid, 16:02:06) * I think the Infra git repo is available, but I haven't put anything in it (quaid, 16:02:26)
i tried to follow the thread, but could discern the summary of which repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each.
* LINK: https://fedorahosted.org/ovirt/ticket/5 (quaid, 16:09:43) * We'll need to have a how to file a ticket process in place one before doing all the hosting switching (quaid, 16:10:18)
nit: if you can have the title of the ticket in summary, would be able to read this offline/without clicking the link. thanks, Itamar
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig941BE2428AAE371D0C12DFB7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/27/2012 12:08 PM, Itamar Heim wrote:
On 11/26/2012 11:18 AM, Karsten 'quaid' Wade wrote: ...
* Hosting (quaid, 15:20:56) * My Red Hat IT contact told me last week he is provisioning two servers at RackSpace for us, bare metal to use as we wish (quaid, 15:21:23) =20 are these physical machines or VMs? if VMs, do they support nested virt?
Physical machines at RackSpace, AIUI. The specs are roughly what we requested from AlterWay, without the superfast I/O to disk. 4 to 8 cores, 8 to 16 GB RAM, plenty of harddisk. (I'd like to talk about setting up e.g. GlusterFS with our extra hard disk space.)
=20
=20 * Gerrit (quaid, 16:02:06) * I think the Infra git repo is available, but I haven't put anything in it (quaid, 16:02:26) =20 i tried to follow the thread, but could discern the summary of which=20 repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each.
We need to do that, but haven't figured it out all the way, I think? At the least, I think we need: web :: (all of Infra team) + dneary, garrett, jbrooks For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway? infra_scripts: (all of Infra team) http://wiki.ovirt.org/wiki/Infrastructure#Team
* LINK: https://fedorahosted.org/ovirt/ticket/5 (quaid, 16:09:43) * We'll need to have a how to file a ticket process in place one before doing all the hosting switching (quaid, 16:10:18) =20 nit: if you can have the title of the ticket in summary, would be able to read this offline/without clicking the link.
Will do, thanks for the tip. - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enig941BE2428AAE371D0C12DFB7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iD8DBQFQtSMu2ZIOBq0ODEERAq3GAJ9hAgyvnWj5AQOXgCPKLzvsOgSHJACfWsRt GWHCJfRQQcbFlT50UGSe7pE= =/Ajt -----END PGP SIGNATURE----- --------------enig941BE2428AAE371D0C12DFB7--
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
i tried to follow the thread, but could discern the summary of which repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each. We need to do that, but haven't figured it out all the way, I think?
At the least, I think we need:
web :: (all of Infra team) + dneary, garrett, jbrooks
For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway?
infra_scripts: (all of Infra team)
are these the final names?
On Tue, Nov 27, 2012 at 06:11:19PM -0500, Itamar Heim wrote:
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
i tried to follow the thread, but could discern the summary of which repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each. We need to do that, but haven't figured it out all the way, I think?
At the least, I think we need:
web :: (all of Infra team) + dneary, garrett, jbrooks
I'm more in favor of website, but can be fine with web.
For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway?
I'd prefer puppet here, but try to keep RPMs out of it. When we need those I'd rather make a real yum repository. Maybe keep the spec files in our scripts repo or something.
infra_scripts: (all of Infra team)
How about infra-scripts? Again, minor bike shedding but I feel it's more consistent with other repositories that also use a dash.
are these the final names?
Almost ;)
On 11/27/2012 07:29 PM, Ewoud Kohl van Wijngaarden wrote:
On Tue, Nov 27, 2012 at 06:11:19PM -0500, Itamar Heim wrote:
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
i tried to follow the thread, but could discern the summary of which repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each. We need to do that, but haven't figured it out all the way, I think?
At the least, I think we need:
web :: (all of Infra team) + dneary, garrett, jbrooks
I'm more in favor of website, but can be fine with web.
i suggest prefixing all with infra to not confuse with ovirt web. so infra-web, etc.
For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway?
I'd prefer puppet here, but try to keep RPMs out of it. When we need those I'd rather make a real yum repository. Maybe keep the spec files in our scripts repo or something.
infra_scripts: (all of Infra team)
How about infra-scripts? Again, minor bike shedding but I feel it's more consistent with other repositories that also use a dash.
are these the final names?
Almost ;) _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Wed, Nov 28, 2012 at 04:23:47AM -0500, Itamar Heim wrote:
On 11/27/2012 07:29 PM, Ewoud Kohl van Wijngaarden wrote:
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
[we need a git repository on gerrit for our website]
web :: (all of Infra team) + dneary, garrett, jbrooks
I'm more in favor of website, but can be fine with web.
i suggest prefixing all with infra to not confuse with ovirt web. so infra-web, etc.
I thinking about something similar so +1 from me.
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0273555AB4A102606EC9161E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/27/2012 04:29 PM, Ewoud Kohl van Wijngaarden wrote:
On Tue, Nov 27, 2012 at 06:11:19PM -0500, Itamar Heim wrote:
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
i tried to follow the thread, but could discern the summary of whic= h repos you want (separate for foreman/puppet, etc.). please summariz= e for me name of repos and maintainers for each. We need to do that, but haven't figured it out all the way, I think?
At the least, I think we need:
web :: (all of Infra team) + dneary, garrett, jbrooks =20 I'm more in favor of website, but can be fine with web.
infra-website sounds good to me - combine the suggestions. :)
For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway? =20 I'd prefer puppet here, but try to keep RPMs out of it. When we need
=20 those I'd rather make a real yum repository. Maybe keep the spec files in our scripts repo or something.
infra-puppet? Right, so all scripts Puppet is going to run come from infra-puppet. We can make a yum repo of RPMs later, if needed. Is that correct?
infra_scripts: (all of Infra team) =20 How about infra-scripts? Again, minor bike shedding but I feel it's mor= e consistent with other repositories that also use a dash.
Nope, you are correct - infra-scripts is better. Anything else we're missing here? For maintainers: infra-website Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade Dave Neary Garrett Lesage Jason Brooks infra-scripts Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade infra-puppet Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enig0273555AB4A102606EC9161E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iD8DBQFQtj9T2ZIOBq0ODEERAjBlAJ9+lv7PreBjQum5h8G2DN0KLxb8OgCgljVI 2jaS8ziVK01hq96IVpd/yuY= =lODZ -----END PGP SIGNATURE----- --------------enig0273555AB4A102606EC9161E--
On 11/28/2012 11:44 AM, Karsten 'quaid' Wade wrote:
On 11/27/2012 04:29 PM, Ewoud Kohl van Wijngaarden wrote:
On Tue, Nov 27, 2012 at 06:11:19PM -0500, Itamar Heim wrote:
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
i tried to follow the thread, but could discern the summary of which repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each. We need to do that, but haven't figured it out all the way, I think?
At the least, I think we need:
web :: (all of Infra team) + dneary, garrett, jbrooks
I'm more in favor of website, but can be fine with web.
infra-website sounds good to me - combine the suggestions. :)
For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway?
I'd prefer puppet here, but try to keep RPMs out of it. When we need those I'd rather make a real yum repository. Maybe keep the spec files in our scripts repo or something.
infra-puppet?
Right, so all scripts Puppet is going to run come from infra-puppet. We can make a yum repo of RPMs later, if needed. Is that correct?
infra_scripts: (all of Infra team)
How about infra-scripts? Again, minor bike shedding but I feel it's more consistent with other repositories that also use a dash.
Nope, you are correct - infra-scripts is better.
Anything else we're missing here?
For maintainers:
infra-website Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade Dave Neary Garrett Lesage Jason Brooks
infra-scripts Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade
infra-puppet Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade
just ping me when these are final and i'll create them. thanks
On Wed, Nov 28, 2012 at 08:44:03AM -0800, Karsten 'quaid' Wade wrote:
On 11/27/2012 04:29 PM, Ewoud Kohl van Wijngaarden wrote:
On Tue, Nov 27, 2012 at 06:11:19PM -0500, Itamar Heim wrote:
On 11/27/2012 03:31 PM, Karsten 'quaid' Wade wrote:
i tried to follow the thread, but could discern the summary of which repos you want (separate for foreman/puppet, etc.). please summarize for me name of repos and maintainers for each. We need to do that, but haven't figured it out all the way, I think?
At the least, I think we need:
web :: (all of Infra team) + dneary, garrett, jbrooks
I'm more in favor of website, but can be fine with web.
infra-website sounds good to me - combine the suggestions. :)
For Foreman/Puppet, I'm not sure yet. What I would have put in git before (scripts, etc.) will be RPMs for Puppet to consume. But maybe we need a source control for that anyway?
I'd prefer puppet here, but try to keep RPMs out of it. When we need those I'd rather make a real yum repository. Maybe keep the spec files in our scripts repo or something.
infra-puppet?
Right, so all scripts Puppet is going to run come from infra-puppet. We can make a yum repo of RPMs later, if needed. Is that correct?
Correct
infra_scripts: (all of Infra team)
How about infra-scripts? Again, minor bike shedding but I feel it's more consistent with other repositories that also use a dash.
Nope, you are correct - infra-scripts is better.
Anything else we're missing here?
For maintainers:
infra-website Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade Dave Neary Garrett Lesage Jason Brooks
infra-scripts Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade
infra-puppet Mike Burns Eyal Edri Itamar Heim Ewoud Kohl van Wijngaarden Robert Middleswarth Ofer Schreiber Karsten Wade
+1
participants (3)
-
Ewoud Kohl van Wijngaarden -
Itamar Heim -
Karsten 'quaid' Wade