I've been looking at easybuild for a little while now and it appears
to be a suitable framework for a good portion of our needs.
Easybuild already has support for a lot of the packages we are
interested in running. I was also able to find answers to several of
my early problems in the mailing lis
Howdy Stuart,
I'll offer an unofficial welcome to EasyBuild. I can relate
to quite a bit of the below. I'm not sure I have any good
answers yet. But WELCOME Your comments will not
go unnoticed
For example, I just want to second one of your points
(while I ponder if I can better answer y
On Wed, Feb 11, 2015 at 2:32 AM, Stuart Barkley wrote:
> I've been looking at easybuild for a little while now and it appears
> to be a suitable framework for a good portion of our needs.
Welcome to EB!
> My cluster does not have direct access to the Internet so I can't use
> any of the automate
Hi Stuart,
On Feb 11, 2015, at 2:32 AM, Stuart Barkley wrote:
> I've been looking at easybuild for a little while now and it appears
> to be a suitable framework for a good portion of our needs.
If you provide software for HPC you are on the right road.
> I think I eventually used "--dry-run -
Hi Fotis & Stuart,
>> What do people do/recommend for multiple OS environments? We are
>> currently CentOS 6 but will eventually move to C7. I'm thinking I
>> will want a separate application tree for each OS (/projects/app-c6
>> and /projects/app-c7).
>>
>> How do people deal with soft
On 02/11/2015 10:09 AM, Cook, Malcolm wrote:
Hi Fotis & Stuart,
What do people do/recommend for multiple OS environments? We are
>> currently CentOS 6 but will eventually move to C7. I'm thinking I
>> will want a separate application tree for each OS (/projects/app-c6
>> and /proje
On Wed, Feb 11, 2015 at 10:30:30AM -0600, Jack Perdue wrote:
> On 02/11/2015 10:09 AM, Cook, Malcolm wrote:
> >Hi Fotis & Stuart,
> >
> >>>What do people do/recommend for multiple OS environments? We are
> > >> currently CentOS 6 but will eventually move to C7. I'm thinking I
> > >> will wa
Hi Malcolm, Jack,
>> >Then you might create symlinks like:
>> > /opt/apps/sandybridge -> /opt/apps/*.MMDD
>> >
>> >I used a dubious example name above but you get the idea.
Something that has functioned in practice before is a scheme like:
/opt/apps/HPCBIOS.haswell -> /opt/apps/HP
2015-02-11 17:09 GMT+01:00 Cook, Malcolm :
>
>
> Fotis, I note your example name, "sandybridge", apparently encoded an
> intel processor microarchitecture, NOT the name of a linux distribution
> (such as c6 or c7 for releases of centOS, as proposed). I'm trying to
> understand the implications
Hi,
>
> >> >Then you might create symlinks like:
> >> > /opt/apps/sandybridge -> /opt/apps/*.MMDD
> >> >
> >> >I used a dubious example name above but you get the idea.
>
> Something that has functioned in practice before is a scheme like:
>
> /opt/apps/HPCBIOS.haswell -> /opt/apps/H
Hi Malcolm,
On Feb 13, 2015, at 8:01 PM, Malcolm Cook wrote:
> This level of symlink indirection is providing for 'buildsets' whose name
> encodes microprocessor-architecture and creation date of the buildset, only
> one of which is 'current', right?
>
> And, the '-h' and 's' _could_ be spel
11 matches
Mail list logo
