[MPI3-IO] Fault Tolerance & I/O Discussion

[Josh Hursey]

Try the new link (I had to close the other poll due to a timezone problem):
  http://www.doodle.com/yifhpi5emyyzrspa

-- Josh

On Tue, Jan 31, 2012 at 4:41 PM, Mohamad Chaarawi <chaarawi at hdfgroup.org>wrote:

>  Hi Josh,
>
> When I click the link, it says the poll has been deleted.
>
> Thanks,
> Mohamad
>
>
> On 01/31/2012 11:52 AM, Josh Hursey wrote:
>
> (Cross posted to both the I/O and FT MPI-3 listservs)
>
>  During the FT plenary session at the Jan. MPI Forum meeting there were
> some concerns about fault tolerance semantics in the I/O chapter. We did
> not have much time to fully discuss the additional semantics during the
> meeting. To make sure that we push towards a complete set of semantics
> useful for the I/O community in the next draft I would like to have a
> teleconf to discuss the I/O chapter of the FT proposal. Preferability in
> the next week and a half (so we have time to fine tune things before the
> next forum meeting).
>
>  Below is a link to a doodle poll to find a good time for a teleconf. If
> you are interested in participating in this discussion, please fill this
> poll out by 2 PM Eastern on Thurs. Feb. 2 so we can set the date/time.
>    http://www.doodle.com/s3hz9daeh8pn483m
>
>  Thanks,
> Josh
>
>  --
> Joshua Hursey
> Postdoctoral Research Associate
> Oak Ridge National Laboratory
> http://users.nccs.gov/~jjhursey
>
>
> _______________________________________________
> MPI3-IO mailing listMPI3-IO at lists.mpi-forum.orghttp://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-io
>
>
>
> _______________________________________________
> MPI3-IO mailing list
> MPI3-IO at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-io
>
>


-- 
Joshua Hursey
Postdoctoral Research Associate
Oak Ridge National Laboratory
http://users.nccs.gov/~jjhursey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-io/attachments/20120131/43eddbda/attachment-0001.html>