Alert.png 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.

Difference between revisions of "GOCDB/notifications"

From EGIWiki
Jump to navigation Jump to search
Line 5: Line 5:
== Proposed Changes ==
== Proposed Changes ==
Please contact [mailto:gocdb-admins@mailman.egi.eu gocdb-admins] if the changes listed below will have repercussions.  
Please contact [mailto:gocdb-admins@mailman.egi.eu gocdb-admins] if the changes listed below will have repercussions.  
These changes were proposed at the Jan OMB with no objections: https://indico.egi.eu/indico/conferenceDisplay.py?confId=2372 


Plan to deploy following updates on Tues 3rd March.  
Dear all,
An update to GocDB v5.4 is planned the morning of the 6th July [https://goc.egi.eu/portal/index.php?Page_Type=Downtime&id=18107 downtime in GocDB]. This version is available for testing at: https://gocdb-test.esc.rl.ac.uk and runs against a separate copy of the data which will quickly become stale when compared to production. All bugs/suggestions please send to gocdb-admins [at] mailman.egi.eu


=== UTF-8 Character Support ===
Important; the update will introduce new site time zone values where existing (legacy) lookup values will be replaced with standard ‘Olsen’ values following ‘Continent/City’ convention or UTC. For the majority of sites, existing time zone values can be copied over automatically. However, there are a number of sites (~92) which use legacy values that can’t be automatically carried over e.g. those starting ‘Etc/…’, ‘CET’, ‘GMT’.  Where possible, we will be contacting the site admins directly and notifying them of the need to update their site time zone either before or shortly after the update.
Allow UTF-8 characters for selected fields with rendering in the output of the relevant PI methods. This will allow chars such as àšëÂÒÚÿaúø (this is only a small selection) on the following fields:
* Human readable 'Description' fields for: Project, NGI, Site, Service, Service Group, Downtime, ServiceType, Scope.
* Certification status change 'Reason' field.
* User Forename and Surname (note, not Cert DN)  
* Extension Property values (Sites, Services, ServiceEndpoints, ServiceGroups).


=== get_user PI method updates ===
IMPORTANT:
* PI method: https://wiki.egi.eu/wiki/GOCDB/PI/get_user_method
* Can all sites check their site time zone is correct after the update.
* New elements: <PRIMARY_KEY> (PK of role's target entity), <SSOUSERNAME>
* This will affect the output of the ‘get_site’ PI method - the site <TIMEZONE> element will only show a valid Olsen value.
* Update values of <ENTITY_TYPE> element so that:
** 'group' value is separated into 'ngi' and 'project'
** All values then become: project, ngi, site, servicegroup


Sample changes highlighted below:
Thanks for your attention,
[[File:GetUserXmlUpdates.jpg|400px|thumb|center|sample PI output with updates]]
GocDB team


<!--
=== Login via EGI SSO Username/Password ===
=== Login via EGI SSO Username/Password ===
* Note, to login via EGI SSO, your account will need to be associated with a valid/recognissed certificate (GOCDB will request SAML attribute for the user’s DN to map to an existing Gocdb account)  
* Note, to login via EGI SSO, your account will need to be associated with a valid/recognissed certificate (GOCDB will request SAML attribute for the user’s DN to map to an existing Gocdb account)  
* Allows login from a browser without personal cert loaded in browser  
* Allows login from a browser without personal cert loaded in browser  
* Does not affect PI - x509 still required for protected methods (no SSO/SAML redirects)
* Does not affect PI - x509 still required for protected methods (no SSO/SAML redirects)
-->

Revision as of 17:05, 18 June 2015

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Tools menu: • Main page • Instructions for developers • AAI Proxy • Accounting Portal • Accounting Repository • AppDB • ARGO • GGUS • GOCDB
• Message brokers • Licenses • OTAGs • Operations Portal • Perun • EGI Collaboration tools • LToS • EGI Workload Manager



Proposed Changes

Please contact gocdb-admins if the changes listed below will have repercussions.

Dear all, An update to GocDB v5.4 is planned the morning of the 6th July downtime in GocDB. This version is available for testing at: https://gocdb-test.esc.rl.ac.uk and runs against a separate copy of the data which will quickly become stale when compared to production. All bugs/suggestions please send to gocdb-admins [at] mailman.egi.eu

Important; the update will introduce new site time zone values where existing (legacy) lookup values will be replaced with standard ‘Olsen’ values following ‘Continent/City’ convention or UTC. For the majority of sites, existing time zone values can be copied over automatically. However, there are a number of sites (~92) which use legacy values that can’t be automatically carried over e.g. those starting ‘Etc/…’, ‘CET’, ‘GMT’. Where possible, we will be contacting the site admins directly and notifying them of the need to update their site time zone either before or shortly after the update.

IMPORTANT:

  • Can all sites check their site time zone is correct after the update.
  • This will affect the output of the ‘get_site’ PI method - the site <TIMEZONE> element will only show a valid Olsen value.

Thanks for your attention, GocDB team


Retrieved from "https://wiki.egi.eu/w/index.php?title=GOCDB/notifications&oldid=80529"