EGI. InSPIRE will collect user requirements and provide support for the current and emerging user communities. Support will also be given to the current heavy users of the infrastructure, such as high energy physics, computational chemistry and life sciences, as they move their critical services and tools from a centralised support model to one driven by their own individual communities.
EGI. InSPIRE and CHAIN may each release information to the public, provided it is related only to its own part of the activities under this MoU. In cases where the activities of the other Party are concerned prior consultation shall be sought. In all relevant public relations activities, the contribution of each Party related to activities covered by this MoU shall be duly acknowledged.
EGI. InSPIRE and ScalaLife may each release information to the public, provided it is related only to its own part of the activities under this MoU. In cases where the activities of the other Party are concerned prior consultation shall be sought. In all relevant public relations activities, the contribution of each Party related to activities covered by this MoU shall be duly acknowledged.
EGI. InSPIRE and SHIWA exchange information on active or potential communities to extend EGI communities and SHIWA workflow communities. Jan 2012 M1.2 Development and deployment of availability monitoring for SHIWA Repository. Jan 2012 M1.3 Exchange of training materials, applications, documentation between EGI and SHIWA support services and teams. As needed M1.4 Exchanging and discussing e-Infrastructure requirements between SHIWA and EGI, following these requirements within EGI through the established requirement tracking processes. Feb 2012 M2.2 Organise joint topical workshop on e-Science Workflows in Budapest 9-10 February 2012. Mar 2012 M2.3 Organise joint activity at EGI Community Forum 2012. May 2012 M2.4 Final report on the main achievements, open issues and future plans related to the collaboration between XXXXX and EGI-InSPIRE. The input must cover all of the activities that are defined in the Joint Work Plan section of the signed MoU.
EGI. InSPIRE and DECIDE may each release information to the public, provided it is related only to its own part of the activities under this MoU. In cases where the activities of the other Party are concerned prior consultation shall be sought. In all relevant public relations activities, the contribution of each Party related to activities covered by this MoU shall be duly acknowledged.
EGI. ARC, TP, CWF, EVW, CIII and LEG hereby designate each of Norwest and ANDA as a Financial Sponsor and Indemnitee for all purposes under the Indemnification Agreement, entitled to all of the rights and subject to all of the obligations attendant thereunder to that status. Each of Norwest and ANDA hereby consents and agrees to such designation, and further agrees that upon execution of this Joinder Agreement, it shall become a party to the Indemnification Agreement as a Financial Sponsor and an Indemnitee thereunder and shall be fully bound by, and subject to, all of the covenants, terms and conditions of the Indemnification Agreement as a Financial Sponsor and Indemnitee thereunder as though originally a party as a Financial Sponsor and Indemnitee thereunder.
EGI. InSPIRE and SIENA may each release information to the public, provided it is related only to its own part of the activities under this MoU. In cases where the activities of the other Party are concerned prior consultation shall be sought. In all relevant public relations activities, the contribution of each Party related to activities covered by this MoU shall be duly acknowledged.
EGI. The definition of the term "EGI" set forth in Article XI to the Loan Agreement is hereby amended in its entirety to read as follows:
EGI. InSPIRE and SHIWA exchange information on active or potential communities to extend EGI communities and SHIWA workflow communities. Jan 2012 M1.2 Development and deployment of availability monitoring for SHIWA Repository. Jan 2012 M1.3 Exchange of training materials, applications, documentation between EGI and SHIWA support services and teams. As needed M1.4 Exchanging and discussing e-Infrastructure requirements between SHIWA and EGI, following these requirements within EGI through the established requirement tracking processes. Feb 2012 M2.2 Organise joint topical workshop on e-Science Workflows in Budapest 9-10 February 2012. Mar 2012 M2.3 Organise joint activity at EGI Community Forum 2012.
EGI. On top of the Jupyter notebook production service as listed in the above table, the service xxxxx://xxxxxxxxx-xxxxxx.xxxxxxxx-xx.xxxxxxxx.xx/ and a Binder instance xxxxx://xxxxxx- xxxxxx.xxxxxxxx-xx.xxxxxxxx.xx/ are deployed on the CESNET-MCC cloud infrastructure. From a technical perspective, these two services are not in production even if production recipes were used. A Kubernetes cluster composed by one master and 3 worker nodes is used to spawn jupyter notebooks on demand. No GPU resources are currently available. Access to the resources granted using UmbrellaID. The h5web plugin for JupyterLab (xxxxx://xxxxxx.xxx/silx-kit/jupyterlab-h5web) has been installed at all facilities.
