EGIDS WP 3 workshop Day 2 Operations Model

  • Slides: 5
Download presentation
EGI-DS WP 3 workshop, Day 2 • Operations – Model still not clarified •

EGI-DS WP 3 workshop, Day 2 • Operations – Model still not clarified • Should support both production-level and research services, all kinds of sites w. r. t. their size – People seem to agree towards • A thin layer ensuring NGI interop through definition of accounting/monitoring/etc specs and standards to use • A multi-tier approach a la ROC, w/ ROC == NGI most probably • An entity coordinating (some) NGI work and planning – Exact functions of this entity must be defined • Services targeting high availability for demanding VOs – A group of 5 to convene and suggest a plan (by March 3 rd) of essential services, their availability / manpower reqs • Fotis, Jamie, Per, Rolf, Tiziana

EGI-DS WP 3 workshop, Day 2 • Middleware – DECISION: EGI must drive different

EGI-DS WP 3 workshop, Day 2 • Middleware – DECISION: EGI must drive different stacks towards interoperability through selection / proposition of standards – ISSUE: Must distinguish between core and high-level services. EGI has significant control over foundation services only. – ISSUE: Compromise between production-level infrastructure and being inclusive – DECISION: The EGI will NOT carry out s/w development, only coordinate that if needed. Pot of money to outsource may be an option. • g. Lite must continue being supported by current EGEE partners. Mirco, Claudio, Kudek, Alistair, Flavia to meet again about that on 22 Feb.

EGI-DS WP 3 workshop, Day 2 • Build/test systems – ISSUE: ETICS or a

EGI-DS WP 3 workshop, Day 2 • Build/test systems – ISSUE: ETICS or a similar tool to be used? • �tandards-compliance tests: To be written by EGI? Alternatively, could S that be outsourced to ETSI? • Component selection/validation/deployment [core services] – DECISION on software from commercial/other entities: Validation is a responsibility of interested communities – DECISION: Quality control mechanisms to be used only as rough guidance, not by the book. – DECISION: Component selection driven by EGI as small central facilitator • Legal entity – DECISION: Location to be decided by the NGIs • After a tender? – Agreement that an Mo. U is just a next step (to the Lo. Is), not a legal liability footing. – ISSUE: What percentage of people to be located on-site? (Recommendation to leave this to the managers to decide)

EGI-DS WP 3 workshop, Day 2 • Management – Agreement on the structure proposed

EGI-DS WP 3 workshop, Day 2 • Management – Agreement on the structure proposed by Klaus • Resource allocation – DECISION (? ): Drop resource allocation from EGI functions, leave it all to the NGIs • The NGIs are free to use whatever resources they please, be it cloud computing from commercial providers or whatever – Simple entry strategy for new VOs is needed (esp. for VOs w/ small requirements) • Have spare resources allocated to a catch-all, best-effort VO. Longer term use of this VO implies dedication of resources from the interested scientific group. Resources to be slices from NGI resources. EGI functions as a broker ONLY in this case. – One more group to be created offline and research this issue

EGI-DS WP 3 workshop, Day 2 • Standardization – DECISION: One person coordinating and

EGI-DS WP 3 workshop, Day 2 • Standardization – DECISION: One person coordinating and acting as a liaison to stdn bodies • Policies – DECISION: Not getting into their content at this stage; Only short elaboration for each of the candidate policies identified • Representation of EU grid efforts – Concensus on the need to have such a function.