1 / 16

PY4 Project Report Summary of incomplete PY4 IPP items

PY4 Project Report Summary of incomplete PY4 IPP items. Report. The report is on the wiki under this meeting agenda Outline of report is identical to IPP Only incomplete items are described in this report. User Support.

etan
Download Presentation

PY4 Project Report Summary of incomplete PY4 IPP items

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PY4 Project ReportSummary of incomplete PY4 IPP items

  2. Report The report is on the wiki under this meeting agenda Outline of report is identical to IPP Only incomplete items are described in this report

  3. User Support • HelpDesk and Frontline User Support (US.Coord, US.RP-TR, US.MTG, US.TPS) • While the user satisfaction survey ranking was very high for 2009, we are continuing in PY5 to work on reducing the “ticket open” time to less than 2 weeks.

  4. UFP (1) • Enhanced TeraGrid User Access (UFP.EUA) • Shibboleth related work delayed to PY5 due to PY4 delay in LifeRay implementation. Work on Shibboleth is included in PY5 UFP plans. • Job submission and workflow projects being reconsidered; may be canceled. Dependent on Scheduling work in the Software Integration group. • Co-scheduling POC continued to PY5. Also dependent on Scheduling work in the Software Integration group. • User survey rank 3.1 not 4.0 but about the same as last year.

  5. UFP (2) • Allocations Process and Allocations Management (UFP.AP) • POPS-TGUP integration being reconsidered for PY5; may be canceled. Currently included in PY5 Resource Authorization and Management (UFP.RAAM) plans. • POPS improvements continued to PY5. Also included in PY5 UFP.RAAM plans.

  6. UFP (3) • RP Integration and Information Sharing (UFP.IIS) • TGCDB failover production deployment delayed by HW acquisition; to complete early PY5. No impact on other planned PY5 activities. • TGCDB updates continued to PY5. No impact on other planned PY5 activities. • Storage usage record being reconsidered for PY5; may be canceled. No dependencies. Considered to be an optional activity that will depend on priorities and resource availability. • RDR prototype and production deployment will complete in early PY5. No impact on other planned PY5 activities. • Multi-audience TGCDB and POPS reporting implementation in TGUP delayed by LifeRay implementation; continued to PY5. No impact on other planned PY5 activities

  7. UFP (4) • User Information Presentation (UFP.IIP) • Liferay pushed back due to change from WebSphere. Will be complete in early PY5. • Analysis of Knowledgebase success to be completed in early PY5. Results may guide metrics and reporting changes. Otherwise, no impact on other planned PY5 activities. • Post-migration alignment of portal and web site look and feel delayed by LifeRay implementation; continue to PY5. • Integration of third-party SW and CTSS into MDS-based catalog partially done; complete in PY5. • Development of scalable documentation model delayed by LifeRay implementation; continue to PY5. No impact on other planned PY5 activities. • Migration to RDR/MDS as source of Resource Catalog info continued to PY5. Will proceed in parallel with other planned RDR work. • Enhancement of TGUP with expanded resource information continued to PY5. Part of 6 above.

  8. NOS • Networking (NOS.N) • The Instrumentation activity was significantly negatively impacted with the departure of staff assigned to that activity and the inability to hire new staff due to the short horizon of this award. Pending availability of existing NCSA staff with appropriate expertise, we are hopeful this activity will resume in PY5. • Security • The Risk Assessment activity was delayed and pushed into the first half of PY5.

  9. DV (1) • Distributed Data Management (DV.DWG, DV.DPI, DV.GFS, DV.DDM) • While progress was made on the Data Architecture document, completion is delayed into PY5, and implementation of recommendation is expected to be accomplished during PY5.

  10. DV (2) • Maintaining Data Collections (DV.DataColl) • It was recognized mid-year that the Data Collections activity did not make adequate progress on its goal to implement an infrastructure to address cataloguing of data collections. This resulted in a decision to transition leadership of this activity to Indiana University who is rescoping the effort.

  11. SI (1) • Advanced Scheduling Capabilities (SI.Skd, SI.QBETS, SI.SPRC, SI.ARS, SI.ARCS) • On-demand compute capability documented and integrated into production operations on RP systems - On-demand capability has already been implement by a number of RPs, documentation and awareness is still needed for this implementation. This will be completed by Dec 09. This will not impact PY5 tasks. • Cost policies for reservations, application hosting, and on-demand compute capabilities drafted and proposed to TeraGrid Forum – The TG forum needs to agree that we do not need a cost policy and then this will be closed. • Queue prediction capability documented and integrated into TeraGrid's production operations – This needs to be moved to PY5. Not expected to impact PY5 deliverables.

  12. SI (2) • Capability Development and Expansion (SI.Host, SI.PBT, SI.CSDI) • Application Hosting Service Description & Implementation Documents – This has a small amount of description documentation updates still required. Due to the small amount of work it will not impact PY5 deliverables. • Coordinate Inca, IS Schema for Hosting Service – Removed TGCDB, RP Software Package Changes and Deployment for Hosting Service Expecting new scope to require 3 weeks of effort 8/3. This has an October end date so it was not expected to end at the end of PY4. It is on target for October 2009.

  13. SI (3) • Information Services Enhancements (SI.IS) • Information services meta-data in IIS – This has a September end date so it was not expected to end at the end of PY4. It is on target. • Data about RP HPC software availability is present in TG IIS and used by docs and/or TG user portal by 2/28/2009. This is now targeted for 12/31/2009.

  14. SGW (1) • Gateway Operations (SGW.Coord, SGW.GDoc) • Urgent computing for gateways will be pursued during the TG Extension after the capability is developed by the Scheduling WG. Currently, no RP supports on-demand computing. • Targeted effort to standardize treatment of community accounts funded at NICS in PY5. • Gateways User Count (SGW.UCnt) • Extension of TGCDB to store attributes that will facilitate production of detailed usage reports will be completed in PY5.

  15. SGW (2) • Gateways General Services Discovery (SGW.Svcs , SGW.LEAD) • Visualization pipeline canceled due to staff departure. • Reusable SimpleGird Modules - Not tested by 5 gateways, but modules put to many other uses. • 5 gateways develop resource reservation policies and components - Canceled due to major reduction in sites supporting advanced reservations in PY5. • SimpleGrid portal and tutorial server have been deployed on TeraGrid gateway cluster for two gateway developers and new gateway tutorials (TeraGrid'09 and SciDAC'09We will release the online learning service in mid-PY05 for targeted evaluation. • Continuing SimpleGrid work is funded for PY5.

  16. EOT • Evaluation • The piloting effort required further refinements to the instruments. This was based on feedback from the pilot effort that led to changes to the instruments themselves. As of the end of PY4 all of the RPs will have adopted the instruments. • The evaluator will provide the first cumulative summary by December.

More Related