Puppet users - Oct 2013 - Exported resources not in the catalog

Hi,

I''m trying to use Puppet ability to export and collect resources using 
PuppetDB.
My PuppetDB and Puppet Master are running on the same host and I used the 
PuppetDB puppet module to install PuppetDB and configure the Puppet master.

Each time the puppet agent runs on a client, the facts and the catalog are 
being pushed in PuppetDB and I can query the PuppetDB server to get 
information on the nodes and the resources.

The point is as soon as I flag a resource as being exported (with @@), the 
resource is not part of the catalog anymore.

Any idea ?

Thanks

I''m using Foreman 1.3 with Puppet 3.3.1

Here is the content of my puppet.conf 

[main]
    # The Puppet log directory.
    # The default value is ''$vardir/log''.
    logdir = /var/log/puppet

    # Where Puppet PID files are kept.
    # The default value is ''$vardir/run''.
    rundir = /var/run/puppet

    # Where SSL certificates are kept.
    # The default value is ''$confdir/ssl''.
    ssldir = $vardir/ssl

    # Allow services in the ''puppet'' group to access key
(Foreman + proxy)
    privatekeydir = $ssldir/private_keys { group = service }
    hostprivkey = $privatekeydir/$certname.pem { mode = 640 }

    # Puppet 3.0.x requires this in both [main] and [master] - harmless on 
agents
    autosign       = $confdir/autosign.conf { mode = 664 }


[agent]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion.  Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is ''$confdir/classes.txt''.
    classfile = $vardir/classes.txt

    # Where puppetd caches the local configuration.  An
    # extension indicating the cache format is added automatically.
    # The default value is ''$confdir/localconfig''.
    localconfig = $vardir/localconfig

    # Disable the default schedules as they cause continual skipped
    # resources to be displayed in Foreman - only for Puppet >= 3.4
    default_schedules = false

    report      = true
    pluginsync  = true
    masterport  = 8140
    environment = production
    certname    = foreman.localdomain
    server      = foreman.localdomain
    listen      = false
    splay       = false
    runinterval = 1800
    noop        = false
    show_diff   = false
### Next part of the file is managed by a different template ###
## Module:           ''puppet''
## Template source: 
''MODULES/puppet/templates/server/puppet.conf.erb''

[master]
    autosign       = $confdir/autosign.conf { mode = 664 }
    reports        = foreman
    external_nodes = /etc/puppet/node.rb
    node_terminus  = exec
    ca             = true
    ssldir         = /var/lib/puppet/ssl
    storeconfigs_backend = puppetdb
    storeconfigs = true

[development]
    modulepath     = 
/etc/puppet/environments/development/modules:/etc/puppet/environments/common:/usr/share/puppet/modules
    config_version = 
[production]
    modulepath     = 
/etc/puppet/environments/production/modules:/etc/puppet/environments/common:/usr/share/puppet/modules
    config_version = 

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

> I''m trying to use Puppet ability to export and collect resources
using
> PuppetDB.
> My PuppetDB and Puppet Master are running on the same host and I used the
> PuppetDB puppet module to install PuppetDB and configure the Puppet master.
>
> Each time the puppet agent runs on a client, the facts and the catalog are
> being pushed in PuppetDB and I can query the PuppetDB server to get
> information on the nodes and the resources.
>
> The point is as soon as I flag a resource as being exported (with @@), the
> resource is not part of the catalog anymore.
Can you clarify what you mean by this? And how you determined that?

Do you mean it no longer runs as part of the catalog it was declared
in? This is expected, unless you are collecting it immediately on the
same node of course.

Or do you mean it is no longer represented in PuppetDB?

Perhaps an example showing where it breaks down might be useful.

ken.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Le jeudi 17 octobre 2013 10:45:12 UTC+2, Ken Barber a écrit
:
>
>
> Can you clarify what you mean by this? And how you determined that? 
>
> Do you mean it no longer runs as part of the catalog it was declared 
> in? This is expected, unless you are collecting it immediately on the 
> same node of course.

That''s what I did not understand. It definitely makes sense now.
Thanks.

>
> Or do you mean it is no longer represented in PuppetDB? 
>
> Perhaps an example showing where it breaks down might be useful. 
>
> ken. 
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.