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"
| Line 17: | Line 17: | ||
Thanks for your attention, | Thanks for your attention, | ||
GocDB team | GocDB team | ||
To send to sites: | |||
On 6th July GOCDB v5.4 will go live. One key database change relates to timezones. | |||
IMPORTANT: | |||
Your site has been identified as using a timezone string (typically based on a 3-letter TZ or starting 'Etc/') which we can't automatically convert to the new "Olsen Style" which are typically of the form ‘Continent/City’ or 'UTC'. The new timezone values are available for testing at: https://gocdb-test.esc.rl.ac.uk | |||
If possible, please can you update your site's timezone in the production GOCDB before the 6th July. If this is not currently possible in the production instance (because there is not a suitable timezone for your site that folllows the 'Continent/City' convention), then it is important that this is done as soon as possible after the update. | |||
Revision as of 17:14, 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 with any bugs/issues.
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.
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
To send to sites:
On 6th July GOCDB v5.4 will go live. One key database change relates to timezones.
IMPORTANT: Your site has been identified as using a timezone string (typically based on a 3-letter TZ or starting 'Etc/') which we can't automatically convert to the new "Olsen Style" which are typically of the form ‘Continent/City’ or 'UTC'. The new timezone values are available for testing at: https://gocdb-test.esc.rl.ac.uk If possible, please can you update your site's timezone in the production GOCDB before the 6th July. If this is not currently possible in the production instance (because there is not a suitable timezone for your site that folllows the 'Continent/City' convention), then it is important that this is done as soon as possible after the update.