Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Search results

Jump to navigation Jump to search

  • EGI-Engage:WP6 Caffe
    | '''User Documentation''' | '''Technical Documentation'''
    1 KB (156 words) - 16:53, 27 November 2015
  • GGUS:WLCG Network Throughput
    ...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
    1 KB (216 words) - 13:30, 26 January 2022
  • VO Services
    [[Category:Operations Documentation]] ...e consultancy services to VO managers, clarifying procedures and gathering documentation aiming to optimize the VO managers daily work.
    7 KB (1,108 words) - 11:41, 23 November 2012
  • EGI-InSPIRE:Sa1 2013-05-28
    * UMD Release Team meeting: contribution and preparation of the agenda * organization of the DRIHM collaboration (user contacts, testbed and infrastructure providers)
    5 KB (705 words) - 18:25, 6 January 2015
  • EGI-InSPIRE:Sa1 2013-04-30
    ...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)
    4 KB (518 words) - 18:24, 6 January 2015
  • EGI-InSPIRE:Sa1 2013-01-29
    ...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
    3 KB (474 words) - 18:20, 6 January 2015
  • GGUS:OSG Topology Interface FAQ
    ...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
    3 KB (417 words) - 13:50, 28 March 2019
  • EGI Software Component Delivery
    = 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
    7 KB (984 words) - 11:48, 19 February 2019
  • EGI-InSPIRE:SA1.8-QR11
    == Documentation == ...was focused on four areas: EGI wiki, procedures, EGI discussion forum and documentation creation.
    7 KB (1,032 words) - 19:15, 6 January 2015
  • NGI International Task Review MS109 Portugal
    ...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
    10 KB (1,572 words) - 18:55, 19 December 2012
  • EGI CSIRT:Alerts/openpbs-23-10-2006
    EGEE Operational Security Coordination Team security alert Security Coordination Team (OSCT) have been made aware of a security
    7 KB (993 words) - 13:20, 21 June 2010
  • EGI-XSEDE:Collaboration
    ...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 ===
    9 KB (1,334 words) - 14:38, 2 June 2014
  • GT-EOS:Globus-Toolkit EOS
    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
    6 KB (939 words) - 16:31, 30 November 2017
  • NGI International Task Review MS109 Bulgaria
    ...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.
    5 KB (692 words) - 18:36, 19 December 2012
  • EGI-Engage:AMB-2016-02-24
    * assessment of FedCloud and next steps to improve its operational status and documentation ***Gergely contacts passed from EBI meeting, following up (includes Elixir contacts
    7 KB (892 words) - 16:20, 4 March 2016
  • EGI-InSPIRE:Sa1 2012-09-25
    * 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
    5 KB (764 words) - 17:45, 6 January 2015
  • EGI-InSPIRE:Sa1 2012-12-18
    * TF-NOC meeting and contacts established with GEANT operations and EduPERT * Monthly team meeting was held on Thursday 13th Dec.
    7 KB (1,005 words) - 18:19, 6 January 2015
  • EGI-InSPIRE:TNA3.3 NGI User Support Teams
    * '''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.
    41 KB (5,314 words) - 18:06, 24 December 2014
  • NGI International Task Review MS109 Serbia
    ...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
    5 KB (741 words) - 18:55, 19 December 2012
  • Agenda-17-11-2014
    * [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
    9 KB (1,348 words) - 16:03, 18 November 2014

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Retrieved from "https://wiki.egi.eu/wiki/Special:Search"