Resource Selection Service (ReSS) Phase - II

1
Resource Selection Service (ReSS)Phase - II

• Parag Mhashilkar
• Computing Division, Fermilab

2
My goals for this meeting

• Understand focus of the project
• Stakeholders / Sponsor
• Discuss Tasks and Priorities
• Metrics
• Duration

3
Phase II Project Highlights

• Major emphasis on supporting the ReSS
  infrastructure for the existing VOs
• Making ReSS compliant to FermiGrid operational
  model
• Working on improving the robustness and security
  of the service.
• Evolving ReSS based on changes in the OSG
  Information System

4
PossibleStakeholders Sponsors

• Sponsor(s)
• Computing Division ?
• OSG ?
• Any VO ?
• Stakeholders
• Open Science Grid (OSG)
• OSG VOs, including
• DZero VO
• Engagement VO
• DES VO
• Fermigrid
•  Responsible/Host
• Computing Division, Fermilab

5
Initial Task List (I)

• Tasks identified by the ReSS team that needs to
  be addressed
• Maintaining and supporting the infrastructure.
• Improving the troubleshooting test suite to
  detect installation/deployment problems
• Improving security features
• Supporting users to improve or bootstrap the
  integration of ReSS with their job management
  systems
• Extending ReSS services to support a High
  Availability deployment mode
• Fully transitioning operations to FermiGrid,
  introducing compliance of ReSS to the FermiGrid
  operational specifications

6
Initial Task List (II)

• Maintaining ReSS functionalities as the OSG IS
  evolved
• preparing for the deployment of Glue Schema v2
• Evolution of GIP for new foci
• ReSS team will be working with the users to
  understand
• New features
• Task Priorities

7
Potential Risks and Challenges

• CEMon
• Publication mechanism of choice for the OSG IS
  (BDII and ReSS) and is a critical component in
  OSG stack
• Seeking involvement of GIP group for CEMon
  support activities
• Collaboration with CEMon group so far has been
  successful. Can improve code management.
• Dependence on continued support for CEMon
• Future changes to ReSS based on OSG IS changes
• Uncertain timeline of GLUE Schema V2.
• Possibly complex changes to the basic CEMon OSG
  plug-in.

8
Operations

• ReSS has 3 components
• A site-deployed publishing service (CEMon)
• deployed via VDT and operated by sites.
• ReSS central services
• 2 machines at Fermilab
• OS and HW maintained by FermiGrid
• Operations require minimal effort and are
  maintained by the ReSS team and FermiGrid
• Monitoring tools and web pages.
• Set of cron jobs on a central machine.
• The tools require minimal operational effort and
  are maintained by the ReSS team.

9
Support and Maintenance

• Support
• ReSS is supported by the ReSS team.
• Users open tickets with the OSG Grid Operation
  Center (GOC).
• GOC generates tickets and forwards them
  toress-support_at_fnal.gov.
• Tickets are generally acknowledged the same day
  and are prioritized w/ OSG bodies (e.g ITB team,
  Troubleshooting team, etc.)
• Maintenance
• ReSS is an integration project based on Condor
  and CEMon.
• Condor components are maintained by the Condor
  Team at the University of Wisconsin, Madison.
• CEmon is maintained by gLite, INFN Bologna group.
  
• All other SW, including an OSG CEMon plug-in, is
  maintained by the ReSS team.

10
Documentation Project Home

• Project home for ReSS will continue to be as in
  phase - I
• https//twiki.grid.iu.edu/twiki/bin/view/ResourceS
  election
• All the previous documentation will continue to
  be available at the above page
• Documentation for phase II will also be
  available at the above page.

11
Conclusion

• Phase II of the project will continue the
  support for ReSS
• Some of tasks for future work have been
  identified
• Some questions still need answers
• Stakeholders / Sponsor
• Discuss Tasks with the users and set priorities
• Metrics
• Duration of the project