Re: jenkins slaves

Hi Douglas, On 07/11/2012 07:41 AM, Douglas Landgraf wrote: 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! I just checked http://jenkins.ovirt.org/job/vdsm_unit_tests/ and it looks like the dependency issue was taken care of a day or two ago. Can you confirm that all is well now? Thanks, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62