Gentoo Archives: gentoo-dev

From: Jochen Maes <gentoo-dev@××××.be>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August
Date: Fri, 04 Aug 2006 05:37:14
Message-Id: 10581.81.241.146.66.1154667982.squirrel@squirrel.sejo.be
In Reply to: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August by Patrick Lauer
1 > On Thu, 2006-08-03 at 13:20 +0000, Alec Warner wrote:
2 >> > No, not really. Just that I'd expect kinda more proactive approach
3 >> than
4 >> > the one demonstrated fex. in
5 >> > http://bugs.gentoo.org/show_bug.cgi?id=128588#c29 (and a bit more
6 >> > flexible approach to other alternatives, such as HW/hosting offers
7 >> we've
8 >> > received before) and that have been declined for various strange
9 >> reasons.
10 >>
11 >> Linking to a bug where you make crazed comments about how bugs isn't
12 >> fixed!!!!1111oneone and that dammit someone should do something
13 >> now!!!1111 doesn't really help your case.
14 >>
15 >> I bet if I was infra I'd be wondering what my options were since:
16 >>
17 >> bugs is a pretty critical part of developing; AND
18 > yes
19 >> you can't just host it anywhere; AND
20 > it's not _that_ much hardware (and bandwidth) needed
21 >> the hardware needed for it to perform is expensive; AND
22 > for a single person yes. For a sponsor (or a group of sponsors) it may
23 > be ok
24 >
25 >> they did not know what the problem was at first
26 > And even there it took some heavy prodding to get people to look at the
27 > problem.
28 >
29 > After about half a year of waiting, with people we would consider
30 > reliable offering pretty much everything from hosting to hardware, it's
31 > hard to listen to the "be patient" mantra without thinking "omgwtfbbq,
32 > it is _still_ not fixed?". Especially since bugs is considered an
33 > important part of our infrastructure.
34 >
35 >> As in, you don't just grab the first dual proc system that was offered
36 >> out of some guys basement to host bugs on.
37 > Agreed, but I'd say a webhoster with >1000 machines should know what
38 > they are doing.
39 >
40 >> You need a dedicated host
41 >> who will stick around and provide good support should something go
42 >> wrong.
43 > Only experience can tell you how they will respond, and even reliable
44 > sponsors could get axed if their managment changes. We have almost no
45 > hardware in Europe, that's a huge untapped ressource ...
46 >
47 >> You need expensive hardware ( I believe we got a blade server
48 >> with 3 blades in it, which is fscking expensive if you haven't priced
49 >> one out before ). So once again, chill out. They are working on it.
50 > Dude, you don't need blades for it. Any "normal" server will do, two for
51 > DB and one for web frontend.
52 I hope you know what you are talking about and if you use 2 db's with one
53 database (i think you mean a sort of loadbalancing/clustering) you
54 practicly need double mem +10% of the size of you database...
55
56 > That we got blades is really nice and sweet, but if you check the
57 > traffic and throughput of bugzilla (and then double or triple that for
58 > future growth) you should still be able to do it easily.
59 >
60 > (Note to our sponsors: you rock. Keep on rocking.)
61 >
62 > Right now bugs is served from a 2,4Ghz P4 - that's roughly a normal
63 > desktop box from last year.
64 >
65 >> And yes bugs is slow and yes it sucks, but bitching about it doesn't
66 >> accomplish anything :x
67 > It may cause discussion that may lead to accelerated problem solving :-)
68 >
69 > hth,
70 >
71 > Patrick
72 > --
73 > Stand still, and let the rest of the universe move
74 >
75
76
77 --
78 gentoo-dev@g.o mailing list