HPCP Extensions Session Presenter: Steven Newhouse Note Taker: Stephen McGough Where are the specifications for public comment? - GridForge - But GridForge is broken - This is known problem - Will there be extra time for this? - Clock only starts when they appear on GridForge, also there's a 60 day period. Other extensions? - SAML extension (but person to champion this is not present) - Extend State model - what are the rules for doing this? (hold / suspend job) - BES defines how to extend state model - But how do I extend the interface provided for the EPR to change the job state - Could just define a new port type which will not break current compatibility - Can inspect a BES service to define what extensions are available - Problem: which state changes are allowed: which ones are allowed? - same as previous question? - return to pending state? - Not currently allowed through BES - State diagram is too restrictive - If you allow state transition which is not in BES then you're not BES compliant - What is your use case? - If your data transfer fails go back from failed to staging out state later for retry - Would it be better to stay in running and sub-state that? - JSDL extensions: - Access control - Notification of activity - Is this Activity schema work? - Terminal states - how long does job stay in this state. Extension to JSDL - Write this up as an extension and submit it - Where to bring this up? BES/JSDL/HPCP - Here for now and will figure out where it should end up