70 likes | 181 Views
GIG Software Integration Project Plan, PY4-PY5. Lee Liming Mary McIlvain John-Paul Navarro. Demand-driven Tasks. Operating central services (0.1 FTE) MDS Index (used by docs, user portal, inca) Build & Test Dispatcher (used internally for efficiency) Maintain current CTSS kits (0.45 FTE)
E N D
GIG Software IntegrationProject Plan, PY4-PY5 Lee Liming Mary McIlvainJohn-Paul Navarro
Demand-driven Tasks • Operating central services (0.1 FTE) • MDS Index (used by docs, user portal, inca) • Build & Test Dispatcher (used internally for efficiency) • Maintain current CTSS kits (0.45 FTE) • Keep software & requirements current, respond to issues • Seven (of the 11) CTSS kits @ ~5% FTE each • Area coordination (0.73 FTE) • SW WG chair, lots of coordination with many other teams • Package software (1.9 FTE) • Support new or updated software capabilities driven by other TG areas (and ultimately by the users) • E.g., scheduling kits, changed/updated data kits, client toolkits • Any additional coordination that people demand • These tasks are not pre-ordained. They will be driven by demand.
Information Services Enhancements Expanded content *HPC Software inventory Data collections GIG operated services Hardware capabilities (New capability kits) Batch Queue Prediction (BQP) Core 2.0 RP local capabilities etc. Scheduling information Science Gateway information Expanded meta-data Information services meta-data
Information Services Enhancements Expanded formats and interfaces Web 2.0, WS/REST, etc publishing Expanded community Community information Peer grid information Improved reliability .999 TeraGrid wide availability
Application Hosting Service Partnership • 0.25 FTE (heavily leveraging the partnership) • Purpose: Significantly reduce the cost and complexity of deploying/maintaining customized user services by automating obvious tasks and integrating with existing resource management and accounting systems. • Pre-requisites (in PY3) • Form a working partnership with RP(s) and users • Complete an operational prototype • Prototype in operation on at least one RP system • Prototype used by 1-3 user teams • Significant goals (PY4 & PY5) • Integrate with TG central accounting system • Add support in Inca, user docs, operations, help desk • Document the service definition and reference implementation for use by other RPs • Expand the user base • Expand the RP host base
Public Build & Test Service • 0.2 FTE • Purpose: Offer software build & test system required by OCI for software development awards on TeraGrid systems. • Significant goals: • Decouple B&T from current CTSS core (make optional) • Define service definition & reference implementation • Harden existing central service • Expand user base among RP software maintainers • Explore expanding user base to include users (probably OCI and CISE software developers)