1 / 6

Proposal for generation of NGI A/R monthly reports

This proposal suggests two solutions for generating NGI A/R monthly reports, including a virtual site group and grouping all NGI services in one existing site.

matthew-schultz
Download Presentation

Proposal for generation of NGI A/R monthly reports

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposal for generation ofNGI A/R monthly reports T. Ferrari OMB 29/11/2011

  2. Current NGI A/R statistics • Only top-BDII • List of end-points to be tested manually maintained • some NGIs have distributed top-BDII instances • Information extracted from SAM PI • Script developed in-house (EGI.eu) based on profile “ROC” • Problem • “NGI” services distributed across multiple GOCDB sites • list of NGI services has to be manually maintained • Existing A/R computation and reporting framework cannot be used

  3. Tools • Extensions needed in the operations tools to have a complete A/R reporting structure • GOCDB • Implementation of “virtual site” group • ATP and POEM • Virtual site topology information consumed by ATP • NGI Profile in POEM • Operations portal A/R report generation

  4. Proposal 1/2 • Interim solution • For large NGIs with “NGI” services distributed multiple GOCDB sites • Create a NGI site NGI_<countrycode>_SERVICES hosting all NGI services • PROs • Mechanism can be adopted also for DNS load-balanced services (registration of alias, single physical instances can stay in the current GOCDB site) • NGI A/R information gathered with profile ROC_OPERATORS • No extensions in the tools needed • No service downtime to migrate end-points • CONs • A site-BDII needs to be deployed, failover configuration

  5. Proposal 2/2 • For small NGIs (one or few sites) • Group all NGI services in one existing site. This site will be used as NGI reference site in A/R computation • PROs • No additional site-BDII needed • An existing GOCDB site is used • CONs • ROC_OPERATORS includes CE and SE  NGI A/R availability will depend on CE and SE performance

  6. Discussion • Circulate comments via e-mail • Approval/rejection of proposal in December OMB

More Related