Difference between revisions of "Infrastructure Team/Puppet"

From Sugar Labs
Jump to navigation Jump to search
Line 14: Line 14:
 
Module resources should be registered after ''initialize'' stage and might be before ''main'' one.
 
Module resources should be registered after ''initialize'' stage and might be before ''main'' one.
  
== Low-level modules ==
+
== Modules ==
  
Modules to maintain particular applications that don't contain any data tied to end-usage environment, all configuration happen via class/define/type arguments from out of these modules. Not all module repositories might be hosted on git.sugarlabs.org.
+
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 ===
  
 
'''[http://git.sugarlabs.org/projects/puppet-util util]'''<br>
 
'''[http://git.sugarlabs.org/projects/puppet-util util]'''<br>
Line 36: Line 38:
 
Setup supybot IRC bot.
 
Setup supybot IRC bot.
  
== Sugar Labs specific modules ==
+
=== Sugar Labs specific modules ===
 
 
Modules to maintain applications that make sense only in Sugar Labs environment. Modules don't contain any data tied to end-usage environment, all configuration happen via class/define/type arguments from out of these modules. All module repositories are hosted on git.sugarlabs.org.
 
  
 
'''[http://git.sugarlabs.org/projects/puppet-bazaar bazaar]'''<br>
 
'''[http://git.sugarlabs.org/projects/puppet-bazaar bazaar]'''<br>

Revision as of 10:35, 5 September 2010

Sugar Labs Puppet infrastructure.

Run stages

Run stages were introduced in Puppet v2.6. Within Sugar Labs infrastructure there are additional, to default Puppet, stages. All puppet modules should take care about it.

Defined stages:

  • initialize only for high-level initialization on nodes level,
  • main default Puppet stage to run nodes.

Module resources should be registered after initialize stage and might be before main one.

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.

supybot
Setup supybot IRC bot.

Sugar Labs specific modules

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.

jita.sugarlabs.org