Difference between revisions of "GOCDB/Release4/Development/conditionalCertificationStatusRules"
(21 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} | |||
{{Template:GOCDB_menubar}} | |||
{{TOC_right}} | |||
[[Category:GOCDB]] | [[Category:GOCDB]] | ||
<< Back to [[GOCDB/Release4/Development]] <br/> | << Back to [[GOCDB/Release4/Development]] <br/> | ||
==Extend Scoping to Support Multiple Projects/Target Infrastructures== | |||
===Overview=== | ===Overview=== | ||
The scoping extensions outlined below are relevant to how SEs are monitored in GOCDB and support for hosting multiple projects within a single GOCDB instance. | |||
The | ===Extensions=== | ||
* | * Sites, Services, and NGIs will each be able to define multiple 'scope' tags to associate each with different project/infrastructure scopes. | ||
* | * 'Site.scope' will be used to identify a site's Target Infrastructure (i.e. Grid/Project) rather than 'Site.Production_Status' value. | ||
* 'Service.scope'will be used to identify an SE's target infrastructure. | |||
* The scope value will become multi-selection, allowing a site and service to be associated with more than one project. | |||
* The PI '&scope' parameter will allow a comma-separated list of scope values rather than a single scope value. | |||
<!--* 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.--> | |||
* The 'Site.Production_Status' value is EGI specific and should be used to represent site's overall quality (Production, Test etc) and *not* to identify the Target Infrastructure. | |||
* 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. | |||
* The present certification statuses will remain. | |||
<b><font color="red">Comment (Tiziana)</font></b>: 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. | |||
=== | <b><font color="red">Comment (DM)</font></b>: Yes I agree with your comments, proposals updated to reflect these. | ||
<br/> | |||
<br/> | |||
===Example=== | |||
<br/> | |||
[[File:ScopeCertStatusProdStatusRules.jpg|650px|x]] | |||
<br/> | |||
<br/> | |||
<br/> | |||
===Definitions=== | |||
<b>Site.Production_Status</b> | |||
* Values = Production|Test (<strike>PPS, SC</strike> obsolete) | |||
* EGI specific flag which is used as a mechanism to stop all of a site’s endpoints from being monitored. | |||
* The GOCDB ‘Site.Production_Status’ field is *currently* labelled in the portal as ‘Infrastructure.’ However, the Scope value should be used to identify the TargInfr as described above. We could consider deprecating the ‘Site.Production_Status’ field, but this field is currently used in EGI as a shortcut mechanism to indicate that all of a site’s services should be monitored or not. | |||
<br/> | |||
<b>Site.Scope</b> | |||
* Values = EGI|Test|EUDAT|... | |||
* Lists the names of any Grids or Projects to which the Site belongs (an open enum list). | |||
* For GOCDB, ‘Local’ means the site is not part of EGI or any other named Project/Grid. This is equivalent to the ‘AdminDomain.OtherInfo.GRID=INFO’ value in the EGI_GLUE2 profile (p16) which means the Grid is unknown and is present for information purposes. | |||
<br/> | |||
<b>Site.Certification_Status</b> | |||
* Values = Candidate(temporary, max of 2 months)|Uncertified|Certified(long-term state)|Suspended(temporary state, max of 4 months)|Closed(indefinite state) | |||
* EGI specific flag which is used to identify the site’s SA1 site certification status. | |||
* Only Certified sites services are monitored. | |||
<br/> | |||
<b>SE.Scope</b> | |||
* Values = EGI|Test|EUDAT|... | |||
* Allows a Site to define a mix of services for different projects. | |||
* An extra business rule is necessary: An SE can only select a Scope from its parent Site Scope list. | |||
* In the EGI_GLUE2 profile there is no corresponding ‘Service.OtherInfo.GRID’ attribute defined for Service (section 2.8). | |||
<br/> | |||
<b>SE.Production</b> | |||
* Values = True|False | |||
* Quality level/maturity level of the service - does the service deliver a production quality service (or not) to its Target Infrastructure/Project. | |||
* Maps to GLUE2 Service.QualityLevel = development|production|pre-production|testing (open enum) | |||
=== | <!-- | ||
===Notes=== | |||
A Site's 'Target Infrastructure' and 'Certification Status' settings are currently unrelated and do not affect each other; a site may change its Target Infrastructure independently of the Certification Status. For example, a site that delivers to the ‘Test’ target infrastructure could specify that it is ‘Certified’. This is questionable since a Certified site only really has a meaning to the 'Production' infrastrucutre. | |||
Since the Certification Status values only really apply to the EGI | This is questionable: Since the Certification Status values only really apply to the 'EGI' infrastructure/scope, we <b>could?</b> impose rules to limit the allowed values of the Certification Status depending on the Target Infrastructure/Scope as follows: | ||
* Sites that define the 'Test' target infrastructure can only specify a 'Candidate' Certification Status. | * Sites that define the 'Test' target infrastructure can only specify a 'Candidate' Certification Status. | ||
* Changing a Site's Target Infrastructure from 'Production' to 'Test' will cause the Site's Certification Status to be automatically relegated to ‘Candidate’. | * Changing a Site's Target Infrastructure from 'Production' to 'Test' will cause the Site's Certification Status to be automatically relegated to ‘Candidate’. | ||
Line 49: | Line 77: | ||
====Proposal 3==== | ====Proposal 3==== | ||
This | This is questionable: The Service Endpoints 'Production level' flag is a simple boolean which can be translated as ‘Does this SE provide a production level service (t/f) to the Site's target infrastructure?’ Therefore, we <b>could</b> impose the following rule as follows: | ||
* If the site’s target infrastructure is ‘Production,’ a child SE's Production flag can only be set to true if the site is ‘Certified’?: | * If the site’s target infrastructure is ‘Production,’ a child SE's Production flag can only be set to true if the site is ‘Certified’?: | ||
Line 82: | Line 110: | ||
Stephen | Stephen | ||
--> |
Latest revision as of 17:20, 5 August 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
GOC DB menu: | Home • | Documentation Index • |
<< Back to GOCDB/Release4/Development
Extend Scoping to Support Multiple Projects/Target Infrastructures
Overview
The scoping extensions outlined below are relevant to how SEs are monitored in GOCDB and support for hosting multiple projects within a single GOCDB instance.
Extensions
- Sites, Services, and NGIs will each be able to define multiple 'scope' tags to associate each with different project/infrastructure scopes.
- 'Site.scope' will be used to identify a site's Target Infrastructure (i.e. Grid/Project) rather than 'Site.Production_Status' value.
- 'Service.scope'will be used to identify an SE's target infrastructure.
- The scope value will become multi-selection, allowing a site and service to be associated with more than one project.
- The PI '&scope' parameter will allow a comma-separated list of scope values rather than a single scope value.
- The 'Site.Production_Status' value is EGI specific and should be used to represent site's overall quality (Production, Test etc) and *not* to identify the Target Infrastructure.
- 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.
- 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, proposals updated to reflect these.
Example
Definitions
Site.Production_Status
- Values = Production|Test (
PPS, SCobsolete) - EGI specific flag which is used as a mechanism to stop all of a site’s endpoints from being monitored.
- The GOCDB ‘Site.Production_Status’ field is *currently* labelled in the portal as ‘Infrastructure.’ However, the Scope value should be used to identify the TargInfr as described above. We could consider deprecating the ‘Site.Production_Status’ field, but this field is currently used in EGI as a shortcut mechanism to indicate that all of a site’s services should be monitored or not.
Site.Scope
- Values = EGI|Test|EUDAT|...
- Lists the names of any Grids or Projects to which the Site belongs (an open enum list).
- For GOCDB, ‘Local’ means the site is not part of EGI or any other named Project/Grid. This is equivalent to the ‘AdminDomain.OtherInfo.GRID=INFO’ value in the EGI_GLUE2 profile (p16) which means the Grid is unknown and is present for information purposes.
Site.Certification_Status
- Values = Candidate(temporary, max of 2 months)|Uncertified|Certified(long-term state)|Suspended(temporary state, max of 4 months)|Closed(indefinite state)
- EGI specific flag which is used to identify the site’s SA1 site certification status.
- Only Certified sites services are monitored.
SE.Scope
- Values = EGI|Test|EUDAT|...
- Allows a Site to define a mix of services for different projects.
- An extra business rule is necessary: An SE can only select a Scope from its parent Site Scope list.
- In the EGI_GLUE2 profile there is no corresponding ‘Service.OtherInfo.GRID’ attribute defined for Service (section 2.8).
SE.Production
- Values = True|False
- Quality level/maturity level of the service - does the service deliver a production quality service (or not) to its Target Infrastructure/Project.
- Maps to GLUE2 Service.QualityLevel = development|production|pre-production|testing (open enum)