5,705
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − There are two kinds of Puppet recipes:+ − * Puppet modules that are abstracted from final usage on particular Sugar Labs sites,+ − * and recipes that composite modules and describe final configurations of Sugar Labs services. − − === Modules === − − Puppet modules configure particular services (e.g., mysqld) and are not tied to final configurations. All modules are collected as repositories in [http://git.sugarlabs.org/puppets puppets] Gitorious project. Modules might be created from scratch or mirrored from upstream, so, all modules that are used within Sugar Labs are stored in one place. Module repository might have followed branches: Line 18:
Line 13: − + + + − Final recipes are stored on [[Machine/lightwave|puppetmaster host]] in private git repository:+ Line 56:
Line 53: − + + + + + + + + − + + + + + − End-usage nodes. Configuration settings are tracked by local git repository only since contain private data.+ + − === jita.sugarlabs.org ===+
Infrastructure Team/Puppet (view source)
Revision as of 16:10, 14 November 2010
, 16:10, 14 November 2010no edit summary
Sugar Labs Puppet infrastructure.
Sugar Labs Puppet infrastructure.
== Recipes ==
== Modules ==
Puppet modules configure particular services like [[Service/git|git.sugarlabs.org]] or MySQL but not tied to final configurations, they are being configured from [[#Master|puppetmaster]].
All modules are collected as repositories in [http://git.sugarlabs.org/puppets puppets] Gitorious project. Modules might be created from scratch or mirrored from upstream, so, all modules that are used within Sugar Labs are stored in one place. Module repository might have followed branches:
* ''master'', development version (might be absent if project is mirrorred from upstream),
* ''master'', development version (might be absent if project is mirrorred from upstream),
Auto generated [http://api.sugarlabs.org/puppets/ documentation].
Auto generated [http://api.sugarlabs.org/puppets/ documentation].
=== Final configuration ===
== Master ==
Only puppetmaster keeps final configuration for all Sugar Labs services. It is being started on [[Machine/lightwave|security machine]] in private git repository.
=== Private repository ===
* {{Code|/var/lib/puppet/etc/puppet.git}}
* {{Code|/var/lib/puppet/etc/puppet.git}}
sleep 3
sleep 3
Git repository has submodules to all, used on all puppetized hosts, modules from [http://git.sugarlabs.org/puppets puppets] project. All submodules are checked out to ''production'' branch.
=== Repository hierarchy ===
Git repository consists of:
* {{Code|modules/}}, all used modules from [http://git.sugarlabs.org/puppets puppets] project in form of submodules.
* {{Code|manifests/site.pp}}, main recipe which contain common settings and includes nodes.
* {{Code|manifests/roles/}}, recipes that describes final configuration for particular service.
* {{Code|manifests/nodes/}}, puppetized nodes, configuration for hosts that ask puppetmaster.
== Nodes ==
== Nodes ==
''In progress''
Hosts that fetch configuration from the [[#Master|puppetmast]] need <code>puppet >= 2.6</code> package. If {{Code|puppet}} was installed from gems, it needs to be initially configured:
puppetmasterd --mkusers
Node's puppet agent might have optional configuration in {{Code|/etc/puppet/puppet.conf}}:
[main]
runinterval = <fetch-configuration-in-every-n-seconds>
Every puppetized host should have particular node file in {{Code|manifests/nodes/<host-name>.pp}} on [[#Master|puppetmaster]].