GOC Service Update - Tuesday, September 28, 2010, 1400 UTC

The GOC will upgrade the following services beginning at Tuesday, September 28th, 2010 at 14:00 UTC. The GOC reserves four hours (14:00 - 18:00 UTC) in the unlikely event that unexpected problems are encountered.

OIM 2.25 (https://oim.grid.iu.edu)

ITB version is now available for testing at https://oim-itb.grid.iu.edu; we encourage users to test this service before the production release.

* Resource / Added tape_capacity field for under WLCG information [OIM-51]
* Fixed the http/https mingling issue for topology slideshow.

MyOSG 1.27 (https://myosg.grid.iu.edu)

ITB version is now available for testing at https://myosg-itb.grid.iu.edu; we encourage users to test this service before the production release.

* Removed long-depricated Gratia graph pages (wizardaccount, wizardsc, wizardce)
* Updated URLs for Resource Group/Gratia (SE/CE) pages with new graph URL.
* Added new field (tape_capacity) for Resource Group / Summary / WLCG information [OIM-51]

GOC Ticket 1.27 (https://ticket.grid.iu.edu)

ITB version is now available for testing at https://ticket-itb.grid.iu.edu; we encourage users to test this service before the production release.

* Added some verbiages to make it clear who will be able to see various security tickets
* Ress Form / Updated the assignment rule [GOCTICKET-26]
* Navigator / Downgraded to DataTables 1.6 from 1.7 (which was causing keyboard focus issue)
* Navigator / Added Submitter field pulled from metadata
* Added submitter metadata to be used to show ticket submitter [GOCTICKET-71] [GOCTICKET-74]
Ticket Synchronizer 1.13
* Added metadata information indicating ticket submitter (so that GOC Ticket can display this information) [GOCTICKET-71] [GOCTICKET-74]

CEMon/BDII - *ITB Only* (http://is-itb.grid.iu.edu)

We will be upgrading our ITB instances to the latest version of BDII version 5.7.1. This upgrade will *not* be applied to our production.

* Install-Capacitor filtering script / Bug fixes, and adjusted HEPSPEC values


In addition to this, all machines will receive any routine operating system updates, which may result in the need to reboot the machine.