From: "Douglas Landgraf" <dougsland(a)redhat.com&gt; To: infra(a)ovirt.org Cc: "Barak Azulay" <bazulay(a)redhat.com&gt; Sent: Monday, July 9, 2012 5:29:37 PM Subject: jenkins slaves Hi, My name is Douglas Schilling Landgraf, I work for Red Hat to provide improvements for VDSM/oVirt. I have noticed that jenkins vdsm_unit_tests project failed because of a package dependency. If possible, can I have access to jenkins slaves to help maintain this VDSM test project? Thanks! -- Cheers Douglas _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

From: "Douglas Landgraf" <dougsland(a)redhat.com&gt; To: "Eyal Edri" <eedri(a)redhat.com&gt; Cc: "Barak Azulay" <bazulay(a)redhat.com&gt;, infra(a)ovirt.org Sent: Wednesday, July 11, 2012 8:41:04 AM Subject: Re: jenkins slaves Hi Eyal, On 07/10/2012 02:53 AM, Eyal Edri wrote: > Hi Douglas, > > If any dependency is missing you can always send an email to > infra(a)ovirt.org and request to install it. ok > As for getting access to Jenkins slaves in ovirt -> that requires > being a member of the infra team and approval of > its memebers/trust seeds. > > If you feel you want to contribute to the oVirt infra team, please > send a request to infra(a)ovirt.org with some background > (team, project, redhat exp,etc...). hum, could you please provide a detailed example?

> > for now, please provide the missing rpms you know are failing the > tests and i'll look into fixing it. Can you please confirm if cherrypy (and all dependencies) is installed? (As Dan pointed) > thanks, > > Eyal Edri > Thanks! > > ----- Original Message ----- >> From: "Douglas Landgraf&quot;&lt;dougsland(a)redhat.com&gt; >> To: infra(a)ovirt.org >> Cc: "Barak Azulay&quot;&lt;bazulay(a)redhat.com&gt; >> Sent: Monday, July 9, 2012 5:29:37 PM >> Subject: jenkins slaves >> >> Hi, >> >> My name is Douglas Schilling Landgraf, I work for Red >> Hat to >> provide improvements for VDSM/oVirt. >> I have noticed that jenkins vdsm_unit_tests project failed because >> of >> a >> package dependency. >> If possible, can I have access to jenkins slaves to help maintain >> this >> VDSM test project? >> >> >> Thanks! >> >> -- >> Cheers >> Douglas >> >> _______________________________________________ >> Infra mailing list >> Infra(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> -- Cheers Douglas

From: "Dave Neary" <dneary(a)redhat.com&gt; To: infra(a)ovirt.org Sent: Wednesday, July 11, 2012 11:45:12 AM Subject: Re: jenkins slaves Hi, On 07/11/2012 09:58 AM, Eyal Edri wrote: > Guys, do we have a formal way of accepting new people to the infra > team? > what should the do, what kind of background the need to provide? > is it enough if they work in one the supporting companies? That's what Karsten, Robert, Mike, Itamar, you and others are working on at the moment (between the mission statement, the "trust seed", managing configs with Puppet, and we still need to figure out how we can graduate involvement and trust so that people not on the team can make positive contributions and thus build reputation and join the team.

Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62 _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Hi, On 07/11/2012 09:58 AM, Eyal Edri wrote: > Guys, do we have a formal way of accepting new people to the > infra team? what should the do, what kind of background the need > to provide? is it enough if they work in one the supporting > companies?

That's what Karsten, Robert, Mike, Itamar, you and others are working on at the moment (between the mission statement, the "trust seed", managing configs with Puppet, and we still need to figure out how we can graduate involvement and trust so that people not on the team can make positive contributions and thus build reputation and join the team.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP/Y/b2ZIOBq0ODEERAkxgAKCqBb+54PwwWAVvcw75C9OpilCACQCfZrnD N4afndIlHXOXq10NUJT0tww= =f0rT -----END PGP SIGNATURE-----

Hi Douglas, On 07/11/2012 07:41 AM, Douglas Landgraf wrote: > On 07/10/2012 02:53 AM, Eyal Edri wrote: >> If you feel you want to contribute to the oVirt infra team, please >> send a request to infra(a)ovirt.org with some background >> (team, project, redhat exp,etc...). > > hum, could you please provide a detailed example? The infrastructure team is working on better enabling people outside the team to join at the moment (see "Trust seed" and mission statement threads for more detail) - the general plan is to have the configuration for all of oVirt's infrastructure managed by Puppet, and to liberally provide access to interested people (like yourself) who have shown an ability to correctly identify, characterise and propose a fix for infra issues. One example relative to me (although I have no desire to be on the infra team at the moment) is my proposal to modify how we sign people up for new accounts in the wiki - the current method is to have existing wiki users add new user accounts, but if you don't know anyone in the project that doesn't really work.

My proposal is to have requests for new wiki accounts added to a moderation queue - I sourced the module and would be prepared to check it out on a local instance of MediaWiki, and document any configuration options we need to do to get it enabled. Basically, do all the ground work for the sysadmin who will install it. In your case, you helped by pointing out the failing module, and characterising the problem (missing cherry-py dependency) which made it easier to fix the problem. From there, it's a small step to have someone say "look good, please go ahead and fix that - here's how to connect to (whatever resource)". At least, I hope so!

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/10/2012 10:41 PM, Douglas Landgraf wrote: > Hi Eyal, > > On 07/10/2012 02:53 AM, Eyal Edri wrote: >> Hi Douglas, >> >> If any dependency is missing you can always send an email to >> infra(a)ovirt.org and request to install it. > ok >> As for getting access to Jenkins slaves in ovirt -> that >> requires being a member of the infra team and approval of its >> memebers/trust seeds. >> >> If you feel you want to contribute to the oVirt infra team, >> please send a request to infra(a)ovirt.org with some background >> (team, project, redhat exp,etc...). > hum, could you please provide a detailed example? Douglas, sorry, you happened to arrive just as we are more formally creating the Infra team, which means we are just figuring out how to give out access, and so forth. Your question is a good one, we need to get that up on our wiki page so it's clear what we mean by contributing to get involved.

