>> If you are using Cray Linux - I believe its based on the SuSE Linux
>> platform (and we do support SLES 11sp1/2) - so if you have trouble I'm
>> sure it wouldn't be hard to adapt, although it isn't a platform we
>> have specifically targeted in the past. Some Facter patches would
>> probably be needed to identify its version and OS - but if it works
>> like SuSE in respect to packaging we already have the code to support
>> zypper packages (if that is indeed what it uses) and other SuSE
>> facilities - it all depends on the variations that Cray have taken.
>
>
> This is exactly the case. Since it's a Linux, I guess you can always compile
> and run the code, but patches like the ones you mention would be necessary,
> and knowing that somebody has done this before is good to know, not only in
> PE (which is good) but also around the community... does any?

To answer your PE question - no - 'we' (as in the collective
Puppetlabs) haven't done anything for PE today and Cray Linux is not
specifically supported by us today from a commercial perspective.

On the other hand, I would be surprised if you couldn't get Puppet on
its own to work on Cray Linux.

If you get no other responses from people - I would try getting just
the open source parts of Puppet to work, focusing on SuSE instructions
and see how far you get, then come back to the list for help. My gut
feel would be that the variations would be small enough for you to
make it work.

I would anticipate perhaps some Facter patches to identify your OS and
mark it a SLES variant would be helpful - which is fairly easy to do.

Here is an example to give you a feel for at least the Facter patch
complexity, in this case we added Ascendos support (a Redhat variant):

https://github.com/puppetlabs/facter/commit/c9db305096a8aa95a48bd717e752abccecea6009

Roughly 20 lines of change ... and its probably less these days since
we've simplified some parts of the code since that patch.

>> BlueGene/Q on the other hand is a PPC architecture isn't it? So what
>> OS are you running on it? In most cases when it comes to Puppet - its
>> the OS that matters.
>
>
> Yes, PPC A2 processors, but the distribution is a patched RHEL6. I guess the
> same as with Cray applies here: you would need patches, and knowing that
> someone around the community has done this before would be a great relief!

If its RHEL6, then its probably going to work, I don't believe we ship
PPC RPM's today though for architecture specific elements that we
bundle with PE. With PE we ship our own Ruby and Apache and these are
only i386 and x86_64 today.

I do however believe Puppet itself (without-PE) should work, since
RHEL features are usually well covered by Puppet. You just need to use
all the OS bundled items like Apache and Ruby shipped with RHEL6.

ken.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to