You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it make sense to synchronize nodes using bittorrent instead of rsync when reaching node:all, especially with high --concurrency setting?
There's already a tool that does it: https://github.com/lg/murder and I was wondering whether is it worth exploring this idea in the context of littlechef. What do you think?
The text was updated successfully, but these errors were encountered:
Of course bittorrent distribution would not pose a bottleneck as rsync may do with high concurrency. On the other hand if we start thinking on this terms, then you get into MCollective & co territory, and we would have to rethink the purpose of LittleChef.
Would it make sense to synchronize nodes using bittorrent instead of rsync when reaching
node:all
, especially with high--concurrency
setting?There's already a tool that does it: https://github.com/lg/murder and I was wondering whether is it worth exploring this idea in the context of littlechef. What do you think?
The text was updated successfully, but these errors were encountered: