# Ubuntu Patch Management

**URL:** <https://forum.ansible.com/t/ubuntu-patch-management/20610>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [February 18, 2016, 3:26am UTC](https://forum.ansible.com/t/ubuntu-patch-management/20610 "2016-02-18T03:26:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_Domigan](https://avatars.discourse-cdn.com/v4/letter/c/a4c791/32.png) [@Chris\_Domigan](https://forum.ansible.com/u/Chris_Domigan)\
**Post date:** [February 18, 2016, 3:26am UTC](https://forum.ansible.com/t/ubuntu-patch-management/20610/1 "2016-02-18T03:26:34Z")

</div>

I’m wanting to manage the rollout of Ubuntu package updates across my production servers.

The workflow I have in mind:

1. Update a test server with the latest packages
2. Test this server for any issues, over the course of a week
3. If all okay, deploy _only these tested updates_ to my production servers. I don’t want any more recent (and therefore untested) updates sneaking in to my production servers.

Could anyone point me in the right direction on how to do this with Ansible?

**Specifically: How can I “capture” the package versions of my test server, and install only those updates to my live systems?**

Thank you!

---

<div class="post-metadata">

**Author:** ![David\_Karban](https://avatars.discourse-cdn.com/v4/letter/d/90db22/32.png) [@David\_Karban](https://forum.ansible.com/u/David_Karban)\
**Post date:** [February 18, 2016, 9:07am UTC](https://forum.ansible.com/t/ubuntu-patch-management/20610/2 "2016-02-18T09:07:18Z")

</div>

Hi,

usually the simplest way is to have your own repository mirror. This way, you firt sync the mirror, upgrade test host and after internal tests, you update rest of servers. After that you can sync repo again and repeat.
