Search results

| '''User Documentation''' | '''Technical Documentation'''

...ponsible= WLCG Network Throughput Team (T0/T1, R&E and experiments network contacts). This unit works in collaboration with GEANT's EDUPERT and GlobalNOC PET. |documentation= https://twiki.cern.ch/twiki/bin/view/LCG/NetworkTransferMetrics#Network_Pe

[[Category:Operations Documentation]] ...e consultancy services to VO managers, clarifying procedures and gathering documentation aiming to optimize the VO managers daily work.

* UMD Release Team meeting: contribution and preparation of the agenda * organization of the DRIHM collaboration (user contacts, testbed and infrastructure providers)

...nd contribution to last EMI EMT meeting about the start of the UMD Release Team as continuation of the EMI EMT meeting * main activity has been the face to face meeting of the EGI CSIRT team in Linkoping, Sweden (24-25 April 2013)

...nt of VO views in accounting portal and discussion of issues with the APEL team * Initial contacts with South African Observatory on establishing a Registration Authority on

...AQ]]''' / '''<span class="plainlinks">[https://ggus.eu/pages/docu.php GGUS Documentation]</span>''' / '''<span class="plainlinks">[https://ggus.eu/ GGUS Helpdesk]</ ...r example, OSG Topology Interface has the following record for GGUS: "GGUS Contacts Reader" /C=DE/O=GermanGrid/OU=FZK/CN=prod-ars.ggus.eu

= Initial activities - Joining UMD Release Team<br> = To be included in [https://wiki.egi.eu/wiki/URT UMD Release Team (URT)] the interested Technology Provider should provide following informat

== Documentation == ...was focused on four areas: EGI wiki, procedures, EGI discussion forum and documentation creation.

...ntacts. It is also done via operational channels (weekly contacts, mailing contacts) since operational staff at sites represent the infrastructure / middleware ...the Ibergrid context via weekly operations meetings and operation mailing contacts. Requirements to EMI 1.0 and 2.0 were already collected using these mechani

EGEE Operational Security Coordination Team security alert Security Coordination Team (OSCT) have been made aware of a security

...ation (17.09.2013) on '''TBD '''(XSEDE): get the XSEDE Operations Security team to add the identified CAs to the XSEDE accepted CAs list === Documentation ===

On May 2017, the Globus team at the University of Chicago announced that they will no longer support the Contacts from [https://wiki.egi.eu/wiki/UMD_products_ID_cards UMD product ID cards p

...tsGathering_Assessment = Collecting of requirements is done through direct contacts with user communities and through Grid users dissemination events and consu | US_HS_Consultancy_HowToImprove = Further development of documentation available at www.grid.bas.bg.

* assessment of FedCloud and next steps to improve its operational status and documentation ***Gergely contacts passed from EBI meeting, following up (includes Elixir contacts

* Follow up with sites with missing security contacts Internal reports to the GARR Team about Prage's TF 2012. Planning of next steps and allocation of further res

* TF-NOC meeting and contacts established with GEANT operations and EduPERT * Monthly team meeting was held on Thursday 13th Dec.

* '''Training''': Many NGIs provide their own training team and facilities for users. These NGI teams provide courses at various levels ...on as new technologies and procedures become available, or gaps in current documentation is found.

...tsGathering_Assessment = Collecting of requirements is done through direct contacts with user communities and through Grid users training events. | US_HS_Training_Assessment = NGI training team is organizing training events for Grid users and site administrators at the

* [http://fts3-service.web.cern.ch/documentation/releases#quicktabs-release=2 FTS3 - 3.2.26] ...ducts are still correct and send me email if you need to add / remove some contacts (SSO account mandatory): ([https://www.egi.eu/earlyAdopters/table full site

| Starting team to investigate accounting of failed jobs As part of the WLCG Ops Co-ordination team, Alessandra Forti co-chairs the Multicore Task Force.

...(Unplanned, Planned, Queued, Released); when Queued, it means that the UMD team has included the product in the corresponding RT queue, and is working on i *'''Contacts''' for technical discussions; this can be different from the responsible, n

...details/templates will need modification. Suggested a maintained software contacts list for EGI, not just for SVG, which I can help maintain. * Planning for monthly CSIRT team meeting

* [http://fts3-service.web.cern.ch/documentation/releases#quicktabs-release=2 FTS3 - 3.2.26] ...ducts are still correct and send me email if you need to add / remove some contacts (SSO account mandatory): ([https://www.egi.eu/earlyAdopters/table full site

...ce endpoint level, it will be used the site contact. '''Please review your contacts'''. * '''The DPM team has agreed to extend support for security updates for the DPM legacy functi

...ce endpoint level, it will be used the site contact. '''Please review your contacts'''. * '''The DPM team has agreed to extend support for security updates for the DPM legacy functi

...ilman.egi.eu, dirac@mailman.egi.eu, dirac-admins@mailman.egi.eu (operation team) | '''Documentation'''

| Globus support is provided by the EGCF product team through the EGI Helpdesk with base level of service support | '''Documentation'''<br>

...are expected anymore since 8.8 is more than six months old already. CREAM team may be able to respond in case of actual emergency (required changes could ...ce endpoint level, it will be used the site contact. '''Please review your contacts'''.

...nd accounting level [[Desktop Grids integration|read more]]. The remaining documentation, training, and support related integration to be continued until the start Main objectives of the proposed Virtual Team:

Contacts with all the NGIs and integrated Resource Infrastructure Providers were suc ...essfully established during PQ1. SVG counts 15 members and has established contacts with the software developers of the main deployed middleware stacks. SVG, j

...ce endpoint level, it will be used the site contact. '''Please review your contacts'''. ...ne, [https://gitlab.cern.ch/lcgdm/dmlite/blob/master/doc/dome/dome.pdf see documentation])

...ce endpoint level, it will be used the site contact. '''Please review your contacts'''. ...ne, [https://gitlab.cern.ch/lcgdm/dmlite/blob/master/doc/dome/dome.pdf see documentation])

...ce endpoint level, it will be used the site contact. '''Please review your contacts'''. ...ne, [https://gitlab.cern.ch/lcgdm/dmlite/blob/master/doc/dome/dome.pdf see documentation])

The Site Security Contact and the team members will be informed of and agree to * test site and especially security contacts

...optional, avoiding failures if no OCCI endpoint is configured; updates on documentation, now stored on a dedicated EGI Foundation github store ** '''found dependency problem with cloudkeeper-os''' (UMD team on it) https://ggus.eu/index.php?mode=ticket_info&ticket_id=135539

*'''Contacts''' for technical discussions ...nd configuration guide'' must be provided by the TP, that the verification team can use to create the verification procedure

* Regional security contacts have been actively involved in the security service challenge 5 both suppor ...ration problems are discussed in the regular coordination meeting. The ROD team works well. Grid services are maintained up-to-date.

=== Patches, Bug Fixes and Documentation Changes === * Updates to Install documentation and GitHub related files ([https://github.com/GOCDB/gocdb/pull/210 #210], [

...optional, avoiding failures if no OCCI endpoint is configured; updates on documentation, now stored on a dedicated EGI Foundation github store ** '''found dependency problem with cloudkeeper-os''' (UMD team on it) https://ggus.eu/index.php?mode=ticket_info&ticket_id=135539

== Tasks and contacts == ...ns’ feedback to increase the quality and relevance of the publications and documentation produced by task NA2.1.2.

...w and thus many changes had to be made. The developments are ready and the documentation will follow in the next couple of days. #. finalize the new version of the documentation (ready in a couple of days)

...ere started during the first year and are now structured to better reflect team activities and support the EGI strategy development. ...overnance, standardisation and integration with other infrastructures. The team also develops EGI’s strategic response and alignment to EU policy and EC

*The CERN data management team maintains a set of data management clients, including gfal2, gfal2-utils an ** the regular support scope (documentation, 3rd level incident handling, &c) extends to all communities and users that

...Study “Aerodynamic Study of Airflow around an Airfoil in the EGI Cloud” - (Team 194 - http://www.theubercloud.com/wp-content/uploads/2016/12/UberCloud-Comp ***9 total (3 new; 6 backlogging of current contacts)