Hi Puppeteers , I am using puppet in such environment where other than exec,service, packages large number of static files (wars,jars,properties files, zips etc) and template need to be served to puppet client other than exec,service, packages,custom resource type. For now what i have written is that all puppet client fetches all form puppet master depending on environment (development,testing ,production etc). lets say at particular time , puppet client is configured for development environment. and only few static file (jars, property files and XML) and template are been modified that to be applied to same puppet client. If i trigger puppet client, than i will fetches all from puppet master and deploy on it. what i want is , Only those things should be triggered that is being updated. and rest should be untouched.(apply patch). Few Questions : How can i achieve "PATCH MANAGEMENT" with puppet? How can i maintain multiple patchs for puppet modules ? what are various ways , i can use to do this ? can I use dynamic manifest approach(only modified stuff) for patch management ? Regards, Sanjiv Singh Software Engineer (iLabs) Impetus Infotech (India) Pvt. Ltd. -- 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, On 12/28/2011 02:26 PM, sanjiv singh wrote:> If i trigger puppet client, than i will fetches all from puppet > master and deploy on it.the complete catalog is fetched, that is true. However, the agent will only touch resources that *do* need a change due running in your development environment.> what i want is , Only those things should be triggered that is being > updated. and rest should be untouched.(apply patch).That''s the normal mode of puppet operation. I suspect there is a misunderstanding here. Before giving any more details, it would probably be helpful if you could rephrase the issues you are facing. Perhaps with a working example of what you see happening and would like to suppress. Cheers, Felix -- 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.
As far as control of software package versions,
I would think you could use the "ensure" metaparameter for the
"package" type
package { "foo":
...
ensure => "1.2.3.4.5-1",
...
}
as opposed to
package { "foo":
...
ensure => latest,
...
}
The first one would give you more control - it would only install when the
catalog is updated rather than auto-updating when a new version appears.
A side-question:
Assume I move from
package { "foo": ensure => "1.2-0", }
to
package { "foo": ensure => "1.5-0", }
and then find that the update breaks other things. Would changing the catalog
back remove the newer version and re-load the older one ?
On Jan 4, 2012, at 7:17 AM, Felix Frank wrote:
> Hi,
>
> On 12/28/2011 02:26 PM, sanjiv singh wrote:
>> If i trigger puppet client, than i will fetches all from puppet
>> master and deploy on it.
>
> the complete catalog is fetched, that is true. However, the agent will
> only touch resources that *do* need a change due running in your
> development environment.
>
>> what i want is , Only those things should be triggered that is being
>> updated. and rest should be untouched.(apply patch).
>
> That''s the normal mode of puppet operation.
>
> I suspect there is a misunderstanding here. Before giving any more
> details, it would probably be helpful if you could rephrase the issues
> you are facing. Perhaps with a working example of what you see happening
> and would like to suppress.
>
> Cheers,
> Felix
>
> --
> 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.
Whoo, hijack :-) On 01/05/2012 03:09 AM, Dan White wrote:> Assume I move from > > package { "foo": ensure => "1.2-0", } > > to > > package { "foo": ensure => "1.5-0", } > > and then find that the update breaks other things. Would changing the catalog back remove the newer version and re-load the older one ?Assuming the package provider you''re using is capable of doing that (apt[itude] is, so should yum), then yes - it will remove whatever "wrong" version it finds on your system and replace it with the one requested. -- 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.
I did not mean to hijack the thread. I thought this information would be helpful to the original poster. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) ----- Felix Frank <felix.frank@alumni.tu-berlin.de> wrote:> Whoo, hijack :-) > > On 01/05/2012 03:09 AM, Dan White wrote: > > Assume I move from > > > > package { "foo": ensure => "1.2-0", } > > > > to > > > > package { "foo": ensure => "1.5-0", } > > > > and then find that the update breaks other things. Would changing the catalog back remove the newer version and re-load the older one ? > > Assuming the package provider you''re using is capable of doing that > (apt[itude] is, so should yum), then yes - it will remove whatever > "wrong" version it finds on your system and replace it with the one > requested.-- 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.