大网数据广告活动
服务器运维问答

How do you manage package updates with Ansible?

· 52CE 我爱测

I'd like to use Ansible to roll out package updates to my machines. But I'd like to test those updates on a local vm first. How is this usually achieved in the real world ? Do I "lock" every important package in my Ansible config…

问题原文

原帖链接 · agregoire · CC BY-SA 3.0

I'd like to use Ansible to roll out package updates to my machines. But I'd like to test those updates on a local vm first. How is this usually achieved in the real world ?

  • Do I "lock" every important package in my Ansible configuration to a specific version and then test every update ?
  • Do I periodically get a list of upgradable packages and update them all at the same time on my vms, then on my servers ? I'd probably have some trouble keeping my servers and vms synchronized.

Is there a best practice for managing updates ?

已采纳解答

原帖链接 · Michael Hampton · CC BY-SA 3.0

Ansible wasn't really meant to solve this sort of problem. It can do so, but it would be cumbersome at best.

Something like Katello (the open source on which Red Hat Satellite 6 is based) can handle this sort of thing well. It maintains packages at the exact versions you've tested and allows you to promote them from development to staging to production, or define whatever workflow makes sense for you. Not to mention handles bare metal provisioning and many other things. Its only drawback in this scenario is it's well integrated with Puppet, so using it with Ansible may be a bit less automated in places than it otherwise could be.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-04-04)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。