Greetings,
Here is my first run with chef on opensolaris and the feedback of the
installation process and usage
cat /etc/release
OpenSolaris 2009.06 snv_111a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 April 2009
platform is being detected incorrectly (I assume it should be just solaris)
I had to symlink
some ohai plugins
The code uses the output of this command:
/sbin/uname -X
System = SunOS
Node = xxxx.xxxxxxxx.xxxxxxx
Release = 5.11
KernelID = snv_111a
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
The hacky fix was this
cd /var/ruby/1.8/gem_home/gems/ohai-0.3.2/lib/ohai/plugins
ln -s solaris2/ solaris2.11
I didn’t use bootstrap for chef to setup instead did it manually in bash
script since the group and user resources are missing.
Then after working with solaris for a bit I realized I needed to write a
package provider. I developed Chef::Provider:
:Opensolaris that uses
IPS.
The code was modeled after the gem package manager so some things don’t make
sense but it works.
I also developed Chef::Provider::Service::Opensolaris which does the basics
with svcs/svcadmin and has worked for me thus far. I intend to make more
revisions to these as time/need permits but here it is now.
Also put together a very mininum zfs resource/provider pair. Far from
complete but it got the job done 
There was also some issues with building and installing. I ran into the
"isinf()" undefined symbol, addressed here:
http://wiki.opscode.com/display/chef/Installation+on+OpenSolaris+2008.11+with+RubyGems
And from snv101 to svn111 the install prefixes changes durastically too.
Uncertain why
The attached tar.gz contains the three providers (and resources) mentioned,
it’d be nice to get these put into mainstream chef.
Keep it cooking,
~ Sig
I'll be using chef some on (regular) Solaris soon, so this is interesting to
hear.
If you want to submit improvements to Chef you gotta do the dance as
described here:
http://wiki.opscode.com/display/opscode/Contributing
It's a bit of a PITA, but Opscode thinks it's needed to protect everyone
from patent trolls, and they have lawyers who know more about that stuff
than I do.
HTH,
Dan DeLeo
On Tue, Sep 1, 2009 at 10:24 AM, Sig Lange sig.lange@gmail.com wrote:
Greetings,
Here is my first run with chef on opensolaris and the feedback of the
installation process and usage
cat /etc/release
OpenSolaris 2009.06 snv_111a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 April 2009
platform is being detected incorrectly (I assume it should be just solaris)
I had to symlink
some ohai plugins
The code uses the output of this command:
/sbin/uname -X
System = SunOS
Node = xxxx.xxxxxxxx.xxxxxxx
Release = 5.11
KernelID = snv_111a
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
The hacky fix was this
cd /var/ruby/1.8/gem_home/gems/ohai-0.3.2/lib/ohai/plugins
ln -s solaris2/ solaris2.11
I didn't use bootstrap for chef to setup instead did it manually in bash
script since the group and user resources are missing.
Then after working with solaris for a bit I realized I needed to write a
package provider. I developed Chef::Provider:
:Opensolaris that uses
IPS.
The code was modeled after the gem package manager so some things don't
make sense but it works.
I also developed Chef::Provider::Service::Opensolaris which does the basics
with svcs/svcadmin and has worked for me thus far. I intend to make more
revisions to these as time/need permits but here it is now.
Also put together a very mininum zfs resource/provider pair. Far from
complete but it got the job done 
There was also some issues with building and installing. I ran into the
"isinf()" undefined symbol, addressed here:
http://wiki.opscode.com/display/chef/Installation+on+OpenSolaris+2008.11+with+RubyGems
And from snv101 to svn111 the install prefixes changes durastically too.
Uncertain why
The attached tar.gz contains the three providers (and resources) mentioned,
it'd be nice to get these put into mainstream chef.
Keep it cooking,
~ Sig
Also, it's way less a PITA than it used to be - you can now just click
through, basically.
Adam
On Tue, Sep 1, 2009 at 10:29 AM, Daniel DeLeodan@kallistec.com wrote:
I'll be using chef some on (regular) Solaris soon, so this is interesting to
hear.
If you want to submit improvements to Chef you gotta do the dance as
described here:
http://wiki.opscode.com/display/opscode/Contributing
It's a bit of a PITA, but Opscode thinks it's needed to protect everyone
from patent trolls, and they have lawyers who know more about that stuff
than I do.
HTH,
Dan DeLeo
On Tue, Sep 1, 2009 at 10:24 AM, Sig Lange sig.lange@gmail.com wrote:
Greetings,
Here is my first run with chef on opensolaris and the feedback of the
installation process and usage
cat /etc/release
OpenSolaris 2009.06 snv_111a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 April 2009
platform is being detected incorrectly (I assume it should be just
solaris) I had to symlink
some ohai plugins
The code uses the output of this command:
/sbin/uname -X
System = SunOS
Node = xxxx.xxxxxxxx.xxxxxxx
Release = 5.11
KernelID = snv_111a
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
The hacky fix was this
cd /var/ruby/1.8/gem_home/gems/ohai-0.3.2/lib/ohai/plugins
ln -s solaris2/ solaris2.11
I didn't use bootstrap for chef to setup instead did it manually in bash
script since the group and user resources are missing.
Then after working with solaris for a bit I realized I needed to write a
package provider. I developed Chef::Provider::Opensolaris that uses
IPS.
The code was modeled after the gem package manager so some things don't
make sense but it works.
I also developed Chef::Provider::Service::Opensolaris which does the
basics with svcs/svcadmin and has worked for me thus far. I intend to make
more revisions to these as time/need permits but here it is now.
Also put together a very mininum zfs resource/provider pair. Far from
complete but it got the job done
There was also some issues with building and installing. I ran into the
"isinf()" undefined symbol, addressed here:
http://wiki.opscode.com/display/chef/Installation+on+OpenSolaris+2008.11+with+RubyGems
And from snv101 to svn111 the install prefixes changes durastically too.
Uncertain why
The attached tar.gz contains the three providers (and resources)
mentioned, it'd be nice to get these put into mainstream chef.
Keep it cooking,
~ Sig
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
Sorry for the massive delay on this, but I am through all the hoops on my
end and am proud to release my first chef changes
preliminary support for user, group, zfs and package on opensolaris
pull from GitHub - sigmonsays/chef at CHEF-529
Lemme know how it goes for you or how I can further assist.
Cheeers,
~ Sig
On Thu, Sep 3, 2009 at 9:43 AM, Sig Lange sig.lange@gmail.com wrote:
done and done
Signed the CLA
opened ticket http://tickets.opscode.com/browse/CHEF-529 to track support
I'll do the github branch soon...
~ Sig
On Tue, Sep 1, 2009 at 10:32 AM, Adam Jacob adam@opscode.com wrote:
Also, it's way less a PITA than it used to be - you can now just click
through, basically.
Adam
On Tue, Sep 1, 2009 at 10:29 AM, Daniel DeLeodan@kallistec.com wrote:
I'll be using chef some on (regular) Solaris soon, so this is
interesting to
hear.
If you want to submit improvements to Chef you gotta do the dance as
described here:
http://wiki.opscode.com/display/opscode/Contributing
It's a bit of a PITA, but Opscode thinks it's needed to protect everyone
from patent trolls, and they have lawyers who know more about that stuff
than I do.
HTH,
Dan DeLeo
On Tue, Sep 1, 2009 at 10:24 AM, Sig Lange sig.lange@gmail.com wrote:
Greetings,
Here is my first run with chef on opensolaris and the feedback of the
installation process and usage
cat /etc/release
OpenSolaris 2009.06 snv_111a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 April 2009
platform is being detected incorrectly (I assume it should be just
solaris) I had to symlink
some ohai plugins
The code uses the output of this command:
/sbin/uname -X
System = SunOS
Node = xxxx.xxxxxxxx.xxxxxxx
Release = 5.11
KernelID = snv_111a
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
The hacky fix was this
cd /var/ruby/1.8/gem_home/gems/ohai-0.3.2/lib/ohai/plugins
ln -s solaris2/ solaris2.11
I didn't use bootstrap for chef to setup instead did it manually in
bash
script since the group and user resources are missing.
Then after working with solaris for a bit I realized I needed to write
a
package provider. I developed Chef::Provider::Opensolaris that
uses
IPS.
The code was modeled after the gem package manager so some things don't
make sense but it works.
I also developed Chef::Provider::Service::Opensolaris which does the
basics with svcs/svcadmin and has worked for me thus far. I intend to
make
more revisions to these as time/need permits but here it is now.
Also put together a very mininum zfs resource/provider pair. Far from
complete but it got the job done
There was also some issues with building and installing. I ran into the
"isinf()" undefined symbol, addressed here:
http://wiki.opscode.com/display/chef/Installation+on+OpenSolaris+2008.11+with+RubyGems
And from snv101 to svn111 the install prefixes changes durastically
too.
Uncertain why
The attached tar.gz contains the three providers (and resources)
mentioned, it'd be nice to get these put into mainstream chef.
Keep it cooking,
~ Sig
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
On Mon, Oct 05, 2009 at 05:44:59PM -0700, Sig Lange wrote:
Sorry for the massive delay on this, but I am through all the hoops on my
end and am proud to release my first chef changes
preliminary support for user, group, zfs and package on opensolaris
pull from GitHub - sigmonsays/chef at CHEF-529
Lemme know how it goes for you or how I can further assist.
Cheeers,
~ Sig
Hiya,
I believe that Chef::Provider::Group::Opensolaris is no longer required.
I rolled in support for OpenSolaris in Chef::Provider::Group::Usermod
at the same time as I did the bits for the upcoming OpenBSD and NetBSD
support.
This was recently merged into master
http://github.com/opscode/chef/blob/master/chef/lib/chef/provider/group/usermod.rb
done and done
Signed the CLA
opened ticket http://tickets.opscode.com/browse/CHEF-529 to track support
I'll do the github branch soon...
~ Sig
On Tue, Sep 1, 2009 at 10:32 AM, Adam Jacob adam@opscode.com wrote:
Also, it's way less a PITA than it used to be - you can now just click
through, basically.
Adam
On Tue, Sep 1, 2009 at 10:29 AM, Daniel DeLeodan@kallistec.com wrote:
I'll be using chef some on (regular) Solaris soon, so this is interesting
to
hear.
If you want to submit improvements to Chef you gotta do the dance as
described here:
http://wiki.opscode.com/display/opscode/Contributing
It's a bit of a PITA, but Opscode thinks it's needed to protect everyone
from patent trolls, and they have lawyers who know more about that stuff
than I do.
HTH,
Dan DeLeo
On Tue, Sep 1, 2009 at 10:24 AM, Sig Lange sig.lange@gmail.com wrote:
Greetings,
Here is my first run with chef on opensolaris and the feedback of the
installation process and usage
cat /etc/release
OpenSolaris 2009.06 snv_111a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 April 2009
platform is being detected incorrectly (I assume it should be just
solaris) I had to symlink
some ohai plugins
The code uses the output of this command:
/sbin/uname -X
System = SunOS
Node = xxxx.xxxxxxxx.xxxxxxx
Release = 5.11
KernelID = snv_111a
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
The hacky fix was this
cd /var/ruby/1.8/gem_home/gems/ohai-0.3.2/lib/ohai/plugins
ln -s solaris2/ solaris2.11
I didn't use bootstrap for chef to setup instead did it manually in bash
script since the group and user resources are missing.
Then after working with solaris for a bit I realized I needed to write a
package provider. I developed Chef::Provider::Opensolaris that
uses
IPS.
The code was modeled after the gem package manager so some things don't
make sense but it works.
I also developed Chef::Provider::Service::Opensolaris which does the
basics with svcs/svcadmin and has worked for me thus far. I intend to
make
more revisions to these as time/need permits but here it is now.
Also put together a very mininum zfs resource/provider pair. Far from
complete but it got the job done
There was also some issues with building and installing. I ran into the
"isinf()" undefined symbol, addressed here:
http://wiki.opscode.com/display/chef/Installation+on+OpenSolaris+2008.11+with+RubyGems
And from snv101 to svn111 the install prefixes changes durastically too.
Uncertain why
The attached tar.gz contains the three providers (and resources)
mentioned, it'd be nice to get these put into mainstream chef.
Keep it cooking,
~ Sig
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
Yay you!
Adam
On Thu, Sep 3, 2009 at 9:43 AM, Sig Langesig.lange@gmail.com wrote:
done and done
Signed the CLA
opened ticket http://tickets.opscode.com/browse/CHEF-529 to track support
I'll do the github branch soon...
~ Sig
On Tue, Sep 1, 2009 at 10:32 AM, Adam Jacob adam@opscode.com wrote:
Also, it's way less a PITA than it used to be - you can now just click
through, basically.
Adam
On Tue, Sep 1, 2009 at 10:29 AM, Daniel DeLeodan@kallistec.com wrote:
I'll be using chef some on (regular) Solaris soon, so this is
interesting to
hear.
If you want to submit improvements to Chef you gotta do the dance as
described here:
http://wiki.opscode.com/display/opscode/Contributing
It's a bit of a PITA, but Opscode thinks it's needed to protect everyone
from patent trolls, and they have lawyers who know more about that stuff
than I do.
HTH,
Dan DeLeo
On Tue, Sep 1, 2009 at 10:24 AM, Sig Lange sig.lange@gmail.com wrote:
Greetings,
Here is my first run with chef on opensolaris and the feedback of the
installation process and usage
cat /etc/release
OpenSolaris 2009.06 snv_111a X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 17 April 2009
platform is being detected incorrectly (I assume it should be just
solaris) I had to symlink
some ohai plugins
The code uses the output of this command:
/sbin/uname -X
System = SunOS
Node = xxxx.xxxxxxxx.xxxxxxx
Release = 5.11
KernelID = snv_111a
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
The hacky fix was this
cd /var/ruby/1.8/gem_home/gems/ohai-0.3.2/lib/ohai/plugins
ln -s solaris2/ solaris2.11
I didn't use bootstrap for chef to setup instead did it manually in
bash
script since the group and user resources are missing.
Then after working with solaris for a bit I realized I needed to write
a
package provider. I developed Chef::Provider::Opensolaris that
uses
IPS.
The code was modeled after the gem package manager so some things don't
make sense but it works.
I also developed Chef::Provider::Service::Opensolaris which does the
basics with svcs/svcadmin and has worked for me thus far. I intend to
make
more revisions to these as time/need permits but here it is now.
Also put together a very mininum zfs resource/provider pair. Far from
complete but it got the job done
There was also some issues with building and installing. I ran into the
"isinf()" undefined symbol, addressed here:
http://wiki.opscode.com/display/chef/Installation+on+OpenSolaris+2008.11+with+RubyGems
And from snv101 to svn111 the install prefixes changes durastically
too.
Uncertain why
The attached tar.gz contains the three providers (and resources)
mentioned, it'd be nice to get these put into mainstream chef.
Keep it cooking,
~ Sig
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com