https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Barbarak&feedformat=atom
EGIWiki - User contributions [en]
2024-03-19T05:54:28Z
User contributions
MediaWiki 1.37.1
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-EGI-SVG-2021-17247&diff=112969
SVG:Advisory-EGI-SVG-2021-17247
2021-05-16T20:01:57Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}}<br />
<br />
<pre><br />
<br />
Affected software and risk<br />
==========================<br />
<br />
HIGH risk vulnerability concerning Squid<br />
<br />
Package : Squid, including Frontier Squid [R 3] before version 4.15<br />
<br />
The Squid project has publicly announced [R 1] new vulnerabilities, one of which is deemed HIGH risk, viz. CVE-2020-25097 [R 2], because it may allow services to be exposed that are not directly accessible from the client host. The other ones only concern potential denial of service and hence are deemed low risk.<br />
<br />
<br />
Actions required/recommended<br />
============================<br />
<br />
Sites are recommended to update relevant components or apply the mitigation detailed below as soon as possible.<br />
<br />
<br />
Component installation information<br />
==================================<br />
<br />
The official repository for the distribution of grid middleware for EGI sites is<br />
repository.egi.eu which contains the EGI Unified Middleware Distribution (UMD).<br />
Sites using frontier-squid from the EGI UMD 4 should see:<br />
<br />
http://repository.egi.eu/sw/production/umd/4/centos7/x86_64/updates/<br />
<br />
The fixed version is frontier-squid-4.15-1.1. It is expected to become available<br />
in the next days, at which time an update to this advisory will be sent.<br />
<br />
<br />
Sites installing Squid from anywhere else should see information from their provider.<br />
<br />
Fixed versions (squid-3.5.20-17.el7_9.6) are available for RHEL 7 [R 5], CentOS 7 [R 6], SL 7 [R 7].<br />
<br />
<br />
Mitigation<br />
==========<br />
<br />
For sites that cannot upgrade in a timely manner, temporary workarounds for the<br />
high-risk vulnerability are provided here.<br />
<br />
If frontier-squid is used, update customize.sh with the following line and either reload or restart frontier-squid:<br />
<br />
setoption("uri_whitespace", "deny")<br />
<br />
<br />
<br />
If a plain squid is used instead, set the "uri_whitespace" directive in squid.conf to either:<br />
<br />
uri_whitespace deny<br />
<br />
or<br />
<br />
uri_whitespace encode<br />
<br />
and restart the squid service.<br />
<br />
<br />
Affected software details<br />
=========================<br />
<br />
All versions of squid and frontier-squid earlier than 4.15 are affected.<br />
<br />
<br />
Additional information<br />
======================<br />
<br />
Note that exposure of squid services should usually be limited by access control to addresses within a local area network.<br />
<br />
<br />
TLP and URL<br />
===========<br />
<br />
** WHITE information - Unlimited distribution<br />
- see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** <br />
<br />
URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-2021-17247 <br />
<br />
Minor updates may be made without re-distribution to the sites<br />
<br />
<br />
Comments<br />
========<br />
<br />
Comments or questions should be sent to svg-rat at mailman.egi.eu<br />
<br />
If you find or become aware of another vulnerability which is relevant to EGI you may report it by e-mail to <br />
<br />
report-vulnerability at egi.eu<br />
the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 4] <br />
<br />
Note that this is undergoing revision to fully handle vulnerabilities in the EOSC-hub era.<br />
<br />
<br />
References<br />
==========<br />
<br />
[R 1] http://lists.squid-cache.org/pipermail/squid-announce/2021-May/000127.html<br />
<br />
[R 2] https://github.com/squid-cache/squid/security/advisories/GHSA-jvf6-h9gj-pmj6<br />
<br />
[R 3] https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid<br />
<br />
[R 4] https://documents.egi.eu/public/ShowDocument?docid=3145<br />
<br />
[R 5] https://access.redhat.com/errata/RHSA-2021:1135<br />
<br />
[R 6] https://lists.centos.org/pipermail/centos-announce/2021-April/048302.html<br />
<br />
[R 7] https://listserv.fnal.gov/scripts/wa.exe?A2=ind2104&L=SCIENTIFIC-LINUX-ERRATA&P=1049<br />
<br />
<br />
Credit<br />
======<br />
<br />
SVG was alerted to this vulnerability by Dave Dykstra.<br />
<br />
Information on these vulnerabilities contained in this advisory is based on the corresponding OSG advisory for these vulnerabilities.<br />
<br />
<br />
Timeline <br />
========<br />
Yyyy-mm-dd [EGI-SVG-2021-17247]<br />
<br />
2021-05-10 SVG alerted to this issue by Dave Dykstra (FNAL)<br />
2021-05-10 Acknowledgement from the EGI SVG to the reporter<br />
2021-05-10 Investigation of vulnerability and relevance to EGI carried out<br />
2021-05-11 EGI SVG Risk Assessment completed<br />
2021-05-11 SVG drafts advisory based on OSG announcement<br />
2021-05-12 Advisory sent to sites<br />
<br />
<br />
Context<br />
=======<br />
<br />
This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose<br />
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"<br />
<br />
The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 4] in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. <br />
<br />
-----------------------------<br />
This advisory is subject to the Creative commons license https://creativecommons.org/licenses/by/4.0/ and the EGI https://www.egi.eu/ Software Vulnerability Group must be credited.<br />
-----------------------------<br />
<br />
Note that the SVG issue handling procedure is currently under review, to take account of the increasing inhomogeneity of the EGI infrastructure and the services in the EOSC-hub catalogue.<br />
<br />
On behalf of the EGI SVG,<br />
<br />
David Crooks<br />
<br />
</pre></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-EGI-SVG-2021-17247&diff=112968
SVG:Advisory-EGI-SVG-2021-17247
2021-05-16T20:00:19Z
<p>Barbarak: Blanked the page</p>
<hr />
<div></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-EGI-SVG-2021-17247&diff=112967
SVG:Advisory-EGI-SVG-2021-17247
2021-05-16T19:58:56Z
<p>Barbarak: Created page with "Affected software and risk ========================== HIGH risk vulnerability concerning Squid Package : Squid, including Frontier Squid [R 3] before version 4.15 The Sq..."</p>
<hr />
<div>Affected software and risk<br />
==========================<br />
<br />
HIGH risk vulnerability concerning Squid<br />
<br />
Package : Squid, including Frontier Squid [R 3] before version 4.15<br />
<br />
The Squid project has publicly announced [R 1] new vulnerabilities, one of which is deemed HIGH risk, viz. CVE-2020-25097 [R 2], because it may allow services to be exposed that are not directly accessible from the client host. The other ones only concern potential denial of service and hence are deemed low risk.<br />
<br />
<br />
Actions required/recommended<br />
============================<br />
<br />
Sites are recommended to update relevant components or apply the mitigation detailed below as soon as possible.<br />
<br />
<br />
Component installation information<br />
==================================<br />
<br />
The official repository for the distribution of grid middleware for EGI sites is<br />
repository.egi.eu which contains the EGI Unified Middleware Distribution (UMD).<br />
Sites using frontier-squid from the EGI UMD 4 should see:<br />
<br />
http://repository.egi.eu/sw/production/umd/4/centos7/x86_64/updates/<br />
<br />
The fixed version is frontier-squid-4.15-1.1. It is expected to become available<br />
in the next days, at which time an update to this advisory will be sent.<br />
<br />
<br />
Sites installing Squid from anywhere else should see information from their provider.<br />
<br />
Fixed versions (squid-3.5.20-17.el7_9.6) are available for RHEL 7 [R 5], CentOS 7 [R 6], SL 7 [R 7].<br />
<br />
<br />
Mitigation<br />
==========<br />
<br />
For sites that cannot upgrade in a timely manner, temporary workarounds for the<br />
high-risk vulnerability are provided here.<br />
<br />
If frontier-squid is used, update customize.sh with the following line and either reload or restart frontier-squid:<br />
<br />
setoption("uri_whitespace", "deny")<br />
<br />
<br />
<br />
If a plain squid is used instead, set the "uri_whitespace" directive in squid.conf to either:<br />
<br />
uri_whitespace deny<br />
<br />
or<br />
<br />
uri_whitespace encode<br />
<br />
and restart the squid service.<br />
<br />
<br />
Affected software details<br />
=========================<br />
<br />
All versions of squid and frontier-squid earlier than 4.15 are affected.<br />
<br />
<br />
Additional information<br />
======================<br />
<br />
Note that exposure of squid services should usually be limited by access control to addresses within a local area network.<br />
<br />
<br />
TLP and URL<br />
===========<br />
<br />
** WHITE information - Unlimited distribution<br />
- see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** <br />
<br />
URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-2021-17247 <br />
<br />
Minor updates may be made without re-distribution to the sites<br />
<br />
<br />
Comments<br />
========<br />
<br />
Comments or questions should be sent to svg-rat at mailman.egi.eu<br />
<br />
If you find or become aware of another vulnerability which is relevant to EGI you may report it by e-mail to <br />
<br />
report-vulnerability at egi.eu<br />
the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 4] <br />
<br />
Note that this is undergoing revision to fully handle vulnerabilities in the EOSC-hub era.<br />
<br />
<br />
References<br />
==========<br />
<br />
[R 1] http://lists.squid-cache.org/pipermail/squid-announce/2021-May/000127.html<br />
<br />
[R 2] https://github.com/squid-cache/squid/security/advisories/GHSA-jvf6-h9gj-pmj6<br />
<br />
[R 3] https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid<br />
<br />
[R 4] https://documents.egi.eu/public/ShowDocument?docid=3145<br />
<br />
[R 5] https://access.redhat.com/errata/RHSA-2021:1135<br />
<br />
[R 6] https://lists.centos.org/pipermail/centos-announce/2021-April/048302.html<br />
<br />
[R 7] https://listserv.fnal.gov/scripts/wa.exe?A2=ind2104&L=SCIENTIFIC-LINUX-ERRATA&P=1049<br />
<br />
<br />
Credit<br />
======<br />
<br />
SVG was alerted to this vulnerability by Dave Dykstra.<br />
<br />
Information on these vulnerabilities contained in this advisory is based on the corresponding OSG advisory for these vulnerabilities.<br />
<br />
<br />
Timeline <br />
========<br />
Yyyy-mm-dd [EGI-SVG-2021-17247]<br />
<br />
2021-05-10 SVG alerted to this issue by Dave Dykstra (FNAL)<br />
2021-05-10 Acknowledgement from the EGI SVG to the reporter<br />
2021-05-10 Investigation of vulnerability and relevance to EGI carried out<br />
2021-05-11 EGI SVG Risk Assessment completed<br />
2021-05-11 SVG drafts advisory based on OSG announcement<br />
2021-05-12 Advisory sent to sites<br />
<br />
<br />
Context<br />
=======<br />
<br />
This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose<br />
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"<br />
<br />
The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 4] in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. <br />
<br />
-----------------------------<br />
This advisory is subject to the Creative commons license https://creativecommons.org/licenses/by/4.0/ and the EGI https://www.egi.eu/ Software Vulnerability Group must be credited.<br />
-----------------------------<br />
<br />
Note that the SVG issue handling procedure is currently under review, to take account of the increasing inhomogeneity of the EGI infrastructure and the services in the EOSC-hub catalogue.<br />
<br />
On behalf of the EGI SVG,<br />
<br />
David Crooks</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisories&diff=112966
SVG:Advisories
2021-05-16T19:57:59Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}} <br />
<br />
<br />
All advisories which are disclosed publicly by SVG are placed on this wiki. <br />
<br />
All advisories which are disclosed publicly by SVG are subject to the Creative commons licence<br />
[https://creativecommons.org/licenses/by/4.0/ CC-BY 4.0.] including crediting the EGI [https://www.egi.eu/ https://www.egi.eu/] Software Vulnerability Group. <br />
<br />
A guide to the risk categories is available at [[SVG:Notes On Risk | Notes On Risk]]<br />
<br />
SVG also provides information that may be useful to various sites concerning the various <br />
[[SVG:Speculative Execution Vulnerabilities | SVG Speculative execution vulnerabilities ]]<br />
<br />
<br />
{| {{egi-table}}<br />
!Date !! Title !! Contents/Link !! Risk !! Status !!<br />
<br />
|-<br />
| 2021-05-12 || Squid Vulnerability <br />
|| [[SVG:Advisory-EGI-SVG-2021-17247 | Advisory-EGI-SVG-2021-17247]] || HIGH || Fixed ||<br />
|-<br />
<br />
<br />
|-<br />
| 2021-01-06, updated2021-03-22, 2021-04-06 || Linux Kernel release fixing various software vulnerabilities<br />
|| [[SVG:Advisory-SVG-CVE-2020-25211 | Advisory-SVG-CVE-2020-25211]] || HIGH || Fixed ||<br />
|-<br />
<br />
<br />
|-<br />
| 2020-11-06, updated 2021-03-23 || DPM vulnerability allowing file deletion <br />
|| [[SVG:Advisory-SVG-2020-16935 | Advisory-SVG-2020-16935]] || Critical || Fixed ||<br />
|-<br />
<br />
|-<br />
| 2021-01-15, updated 2021-03-22 || 2 HTCondor Vulnerabilities affecting a limited number of versions.<br />
|| [[SVG:Advisory-SVG-2021-17030 | Advisory-SVG-2021-17030]] || Critical || Fixed ||<br />
|-<br />
<br />
|-<br />
| 2021-01-27 || sudo privilege escalation vulnerability<br />
|| [[SVG:Advisory-SVG-CVE-2021-3156 | Advisory-SVG-CVE-2021-3156]] || Critical || Fixed ||<br />
|-<br />
| 2020-11-19 updated 2020-11-25, 2021-01-14 || Vulnerability concerning dCache<br />
|| [[SVG:Advisory-SVG-2020-16939 | Advisory-SVG-2020-16939]] || Critical || Fixed ||<br />
|-<br />
|}<br />
<br />
EGI SVG produces advisories according to the [https://documents.egi.eu/document/3145 EGI Software Vulnerability Issue Handling Process ], which was revised in 2017 and approved by the EGI OMB in November 2017. <br />
<br />
Note that SVG is currently working on how to better cope with reducing homogeneity of the infrastructure and handle vulnerabilities related to the EOSC-hub services.<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2020 | Advisories from 2020]]<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2019 | Advisories from 2019]]<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2018 | Advisories from 2018]]<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2017 | Advisories from 2017]]<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2016 | Advisories from 2016]]<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2014-2015 | Advisories from 2014 and 2015 ]] <br />
<br />
In the past (up to the end of 2015) CSIRT also issued general alerts at https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts<br />
and EGI SVG advisories primarily concerned gLite Middleware. <br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2011-2013 | Advisories from 2011 to 2013 ]]<br />
<br />
<br />
<br />
Advisories from prior to 2011 [https://archive.gridpp.ac.uk/gsvg/advisories/ Gridpp Advisories Archive]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPV6_Assessment&diff=101257
IPV6 Assessment
2019-03-11T09:10:19Z
<p>Barbarak: /* Infrastructure status and plans */</p>
<hr />
<div>== Core/EGI services ==<br />
<br />
{| style="border:1px solid black; text-align:left;" class="wikitable" cellspacing="0" cellpadding="5"<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | Core/EGI service <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | Contact point <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | IPv6 readiness <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | Comments<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Accounting repositories and portal<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Adrian Coveney <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Portal is OK, APEL-SSM has been updated to support IPv6 but this functionality is untested<br />
|- style="height:24px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Activities and services for the long tail of science<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Stéphane Gérard<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | hosted by CYFRONET, check CYFRONET<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Application DB <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Kostas Koumantaros <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Collaboration tools <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Martin Kuba <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | full support<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | E-GRANT services hosting and technical operations <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Tomasz Szepieniec <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#cccccc" | CANCELLED<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | to be integrated in Marketplace<br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Helpdesk (GGUS) <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Guenter Grein <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | For production instances IPv6 configuration since GGUS release on July, 26th 2017.<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Helpdesk human support <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Zdeněk Šustr <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | human support, no need to assess readiness<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Message brokers <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Monitoring services <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | Operations Portal <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Cyril L’Orphelin <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | planning to virtualize and replace a part of the web cluster (the only non-IPv6 compliant part) next year (2nd semester)<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Security coordination and security tools <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | David Kelsey <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | UNKNOWN <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | Service registry (GOCDB) <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | George Ryall <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Current configuration and software has been tested. Plans in place to make GOCDB IPv6 accessible by April 2018.<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Services for AAI <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br />
The EGI Catch All CA CRL is served only via IPv4 at the moment, but this will be fixed soon <br />
<br />
The EGI Catch All VOMS <span class="il">services</span>, do NOT support IPv6 and there is no plan to support it <br />
<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | UMD quality assurance <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Jorge Gomes <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ff0000" | NO <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | IFCA/LIP no plans, CESGA partial<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | UMD software provisioning infrastructure <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Kostas Koumantaros <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | CheckIn <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | CSGF <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Roberto Barbera <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | CVMFS Stratum-0 <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Catalin Condurache <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | IPv6 ready, STFC not ready<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | DIRAC4EGI <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Andrei Tsaregorodtsev <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | The DIRAC software is dual stack already<br> and supports IPv4/v6 client server communications. However, the hosting infrastructure at<br> CYFRONET where the DIRAC4EGI servers are running is still IPv4 and not IPv6 ready according<br> to the local administrators. I do not have time estimations from them about the IPv6 enabling.<br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | EC3 <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Miguel Caballer <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | Perun <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Michal Prochazka <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | User registration portal <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Roksana Dobrzańska <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#cccccc" | CANCELLED <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | to be integrated in Marketplace<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | WS-PGRADE <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Zoltán Farkas <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | No tests so far, but should be ready.<br />
|}<br />
<br />
== UMD ==<br />
<br />
The following tables collects the products tested so far during the UMD software provisioning process. Moved from https://wiki.egi.eu/wiki/Middleware_products_verified_for_the_support_of_IPv6 <br />
<br />
<br> <br />
<br />
{| style="border: 1px solid black;" class="wikitable" width="1305" cellspacing="0" cellpadding="5"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| ARC <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| DPM <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| FTS <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| BDII <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| LFC <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| VOMS-SERVER <br />
| bgcolor="#ffcc00" | PARTIAL<br />
| VOMS admin is IPv6 ready, the voms daemon seems not yet IPv6 ready, to be checked<br> <br />
| <br><br />
|-<br />
| UI <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| StoRM <br />
| bgcolor="#00cc00" | YES<br> <br />
| <br> <br />
| <br><br />
|-<br />
| frontier-squid-3 <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli, XACML <br />
| bgcolor="#00cc00" | YES <br />
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli rely fully on libcurl, hence is fully dual-stack. XACML <br />
does not create sockets or do name lookups. <br />
<br />
| <br><br />
|-<br />
| lcmaps-plugins-scas-client <br />
| bgcolor="#00cc00" | YES<br />
| Since version 0.5.7-1 lcmaps-plugins-scas-client is IPv6 compliant.<br />
<br />
| <br><br />
|-<br />
| dCache<br> <br />
| bgcolor="#00cc00" | YES <br />
| All currently supported versions of dCache support IPv6 in dual-stack and stand-alone mode.<br> <br> Since dCache is a distributed system, it is possible to have a dCache cluster that comprises of a mixture of IPv4-only, dual-stack, and IPv6-only machines.&nbsp; This, too, is supported, but obviously an IPv4-connected client cannot be redirected to an IPv6-only node. In such cases, dCache will make internal replicas or proxy the data. <br />
| <br><br />
|}<br />
<br />
== CMD and FedCloud product readiness ==<br />
<br />
== Infrastructure status and plans<br> ==<br />
<br />
{| width="1089" cellspacing="1" cellpadding="1" border="1"<br />
|+ IPv6 infrastructure readiness <br />
|-<br />
| '''NGI'''<br> <br />
| '''Status and plans''' <br />
| '''Total sites'''<br> <br />
| '''Sites implementing IPv6'''<br> <br />
| '''Is NREN ready?'''<br> <br />
| '''Willing tutorial on IPv6 in general''' <br />
| '''Willing tutorial on IPv6 security''' <br />
| '''Comments'''<br><br />
|-<br />
| AsiaPacific<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| CERN<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_AEGIS<br> <br />
| WILL_DO <br />
| 0<br> <br />
| 0<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <span class="im"><br />
<br />
Serbian NREN AMRES provides IPv4 and IPv6 connectivity services. Majority of network equipment was already configured to offer dual-stack IPv4/IPv6 connectivity, and there are no technical issues related to IPv6 implementing. Dedicated training events will speed up the implementation process.<br />
<br />
</span><br />
|-<br />
| NGI_ARMGRID<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_BG<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_BY<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_CH<br> <br />
| WILL_DO <br />
|6 <br> <br />
| 4<br> <br />
| YES<br> <br />
| YES <br />
| YES <br />
| <div>Partially done. Some sites need the Campus infrastructure to comply yet. Not all sites provide storage.</div><br />
|-<br />
| NGI_CZ<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_DE<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_FI<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_FRANCE<br> <br />
| The sites supporting WLCG experiments will provide IPv6 (it is mostly done), for the other sites, it is not a requirement.<br> <br />
| 13<br> <br />
| 11<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br><br />
|-<br />
| NGI_GE<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| In Georgia there is only one Grid site and it is IPv4 only, the same is GRENA network. Currently we are not planing to introduce IPv6 because there is still no demand in it. In this situation mentioned tutorials will not be very useful for our system administrators.<br />
|-<br />
| NGI_GRNET<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_HR<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_HU<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_IBERGRID<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_IL<br> <br />
| <br> WILL_DO<br />
| <br> 3<br />
| <br> 2<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br>D.Cohen: Two of three sites in NGI_IL are running all major services in dual stack for months now.<br />
The third site will follow but unfortunately I cannot predict when.<br />
|-<br />
| NGI_IT<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_MARGI<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_MD<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_ME<br> <br />
| bgcolor="#ff0000" | WON'T_DO <br />
| 1<br> <br />
| 0<br> <br />
| NO<br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_NDGF<br> <br />
| bgcolor="#66ff00" | WILL_DO (but see the comments)<br />
| <br> 5<br />
| <br> 5<br />
| <br> YES<br />
| <br> NO <br />
| <br> NO <br />
| * Storage is on IPv6 already.<br>* Support systems (like squids, bdii, etc.) are on IPv6 already. The only exception is our voms server ([http://voms.ndgf.org/ voms.ndgf.org]), since the software for some peculiar reason refuses to work properly on IPv6. We hope this will be fixed soon, so we can install a new version and switch on IPv6. --&gt; TO BE INVESTIGATED BY UMD<br>* Computing however does not have IPv6 enabled, but following the official request by ATLAS at least half of the computing sites will already have it enabled by June. Unclear if another half will follow, since this request is not a strict requirement.<br><br />
|-<br />
| NGI_NL<br> <br />
| bgcolor="#66ff00" | WILL_DO <br />
| 3<br> <br />
| 3<br> <br />
| 3<br> <br />
| NO<br> <br />
| NO<br> <br />
| <br />
If you, and another NGI or site, are offering capabilities and services that are not yet v6 enabled and offer status web content, please '''consider fronting it with e.g. CloudFlare's free offering to gain such v6''' capability at no cost to you and for the benefit of all <br />
<br />
Security training is in general always good, but - just if case they did not get it - for IPv6 a pointer to the proper guidance RFCs on v6 security should be good. The HEPiX v6 WG also has relevant materials in this area that can be re-used. <br />
<br />
|-<br />
| NGI_PL<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_RO<br> <br />
| bgcolor="#66ff00" | WILL_DO<br> <br />
| <br> <br />
| 100% <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br />
Status: All the sites have available IPv6 class, but it is not implemented. We could do the implementation when it would be mandatory. For the moment we have sufficient IPv4 addresses available. <br />
<br />
Plans: It is planned one implementation of an IPv6 storage.<span>&nbsp; </span>There is one other site that plans to implement IPv6 next year, depending on what CERN experiments and EGI is recommending. <br />
<br />
Hard to manage both stacks and new bugs introduced because of this. <br />
<br />
Before the implementation, extensive tests for the services should be mandatory. <br />
<br />
At an earlier IPv6 test, some time ago, we had compatibility issues regarding CREAM and Storage Element. If they are solved by now, we could try again. <br />
<br />
Is IPv6 compatible with all software from ATLAS/ALICE/LHCb experiments? <br />
<br />
|-<br />
| NGI_SI<br> <br />
| WILL_DO <br />
| 4<br> <br />
| 4<br> <br />
| YES<br> <br />
| <br> <br />
| <br> <br />
| <br />
ARNES - dual stack <br />
<br />
SIGNET - dual stack (one cluster has IPv6-only worker nodes and runs Atlas) <br />
<br />
Atos - dual stack <br />
<br />
Cipkebip - dual stack <br />
<br />
Central services are IPv6-ready. <br />
<br />
|-<br />
| NGI_SK<br> <br />
| bgcolor="#66ff00" | WILL_DO <br />
| 8<br> <br />
| 6<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br />
Five sites have IPv6 connectivity, one site is working on enabling IPv6 connectivity, two sites have only IPv4 connectivity. From the services only one SE is on dual stack, other services do not have their IPv6 addresses in DNS yet.<br />
<br />
|-<br />
| NGI_TR<br> <br />
| WILL_DO <br />
| 3<br> <br />
| 3<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
|<br />
Storage services are running on both IPv4 and IPv6 already.<br />
<br />
Support systems squid services and phedex server are running on both IPv4 and IPv6 already.<br />
<br />
Other services bdii and argus are running on IPv4 only. They will be on both IPv4 and IPv6 until the end of July.<br />
<br />
Computing services and worker nodes does not have IPv6 enabled yet.<br><br />
|-<br />
| NGI_UA<br> <br />
| WILL_DO<br> <br />
| 15<br> <br />
| 3<br> <br />
| YES<br> <br />
| <br> <br />
| <br> <br />
| bout simplicity and convenience of IPv6 compared to IPv4.<div class="gmail_default" style="font-family:courier new,monospace">&nbsp; But for many people, grid site administration is only a small part of their general duties and commonly they are not related to computer networking or IT support - they are scientists, professors or managers at most. Only a few sites have dedicated qualified engineers to support operations.</div><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; That means that site support is provided on best-effort basis and with least action. There even exist unofficial team of volunteers who silently support 1/3 of all the sites just to keep them running, because that sites simply do not have designated local technical administrator.</div><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; So, IPv6 is far off site administrators' interests and until there are no strong reason to migrate (e.g. 10% of web-sites in the Internet will be IPv6-only), I there will be no progress on this.</div><br><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; IPv6 was planned and/or deployed on the sites where it was a requirement (e.g. of WLCG experiment) and/or there is strong engineer team supporting the whole organization, not only its grid site.</div><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; I think that we do not have much audience interested enough in IPv6 tutorials in NGI_UA, unfortunately.</div>&nbsp; Nevertheless, personally I would like to continue promoting IPv6 in grid community.<br />
|-<br />
| NGI_UK<br> <br />
| Various stages of implementation<br> <br />
| 19<br> <br />
| 19<br> <br />
| Yes<br> <br />
| Yes<br> <br />
| Yes<br> <br />
| <br><br />
|-<br />
| ROC_Canada<br> <br />
| bgcolor="#66ff00" | WILL_DO<br> <br />
| 4<br> <br />
| 4<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| Four sites: one site has storage testbed with IPv6 enabled and plan to put all production storage services on IPv6 (dual stack) before April 2018. Another 3 sites plan to implement dual stack in 1~2 years.<br />
|-<br />
| ROC_LA<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Russia<br> <br />
| WILL_DO <br />
| <br> <br />
| ALL<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br><br />
|-<br />
| IDGF<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_CHINA<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
== WLCG plans ==<br />
<br />
== References ==<br />
<br />
*old wiki https://wiki.egi.eu/wiki/IPv6 <br />
*IPv6 test http://ipv6-test.com/ <br />
*status of the WLCG Tier0 and Tier 1 sites http://hepix-ipv6.web.cern.ch/sites-connectivity</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Meltdown_and_Spectre_Vulnerabilities&diff=98297
SVG:Meltdown and Spectre Vulnerabilities
2018-01-15T11:12:46Z
<p>Barbarak: /* RedHat Information */</p>
<hr />
<div>{{svg-header}} <br />
<br />
More information is likely to be added in the coming days. This is an initial version. <br />
<br />
== Purpose of this page ==<br />
<br />
To provide useful links and other information concerning the Meltdown and Spectre vulnerabilities, which we consider relevant to the EGI infrastructure.<br />
<br />
== What are they? ==<br />
<br />
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems. <br />
<br />
Meltdown affects most Intel chips, and has CVE-2017-5754 <br />
<br />
Spectre affects a wide range of chips, CVE-2017-5753 and CVE-2017-5715. <br />
<br />
Here you will find more information&nbsp; [http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/ http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/] <br />
<br />
[https://meltdownattack.com/ https://meltdownattack.com/ ], [https://spectreattack.com/ https://spectreattack.com/] and [https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html] <br />
<br />
== CERN information ==<br />
<br />
CERN has compiled information which is useful for many EGI sites <br />
<br />
[https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml] <br />
<br />
== Intel Information ==<br />
<br />
Product patches <br />
<br />
[https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File] <br />
<br />
== RedHat Information ==<br />
<br />
RedHat description: <br />
<br />
[https://access.redhat.com/security/vulnerabilities/speculativeexecution https://access.redhat.com/security/vulnerabilities/speculativeexecution] <br />
<br />
[https://access.redhat.com/articles/3307751 https://access.redhat.com/articles/3307751] <br />
<br />
<br> <br />
<br />
RedHat CVE info: [https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5754 https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5753 https://access.redhat.com/security/cve/CVE-2017-5753] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5715 https://access.redhat.com/security/cve/CVE-2017-5715] <br />
<br />
<br> <br />
<br />
RHEL6: <br />
<br />
kernel-2.6.32-696.18.7.el6: [https://access.redhat.com/errata/RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008] <br />
<br />
microcode_ctl-1.17-25.2.el6_9: [https://access.redhat.com/errata/RHSA-2018:0013 https://access.redhat.com/errata/RHSA-2018:0013] <br />
<br />
'''Important!''' <br />
<br />
There appears to be a bug with the microcode_ctl update for Intel model 79 processors (Intel(R) Xeon(R) CPU E5-2637 v4 @ 3.50GHz, Intel(R) Xeon(R) CPU E5-2643 v4 @ 3.40GHz, Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz and Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.50GHz). The system fails to boot due to udev rules. There is no solution to the problem but to downgrade the microcode_ctl package. For more information, see: https://bugzilla.redhat.com/show_bug.cgi?id=1532283 <br />
<br />
https://access.redhat.com/solutions/3314661 <br />
<br />
<br> RHEL7: <br />
<br />
kernel-3.10.0-693.11.6.el7: [https://access.redhat.com/errata/RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007] <br />
<br />
microcode_ctl-2.1-22.2.el7: [https://access.redhat.com/errata/RHSA-2018:0012 https://access.redhat.com/errata/RHSA-2018:0012] <br />
<br />
linux-firmware-20170606-57.gitc990aae.el7_4: [https://access.redhat.com/errata/RHSA-2018:0014 https://access.redhat.com/errata/RHSA-2018:0014] <br />
<br />
<br> qemu-kvm: <br />
<br />
RHEL6: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0024 https://access.redhat.com/errata/RHSA-2018:0024] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0030 https://access.redhat.com/errata/RHSA-2018:0030] <br />
<br />
RHEL7: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0023 https://access.redhat.com/errata/RHSA-2018:0023] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0029 https://access.redhat.com/errata/RHSA-2018:0029]<br />
<br />
== CentOS Information ==<br />
<br />
CentOS 7:<br />
<br />
* kernel Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022696.html CESA-2018:0007]<br />
* microcode_ctl Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022697.html CESA-2018:0012] <br> also needs dracut BugFix Update for AMD: [https://lists.centos.org/pipermail/centos-announce/2018-January/022708.html CEBA-2018:0042]<br />
* linux-firmware Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022698.html CESA-2018:0014]<br />
* qemu-kvm Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022705.html CESA-2018:0023]<br />
* libvirt Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022704.html CESA-2018:0029]<br />
<br />
CentOS 6:<br />
<br />
* kernel Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html CESA-2018:0008]<br />
* microcode_ctl Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022700.html CESA-2018:0013]<br />
* qemu-kvm Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022702.html CESA-2018:0024]<br />
* libvirt Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022703.html CESA-2018:0030]<br />
<br />
See further in the centos-announce Security mails for January<br />
[https://lists.centos.org/pipermail/centos-announce/2018-January/date.html https://lists.centos.org/pipermail/centos-announce/2018-January/date.html]<br />
<br />
== Some RedHat Linux related issues found ==<br />
<br />
A serious bug in the microcode updates for some Intel CPUs (model 79) as distributed by Redhat (at least for RHEL 6 and derivatives) was found by one site and reported to us. <br />
This update rendered systems unbootable.<br />
<br />
[https://bugzilla.redhat.com/show_bug.cgi?id=1532283 https://bugzilla.redhat.com/show_bug.cgi?id=1532283]<br />
<br />
[https://access.redhat.com/solutions/3314661 https://access.redhat.com/solutions/3314661<br />
<br />
== Scientific Linux ==<br />
<br />
SL6: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/] <br />
<br />
SL7: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/] <br />
<br />
<br> <br />
<br />
qemu-kvn: <br />
<br />
SL6: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180024-1/ http://scientificlinux.org/category/sl-errata/slsa-20180024-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180030-1/ http://scientificlinux.org/category/sl-errata/slsa-20180030-1/] <br />
<br />
SL7: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180023-1/ http://scientificlinux.org/category/sl-errata/slsa-20180023-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180029-1/ http://scientificlinux.org/category/sl-errata/slsa-20180029-1/] <br />
<br />
== Ubuntu ==<br />
<br />
[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown] <br />
<br />
== Xen ==<br />
<br />
* [https://xenbits.xen.org/xsa/advisory-254.html https://xenbits.xen.org/xsa/advisory-254.html]<br />
* [https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/ https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/]<br />
* [https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ]<br />
* [https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre]<br />
<br />
== Other Cloud related ==<br />
<br />
The Kernel update of the hypervisor appears to be enough to ensure the isolation of the VMs. <br />
<br />
[https://www.qemu.org/2018/01/04/spectre/ https://www.qemu.org/2018/01/04/spectre/]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Meltdown_and_Spectre_Vulnerabilities&diff=98281
SVG:Meltdown and Spectre Vulnerabilities
2018-01-15T07:17:19Z
<p>Barbarak: /* RedHat Information */</p>
<hr />
<div>{{svg-header}} <br />
<br />
More information is likely to be added in the coming days. This is an initial version. <br />
<br />
== Purpose of this page ==<br />
<br />
To provide useful links and other information concerning the Meltdown and Spectre vulnerabilities, which we consider relevant to the EGI infrastructure.<br />
<br />
== What are they? ==<br />
<br />
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems. <br />
<br />
Meltdown affects most Intel chips, and has CVE-2017-5754 <br />
<br />
Spectre affects a wide range of chips, CVE-2017-5753 and CVE-2017-5715. <br />
<br />
Here you will find more information&nbsp; [http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/ http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/] <br />
<br />
[https://meltdownattack.com/ https://meltdownattack.com/ ], [https://spectreattack.com/ https://spectreattack.com/] and [https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html] <br />
<br />
== CERN information ==<br />
<br />
CERN has compiled information which is useful for many EGI sites <br />
<br />
[https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml] <br />
<br />
== Intel Information ==<br />
<br />
Product patches <br />
<br />
[https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File] <br />
<br />
== RedHat Information ==<br />
<br />
RedHat description: <br />
<br />
[https://access.redhat.com/security/vulnerabilities/speculativeexecution https://access.redhat.com/security/vulnerabilities/speculativeexecution] <br />
<br />
[https://access.redhat.com/articles/3307751 https://access.redhat.com/articles/3307751] <br />
<br />
<br> <br />
<br />
RedHat CVE info: [https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5754 https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5753 https://access.redhat.com/security/cve/CVE-2017-5753] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5715 https://access.redhat.com/security/cve/CVE-2017-5715] <br />
<br />
<br> <br />
<br />
RHEL6: <br />
<br />
kernel-2.6.32-696.18.7.el6: [https://access.redhat.com/errata/RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008] <br />
<br />
microcode_ctl-1.17-25.2.el6_9: [https://access.redhat.com/errata/RHSA-2018:0013 https://access.redhat.com/errata/RHSA-2018:0013] <br />
<br />
'''Important!''' <br />
<br />
There appears to be a bug with the microcode_ctl update for Intel model 79 processors. The system fails to boot due to udev rules. There is no solution to the problem but to downgrade the microcode_ctl package. For more information, see: https://bugzilla.redhat.com/show_bug.cgi?id=1532283 <br />
<br />
https://access.redhat.com/solutions/3314661 <br />
<br />
<br> RHEL7: <br />
<br />
kernel-3.10.0-693.11.6.el7: [https://access.redhat.com/errata/RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007] <br />
<br />
microcode_ctl-2.1-22.2.el7: [https://access.redhat.com/errata/RHSA-2018:0012 https://access.redhat.com/errata/RHSA-2018:0012] <br />
<br />
linux-firmware-20170606-57.gitc990aae.el7_4: [https://access.redhat.com/errata/RHSA-2018:0014 https://access.redhat.com/errata/RHSA-2018:0014] <br />
<br />
<br> qemu-kvm: <br />
<br />
RHEL6: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0024 https://access.redhat.com/errata/RHSA-2018:0024] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0030 https://access.redhat.com/errata/RHSA-2018:0030] <br />
<br />
RHEL7: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0023 https://access.redhat.com/errata/RHSA-2018:0023] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0029 https://access.redhat.com/errata/RHSA-2018:0029]<br />
<br />
== CentOS Information ==<br />
<br />
CentOS 7:<br />
<br />
* kernel Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022696.html CESA-2018:0007]<br />
* microcode_ctl Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022697.html CESA-2018:0012] <br> also needs dracut BugFix Update for AMD: [https://lists.centos.org/pipermail/centos-announce/2018-January/022708.html CEBA-2018:0042]<br />
* linux-firmware Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022698.html CESA-2018:0014]<br />
* qemu-kvm Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022705.html CESA-2018:0023]<br />
* libvirt Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022704.html CESA-2018:0029]<br />
<br />
CentOS 6:<br />
<br />
* kernel Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html CESA-2018:0008]<br />
* microcode_ctl Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022700.html CESA-2018:0013]<br />
* qemu-kvm Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022702.html CESA-2018:0024]<br />
* libvirt Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022703.html CESA-2018:0030]<br />
<br />
See further in the centos-announce Security mails for January<br />
[https://lists.centos.org/pipermail/centos-announce/2018-January/date.html https://lists.centos.org/pipermail/centos-announce/2018-January/date.html]<br />
<br />
== Scientific Linux ==<br />
<br />
SL6: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/] <br />
<br />
SL7: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/] <br />
<br />
<br> <br />
<br />
qemu-kvn: <br />
<br />
SL6: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180024-1/ http://scientificlinux.org/category/sl-errata/slsa-20180024-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180030-1/ http://scientificlinux.org/category/sl-errata/slsa-20180030-1/] <br />
<br />
SL7: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180023-1/ http://scientificlinux.org/category/sl-errata/slsa-20180023-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180029-1/ http://scientificlinux.org/category/sl-errata/slsa-20180029-1/] <br />
<br />
== Ubuntu ==<br />
<br />
[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown] <br />
<br />
<br />
== Xen ==<br />
<br />
* [https://xenbits.xen.org/xsa/advisory-254.html https://xenbits.xen.org/xsa/advisory-254.html]<br />
* [https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/ https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/]<br />
* [https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ]<br />
* [https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre]<br />
<br />
== Other Cloud related ==<br />
<br />
The Kernel update of the hypervisor appears to be enough to ensure the isolation of the VMs. <br />
<br />
[https://www.qemu.org/2018/01/04/spectre/ https://www.qemu.org/2018/01/04/spectre/]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Meltdown_and_Spectre_Vulnerabilities&diff=98280
SVG:Meltdown and Spectre Vulnerabilities
2018-01-15T07:16:35Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}} <br />
<br />
More information is likely to be added in the coming days. This is an initial version. <br />
<br />
== Purpose of this page ==<br />
<br />
To provide useful links and other information concerning the Meltdown and Spectre vulnerabilities, which we consider relevant to the EGI infrastructure.<br />
<br />
== What are they? ==<br />
<br />
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems. <br />
<br />
Meltdown affects most Intel chips, and has CVE-2017-5754 <br />
<br />
Spectre affects a wide range of chips, CVE-2017-5753 and CVE-2017-5715. <br />
<br />
Here you will find more information&nbsp; [http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/ http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/] <br />
<br />
[https://meltdownattack.com/ https://meltdownattack.com/ ], [https://spectreattack.com/ https://spectreattack.com/] and [https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html] <br />
<br />
== CERN information ==<br />
<br />
CERN has compiled information which is useful for many EGI sites <br />
<br />
[https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml] <br />
<br />
== Intel Information ==<br />
<br />
Product patches <br />
<br />
[https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File] <br />
<br />
== RedHat Information ==<br />
<br />
RedHat description: <br />
<br />
[https://access.redhat.com/security/vulnerabilities/speculativeexecution https://access.redhat.com/security/vulnerabilities/speculativeexecution] <br />
<br />
[https://access.redhat.com/articles/3307751 https://access.redhat.com/articles/3307751] <br />
<br />
<br />
<br />
RedHat CVE info: [https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5754 https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5753 https://access.redhat.com/security/cve/CVE-2017-5753] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5715 https://access.redhat.com/security/cve/CVE-2017-5715] <br />
<br />
<br />
<br />
RHEL6: <br />
<br />
kernel-2.6.32-696.18.7.el6: [https://access.redhat.com/errata/RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008] <br />
<br />
microcode_ctl-1.17-25.2.el6_9: [https://access.redhat.com/errata/RHSA-2018:0013 https://access.redhat.com/errata/RHSA-2018:0013] <br />
<br />
'''<br />
Important!'''<br />
There appears to be a bug with the microcode_ctl update for Intel model 79 processors. The system fails to boot due to udev rules. There is no solution to the problem but to downgrade the microcode_ctl package. For more information, see:<br />
https://bugzilla.redhat.com/show_bug.cgi?id=1532283<br />
https://access.redhat.com/solutions/3314661<br />
<br />
<br />
RHEL7: <br />
<br />
kernel-3.10.0-693.11.6.el7: [https://access.redhat.com/errata/RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007] <br />
<br />
microcode_ctl-2.1-22.2.el7: [https://access.redhat.com/errata/RHSA-2018:0012 https://access.redhat.com/errata/RHSA-2018:0012] <br />
<br />
linux-firmware-20170606-57.gitc990aae.el7_4: [https://access.redhat.com/errata/RHSA-2018:0014 https://access.redhat.com/errata/RHSA-2018:0014] <br />
<br />
<br> qemu-kvm: <br />
<br />
RHEL6: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0024 https://access.redhat.com/errata/RHSA-2018:0024] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0030 https://access.redhat.com/errata/RHSA-2018:0030] <br />
<br />
RHEL7: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0023 https://access.redhat.com/errata/RHSA-2018:0023] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0029 https://access.redhat.com/errata/RHSA-2018:0029]<br />
<br />
== CentOS Information ==<br />
<br />
CentOS 7:<br />
<br />
* kernel Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022696.html CESA-2018:0007]<br />
* microcode_ctl Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022697.html CESA-2018:0012] <br> also needs dracut BugFix Update for AMD: [https://lists.centos.org/pipermail/centos-announce/2018-January/022708.html CEBA-2018:0042]<br />
* linux-firmware Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022698.html CESA-2018:0014]<br />
* qemu-kvm Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022705.html CESA-2018:0023]<br />
* libvirt Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022704.html CESA-2018:0029]<br />
<br />
CentOS 6:<br />
<br />
* kernel Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html CESA-2018:0008]<br />
* microcode_ctl Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022700.html CESA-2018:0013]<br />
* qemu-kvm Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022702.html CESA-2018:0024]<br />
* libvirt Security Update: [https://lists.centos.org/pipermail/centos-announce/2018-January/022703.html CESA-2018:0030]<br />
<br />
See further in the centos-announce Security mails for January<br />
[https://lists.centos.org/pipermail/centos-announce/2018-January/date.html https://lists.centos.org/pipermail/centos-announce/2018-January/date.html]<br />
<br />
== Scientific Linux ==<br />
<br />
SL6: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/] <br />
<br />
SL7: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/] <br />
<br />
<br> <br />
<br />
qemu-kvn: <br />
<br />
SL6: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180024-1/ http://scientificlinux.org/category/sl-errata/slsa-20180024-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180030-1/ http://scientificlinux.org/category/sl-errata/slsa-20180030-1/] <br />
<br />
SL7: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180023-1/ http://scientificlinux.org/category/sl-errata/slsa-20180023-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180029-1/ http://scientificlinux.org/category/sl-errata/slsa-20180029-1/] <br />
<br />
== Ubuntu ==<br />
<br />
[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown] <br />
<br />
<br />
== Xen ==<br />
<br />
* [https://xenbits.xen.org/xsa/advisory-254.html https://xenbits.xen.org/xsa/advisory-254.html]<br />
* [https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/ https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/]<br />
* [https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ]<br />
* [https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre]<br />
<br />
== Other Cloud related ==<br />
<br />
The Kernel update of the hypervisor appears to be enough to ensure the isolation of the VMs. <br />
<br />
[https://www.qemu.org/2018/01/04/spectre/ https://www.qemu.org/2018/01/04/spectre/]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Meltdown_and_Spectre_Vulnerabilities&diff=98267
SVG:Meltdown and Spectre Vulnerabilities
2018-01-11T15:06:12Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}} <br />
<br />
{{Template:Under_construction}} <br />
<br />
== Purpose of this page ==<br />
<br />
To provide useful links and other information concerning the Meltdown and Spectre vulnerabilities. <br />
<br />
== What are they? ==<br />
<br />
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems. <br />
<br />
Meltdown affects most Intel chips, and has CVE-2017-5754 <br />
<br />
Spectre affects a wide range of chips, CVE-2017-5753 and CVE-2017-5715. <br />
<br />
Here you will find more information&nbsp; [http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/ http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/] <br />
<br />
[https://meltdownattack.com/ https://meltdownattack.com/ ], [https://spectreattack.com/ https://spectreattack.com/] and [https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html] <br />
<br />
== CERN information ==<br />
<br />
CERN has compiled information which is useful for may EGI sites <br />
<br />
[https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml] <br />
<br />
== Intel Information ==<br />
<br />
Product patches <br />
<br />
[https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File] <br />
<br />
== RedHat Information ==<br />
<br />
RedHat description: <br />
<br />
[https://access.redhat.com/security/vulnerabilities/speculativeexecution https://access.redhat.com/security/vulnerabilities/speculativeexecution] <br />
<br />
[https://access.redhat.com/articles/3307751 https://access.redhat.com/articles/3307751] <br />
<br />
<br />
<br />
RedHat CVE info: [https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5754 https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5753 https://access.redhat.com/security/cve/CVE-2017-5753] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5715 https://access.redhat.com/security/cve/CVE-2017-5715] <br />
<br />
<br />
<br />
RHEL6: <br />
<br />
kernel-2.6.32-696.18.7.el6: [https://access.redhat.com/errata/RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008] <br />
<br />
microcode_ctl-1.17-25.2.el6_9: [https://access.redhat.com/errata/RHSA-2018:0013 https://access.redhat.com/errata/RHSA-2018:0013] <br />
<br />
RHEL7: <br />
<br />
kernel-3.10.0-693.11.6.el7: [https://access.redhat.com/errata/RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007] <br />
<br />
microcode_ctl-2.1-22.2.el7: [https://access.redhat.com/errata/RHSA-2018:0012 https://access.redhat.com/errata/RHSA-2018:0012] <br />
<br />
linux-firmware-20170606-57.gitc990aae.el7_4: [https://access.redhat.com/errata/RHSA-2018:0014 https://access.redhat.com/errata/RHSA-2018:0014] <br />
<br />
<br> qemu-kvm: <br />
<br />
RHEL6: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0024 https://access.redhat.com/errata/RHSA-2018:0024] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0030 https://access.redhat.com/errata/RHSA-2018:0030] <br />
<br />
RHEL7: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0023 https://access.redhat.com/errata/RHSA-2018:0023] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0029 https://access.redhat.com/errata/RHSA-2018:0029]<br />
<br />
== Scientific Linux ==<br />
<br />
SL6: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/] <br />
<br />
SL7: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/] <br />
<br />
<br> <br />
<br />
qemu-kvn: <br />
<br />
SL6: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180024-1/ http://scientificlinux.org/category/sl-errata/slsa-20180024-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180030-1/ http://scientificlinux.org/category/sl-errata/slsa-20180030-1/] <br />
<br />
SL7: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180023-1/ http://scientificlinux.org/category/sl-errata/slsa-20180023-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180029-1/ http://scientificlinux.org/category/sl-errata/slsa-20180029-1/] <br />
<br />
== Ubuntu ==<br />
<br />
[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown] <br />
<br />
== Xen ==<br />
<br />
[https://xenbits.xen.org/xsa/advisory-254.html https://xenbits.xen.org/xsa/advisory-254.html] <br />
<br />
== Other Cloud related ==<br />
<br />
The Kernel update of the hypervisor appears to be enough to ensure the isolation of the VMs. <br />
<br />
[https://www.qemu.org/2018/01/04/spectre/ https://www.qemu.org/2018/01/04/spectre/]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Meltdown_and_Spectre_Vulnerabilities&diff=98266
SVG:Meltdown and Spectre Vulnerabilities
2018-01-11T14:37:50Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}} <br />
<br />
{{Template:Under_construction}} <br />
<br />
== Purpose of this page ==<br />
<br />
To provide useful links and other information concerning the Meltdown and Spectre vulnerabilities. <br />
<br />
== What are they? ==<br />
<br />
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems. <br />
<br />
Meltdown affects most Intel chips, and has CVE-2017-5754 <br />
<br />
Spectre affects a wide range of chips, CVE-2017-5753 and CVE-2017-5715. <br />
<br />
Here you will find more information&nbsp; [http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/ http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/] <br />
<br />
[https://meltdownattack.com/ https://meltdownattack.com/ ], [https://spectreattack.com/ https://spectreattack.com/] and [https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html] <br />
<br />
== CERN information ==<br />
<br />
CERN has compiled information which is useful for may EGI sites <br />
<br />
[https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml] <br />
<br />
== Intel Information ==<br />
<br />
Product patches <br />
<br />
[https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File] <br />
<br />
== RedHat Information ==<br />
<br />
RedHat description:<br />
<br />
[https://access.redhat.com/security/vulnerabilities/speculativeexecution https://access.redhat.com/security/vulnerabilities/speculativeexecution] <br />
<br />
[https://access.redhat.com/articles/3307751 https://access.redhat.com/articles/3307751] <br />
<br />
RedHat CVE info: [https://access.redhat.com/security/cve/CVE-2017-5754 ]<br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5754 https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5753 https://access.redhat.com/security/cve/CVE-2017-5753] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5715 https://access.redhat.com/security/cve/CVE-2017-5715] <br />
<br />
RHEL6: <br />
<br />
kernel-2.6.32-696.18.7.el6: [https://access.redhat.com/errata/RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008] <br />
<br />
microcode_ctl-1.17-25.2.el6_9: [https://access.redhat.com/errata/RHSA-2018:0013 https://access.redhat.com/errata/RHSA-2018:0013] <br />
<br />
RHEL7: <br />
<br />
kernel-3.10.0-693.11.6.el7: [https://access.redhat.com/errata/RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007] <br />
<br />
microcode_ctl-2.1-22.2.el7: [https://access.redhat.com/errata/RHSA-2018:0012 https://access.redhat.com/errata/RHSA-2018:0012] <br />
<br />
linux-firmware-20170606-57.gitc990aae.el7_4: [https://access.redhat.com/errata/RHSA-2018:0014 https://access.redhat.com/errata/RHSA-2018:0014] <br />
<br />
<br> qemu-kvn: <br />
<br />
RHEL6: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0024 https://access.redhat.com/errata/RHSA-2018:0024] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0030 https://access.redhat.com/errata/RHSA-2018:0030] <br />
<br />
RHEL7: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0023 https://access.redhat.com/errata/RHSA-2018:0023] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0029 https://access.redhat.com/errata/RHSA-2018:0029] <br />
<br />
== Scientific Linux ==<br />
<br />
SL6: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/] <br />
<br />
SL7: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/] <br />
<br />
<br> <br />
<br />
qemu-kvn: <br />
<br />
SL6: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180024-1/ http://scientificlinux.org/category/sl-errata/slsa-20180024-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180030-1/ http://scientificlinux.org/category/sl-errata/slsa-20180030-1/] <br />
<br />
SL7: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180023-1/ http://scientificlinux.org/category/sl-errata/slsa-20180023-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180029-1/ http://scientificlinux.org/category/sl-errata/slsa-20180029-1/] <br />
<br />
== Ubuntu ==<br />
<br />
[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown] <br />
<br />
== Xen ==<br />
<br />
[https://xenbits.xen.org/xsa/advisory-254.html https://xenbits.xen.org/xsa/advisory-254.html] <br />
<br />
== Other Cloud related ==<br />
<br />
The Kernel update of the hypervisor appears to be enough to ensure the isolation of the VMs. <br />
<br />
[https://www.qemu.org/2018/01/04/spectre/ https://www.qemu.org/2018/01/04/spectre/]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Meltdown_and_Spectre_Vulnerabilities&diff=98265
SVG:Meltdown and Spectre Vulnerabilities
2018-01-11T14:36:54Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}} <br />
<br />
{{Template:Under_construction}} <br />
<br />
== Purpose of this page ==<br />
<br />
To provide useful links and other information concerning the Meltdown and Spectre vulnerabilities. <br />
<br />
== What are they? ==<br />
<br />
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems. <br />
<br />
Meltdown affects most Intel chips, and has CVE-2017-5754 <br />
<br />
Spectre affects a wide range of chips, CVE-2017-5753 and CVE-2017-5715. <br />
<br />
Here you will find more information&nbsp; [http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/ http://www.theregister.co.uk/2018/01/04/intel_amd_arm_cpu_vulnerability/] <br />
<br />
[https://meltdownattack.com/ https://meltdownattack.com/ ], [https://spectreattack.com/ https://spectreattack.com/] and [https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html]<br />
<br />
== CERN information ==<br />
<br />
CERN has compiled information which is useful for may EGI sites <br />
<br />
[https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml] <br />
<br />
== Intel Information ==<br />
<br />
Product patches <br />
<br />
[https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File] <br />
<br />
== RedHat Information ==<br />
<br />
RedHat description [https://access.redhat.com/security/vulnerabilities/speculativeexecution https://access.redhat.com/security/vulnerabilities/speculativeexecution] <br />
<br />
[https://access.redhat.com/articles/3307751 https://access.redhat.com/articles/3307751] <br />
<br />
RedHat CVE info: [https://access.redhat.com/security/cve/CVE-2017-5754 https://access.redhat.com/security/cve/CVE-2017-5754] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5753 https://access.redhat.com/security/cve/CVE-2017-5753] <br />
<br />
[https://access.redhat.com/security/cve/CVE-2017-5715 https://access.redhat.com/security/cve/CVE-2017-5715] <br />
<br />
RHEL6: <br />
<br />
kernel-2.6.32-696.18.7.el6: [https://access.redhat.com/errata/RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008] <br />
<br />
microcode_ctl-1.17-25.2.el6_9: [https://access.redhat.com/errata/RHSA-2018:0013 https://access.redhat.com/errata/RHSA-2018:0013] <br />
<br />
RHEL7: <br />
<br />
kernel-3.10.0-693.11.6.el7: [https://access.redhat.com/errata/RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007] <br />
<br />
microcode_ctl-2.1-22.2.el7: [https://access.redhat.com/errata/RHSA-2018:0012 https://access.redhat.com/errata/RHSA-2018:0012] <br />
<br />
linux-firmware-20170606-57.gitc990aae.el7_4: [https://access.redhat.com/errata/RHSA-2018:0014 https://access.redhat.com/errata/RHSA-2018:0014] <br />
<br />
<br> qemu-kvn: <br />
<br />
RHEL6: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0024 https://access.redhat.com/errata/RHSA-2018:0024] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0030 https://access.redhat.com/errata/RHSA-2018:0030] <br />
<br />
RHEL7: <br />
<br />
qemu-kvm: [https://access.redhat.com/errata/RHSA-2018:0023 https://access.redhat.com/errata/RHSA-2018:0023] <br />
<br />
libvirt: [https://access.redhat.com/errata/RHSA-2018:0029 https://access.redhat.com/errata/RHSA-2018:0029] <br />
<br />
== Scientific Linux ==<br />
<br />
SL6: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/] <br />
<br />
SL7: <br />
<br />
[https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/ https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/] <br />
<br />
<br> <br />
<br />
qemu-kvn: <br />
<br />
SL6: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180024-1/ http://scientificlinux.org/category/sl-errata/slsa-20180024-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180030-1/ http://scientificlinux.org/category/sl-errata/slsa-20180030-1/] <br />
<br />
SL7: <br />
<br />
qemu-kvm: [http://scientificlinux.org/category/sl-errata/slsa-20180023-1/ http://scientificlinux.org/category/sl-errata/slsa-20180023-1/] <br />
<br />
libvirt: [http://scientificlinux.org/category/sl-errata/slsa-20180029-1/ http://scientificlinux.org/category/sl-errata/slsa-20180029-1/] <br />
<br />
== Ubuntu ==<br />
<br />
[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown] <br />
<br />
== Xen ==<br />
<br />
[https://xenbits.xen.org/xsa/advisory-254.html https://xenbits.xen.org/xsa/advisory-254.html] <br />
<br />
== Other Cloud related ==<br />
<br />
The Kernel update of the hypervisor appears to be enough to ensure the isolation of the VMs. <br />
<br />
[https://www.qemu.org/2018/01/04/spectre/ https://www.qemu.org/2018/01/04/spectre/]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPV6_Assessment&diff=97987
IPV6 Assessment
2017-11-20T13:28:49Z
<p>Barbarak: /* Infrastructure status and plans */</p>
<hr />
<div>== Core/EGI services ==<br />
<br />
{| style="border:1px solid black; text-align:left;" class="wikitable" cellspacing="0" cellpadding="5"<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | Core/EGI service <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | Contact point <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | IPv6 readiness <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-weight:bold;" | Comments<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Accounting repositories and portal<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Adrian Coveney <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Portal is OK, updates to SSM required to support IPv6.<br />
|- style="height:24px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Activities and services for the long tail of science<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Stéphane Gérard<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | hosted by CYFRONET, check CYFRONET<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Application DB <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Kostas Koumantaros <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Collaboration tools <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Martin Kuba <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | full support<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | E-GRANT services hosting and technical operations <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Tomasz Szepieniec <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#cccccc" | CANCELLED<br> <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | to be integrated in Marketplace<br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Helpdesk (GGUS) <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Guenter Grein <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | For production instances IPv6 configuration is scheduled for the GGUS release on July, 26th 2017.<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Helpdesk human support <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Zdeněk Šustr <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | human support, no need to assess readiness<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Message brokers <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Monitoring services <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | Operations Portal <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Cyril L’Orphelin <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | planning to virtualize and replace a part of the web cluster (the only non-IPv6 compliant part) next year (2nd semester)<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Security coordination and security tools <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | David Kelsey <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | UNKNOWN <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | Service registry (GOCDB) <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | George Ryall <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | IPv6 ready, STFC not ready<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | Services for AAI <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br />
The EGI Catch All CA CRL is served only via IPv4 at the moment, but this will be fixed soon <br />
<br />
The EGI Catch All VOMS <span class="il">services</span>, do NOT support IPv6 and there is no plan to support it <br />
<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;font-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | UMD quality assurance <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Jorge Gomes <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ff0000" | NO <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | IFCA/LIP no plans, CESGA partial<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffccff" | UMD software provisioning infrastructure <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Kostas Koumantaros <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | CheckIn <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Christos Kanellopoulos <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | CSGF <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Roberto Barbera <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | CVMFS Stratum-0 <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Catalin Condurache <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ffff00" | PARTIAL <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | IPv6 ready, STFC not ready<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | DIRAC4EGI <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Andrei Tsaregorodtsev <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | The DIRAC software is dual stack already<br> and supports IPv4/v6 client server communications. However, the hosting infrastructure at<br> CYFRONET where the DIRAC4EGI servers are running is still IPv4 and not IPv6 ready according<br> to the local administrators. I do not have time estimations from them about the IPv6 enabling.<br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | EC3 <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Miguel Caballer <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | Perun <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Michal Prochazka <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | <br><br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | User registration portal <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Roksana Dobrzańska <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#cccccc" | CANCELLED <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | to be integrated in Marketplace<br />
|- style="height:21px;"<br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#ccffff" | WS-PGRADE <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | Zoltán Farkas <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" bgcolor="#66ff00" | YES <br />
| style="overflow:hidden;padding:2px 3px 2px 3px;vertical-align:bottom;" | No tests so far, but should be ready.<br />
|}<br />
<br />
== UMD ==<br />
<br />
The following tables collects the products tested so far during the UMD software provisioning process. Moved from https://wiki.egi.eu/wiki/Middleware_products_verified_for_the_support_of_IPv6 <br />
<br />
<br> <br />
<br />
{| style="border: 1px solid black;" class="wikitable" width="1305" cellspacing="0" cellpadding="5"<br />
|- style="background-color:darkgray;"<br />
! Product name <br />
! IPv6 support <br />
! Comments <br />
! GGUS ticket<br />
|-<br />
| CREAM <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| DPM <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| FTS <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| BDII <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| LFC <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| VOMS-SERVER <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| UI <br />
| bgcolor="#00cc00" | YES <br />
| <br> <br />
| <br><br />
|-<br />
| StoRM <br />
| bgcolor="#00cc00" | YES<br> <br />
| <br> <br />
| <br><br />
|-<br />
| frontier-squid-3 <br />
| bgcolor="#00cc00" | YES <br />
| <br><br />
| <br><br />
|-<br />
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli, XACML <br />
| bgcolor="#00cc00" | YES <br />
| argus-pep-api-c, lcmaps-plugins-c-pep, argus-gsi-pep-callout, argus-pepcli rely fully on libcurl, hence is fully dual-stack. XACML <br />
does not create sockets or do name lookups. <br />
<br />
| <br><br />
|-<br />
| lcmaps-plugins-scas-client <br />
| bgcolor="#ffcc00" | PARTIAL <br />
| lcmaps-plugins-scas-client does do a name lookup and socket creation and <br />
is currently not IPv6 compliant, but can only connect over IPv4. This is fixed in our trunk and will be released together with a fix for OpenSSL 1.1, which is currently blocked by VOMS. <br />
<br />
| <br><br />
|-<br />
| dCache<br> <br />
| bgcolor="#00cc00" | YES <br />
| All currently supported versions of dCache support IPv6 in dual-stack and stand-alone mode.<br> <br> Since dCache is a distributed system, it is possible to have a dCache cluster that comprises of a mixture of IPv4-only, dual-stack, and IPv6-only machines.&nbsp; This, too, is supported, but obviously an IPv4-connected client cannot be redirected to an IPv6-only node. In such cases, dCache will make internal replicas or proxy the data. <br />
| <br><br />
|}<br />
<br />
== CMD and FedCloud product readiness ==<br />
<br />
== Infrastructure status and plans<br> ==<br />
<br />
{| width="1089" cellspacing="1" cellpadding="1" border="1"<br />
|+ IPv6 infrastructure readiness <br />
|-<br />
| '''NGI'''<br> <br />
| '''Status and plans''' <br />
| '''Total sites'''<br> <br />
| '''Sites implementing IPv6'''<br> <br />
| '''Is NREN ready?'''<br> <br />
| '''Willing tutorial on IPv6 in general''' <br />
| '''Willing tutorial on IPv6 security''' <br />
| '''Comments'''<br><br />
|-<br />
| AsiaPacific<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| CERN<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_AEGIS<br> <br />
| WILL_DO <br />
| 0<br> <br />
| 0<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <span class="im"><br />
<br />
Serbian NREN AMRES provides IPv4 and IPv6 connectivity services. Majority of network equipment was already configured to offer dual-stack IPv4/IPv6 connectivity, and there are no technical issues related to IPv6 implementing. Dedicated training events will speed up the implementation process.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
</span><br />
|-<br />
| NGI_ARMGRID<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_BG<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_BY<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_CH<br> <br />
| WILL_DO <br />
| <br> <br />
| <br> <br />
| SHOULD&nbsp;BE<br> <br />
| YES <br />
| YES <br />
| <div>since our sites serve WLCG only, we will do our best to adhere to their deployment timeline. It would be desirable that the EGI timeline would somehow overlap.</div><br />
|-<br />
| NGI_CZ<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_DE<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_FI<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_FRANCE<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_GE<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| In Georgia there is only one Grid site and it is IPv4 only, the same is GRENA network. Currently we are not planing to introduce IPv6 because there is still no demand in it. In this situation mentioned tutorials will not be very useful for our system administrators.<br />
|-<br />
| NGI_GRNET<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_HR<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_HU<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_IBERGRID<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_IL<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_IT<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_MARGI<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_MD<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_ME<br> <br />
| bgcolor="#ff0000" | WON'T_DO <br />
| 1<br> <br />
| 0<br> <br />
| NO<br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_NDGF<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_NL<br> <br />
| bgcolor="#66ff00" | WILL_DO <br />
| 3<br> <br />
| 3<br> <br />
| 3<br> <br />
| NO<br> <br />
| NO<br> <br />
| <br />
If you, and another NGI or site, are offering capabilities and services that are not yet v6 enabled and offer status web content, please '''consider fronting it with e.g. CloudFlare's free offering to gain such v6''' capability at no cost to you and for the benefit of all <br />
<br />
Security training is in general always good, but - just if case they did not get it - for IPv6 a pointer to the proper guidance RFCs on v6 security should be good. The HEPiX v6 WG also has relevant materials in this area that can be re-used. <br />
<br />
|-<br />
| NGI_PL<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_RO<br> <br />
| bgcolor="#66ff00" | WILL_DO<br> <br />
| <br> <br />
| 100% <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br />
Status: All the sites have available IPv6 class, but it is not implemented. We could do the implementation when it would be mandatory. For the moment we have sufficient IPv4 addresses available. <br />
<br />
Plans: It is planned one implementation of an IPv6 storage.<span>&nbsp; </span>There is one other site that plans to implement IPv6 next year, depending on what CERN experiments and EGI is recommending. <br />
<br />
Hard to manage both stacks and new bugs introduced because of this. <br />
<br />
Before the implementation, extensive tests for the services should be mandatory. <br />
<br />
At an earlier IPv6 test, some time ago, we had compatibility issues regarding CREAM and Storage Element. If they are solved by now, we could try again. <br />
<br />
Is IPv6 compatible with all software from ATLAS/ALICE/LHCb experiments? <br />
<br />
|-<br />
| NGI_SI<br> <br />
| WILL_DO <br />
| 4<br> <br />
| 4<br> <br />
| YES<br> <br />
| <br> <br />
| <br> <br />
| <br />
ARNES - dual stack<br />
<br />
SIGNET - dual stack (one cluster has IPv6-only worker nodes and runs Atlas)<br />
<br />
Atos - dual stack<br />
<br />
Cipkebip - dual stack<br />
<br />
Central services are not all IPv6-ready. Will reconfigure until the end of the year.<br />
<br />
|-<br />
| NGI_SK<br> <br />
| bgcolor="#66ff00" | WILL_DO <br />
| 8<br> <br />
| 3<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br />
IISAS-Bratislava - testing IPv6 connectivity <br />
<br />
IEPSAS-Kosice - firewall blocking IPv6, they are working on solution <br />
<br />
FMPhI-UNIBA - has IPv6 addresses, they plan to implement IPv6 before April 2018 <br />
<br />
|-<br />
| NGI_TR<br> <br />
| bgcolor="#66ff00" | WILL_DO <br />
| 3<br> <br />
| 3<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br><br />
|-<br />
| NGI_UA<br> <br />
| WILL_DO<br> <br />
| 15<br> <br />
| 3<br> <br />
| YES<br> <br />
| <br> <br />
| <br> <br />
| bout simplicity and convenience of IPv6 compared to IPv4.<div class="gmail_default" style="font-family:courier new,monospace">&nbsp; But for many people, grid site administration is only a small part of their general duties and commonly they are not related to computer networking or IT support - they are scientists, professors or managers at most. Only a few sites have dedicated qualified engineers to support operations.</div><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; That means that site support is provided on best-effort basis and with least action. There even exist unofficial team of volunteers who silently support 1/3 of all the sites just to keep them running, because that sites simply do not have designated local technical administrator.</div><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; So, IPv6 is far off site administrators' interests and until there are no strong reason to migrate (e.g. 10% of web-sites in the Internet will be IPv6-only), I there will be no progress on this.</div><br><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; IPv6 was planned and/or deployed on the sites where it was a requirement (e.g. of WLCG experiment) and/or there is strong engineer team supporting the whole organization, not only its grid site.</div><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_default" style="font-family:courier new,monospace">&nbsp; I think that we do not have much audience interested enough in IPv6 tutorials in NGI_UA, unfortunately.</div>&nbsp; Nevertheless, personally I would like to continue promoting IPv6 in grid community.<br />
|-<br />
| NGI_UK<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| ROC_Canada<br> <br />
| bgcolor="#66ff00" | WILL_DO<br> <br />
| 4<br> <br />
| 4<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| Four sites: one site has storage testbed with IPv6 enabled and plan to put all production storage services on IPv6 (dual stack) before April 2018. Another 3 sites plan to implement dual stack in 1~2 years.<br />
|-<br />
| ROC_LA<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| Russia<br> <br />
| WILL_DO <br />
| <br> <br />
| ALL<br> <br />
| YES<br> <br />
| YES<br> <br />
| YES<br> <br />
| <br><br />
|-<br />
| IDGF<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| NGI_CHINA<br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
== WLCG plans ==<br />
<br />
== References ==<br />
<br />
*old wiki https://wiki.egi.eu/wiki/IPv6 <br />
*IPv6 test http://ipv6-test.com/ <br />
*status of the WLCG Tier0 and Tier 1 sites http://hepix-ipv6.web.cern.ch/sites-connectivity</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-SVG-CVE-2017-5689&diff=94829
SVG:Advisory-SVG-CVE-2017-5689
2017-05-17T08:55:18Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}}<br />
<br />
<pre><br />
<br />
Title: EGI-SVG Advisory [TLP:WHITE] 'HEADS-UP' on the escalation of privilege vulnerability in Intel AMT CVE-2017-5689 [EGI-SVG-CVE-2017-5689]<br />
<br />
Date: 2017-05-17 <br />
<br />
<br />
Affected software and risk<br />
==========================<br />
<br />
HEADS-UP on Intel AMT Vulnerability<br />
<br />
Package : Intel Active Management Technology (AMT)<br />
CVE ID : CVE-2017-5689<br />
<br />
Escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology<br />
<br />
<br />
Actions required/recommended<br />
============================<br />
<br />
Sites should upgrade the firmware as soon as available.<br />
<br />
Affected software details<br />
=========================<br />
<br />
There is an escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology versions firmware <br />
versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 that can allow an unprivileged attacker to gain control of the manageability features provided by these products.<br />
<br />
More information<br />
================<br />
<br />
On May 1st Intel released a security advisory [R 1] about a firmware vulnerability in certain systems that utilise Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM) <br />
or Intel® Small Business Technology (SBT). The vulnerability could enable a network attacker to remotely gain access to computers or devices that use these technologies. <br />
Computers and devices can be exploited even if powered down. Intel published a detection tool for the vulnerable systems [R 2]. Vendor specific details can be found on the Intel advisory page [R 3].<br />
<br />
To detect vulnerable machines in Linux you can use nmap:<br />
nmap -P0 -sT -sU -p16992,16993,16994,16995,623,664 <wired IP address><br />
<br />
Results of this test should be either closed or filtered for all ports.<br />
<br />
You can also use a python script for detection, see [R 4].<br />
<br />
Intel chipsets include a "Management Engine" (ME), if AMT is used in the ME, your system is vulnerable. You can check if the ME is enabled with lspci (See [R 5]:<br />
lspci | egrep '(MEI|HECI)'<br />
<br />
<br />
For more information, read also [R 6].<br />
<br />
Mitigations<br />
===========<br />
Some vendors announced the release of the new firmware only for the end of this month. The operating system is unaware of and cannot control the Intel AMT, <br />
hence a workaround for the firmware flaw cannot be applied in the operating system. As a mitigation firewall rules can be applied on the edge of the site <br />
(not on the level of operating system, as Intel AMT can intercept network packets destined for the system already before reaching the OS).<br />
<br />
TLP and URL<br />
===========<br />
<br />
** WHITE information - Unlimited distribution - see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** <br />
<br />
URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2017-5689 <br />
<br />
Minor updates may be made without re-distribution to the sites<br />
<br />
Comments<br />
========<br />
<br />
Comments or questions should be sent to svg-rat at mailman.egi.eu<br />
<br />
If you find or become aware of a vulnerability which is relevant to EGI you may report it by e-mail to <br />
<br />
report-vulnerability at egi.eu<br />
<br />
the EGI Software Vulnerability Group will take a look. <br />
<br />
<br />
References<br />
==========<br />
<br />
[R 1] https://newsroom.intel.com/news/important-security-information-intel-manageability-firmware/<br />
[R 2] https://downloadcenter.intel.com/download/26755<br />
[R 3] https://www.ssh.com/vulnerability/intel-amt/<br />
[R 4] https://github.com/CerberusSecurity/CVE-2017-5689<br />
[R 5] https://access.redhat.com/solutions/3019961<br />
[R 6] https://nvd.nist.gov/vuln/detail/CVE-2017-5689<br />
<br />
<br />
<br />
Credit<br />
======<br />
<br />
SVG was alerted to this vulnerability by Barbara Krasovec and Mischa Salle. <br />
<br />
<br />
Timeline <br />
========<br />
Yyyy-mm-dd [CVE-2017-5689] <br />
<br />
2017-05-12 SVG alerted to this issue.<br />
2017-05-12 Investigation of vulnerability and relevance to EGI carried out<br />
2017-01-13 EGI SVG Risk Assessment - agreed varies depending on the hardware<br />
2017-05-15 Agreed to send advisory<br />
2017-05-17 Advisory/Alert sent to sites<br />
<br />
<br />
Context<br />
=======<br />
<br />
This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose <br />
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"<br />
<br />
The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 5] in the context of how the software is used in the EGI infrastructure. <br />
It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. <br />
<br />
Others may re-use this information provided they:-<br />
<br />
1) Respect the provided TLP classification<br />
<br />
2) Credit the EGI https://www.egi.eu/ Software Vulnerability Group<br />
<br />
</pre></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-SVG-CVE-2017-5689&diff=94828
SVG:Advisory-SVG-CVE-2017-5689
2017-05-17T08:47:20Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}}<br />
<br />
<pre><br />
<br />
Title: EGI-SVG Advisory [TLP:WHITE] 'HEADS-UP' on the escalation of privilege vulnerability in Intel AMT CVE-2017-5689 [EGI-SVG-CVE-2017-5689]<br />
<br />
Date: 2017-05-17 <br />
<br />
<br />
Affected software and risk<br />
==========================<br />
<br />
HEADS-UP on Intel AMT Vulnerability<br />
<br />
Package : Intel Active Management Technology (AMT)<br />
CVE ID : CVE-2017-5689<br />
<br />
Escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology<br />
<br />
<br />
Actions required/recommended<br />
============================<br />
<br />
Sites should upgrade the firmware as soon as available.<br />
<br />
Affected software details<br />
=========================<br />
<br />
There is an escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology versions firmware versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 that can allow an unprivileged attacker to gain control of the manageability features provided by these products.<br />
<br />
More information<br />
================<br />
<br />
On May 1st Intel released a security advisory [R 1] about a firmware vulnerability in certain systems that utilise Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM) or Intel® Small Business Technology (SBT). The vulnerability could enable a network attacker to remotely gain access to computers or devices that use these technologies. Computers and devices can be exploited even if powered down. Intel published a detection tool for the vulnerable systems [R 2]. Vendor specific details can be found on the Intel advisory page [R 3].<br />
<br />
To detect vulnerable machines in Linux you can use nmap:<br />
nmap -P0 -sT -sU -p16992,16993,16994,16995,623,664 <wired IP address><br />
<br />
Results of this test should be either closed or filtered for all ports.<br />
<br />
You can also use a python script for detection, see [R 4].<br />
<br />
Intel chipsets include a "Management Engine" (ME), if AMT is used in the ME, your system is vulnerable. You can check if the ME is enabled with lspci (See [R 5]:<br />
lspci | egrep '(MEI|HECI)'<br />
<br />
<br />
For more information, read also [R 6].<br />
<br />
Mitigations<br />
===========<br />
Some vendors announced the release of the new firmware only for the end of this month. The operating system is unaware of and cannot control the Intel AMT, hence a workaround for the firmware flaw cannot be applied in the operating system. As a mitigation firewall rules can be applied on the edge of the site (not on the level of operating system, as Intel AMT can intercept network packets destined for the system already before reaching the OS).<br />
<br />
TLP and URL<br />
===========<br />
<br />
** WHITE information - Unlimited distribution - see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** <br />
<br />
URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2017-5689 <br />
<br />
Minor updates may be made without re-distribution to the sites<br />
<br />
Comments<br />
========<br />
<br />
Comments or questions should be sent to svg-rat at mailman.egi.eu<br />
<br />
If you find or become aware of a vulnerability which is relevant to EGI you may report it by e-mail to <br />
<br />
report-vulnerability at egi.eu<br />
<br />
the EGI Software Vulnerability Group will take a look. <br />
<br />
<br />
References<br />
==========<br />
<br />
[R 1] https://newsroom.intel.com/news/important-security-information-intel-manageability-firmware/<br />
[R 2] https://downloadcenter.intel.com/download/26755<br />
[R 3] https://www.ssh.com/vulnerability/intel-amt/<br />
[R 4] https://github.com/CerberusSecurity/CVE-2017-5689<br />
[R 5] https://access.redhat.com/solutions/3019961<br />
[R 6] https://nvd.nist.gov/vuln/detail/CVE-2017-5689<br />
<br />
<br />
<br />
Credit<br />
======<br />
<br />
SVG was alerted to this vulnerability by Barbara Krasovec and Mischa Salle. <br />
<br />
<br />
Timeline <br />
========<br />
Yyyy-mm-dd [CVE-2017-5689] <br />
<br />
2017-05-12 SVG alerted to this issue.<br />
2017-05-12 Investigation of vulnerability and relevance to EGI carried out<br />
2017-01-13 EGI SVG Risk Assessment - agreed varies depending on the hardware<br />
2017-05-15 Agreed to send advisory<br />
2017-05-17 Advisory/Alert sent to sites<br />
<br />
<br />
Context<br />
=======<br />
<br />
This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose <br />
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"<br />
<br />
The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 5] in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. <br />
<br />
Others may re-use this information provided they:-<br />
<br />
1) Respect the provided TLP classification<br />
<br />
2) Credit the EGI https://www.egi.eu/ Software Vulnerability Group<br />
<br />
</pre></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-SVG-CVE-2017-5689&diff=94827
SVG:Advisory-SVG-CVE-2017-5689
2017-05-17T08:36:01Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}}<br />
<br />
<pre><br />
<br />
Title: Intel AMT [TLP:WHITE] 'HEADS-UP on the escalation of privilege vulnerability' <br />
CVE-2017-2636 [EGI-SVG-CVE-2017-5689]<br />
<br />
Date: 2017-05-17 <br />
<br />
<br />
Affected software and risk<br />
==========================<br />
<br />
HEADS-UP on Intel AMT Vulnerability<br />
<br />
Package : Intel Active Management Technology (AMT)<br />
CVE ID : CVE-2017-5689<br />
<br />
Escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology<br />
<br />
<br />
Actions required/recommended<br />
============================<br />
<br />
Sites should upgrade the firmware as soon as available.<br />
<br />
Affected software details<br />
=========================<br />
<br />
There is an escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology versions firmware versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 that can allow an unprivileged attacker to gain control of the manageability features provided by these products.<br />
<br />
More information<br />
================<br />
<br />
On May 1st Intel released a security advisory [R 1] about a firmware vulnerability in certain systems that utilise Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM) or Intel® Small Business Technology (SBT). The vulnerability could enable a network attacker to remotely gain access to computers or devices that use these technologies. Computers and devices can be exploited even if powered down. Intel published a detection tool for the vulnerable systems [R 2]. Vendor specific details can be found on the Intel advisory page [R 3].<br />
<br />
To detect vulnerable machines in Linux you can use nmap:<br />
nmap -P0 -sT -sU -p16992,16993,16994,16995,623,664 <wired IP address><br />
<br />
Results of this test should be either closed or filtered for all ports.<br />
<br />
You can also use a python script for detection, see [R 4].<br />
<br />
Intel chipsets include a "Management Engine" (ME), if AMT is used in the ME, your system is vulnerable. You can check if the ME is enabled with lspci (See [R 5]:<br />
lspci | egrep '(MEI|HECI)'<br />
<br />
<br />
For more information, read also [R 6].<br />
<br />
Mitigations<br />
===========<br />
Some vendors announced the release of the new firmware only for the end of this month. The operating system is unaware of and cannot control the Intel AMT, hence a workaround for the firmware flaw cannot be applied in the operating system. As a mitigation firewall rules can be applied on the edge of the site (not on the level of operating system, as Intel AMT can intercept network packets destined for the system already before reaching the OS).<br />
<br />
TLP and URL<br />
===========<br />
<br />
** WHITE information - Unlimited distribution - see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** <br />
<br />
URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2017-5689 <br />
<br />
Minor updates may be made without re-distribution to the sites<br />
<br />
Comments<br />
========<br />
<br />
Comments or questions should be sent to svg-rat at mailman.egi.eu<br />
<br />
If you find or become aware of a vulnerability which is relevant to EGI you may report it by e-mail to <br />
<br />
report-vulnerability at egi.eu<br />
<br />
the EGI Software Vulnerability Group will take a look. <br />
<br />
<br />
References<br />
==========<br />
<br />
[R 1] https://newsroom.intel.com/news/important-security-information-intel-manageability-firmware/<br />
[R 2] https://downloadcenter.intel.com/download/26755<br />
[R 3] https://www.ssh.com/vulnerability/intel-amt/<br />
[R 4] https://github.com/CerberusSecurity/CVE-2017-5689<br />
[R 5] https://access.redhat.com/solutions/3019961<br />
[R 6] https://nvd.nist.gov/vuln/detail/CVE-2017-5689<br />
<br />
<br />
<br />
Credit<br />
======<br />
<br />
SVG was alerted to this vulnerability by Barbara Krasovec and Mischa Salle. <br />
<br />
<br />
Timeline <br />
========<br />
Yyyy-mm-dd [CVE-2017-5689] <br />
<br />
2017-05-12 SVG alerted to this issue.<br />
2017-05-12 Investigation of vulnerability and relevance to EGI carried out<br />
2017-01-13 EGI SVG Risk Assessment - agreed varies depending on the hardware<br />
2017-05-15 Agreed to send advisory<br />
2017-05-17 Advisory/Alert sent to sites<br />
<br />
<br />
Context<br />
=======<br />
<br />
This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose <br />
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"<br />
<br />
The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 5] in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. <br />
<br />
Others may re-use this information provided they:-<br />
<br />
1) Respect the provided TLP classification<br />
<br />
2) Credit the EGI https://www.egi.eu/ Software Vulnerability Group<br />
<br />
</pre></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisory-SVG-CVE-2017-5689&diff=94826
SVG:Advisory-SVG-CVE-2017-5689
2017-05-17T08:29:43Z
<p>Barbarak: Created page with "Affected software and risk ========================== HEADS-UP on Intel AMT Vulnerability Package : Intel Active Management Technology (AMT) CVE ID : CVE-2017-5689 Escalation..."</p>
<hr />
<div>Affected software and risk<br />
==========================<br />
<br />
HEADS-UP on Intel AMT Vulnerability<br />
<br />
Package : Intel Active Management Technology (AMT)<br />
CVE ID : CVE-2017-5689<br />
<br />
Escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology<br />
<br />
<br />
Actions required/recommended<br />
============================<br />
<br />
Sites should upgrade the firmware as soon as available.<br />
<br />
Affected software details<br />
=========================<br />
<br />
There is an escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology versions firmware versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 that can allow an unprivileged attacker to gain control of the manageability features provided by these products.<br />
<br />
More information<br />
================<br />
<br />
On May 1st Intel released a security advisory [R 1] about a firmware vulnerability in certain systems that utilise Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM) or Intel® Small Business Technology (SBT). The vulnerability could enable a network attacker to remotely gain access to computers or devices that use these technologies. Computers and devices can be exploited even if powered down. Intel published a detection tool for the vulnerable systems [R 2]. Vendor specific details can be found on the Intel advisory page [R 3].<br />
<br />
To detect vulnerable machines in Linux you can use nmap:<br />
nmap -P0 -sT -sU -p16992,16993,16994,16995,623,664 <wired IP address><br />
<br />
Results of this test should be either closed or filtered for all ports.<br />
<br />
You can also use a python script for detection, see [R 4].<br />
<br />
Intel chipsets include a "Management Engine" (ME), if AMT is used in the ME, your system is vulnerable. You can check if the ME is enabled with lspci (See [R 5]:<br />
lspci | egrep '(MEI|HECI)'<br />
<br />
<br />
For more information, read also [R 6].<br />
<br />
Mitigations<br />
===========<br />
Some vendors announced the release of the new firmware only for the end of this month. The operating system is unaware of and cannot control the Intel AMT, hence a workaround for the firmware flaw cannot be applied in the operating system. As a mitigation firewall rules can be applied on the edge of the site (not on the level of operating system, as Intel AMT can intercept network packets destined for the system already before reaching the OS).<br />
<br />
TLP and URL<br />
===========<br />
<br />
** WHITE information - Unlimited distribution - see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** <br />
<br />
URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2017-5689 <br />
<br />
Minor updates may be made without re-distribution to the sites<br />
<br />
Comments<br />
========<br />
<br />
Comments or questions should be sent to svg-rat at mailman.egi.eu<br />
<br />
If you find or become aware of a vulnerability which is relevant to EGI you may report it by e-mail to <br />
<br />
report-vulnerability at egi.eu<br />
<br />
the EGI Software Vulnerability Group will take a look. <br />
<br />
<br />
References<br />
==========<br />
<br />
[R 1] https://newsroom.intel.com/news/important-security-information-intel-manageability-firmware/<br />
[R 2] https://downloadcenter.intel.com/download/26755<br />
[R 3] https://www.ssh.com/vulnerability/intel-amt/<br />
[R 4] https://github.com/CerberusSecurity/CVE-2017-5689<br />
[R 5] https://access.redhat.com/solutions/3019961<br />
[R 6] https://nvd.nist.gov/vuln/detail/CVE-2017-5689<br />
<br />
<br />
<br />
Credit<br />
======<br />
<br />
SVG was alerted to this vulnerability by Barbara Krasovec and Mischa Salle. <br />
<br />
<br />
Timeline <br />
========<br />
Yyyy-mm-dd [CVE-2017-5689] <br />
<br />
2017-05-12 SVG alerted to this issue.<br />
2017-05-12 Investigation of vulnerability and relevance to EGI carried out<br />
2017-01-13 EGI SVG Risk Assessment - agreed varies depending on the hardware<br />
2017-05-15 Agreed to send advisory<br />
2017-05-17 Advisory/Alert sent to sites<br />
<br />
<br />
Context<br />
=======<br />
<br />
This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose <br />
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"<br />
<br />
The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 5] in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. <br />
<br />
Others may re-use this information provided they:-<br />
<br />
1) Respect the provided TLP classification<br />
<br />
2) Credit the EGI https://www.egi.eu/ Software Vulnerability Group</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=SVG:Advisories&diff=94825
SVG:Advisories
2017-05-17T08:29:26Z
<p>Barbarak: </p>
<hr />
<div>{{svg-header}} <br />
<br />
<br />
All advisories which are disclosed publicly by SVG are placed on this wiki. <br />
<br />
A guide to the risk categories is available at [[SVG:Notes On Risk | Notes On Risk]]<br />
<br />
<br />
{| {{egi-table}}<br />
!Date !! Title !! Contents/Link !! Risk !! Status !!<br />
<br />
|-<br />
| 2017-05-17 || Intel AMT Vulnerability || [[SVG:Advisory-SVG-CVE-2017-5689 | Advisory-SVG-CVE-2017-5689 ]] || || (Check) ||<br />
|-<br />
<br />
|-<br />
| 2017-03-09 updated 2017-04-27 || Linux Kernel (n_hdlc module) privilege escalation vulnerability || [[SVG:Advisory-SVG-CVE-2017-2636 | Advisory-SVG-CVE-2017-2636 ]] || High || Fixed ||<br />
|-<br />
<br />
<br />
<br />
|-<br />
| 2017-02-28 || Linux Kernel (DCCP module) privilege escalation vulnerability || [[SVG:Advisory-SVG-CVE-2017-6074 | Advisory-SVG-CVE-2017-6074 ]] || High || Fixed ||<br />
|-<br />
<br />
<br />
|-<br />
| 2017-02-17 || Singularity container escape vulnerability || [[SVG:Advisory-SVG-2017-12381 | Advisory-SVG-2017-12381 ]] || Up to High || Fixed ||<br />
|-<br />
<br />
<br />
|-<br />
| 2017-02-13 || Attacks on Hadoop installations - check configuration || [[SVG:Advisory-SVG-2017-12931 | Advisory-SVG-2017-12931 ]] || || (Check) ||<br />
|-<br />
<br />
<br />
|-<br />
| 2017-02-01 || Ansible input validation vulnerability || [[SVG:Advisory-SVG-CVE-2016-9587 | Advisory-SVG-CVE-2016-9587 ]] || Up to High || Fixed ||<br />
|-<br />
<br />
<br />
|-<br />
| 2016-11-10 updated 2016-12-14, 2017-01-13 || Linux kernel vulnerability || [[SVG:Advisory-SVG-CVE-2016-7117 | Advisory-SVG-CVE-2016-7117 ]] || High || Fixed ||<br />
|-<br />
<br />
<br />
|-<br />
| 2017-01-11 || OpenStack Nova Metadata leak -sites should check || [[SVG:Advisory-SVG-2016-12231 | Advisory-SVG-2016-12231 ]] || || (check) ||<br />
|-<br />
<br />
|-<br />
| 2017-01-10 || SLURM vulnerability CVE-2016-10030 || [[SVG:Advisory-SVG-CVE-2016-10030 | Advisory-SVG-CVE-2016-10030 ]] || High || Fixed ||<br />
|-<br />
<br />
<br />
|}<br />
<br />
EGI SVG produces advisories according to the EGI SVG issue handling procedure, which was revised in autumn 2015.<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2016 | Advisories from 2016]]<br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2014-2015 | Advisories from 2014 and 2015 ]] <br />
<br />
In the past (up to the end of 2015) CSIRT also issued general alerts at https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts<br />
and EGI SVG advisories primarily concerned gLite Middleware. <br />
<br />
Earlier Advisories: [[SVG:Advisories-SVG-2011-2013 | Advisories from 2011 to 2013 ]]<br />
<br />
<br />
<br />
Advisories from prior to 2011 [https://archive.gridpp.ac.uk/gsvg/advisories/ Gridpp Advisories Archive]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-US-QR10&diff=45732
EGI-InSPIRE:Slovenia-US-QR10
2012-11-20T10:04:41Z
<p>Barbarak: </p>
<hr />
<div><!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--> <br />
<br />
__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| QR10<br />
| NGI_SI<br />
| ARNES<br />
| Barbara Krasovec<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date<br />
! Location<br />
! Title<br />
! Participants<br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-19.10.2012<br />
| Ljubljana, Slovenia<br />
| Arc School<br />
| 25<br />
| <br />
http://arcschool.blog.arnes.si/<br />
<br />
(available only in slovene)<br />
<br />
|}<br />
<br />
<br> ===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title<br />
! Journal / Proceedings title<br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''<br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. User Support achievements ===<br />
<br />
- new users<br />
<br />
- Arc school<br />
<br />
=== 2.2. Plans ===<br />
<br />
- Change of LRMS at site Arnes<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --> <br />
<br />
- New nodes<br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--> <br />
<br />
[[Category:NGI_QR_Reports]]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReportArcCE&diff=40841
IPv6TestReportArcCE
2012-09-25T05:28:10Z
<p>Barbarak: /* D.1): gridftp test */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Tools menubar}} <br />
<br />
<br> <br />
<br />
= A): Dual Stack on both C and S behavior: =<br />
<br />
=== A.1): Submission ===<br />
<pre>arctest -J 3 -c meja.arnes.si<br />
<br />
Test submitted with jobid: gsiftp://meja.arnes.si:2811/jobs/MKoMDm6UjXgnYFU0XooFSKOnABFKDmABFKDmqwHKDmABFKDmIVla6n<br />
</pre> <br />
<br> <br />
<pre>arcls gsiftp://meja.arnes.si:2811<br />
jobs</pre> <br />
;<br />
<br />
= <br> = B): IPv6-only on Client; Server in Dual Stack behavior: =<br />
<br />
;;<br> =<br />
<br />
=== B.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre><br />
<br> <br> <br />
<br />
=== B.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = C): IPv6-only on Server; Client in Dual Stack -behavior: =<br />
<br />
;;<br> =<br />
<br />
=== C.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre> <br />
;<br />
<br />
<br> <br> <br />
<br />
=== C.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = D): IPv6-only on both Client and Server - behavior =<br />
<br />
;;<br> =<br />
<br />
=== D.1): gridftp test ===<br />
<pre>arcls gsi[ftp://meja.arnes.si:2811 ftp://meja.arnes.si:2811]<br />
ERROR: Failed connecting to server meja.arnes.si:2811<br />
ERROR: Failed to obtain stat from ftp: globus_xio: Unable to connect to meja.arnes.si:2811/globus_xio: globus_l_xio_tcp_connect_next failed./globus_xio: \<br />
globus_xio_system_socket_register_connect failed./globus_xio: System error in connect: Network is unreachable/globus_xio: \<br />
A system call failed: Network is unreachable<br />
ERROR: Failed connecting to server meja.arnes.si:2811<br />
ERROR: Failed to obtain listing from ftp: globus_xio: Unable to connect to meja.arnes.si:2811/globus_xio: globus_l_xio_tcp_connect_next failed./globus_xio: \<br />
globus_xio_system_socket_register_connect failed./globus_xio: System error in connect: Network is unreachable/globus_xio: \<br />
A system call failed: Network is unreachable<br />
ERROR: Failed listing files </pre> <br />
;<br />
<br />
<br> <br><br />
<br />
=== D.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br />
<br />
[[Category:Network]]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReportArcCE&diff=40629
IPv6TestReportArcCE
2012-09-17T08:52:10Z
<p>Barbarak: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Tools menubar}} <br />
<br />
<br> <br />
<br />
= A): Dual Stack on both C and S behavior: =<br />
<br />
=== A.1): Submission ===<br />
<pre>arctest -J 3 -c meja.arnes.si<br />
<br />
Test submitted with jobid: gsiftp://meja.arnes.si:2811/jobs/MKoMDm6UjXgnYFU0XooFSKOnABFKDmABFKDmqwHKDmABFKDmIVla6n<br />
</pre> <br />
<br> <br />
<pre>arcls gsiftp://meja.arnes.si:2811<br />
jobs</pre> <br />
;<br />
<br />
= <br> = B): IPv6-only on Client; Server in Dual Stack behavior: =<br />
<br />
;;<br> =<br />
<br />
=== B.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre><br />
<br> <br> <br />
<br />
=== B.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = C): IPv6-only on Server; Client in Dual Stack -behavior: =<br />
<br />
;;<br> =<br />
<br />
=== C.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre> <br />
;<br />
<br />
<br> <br> <br />
<br />
=== C.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = D): IPv6-only on both Client and Server - behavior =<br />
<br />
;;<br> =<br />
<br />
=== D.1): gridftp test ===<br />
<pre>arcls gsi[ftp://meja.arnes.si:2811 ftp://meja.arnes.si:2811]<br />
ERROR: Failed connecting to server meja.arnes.si:2811<br />
ERROR: Failed to obtain stat from ftp: globus_xio: Unable to connect to meja.arnes.si:2811/globus_xio: globus_l_xio_tcp_connect_next failed./globus_xio: globus_xio_system_socket_register_connect failed./globus_xio: System error in connect: Network is unreachable/globus_xio: A system call failed: Network is unreachable<br />
ERROR: Failed connecting to server meja.arnes.si:2811<br />
ERROR: Failed to obtain listing from ftp: globus_xio: Unable to connect to meja.arnes.si:2811/globus_xio: globus_l_xio_tcp_connect_next failed./globus_xio: globus_xio_system_socket_register_connect failed./globus_xio: System error in connect: Network is unreachable/globus_xio: A system call failed: Network is unreachable<br />
ERROR: Failed listing files </pre> <br />
;<br />
<br />
<br> <br><br />
<br />
=== D.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br />
<br />
[[Category:Network]]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReportArcCE&diff=40628
IPv6TestReportArcCE
2012-09-17T08:51:15Z
<p>Barbarak: /* D.1): &lt;description of command&gt; */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Tools menubar}} <br />
<br />
<br> <br />
<br />
= A): Dual Stack on both C and S behavior: =<br />
<br />
=== A.1): Submission ===<br />
<pre>arctest -J 3 -c meja.arnes.si<br />
<br />
Test submitted with jobid: gsiftp://meja.arnes.si:2811/jobs/MKoMDm6UjXgnYFU0XooFSKOnABFKDmABFKDmqwHKDmABFKDmIVla6n<br />
</pre> <br />
<br> <br />
<pre>arcls gsiftp://meja.arnes.si:2811<br />
jobs</pre> <br />
;<br />
<br />
= <br> = B): IPv6-only on Client; Server in Dual Stack behavior: =<br />
<br />
;;<br> =<br />
<br />
=== B.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre><br />
<br> <br> <br />
<br />
=== B.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = C): IPv6-only on Server; Client in Dual Stack -behavior: =<br />
<br />
;;<br> =<br />
<br />
=== C.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre> <br />
;<br />
<br />
<br> <br> <br />
<br />
=== C.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = D): IPv6-only on both Client and Server - behavior =<br />
<br />
;;<br> =<br />
<br />
=== D.1): gridftp test ===<br />
<br />
arcls gsi[ftp://meja.arnes.si:2811 ftp://meja.arnes.si:2811]<br>ERROR: Failed connecting to server meja.arnes.si:2811<br>ERROR: Failed to obtain stat from ftp: globus_xio: Unable to connect to meja.arnes.si:2811/globus_xio: globus_l_xio_tcp_connect_next failed./globus_xio: globus_xio_system_socket_register_connect failed./globus_xio: System error in connect: Network is unreachable/globus_xio: A system call failed: Network is unreachable<br>ERROR: Failed connecting to server meja.arnes.si:2811<br>ERROR: Failed to obtain listing from ftp: globus_xio: Unable to connect to meja.arnes.si:2811/globus_xio: globus_l_xio_tcp_connect_next failed./globus_xio: globus_xio_system_socket_register_connect failed./globus_xio: System error in connect: Network is unreachable/globus_xio: A system call failed: Network is unreachable<br>ERROR: Failed listing files<br />
<br />
;<br />
<br />
<br> <br><br />
<br />
=== D.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br />
<br />
[[Category:Network]]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReportArcCE&diff=40627
IPv6TestReportArcCE
2012-09-17T07:31:14Z
<p>Barbarak: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Tools menubar}} <br />
<br />
<br> <br />
<br />
= A): Dual Stack on both C and S behavior: =<br />
<br />
=== A.1): Submission ===<br />
<pre>arctest -J 3 -c meja.arnes.si<br />
<br />
Test submitted with jobid: gsiftp://meja.arnes.si:2811/jobs/MKoMDm6UjXgnYFU0XooFSKOnABFKDmABFKDmqwHKDmABFKDmIVla6n<br />
</pre> <br />
<br> <br />
<pre>arcls gsiftp://meja.arnes.si:2811<br />
jobs</pre> <br />
;<br />
<br />
= <br> = B): IPv6-only on Client; Server in Dual Stack behavior: =<br />
<br />
;;<br> =<br />
<br />
=== B.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre><br />
<br> <br> <br />
<br />
=== B.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = C): IPv6-only on Server; Client in Dual Stack -behavior: =<br />
<br />
;;<br> =<br />
<br />
=== C.1): Submission ===<br />
<pre wrap="">arctest -J 3 -c meja.arnes.si<br />
Job submission failed, no more possible targets<br />
</pre> <pre wrap="">arcsub -c meja.arnes.si test.xrsl<br />
Job submission failed, no more possible targets</pre> <br />
;<br />
<br />
<br> <br> <br />
<br />
=== C.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
= <br> <br> =<br />
<br />
= = D): IPv6-only on both Client and Server - behavior =<br />
<br />
;;<br> =<br />
<br />
=== D.1): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br> <br />
<br />
=== D.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br />
<br />
[[Category:Network]]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReportArcCE&diff=40626
IPv6TestReportArcCE
2012-09-17T06:22:40Z
<p>Barbarak: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Tools menubar}} <br />
<br />
<br> <br />
<br />
= A): Dual Stack on both C and S behavior: =<br />
<pre>arctest -J 3 -c meja.arnes.si<br />
<br />
Test submitted with jobid: gsiftp://meja.arnes.si:2811/jobs/MKoMDm6UjXgnYFU0XooFSKOnABFKDmABFKDmqwHKDmABFKDmIVla6n<br />
</pre> <br />
<br> <br />
<pre>arcls gsiftp://meja.arnes.si:2811<br />
jobs</pre> <br />
;<br />
<br />
= <br> = B): IPv6-only on Client; Server in Dual Stack behavior: =<br />
<br />
;;<br> =<br />
<br />
=== B.1): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br> <br />
<br />
=== B.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br> <br />
<br />
= C): IPv6-only on Server; Client in Dual Stack -behavior: <br />
<br />
;;<br> =<br />
<br />
=== C.1): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br> <br />
<br />
=== C.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br> <br />
<br />
= D): IPv6-only on both Client and Server - behavior <br />
<br />
;;<br> =<br />
<br />
=== D.1): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br> <br />
<br />
=== D.2): &lt;description of command&gt; ===<br />
<br />
&lt;report here command and outcome&gt; <br />
<br />
;<br />
<br />
<br> <br />
<br />
[[Category:Network]]</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReportArcCE&diff=40584
IPv6TestReportArcCE
2012-09-15T15:47:47Z
<p>Barbarak: /* A): Dual Stack on both C and S (both on DPM server and UI) behavior: */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
[[Category:Network]]<br />
<br />
<br />
= A): Dual Stack on both C and S behavior: =<br />
<br />
=== A.1): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
<br />
<br />
=== A.2): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
= B): IPv6-only on Client; Server in Dual Stack behavior:<dt> =<br />
<br />
<br />
=== B.1): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
<br />
=== B.2): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
<br />
<br />
= C): IPv6-only on Server; Client in Dual Stack -behavior:<dt> =<br />
<br />
<br />
=== C.1): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
<br />
=== C.2): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
<br />
<br />
= D): IPv6-only on both Client and Server - behavior <dt> =<br />
<br />
=== D.1): <description of command> ===<br />
<br />
<report here command and outcome> <dt><br />
<br />
<br />
<br />
=== D.2): <description of command> ===<br />
<br />
<report here command and outcome> <dt></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReports&diff=39798
IPv6TestReports
2012-08-23T06:12:03Z
<p>Barbarak: /* Test Results */</p>
<hr />
<div>= Testing reports =<br />
<br />
We gather here all test reports about UMD Components, spanning different test domains: <dt> <br><br />
<br />
1. Installation : Has it been possible to install the service using only IPv6 ? <dt><br />
2. Configuration: Was configuration possible using only IPv6 ? <dt><br />
3. Dual Stack : Did switching on the IPv6 stack break anything ? <dt><br />
4. Smoke testing : was is possible to start the services properly using only IPv6 ? <dt><br />
5. Basic Functional Tests: Was the expected basic functionality correctly provided ? <dt><br />
6. Has the system been stressed using IPv6-only ? <dt><br />
<br />
<br />
=== Test Results ===<br />
<br />
{| class="wikitable sortable collapsible collapsed" "style="background:#cccc99;color:black;width:80%;" border="1";cellpadding="5";cellspacing="0";align="center"<br />
! Dist !! Fam !! Service !! Exact Ref !! 1) Was IPv6-only install<br> possible? !! 2) Was IPv6-only config<br> possible ? !! 3) Did switching on IPv6 break anything ? !! 4) Smoke: Did all daemons start <br> properly ?!! 5) Basic Functionality provided in IPv6-only ? !! 6) Stress Tested using IPv6 ? !! class="unsortable"| 7) Ref Doc. !! Tester <br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' CE'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| [[Install Log][https://wiki.egi.eu/w/images/2/20/LOGFILE_OF_OPERATIONS_UMD_CREAM_CE_Installation.pdf]]<br />
| M.Reale<br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' WMS'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' WN'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' BDII'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''ARC'''<br />
|''' CE'''<br />
| ''''''<br />
| yes<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| Barbara (Arnes)<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''ARC'''<br />
|''' WN'''<br />
| ''''''<br />
| yes<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| Barbara (Arnes)<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''ARC'''<br />
|''' UI'''<br />
| ''''''<br />
| yes<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
|Barbara (Arnes<br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''UNICORE'''<br />
|''' CE'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
|<br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''UNICORE'''<br />
|''' UI'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
|</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6TestReports&diff=39797
IPv6TestReports
2012-08-23T06:05:10Z
<p>Barbarak: /* Test Results */</p>
<hr />
<div>= Testing reports =<br />
<br />
We gather here all test reports about UMD Components, spanning different test domains: <dt> <br><br />
<br />
1. Installation : Has it been possible to install the service using only IPv6 ? <dt><br />
2. Configuration: Was configuration possible using only IPv6 ? <dt><br />
3. Dual Stack : Did switching on the IPv6 stack break anything ? <dt><br />
4. Smoke testing : was is possible to start the services properly using only IPv6 ? <dt><br />
5. Basic Functional Tests: Was the expected basic functionality correctly provided ? <dt><br />
6. Has the system been stressed using IPv6-only ? <dt><br />
<br />
<br />
=== Test Results ===<br />
<br />
{| class="wikitable sortable collapsible collapsed" "style="background:#cccc99;color:black;width:80%;" border="1";cellpadding="5";cellspacing="0";align="center"<br />
! Dist !! Fam !! Service !! Exact Ref !! 1) Was IPv6-only install<br> possible? !! 2) Was IPv6-only config<br> possible ? !! 3) Did switching on IPv6 break anything ? !! 4) Smoke: Did all daemons start <br> properly ?!! 5) Basic Functionality provided in IPv6-only ? !! 6) Stress Tested using IPv6 ? !! class="unsortable"| 7) Ref Doc. !! Tester <br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' CE'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| [[Install Log][https://wiki.egi.eu/w/images/2/20/LOGFILE_OF_OPERATIONS_UMD_CREAM_CE_Installation.pdf]]<br />
| M.Reale<br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' WMS'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' WN'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''gLite'''<br />
|''' BDII'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''ARC'''<br />
|''' CE'''<br />
| '''yes'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| Barbara (Arnes)<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''ARC'''<br />
|''' WN'''<br />
| ''''''<br />
| yes<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| Barbara (Arnes)<br />
<br />
|<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''ARC'''<br />
|''' UI'''<br />
| ''''''<br />
| yes<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
|Barbara (Arnes<br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''UNICORE'''<br />
|''' CE'''<br />
| '''..'''<br />
| yes<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
|<br />
<br />
|- style="background:white; color:black"<br />
! UMD<br />
| '''UNICORE'''<br />
|''' UI'''<br />
| '''..'''<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
| ..<br />
|</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6Testbed&diff=34276
IPv6Testbed
2012-03-15T13:20:31Z
<p>Barbarak: /* Testbed Resources */</p>
<hr />
<div>= Testbed Goals =<br />
<br />
The Goals of the EGI IPv6 testbed are the following ones:<dt><br />
<br />
1. Allow general purpose testing of UMD components using the IPv6 protocol<dt><br />
2. Enable specific IPv6 test campaigns on selected UMD components or required external dependencies<dt><br />
3. Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security <dt><br />
4. Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community <dt><br />
5. Allow the IPv6 testing of EGI-Inspire JRA1 Operationals Tools components <dt><br />
6. Complement the work done by the HEPiX IPv6 WG, focusing on the middleware <dt><br />
<br />
= Testbed Resources =<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! NGI/Institute<br />
! Node Name<br />
! IPv4 Name<br />
! IPv6 Name<br />
! IPv4 address<br />
! IPv6 address<br />
! Deployed UMD services<br />
! notes<br />
|-<br />
|'''GARR'''<br />
| hepix-ui.dir.garr.it <br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|-<br />
|'''FZU '''<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
| ..<br />
|-<br />
|'''ARNES'''<br />
| meja.arnes.si<br />
| meja.arnes.si<br />
| meja.arnes.si<br />
|109.127.252.39<br />
|2001:1470:8000:403::39<br />
| ARC CE<br />
|<br />
|-<br />
|'''....'''<br />
| ...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6Testbed&diff=34275
IPv6Testbed
2012-03-15T13:19:48Z
<p>Barbarak: /* Testbed Resources */</p>
<hr />
<div>= Testbed Goals =<br />
<br />
The Goals of the EGI IPv6 testbed are the following ones:<dt><br />
<br />
1. Allow general purpose testing of UMD components using the IPv6 protocol<dt><br />
2. Enable specific IPv6 test campaigns on selected UMD components or required external dependencies<dt><br />
3. Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security <dt><br />
4. Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community <dt><br />
5. Allow the IPv6 testing of EGI-Inspire JRA1 Operationals Tools components <dt><br />
6. Complement the work done by the HEPiX IPv6 WG, focusing on the middleware <dt><br />
<br />
= Testbed Resources =<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! NGI/Institute<br />
! Node Name<br />
! IPv4 Name<br />
! IPv6 Name<br />
! IPv4 address<br />
! IPv6 address<br />
! Deployed UMD services<br />
! notes<br />
|-<br />
|'''GARR'''<br />
| hepix-ui.dir.garr.it <br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|-<br />
|'''FZU '''<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
| ..<br />
|-<br />
|'''ARNES'''<br />
| meja.arnes.si<br />
| <br />
| <br />
|<br />
|109.127.252.39<br />
|2001:1470:8000:403::39<br />
|<br />
|-<br />
|'''....'''<br />
| ...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6Testbed&diff=34274
IPv6Testbed
2012-03-15T13:19:26Z
<p>Barbarak: /* Testbed Resources */</p>
<hr />
<div>= Testbed Goals =<br />
<br />
The Goals of the EGI IPv6 testbed are the following ones:<dt><br />
<br />
1. Allow general purpose testing of UMD components using the IPv6 protocol<dt><br />
2. Enable specific IPv6 test campaigns on selected UMD components or required external dependencies<dt><br />
3. Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security <dt><br />
4. Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community <dt><br />
5. Allow the IPv6 testing of EGI-Inspire JRA1 Operationals Tools components <dt><br />
6. Complement the work done by the HEPiX IPv6 WG, focusing on the middleware <dt><br />
<br />
= Testbed Resources =<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! NGI/Institute<br />
! Node Name<br />
! IPv4 Name<br />
! IPv6 Name<br />
! IPv4 address<br />
! IPv6 address<br />
! Deployed UMD services<br />
! notes<br />
|-<br />
|'''GARR'''<br />
| hepix-ui.dir.garr.it <br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|-<br />
|'''FZU '''<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
| ..<br />
|-<br />
|'''ARNES'''<br />
| meja.arnes.si<br />
| 109.127.252.39<br />
| 2001:1470:8000:403::39<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|'''....'''<br />
| ...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6Testbed&diff=34273
IPv6Testbed
2012-03-15T13:17:59Z
<p>Barbarak: /* Testbed Resources */</p>
<hr />
<div>= Testbed Goals =<br />
<br />
The Goals of the EGI IPv6 testbed are the following ones:<dt><br />
<br />
1. Allow general purpose testing of UMD components using the IPv6 protocol<dt><br />
2. Enable specific IPv6 test campaigns on selected UMD components or required external dependencies<dt><br />
3. Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security <dt><br />
4. Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community <dt><br />
5. Allow the IPv6 testing of EGI-Inspire JRA1 Operationals Tools components <dt><br />
6. Complement the work done by the HEPiX IPv6 WG, focusing on the middleware <dt><br />
<br />
= Testbed Resources =<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! NGI/Institute<br />
! Node Name<br />
! IPv4 Name<br />
! IPv6 Name<br />
! IPv4 address<br />
! IPv6 address<br />
! Deployed UMD services<br />
! notes<br />
|-<br />
|'''GARR'''<br />
| hepix-ui.dir.garr.it <br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|-<br />
|'''FZU '''<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
| ..<br />
|-<br />
|'''ARNES'''<br />
| meja.arnes.si<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|'''....'''<br />
| ...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-ARNES_Metrics&diff=27093
EGI-InSPIRE:Slovenia-ARNES Metrics
2011-11-04T15:26:56Z
<p>Barbarak: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months. <br />
<br />
'''Note: Starting from Q6 NGI metrics must be reported using the metrics portal.''' <br />
<br />
<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Metric Name/<br>Quarters <br />
! scope="col" | QR1<br />
! QR2<br />
! QR3<br />
! QR4<br />
! QR5<br />
! QR6<br />
! QR7<br />
! QR8<br />
! QR9<br />
! QR10<br />
! QR11<br />
! QR12<br />
! QR13<br />
! QR14<br />
! QR15<br />
! QR16<br />
|-<br />
! scope="row" | M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 26,616,196<br />
| 23,490,448<br />
| 33,293,048<br />
| 24,202,420<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.2, Total number of production logical cpus <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1390<br />
| 1408<br />
| 1408<br />
| 1408<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 13622<br />
| 13798<br />
| 13798<br />
| 13798<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.4, Installed Disk Capacity (PB) per NGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.5, Installed Tape Capacity (PB) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.1, Number of production HPC clusters <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.2, Number of production sites supporting MPI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.ServiceValidation.1, Total number of staged rollout components <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 4<br />
| 4<br />
| 4<br />
| 4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-ARNES_Metrics&diff=27092
EGI-InSPIRE:Slovenia-ARNES Metrics
2011-11-04T15:20:45Z
<p>Barbarak: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months. <br />
<br />
'''Note: Starting from Q6 NGI metrics must be reported using the metrics portal.''' <br />
<br />
<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Metric Name/<br>Quarters <br />
! scope="col" | QR1<br />
! QR2<br />
! QR3<br />
! QR4<br />
! QR5<br />
! QR6<br />
! QR7<br />
! QR8<br />
! QR9<br />
! QR10<br />
! QR11<br />
! QR12<br />
! QR13<br />
! QR14<br />
! QR15<br />
! QR16<br />
|-<br />
! scope="row" | M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 26,616,196<br />
| 23,490,448<br />
| 33,293,048<br />
| 24,202,420<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.2, Total number of production logical cpus <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1390<br />
| 1408<br />
| 1408<br />
| 1408<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 13622<br />
| 13798<br />
| &lt;Q5_value&gt;<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.4, Installed Disk Capacity (PB) per NGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.5, Installed Tape Capacity (PB) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.1, Number of production HPC clusters <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.2, Number of production sites supporting MPI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.ServiceValidation.1, Total number of staged rollout components <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 4<br />
| 4<br />
| 4<br />
| 4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-ARNES_Metrics&diff=27091
EGI-InSPIRE:Slovenia-ARNES Metrics
2011-11-04T15:16:48Z
<p>Barbarak: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months. <br />
<br />
'''Note: Starting from Q6 NGI metrics must be reported using the metrics portal.''' <br />
<br />
<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Metric Name/<br>Quarters <br />
! scope="col" | QR1<br />
! QR2<br />
! QR3<br />
! QR4<br />
! QR5<br />
! QR6<br />
! QR7<br />
! QR8<br />
! QR9<br />
! QR10<br />
! QR11<br />
! QR12<br />
! QR13<br />
! QR14<br />
! QR15<br />
! QR16<br />
|-<br />
! scope="row" | M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 26,616,196<br />
| 23,490,448<br />
| &lt;Q5_value&gt;<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.2, Total number of production logical cpus <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1390<br />
| 1408<br />
| 1408<br />
| 1408<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 13622<br />
| 13798<br />
| &lt;Q5_value&gt;<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.4, Installed Disk Capacity (PB) per NGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.5, Installed Tape Capacity (PB) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.1, Number of production HPC clusters <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.2, Number of production sites supporting MPI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.ServiceValidation.1, Total number of staged rollout components <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 4<br />
| 4<br />
| 4<br />
| 4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-ARNES_Metrics&diff=27090
EGI-InSPIRE:Slovenia-ARNES Metrics
2011-11-04T15:15:49Z
<p>Barbarak: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months. <br />
<br />
'''Note: Starting from Q6 NGI metrics must be reported using the metrics portal.''' <br />
<br />
<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Metric Name/<br>Quarters <br />
! scope="col" | QR1<br />
! QR2<br />
! QR3<br />
! QR4<br />
! QR5<br />
! QR6<br />
! QR7<br />
! QR8<br />
! QR9<br />
! QR10<br />
! QR11<br />
! QR12<br />
! QR13<br />
! QR14<br />
! QR15<br />
! QR16<br />
|-<br />
! scope="row" | M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 26,616,196<br />
| 23,490,448<br />
| &lt;Q5_value&gt;<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
|-<br />
! scope="row" | M.SA1.Size.2, Total number of production logical cpus <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1390<br />
| 1408<br />
| 1408<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 13622<br />
| 13798<br />
| &lt;Q5_value&gt;<br />
| &lt;Q6_value&gt;<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.4, Installed Disk Capacity (PB) per NGI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| 0.222<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Size.5, Installed Tape Capacity (PB) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.1, Number of production HPC clusters <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.2, Number of production sites supporting MPI <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| 1548.4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC) <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 0<br />
| 0<br />
| 0<br />
| 0<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.ServiceValidation.1, Total number of staged rollout components <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 4<br />
| 4<br />
| 4<br />
| 4<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|-<br />
! scope="row" | M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
| &lt;Q1_value&gt;<br />
| &lt;Q2_value&gt;<br />
| 2<br />
| 2<br />
| 2<br />
| 2<br />
| &lt;Q7_value&gt;<br />
| &lt;Q8_value&gt;<br />
| &lt;Q9_value&gt;<br />
| &lt;Q10_value&gt;<br />
| &lt;Q11_value&gt;<br />
| &lt;Q12_value&gt;<br />
| &lt;Q13_value&gt;<br />
| &lt;Q14_value&gt;<br />
| &lt;Q15_value&gt;<br />
| &lt;Q16_value&gt;<br />
| <br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6&diff=26546
IPv6
2011-10-26T09:28:11Z
<p>Barbarak: </p>
<hr />
<div>'''EGI IPv6 related activities and survey<br />
'''<br />
<br />
[[File:Ipv6-logo_transparant.png|options|caption]]<br />
<br />
<br />
<h3>'''IPv6 Tools and Links / Guides '''</h3><br />
<UL><br />
<LI>[https://twiki.cern.ch/twiki/bin/view/EGEE/IPv6FollowUp EGEE III SA2 IPv6 Follow Up pages] <br></li><br />
<LI>[https://w3.hepix.org/ipv6-bis/doku.php HEPiX IPv6 Working Group]<br></li><br />
</UL><br />
<h3>'''IPv6 Survey'''</h3><br />
<br />
https://wiki.egi.eu/wiki/File:IPv6_Questionnaire_for_NGIs-v1.0.pdf<br />
<br />
<h3>'''IPv6 Survey Result (23 NGIs answered as of Sept 21, 2011)'''</h3><br />
<br />
<br />
{| style="background:#cccc99;color:black;width:80%;" border="1";cellpadding="5";cellspacing="0";align="center"<br />
<br />
! # !!Short!!Country!!NGI!! 1) Any <br>IPv6-only site? !! 2) IPv6 sites <br> today ? !! 3) IPv6 sites <br> planned ?!! 4) How many sites <hr> with IPv6 connect? !! 5)NREN IPv6? !! 6)Motivation<br> for IPv6 !! 7)Tutorials <br>IPv6 ? !! 8)Tutorials IPv6 <br> security ? !! 9) Testbed? !! 10) Task <br>Force? !! other info<br>or comments <br />
|- style="background:white; color:black"<br />
! 1.<br />
| AL<br />
| Albania<br />
| ALBGRID<br />
| <br />
|...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|...<br />
|- style="background:white; color:black"<br />
! 2.<br />
| AM<br />
| Armenia<br />
| ANGI<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 3.<br />
| AT <br />
| ''Austria''<br />
| AustrianGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 4.<br />
| BY<br />
| Belarus<br />
| BNGI<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 5.<br />
| BE<br />
| Belgium<br />
| BEgrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 6.<br />
| '''BA'''<br />
| '''Bosnia-Herzegovina'''<br />
| '''NGI_BA'''<br />
| YES<br />
| NO<br />
| YES, NEXT 6 MONTHS (ROUGHLY)<br />
| 2<br />
| YES/NO (2 RENs)<br />
| Lack of IPv4 addresses<br />
| YES<br />
| YES<br />
| YES (IN 6 MOTHS TIME)<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 7.<br />
| '''BG'''<br />
| '''Bulgaria'''<br />
| '''BGI'''<br />
| NO<br />
| NO<br />
| YES,at least 3 months<br />
| 5<br />
| YES<br />
| We have enough IPv4 addresses for now , but Ipv6 is a newer and much better networking protocol, it is the future.<br />
| YES<br />
| YES<br />
| YES, but with limited manpower<br />
| NO<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 8.<br />
| '''HR'''<br />
| '''Croatia'''<br />
| '''CRO NGI'''<br />
| NO<br />
| NO<br />
| NO<br />
| All<br />
| YES<br />
| To take advantage of IPv6 protocol specific fetures <br>To promote IPv6 services<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|<br />
|- style="background:white; color:black"<br />
! 9.<br />
| '''CY'''<br />
| '''Cyprus'''<br />
| '''CGI'''<br />
| NO<br />
| NO<br />
| NO<br />
| 0<br />
| NO<br />
|<br />
| YES<br />
| NO<br />
| NO<br />
| NO<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 10.<br />
| '''CZ'''<br />
|''' Czech Republic'''<br />
| '''MetaCentrum'''<br />
| NO<br />
| NO<br />
| YES <br>- FZU (Institute of Physics of Academy of Sciences) have a project to try IPv6 for its EGI site, it just started. <br><br />
-CERIT-SC at Masaryk University is interested to provide access to its resources provided the deployed services will become IPv6 ready.<br />
| All<br />
| YES<br />
| Lack of IPv4 addresses. For providing resources as a virtual clusters (many virtual nodes), but in “classic” deployment too.<br />
| Depends on context – not useful without particular deployment plans<br />
| Depends on context – not useful without particular deployment plans<br />
| YES, FZU site<br />
| NO, it can change over time. FZU is involved in the HEPIX IPv6 WG and interested in EGI-wide cooperation.<br />
| <br />
<br />
|- style="background:white; color:black"<br />
! 11.<br />
| DK<br />
| ''Denmark''<br />
| <TBA><br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 12.<br />
| '''FI'''<br />
| '''Finland'''<br />
| '''CSC/Funet'''<br />
| NO<br />
| YES<br />
| YES, where available<br />
| 1 <br />
| YES <br />
| Testing and futureproofing <br />
| YES <br />
| YES<br />
| YES <br />
| NO <br />
| <br />
|- style="background:#f0f0f0; color:black"<br />
! 13.<br />
| '''FR'''<br />
|''' France'''<br />
| '''IDG/FranceGrilles'''<br />
| NO<br />
| YES <br />
| YES<br />
| > 1 (in evaluation)<br />
| YES<br />
| TESTING AND DEPLOYING (collaboration with sites without IPv4 adresses)<br />
| YES<br />
| NO<br />
| YES (out of NGI)<br />
| YES<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 14.<br />
| '''GE'''<br />
|''' Georgia'''<br />
| '''GEO-GRID'''<br />
| NO<br />
| NO<br />
| NO (Not Yet)<br />
| 0 <br />
| NO<br />
| NO<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 15.<br />
| '''DE'''<br />
| '''Germany'''<br />
| '''NGI-DE'''<br />
| NO : - currently we no information about a site which will run IPv6 only<br />
| YES<br />
| 3-10 (1 year) <br> '''-deploying some services over IPv4/6 dualstack''' (probably 10 sites within the next year) '''--running a Grid center over ipv6.''' (this will be a very small number, may be 3 sites)<br />
| View sites e.g Desy / LMU are running ipv6 (but not necessarily at their Grid (Tier-2) installation )<br />
| 2 with “native” IPv6 : DFN and Belwue<br />
| - Connectivity to collaborating sites reachable only via IPv6<br />
- offer services via IPv6<br />
- Our organization decided do deploy IPv6, to be prepared for future. IPv6 definitively will come on the global internet. Step by step KIT will rollout IPv6 on all available services.<br />
| YES, but Grid site and Middelware specific, since there are already lots of training and tutorials available (from NRENs, Geant/Dante, Ripe,… and commercial companies)<br />
| YES, but Grid site and Middelware specific, since there are already lots of training and tutorials available (from NRENs, Geant/Dante, Ripe,… and commercial companies)<br />
| YES<br />
| NO - KIT is involved in HEPIX IPv6 WG<br />
- and we would be a Grid middleware test side<br />
- everything beyond would be over our capacity we are able to provide <br />
|<br />
<br />
<br />
|- style="background:#f0f0f0; color:black"<br />
! 16.<br />
| '''GR'''<br />
| '''Greece'''<br />
| '''GRNET/Hellasgrid'''<br />
| NO<br />
| NO<br />
| NO<br />
| NO<br />
| YES<br />
|<br />
| NO<br />
| NO<br />
| YES<br />
| NO<br />
|<br />
<br />
|- style="background:white; color:black"<br />
! 17.<br />
| HU<br />
| Hungary<br />
| MGKK<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 18.<br />
| '''IE'''<br />
| '''Ireland'''<br />
| '''GridIreland'''<br />
| NO<br />
| YES - Not a Grid Site level, but at Institute level. 5 of our 6 grid connected sites support IPv6<br />
| NO<br />
| 5<br />
| YES<br />
| Technological advantages<br />
| YES<br />
| YES – In particular Ipv6 firewalling<br />
| NO<br />
| NO – Due to other workload commitments<br />
| <br />
|- style="background:white; color:black"<br />
! 19.<br />
| IL<br />
| Israel<br />
| ISRAGRID<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 20.<br />
| '''IT'''<br />
| '''Italy'''<br />
| '''IGI'''<br />
| NO<br />
| YES <br />
| NO<br />
| All<br />
| YES<br />
| Experiment m/w using IPv6<br />
| YES<br />
| YES<br />
| YES<br />
| YES<br />
|...<br />
|- style="background:#cccc99;color:black;width:80%;" border="1";cellpadding="5";cellspacing="0";align="center"<br />
<br />
! # !!Short!!Country!!NGI!! 1) Any <br>IPv6-only site? !! 2) IPv6 sites <br> today ? !! 3) IPv6 sites <br> planned ?!! 4) How many sites <hr> with IPv6 connect? !! 5)NREN IPv6? !! 6)Motivation<br> for IPv6 !! 7)Tutorials <br>IPv6 ? !! 8)Tutorials IPv6 <br> security ? !! 9) Testbed? !! 10) Task <br>Force? !! other info<br>or comments <br />
|- style="background:white; color:black"<br />
<br />
! 21.<br />
| LV<br />
| Latvia<br />
| LatvianGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 22.<br />
| LT<br />
| Lithuania<br />
| LitGRID<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 23.<br />
| MK<br />
| FYR Macedonia<br />
| MARGI<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 24.<br />
| '''MD'''<br />
| '''Moldova'''<br />
| '''MD-Grid'''<br />
| NO<br />
| NO<br />
| NO<br />
| None<br />
| NO<br />
| Lack of IPv4 addresses, improved security<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
|- style="background:white; color:black"<br />
! 25.<br />
| '''ME'''<br />
| '''Montenegro'''<br />
| '''MREN'''<br />
| NO<br />
| NO<br />
| YES, next 12 months<br />
| 0<br />
| YES<br />
| Lack of IPv4 addresses<br />
| YES <br />
| YES<br />
| YES (in 18 months time)<br />
| NO<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 26.<br />
| '''NL'''<br />
| '''The Netherlands'''<br />
| '''BIG Grid'''<br />
|NO<br />
|NO<br />
|NO<br />
|ALL<br />
|YES<br />
|Be ready to conect to ipv6-only sites<br />
|YES<br />
|YES<br />
|YES<br />
|MAYBE<br />
|...<br />
<br />
<br />
|- style="background:white; color:black"<br />
! 27.<br />
| NO<br />
| Norway<br />
| NorGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 28.<br />
| '''PL'''<br />
| '''Poland'''<br />
|''' PL-Grid'''<br />
| NO<br />
| NO<br />
| Sites only have very vague plans to implement IPv6 in the future. No timescale can be given. Sites rather do not need to have IPv6 yet, but will implement it if needed or if it will be a general recommendation from EGI.<br />
| All (6)<br />
| Yes<br />
| n/a<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
| <br />
|- style="background:white; color:black"<br />
! 29.<br />
| '''PT'''<br />
| '''Portugal'''<br />
| '''NGI-PT'''<br />
| NO<br />
| NO<br />
| NO<br />
| 0<br />
| YES<br />
| <br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 30.<br />
| '''RO'''<br />
| '''Romania'''<br />
| '''RoGrid'''<br />
| NO <br />
| YES<br />
| NO<br />
| 2 (UVT and UPB)<br />
| YES<br />
| <br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 31.<br />
| RU<br />
| ''Russian Federation''<br />
| <TBA><br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 32.<br />
| '''RS'''<br />
|''' Serbia'''<br />
| '''AEGIS'''<br />
| NO<br />
| NO<br />
| Yes, at least one site, in 12 months.<br />
| All<br />
| YES<br />
|<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 33.<br />
| '''SK'''<br />
| '''Slovakia'''<br />
| '''SlovakGrid'''<br />
| NO<br />
| NO<br />
| NO<br />
| 0<br />
| NO<br />
| <br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 34.<br />
| SI<br />
| Slovenia<br />
| SLING<br />
| NO<br />
| NO<br />
| YES<br />
| ALL<br />
| YES<br />
| Lack of IPv4 addresses<br />
| YES<br />
| YES<br />
| YES<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 35.<br />
| '''ES'''<br />
|''' Spain'''<br />
| '''RedIRIS'''<br />
| NO <br />
| YES<br />
| YES, in short term<br />
| All<br />
| YES<br />
| IPv6 promotion and deployment; Test IPv6 capabilities<br />
| YES<br />
| YES<br />
| We have to check<br />
| We have to check<br />
|...<br />
|- style="background:white; color:black"<br />
! 36.<br />
| SW<br />
| Sweeden<br />
| SweGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 37.<br />
| '''CH'''<br />
| '''Switzerland'''<br />
| '''SwiNG'''<br />
| NO<br />
| NO<br />
| NO<br />
| CSCS-LCG2 could switch IPv6 on if WLCG would ask for it. T3_CH_PSI should get ready by mid-2012 but there's no decision about switching it on yet.<br />
| YES<br />
| Motivation is mostly to stay compatible with the current developments, e.g. customers wanting to interact with PSI over IPv6.<br />
| YES<br />
| YES<br />
| YES (Only with very little manpower contribution)<br />
| NO<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 38.<br />
| '''TR'''<br />
| '''Turkey'''<br />
| '''TR-Grid'''<br />
| NO<br />
| NO<br />
| NO<br />
| All<br />
| YES<br />
| Utilizing functional properties that IPV6 protocol provides<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|<br />
|- style="background:white; color:black"<br />
! 39.<br />
| UK<br />
| United Kingdom<br />
| NGS<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 40.<br />
| EIRO<br />
| CERN<br />
| CERN<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 41.<br />
| EIRO<br />
| EMBL<br />
| EMBL<br />
|<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 42.<br />
| '''TW'''<br />
| '''Taiwan'''<br />
| '''ASGC'''<br />
| NO<br />
| YES<br />
| NO <br />
| NO <br />
| YES<br />
| The collaboration project is ready and <br>required to support IPv6 services. <br />
| YES, at tech.level <br> On IPv6 deployment, won't help.<br />
| YES, at tech.level<br />
| YES<br />
| NO<br />
| <br />
<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=IPv6&diff=26541
IPv6
2011-10-26T09:14:33Z
<p>Barbarak: </p>
<hr />
<div>'''EGI IPv6 related activities and survey<br />
'''<br />
<br />
[[File:Ipv6-logo_transparant.png|options|caption]]<br />
<br />
<br />
<h3>'''IPv6 Tools and Links / Guides '''</h3><br />
<UL><br />
<LI>[https://twiki.cern.ch/twiki/bin/view/EGEE/IPv6FollowUp EGEE III SA2 IPv6 Follow Up pages] <br></li><br />
<LI>[https://w3.hepix.org/ipv6-bis/doku.php HEPiX IPv6 Working Group]<br></li><br />
</UL><br />
<h3>'''IPv6 Survey'''</h3><br />
<br />
https://wiki.egi.eu/wiki/File:IPv6_Questionnaire_for_NGIs-v1.0.pdf<br />
<br />
<h3>'''IPv6 Survey Result (23 NGIs answered as of Sept 21, 2011)'''</h3><br />
<br />
<br />
{| style="background:#cccc99;color:black;width:80%;" border="1";cellpadding="5";cellspacing="0";align="center"<br />
<br />
! # !!Short!!Country!!NGI!! 1) Any <br>IPv6-only site? !! 2) IPv6 sites <br> today ? !! 3) IPv6 sites <br> planned ?!! 4) How many sites <hr> with IPv6 connect? !! 5)NREN IPv6? !! 6)Motivation<br> for IPv6 !! 7)Tutorials <br>IPv6 ? !! 8)Tutorials IPv6 <br> security ? !! 9) Testbed? !! 10) Task <br>Force? !! other info<br>or comments <br />
|- style="background:white; color:black"<br />
! 1.<br />
| AL<br />
| Albania<br />
| ALBGRID<br />
| <br />
|...<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|...<br />
|- style="background:white; color:black"<br />
! 2.<br />
| AM<br />
| Armenia<br />
| ANGI<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 3.<br />
| AT <br />
| ''Austria''<br />
| AustrianGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 4.<br />
| BY<br />
| Belarus<br />
| BNGI<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 5.<br />
| BE<br />
| Belgium<br />
| BEgrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 6.<br />
| '''BA'''<br />
| '''Bosnia-Herzegovina'''<br />
| '''NGI_BA'''<br />
| YES<br />
| NO<br />
| YES, NEXT 6 MONTHS (ROUGHLY)<br />
| 2<br />
| YES/NO (2 RENs)<br />
| Lack of IPv4 addresses<br />
| YES<br />
| YES<br />
| YES (IN 6 MOTHS TIME)<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 7.<br />
| '''BG'''<br />
| '''Bulgaria'''<br />
| '''BGI'''<br />
| NO<br />
| NO<br />
| YES,at least 3 months<br />
| 5<br />
| YES<br />
| We have enough IPv4 addresses for now , but Ipv6 is a newer and much better networking protocol, it is the future.<br />
| YES<br />
| YES<br />
| YES, but with limited manpower<br />
| NO<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 8.<br />
| '''HR'''<br />
| '''Croatia'''<br />
| '''CRO NGI'''<br />
| NO<br />
| NO<br />
| NO<br />
| All<br />
| YES<br />
| To take advantage of IPv6 protocol specific fetures <br>To promote IPv6 services<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|<br />
|- style="background:white; color:black"<br />
! 9.<br />
| '''CY'''<br />
| '''Cyprus'''<br />
| '''CGI'''<br />
| NO<br />
| NO<br />
| NO<br />
| 0<br />
| NO<br />
|<br />
| YES<br />
| NO<br />
| NO<br />
| NO<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 10.<br />
| '''CZ'''<br />
|''' Czech Republic'''<br />
| '''MetaCentrum'''<br />
| NO<br />
| NO<br />
| YES <br>- FZU (Institute of Physics of Academy of Sciences) have a project to try IPv6 for its EGI site, it just started. <br><br />
-CERIT-SC at Masaryk University is interested to provide access to its resources provided the deployed services will become IPv6 ready.<br />
| All<br />
| YES<br />
| Lack of IPv4 addresses. For providing resources as a virtual clusters (many virtual nodes), but in “classic” deployment too.<br />
| Depends on context – not useful without particular deployment plans<br />
| Depends on context – not useful without particular deployment plans<br />
| YES, FZU site<br />
| NO, it can change over time. FZU is involved in the HEPIX IPv6 WG and interested in EGI-wide cooperation.<br />
| <br />
<br />
|- style="background:white; color:black"<br />
! 11.<br />
| DK<br />
| ''Denmark''<br />
| <TBA><br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 12.<br />
| '''FI'''<br />
| '''Finland'''<br />
| '''CSC/Funet'''<br />
| NO<br />
| YES<br />
| YES, where available<br />
| 1 <br />
| YES <br />
| Testing and futureproofing <br />
| YES <br />
| YES<br />
| YES <br />
| NO <br />
| <br />
|- style="background:#f0f0f0; color:black"<br />
! 13.<br />
| '''FR'''<br />
|''' France'''<br />
| '''IDG/FranceGrilles'''<br />
| NO<br />
| YES <br />
| YES<br />
| > 1 (in evaluation)<br />
| YES<br />
| TESTING AND DEPLOYING (collaboration with sites without IPv4 adresses)<br />
| YES<br />
| NO<br />
| YES (out of NGI)<br />
| YES<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 14.<br />
| '''GE'''<br />
|''' Georgia'''<br />
| '''GEO-GRID'''<br />
| NO<br />
| NO<br />
| NO (Not Yet)<br />
| 0 <br />
| NO<br />
| NO<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 15.<br />
| '''DE'''<br />
| '''Germany'''<br />
| '''NGI-DE'''<br />
| NO : - currently we no information about a site which will run IPv6 only<br />
| YES<br />
| 3-10 (1 year) <br> '''-deploying some services over IPv4/6 dualstack''' (probably 10 sites within the next year) '''--running a Grid center over ipv6.''' (this will be a very small number, may be 3 sites)<br />
| View sites e.g Desy / LMU are running ipv6 (but not necessarily at their Grid (Tier-2) installation )<br />
| 2 with “native” IPv6 : DFN and Belwue<br />
| - Connectivity to collaborating sites reachable only via IPv6<br />
- offer services via IPv6<br />
- Our organization decided do deploy IPv6, to be prepared for future. IPv6 definitively will come on the global internet. Step by step KIT will rollout IPv6 on all available services.<br />
| YES, but Grid site and Middelware specific, since there are already lots of training and tutorials available (from NRENs, Geant/Dante, Ripe,… and commercial companies)<br />
| YES, but Grid site and Middelware specific, since there are already lots of training and tutorials available (from NRENs, Geant/Dante, Ripe,… and commercial companies)<br />
| YES<br />
| NO - KIT is involved in HEPIX IPv6 WG<br />
- and we would be a Grid middleware test side<br />
- everything beyond would be over our capacity we are able to provide <br />
|<br />
<br />
<br />
|- style="background:#f0f0f0; color:black"<br />
! 16.<br />
| '''GR'''<br />
| '''Greece'''<br />
| '''GRNET/Hellasgrid'''<br />
| NO<br />
| NO<br />
| NO<br />
| NO<br />
| YES<br />
|<br />
| NO<br />
| NO<br />
| YES<br />
| NO<br />
|<br />
<br />
|- style="background:white; color:black"<br />
! 17.<br />
| HU<br />
| Hungary<br />
| MGKK<br />
| <br />
|<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 18.<br />
| '''IE'''<br />
| '''Ireland'''<br />
| '''GridIreland'''<br />
| NO<br />
| YES - Not a Grid Site level, but at Institute level. 5 of our 6 grid connected sites support IPv6<br />
| NO<br />
| 5<br />
| YES<br />
| Technological advantages<br />
| YES<br />
| YES – In particular Ipv6 firewalling<br />
| NO<br />
| NO – Due to other workload commitments<br />
| <br />
|- style="background:white; color:black"<br />
! 19.<br />
| IL<br />
| Israel<br />
| ISRAGRID<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 20.<br />
| '''IT'''<br />
| '''Italy'''<br />
| '''IGI'''<br />
| NO<br />
| YES <br />
| NO<br />
| All<br />
| YES<br />
| Experiment m/w using IPv6<br />
| YES<br />
| YES<br />
| YES<br />
| YES<br />
|...<br />
|- style="background:#cccc99;color:black;width:80%;" border="1";cellpadding="5";cellspacing="0";align="center"<br />
<br />
! # !!Short!!Country!!NGI!! 1) Any <br>IPv6-only site? !! 2) IPv6 sites <br> today ? !! 3) IPv6 sites <br> planned ?!! 4) How many sites <hr> with IPv6 connect? !! 5)NREN IPv6? !! 6)Motivation<br> for IPv6 !! 7)Tutorials <br>IPv6 ? !! 8)Tutorials IPv6 <br> security ? !! 9) Testbed? !! 10) Task <br>Force? !! other info<br>or comments <br />
|- style="background:white; color:black"<br />
<br />
! 21.<br />
| LV<br />
| Latvia<br />
| LatvianGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 22.<br />
| LT<br />
| Lithuania<br />
| LitGRID<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 23.<br />
| MK<br />
| FYR Macedonia<br />
| MARGI<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 24.<br />
| '''MD'''<br />
| '''Moldova'''<br />
| '''MD-Grid'''<br />
| NO<br />
| NO<br />
| NO<br />
| None<br />
| NO<br />
| Lack of IPv4 addresses, improved security<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
|- style="background:white; color:black"<br />
! 25.<br />
| '''ME'''<br />
| '''Montenegro'''<br />
| '''MREN'''<br />
| NO<br />
| NO<br />
| YES, next 12 months<br />
| 0<br />
| YES<br />
| Lack of IPv4 addresses<br />
| YES <br />
| YES<br />
| YES (in 18 months time)<br />
| NO<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 26.<br />
| '''NL'''<br />
| '''The Netherlands'''<br />
| '''BIG Grid'''<br />
|NO<br />
|NO<br />
|NO<br />
|ALL<br />
|YES<br />
|Be ready to conect to ipv6-only sites<br />
|YES<br />
|YES<br />
|YES<br />
|MAYBE<br />
|...<br />
<br />
<br />
|- style="background:white; color:black"<br />
! 27.<br />
| NO<br />
| Norway<br />
| NorGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 28.<br />
| '''PL'''<br />
| '''Poland'''<br />
|''' PL-Grid'''<br />
| NO<br />
| NO<br />
| Sites only have very vague plans to implement IPv6 in the future. No timescale can be given. Sites rather do not need to have IPv6 yet, but will implement it if needed or if it will be a general recommendation from EGI.<br />
| All (6)<br />
| Yes<br />
| n/a<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
| <br />
|- style="background:white; color:black"<br />
! 29.<br />
| '''PT'''<br />
| '''Portugal'''<br />
| '''NGI-PT'''<br />
| NO<br />
| NO<br />
| NO<br />
| 0<br />
| YES<br />
| <br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 30.<br />
| '''RO'''<br />
| '''Romania'''<br />
| '''RoGrid'''<br />
| NO <br />
| YES<br />
| NO<br />
| 2 (UVT and UPB)<br />
| YES<br />
| <br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 31.<br />
| RU<br />
| ''Russian Federation''<br />
| <TBA><br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 32.<br />
| '''RS'''<br />
|''' Serbia'''<br />
| '''AEGIS'''<br />
| NO<br />
| NO<br />
| Yes, at least one site, in 12 months.<br />
| All<br />
| YES<br />
|<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 33.<br />
| '''SK'''<br />
| '''Slovakia'''<br />
| '''SlovakGrid'''<br />
| NO<br />
| NO<br />
| NO<br />
| 0<br />
| NO<br />
| <br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 34.<br />
| SI<br />
| Slovenia<br />
| SLING<br />
| NO<br />
| NO<br />
| YES<br />
| ALL<br />
| YES<br />
| Testing<br />
| YES<br />
| YES<br />
| YES<br />
| NO<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 35.<br />
| '''ES'''<br />
|''' Spain'''<br />
| '''RedIRIS'''<br />
| NO <br />
| YES<br />
| YES, in short term<br />
| All<br />
| YES<br />
| IPv6 promotion and deployment; Test IPv6 capabilities<br />
| YES<br />
| YES<br />
| We have to check<br />
| We have to check<br />
|...<br />
|- style="background:white; color:black"<br />
! 36.<br />
| SW<br />
| Sweeden<br />
| SweGrid<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
<br />
|- style="background:white; color:black"<br />
! 37.<br />
| '''CH'''<br />
| '''Switzerland'''<br />
| '''SwiNG'''<br />
| NO<br />
| NO<br />
| NO<br />
| CSCS-LCG2 could switch IPv6 on if WLCG would ask for it. T3_CH_PSI should get ready by mid-2012 but there's no decision about switching it on yet.<br />
| YES<br />
| Motivation is mostly to stay compatible with the current developments, e.g. customers wanting to interact with PSI over IPv6.<br />
| YES<br />
| YES<br />
| YES (Only with very little manpower contribution)<br />
| NO<br />
|<br />
|- style="background:#f0f0f0; color:black"<br />
! 38.<br />
| '''TR'''<br />
| '''Turkey'''<br />
| '''TR-Grid'''<br />
| NO<br />
| NO<br />
| NO<br />
| All<br />
| YES<br />
| Utilizing functional properties that IPV6 protocol provides<br />
| YES<br />
| YES<br />
| NO<br />
| NO<br />
|<br />
|- style="background:white; color:black"<br />
! 39.<br />
| UK<br />
| United Kingdom<br />
| NGS<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 40.<br />
| EIRO<br />
| CERN<br />
| CERN<br />
| <br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:white; color:black"<br />
! 41.<br />
| EIRO<br />
| EMBL<br />
| EMBL<br />
|<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|...<br />
|- style="background:#f0f0f0; color:black"<br />
! 42.<br />
| '''TW'''<br />
| '''Taiwan'''<br />
| '''ASGC'''<br />
| NO<br />
| YES<br />
| NO <br />
| NO <br />
| YES<br />
| The collaboration project is ready and <br>required to support IPv6 services. <br />
| YES, at tech.level <br> On IPv6 deployment, won't help.<br />
| YES, at tech.level<br />
| YES<br />
| NO<br />
| <br />
<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-ARNES_Metrics&diff=22959
EGI-InSPIRE:Slovenia-ARNES Metrics
2011-08-05T06:04:02Z
<p>Barbarak: </p>
<hr />
<div>NGI Metrics. Values reported need to be aggregated during the reference three months.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Metric Name/<br>Quarters<br />
!scope="col"| QR1||QR2||QR3||QR4||QR5||QR6||QR7||QR8||QR9||QR10||QR11||QR12||QR13||QR14||QR15||QR16<br />
|-<br />
!scope="row"|M.SA1.Usage.2, Normalized Elapsed time to a reference value of HEPSPEC06 (HEPSPEC06-hours) <br />
|<Q1_value>||<Q2_value>||26,616,196||23,490,448||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.1, Total number of production resource centers that are part of the EGI <br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value><br />
|-<br />
!scope="row"|M.SA1.Size.2, Total number of production logical cpus <br />
|<Q1_value>||<Q2_value>||1390||1408||1408||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.3, Installed Capacity in HEP SPEC in EGI <br />
|<Q1_value>||<Q2_value>||13622||13798||<Q5_value>||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.4, Installed Disk Capacity (PB) per NGI<br />
|<Q1_value>||<Q2_value>||0.222||0.222||0.222||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Size.5, Installed Tape Capacity (PB)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.1, Number of production HPC clusters<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.2, Number of production sites supporting MPI<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.3, Amount of integrated desktop resources (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||1548.4||1548.4||1548.4||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Integration.4, Amount of virtualised installed capacity accessible to EGI users (HEPSPEC)<br />
|<Q1_value>||<Q2_value>||0||0||0||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.ServiceValidation.1, Total number of staged rollout components<br />
|<Q1_value>||<Q2_value>||4||4||4||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
!scope="row"|M.SA1.Accounting.1, Number of sites adopting AMQ messaging for Usage Record publication <br />
|<Q1_value>||<Q2_value>||2||2||2||<Q6_value>||<Q7_value>||<Q8_value>||<Q9_value>||<Q10_value>||<Q11_value>||<Q12_value>||<Q13_value>||<Q14_value>||<Q15_value>||<Q16_value>||<br />
|-<br />
|-<br />
|}</div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR3&diff=22958
EGI-InSPIRE:Slovenia-QR3
2011-08-05T05:42:00Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|3<br />
|NGI_SI<br />
|Slovenia<br />
|Barbara Krasovec, Jan Jona Javorsek<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|22.11.2010||Ljubljana||NGI meeting||13||Available only in slovene, on the following URL: <br />
http://www.arnes.si/pomoc-uporabnikom/grid/dokumenti.html<br />
<br />
Faculty of computer and information science, Environment Agency of the Republic of Slovenia, Faculty of Civil Engineering are interested to join to NGI Slovenia with their cluster. <br />
HPC is desirable by users.<br />
Clusters will support Arc and gLite<br />
all the documentation for users and site administrators will be published on the NGI wiki and will be available when using a valid certificate (this is done already)<br />
training for users will be organized when needed<br />
|-<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
||||||||| <br />
|-<br />
||||||||| <br />
|-<br />
|||||||||<br />
<!-- formatting text --><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br><br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
<!-- Provide your test below --><br />
<br />
===2.2. Main Achievements===<br />
<!--<br />
Provide your text below<br />
--><br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|Issue description || Issue mitigation<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR3&diff=22848
EGI-InSPIRE:Slovenia-QR3
2011-08-04T10:50:00Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|3<br />
|NGI_SI<br />
|Slovenia<br />
|Barbara Krasovec, Jan Jona Javorsek<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|22.11.2010||Ljubljana||NGI meeting||13||Available only in slovene, on the following URL: <br />
http://www.arnes.si/pomoc-uporabnikom/grid/dokumenti.html<br />
<br />
Faculty of computer and information science, Environment Agency of the Republic of Slovenia, Faculty of Civil Engineering are interested to join to NGI Slovenia with their cluster. <br />
HPC is desirable by users.<br />
Clusters will support Arc and gLite<br />
all the documentation for users and site administrators will be published on the NGI wiki and will be available when using a valid certificate (this is done already)<br />
training for users will be organized when needed<br />
|-<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
|<Date>||<Location>||Title||Participants||Outcome Test <br />
<!-- formatting text --><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br><br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br><br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3. <Author3><br><br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
<!-- Provide your test below --><br />
<br />
===2.2. Main Achievements===<br />
<!--<br />
Provide your text below<br />
--><br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|Issue description || Issue mitigation<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR4&diff=22844
EGI-InSPIRE:Slovenia-QR4
2011-08-04T10:39:05Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|4<br />
|NGI_SI<br />
|Slovenia<br />
|Barbara Krasovec, Jan Jona Javoršek<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!-- <br />
=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|10.2.2011||Utrecht||TF-CPR workshop on EGI and TERENA||11||The goal of the joint EGI and TERENA TF-CPR workshop was to identify possible communication issues between local NGIs and NREN and looking for solutions to overcome them. The second very important goal was to set the basis for dissemination strategy for NGIs including defining target audiences, targeted messages and means of dissemination. At the end of the workshop we produced actual draft leaflet and pull up stand, that can be used by any local NGI.<br />
There were 11 participants on site, and one participant joined the workshop via video conference. ARNES planed and led the workshop and also made sure, the outcomes of the workshop would be available to other NGIs through their local NREN.<br />
|-<br />
|13.4.2011||Kranjska Gora, Slovenia||SIRIKT||300||http://www.sirikt.si/<br />
http://www.sirikt.si/fileadmin/Sirikt2011/konferenca-arnes/clanki/kersevan-javorsek-ngi.pdf<br />
Presentation of grid technology, Slovenian NGI activities, procedures, policy etc.<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
<!-- formatting text --><br />
|-<br />
|10-14.4.2011||Vilnius,Lithuania||EGI User Forum||500||https://www.egi.eu/indico/conferenceTimeTable.py?confId=207#20110411 ; Presentation on dissemination activities in Slovenia.<br />
https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=160&confId=207<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
<!--<br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3.<Author3><br> <br />
(Copy the two rows above to add a new entry in the table)<br />
--><br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
<!-- Provide your test below --><br />
<br />
===2.2. Main Achievements===<br />
<!--<br />
Provide your text below<br />
--><br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
<!--<br />
|-<br />
|<Issue description> || <Issue mitigation><br />
--><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR4&diff=22843
EGI-InSPIRE:Slovenia-QR4
2011-08-04T10:36:58Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|4<br />
|NGI_SI<br />
|Slovenia<br />
|Barbara Krasovec, Jan Jona Javoršek<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!-- <br />
=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|10.2.2011||Utrecht||TF-CPR workshop on EGI and TERENA||11||The goal of the joint EGI and TERENA TF-CPR workshop was to identify possible communication issues between local NGIs and NREN and looking for solutions to overcome them. The second very important goal was to set the basis for dissemination strategy for NGIs including defining target audiences, targeted messages and means of dissemination. At the end of the workshop we produced actual draft leaflet and pull up stand, that can be used by any local NGI.<br />
There were 11 participants on site, and one participant joined the workshop via video conference. ARNES planed and led the workshop and also made sure, the outcomes of the workshop would be available to other NGIs through their local NREN.<br />
|-<br />
|13.4.2011||Kranjska Gora, Slovenia||SIRIKT||300||http://www.sirikt.si/<br />
http://www.sirikt.si/fileadmin/Sirikt2011/konferenca-arnes/clanki/kersevan-javorsek-ngi.pdf<br />
Presentation of grid technology, Slovenian NGI activities, procedures, policy etc.<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
<!-- formatting text --><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
<!--<br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3.<Author3><br> <br />
(Copy the two rows above to add a new entry in the table)<br />
--><br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
<!-- Provide your test below --><br />
<br />
===2.2. Main Achievements===<br />
<!--<br />
Provide your text below<br />
--><br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
<!--<br />
|-<br />
|<Issue description> || <Issue mitigation><br />
--><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR4&diff=22828
EGI-InSPIRE:Slovenia-QR4
2011-08-04T09:14:01Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|4<br />
|NGI_SI<br />
|Slovenia<br />
|Barbara Krasovec, Jan Jona Javoršek<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!-- <br />
=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
<!--<br />
|-<br />
|10.2.2011||Utrecht||TF-CPR workshop on EGI and TERENA||11||The goal of the joint EGI and TERENA TF-CPR workshop was to identify possible communication issues between local NGIs and NREN and looking for solutions to overcome them. The second very important goal was to set the basis for dissemination strategy for NGIs including defining target audiences, targeted messages and means of dissemination. At the end of the workshop we produced actual draft leaflet and pull up stand, that can be used by any local NGI.<br />
There were 11 participants on site, and one participant joined the workshop via video conference. ARNES planed and led the workshop and also made sure, the outcomes of the workshop would be available to other NGIs through their local NREN.<br />
|-<br />
|13.4.2011||Kranjska Gora, Slovenia||SIRIKT||300||http://www.sirikt.si/<br />
http://www.sirikt.si/fileadmin/Sirikt2011/konferenca-arnes/clanki/kersevan-javorsek-ngi.pdf<br />
Presentation of grid technology, Slovenian NGI activities, procedures, policy etc.<br />
<br />
<br />
(Copy the two rows above to add a new entry in the table)<br />
--><br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
<!-- formatting text --><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
<!--<br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3.<Author3><br> <br />
(Copy the two rows above to add a new entry in the table)<br />
--><br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
<!-- Provide your test below --><br />
<br />
===2.2. Main Achievements===<br />
<!--<br />
Provide your text below<br />
--><br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
<!--<br />
|-<br />
|<Issue description> || <Issue mitigation><br />
--><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR4&diff=22823
EGI-InSPIRE:Slovenia-QR4
2011-08-04T09:08:49Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|4<br />
|NGI_SI<br />
|Slovenia<br />
|Barbara Krasovec, Jan Jona Javoršek<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!-- <br />
=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
<!--<br />
|-<br />
|<Date>||<Location>||<Title>||<Participants>||<Outcome><br />
(Copy the two rows above to add a new entry in the table)<br />
--><br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
<!-- formatting text --><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
<!--<br />
|-<br />
|<Publication title>||<Journal/Proceedings>||Vol:<volume number><br>Issue:<Issue><br>Pg: <from> - <to>||1.<Author 1><br>2.<Author2><br>3.<Author3><br> <br />
(Copy the two rows above to add a new entry in the table)<br />
--><br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
<!-- Provide your test below --><br />
<br />
===2.2. Main Achievements===<br />
<!--<br />
Provide your text below<br />
--><br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
<!--<br />
|-<br />
|<Issue description> || <Issue mitigation><br />
--><br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22822
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:06:07Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|-<br />
|5<br />
|NGI_SI<br />
|Arnes, IJS<br />
|Barbara Krasovec, Jan Jona Javorsek<br />
<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|-<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|Why virtualization support is needed in HEP||Nordugrid 2011||||Andrej Filipčič<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22821
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:05:28Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|-<br />
|5<br />
|NGI_SI<br />
|Arnes, IJS<br />
|Barbara Krasovec, Jan Jona Javorsek<br />
<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|-<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|Why virtualization support is needed in HEP||Nordugrid 2011<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22820
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:05:06Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|-<br />
|5<br />
|-<br />
|NGI_SI<br />
|-<br />
|Arnes, IJS<br />
|-<br />
|Barbara Krasovec, Jan Jona Javorsek<br />
<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|-<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|Why virtualization support is needed in HEP||Nordugrid 2011<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22819
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:04:49Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|5<br />
|-<br />
|NGI_SI<br />
|-<br />
|Arnes, IJS<br />
|-<br />
|Barbara Krasovec, Jan Jona Javorsek<br />
<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|-<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|Why virtualization support is needed in HEP||Nordugrid 2011<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22818
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:03:26Z
<p>Barbarak: </p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|-<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|Why virtualization support is needed in HEP||Nordugrid 2011<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22817
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:01:33Z
<p>Barbarak: /* 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED */</p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|-<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak
https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Slovenia-QR5&diff=22816
EGI-InSPIRE:Slovenia-QR5
2011-08-04T09:01:06Z
<p>Barbarak: /* 1. MEETINGS AND DISSEMINATION */</p>
<hr />
<div>__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|23-25.5.2011||Ljubljana||4th Belle II Computing Workshop||40||http://kds.kek.jp/confLogin.py?returnURL=http%3A%2F%2Fkds.kek.jp%2FconferenceDisplay.py%3FconfId%3D6893&confId=6893<br />
|}<br />
<br />
===1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|9-12.5.2011||Oslo||Nordugrid 2011||60||http://indico.hep.lu.se//conferenceTimeTable.py?confId=1047<br />
|16-19.5.2011||Prague||Terena networking conference||500||ttps://tnc2011.terena.org/web/media/archive<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. Progress Summary===<br />
===2.2. Main Achievements===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>
Barbarak