Search results

...s on reaching members of the EGI community (see point below). Reaching non-EGI audiences is outside of the VT, and should be done by IGTF separately, but ...n the VT, because he is the leader of the dissemination activity in IDGF. (Action - Robert) Tamas Kiss is responsible for reaching scientific users for IDGF.

{{EGI-Inspire_menubar}} |'''Time before submission'''|| '''Person'''|| '''Action''' || '''RT Action'''

* [https://documents.egi.eu/secure/RetrieveFile?docid=203&version=1&filename=EGI-InSPIRE-Partners_list.pdf Members list]: full and short name, country, part * [https://documents.egi.eu/secure/RetrieveFile?docid=204&version=2&filename=EGI-InSPIRE-Partners_list%26JRUs.pdf Members and JRUs list]: JRUs in bold are t

{{Template:EGI-Engage menubar}} {{TOC_right}} '''Help and support:''' quality@egi.eu

{{EGI-Inspire_menubar}}{{Template:Inspire_reports_menubar}} {{TOC_right}} * Finalized EGI.eu RP OLA document (March 2012) [https://documents.egi.eu/document/463]

[[Category:Special Interest groups]] ...[https://indico.egi.eu/indico/categoryDisplay.py?categId=86 https://indico.egi.eu/indico/categoryDisplay.py?categId=86]

{{EGI-Inspire_menubar}} ...AM VO (NGI_FI, NGI_NDGF, NGI_DE, NGI_IT, NGI_IE, NGI_UK, NGI_ZA) and 3 ROC Groups were decommissioned (ROC_Italy, SEE, dech)

{{Template:EGI-Engage menubar}} {{TOC_right}} | https://wiki.egi.eu/wiki/PROC06_Review_of_project_outputs

...nt is available at [https://documents.egi.eu/document/86 https://documents.egi.eu/document/86]. ...r define the Security Policy ([https://wiki.egi.eu/wiki/SPG:Documents wiki.egi.eu/wiki/SPG:Documents]). This individual document must be considered in con

[[Category:Special Interest groups]] '''Coordinator''': M. Krakowian/EGI.eu

[[Category:Special Interest groups]] '''Coordinator''': M. Krakowian/EGI.eu<br>

{{Template:EGI-Engage menubar}} '''Help and support:''' quality@egi.eu

{{Template:EGI-Inspire menubar}} |https://www.egi.eu/indico/conferenceDisplay.py?confId=354

*''Management'' is the collection of the various boards, committees, groups and individuals mandated to oversee and control the ''Grid''. is the collection of various individuals and groups mandated to oversee

{{Template:EGI-Inspire menubar}} * MS427 Integrating Resources into the EGI Production Infrastructure: ToC ready and content being drafted

...propriate values. If the problem spans multiple compoments and 3rd support action is needed, the ticket is cloned (one new ticket per component), and the clo ...ould be properly documented as [[EGI_DMSU_Documentation#DMSU Digests]] and EGI operations should be informed.

{{EGI-Inspire_menubar}} One more (more pragmatic) example: Since the release ca-policy-egi-core-1.37-1 it is associated with the ca-1.0 major release,

'''Action''': * Data is replicated between CANFAR and EGI infrastructures

*Open submission interface for the groups <span style="color:green">'''Done'''</span> ...olve requirements and recommendations communicated by user communities and EGI stakeholders. The page provides manuals and background information to those

= EGI Federated Cloud jOCCI APIs = ...utions, Orchestrators, etc.) for scientific user communities on top of the EGI Federated Cloud.

...collect and report to VMOps information about the local VM configuration. Action: Vincenzo to contact IFCA, and push 3 sites that didn't reply yet. <br> ...e any comments on the content of this page, please contact '''operations @ egi.eu'''.

...POR partners during the first 3 months of the project (see [https://indico.egi.eu/indico/categoryDisplay.py?categId=100 Indico meetings]). Its goal is to ...O Support teams is generally to make the liaison between three actors: the EGI instances (UCST, UCB), the resource centres, and the VO users. The VO Suppo

...trator must be aware while setting up and operating a VO integrated in the EGI. #VO managers should read the <big>'''[https://documents.egi.eu/document/77 VO Operations Policy]'''</big> to understand their duties

{{Template:EGI-Engage menubar}} {{TOC_right}} [[EGI-Engage:Dissemination|Dissemination reports]]

{{EGI-Inspire_menubar}} ...itors the content of the page and incorporates contents from here into the EGI user support processes.

...ated reconstruction of neuron morphology has been studied by many research groups. Methods including fitting tubes or other geometrical elements, ray casting '''Action''':

...NILs]] and EGI.eu members. If you are a NGI staff, and you need access to EGI CRM, you should contact your NIL. NILs can ask for the inclusion of other a The EGI CRM can be accessed at http://crm.egi.eu by using EGI SSO credentials.

[[Category:Special Interest groups]] '''Meetings page''': [https://indico.egi.eu/indico/categoryDisplay.py?categId=115 Agendas]

{{Template:EGI-Engage menubar}} {{TOC_right}} [[EGI-Engage:Dissemination|Dissemination reports]]

= Summary of requirements collected by EGI Operations = {{TOC_right}} List of requirements by EGI Operations from the end of 2010 to February 2011.

{{Template:EGI-Inspire menubar}} This document provided by the partners responsible of EGI operations global tasks provide information about current status and the en