On Mon, Jan 16, 2012 at 6:01 PM, Ryan Bowlby <rbowlby83@gmail.com>
wrote:> I have a somewhat abstract best practice question. In some instances
> fully applying a node''s puppet catalog results in that node
> interacting with production infrastructure. Sometimes you want to
> provision a new host and have it apply it''s puppet catalog but not
yet
> integrate into the production environment. What methods have people
> taken to delay the final production state of a host without disabling
> puppet entirely? Also, any terminology I should be aware of?
>
> Example:
>
> host provisioned -> initial puppet apply -> system and services
> configured -> waiting for prod deployment -> deployed
>
This sounds like a good use case for puppet environments. You could
have an environment that does much of the prep-work and then another
that actually cuts it into the production state. You would just have
to change the environment the client is utilizing.
http://docs.puppetlabs.com/guides/environment.html
> --
> 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.
>
--
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.