Search results

::O-E-1 GOCDB (Core Grid Services/Core Technical Grid Services/GOCDB) ::O-E-8 User requirements ()

...nts should go into staged rollout in order to be released. Ops tools info. COD issues. |dedicated meeting on "new GOCDB Features needed to integrate all new service-types"

* preparation of resource allocation requirements, allocation models and use cases from the user community * Preparation for the Evolving EGI workshop in relation to future requirements for global tasks in security

...I meeting on mw support schedules, EGI/WLCG/EMI meeting on WLCG repository requirements ...s were performed on August 30th from 8:00 to 14:00 (UTC). During that time GOCDB was set to read-only mode. The PI was available.

...HPC, etc.), interoperability with regional grids, feeding interoperability requirements into EGI ...Grids, e.g. of the accounting and monitoring infrastructure, gathering or requirements

EGI operations oversight (COD) === Requirements Gathering ===

|COD |COD F2F

* Security meeting (CSIRT/COD) for followup of progress of upgrading of unsupported software and definiti * Follow up with NGIs not deploying SAM instances compatible with the new GOCDB service types

...ace meeting: discussion of application of service management processes and requirements to various operations services. Status of these will be assessed at the beg * Start of PRACE testing activities of GOCDB

...3 NGIs deploying a national ARGUS instance to register that (emi.ARGUS) in GOCDB as part of the NGI service site/grouping ...TION 3. DEADLINE 17-06-2013 RODs to provide feedback about test eu.egi.MPI-GOCDB-Check

...rted in PQ5. The first step was reorganization of operational tools in the GOCDB: GOCDB failover implementation was postponed due to the GOCDB 4.1 development. The task is on the roadmap for Dec 2011 and 2012 (now depe

* GOCDB meeting to assess implications of service renaming and implementation plans ...icket=92484 Request for setting QCG tests an operations tests] was send to COD team

...st time the Operations Community was collectively involved in a structured requirements gathering process. ...Centres in their country or region, whereas the Central Operator on Duty (COD) is responsible for the global oversight over the whole EGI infrastructure.

...ties (VRCs) meet to review and agree on the prioritisation of the emerging requirements for their use of EGI resources on a regular basis. The VRC model encourages ...heir inclusion into UMD these components are verified against the original requirements to ensure that these have been met.

...ties (VRCs) meet to review and agree on the prioritisation of the emerging requirements for their use of EGI resources on a regular basis. The VRC model encourages ...heir inclusion into UMD these components are verified against the original requirements to ensure that these have been met.

...ite certification process. In addition a portal was built, that syncs with GOCDB and gives the ability to the NGI Managers to add and remove on demand uncer That was not really needed, depending on the requirements sometimes 2 meetings took place within 1 month, as the TF work has to go th

* Review and discuss the changes in GOCDB for the registration of NGI services in order to produce NGI Availability/R * Review and discuss GOCDB roles restructuring proposal

...erations, or because of new Resource Providers joining the infrastructure. COD was involved in training and dissemination activities, in follow-up of unde ...other things, many bug fixes, extended FQAN-based views and new graphics. GOCDB functionality was also significantly extended with the support of virtual s

...and of the definition and execution of processes for periodic gathering of requirements. ...ral (COD) level contribute to it, solving problems within their scope. The COD part of the function is a global task.

*'''COD''' - Central Operator on Duty *'''GOCDB''' - Grid Operations Center Database