SG-OSG Transition FAQ

From SURAgrid
Revision as of 16:00, 19 January 2011 by (Talk | contribs)

Jump to: navigation, search

Please add or answer questions below


What about the cert requirement?

A: At the heart of OSG, you choose to trust the OSG (the DOE?) certificate and with that CERT in your browser, you have access to services.

Currently SURAgrid membership is determined by contributing resources. Is this the same?

A: De facto, by being a supporter of SGVO – i.e. providing a resource that can be used by SGVO – SURAgrid membership is obtained. Perhaps SGC should review/adjust the SURAgrid Membership criteria ( and consider a shift of emphasis to value the effort in community participation and contribution.
NB: Alan Sill: Contribute resource and/or submit SG approved application.

Can I be a member of SGVO using the orginal simplified install SURAgrid stack?

A1: It is not an either/or state. Likely, a roadmap statement is wise approach. OSG stack is superset of SURAgrid (by design of SURAgrid requirements defined by SG stack providers). Further, the requirements can be met in several ways (e.g. OSG stack, SG stack, other).

A2: We can use OSG working groups to present, advocate, and help implement features desired.

How different?

A: SURAgrid has documented its sw stack requirements (basically a Web services GRAM, with option pre-WebServices GRAM, with gsi-ssh recommended) and we will engage our SURAgrid community to review and recommend the specific transition requirements.

A: If you are using the OSG stack currently, you are compatible enough for SURAgrid. If you are using the original SG stack, you are minimally compatible with OSG but would not be able register your resource for discovery services making it difficult to use. We believe the Globus compatibility is technically satisfied, but smooth operation warrants switching resources to the OSG stack.

Is OSG a single organization?

A: Actually, OSG has many VOs and each may have some individual requirements. While basically, OSG VDT stack is the basis of OSG, various VOs may vary.

Is OSG accounting/reporting required for the OSG VDT stack.

A: OSG stack has reporting tools, extra configuration options, gracia accounting tools… each of which adds functionality. We believe that SURAgrid stack can be enhanced by considering these reporting/accounting functions.

Is there a SG-OSG roadmap?

A: Yes and you can help define it further. Original Roadmap concept is outlined in the SURAgrid Strategic Plan, was described in the SG-OSG Statement of Shared Interest and has been further developed via working groups within SURAgrid. The road map is now being expanded via this transition document.

How does the Access Management Working Group change?

A: The AMWG will continue as a technical requirements forum that we think would work well within the OSG working groups; and the AMWG will also continue as a high-level in supporting the access management infrastructure used by SGVO.

What certificates will SGVO use?

A: In order to access OSG resources, SG user would need to use an International Grid Trust Federation (IGTF accredited certificate.

Does the OSG stack come with installed certs?

A: Actually, OSG stack comes without any certs, and you can install any certs that you wish. You make the choice. SGC recommends that the SGVO host certs are IGTF-accredited which will enable full accounting/reporting capabilities.

Is there someone looking into these technical details?

A: Yes. The SURAgrid Access Management Working Group, the SG-OSG Transition Group, and the SGC have been working these details over the last two years. You are welcome to join these technical working group discussions.

How does this fit with the SURAgrid Starategic Plan?

A: GOAL 1 – will significantly expand our outreach potential.
GOAl 5: Strengthen our partnership.

What is the SG Membership database?

A: OSG uses VOMs. Much like the SURAgrid LDAP server, VOMS provides a needed mechanism to manage the user base.

Does operating an OSG VO mean that SURAgrid is subordinate to OSG?

A: In OSG terminology, a Virtual Organization (VO) is an abstraction designed to facilitate resource sharing between sites. It is does not define how those organizations operate pursuant to their missions. There are many examples of independent, real-world organizations that leverage OSG conventions to facilitate resource sharing for example LIGO, LHC, and a number of universities.

In an era of clouds, do grids matter?

A: Clouds have greatly enhanced our ability to package services for consumption by a broad spectrum of users. Grid services are a vital component of this framework and provide a proven platform for adding large amounts of compute capacity to your applications. An important goal of the SGVO is to simplify access to these compute resources so they can enhance the performance of applications available to your campus community.

Open Questions:

Please contribute answers to the questions below, add your own questions if you don't see it listed or add comments on the Talk page if you wish to discuss options or provide details.

How will I run an application on SGVO?

Can I use CILogin for my Certificate provider?

What happens to the BridgeCA in the context of SGVO?

Will SURAgrid still have All-Hands Meetings of its own?

How do I get a DOE certificate?

My resource is behind a firewall, how do I do share it with SGVO?

Do I have to run a grid gateway?

Can I share storage with SGVO?

How do I register an application with SGVO?

What happend to AIX support?

What OSG working groups exist?

Why do I have to run a resource monitor?

How does SGVO improve my life?

What is an application maintainer?

What is the role of a system admin?

OSG runs single processor jobs, can I run MPI jobs?

Does my resource require an IGTF certificate for registration?

Can I still use may campus CA as part of the SURAgrid Bridge CA?

Personal tools