[Dev] Hubble and config restore

[Brett Wooldridge]

I'd like us to avoid writing a Provider for the config restore feature.  The config restore, just like a backup should be a job scheduled through the Scheduler Provider (even interactive backups are "Run now" schedules).  There is no special backup provider, and it should be the same with restore.  I believe that the JobData abstraction is capable of holding all of the relevant inputs to the restore (or just about any other operation we can come up with).  Doing it this way ensures that there aren't two paths to executing backup/restore, and once implemented we get scheduling of the operation for "free".

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ziptie.org/pipermail/dev/attachments/20080212/20496820/attachment.html