[gin-auth] Re: Create a VO for MultiGrid team ?

Oxana Smirnova oxana.smirnova at hep.lu.se
Thu Mar 2 15:57:37 CST 2006


Hi,

I'm sorry, but what if soon somebody else will create a VO called GIN? How can we tell one from anther? Maybe such a VO already exists and we are going to infringe on somebody's rights?

What I mean, please let's call it GRID.GIN, or GGF.GIN, or at least (worse is only simply GIN) GIN.GGF.ORG, before we all agree on globally unique VO names. Oscar, you should know better than anybody else about the "FUSION" VO name clash couple of weeks ago.

Cheers,
Oxana

Oscar Koeroo пишет:
> Hi Dane,
> 
> I will create a new VO called "GIN" in the morning (Central European 
> Time) which means a new VOMS Admin instance and a new VOMS daemon (AC 
> provider).
> It will have the grid-mapfile interface limited to everybody who can 
> present a user/hostcertificate signed by a CA within the IGTF (standard 
> policy but I can be more flexibel for the GIN VO).
> 
> I'll email to this list about the coordinates of the VOMS server.
> 
> 
>    Oscar
> 
> 
> Dane Skow wrote:
> 
>>
>> Thanks for the ping Erwin. I'm sorry for the slow response. Yes, I  
>> think we should take you up on the offer. I've done a quick survey of  
>> those who mentioned interest in running a VOMS and the other options  
>> would have greater startup delays and effort. I like the "GIN" name.   
>> Oscar can you let us know when this is setup and how to register  
>> people's certificates ? Once we have this ready, we should announce  
>> it to the full GIN at ggf.org list since the other groups will likely  
>> want to start registering too.
>>
>> To be clear, we want both VOMS functions (right?):  to be able to  
>> generate a list of DNs (for constructing a gridmapfile snippet) and  
>> the ability to generate VOMS authorization attributes so people can  
>> use whichever
>> combination they need to get started. I think we'll likely have a mix  
>> of gridmapfiles and authorization service calls for a while yet.
>>
>> Dane
>>
>> On Mar 2, 2006, at 2:42 AM, Erwin Laure wrote:
>>
>>> Hi Dane,
>>>
>>> Was there already a decision which VOMS server to use? I haven't  
>>> heard anything so I assume it will be the NIKHEF one.
>>>
>>> Cheers,
>>>
>>> -- Erwin
>>>
>>> Erwin Laure wrote:
>>>
>>>> Hi Dane et al.,
>>>> This is a very good plan.
>>>> EGEE could offer our existing VOMS service that runs in NIKHEF  
>>>> (Oscar Koeroo, cc'ed, is the responsible for the system) and  
>>>> already serves a number EGEE pre-production VOs.
>>>> I'd suggest we call the VO "gin" ;-)
>>>> Cheers,
>>>> -- Erwin
>>>> Dane Skow wrote:
>>>>
>>>>>
>>>>> First copy of this didn't get through due to list problem.  
>>>>> Hopefully  fixed now.
>>>>> D
>>>>>
>>>>> On Feb 23, 2006, at 11:23 AM, Dane Skow wrote:
>>>>>
>>>>>>
>>>>>> Oxana brought up the excellent suggestion that we should  quickly  
>>>>>> create a VOMS service for persons working on bringing  up the  
>>>>>> MultiGrid interoperation. Since we need to identify a  manageable  
>>>>>> set of DNs for early adopters to enable and clearly  identify 
>>>>>> them  (and they will be involved in different groups),  and we're  
>>>>>> consolidating on the VOMS authorization info for now,  this seems  
>>>>>> like a good bootstrap idea. Rhys from APAC has  offered to setup  
>>>>>> such a VOMS service but is checking on the  timescale that could 
>>>>>> be  done. Is there someone else ready and  eager to setup a VOMS  
>>>>>> instance so we can get started with  identifying people working 
>>>>>> on  GIN ?
>>>>>>
>>>>>> Another thing I've started is a matrix of CA usage by the  
>>>>>> various  grids (updated by David Groep and Yoshio Tanaka -  
>>>>>> thanks). I've  discovered this list is rather larger than I  
>>>>>> expected and that it's  changing quickly as people move forward  
>>>>>> on interoperation, but I  think there may be value in creating a  
>>>>>> snapshot of what our grids  use now. It may not be worth the  
>>>>>> effort to try to keep a current  master list, but we can see.   
>>>>>> I'll keep a current copy at http:// www.mcs.anl.gov/~skow/GIN/ 
>>>>>> GIN-CAs.xls if folks send me their  updates (at least til we get  
>>>>>> a full coverage).
>>>>>>
>>>>>> Cheers,
>>>>>> Dane
>>>>>
>>>>>
>>>>>
>>>>>
>>>
> 





More information about the gin-auth mailing list