[Systems] puppetization

[David Farning]

Puppetiation is going pretty well.  Puppet is a configuration management
system.  http://reductivelabs.com/products/puppet/ . The end goal is to
reduce system administration load even as we increase the number of
machine.  Instead of working on individual nodes by sshing into them
sysadmins will modify the puppet scripts.

I spent the weekend getting familiar with the system.  It is not as powerful
as bcfg2... but it is much simpler and intuitive.

The current plan is to 'test run' puppet by setting up the ASLO node with
it. While doing that I am thinking about how to puppetized the build farm.
The basic topographic layout of the infrastructure with be:

Roles (function) = Machines can serve in one or more roles such as:
webserver, database, proxy, buildfarm, wikiserver....  Roles include what
packages are installed and how they are configured.

Zone (classes) = Machines can exist in exactly one zone (or geographical
location) such as: Pika, RIT, Delver, Gnaps....  Zones include location
specific information such as administrators and private network address
ranges

Base = All Machines have several things in common.... Such as a common
name_server, backup_server, and muni_server.

Nodes = an individual machine is called a node.

This gives us the ability to define nodes as follows:

node aslo1 inherits zone_rit {

include base
include role_1
include role_2

....

Custom node stuff

....

}

david
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/private/systems/attachments/20100222/bb3eba67/attachment.htm