Forwarding this again so that Eroma can reply to thread. Thanks Amila
On Thu, Apr 3, 2014 at 2:18 PM, Suresh Marru <[email protected]> wrote: > Thanks Saminda, Amila, Terri for this nice discussion. > > Eroma, > > Since you are working on capturing the sequence diagram for Airavata > operations, it will be good to share that and then discuss fault tolerance > after every one is on same page with all the steps. > > Suresh > > > On Tue, Apr 1, 2014 at 4:00 PM, Amila Jayasekara <[email protected] > >wrote: > > > One suggestion is to first identify states in the system. Then identify > > actions (operation / method invocations) which change the state of the > > system. Then model FT cases by analyzing system state after and before a > > failure (during those operation invocations). > > > > Thanks > > Amila > > > > > > On Tue, Apr 1, 2014 at 3:49 PM, Saminda Wijeratne <[email protected] > > >wrote: > > > > > Hi All, > > > > > > We are trying to identify scenarios in job management which is critical > > to > > > provide fault tolerant solutions. The spreadsheet[1] contains a list of > > > such use cases I have compiled to the best of my knowledge (which is no > > way > > > complete). Thoughts are welcome (reply/comment or edit spreadsheet) > > > > > > I think it is particularly useful to learn how gateways like > > > CIPRES/NSG/Ultrascan (who has a large user base) already handle these > > > situations. Spreadsheet updated to record those as well. > > > > > > (if you don't have edit privileges just drop me a mail/reply) > > > > > > Thanks and Regards, > > > Saminda > > > > > > 1. > > > > > > > > > https://docs.google.com/spreadsheets/d/1eukcg2nXIoMzXa0GakNQVIICMd8y0UYGGjQs32232Hs/edit#gid=1448745788 > > > > > >
