Hey there,

i'm stuck with the plugin in modules section.
i've got 2 environments set called
development and production.

my puppet.conf on the puppetmasterd looks like this.

[development]
    manifest = /etc/puppet/development/manifests/site.pp
    manifestdir = /etc/puppet/development/manifests
    templatedir = /etc/puppet/development/manifests/templates
    modulepath = /etc/puppet/development/modules

[production]
    manifest = /etc/puppet/production/manifests/site.pp
    manifestdir = /etc/puppet/production/manifests
    templatedir = /etc/puppet/production/manifests/templates
    modulepath = /etc/puppet/production/modules

[puppetmasterd]
    dbuser = puppet
    dbname = puppet
    dbpassword = password
    dbadapter = mysql
    dbserver = localhost
    dbsocket = /var/lib/mysql/mysql.sock
    masterport = 8140
    group = root
    storeconfigs = true
    node_name = facter
    user = root
    autosign = true
    libdir = /opt/puppet-dashboard

Al my clients are connecting with this puppet.conf:

[puppetd]
    pluginsync = true
    factsync = true
    environment = development
    listen = false
    report = true
    yamldir = /var/puppet/yaml
    node_name = facter
    rrddir = /var/puppet/rrd
    rrdinterval = 1800
    railslog = /var/puppet/log/rails.log
    templatedir = /var/puppet/templates

now i wanted to have the sysctl plugin inserted in my development
environment without harming anything in production.
http://github.com/duritong/puppet-sysctl

Now this page is refering to me, that this will not work...
http://projects.puppetlabs.com/projects/puppet/wiki/Using_Multiple_Environments
"Note that currently Plugins In Modules don’t mix well with
environments."

meaning that i should create this?
/etc/puppet/development/modules/facts
/etc/puppet/development/modules/plugins/files/puppet/provider/sysctl/
parsed.rb
/etc/puppet/development/modules/plugins/files/puppet/type/sysctl.rb

but of course here it still stating:
http://docs.reductivelabs.com/guides/plugins_in_modules.html

in 0.25.0 and later releases, Puppet changes uses ‘lib’ for the name
of the plugins directory.
This change was introducued in 0.25.0 and modules with an outdated
plugins directory name will generate a deprecation warning. The
plugins directory will be formally deprecated in the Rowlf release of
Puppet. This deprecation changes your module paths to:

<MODULEPATH>/<module>/lib/puppet/type
For providers, place them in:

<MODULEPATH>/<module>/lib/puppet/provider
Similarly, Facter facts belong in the facter subdirectory of the
library directory:

<MODULEPATH>/<module>/lib/facter
So, if we are using our custom module and our modulepath is /etc/
puppet/modules then types and facts would be stored in the following
directories:

/etc/puppet/modules/custom/lib/puppet/type
/etc/puppet/modules/custom/lib/puppet/provider
/etc/puppet/modules/custom/lib/facter


so with other words:
how do i needs to setup the filesystem to actually sync my custom
modules over to the client etc...
hope anybody can help.. i've lost the complete overview...

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Reply via email to