110 likes | 214 Views
ATLAS Hierarchical MDS Server. Patrick McGuigan. Introduction. Current state of information gathering Information can be: Node existence/configuration Installed software Services Methods Gridview Mailing lists / teleconferences grid-info-search on known hosts
E N D
ATLAS Hierarchical MDS Server Patrick McGuigan Atlas Testbed Workshop
Introduction • Current state of information gathering • Information can be: • Node existence/configuration • Installed software • Services • Methods • Gridview • Mailing lists / teleconferences • grid-info-search on known hosts • How do we evolve a strategy for the entire testbed? Atlas Testbed Workshop
Hierarchical GIIS for ATLAS • Moves testbed toward being a Virtual Organization (VO) • Provides mechanism for distributed information retrieval by querying well known resources • Allows users or agents to compare information about distributed resources. Atlas Testbed Workshop
GIIS 2 GIIS 1 GRIS IP Background GIIS 1 registers with GIIS 2 GIIS 1 is registrant GIIS 2 is registrar GRIS registers with GIIS 1 GRIS is registrant GIIS 1 is registrar Registration is an LDAP entry that has a specified time to live (TTL) Atlas Testbed Workshop
Background (cont.) GIIS 2 GIIS 4 GIIS 1 GIIS 3 GRIS IP An entity can register with multiple “parents” Atlas Testbed Workshop
ATLAS_TB ATLAS_TB Testbed GIIS Hierarchy Primary GIIS at UTA Alternate GIIS at ? ANL BNL BU Indiana LBL UMich OU UTA Site level GIIS’s Atlas Testbed Workshop
Testbed Site Policy Issues • Each testbed site registers one or more site-level GIIS • The name of a site-level GIIS should be based on domain name • Testbed sites are free to develop internal structure Atlas Testbed Workshop
Reliability Concerns • Dual registrations guard against single point of failure • Secondary GIIS is not a replica • Secondary and Primary GIIS’s may have different values for an entry during the entry’s TTL • Dual registrations a problem if Atlas GIIS reports to a parent Atlas Testbed Workshop
Security Issues • Security is not mature in GIIS backend • Performs anonymous binds to registrants when suffering a cache miss • Ignores binding rules when accepting registration messages • For now • Allow anonymous binds • Use filtering rule for accepting specific registrations Atlas Testbed Workshop
LDAP Configuration • Schema files control structure of entries in LDAP • Schema elements are required to be globally unique. • Becomes an issue if testbed members are interested in developing information providers and schema elements • A registrar should have the same schema files as all registrants. Atlas Testbed Workshop
Implementation Instructions http://www-hep.uta.edu/~mcguigan/atlas_giis Atlas Testbed Workshop