public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August
Date: Thu, 03 Aug 2006 20:08:32 +0200	[thread overview]
Message-ID: <1154628512.24984.70.camel@localhost> (raw)
In-Reply-To: <44D1F809.5010801@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2846 bytes --]

On Thu, 2006-08-03 at 13:20 +0000, Alec Warner wrote:
> > No, not really. Just that I'd expect kinda more proactive approach than
> > the one demonstrated fex. in
> > http://bugs.gentoo.org/show_bug.cgi?id=128588#c29 (and a bit more
> > flexible approach to other alternatives, such as HW/hosting offers we've
> > received before) and that have been declined for various strange reasons.
> 
> Linking to a bug where you make crazed comments about how bugs isn't
> fixed!!!!1111oneone and that dammit someone should do something
> now!!!1111 doesn't really help your case.
> 
> I bet if I was infra I'd be wondering what my options were since:
> 
> bugs is a pretty critical part of developing; AND
yes
> you can't just host it anywhere; AND
it's not _that_ much hardware (and bandwidth) needed
> the hardware needed for it to perform is expensive; AND
for a single person yes. For a sponsor (or a group of sponsors) it may
be ok

> they did not know what the problem was at first
And even there it took some heavy prodding to get people to look at the problem.

After about half a year of waiting, with people we would consider
reliable offering pretty much everything from hosting to hardware, it's
hard to listen to the "be patient" mantra without thinking "omgwtfbbq,
it is _still_ not fixed?". Especially since bugs is considered an
important part of our infrastructure.

> As in, you don't just grab the first dual proc system that was offered
> out of some guys basement to host bugs on.
Agreed, but I'd say a webhoster with >1000 machines should know what
they are doing.

>   You need a dedicated host
> who will stick around and provide good support should something go
> wrong.
Only experience can tell you how they will respond, and even reliable
sponsors could get axed if their managment changes. We have almost no
hardware in Europe, that's a huge untapped ressource ...

>   You need expensive hardware ( I believe we got a blade server
> with 3 blades in it, which is fscking expensive if you haven't priced
> one out before ).  So once again, chill out.  They are working on it.
Dude, you don't need blades for it. Any "normal" server will do, two for DB and one for web frontend.
That we got blades is really nice and sweet, but if you check the
traffic and throughput of bugzilla (and then double or triple that for
future growth) you should still be able to do it easily.

(Note to our sponsors: you rock. Keep on rocking.)

Right now bugs is served from a 2,4Ghz P4 - that's roughly a normal
desktop box from last year. 

> And yes bugs is slow and yes it sucks, but bitching about it doesn't
> accomplish anything :x
It may cause discussion that may lead to accelerated problem solving :-)

hth,

Patrick
-- 
Stand still, and let the rest of the universe move

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2006-08-03 18:14 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for August Mike Frysinger
2006-08-01 11:13 ` Wernfried Haas
2006-08-14 17:23   ` Thierry Carrez
2006-08-15  9:22     ` Stuart Herbert
2006-08-03  9:21 ` Jakub Moc
2006-08-03 12:23   ` Ned Ludd
2006-08-03 13:06     ` Lance Albertson
2006-08-03 13:35       ` Ned Ludd
2006-08-03 14:07         ` Jakub Moc
2006-08-03 14:48           ` Ned Ludd
2006-08-03 15:05             ` Jakub Moc
2006-08-03 13:20               ` Alec Warner
2006-08-03 18:08                 ` Patrick Lauer [this message]
2006-08-03 18:48                   ` Lance Albertson
2006-08-03 19:22                     ` Patrick Lauer
2006-08-04  4:58                       ` Jochen Maes
2006-08-03 19:55                     ` Chris Bainbridge
2006-08-03 20:54                       ` kashani
2006-08-03 21:10                         ` Lance Albertson
2006-08-04  8:15                           ` Simon Stelling
2006-08-04 13:13                             ` Lance Albertson
2006-08-03 20:55                       ` Lance Albertson
2006-08-04  5:06                   ` Jochen Maes
2006-08-03 18:51                 ` Lance Albertson
2006-08-03 19:02                   ` Ciaran McCreesh
2006-08-03 19:21                     ` Lance Albertson
2006-08-04  5:07                     ` Jochen Maes
2006-08-03 17:03               ` Simon Stelling
2006-08-03 17:55                 ` Patrick Lauer
2006-08-03 14:58           ` Lance Albertson
2006-08-03 15:10             ` Jakub Moc
2006-08-04  8:57         ` Curtis Napier
2006-08-04  9:07           ` Curtis Napier
     [not found]           ` <44D34753.6090604@gentoo.org>
2006-08-04 15:53             ` Joshua Jackson
2006-08-04 16:08               ` Alec Warner
2006-08-04 19:23                 ` Mike Doty
2006-08-04 18:07               ` kashani
2006-08-04 19:56                 ` Robin H. Johnson
     [not found] <886253338-1154701653-cardhu_blackberry.rim.net-693078490-@bwe059-cell00.bisx.prod.on.blackberry>
2006-08-04 23:22 ` Matthew Marlowe
  -- strict thread matches above, loose matches on Subject: below --
2007-08-01  8:08 Mike Frysinger
2007-08-01 13:14 ` Mike Frysinger
2008-08-01  5:30 Mike Frysinger
2009-08-01  5:30 Mike Frysinger
2009-08-01 13:10 ` Sebastian Pipping
2009-08-02 15:58   ` Denis Dupeyron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1154628512.24984.70.camel@localhost \
    --to=patrick@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox