Difference between revisions of "Infrastructure Team/Puppet"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
Sugar Labs Puppet infrastructure. | Sugar Labs Puppet infrastructure. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Modules == | == Modules == | ||
Revision as of 13:38, 5 September 2010
Sugar Labs Puppet infrastructure.
Modules
Modules are end-usage environment independent blocks to build final configuration. All end-usage configuration happen via class/define/type arguments from out of these modules in the nodes. Modules are stored in vcs.
Low-level
util
Common infrastructure routines. Module contains only code, not any data.
firewall
High level setup of iptables.
mysql
MySQL procedures.
lighttpd
Lighttpd support.
vcsrepo
Version control systems procedures.
End applications
supybot
Setup supybot IRC bot.
bazaar
Maintain bazaar.sugarlabs.org infrastructure.
Nodes
In progress
End-usage nodes. Configuration settings are tracked by local git repository only since contain private data.