Skip to content

Conversation

@nalyanyam
Copy link
Contributor

Add Solaris 11 support.
Solaris 11 uses SMF registry for a number of configurations and files are becoming obsolete, but retained for backward compatibilty. I have seen that this support would be available in future puppet version release (may be from 3.4.1), but there are already library codes that can implement this.

library provider/type source:
https://java.net/projects/solaris-userland/sources/gate/show/components/puppet/files/solaris/lib/puppet?rev=1878

I will get the code tested more and confirm here.

@nalyanyam
Copy link
Contributor Author

@ghoneycutt ,
Could you please look at this code and let me know what you think?

@ghoneycutt
Copy link
Owner

It seems that all files under https://java.net/projects/solaris-userland/sources/gate/show/components/puppet/files/solaris/lib/puppet should be in their own module and then nsswitch can depend on that module. We don't want to fork their code. Do they supply modules or just that repo?

@nalyanyam
Copy link
Contributor Author

They only provide resource types and providers that can be used in the modules. At least i did not see any modules. Apparently, some of these resource types are supposed to be integrated in future puppet releases. Not sure how far they are going to support some of these types because i have also seen that from Solaris 11.2 roadmap, there will be text based SMF stencils that could be configured and then imported into the SMF configurations. That means it will then be easier to manage smf-based files by puppet once more. (https://blogs.oracle.com/c0t0d0s0/entry/new_solaris_11_2_beta)

So the SMF puppet configuration issues will be a problem only for Solaris 11.0 & 11.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants