The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
GOCDB/Release4/Development/conditionalCertificationStatusRules
<< Back to GOCDB/Documentation_Index
<< Back to GOCDB/Release4/Development
Overview
The proposals outlined below are relevant to how SEs are monitored in GOCDB and support for hosting multiple projects within a single GOCDB instance.
Proposals
- 1) 'Site.scope' will be used to identify a site's Target Infrastructure (i.e. Grid/Project) rather than 'Site.Production_Status' value.
- 2) The 'SE.scope'will be used to identify an SE's target infrastructure.
- 3) The scope value will become multi-selection, allowing a site and service to be associated with more than one project.
- 4) The available options for the 'SE.Scope' value will be limited to the parent 'Site.Scope' values. This way, an SE can't define a scope that is not already defined by its parent site.
- 5) The 'Site.Production_Status' value is EGI specific and should be used to represent site's overall quality (Production, Test, PPS etc) and *not* to identify the Target Infrastructure.
- 6) Once we move the GIIS URL from site to SE, it will be possible to define a GIIS Url per target infrastructure using duplicate SEs defined under different scopes.
- 7) The present certification statuses will remain.
Comment (Tiziana): shall we reconsider the semantics of the Target Infrastructure, and use it to define the target production infrastructure a site (or better: an end-point) belongs to? Examples of Target infrastructures could be: EGI, EUDAT, PRACE, TEST. This would mean replacement of what today is "Production" into "EGI".
- Advantages. This would allow a single GOCDB site to host services that are part of different infrastructures.
- Disadvantages. This requires a reconsideration of scoping. Scoping was defined to be a on off (either in EGI or out of it). By having N target infrastructures, not part of EGI would mean being part of another Target Infrastructure).
The impact of this change in production would be small as usage of scoping is still limited in GOCDB.
Comment (DM): Yes I agree with your comments.