On-going maintainance with puppet (for UEC and more)

Registered by Mathias Gug on 2010-10-15

As a UEC admin I can move one Node Controller to another Cluster without logging into the NC by updating a recipe on the puppet service.
As a UEC admin I can easily deploy new NC.

Notes: provide a puppet service to manage UEC itself, provide puppet recipes to manage each component of UEC and integrate them together.

Blueprint information

Status:
Not started
Approver:
Robbie Williamson
Priority:
Undefined
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Review
Series goal:
None
Implementation:
Deferred
Milestone target:
None

Related branches

Sprints

Whiteboard

Work Items:
Create puppetmaster-webrick package and turn puppetmaster into a meta-package depending on puppetmaster-webrick | puppetmaster-passenger.
Investigate feasibility of promoting passenger to main.
Switch default puppetmaster package to run under passenger rather than webrick.
Write puppet module for UEC CLC, Walrus.
Write puppet module for UEC SC, CC.
Write puppet module for UEC NC.
Ship all recipes in a single UEC package in /etc/puppet/modules/.
Write documentation to outline how to deploy UEC with a puppetmaster running on UEC CLC.
Install puppetmaster on the CLC by default.

================
UDS Natty discusion
================

* Run Puppet Master under Passenger.
 * May need modpassenger in Main, but may have issues with dependencies.

* Define UEC compenents as puppet classes and modules.
* Have recipes in packages, or a package of recipes
 * Recipes should probably be in /etc/puppet rather than /usr/share/puppet.
 * For Natty create /etc/puppet/modules.

* Installation Service can live on the same box as the Puppet Master.

(?)

Work Items