Puppet users - May 2012 - Is there a quick way to export a manifest from a master/client to a new standalone?

I have a large puppet master / client setup with lots of files and
templates and modules and so on. Is there a way to make a stand alone
manifest for one server so I can hand it to a third party?

For example, I have www03.example.com as one of many servers. I need
to create a manifest for that one server for a new stand alone server.
Is there a quick way to do this?

Thanks,
James Glenn

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi James,

On Mon, May 21, 2012 at 3:02 PM, thedonkdonk <thedonkdonk@gmail.com>
wrote:
> I have a large puppet master / client setup with lots of files and
> templates and modules and so on. Is there a way to make a stand alone
> manifest for one server so I can hand it to a third party?
If you mean to take the resultant catalog for a given machine and use
that same catalog on another machine without interacting with the
Puppet Master, you may want to take a look at the catalog Face. Try
running ''puppet man catalog'' on a newer version of Puppet.

In short, it sounds like you''d want to retrieve the catalog for
www03.example.com from the Puppet Master with the download action,
ship it around however you''d like and use the apply action with
--terminus yaml to apply that catalog.

Does that sound like what you''re looking for? You''re going to
lose
some things like remote file retrieval and dynamic facts evaluation by
taking this approach but if you can''t access a Puppet Master or apply
local modules, this is another route you can take. Final disclaimer, I
haven''t actually used this Face more than basic experimentation so
YMMV.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mon, May 21, 2012 at 8:16 PM, Ryan Coleman <ryan@puppetlabs.com>
wrote:
> Hi James,
>
> On Mon, May 21, 2012 at 3:02 PM, thedonkdonk <thedonkdonk@gmail.com>
wrote:
>> I have a large puppet master / client setup with lots of files and
>> templates and modules and so on. Is there a way to make a stand alone
>> manifest for one server so I can hand it to a third party?
>
> If you mean to take the resultant catalog for a given machine and use
> that same catalog on another machine without interacting with the
> Puppet Master, you may want to take a look at the catalog Face. Try
> running ''puppet man catalog'' on a newer version of
Puppet.
>
> In short, it sounds like you''d want to retrieve the catalog for
> www03.example.com from the Puppet Master with the download action,
> ship it around however you''d like and use the apply action with
> --terminus yaml to apply that catalog.
>
> Does that sound like what you''re looking for? You''re
going to lose
> some things like remote file retrieval and dynamic facts evaluation by
> taking this approach but if you can''t access a Puppet Master or
apply
> local modules, this is another route you can take.
Yes, this sounds like what I am looking for. I need to include file
content as well as package and user management. Will this work? Should
I try a different tactic?

-- 
Thanks,
James Glenn

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mon, May 21, 2012 at 7:22 PM, James Glenn <thedonkdonk@gmail.com>
wrote:
> Yes, this sounds like what I am looking for. I need to include file
> content as well as package and user management. Will this work? Should
> I try a different tactic?
What are your limitations? Why are you unable to rely on the Puppet
Agent -> Puppet Master model? Perhaps the community can address your
concerns and see if there''s an opportunity to use this functionality?

Shipping pre-compiled catalogs is an alternative to that model but
it''s got a number of limitations, file serving being one of them. You
may also want to experiment with shipping modules and manifests to
your remote machines and using Puppet Apply to locally compile a
catalog, move files around and so on.

--Ryan

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.