Re: Machine available for community use

Just a follow-up to note that Red Hat has graciously donated a 1 year
RHEL subscription and myYearbook is paying Command Prompt to setup the
RHEL box for community use.

We've not worked out a scheduling methodology, or how to best organize
the use of said hardware, but I know that Tom and others are
interested.

Does anyone have a scheduling solution for things like this to make
sure people aren't stepping on each others toes processor/ram/disk
wise?

Also, what should the policies be for making sure that people can use
the box for what they need to use the box for?

Should people clean up after themselves data usage wise after their
scheduled time?

Should people only be able to run PostgreSQL in the context of their
own user? Do we have experience with such setups in the past? What
has worked well and what hasn't?

Gavin

On 7/25/07, Gavin M. Roy <gavinmroy(at)gmail(dot)com> wrote:
> Recently I've been involved in or overheard discussions about SMP
> scalability at both the PA PgSQL get together and in some list
> traffic.
>
> myYearbook.com would ike to make one of our previous production
> machines available to established PgSQL Hackers who don't have access
> to this level of hardware for testing, benchmarking and development to
> work at improving SMP scalability and related projects.
>
> The machine is a HP 585 G1, 8 Core AMD, 32GB RAM with one 400GB 14
> Spindle DAS Array dedicated to community use. I've attached a text
> file with dmesg and /proc/cpuinfo output.
>
> I'm working on how this will be setup and am open to suggestions on
> how to structure access.
>
> I'm currently in the process of having Gentoo linux reinstalled on the
> box since that is what I am most comfortable administering from a
> security perspective. If this will be a blocker for developers who
> would actually work on it, please let me know.
>
> If you're interested in access, my only requirement is that you're a
> current PgSQL Hacker with a proven track-record of committing patches
> to the community. This is a resource we could be using for something
> else, and I'd like to see the community get direct benefit from it as
> opposed to it being a play sandbox for people who want to tinker.
>
> Please let me know thoughts, concerns or suggestions.
>
> Gavin M. Roy
> CTO
> myYearbook.com
> gmr(at)myyearbook(dot)com
>
>