May 26th CloudSync Update
Chris Wilper
It's been a couple weeks since I sent an official update out. Last
week I was in the midst of getting the "List" tasks working and wanted
to make a little more headway before sending out another report.
Here's what's been done since the last update:
1) The demo site has moved to a more memorable URL and is now using a
legit SSL cert so you don't get the annoying browser warnings anymore:
https://cloudsync.duraspace.org/
2) The entire task lifecycle is implemented. Long-running tasks can be
paused and/or canceled while running. Any number of tasks may be run
at once. At server shutdown, any tasks that are still active are
auto-canceled as part of the clean shutdown process.
3) List tasks now work vs. Fedora and DuraCloud. The demo site is
using a local Fedora instance that has been populated with the
out-of-box Fedora demo objects, so if you "List All Objects in Fedora
Repository" and "View Log", you'll see those objects. Listing other
kinds of Object Sets (query-based, etc) also works. Note that
query-based List tasks do NOT work against DuraCloud. It's a little
confusing right now because the UI lets you (for example) specify that
you want to list all content models (a RDF query-based Object Set) in
a DuraCloud-based Object Store. If you run that task, it will
ultimately result in an error because DuraCloud doesn't have an
RDF-based search index.
4) Copy tasks are started, but the actual physical copying is not done
yet. When specifying a copy task, you choose the Object Set, the
Object Store against which to materialize the set, AND the source and
destination Object Stores. Hopefully that makes enough sense for now,
but I realize the UI could do a better job of explaining it.
5) Tasks can be run automatically at creation time (by default).
I will probably send out one last dev status update before Open
Repositories. Look for that late next week. By that time, I should
have the basic copy functionality working and will be preparing to do
the initial (beta) release and starting to think about testing.
In the meantime, as usual, individual emails to me or comments via
this list are very welcome.
Thanks,
Chris