Re: [Gforge-admins] Re: PgFoundry Move

Well, the problems with the current setup are well known, including:
- running on a machine that is sometimes rather loaded
- no separation of users / gforge , meaning we have had to restrict what
users / groups can do for security reasons
- unsupported (and in fact unknown) mailman version
- missing features like SVN support

JoshB and others have been working on a new box, that's true. But it's
been a very long time coming.

Joshua's offer is attractive because of the level of support promised. I
can certainly testify that when I screwed up the buildfarm badly, CP was
wonderfully responsive and we were back running with almost no data loss
within a couple of hours. Service like that is hard to beat.

cheers

andrew

On Mon, 2006-01-16 at 14:59 -0400, Marc G. Fournier wrote:
> Not sure where this email came from, but JoshB has gone to the trouble of
> setting up a new server for pgFoundry, and when that is ready, it will be
> moved there ...
>
> Is there a problem that I haven't been informed of with the server it is
> currently running on?
>
>
> On Mon, 16 Jan 2006, Joshua D. Drake wrote:
>
> > Hello,
> >
> > In the essence of being efficient I would like to suggest that we move
> > Pgfoundry. I know we have been trying to "migrate" for what seems like
> > forever but maybe it is time we just up and move the whole site :).
> >
> > I would like to again offer Command Prompt's services in hosting
> > pgFoundry.
> >
> > Some key benefits to moving the system to CMD:
> >
> > 1. You can call us
> > 2. You can call us at 3:00 am
> > 3. We have service level monitoring
> > 4. We have a lot of bandwidth
> > 5. All our stuff is on natural gas conditioned power generators
> >
> > We have proven to be very stable with the Buildfarm and with the archives.
> > With the only recent problem with either not being at the hands of CMD,
> > (gentle poke at Andrew).
> >
> > The longest outage we have had in the last 24 months is four hours for a
> > single
> > machine that we had to recover from backup.
> >
> > The longest outage we have had that was global in the last 24 months (that
> > wasn't
> > scheduled) was 90 minutes when we lost a nic in one of our firewalls.
> >
> > We did recently have a scheduled outage of 4.5 hours but that was from
> > midnight
> > to 4:30 while we upgraded some power facilities.
> >
> > The only change that we would require would be to move the system to Linux.
> > This should be a very minor change in general and will probably require
> > very if any work on the Gforge end.
> >
> > Thoughts, Flames, better suggestions?
> >
> > Sincerely,
> >
> > Joshua D. Drake
> >
> > --
> > The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
> > PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> > Managed Services, Shared and Dedicated Hosting
> > Co-Authors: PLphp, PLperl - http://www.commandprompt.com/
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> > choose an index scan if your joining column's datatypes do not
> > match
> >
>
> ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
> _______________________________________________
> Gforge-admins mailing list
> Gforge-admins(at)pgfoundry(dot)org
> http://pgfoundry.org/mailman/listinfo/gforge-admins