1 |
On Sat, Oct 16, 2004 at 04:55:10PM +0200 or thereabouts, Jose Gonzalez Gomez wrote: |
2 |
> From my limited understanding, cfengine provides a way to centrally |
3 |
> manage hosts with common configuration, am I right? |
4 |
|
5 |
Yes. |
6 |
|
7 |
> Do you have the |
8 |
> possibility of defining "classes" of hosts? I mean, let's say I have a |
9 |
> mail server, several web servers, desktop machines.... I would like to |
10 |
> have common configurations for all of them, is this possible? |
11 |
|
12 |
Yes. You can also have common configurations for most of them, but specific |
13 |
special configurations that apply to only one or two machines. You have |
14 |
nearly limitless flexibility in defining classes. |
15 |
|
16 |
> Another question... let's say I have to install a lot of machines, I |
17 |
> understand that I just would install all the required packages, |
18 |
> configure cfengine, and then all the machines would automatically |
19 |
> configure themselves using my centrally stored configuration, am I |
20 |
> right? |
21 |
|
22 |
Yes. That's what we do now, in fact. |
23 |
|
24 |
> Can you automate the process of package installation, so maybe |
25 |
> you could have a "desktop profile/class", "mail server profile/class", |
26 |
> etc... that stores packages and their configurations? |
27 |
|
28 |
You could do this, but I wouldn't recommend storing the packages |
29 |
themselves. Instead, I'd recommend storing information about how to |
30 |
install the packages the way you want them. |
31 |
|
32 |
In other words, don't store the binaries -- store the ebuilds and have |
33 |
cfengine emerge the packages you want using those ebuilds. |
34 |
|
35 |
--kurt |