I'm just finishing up adding initial Solaris support to my existing Linux-oriented module set. I do think a set of modules covering the basics would be helpful. As a Linux admin learning Solaris trying to understand both the Puppet differences and the OS differences made startup harder.
Solaris Version: 10 64-bit only, both i386 and Sparc Packages: Custom packages using pkgadd, Solaris OS packages using pkgutil, OpenCSW using pkgutil. Most of my difficulties have been around package management, so as far as I'm concerned Solaris 11 and IPS can't happen soon enough. Module Organization: The advice I've followed (which seems to have worked well so far) was to move the contents of existing 'myclass' to 'myclass::linux' and add the Solaris functionality as 'myclass::sunos'. Class 'myclass' becomes a wrapper class which does an 'include myclass::$kernel'. You may want to use 'myclass::solaris', 'myclass::redhat', etc with $operatingsystem instead but since my Linuxes are all RH-like $kernel is convenient. I've created a few defines designed to be shared between Linux and Solaris but since pathing is different for most things and behavior is often different between GNU and Solaris utils it's a pain. Most of the time splitting at the OS level seems to work better. Currently doing: NFS AutoFS Swap Banners DNS client NTP Packages Sendmail SSH Sudo Syslog Users VMware Tools Future plans: I'm expecting to have to do Update Release detection since it sometimes brings significant functionality differences. I haven't gotten into some of the fancier things that are going to require this info yet but there's nothing built into facter (as of 1.5.8) so that'll be fun. Patching via Patch Check Advanced ( http://www.par.univie.ac.at/solaris/pca/) ZFS management (should be pretty easy) Zone management (less easy) Network interface mangement (including standalone adapters, IPMP, and link aggregation) On Wed, Jul 20, 2011 at 12:06 AM, Al @ Lab42 <lab42...@gmail.com> wrote: > I'm considering the opportunity of adding (basic) Solaris support to my > modules ( www.example42.com) but before starting I'd like to gather some > info about best practices and standards. > I've to admit that I've not a great working Solaris experience, so I > actually don't know how people use it, what versions are more used and so > on. > > So let's begin with few points: > > - What version? > I'm tempted to begin only with Solaris 10, in order to avoid too many > complications. Question is... does this makes sense? What versions of > Solaris are currently most used? Since I believe that the best approach to > puppettization is to replicate on new machines the current envrionments > without installing Puppet on existing production servers, does make sense > the assumption that people would generally upgrade their older boxes to > brand new Solaris 10 setups? > I know that mileage may vary, but whatever better informed opinion is > welcomed. > > - What packages? > This might become a nightmare... there are different packages repositories, > blastwave, openCSW, Sunfreeware... , to make modules that manage the same > software from different sources might be a troublesome and I would like to > stick to one. Does this makes sense? What's the most used / updated /large > package repository out there? Do you use any of these on production > environments? > > - What package manager? > Can I assume that (almost) everybody uses (in 2011) pkgutil to install > software on Solaris? If not, what are the alternatives? > > - Existing modules for Solaris? > Has anyone published Puppet modules for Solaris? Can you link them here, > for reference and inspiration... > > There questions might appear particularly naive to a more experienced > Solaris sysadmin but I have to start from some basic points and as usual, > "better ask to the experts"... > > Thanks for any feedback you might want to leave on these questions and to > whatever advice you might give about Puppet on Solaris. > > If someone if interested is collaborating on this effort, just contact > me.... > > All the best > Al > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/yi-nY02p06AJ. > 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. > -- 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.
