| 1 |
On 2015-01-10 23:11, Alan McKinnon wrote: |
| 2 |
> On 10/01/2015 21:40, Tomas Mozes wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Ansible is a not a backup solution. You don't need to download your |
| 6 |
>> /etc |
| 7 |
>> from the machines because you deploy your /etc to machines via |
| 8 |
>> ansible. |
| 9 |
>> |
| 10 |
>> I was also thinking about putting /etc in git and then deploying it |
| 11 |
>> but: |
| 12 |
>> - on updates, will you update all configurations in all /etc repos? |
| 13 |
>> - do you really want to keep all the information in git, is it |
| 14 |
>> necessary? |
| 15 |
> |
| 16 |
> The set of fileS in /etc/ managed by ansible is always a strict subset |
| 17 |
> of everything in /etc |
| 18 |
> |
| 19 |
> For that reason alone, it's a good idea to back up /etc anyway, |
| 20 |
> regardless of having a CM system in place. The smallest benefit is |
| 21 |
> knowing when things changed, by the cm SYSTEM or otherwise |
| 22 |
|
| 23 |
For what reason? |
| 24 |
|
| 25 |
And how does a workflow look like then? You commit changes to your git |
| 26 |
repo of ansible. Then you deploy via ansible and check the /etc of each |
| 27 |
machine and commit a message that you changed something via ansible? |
Archives