On Tue, Apr 29, 2014 at 9:30 PM, William Stein <wst...@gmail.com> wrote:
> On Tue, Apr 29, 2014 at 9:04 PM, Ralf Stephan <gtrw...@gmail.com> wrote:
>> I understand SMC is already in the cloud, so what would be necessary
>> to have Sage with a patchbot running there? Is there some documentation
>> on the Sage side? Ideally I'd just pay and use an existing copy,
>> preferably with control over the ticket numbers.

As documented on the patchbot page,  just run

sage -i 
http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.1.spkg
sage -patchbot

> What would be a minimal useful machine configuration to start with?
>
>    https://cloud.google.com/products/compute-engine/#pricing
>
> I can spin up an Ubuntu 14.04 image for you try if you tell me which
> machine type would work, and send me your ssh key (so you can login).
>  This would be "free for a few months"  -- I have a grant from Google
> for this sort of thing, which expires in November.
>
> Alternatively, you could run a patchbot in a project on SMC itself.
> If you make a project and send me the project id, I can increase the
> disk quota to be enough for this purpose (or you could use scratch),
> disable timeouts, and also peg it to only run on GCE  (rather than
> machines at UW).   My preference would actually just to be do this as
> part of an SMC project, since it is a good test of SMC.

The minimum requirements are enough RAM to compile Sage (several GB
these days for linbox, right?), enough disk for 2 installs of Sage
plus, ideally, several GB for a good ccache. There's no minimum number
of cores, the more you throw at it the faster it'll run.

- Robert

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to