/* * ############################################################## * ## ## * ## CIC OPERATIONS PORTAL ## * ## Communication Interface for Central Operations ## * ## ## * ############################################################## * * developped at IN2P3-CNRS Computing Centre, Lyon, France * http://cc.in2p3.fr * * cic-information@in2p3.fr * * -------------------------------------------------------------- * File & version: $Id: CICPortal_release_note_V-4.7.txt,v 1.2 2007/12/12 13:47:36 oaidel Exp $ * Author : Gilles Mathieu (gilles.mathieu@in2p3.fr) * * Description: * This is the release note of CIC Operations Portal v-4.7 * * * * -------------------------------------------------------------- */ ################################### Overview ################################### The CIC Operations Portal is online at URL http://cic.gridops.org This portal has been created as a part of the SA1 activity. It is dedicated to ensure: # to be a management and operations tool # to be an entry point for all Egee actors for their operational needs # to manage the available informations about EGEE VOs and related VOs # to monitor and ensure grid day-to-day operations on grid resources and services Each actor of Egee will then be able to enter or have access to informations from an operational point of view according to its role into Egee - what we define as an actor's view: # VO views : actions depending upon VO Managers and VO administrator # VO mb views : actions depending upon VO members responsabilities # RC views : actions depending upon RC responsabilities # and so on with COD, ROC and OAG Home section of the portal is public. Other sections are secured using certificates and SSL authentication. ################################### Main changes from v-4.6 ################################### Main changes are presented in 6 groups: 0- Background - technical changes 1- New features 2- Improvements of existing features 3- Bug fixes 4- Failover related work 5- integration and parallel work additionnaly, the exhaustive development list is published at the end of this document, giving for each development the following information: - purpose of the development - entity or person requesting this development - end of development date 0- Background - technical changes ################################### N/A 1- New features ################################### N/A 2- Improvements of existing features ################################### Notification system linked to the new scheduled Downtime procedure ------------------------------------------------------------------ - Improvement of the Broadcast target definition from the core level flag defined in the GOC db - Modification of notifications * Subject shorter and more pertinent * Body mail integrating the reason for which users are notified and the list of impacted core services. - Change on the RSS titles EGEE BROADCAST -------------- - Change in broadcast form layer - target added for Open Science Grid - Broadcasts available through RSS flows - Broadcast archives available, allowing to retrieve broadcasted info as well as related info (date, sender, targets) COD Dashboard ------------- - Integration of requests and suggestions made by COD staff in the last months (COD meetings, EGEE conference, handover, mails) - Layer completely reviewed - filters, sorting and customized displays based on user preferences - Integration of new features like CNAF's IRC chat, documentation page, gridmap - improved CIC/SAM/GGUS synchronization mechanism See the "development details" section for a list of all developments carried out on the dashboard 3- Bug fixes ################################### N/A 4- Failover related work ################################### N/A 5- integration and parallel work ################################### N/A ################################### Development details since last release ################################### ------- 11/2007 ------- + COD dashboard: Implement a transaction mechanism to update GGUS/SAM - asked by COD/GGUS/SAM + COD dashboard: Improve alarm update function on the dashboard, using new function provided by SAM - asked by CIC/SAM + COD dashboard: add a lead/backup filter on the GGUS tickets page, similar to the one available on alarms list - asked by Peter Kunszt + COD dashboard: Remove PPS alarms from COD alarms list - asked by PPS + COD dashboard: Try to reduce number of "clicks" needed to access to ticket creation when starting from an alarm - asked by COD best practices working group + COD dashboard: Send a mail when COD handover log has been filled, showing comments and reminding who's onn duty - asked by Cyril L'Orphelin + COD dashboard: Show sites and nodes in scheduled downtime or not registered in GOCDB from the alarms page - asked by COD best practices working group + COD dashboard: Allow to add more than one WIKI link in a ticket - asked by COD best practices working group ------- 12/2007 ------- + Broadcast Archive : implement a mechanism to retrieve broadcast - asked by all + COD dashboard: When creating a ticket for a master alarm, insert in the ticket body links to all masked failed tests - asked by Peter Kunszt + COD dashboard: Bug correction: if no alarm is associated to a ticket, the link to GOCDB in Tickets list doesn't work - asked by CIC + COD dashboard: Add in alarm details page all useful links to monitoring results, as it is for tickets - asked by Victor Edneral + COD dashboard: Add a page on the dashboard for IRC COD chat - asked by CNAF + COD dashboard: integrate ENOC/network results to the COD dashboard - asked by ENOC + COD dashboard: change mail template for 3rd escalation step - asked by Antonio Retico + schedule downtime procedure improvements: make our mechanism ready for Grid core services integration (GGUS-SAM-GOC-CIC) - asked by OCC/CIC/GOCDB + schedule downtime procedure improvements: implement notification messages granularity - asked by OCC/CIC/GOCDB ################################### About previous releases ################################### Please browse older release notes for information about previous releases: http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-4.6.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-4.5.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-4.4.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-4.3.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-4.2.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-4.0.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-3.2.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-3.1.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-3.0.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-2.5.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-2.4.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-2.3.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-2.2.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-2.0.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-1.3.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-1.0.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-0.5.txt http://cic.gridops.org/common/all/releaseNotes/CICPortal_release_note_V-0.4.txt ##### EOF #####