Using NFS pupmod

30 views
Skip to first unread message

Patrick Devine

unread,
Jun 27, 2017, 2:58:14 PM6/27/17
to SIMP Q&A Forum
We are currently switching from SIMP 4 to SIMP 6 (also upgrading to RHEL7). In the previous NFS module we would define our nfs server in our default yaml file as shown in the Read me file (example nfs::server: "your.server.fqdn"). In the SIMP 6 module the read me still states to use this value in the default yaml but I am not sure if it is even being used any more. In the old nfs::client class I see where the $nfs_server is set as a param like this $nfs_server = defined('$::nfs::server') ? { true => getvar('::nfs_server') , default => hiera('nfs::server') }. In the new nfs::client class the nfs_server is not a defined value but looking at the nfs::client::mount class I can see that $nfs_server should be there but nothing defines is Simplib::Host $nfs_server...

Is there a new way I am suppose to supply the $nfs_server value? Was the nfs::server value removed from the module for a specific reason and if so why would I need it in the default.yaml?

Being bangin my head against the monitor for a couple hours now and I just can see the logic.

Thanks.

Trevor Vaughan

unread,
Jun 27, 2017, 4:25:50 PM6/27/17
to Patrick Devine, SIMP Q&A Forum
Hi Patrick,

There was a MASSIVE rewrite to the SIMP NFS modules which uncovered several bugs and a host of other issues with the previous implementation.

The documentation at http://simp.readthedocs.io/en/master/user_guide/HOWTO/NFS.html should provide a good general purpose walkthrough.

We'll check the README to make sure that it is correct as well.

Please let us know if you have any other issues or where our docs can be improved.

Thanks,

Trevor

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/92f2618e-0110-46e5-a319-4e7ffcd90245%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Trevor Vaughan
Vice President, Onyx Point, Inc

-- This account not approved for unencrypted proprietary information --

Patrick Devine

unread,
Jun 28, 2017, 9:51:26 AM6/28/17
to SIMP Q&A Forum, pdde...@sabine-solutions.com
I figured it was something like that. I put the new configs from the HowTo in place but now I am getting an issue with the Simplib::Netlist resource type is not being found. I see in the Simplib readme that pluginsync needs to be enabled on the clients however the puppet docs say this config should be true by default. Do I need to set the Simplib module in my default yaml for all hosts so they can use these resources?

Sorry to bug you but our SIMP guru decided this was a good week to go on vacation.

On Tuesday, June 27, 2017 at 4:25:50 PM UTC-4, Trevor Vaughan wrote:
Hi Patrick,

There was a MASSIVE rewrite to the SIMP NFS modules which uncovered several bugs and a host of other issues with the previous implementation.

The documentation at http://simp.readthedocs.io/en/master/user_guide/HOWTO/NFS.html should provide a good general purpose walkthrough.

We'll check the README to make sure that it is correct as well.

Please let us know if you have any other issues or where our docs can be improved.

Thanks,

Trevor
On Tue, Jun 27, 2017 at 2:58 PM, Patrick Devine <pdde...@sabine-solutions.com> wrote:
We are currently switching from SIMP 4 to SIMP 6 (also upgrading to RHEL7). In the previous NFS module we would define our nfs server in our default yaml file as shown in the Read me file (example nfs::server: "your.server.fqdn"). In the SIMP 6 module the read me still states to use this value in the default yaml but I am not sure if it is even being used any more. In the old nfs::client class I see where the $nfs_server is set as a param like this $nfs_server = defined('$::nfs::server') ? { true => getvar('::nfs_server') , default => hiera('nfs::server') }. In the new nfs::client class the nfs_server is not a defined value but looking at the nfs::client::mount class I can see that $nfs_server should be there but nothing defines is Simplib::Host $nfs_server...

Is there a new way I am suppose to supply the $nfs_server value? Was the nfs::server value removed from the module for a specific reason and if so why would I need it in the default.yaml?

Being bangin my head against the monitor for a couple hours now and I just can see the logic.

Thanks.

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+uns...@googlegroups.com.

Trevor Vaughan

unread,
Jun 28, 2017, 10:20:54 AM6/28/17
to Patrick Devine, SIMP Q&A Forum
No problem.

'simplib' should be an automatic dependency for all of our modules and present in the classpath without issue.

Did you run 'puppetserver reload' after you updated your code?

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/eb3c40ed-a649-4383-a672-b54736b15e66%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Patrick Devine

unread,
Jun 28, 2017, 10:33:47 AM6/28/17
to SIMP Q&A Forum, pdde...@sabine-solutions.com
That was my thought as well that the simplib would be something all modules could access. I just ran a puppetserver reload after modified the module and when I do a puppet run I am still getting the Resource Type not found.

I am not using the site/manifest/nfs_server.pp structure from the example. We have a custom module for all our site specific classes where I am putting the nfs_server and nfs_client classes. Any ideas on how to check the classpath is getting set correctly? or why a module wouldn't have simplib as a dep?

Trevor Vaughan

unread,
Jun 28, 2017, 10:49:41 AM6/28/17
to Patrick Devine, SIMP Q&A Forum
Ah! The custom module may be it. Can you make sure that the metadata.json has a requirement for simplib in it inside of your module?

Thanks,

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/9cd36b07-c84e-4f66-8121-f879f37bf49b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Patrick Devine

unread,
Jun 28, 2017, 10:57:34 AM6/28/17
to SIMP Q&A Forum, pdde...@sabine-solutions.com
That got it.. Added it to the metadata.json and boom.. Simplib resources now show up..

Thanks

Trevor Vaughan

unread,
Jun 28, 2017, 11:01:19 AM6/28/17
to Patrick Devine, SIMP Q&A Forum
Yeah, that's something that was added in Puppet 4 to try and keep incompatible code from being loaded into the module space.

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/c7cf9652-b9f2-4a03-a8b5-e88004f18a00%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages