SG-OSG Transition FAQ
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 does SGVO improve my life?
Organization and Membership Questions
Is OSG a single organization?
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.
Currently SURAgrid membership is determined by contributing resources. Is this the same?
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 (http://www.sura.org/programs/docs/SGMembershipOct07.pdf) 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.
Is there a SG-OSG roadmap?
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 this fit with the SURAgrid Starategic Plan?
- GOAL 1: will significantly expand our outreach potential.
- GOAL 5: Strengthen our partnership.
Will SURAgrid still have All-Hands Meetings of its own?
What is the SG Membership database?
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?
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.
Working Group Questions
How does the Access Management Working Group change?
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 OSG working groups exist?
What about the cert requirement?
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.
What certificates will SGVO use?
In order to access OSG resources, SG user would need to use an International Grid Trust Federation (IGTF http://www.igtf.net/) accredited certificate.
Does the OSG stack come with installed certs?
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?
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.
Can I use CILogin for my Certificate provider?
What happens to the BridgeCA in the context of SGVO?
How do I get a DOE certificate?
Can I still use may campus CA as part of the SURAgrid Bridge CA?
Service Provider Questions
Can I be a member of SGVO using the original simplified install SURAgrid stack?
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).
We can use OSG working groups to present, advocate, and help implement features desired.
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.
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 accounting/reporting required for the OSG VDT stack.
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.
Do I have to run a grid gateway?
Why do I have to run a resource monitor?
What happend to AIX support?
What is the role of a system admin?
Does my resource require an IGTF certificate for registration?
VO Operation Questions
How will services like the VO user database be operated an maintained?
Running an organization, real or virtual, requires a certain amount of technology infrastructure. With the advances in infrastructure service models brought about by cloud computing, it is easier than ever to maintain services as a community on virtual platforms and have them hosted at member sites. Maintaining these services and providing cycles to run them is a key contributions which members will make to the SURAgrid community.
Is VOMS the SGVO membership database?
Yes, in part. The reason for using the term "membership database" is because this is a more accurate description of the service SURAgrid will maintain. As with any organization, a list of members is crucial for effective operations. Knowing the members of your community allows you to identify participates and the roles they fill in your organization. This information can be used to grant access broadly to all members or restrict access to privileged operations based on their responsibilities. A membership database is a core component of any service organization and SURAgrid currently maintains membership in a veriety of places, both electronically in LDAP and in various static web lists. Our operations will improve as we improve the quality and capabilities of our membership database.
The OSG VO Membership Service (VOMS) provides information about a user to the service provider from which they are requesting compute cycles. This allows that site to know more about the user so that they can provide the services at the request about SURAgrid members. Running a VOMS server is the easiest way to package user information from our membership database so that other OSG sites can understand it. Running a VOMS server does not mean we have to use it's user interfaces. It can be used as an externally facing interface for the express purpose of exposing information to other OSG sites.
We can develop what ever user facing tools for our membership database that are practical and meet the operational needs of SURAgrid. In fact, it is reasonable to expect that other interfaces to our membership database would exist in the future. For example, Shibboleth could be used to add a SAML interface to allow communication with service providers in the InCommon Federation.
How do I register an application with SGVO?
How will I run an application on SGVO?
What is an application maintainer?
OSG runs single processor jobs, can I run MPI jobs?
In an era of clouds, do grids matter?
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.