Difference between revisions of "GOCDB/notifications"
Line 4: | Line 4: | ||
== Proposed Changes == | == Proposed Changes == | ||
Please contact [mailto:gocdb-admins@mailman.egi.eu gocdb-admins] | Please contact [mailto:gocdb-admins@mailman.egi.eu gocdb-admins] with any bugs/issues. | ||
Dear all, | 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. | 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. | ||
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; 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. |
Revision as of 17:06, 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