1 |
On Fri, 2003-02-07 at 19:46, Yannick Koehler wrote: |
2 |
> On February 7, 2003 01:41 pm, Vano D wrote: |
3 |
> > Sorry for double posting. |
4 |
> > |
5 |
> > If that idea is extended and assuming that you have different machines |
6 |
> > with different specs in a big organisation you want to deploy |
7 |
> > gentoo clients to, you can in effect have a |
8 |
> > "configuration management center" server to configure and |
9 |
> > manage software in all of the gentoo machines in that organisation. |
10 |
> > |
11 |
> > Ofcourse if all machines have the same specs you can still use this system |
12 |
> > but without the need to compile software for each machine. |
13 |
> > |
14 |
> > I think the idea is very interesting and can be usefull. |
15 |
> |
16 |
> Which brings up a ver old idea that I again posted on gentoo last summer about |
17 |
> having a script exporting all config file in an xml database/tree and have |
18 |
> utilities developped to display/present/change this information and then make |
19 |
> that information transform back into the original /etc files. |
20 |
> |
21 |
> One could then export the xml and re-import it inside another system. Even |
22 |
> better, would be that you could configure more than simply linux because the |
23 |
> notion of "users" can easily exists in other system and using xslt on an xml |
24 |
> could help converting it to another similar format for the target platform. |
25 |
|
26 |
It is interesting that this issue came up because I have a friend whose |
27 |
end of year university project was the management and configuration of |
28 |
software using tools which interacted with xml templates. Each software |
29 |
configuration file (such as proftpd's config files or samba's) is |
30 |
configured via xml with the use of xml schema defining the config files. |
31 |
|
32 |
You then make "software modules" for each software package you want (or |
33 |
in another words make the xml schema for the configuration file(s), |
34 |
default values, dependencies between directives and values, and a set of |
35 |
default/secure rules) |
36 |
|
37 |
He then developed GUI tools to modify the xml parameters locally and |
38 |
remotely. The whole system also includes dependencies and security |
39 |
(originally the whole idea was for security, so say if you define an XYZ |
40 |
directive in Samba it won't compromise the system because you also had |
41 |
an ABC directive somewhere else.. etc. So in effect the whole system |
42 |
with its dependencies and default/set rules takes care of security and |
43 |
as a side effect: easy configuration). |
44 |
|
45 |
Just thought to let you know about that project since you seem to be |
46 |
interested in the same topic. I think if Gentoo is used with such a |
47 |
system and with the ideas discussed in previous posts, you could have |
48 |
one powerfull ((semi)auto) configuration management system with all its |
49 |
bells and whistles. |
50 |
|
51 |
Check http://inseguro.org/ it's all in Spanish unfortunately. You have |
52 |
some screenshots of his GUIs for the configuration management. Also rpm |
53 |
binaries for RedHat. He intends to release the code for everything when |
54 |
it reaches 1.0. |
55 |
|
56 |
-- |
57 |
Vano D <gentoo-dev@××××××××××××××××.com> |
58 |
|
59 |
|
60 |
-- |
61 |
gentoo-dev@g.o mailing list |