1. EGI Ops Tools Advisory Group (GOCDB)
27/02/2017

2. Overview Review/prioritse outstanding RT tickets
Move tickets into new GOC-DB queue:
0.5 FTE for dev until end of Engage (Aug 2017)
Core Operational Tasks
0.5 FTE for ops until Dec 2017
E-Infra12 Proposals
Requirements discussion

3. RT Review (Estimated Higher Priority)

4. Write API Extensions (11020 )
Requestor: WLCG, Scale of development: Major
Service: Update all Service fields (no Create/Delete)
Service Endpoint: Full CRUD API for all SE fields
Extends current Write API (currently only extension properties)
Same AAA mechanism
Site Admins register authorised cert DNs (Access Control List)
Service
Manual service creation / deletion
API to Update service attributes SE
Full CRUD

5. Verify Data Freshness Check (8240)
Requestor: EGI, Scale of dev: Intermediate
Add Verify Site Data button to Sites
On click, record the verification date
Check also applies to child service data
If the verification date exceeds a threshold (3mths ?), send reminder s to Site Admins
Other actions needed?
New PI method to list unverified sites with optional threshold query parameter
Add ‘Last Verified’ field to Site PI output/XML

6. RT Review (Estimated Medium Priority)

7. NGI Certification Status Rules (9084)
Requestor: EGI, Scale of dev: Major/Intermediate
Add new ‘NGI_CertificationStatus’ value linked to each NGI
Values: Certified, Candidate, Uncertified, Suspended, Closed
Only users with project level roles can edit
NGI level users can’t
Add transition rules similar to Site status transitions
Cascades to child site CertificationStatus:
If NGI is suspended, all child sites are suspended
Sites can only be Certified if parent NGI is also Certified
If NGI is Certified, Sites can have any CertStatus

8. RT Review (Low EGI priority - but happy to reprioritise if required by other communites)

9. Downtime Classification Changes (10845 ),
Requestor: WLCG, Scale of dev: Intermediate / Small
Request that Downtimes over a certain length be declared further in advance to be classified as SCHEDULED, e.g.
If(DT <= 7days) : declare +24hrs in advance
If(DT > 7days and DT <= 14days) : declare +10days in advance
If(DT > 14days and DT < 1month) : declare +1month in advance
If(DT > 1month) : Site will be suspended
Suggest new rules apply to all DTs
Adds complexity to apply different rules to different site or service type groupings
Details still under discussion

10. Requestor EUDAT, Size of dev: Major
Change Logging (9431)
Requestor EUDAT, Size of dev: Major
Log actions performed against a Site/Service/Endpoint
Records who, when and what
Note, already log site CertStatus transitions
Needs clarity
What ‘action granularity’ is needed ?
Provide PI method(s) to query an audit trail of actions?

11. Unique Constraint on Host Name and Service Type (10368)
Requestor: WLCG, Scale of dev: Low
Services with same Host Name and Service Type are not allowed across *different* sites
Services under the *same* site may specify the same Host Name and Service Type
Originally required for UNICORE services that have multiple URLs
Still used, e.g. load balancing example:
Request is to prevent all duplicate services with same HostName and Service Type – still needed?
Would need to investigate the extent that this is currently used

12. Setup email list for user profile and resource request approvers (10481)
Requestor: EGI
Setup list for user profile and resource request approvers
Register this in URP for notification about new requests
Needs clarity ?

13. RT Review (Other, Non-Controversial)
UI enhancements (11546 , ), EGI, Minor
Replace ‘NGI’ with ‘Operations Centre’
Replace ‘Site’ with ‘Resource Centre’
Layout and other improvements
Note, there would be no API changes - GUI only. I.e. the terminology in the API and GUI would diverge
Request to make Selected URL Params Case Insensitive (10422)
A number of minor UI enhancements to improve the user experience, see GitHub issue tracker:

14. Recently Closed Tickets
Role Abstractions (9429)
Improve User Friendliness of Edit Downtime View (8038)
Support federated auth such as X509, SAML (7493)
Integration with EGI-CheckIn service

15. Core Operational Tasks
Migrate to dual-stack infrastructure for IPv6
Virtualise GOCDB failover
OS upgrade to RHEL7

16. E-Infra12 Proposals Extend GOCDB’s role in the Info-Service space
“Dev activities for E-Infra12 should be related to pro-active maintenance, integration, refactoring. Completely new developments don’t fit with the call’s objectives”
Extend GOCDB’s role in the Info-Service space
Increasing interest by key EGI stakeholders to extend the role of GOCDB within the information-service space, e.g.
Write API
Single info service for ARGO (move away from BDII)
Envisage strategic developments to ensure GOCDB stays aligned with EGI and our key stakeholders

17. E-Infra12 Proposals
Replace the UI/interface logic with a modern and more-capable Web framework
A large amount of GOCDB code is boiler-plate for a proprietary MVC/REST framework
Originally proposed for Engage, but delayed due to roadmap reprioritisation
Fits well as an Infra12 refactoring task
A non-trivial development, almost certainly requiring existing GOCDB URLs to be changed

18. E-Infra12 Proposals DB migration scripts/procedures
GOCDB built on a DB abstraction layer (Doctrine ORM)
Could take advantage by developing procedures / scripts to migrate data between different RDBMS
Build service resilience through increased portability
Currently require Oracle + associated license fees
More attractive to other communities with a preference for open-source DB

19. Discussion Summary Smaller requested improvements all OK
EGI High priority
WriteAPI Extensions (11020)
Verify data freshness check (8240)
EGI Intermediate priority
NGI Certification Status Rules (9084)
Useful to have a quick way of changing CertStatus of all Sites belonging to an NGI.
Determine if following account portal requirement is related/needed:
EGI Lower priority but happy to reprioritize as needed e.g. DT changes for WLCG:
Downtime classification changes (10845)
If there are no requirements for complex DT rules based on different Site/SE groupings allowing the same rules to apply to all DTs in GOCDB, then this could be easily implemented. Pending - To agree with WLCG/EGI
Add unique constraint on HostName + ServiceType pair (10368 )
Not an EGI requirement, but check to see if still needed with WLCG
Change Logging (9431)
Determine if still an EUDAT requirement, likely more suitable as an E-Infra12 development
Smaller requested improvements all OK
E.g. Renaming in GUI, layout refinements (11217 , 11546)
E-Infra12 proposals
Replace UI with modern Web framework – OK seems like a good fit
EUDAT: Change logging
A possible requirement for Infra12, to investigate if requirement still exists
Indico: Requirements will probably relate to dynamic attributes and extending GOCDB in info-service space
To investigate
DB migration proposal does not currently seem a high priority for EGI
Actions
Roadmap update (
Provide summary at OMB
Discussion Summary