245:
configuration schema. For example, the component that manages user accounts is registered with the path /software/components/accounts. A dispatcher program running on the node performs an analysis of the freshly retrieved configuration for changes in the relevant sections, and triggers the appropriate components. Run-time dependencies may be expressed in the node's profile, so that a partial order can be enforced on component execution. For example, it is important that the user accounts component runs before the file creation component, to ensure that file ownership can be correctly specified.
22:
127:, improving it in several aspects. At the core of Quattor is Pan, a high-level, typed language with flexible include mechanisms, a range of data structures, and validation features familiar to modern programmers. Pan allows collaborative administrators to build up a complex set of configuration templates describing service types, hardware components, configuration parameters, users etc. The use of a high-level language facilitates code reuse in a way that goes beyond cut-and-paste of configuration snippets.
184:. The extensive validation features in the Pan language maximize the probability of finding configuration problems at compile time, minimizing costly clean-ups of deployed misconfiguration. Pan enables system administrators to define atomic or compound types with associated validation functions; when a part of the configuration schema is bound to a type, the declared constraints are automatically enforced.
208:
load-path with the name-spacing to achieve this. The compiler uses the load-path to search multiple root directories for particular, named templates; the first version found on the load-path is the one that is used by the compiler. This allows modules to be kept in a pristine state while allowing sites to override any particular template.
135:
the architecture of the configuration system itself. Sometimes a set of highly autonomous sites wish to collaborate loosely. In this case each site will host a fairly comprehensive set of configuration servers, with common configuration information being retrieved from a shared database and integrated with the local configuration.
157:
fine-grained control (an ACL can be attached to each template). When many users interact with the system, conflicts and misconfiguration may arise which require a roll back mechanism; to this purpose, a simple concurrent transaction mechanism, based on standard version control systems, was implemented.
177:
by system administrators and produces XML or JSON files (profiles) that are easily consumed by
Quattor clients. The Pan language itself has a simple, declarative syntax that allows simultaneous definition of configuration information and an associated schema. In this section, we focus only on the Pan
161:
database, and finally the deployment is initiated by invoking a separate operation on the server. The centralized approach provides strict control of configuration data. The compilation burden is placed onto the central server, and users can only access and modify templates via a dedicated interface.
152:
Quattor's configuration management system is composed of a configuration database that stores high-level configuration templates, the Pan compiler that validates templates and translates them to XML or JSON profiles, and a machine profile repository that serves the profiles to client nodes. Only the
134:
Devolved management includes the following features: consistency over a multi-site infrastructure, multiple management points, and the ability to accommodate the specific needs of constituent sites. There is no single “correct” model for a devolved infrastructure, thus great flexibility is needed in
119:
The challenge of structuring and sharing components in a collaborative system is not new; over the years programming language designers have attacked this problem from many angles. While trends change, the basic principles are well understood. Features such as encapsulation, abstraction, modularity,
89:
is a generic open-source tool-kit used to install, configure, and manage computers. Quattor was originally developed in the framework of
European Data Grid project (2001-2004). Since its first release in 2003, Quattor has been maintained and extended by a volunteer community of users and developers,
199:
A full site configuration typically consists of a large number of templates organized into directories and subdirectories. The Pan template name-spacing mimics (and enforces) this organization much as is done in the Java language. The name-space hierarchy is independent of the configuration schema.
130:
The principles embodied in
Quattor are in line with those established within the system administration community. In particular, all managed nodes retrieve their configurations from a configuration server backed by a source-control system (or systems in the case of devolved management). This allows
101:
Shared
Configuration and Management Efficiency: Quattor encourages the re-use of configuration information in such a way that it can be distributed and used with little or no modification at different sites, facilitating the distribution of best practices without the need for each site to implement
256:
While nodes normally update themselves automatically, administrators can configure the system to disable automatic change deployment. This is crucial in a devolved system where the responsibilities for, respectively, modifying and deploying the configuration may be separated. A typical scenario is
164:
Since the two paradigms provide essentially the same functionality, the choice between them depends on which fits the management model of an organization better. For instance, the centralized approach fits large computer centres well because of its strictly controlled work-flow, whereas multi-site
207:
The name-spacing allows various parts of the configuration to be separated and identified. To effectively modularize part of the configuration for reuse, administrators must be able to import the modules easily into a site's configuration and to customize them. Users of the Pan compiler combine a
160:
Quattor's modular architecture allows the three configuration management subsystems to be deployed in either a distributed or centralized fashion. In the distributed approach, profile compilation (at development stage) is carried out on client systems, templates are then checked into a suitable
90:
primarily from the community of grid system administrators. The
Quattor tool-kit, like other configuration management systems, reduces the staff required to maintain a cluster and facilitates reliable change management. However, three unique features make it particularly attractive for managing
156:
Devolved management in a cross-domain environment requires users to be authenticated and their operations to be authorized. For the configuration database X.509 certificates can be used because of the support offered by many standard tools, and access control lists (ACLs) because they allow a
138:
Distributing the management task can potentially introduce new costs. For example, transmitting configuration information over the WAN introduces latency and security concerns. Quattor allows servers to be placed at appropriate locations in the infrastructure to reduce latency, and the use of
244:
In
Quattor, managed nodes handle their configuration process autonomously; all actions are initiated locally, once the configuration profile has been retrieved from the repository. Each node has a set of configuration agents (components) that are each registered with a particular part of the
231:
A key feature for administering large distributed infrastructures is the ability to automatically install machines, possibly from a remote location. To this purpose, Quattor provides a modular framework called the
Automated Installation Infrastructure (AII). This framework is responsible for
190:. Pan allows identification and reuse of configuration information through “structure templates.” These identify small, reusable chunks of Pan-level configuration information which can be used whenever an administrator identifies an invariant (or nearly invariant) configuration sub-tree.
110:
These features are also attractive beyond the grid context. This has been confirmed by the growing adoption of
Quattor, by both large commercial organisations and academic institutions, most of them using the tool-kit to manage consistently their grid and non-grid systems.
232:
translating the configuration parameters embodied in node profiles into installation instructions suitable for use by standard installation tools. Current AII modules use node profiles to configure DHCP servers, PXE boot and
Kickstart-guided installations.
235:
Normally AII is set up with an install server at each site. However, the above-mentioned technologies allow the transparent implementation of multi-site installations, by setting up a central server and appropriate relays using standard protocols.
257:
that top-level administrators manage the shared configuration of multiple remote sites and local managers apply it according to their policies. For instance, software updates might be scheduled at different times.
248:
By design, no control loop is provided for ensuring the correct execution of configuration components. Site administrators typically use standard monitoring systems to detect and respond to configuration failures.
211:
Further, module developers can also expose global variables to parameterize the module, permitting a system administrator to use a module without having to understand the inner workings of the module's templates.
105:
Coherent Site Model: Quattor allows an administrator to develop a site model that, once constructed, can be used to manage a range of different resources, such as real machines, virtual machines and cloud
253:
and Lemon are both being used at
Quattor sites for this purpose. In fact, Lemon has been developed in tandem with Quattor, and provides sensors to detect failures in Quattor component execution.
266:
204:
entries, and the like. In contrast, the Pan templates are usually organized based on other criteria like high-level services (web server, mail server, etc.) or by responsible person/group.
196:. With respect to the original design, two new features have been developed to promote modularization and large-scale reuse of configurations: the name-spacing and load-path mechanisms.
98:
Federated Management: The open, modular nature of the tool-kit permits system administrators at different institutes to share the management of their distributed resources.
139:
standard tools and protocols means that existing security systems (such as a public key infrastructure) can be harnessed to encrypt and authenticate communications.
51:
165:
organizations such as GRIF prefer the distributed approach because it allows different parts of the whole configuration set to be handled autonomously.
131:
individual nodes to be recreated in the case of hardware failure. Quattor handles both distributed and traditional (single-site) infrastructures.
120:
and typing produce clear benefits. We believe that similar principles apply when sharing configuration information across administrative domains.
200:
The configuration schema is often organized by low-level services such as firewall settings for ports, account generation, log rotation entries,
153:
Pan compiler is strictly necessary in a Quattor system; the other two subsystems can be replaced by any service providing similar functionality.
351:
73:
306:
356:
178:
features that are relevant to devolved management of distributed sites: validation, configuration reuse, and modularization.
173:
The Pan language compiler panc sits at the core of the Quattor tool-kit. It compiles machine configurations written in the
174:
34:
44:
38:
30:
346:
55:
321:
311:
219:
services. The QWG templates use all of the features of Pan to allow distributed sites to share grid
286:
326:
91:
340:
331:
220:
216:
250:
316:
215:
Quattor Working Group (QWG) templates are used to configure grid
123:
The Quattor configuration tool-kit derives its architecture from
201:
124:
15:
287:
http://www.wallstreetandtech.com/it-infrastructure/216402934
267:
Comparison of open source configuration management software
301:
43:but its sources remain unclear because it lacks
8:
74:Learn how and when to remove this message
278:
7:
14:
332:Documentation on the Pan language
227:Automated installation management
20:
327:Journal of Grid Computing Paper
148:Configuration management system
1:
240:Node configuration management
285:Wall Street and Technology,
373:
175:Pan configuration language
352:Configuration management
29:This article includes a
58:more precise citations.
102:configuration changes.
357:System administration
307:Quattor Case Studies
143:Quattor Architecture
188:Configuration reuse
312:StratusLab Project
31:list of references
84:
83:
76:
364:
317:Quattor on Ohloh
302:Quattor Homepage
289:
283:
79:
72:
68:
65:
59:
54:this article by
45:inline citations
24:
23:
16:
372:
371:
367:
366:
365:
363:
362:
361:
337:
336:
298:
293:
292:
284:
280:
275:
263:
242:
229:
171:
150:
145:
117:
80:
69:
63:
60:
49:
35:related reading
25:
21:
12:
11:
5:
370:
368:
360:
359:
354:
349:
339:
338:
335:
334:
329:
324:
319:
314:
309:
304:
297:
296:External links
294:
291:
290:
277:
276:
274:
271:
270:
269:
262:
259:
241:
238:
228:
225:
194:Modularization
170:
167:
149:
146:
144:
141:
116:
113:
108:
107:
103:
99:
82:
81:
39:external links
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
369:
358:
355:
353:
350:
348:
347:Unix software
345:
344:
342:
333:
330:
328:
325:
323:
322:LISA 08 Paper
320:
318:
315:
313:
310:
308:
305:
303:
300:
299:
295:
288:
282:
279:
272:
268:
265:
264:
260:
258:
254:
252:
246:
239:
237:
233:
226:
224:
222:
218:
213:
209:
205:
203:
197:
195:
191:
189:
185:
183:
179:
176:
168:
166:
162:
158:
154:
147:
142:
140:
136:
132:
128:
126:
121:
114:
112:
104:
100:
97:
96:
95:
93:
88:
78:
75:
67:
64:December 2022
57:
53:
47:
46:
40:
36:
32:
27:
18:
17:
281:
255:
247:
243:
234:
230:
214:
210:
206:
198:
193:
192:
187:
186:
181:
180:
172:
169:Pan language
163:
159:
155:
151:
137:
133:
129:
122:
118:
109:
86:
85:
70:
61:
50:Please help
42:
223:expertise.
94:resources:
56:introducing
341:Categories
273:References
221:middleware
217:middleware
182:Validation
115:Principles
106:resources.
261:See also
87:Quattor
52:improve
251:Nagios
37:, or
202:cron
125:LCFG
92:grid
343::
41:,
33:,
77:)
71:(
66:)
62:(
48:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.