Skip to content

(MODULES-213) Add support for Solaris #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

derekmceachern
Copy link

Added Solaris section to params.pp. In Solaris there are two packages
to install to support ntp, SUNWntpr and SUNWntpu. (Root and User
packages.)
Adding two files to the $package_name array caused the install class
to fail so install.pp was updated so that the $package_name was the
resource title instead of the name attribute.

This change assumes that the packages are already installed for Solaris. If they
are not then this will fail.

This was tested on Solaris 10 update 10 and on SLES 11 SP3 to ensure that it still works for Linux.

Added Solaris section to params.pp. In Solaris there are two packages
to install to support ntp, SUNWntpr and SUNWntpu. (Root and User
packages.)
Adding two files to the $package_name array caused the install class
to fail so install.pp was updated so that the $package_name was the
resouce title instead of the name attribute.

This change assumes that the packages are already installed. If they
are not then this will fail.
@derekmceachern
Copy link
Author

So it looks like I've totally broken the tests with the change to install.pp....

Suggestions on how to make this work for multiple packages?

@hunner
Copy link
Contributor

hunner commented Jun 25, 2014

Thanks for this PR!

You can update the tests to look for a package resource with the title of the $package_name instead of just Package[ntp]. Could you also add a check for the Solaris packages?

@derekmceachern
Copy link
Author

I can certainly try, but I'm really new to this.

Is there a way I can run the Travis tests on my own repository before submitting a new pull request so I can make sure it's clean?

@hunner
Copy link
Contributor

hunner commented Jun 25, 2014

If you just update your branch (as you see here) the travis tests will re-run. You don't want to update the .travis.yml though, so you'll want to rebase your d0750ee commit back out. Then you can just git commit --amend and push until they pass.

@hunner
Copy link
Contributor

hunner commented Jun 25, 2014

I submitted #172 with some test changes and other tweaks, but used your manifest commit. Thanks!

@hunner
Copy link
Contributor

hunner commented Jun 26, 2014

Hmm. Our systems are using CSWntp instead of the SUNW packages. I wonder how we should handle that...

@derekmceachern
Copy link
Author

Couldn't that be solved with Hiera?

I just did a quick test for one of my nodes, and created the following .yaml file:


ntp::package_name:

  • "SUNWntpr"
  • "SUNWntrux"

And it used those modules instead of the defaults in params.pp.

So, couldn't we leave the SUNW packages and then users can override using hiera?

@apenney apenney closed this in #172 Jul 3, 2014
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