1,764
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. Model repository might have followed branches: Line 18:
Line 13: − + + + − Final recipes are stored on [[Machine/lightwave|puppetmaster host]] in private git repository:+ Line 50:
Line 47: − /bin/bash /usr/share/doc/git-core/contrib/hooks/post-receive-email + − tail -n0 -f /var/log/daemon.log & + − puppet kick --all+ − 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.+ + + + − ''In progress''+ + + + + + + − 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 19:17, 1 October 2011
, 19:17, 1 October 2011no 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 in a private git repository on [[Machine/lightwave]], which is a high security machine.
=== Private repository ===
* {{Code|/var/lib/puppet/etc/puppet.git}}
* {{Code|/var/lib/puppet/etc/puppet.git}}
#!/bin/bash
#!/bin/bash
sh /usr/share/doc/git-core/contrib/hooks/post-receive-email
git checkout -f
git checkout -f
for i in $(ls /etc/puppet/manifests/nodes/*.pp); do puppet kick $(basename $i .pp); done
=== Repository hierarchy ===
Git repository consists of:
* {{Code|manifests/site.pp}}, main recipe which contain common settings and includes nodes.
* {{Code|manifests/services/}}, recipes that describes final configuration for particular services.
* {{Code|manifests/nodes/}}, puppetized nodes, configuration for hosts that ask puppetmaster.
* {{Code|modules/}}, git submodules with Puppet [[#Modules|modules]].
== Nodes ==
== Nodes ==
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:
puppet master --mkusers
To complete configuration, execute:
puppet agent --no-daemonize --onetime --server puppet.sugarlabs.org
Every puppetized host should have particular node file in {{Code|manifests/nodes/<host-name>.pp}} on [[#Master|puppetmaster]].