Initial thoughts on Remote Issues
- Security issues
- All components accessing a cluster must be authorized against the cluster; storage component accessed by the cluster also need to be a trusted id.
- New plugins identification and registration in a secure way
- P2P / Thinking@home execution of plugins
- Data flow between remote components. Requirements such as BW must be considered
- Communication between plugins (e.g. via MPI?) add references
- Location of remote plugins. Plugin discovery. E.g. UDDI (OASIS defined) add references
- Registration of new plugins and dynamic registration in execution time
- Implementation language, execution platform: Web Services are independent of both
- There can be multiple implementations of a single WSDL interface. E.g., the same service could be built for Linux and Windows machines, and the user would not realise (or care) which platform was hosting the service.
- WSRF (following initial OGSA/OGSI specifications) adds state to Web services in order to control the remote service during its lifetime(stateful Web Services, Grid Services).
LarkcProject/WP5/docs/platform/Remote Issues (last edited 2008-09-29 09:27:50 by ?GeorginaGallizo)