VersionControlledEtc
2270
Comment: dpkg-bzr?
|
2273
|
Deletions are marked like this. | Additions are marked like this. |
Line 18: | Line 18: |
# Andrew is a systems administrator and his mail server has stopped working. Richard, another administrator, made some changes a week ago but has now gone on holiday to his residence in France. Andrew is unsure what changes Richard made to the mail configuration, but he can use the automated version history to look at the changes made before Richard went away. | # Andrew is a systems administrator and his mail server has stopped working. Richard, another administrator, made some changes a week ago but has now gone on holiday to his residence in France. Andrew is unsure what changes Richard made to the mail configuration, but he can use the automated version history to look at the changes made before Richard went away. |
Line 20: | Line 20: |
# Karl has a box which was working and set up the way he likes. After a failed dist-upgrade his system is left in a half configured state. He would find it benefical to be able to roll back to just before the upgrade. | # Karl has a box which was working and set up the way he likes. After a failed dist-upgrade his system is left in a half configured state. He would find it benefical to be able to roll back to just before the upgrade. |
Line 22: | Line 22: |
# Igor has a few servers upon which he has made identical bespoke modifications to /etc. He would like to be able to store these modifications centrally and then distribute them to his servers when he changes them. | # Igor has a few servers upon which he has made identical bespoke modifications to /etc. He would like to be able to store these modifications centrally and then distribute them to his servers when he changes them. |
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/etc-in-svn
Created: Date(2006-05-17T13:56:05Z) by AndrewBeresford
Contributors: AndrewBeresford KarlGoetz
Packages affected: dpkg
Summary
The specification describes an enhancement to keep automated versioned history of files under /etc.
Rationale
Over time, configuration changes occur and it is easy to forget why changes were made, or what was in a config file prior to the change. It becomes even more difficult when there are multiple administrators working on a machine over a period of time.
Use cases
- # Andrew is a systems administrator and his mail server has stopped working. Richard, another administrator, made some changes a week ago but has now gone on holiday to his residence in France. Andrew is unsure what changes Richard made to the mail configuration, but he can use the automated version history to look at the changes made before Richard went away. # Karl has a box which was working and set up the way he likes. After a failed dist-upgrade his system is left in a half configured state. He would find it benefical to be able to roll back to just before the upgrade. # Igor has a few servers upon which he has made identical bespoke modifications to /etc. He would like to be able to store these modifications centrally and then distribute them to his servers when he changes them.
Scope
Design
Implementation
So far I have tried out the following;
in /etc/;
bzr init bzr add * bzr commit -m "Initial Import"
then I added the following to roots crontab;
0 * * * * cd /etc; bzr commit -v -m "Automated update at ``date``" >& /dev/null
Code
Data preservation and migration
Outstanding issues
- Depending on implimentation files modified by a user could fail to be updated in VCS
- Automating this process at the dpkg level would be highly intrusive.
- is bzr the right choice? I think it is, but what do I know?!
- Is it useful to get dpkg to update the bzr tree when it does things in /etc?
BoF agenda and discussion
VersionControlledEtc (last edited 2010-09-23 04:17:25 by dhcp198-158)