1 |
Devraj, |
2 |
|
3 |
I have been thinking a lot about Gentoo as enterprise distribution, wondering |
4 |
what would be missing to make it work in that role. here's what I think. |
5 |
|
6 |
Actually Gentoo has got all the characteristics to make a solid, performant |
7 |
and scalable enterprise Linux distribution but it can't achieve that role as |
8 |
it is designed and optimised to serve the needs of workstation users. That |
9 |
means for example to maximise the number of packages delivered, to deliver |
10 |
new packages as quickly as possible and to make sure that each package is |
11 |
stable individually. also, packages are compiled and used on the same |
12 |
machine. |
13 |
|
14 |
In contrast, an enterprise class package management system should not be so |
15 |
much concerned about the number of packages delivered and the speed at which |
16 |
new packages are made available but should focus on getting key |
17 |
functionalites delivered in a stable and reliable manner. How long a package |
18 |
remains available is more important than how quickly. |
19 |
So I think an enterprise distribution should focus on providing and |
20 |
maintaining stacks. Stacks are meaningful combinations of packages that |
21 |
deliver specific functionalities (e.g. an email system).The objective is to |
22 |
optimise the stack and not the individual packages. Look at what |
23 |
spikesource.com are doing. |
24 |
|
25 |
Anyway, my point is that meta-ebuilds is a concept that enables the delivery |
26 |
of such stacks and should be developed beyond the current basic functionality |
27 |
to serve an enterprise Gentoo. |
28 |
|
29 |
Other missing features are client-side tools to manage the selection of |
30 |
packages and stacks, their distributed compilation and their roll-out on a |
31 |
number of machines. |
32 |
|
33 |
I am ready to participate in an effort to create an Enterprise Gentoo |
34 |
distribution with other people that share similar views. |
35 |
|
36 |
JC Francois |
37 |
http://www.noirextreme.com |
38 |
|
39 |
On Monday 20 June 2005 02:36, Devraj Mukherjee wrote: |
40 |
> Hi Robert, |
41 |
> |
42 |
> I have an idea for a system administration tool as well. Actually I |
43 |
> started developing a GLSA update manager which would have a web based |
44 |
> front end and eventually came up with the idea of a Gentoo styled |
45 |
> enterprise distribution which would have a web based administration tool. |
46 |
> |
47 |
> Since I don't want to reinvent the wheel, I would use Gentoo as the base |
48 |
> system and this would allow the flexibility of Gentoo Linux and would |
49 |
> then write an ebuild to distribute my web based management tool with the |
50 |
> relevant packages. |
51 |
> |
52 |
> Let me know if you are interested in something like this so I can |
53 |
> discuss the idea with you further. |
54 |
> |
55 |
> Devraj |
56 |
> |
57 |
> -- |
58 |
> Eternity Technologies Pty. Ltd. ACN 107 600 975 |
59 |
> P O Box 5949 Wagga Wagga NSW 2650 Australia |
60 |
> Voice: +61-2-69255866 / Fax: +61-2-69251039 |
61 |
> http://www.eternitytechnologies.com/ |
62 |
> |
63 |
> Robert Larson wrote: |
64 |
> > On Monday 13 June 2005 09:18 pm, Devraj Mukherjee wrote: |
65 |
> >>Is there an ebuild that builds like a LAMP architecture for most popular |
66 |
> >>applications on a Gentoo system? |
67 |
> > |
68 |
> > I can see quite a bit of use for something like this, and I have been |
69 |
> > wondering about something like this too. I have also been thinking a lot |
70 |
> > lately about the possibility of Gentoo portage managing packages across |
71 |
> > multiple hosts. |
72 |
> > |
73 |
> > With this metapackage idea, it seems to me that it would be a pretty |
74 |
> > incredible thing if I could emerge meta-packages where I might answer |
75 |
> > some simple questions, such as this: |
76 |
> > # emerge -meta lamp |
77 |
> > Would you like: |
78 |
> > A. MySQL |
79 |
> > B. PostgreSQL |
80 |
> > |
81 |
> > Or, I don't know, even a set of configuration files set in place to anwer |
82 |
> > these questions for us. The USE variable seems to answer these |
83 |
> > questions, but it may be a bit limited for the concept of metapackages. |
84 |
> > |
85 |
> > I mention all of this because I have been working for months on |
86 |
> > implementing an infrastructure such as the kind described on |
87 |
> > infrastructures.org. It would be nice to be able to build a set of |
88 |
> > packages, on only a few terms. Even further it would be even more |
89 |
> > productive to be able to build across multiple hosts, multiple |
90 |
> > architectures, etc. We are moving into a day where embedded systems are |
91 |
> > more available, imagine having 200 embedded controllers you have Gentoo |
92 |
> > installed on, and you can execute one emerge command across all of them |
93 |
> > (of course, tested in a non-production environment first...). Or, |
94 |
> > likewise, modify the USE flags on all of them with a single push of |
95 |
> > make.conf. |
96 |
> > |
97 |
> > A few example metapackages might be: |
98 |
> > ids: emerges snort, can run multiple sensors, can tie logging mechanisms |
99 |
> > into external programs that may also be included (ie: prelude, and sguil |
100 |
> > for both real-time and post analisys). |
101 |
> > prelude: Network wide logging(securely), hids, nids, and may pull logs |
102 |
> > and alerts from nagios, samhain, snort, etc. and provide a web frontend |
103 |
> > authserver: ldap, sasl, heimdal, pam, samba-tng, squid, etc.... |
104 |
> > avgateway: clamav, pop3vscan, squid, frox, etc... |
105 |
> > gentoo-postinstall-default: vixie-cron, metalog, sudo, vim, (if needed: |
106 |
> > reiserfs, etc)... |
107 |
> > windowing: xorg, gnome, kde, ati, etc. |
108 |
> > themes: gentoo-artwork, kde-themes, icons, etc.. |
109 |
> > stage1: downloads tar, unpacks it, bootstraps, emerges system, etc. - I |
110 |
> > like this one, imagine deploying 100 identical (but, multiplatform) |
111 |
> > workstations, using one gentoo configuration. |
112 |
> > |
113 |
> > Assuming that portage could work across multiple machines, we can define |
114 |
> > the set of packages, the ways that these sets of packages can |
115 |
> > interconnect, define which hosts, and define the incompatiblities, then |
116 |
> > it would not be too daunting a task to supply the admin with a set of |
117 |
> > options that they can use to implement an entire strategy in a day. As |
118 |
> > well, there would be use to me, if I wanted to create my own metapackages |
119 |
> > through something similar to that of the Gentoo portage. |
120 |
> > |
121 |
> > I like the idea of one host to manage them all, and I love the idea of |
122 |
> > stateful configuration. I also love what portage has done to computing |
123 |
> > (not excluding "ports"), and I will obsess until I can see it all |
124 |
> > together. |
125 |
> > |
126 |
> > Just a few thoughts; I wanted to hear others. Sorry for the lengthy |
127 |
> > post. |
128 |
> > |
129 |
> > Robert Larson |
130 |
-- |
131 |
gentoo-server@g.o mailing list |