# Patching using local repository

**URL:** <https://forum.ansible.com/t/patching-using-local-repository/30461>\
**Category:** Ansible Project\
**Created:** [May 31, 2019, 1:32pm UTC](https://forum.ansible.com/t/patching-using-local-repository/30461 "2019-05-31T13:32:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dung\_Do](https://avatars.discourse-cdn.com/v4/letter/d/8baadc/32.png) [@Dung\_Do](https://forum.ansible.com/u/Dung_Do)\
**Post date:** [May 31, 2019, 1:32pm UTC](https://forum.ansible.com/t/patching-using-local-repository/30461/1 "2019-05-31T13:32:54Z")

</div>

I am thinking about pointing Ansible to my local repository for updates. How do I accomplish the task? And more importantly, is pointing Ansible to local repository the right way to design Ansible patching architect?

---

<div class="post-metadata">

**Author:** ![Dick\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@Dick\_Visser](https://forum.ansible.com/u/Dick_Visser)\
**Post date:** [May 31, 2019, 5:02pm UTC](https://forum.ansible.com/t/patching-using-local-repository/30461/2 "2019-05-31T17:02:38Z")

</div>

> I am thinking about pointing Ansible to my local repository for updates. How do I accomplish the task? And more importantly, is pointing Ansible to local repository the right way to design Ansible patching architect?

What repositories? And updates for what?  
OS updates, ansible updates, software updates?

Also, what do you mean by "design Ansible patching architect"?

Please give some more information.

---

<div class="post-metadata">

**Author:** ![Dung\_Do](https://avatars.discourse-cdn.com/v4/letter/d/8baadc/32.png) [@Dung\_Do](https://forum.ansible.com/u/Dung_Do)\
**Post date:** [May 31, 2019, 5:21pm UTC](https://forum.ansible.com/t/patching-using-local-repository/30461/3 "2019-05-31T17:21:55Z")

</div>

Hi Dick  
What repositories? And updates for what? Centos repository. OS and security updates

Also, what do you mean by “design Ansible patching architect”? when I say design Ansible patching architect I meant the way I am planning to set up patching so Ansible pointing to a local repository, instead of a regular repository makes sense. The reason I am thinking about pointing Ansible to the local repository is because our Ansible clients don’t have access to the internet.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Lozada\_De\_L](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@Jonathan\_Lozada\_De\_L](https://forum.ansible.com/u/Jonathan_Lozada_De_L)\
**Post date:** [May 31, 2019, 5:25pm UTC](https://forum.ansible.com/t/patching-using-local-repository/30461/4 "2019-05-31T17:25:48Z")

</div>

use the yum and yum repository modules to do this. With the yum repository module you point your servers to the web servers that host the rpms. If you google around you can find guides on how to create a yum repository. The biggest thing is too make sure your servers are not that far from the yum repo. For example, my DC is in Atlanta and my yum repo is in Japan.