In the meantime, if we cannot be your eyes-in-the-shell for you ... I'm wondering if you could diagnose with basic user ssh access? I.e., without sudo. Then another of us can do the actual fix, etc. (That also would be an example of contributing, and similar to how we're looking to set things up with limited ssh, Puppet, configs in git, etc.)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/2012 10:08 AM, Douglas Landgraf wrote: > Hi Karsten, > > On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 07/10/2012 10:41 PM, Douglas Landgraf wrote: >>> Hi Eyal, >>> >>> On 07/10/2012 02:53 AM, Eyal Edri wrote: >>>> Hi Douglas, >>>> >>>> If any dependency is missing you can always send an email to >>>> infra(a)ovirt.org and request to install it. >>> ok >>>> As for getting access to Jenkins slaves in ovirt -> that >>>> requires being a member of the infra team and approval of >>>> its memebers/trust seeds. >>>> >>>> If you feel you want to contribute to the oVirt infra team, >>>> please send a request to infra(a)ovirt.org with some >>>> background (team, project, redhat exp,etc...). >>> hum, could you please provide a detailed example? >> Douglas, sorry, you happened to arrive just as we are more >> formally creating the Infra team, which means we are just >> figuring out how to give out access, and so forth. Your question >> is a good one, we need to get that up on our wiki page so it's >> clear what we mean by contributing to get involved. > Thanks for the feedback. If I could suggest a possible evaluation > for cases like mine (which require shell access): > > * This person contain contributions in the upstream project? (git > log, wiki, QA, documentation, etc. Could help to determine) * The > upstream maintainer of project [agree/trust] with that? (need to > contact maintainer) Agreed those are valuable. Question is, would that same criteria help get me commit access to ovirt-engine?

>> In the meantime, if we cannot be your eyes-in-the-shell for you >> ... I'm wondering if you could diagnose with basic user ssh >> access? I.e., without sudo. Then another of us can do the actual >> fix, etc. (That also would be an example of contributing, and >> similar to how we're looking to set things up with limited ssh, >> Puppet, configs in git, etc.) > It could be a good start. However, still require contact > additional people (not good for quick fixes). Part of what we are doing is looking for the balance that lets us keep services at a professional sysadmin level. We don't want to bog ourselves down with process, but we want some consistency in what to do and how to do it (a process) so those with sudo access are coordinated. Basically, this means Infra needs to provide training materials to people.

On Wed, Jul 11, 2012 at 02:45:44PM -0400, Douglas Landgraf wrote: > Hi Karsten, > > On 07/11/2012 12:18 PM, Karsten 'quaid' Wade wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 07/11/2012 10:08 AM, Douglas Landgraf wrote: >>> Hi Karsten, >>> >>> On 07/11/2012 10:26 AM, Karsten 'quaid' Wade wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>> >>>> On 07/10/2012 10:41 PM, Douglas Landgraf wrote: >>>>> Hi Eyal, >>>>> >>>>> On 07/10/2012 02:53 AM, Eyal Edri wrote: >>>>>> Hi Douglas, >>>>>> >>>>>> If any dependency is missing you can always send an >>>>>> email to infra(a)ovirt.org and request to install it. >>>>> ok >>>>>> As for getting access to Jenkins slaves in ovirt -> >>>>>> that requires being a member of the infra team and >>>>>> approval of its memebers/trust seeds. >>>>>> >>>>>> If you feel you want to contribute to the oVirt infra >>>>>> team, please send a request to infra(a)ovirt.org with >>>>>> some background (team, project, redhat exp,etc...). >>>>> hum, could you please provide a detailed example? >>>> Douglas, sorry, you happened to arrive just as we are more >>>> formally creating the Infra team, which means we are just >>>> figuring out how to give out access, and so forth. Your >>>> question is a good one, we need to get that up on our wiki >>>> page so it's clear what we mean by contributing to get >>>> involved. >>> Thanks for the feedback. If I could suggest a possible >>> evaluation for cases like mine (which require shell access): >>> >>> * This person contain contributions in the upstream project? >>> (git log, wiki, QA, documentation, etc. Could help to >>> determine) * The upstream maintainer of project [agree/trust] >>> with that? (need to contact maintainer) >> Agreed those are valuable. Question is, would that same >> criteria help get me commit access to ovirt-engine? > I am not the right person to answer that question but from my > point of view should apply to the same/similar criteria. However, > I see your point of view. :-) Upstream maintainers (ovirt-engine, > vdsm) could help to resolve this puzzle. I'm not sure I understand the puzzle. Technically speaking, a host administer can do everything he wants. We *trust* him not do use his powers unecessarily. Preferably, there should be various levels of permissions - being able to setup Jenkins slaves should not mean automatically being able to `git rm` our repo. Since I've known Douglas for a year or so now, I trust him to never abuse his admin rights. I'm looking forward to see him in the infra team, being able to quickly fix infrastructural problems in our testing framework.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP/u9u2ZIOBq0ODEERAphIAKDInY5NuabMOztGFhzlhy3f92QD/QCgwd6M 8VtMlefP4wPgVahkVyZ+++w= =+L2n -----END PGP SIGNATURE-----