Hi Bertrand, You are trying to upgrade the target system and you want to keep a log of the changes in the source system, right?
We have a way to put an agent in passive mode, that means it will not deliver any packages, and it only queues them. When you want to sync the target systems you would switch the state to active. Replaying is not currently possible, unless we clone the state of the agent just before switching it to active. The agent state is made of sling queues + binaries for distribution packages. We can probably implement an agent that has a snapshot state and can be rewind to that state. Marius On 12/16/14, 2:21 PM, "Bertrand Delacretaz" <[email protected]> wrote: >Hi, > >I'm looking at using the new Content Distribution module to help >upgrade Sling-based systems with minimal downtime. > >A possible scenario is to configure a distribution agent to note all >changes occurring after a given time T1, under a given content folder, >and save the result in a list of changes C. > >Then, later and maybe several times, replay C to a different system >that contains a copy of the content at T1, in order to bring it in >sync with the source system. > >Is that already possible, and if not how hard would that be to implement? > >-Bertrand
