Re: Puppet proposal
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden"
<ewoud+ovirt(a)kohlvanwijngaarden.nl>
To: infra(a)ovirt.org
Sent: Tuesday, August 14, 2012 1:01:55 AM
Subject: Puppet proposal
Hello,
As promised and hopefully in time for tomorrows meeting I present to
you
some basic puppet classes and modules to help us manage our infra. I
created a github repo[1] with some very basic classes.
Some things I'm unsure about:
- I'm not sure if a dash ('-') is allowed in the class name. It works
but github highlights it weird.
- I think publishing the public key is no problem (they're public
after
all), but if something like the debian SSH fiasco[2] would happen
again we might be at risk.
- It's very basic, just ensure users exist and sudo is set up. We can
do
much more, but what do we want?
for starts we need to able to install a jenkins slave with all it's deps, this means:
1. installing all packages for making rpms (autoconf,make,gcc,python-*,etc...)
2. installing the jenkins-slave deamon (for running jnlp)
3. jenkins user + home dir..
4. openjdk-1.7.0-java-devel
5. selinux settings.. .
and basically every thing we stumble upon when installing a new slave.
other things might be installing system services on all vms like:
- log collector
- backup
- cleanup
- monitoring
In other words, here's what I worked on and I'd love to hear what you
think.
[1]: https://github.com/ekohl/ovirt-infra-puppet
[2]: http://www.debian.org/security/2008/dsa-1571
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra