1 / 6

GOCDB + EGI Marketplace

The GOCDB is a configuration management database (CMDB) that provides semi-static site and SE information. It is not a user-facing SE marketplace, but rather serves as a role model for EGI/NGI managers, site administrators, and CSIRT. It defines business rules for site certification, state flags, and project scopes. The GOCDB interfaces include a portal and REST API for querying information.

roslyn
Download Presentation

GOCDB + EGI Marketplace

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. GOCDB + EGI Marketplace david.meredith@stfc.ac.uk STFC Daresbury Labs

  2. GOCDB Overview • Configuration Management DB: • CMDB: Semi-Static Site/SE info • Not a user-facing SE marketplace • Audience (SPs/Technical): • EGI/NGI Managers, Site Administrators, CSIRT • Internal Role Model: • Proj/NGI/Site self-mange memberships + roles • Defines Business Rules: • Site Certification, State Flags (Production/Test), Project Scopes (‘EGI’, ‘Local’, ‘ProjectX’) • Interfaces: • Portal + REST API to query info Roles Roles DataModel = Glue2ish subset

  3. https://goc.egi.eu/ https://creg.eudat.eu/

  4. GOCDB’s Role • GOCDB’s role is an underlying Service registry (e.g. Sci-gateways, PaaS/SaaS cloud service descriptions) • Overlying marketplace can then query for ‘in-scope’ Service Descriptions (SD) for display in storefront • Exclude ‘out of scope’ operational services • Aim to keep Service Descriptions DRY[1]: • Multiple registries, but input/register a Service’s Description ideally in one place • Reduce SD duplication and inconsistencies • ‘Content-Enrich’ in other tools when appropriate [1] Don’t Repeat Yourself

  5. What additional SD attributes are needed to support overlying marketplace? Proposed to GlueWG Service Endpoint SE defines 3 canonical PricingPolicy templates (small, medium, large) Small • Review related vocabulary/attributes (FitSM, USDL, …) • Register Business Parameters alongside Sites/Services • Pricing Schemes, SLA Templates • Subclass ‘glue2:Policy’ (abstract) => PricingPolicy + SLAPolicy canonical templates supported by EGI. • Link multiple Policy instances to a Service (e.g. SLA Gold, Silver, Bronze; Price per VO; Price/Scale: small, med, large) • Replace current pilot ‘P4U_*’ (Pay4Use) extension params

  6. Must Clearly Define Roles of Tools + Interactions Marketplace(s) IN: User tools, VApps, VMIs e-Grant Dynamic SE Info AppDB Pricing templates 3) Merge Static + Dynamic 4) Negotiate Customise Price/SLA template per customer SE Pricing templates Static Site + SE Info 2) Dynamic SE Info- from each SiteBDII TopBDII 1) Static Site + SE Info - Certified, Production, SiteBDII URL SiteBDII (No Caching) GOCDB IN: NGIs, Sites, Static SE Info, Pricing IN: Dynamic SE Info (resource publish)

More Related