1 |
>On Thu, 2005-08-04 at 09:04 -0400, Eric Brown wrote: |
2 |
>> |
3 |
>> Interesting thread. I have used Gentoo in enterprise situations very |
4 |
>> successfully, and I think the whole QA/live-tree argument is moot. In |
5 |
>> an enterprise environment, you might have a backup/testing machine to |
6 |
>> run your updates on first before they went live. You also wouldn't run |
7 |
>> new packages unless they passed your own QA tests first. |
8 |
>> |
9 |
>> Given the incredible flexibility of portage to support local mirrors, |
10 |
>> binary package preparation, and localized versions of packages |
11 |
>> (portdir_overlay), I would say that Gentoo is quite a contender in the |
12 |
>> enterprise environment. |
13 |
>> |
14 |
>> Perhaps we need some enterprise documentation to help people realize the |
15 |
>> full potential of portage? |
16 |
> |
17 |
>I think you've missed some of the idea of "enterprise" support. See, |
18 |
>for starters, every person shouldn't have to create their own |
19 |
>implementation of everything. Perhaps a better solution would be a |
20 |
>package that when installed, builds up a local mirror, a binary package |
21 |
>repository (with revision control), an automated update system, a system |
22 |
>for updating rolled out machines without forcing the use of etc-update |
23 |
>on each machine, a slower moving stable tree capable of being certified |
24 |
>with applications, and most likely a phone number of someone to call |
25 |
>when the shit hits the fan. |
26 |
|
27 |
Every business application of Gentoo I've done has been different. I don't think I could generalize my needs into a single ebuild. Although generally I have used rsyncd and apache, I never use them in the same way. What's so hard about using the default rsyncd config, and adding distfiles to your apache document root? (what 90% of people would use). |
28 |
|
29 |
About automating updates and etc-update: you can rsync your config file sometimes and just bypass all of the portage stuff. You could mount some config dirs over nfs even. You could even remove config_protect on some dirs and roll your own custom packages. |
30 |
|
31 |
About a slower moving portage tree for enterprise users: Great idea, I think there's a GLEP about that. I think it's best handled by third parties who can spend the money/man power on that kind of QA. |
32 |
|
33 |
This brings me to your last point about calling someone when there are problems: There are companies that provide Linux services, even Gentoo specific services. Some of these companies might even provide enterprise-grade portage mirrors with support for the packages they maintain there. |
34 |
|
35 |
> |
36 |
>While I will completely agree that Gentoo *can* be used in the |
37 |
>enterprise successfully, that does not make it "enterprise-ready", in |
38 |
>any sense. Many people also seem to misunderstand the concept of |
39 |
>"enterprise" when we are referring to it in this manner. We don't mean |
40 |
>"I'm running it on 10 servers in production" or anything like that. We |
41 |
>mean "I'm running this as our production platform for Linux services |
42 |
>across our entire enterprise, that could be hundreds or even thousands |
43 |
>of servers" instead. While it might be possible to maintain a handful |
44 |
>of Gentoo servers, it is next to impossible to maintain an army of them, |
45 |
>without spending significant up-front manpower to design, test, and |
46 |
>implement your own set of management tools. Gentoo has no real |
47 |
>management tools. There are a few here and there that do specific |
48 |
>tasks, but there isn't anything designed to really take control over |
49 |
>your network of systems. To be fair, Red Hat doesn't have anything like |
50 |
>this, either. Their "Satellite Server" product is good for initial |
51 |
>builds and for updates, but falls short on the management aspects. |
52 |
>Novell's offerings are probably the best examples of what we really |
53 |
>need. Of course, most people would be happy with even rudimentary |
54 |
>management capabilities, as currently, we have none. We don't have any |
55 |
>form of update server. You have to build one yourself. We don't have |
56 |
>any form of "jump-start" or "kickstart" for rapid automated deployments. |
57 |
>You have to build one yourself. Now, we do have the Gentoo Linux |
58 |
>Installer project, which has this as one of its goals, so we will have |
59 |
>this component at some point in the future. |
60 |
|
61 |
I'm sorry, I never ran 1000 Gentoo machines in production like that, I thought enterprise meant this (answers.com): |
62 |
|
63 |
en·ter·prise (ĕn'tər-prīz') pronunciation |
64 |
n. |
65 |
|
66 |
1. An undertaking, especially one of some scope, complication, and risk. |
67 |
2. A business organization. |
68 |
3. Industrious, systematic activity, especially when directed toward profit: Private enterprise is basic to capitalism. |
69 |
4. Willingness to undertake new ventures; initiative: “Through want of enterprise and faith men are where they are, buying and selling, and spending their lives like serfs” (Henry David Thoreau). |
70 |
|
71 |
Doesn't this just go to show that in business, everyone wants something different from Gentoo? What does Novell offer to manage large numbers of linux boxen? Are you sure projects like OpenMosix don't have tools you could use to manage such a large number of machines? |
72 |
|
73 |
Maybe we can't rely on portage so much in scenarios where replication is the goal... |
74 |
|
75 |
> |
76 |
>Last, there's the "Our servers just went belly up, and I want to call up |
77 |
>someone on the phone and give them a piece of my mind" issue which gives |
78 |
>managers a warm, fuzzy feeling, that we cannot provide. If something |
79 |
>goes wrong with RHEL or SLES, you call up Red Hat or Novell and get them |
80 |
>to work on the problem. If something goes wrong with Gentoo, you hop on |
81 |
>IRC, or file a bug, and hope that somebody can help you in the time you |
82 |
>need it done in, and not in 3 weeks when the maintaining developer gets |
83 |
>back from his tour of the African Dung Beetle in it's own environment. |
84 |
>Liability is a big selling point for the enterprise. |
85 |
|
86 |
Of course, I'm sure you can't call Red Hat or Suse if you don't pay them some way or another. If you don't pay, could you find such a supportive community on IRC or in forums? (I think not) |
87 |
|
88 |
There are lots of Gentoo gurus who will gladly accept your money to help you fix your problems =) |
89 |
|
90 |
> |
91 |
>I work for a telecommunications company, and we run Linux and Solaris. |
92 |
>For our Linux, we run Red Hat, even though they have, on staff, one of |
93 |
>the people that understands Gentoo's deployment capabilities better than |
94 |
>most, via catalyst and the GLI. Why do we run Red Hat? When something |
95 |
>breaks with one of their packages, we call them, and expect them to fix |
96 |
>it. It is also a name that gives upper management the warm fuzzies. |
97 |
>Gentoo has neither the brand recognition, nor the support capabilities |
98 |
>to be a good sale to management. |
99 |
|
100 |
Sounds like FUD to me. Use what works for you though. If you managers really need that big brand name with that 800 number, that's just how you'll have to do it. Perhaps I've been lucky at the places I work where I am simply responsible myself for keeping certain systems up, and that's that. |
101 |
|
102 |
> |
103 |
>I'm not denying that Gentoo is very powerful, flexible, and gives the |
104 |
>power back to the administrator, but that doesn't make it enterprise |
105 |
>ready or friendly. A few success stories from a few people isn't much |
106 |
>to support the position, when we are lacking in so many simple and |
107 |
>obvious ways. Remember, if a manager can think of multiple ways to |
108 |
>knock down the use of Gentoo, like the ones I've given above, what are |
109 |
>you going to do to refute his claims? |
110 |
|
111 |
I wouldn't refute my manager's claims if he controlled my paycheck :D |
112 |
But in my professional opinion, as someone who has had to manage up to 10 Linux servers at a time, Gentoo was by far the best choice. That's what I'd say to my manager if he ever asked me why I want to use Gentoo. |
113 |
|
114 |
> |
115 |
>I want to see Gentoo as an enterprise-capable distribution myself, but I |
116 |
>also understand that it is a long, hard road ahead of us, and there will |
117 |
>still be some things we simply cannot provide as a community |
118 |
>distribution, which was my reasoning behind the "fork". There would |
119 |
>need to be an entity that is responsible, liable, if you will, when |
120 |
>something goes wrong, and that has the manpower and resources to fix it. |
121 |
> |
122 |
|
123 |
Ever consider founding a company that specializes in Enterprise Gentoo deployment and support? It sounds like there could be quite a demand for such services :) |
124 |
|
125 |
>-- |
126 |
>Chris Gianelloni |
127 |
>Release Engineering - Strategic Lead/QA Manager |
128 |
>Games - Developer |
129 |
>Gentoo Linux |
130 |
|
131 |
-- |
132 |
gentoo-dev@g.o mailing list |