| | 1 | [[TracNav]] |
| | 2 | |
| | 3 | = Introduction = |
| | 4 | The quattor toolsuite caters for every stage of a typical system management workflow, from specification and management of configurations, to installation of new machines from scratch, to ongoing maintenance of software and services. |
| | 5 | |
| | 6 | [[image:quattor_workflow.png|center]] |
| | 7 | |
| | 8 | |
| | 9 | = Specifying configuration = |
| | 10 | In '''quattor''', templates describing computers and services are written in a declarative language called [https://trac.lal.in2p3.fr/LCGQWG/wiki/Doc/panc Pan]. The set of templates describing the configuration of a complete system are usually stored in a '''configuration database''' that provides user authorisation and version control. Pan templates are compiled to XML profiles which are then deployed to managed machines. |
| | 11 | |
| | 12 | = Installing machines = |
| | 13 | Quattor provides an automated installation infrastructure ('''AII''') that uses the information from profiles to set up an automated installation for managed machines. For example, AII will add DHCP entries and generate PXE configurations for a machine based on the network and OS settings found in its profile. AII has a plugin architecture allowing different installation mechanisms to be supported. Currently, the most commonly-used mechanism is [http://fedoraproject.org/wiki/Anaconda/Kickstart Kickstart/Anaconda] as found in RedHat-like Linux distributions. |
| | 14 | |
| | 15 | = Configuring services = |
| | 16 | On each managed machine, a set of configuration agents (or '''components''') is installed. Each agent is responsible for configuring a particular service. For example, ncm-accounts is in charge of managing local user accounts, and will add accounts specified in the machine's profile. Each agent reads its own parameters from a particular part of the profile (for example, ncm-accounts reads the list of users and groups defined at `/software/components/accounts`). |
