Hi James,
On 11.12.2012 05:41, James Gray wrote:
Now, let's imagine I need to spin up another server to meet some load
but when I do so I find that package y has had a security fix
What sort of solutions are people using to get round this?
You'll have to start managing versions. One way or the other. Client
side there's apt's pinning, yum probably has some plugin to do so.
Server side you can use a custom repo or puppet packages's ensure =>
version.
Another solution might be to have my own package repository
containing just the packages I have tested against and only install
from there but that means another bit of infrastructure to look after
and manage, which I'd like to avoid if at all possible.
For any significant amount of machines and packages, you'll really want
to look into hosting that repo yourself. That way you can
* stage security and other updates
* keep most control over package versions with the least
per-node overhead
* keep installs repeatable
Best Regards, David
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
