* Richard Brooks <[email protected]> [2012-08-01 13:36:07]:
* [Clemson/Brooks] Development of tools for analytical verification of protocols for deadlock, livelock, performance, and information leakage by leveraging AESOP primitives.
--> Still not sure about this one. Do we have any more detail on how this would actually work before committing to delivering this?
How does it sound to do planning here and implementation in the out years?
It's not about the timing; It's just that I don't currently see how aesop primitives make this task easier/possible (that probably says more about me than about the deliverable). Maybe leave aesop out of it, but keep the rest? That would give you the flexibility to investigate other options if needed.
* [Clemson/Brooks] Tools for identifying and mitigating denial of service incidents.
----> Denial of service and related events are basically accounting for 50% of yr3, 33% of yr 4 and 50% of yr 5 (with yr 4 and yr 5 being the same deliverable). Can we really justify so much effort to this one topic?
Is it an issue in similar storage systems? For example, do lustre/gpfs/... have anything in this area and if not, are they looking into adding this?
Given the intended deployment of the storage system, there might be other areas that could provide more benefit?
Do you have suggestions for anything you might find more useful?
That would be welcome. Coming up with 5 year plans with a one day turn around is challenging.
Ideas from you are very welcome at this point....
Unfortunately, no. :( The only thing I can come up with now is to investigate and implement the authorization for the other frontends we would support? (i.e. for posix for example), but not sure if this makes a good deliverable. (It is something we need though). Ideas/suggestions from other people? Dries