update changelog, move __rsyncer from types to other/ (see README.inclusion)

Signed-off-by: Nico Schottelius <nico@brief.schottelius.org>
This commit is contained in:
Nico Schottelius 2012-01-26 11:56:12 +01:00
parent 88ea9bf245
commit 8447702c50
6 changed files with 28 additions and 1 deletions

View file

@ -1,3 +1,9 @@
Changelog
---------
* Changes are always commented with their author in (braces)
* Exception: No braces means author == Nico Schottelius
2.0.6: 2.0.6:
* Bugfix __apt_ppa: * Bugfix __apt_ppa:
Also remove the [ppa-name].list file, if empty. (Tim Kersten) Also remove the [ppa-name].list file, if empty. (Tim Kersten)
@ -9,7 +15,6 @@
* New Type: __rvm_gem (Evax Software) * New Type: __rvm_gem (Evax Software)
* New Type: __rvm_gemset (Evax Software) * New Type: __rvm_gemset (Evax Software)
* New Type: __rvm_ruby (Evax Software) * New Type: __rvm_ruby (Evax Software)
* New Type: __rsyncer (Daniel Maher)
* Feature core: Added new dependency resolver (Steven Armstrong) * Feature core: Added new dependency resolver (Steven Armstrong)
2.0.5: 2012-01-18 2.0.5: 2012-01-18

View file

@ -0,0 +1,22 @@
Description:
Type that supports transfer of huge data, which is a general problem in
configuration management systems.
Good solution using standardised rsync approach.
Problem:
Uses root@$__target_host:$destination notation for transfer.
This breaks the concept of being able to replace __remote_exec and
__remote_copy and then doing chroot or different stuff.
This breaks for instance, if __remote_copy = cp and the destination is
a local chroot.
Solutions:
- Have cdist provide support for rsync syntax?
- Integrate __rsyncer more in line with philosohpy of other components
- Think about the general way of __rsyncer and what cdist would need
to provide for general solution.