Re: Server at Paris VIII

[James]

Hello,

On 13 May 2012 11:41, Phil Holmes <address@hidden> wrote:
> ----- Original Message ----- From: <address@hidden>
> To: "LilyPond-Devel list" <address@hidden>
> Sent: Sunday, May 13, 2012 11:08 AM
> Subject: Server at Paris VIII
>
>
>> Hey all,
>>
>> Just got off the phone with John M about setting up a server at Paris
>> VIII.  He'll be going as the LilyPond rep on Wednesday to chat with the
>> people there (Valentin's teaching piano and I'm in rehearsal all day,
>> otherwise we'd all go...music gets in the way of LilyPond yet again!).
>>
>> John suggests that we set up a basic infrastructure that allows us to
>> access the server via SSH and then do with it as we wish.  Note that I am
>> using the words "SSH" to a lesser extent "server" without really knowing
>> what they mean, but John does and he'll be able to communicate our needs to
>> the technical team.
>>
>> The people there will likely want to know what our intentions are, and I
>> told John that the machine would be used to make nightly builds and to run
>> patchy and patchetta.  He asked if we were thinking of using it for
>> something like weblily and my tentative response was no.
>>
>> Reply to this message if anyone has any questions/comments/concerns.  All
>> y'all can send thank you notes to Anne Sedes, who is very graciously giving
>> us a physical machine to make this thing happen!
>>
>> Cheers,
>> MS
>
>
>
> I think it would also be good to set up some sort of mechanism where
> contributors can request an "on demand" build, choosing make, make doc, make
> test; and a git branch to build.  That way people without multi-core
> machines can check their own changes more quickly.
>
> Do you know its specification?
>

To add to Phil's comments and not wanting to turn this into an IT
headache, if it does have enough cores (and RAM although unless
someone suddenty sets up a massive set of concurrent makes, it is
rarely an issue) that you set up a 'Virtual Infrastructure' and have a
number of Virtual Machines - that way it is easy to segregate Patchy
from letting users in and also for the other possible stuff (mediawiki
LSR etc.).

While Virtualbox is good, I would not use it as a Virtual
Infrastructure, but use Linux's KVM. It seems to have much better
'resource sharing' - I can appear to have 15 CPUs running at once when
in fact I have half that. It does pretty good resource sharing.

However this isn't really the place for that discussion now.

What I would say though Mike is think small first, find the spec and
get patchy-merge working, see how much that uses in 'real life' in
terms of cycles and go from there. I'd give priority to automatic
build then 'websitey' things before dev SSH access. Just because those
are easily controlled.

James