In preparation for the meeting I thought I'd write something about the
state of our puppet use.
First of all, we manage access. I think this works reasonably well, but
the workflow for completeness.
* (New) infra member creates a class ovirt_infra::user::USERNAME
* It is submitted as a review to gerrit.ovirt.org
* Once merged, it's added to the production hostgroup
* On the next puppet runs the user is created
The second big thing we do, is manage our jenkins slaves. I'm not sure I
like the workflow because it's so static. I wonder why so many system
dependencies are needed and if we can't build using mock. This ensures a
Another thing we must fix is renaming ovirt_infra::jenkins-slave to
ovirt_infra::jenkins_slave or ovirt_infra::jenkins::slave because a dash
is discouraged and broken in modern puppet versions.
The next IMHO big improvement is merging r10k deployments,
http://gerrit.ovirt.org/19141. Once that's done, I'd also like to add
tests through http://gerrit.ovirt.org/20367.
For the future I have some other ideas:
* Use puppet exported resources to automatically build the icinga
* Split linode01 into separate servers and manage those using puppet.
Comments, feedback or anything I missed?
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
We need upgrade kernel to 3.11.3-201.fc19 to make a vdsm network
functional test passed on F19 test systems. You could refer to
http://gerrit.ovirt.org/#/c/19974/ for details.
Content-Type: text/html; charset=ISO-8859-1
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<body bgcolor="#FFFFFF" text="#000000">
We need upgrade kernel to
<meta http-equiv="content-type" content="text/html;
3.11.3-201.fc19 to make a vdsm network functional test passed on F19
test systems. You could refer to <a