Download - VO Naming Proposal
INFSO-RI-508833
Enabling Grids for E-sciencE
www.eu-egee.org
VO Naming Proposal
Explanation (first) and Discussion (after first)
Oscar KoerooJRA3
To change: View -> Header and Footer 2
Enabling Grids for E-sciencE
INFSO-RI-508833
Index.voms
• Widely known VO name constraints• VO naming known Guidelines• New Global VO naming proposal• Discussion moment: Where do you want to go today?
To change: View -> Header and Footer 3
Enabling Grids for E-sciencE
INFSO-RI-508833
VO Name Information
• Allowed VO (and group/role name) characters:– [a-zA-Z0-9-_\.]– In English:
VO names can start with a number VO Names can be alphanumeric and contain the characters
minus/dash/hyphen, underscore and dot
• Info from: Vincenzo Ciaschini
To change: View -> Header and Footer 4
Enabling Grids for E-sciencE
INFSO-RI-508833
VO Name Information
• VO names *should* not have a limited length (including the group and role names)
– /United-Federation-Of-Planets_Starship.Enterprise.NGC1701
– /picard/whatistheexactamountofcharactersthatIcanputintothishugestringtobeusedforanormaltypeofgroupinthevonamedafterthecaptainoftheussenterprisefromthestartrekthenextgenerationseriesfromthenineteennightees
– /picard/whatistheexactaboutofcharactersthatIcanputintothishugestringtobeusedforanormaltypeofgroupinthevonamedafterthecaptainoftheussenterprisefromthestartrekthenextgenerationseriesfromthenineteennightees/Role=thisisanewrolespecificallycreatedtocrashasystemthatusesVOMSofcourseIhopethatmysoftwarewhichisLCMAPSprimarilywillholdoutofcourse
• An initiative of Steven Burke to test these things
To change: View -> Header and Footer 5
Enabling Grids for E-sciencE
INFSO-RI-508833
Known Guidelines – Naming a VO
• Decide on a name for the VO that it:– Corresponds to its identity
e.g. DTEAM for the Deployment Team VO
– Easy to remember and recognise Also for Resource Admins how are not affiliated to the VO themselves like
BIOMED for the Biomedical activity VO.
– Don’t risk on using names longer then 6 characters or use special characters which could be mistaken for a regular expression
Like DZERO for the D0 experiment VO
– Doesn’t clash with reserved service or file names in the Grid software distributions
– Give appropriate DNS host aliases and host certificates, when necessary
e.g the sixt-vo.cern.ch is the host alias of the VODB server of the SIXT VO
• Info from: Maria Dimou
To change: View -> Header and Footer 6
Enabling Grids for E-sciencE
INFSO-RI-508833
New Global VO naming proposal
• Problem:– No name (space) control– Name clashes are started to appear
ATLAS vs. USATLAS vs. Swiss Atlas vs. NorduGrid ATLAS uscms vs. cms Biomed vs. Bio Italy
• Solution:– A hierarchical, extensible VO name space is proposed
Info from: Oxana Smirnova
To change: View -> Header and Footer 7
Enabling Grids for E-sciencE
INFSO-RI-508833
New Global VO naming proposal
Overall rules:
• Character set is limited to alphanumeric without punctuation marks, case-insensitive
• A full VO name is constructed of:– level (domain) name fragments– separated by a period (dot)– in level ascending order
level 0 name leftmost, level 1 - next to the right, etc Like: <level0>[.level1][.level2]<.level3>
• Name fragment length is arbitrary, except for the level 0
To change: View -> Header and Footer 8
Enabling Grids for E-sciencE
INFSO-RI-508833
Proposed level 0
• Level 0: (top level) national, global/international– Consists of 241 domains
240 official two-letter country code one cross-country domain named "int“
– Each national level is controlled by the respective national Grid Forum or a similar body
– INT domain is controlled by the GGF/EGA
• Examples: SE.SWEGRID (Swedish VOs) RU.DUBNAGRID (Town Grid project) IT.ENEA (a cross-national VO) INT.CERN (International HEP lab)
To change: View -> Header and Footer 9
Enabling Grids for E-sciencE
INFSO-RI-508833
Proposed level 1
• Level 1: International regional level (optional)– INT domain may have several sub-domains, introduced
whenever necessity appears– Each such sub-domain is controlled by the respective
international Grid initiative, congress or another forum– This level is optional and can be omitted for global transnational
organizations, such as CERN– The level can contain VOs or area/infrastructure sub-levels
• Examples:– INT.BALTIC.BALTICGRID (a regional VO)– INT.CE.VOCE (a regional VO)– INT.EU.EGEE (EU infrastructure sub-level)
To change: View -> Header and Footer 10
Enabling Grids for E-sciencE
INFSO-RI-508833
Proposed level 2
• Level 2: Area or infrastructure level (optional)– If necessary, regional, national or international domains may
have area- or infrastructure-specific sub-domains, aiming at grouping VOs
– Each such sub-domain is controlled by the respective infrastructure project or area-specific initiative
• Examples:– CH.SWISSGRID.ATLAS (Swiss ATLAS Grid VO)– SE.SWEGRID.snic-003-04-59 (a national VO)– INT.EU.EGEE.DTEAM (EGEE VO)– INT.CERN.ATLAS (International HEP VO)
To change: View -> Header and Footer 11
Enabling Grids for E-sciencE
INFSO-RI-508833
Proposed level 3
• Level 3: Virtual Organization Level – This is the actual level controlled by VOs and having VO-specific
structure (not discussed here)– They can decide on a simple name here and should consider to
use the guidelines of naming a VO
To change: View -> Header and Footer 12
Enabling Grids for E-sciencE
INFSO-RI-508833
Proposal summary
• The complete VO name is thus composed from mandatory and optional components as:– <level0>[.level1][.level2]<.level3>
Here "<>" indicates a mandatory element, and "[]" - optional one.
• Valid VO names are:– NL.Astrop– EE.TTU– US.OSG.GROW– CH.SWISSGRID.ATLAS– INT.Dzero– INT.CERN.CMS– INT.NORDIC.ARC-COMMUNITY– INT.EU.EGEE.DTEAM
To change: View -> Header and Footer 13
Enabling Grids for E-sciencE
INFSO-RI-508833
Where do you want to go today?
A few options:
• 1.) We keep on hurdling with just the VO names– Pro: no change needed anywhere – Con: one can expect pitfalls down the road…
• 2.) Implement the VO naming proposal (with or without another string format)– Pro: Name space regulation, controlled by ‘others’– Cons: takes time to setup correctly– Cons: relocation problems when pinned to a level0 to level3 domain
• 3.) Something completely different?– DNS trickery
True DNS: picard.kuiken.nikhef.nl DNS-alike: picard|kuiken.nikhef.nl e-mail-alike: [email protected]
– Please fill in blank with your idea: ______