[Dev] Hubble and config restore

[Brett Wooldridge]

You tha man.


On 2/13/08 2:03 AM, "Dylan White" <dwhite at alterpoint.com> wrote:

Brett,

Fortunatley, I have been designing the restore functionality to be very similar to the backup job; I have a RestoreJob and RestoreTask that both live in the "org.ziptie.server.core.jobs" bundle under a new package name.  While it seems like the most often use case is to run a restore operation interactively, I figured that there was no point in NOT getting all the functionality of a job for free.

- Dylan
________________________________________
From: dev-bounces at ziptie.org [dev-bounces at ziptie.org] On Behalf Of Ryan Kruse [rkruse at alterpoint.com]
Sent: Tuesday, February 12, 2008 7:54 AM
To: 'dev at ziptie.org'
Subject: Re: [Dev] Hubble and config restore

I think this may be how Dylan is putting it together already.  i will update the scoping tasks to reflect it.


----- Original Message -----
From: dev-bounces at ziptie.org <dev-bounces at ziptie.org>
To: ZipTie Development List <dev at ziptie.org>
Sent: Tue Feb 12 04:51:34 2008
Subject: [Dev] Hubble and config restore

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


_______________________________________________
Dev mailing list
Dev at ziptie.org
http://mailman.ziptie.org/listinfo/dev

_______________________________________________
Dev mailing list
Dev at ziptie.org
http://mailman.ziptie.org/listinfo/dev


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