Difference between revisions of "EGI-InSPIRE:JRA1 IPv6 Readiness"

From EGIWiki
Jump to: navigation, search
 
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{EGI-Inspire_menubar}}
 +
[[Category:Deprecated]]
 +
 +
 +
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;"
 +
| style="padding-right: 15px; padding-left: 15px;" |
 +
|[[File:Alert.png]] This article is '''Deprecated''' and should no longer be used, but is still available for reasons of reference.
 +
|}
 +
 +
{{TOC_right}}
 
<!--[if gte mso 9]><xml>
 
<!--[if gte mso 9]><xml>
 
  <w:WordDocument>
 
  <w:WordDocument>
Line 331: Line 341:
 
= EGI-JRA1 Tools IPv6 Readiness<br>  =
 
= EGI-JRA1 Tools IPv6 Readiness<br>  =
  
<br>  
+
== Accounting and Metrics Portals at CESGA ==
 +
ipv6 migration at cesga for the infrastructure should be completed</span><br>  
  
== <span lang="EN-US">Accounting and Metrics Portals at CESGA</span><br>  ==
+
There are no reason for the portals for being not compliant, but official tests were not performed.
 
+
Ok to participate to a testbed if created within EGI.
<span lang="EN-US">ipv6 migration at cesga for
 
the infrastructure should be completed</span><br>
 
 
 
<span lang="EN-US">there are no reason for the portals for
 
being not compliant, but official <span style="mso-spacerun:yes">&nbsp;</span>tests were not performed </span><br>
 
 
 
<span lang="EN-US">ok to participate to a <span style="mso-spacerun:yes">&nbsp;</span>testbed if created within EGI</span>
 
  
 
== GGUS  ==
 
== GGUS  ==
 +
In principle is ok, more investigation with network experts are needed
  
<span lang="EN-US">In principle is ok, more investigation with network experts are needed
+
== Accounting ==
</span>
 
 
 
<br>
 
 
 
<br>
 
 
 
== <span lang="EN-US">Accounting</span>  ==
 
  
 
<span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>'''<span lang="EN-US">clients</span>'''<span lang="EN-US"> have had their code checked</span> within EMI activities.&nbsp;  
 
<span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>'''<span lang="EN-US">clients</span>'''<span lang="EN-US"> have had their code checked</span> within EMI activities.&nbsp;  
Line 359: Line 357:
 
</span></span></span>'''<span lang="EN-US">repository</span>'''<span lang="EN-US">: unknown. RAL site which hosts is not yet supporting IPv6, more details after investigation with the experts</span>  
 
</span></span></span>'''<span lang="EN-US">repository</span>'''<span lang="EN-US">: unknown. RAL site which hosts is not yet supporting IPv6, more details after investigation with the experts</span>  
  
&lt;span lang="EN-US" /&gt;
+
Both have dependency on broker network.
 
 
<span lang="EN-US">Both have dependency on broker network.</span>
 
  
 
== <span lang="EN-US">GOCDB</span><br>  ==
 
== <span lang="EN-US">GOCDB</span><br>  ==
 
+
* Need to add new IPv6 fields to the Site and Service entities for rendering in the PI.
<span lang="EN-US">Not IPv6 capable at the moment, more details after investigation with
+
* GOCDB itself is not IPv6 capable at the moment, more details after investigation with
the experts</span>
+
the experts
  
 
== <span lang="EN-US">SAM</span>  ==
 
== <span lang="EN-US">SAM</span>  ==
 +
Probes: it’s up to EMI, we should investigate with them.
  
<span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></span></span>'''&lt;span lang="EN-US" style="" /&gt;<span lang="EN-US">Probes</span>'''<span lang="EN-US">: it’s up to EMI, we
+
SAM side: apache is ipv6 compliant, nagios is compliant, strong dependence with messaging see next point.
should investigate with them</span>
 
 
 
<span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 
</span></span></span>'''<span lang="EN-US">SAM side</span>'''<span lang="EN-US">: apache is ipv6
 
compliant, nagios is compliant, strong dependence with messaging see next point</span>
 
 
 
== <span lang="EN-US">Messaging</span>  ==
 
 
 
<span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">B</span></span><span lang="EN-US">roker services are not compliant,
 
both at an infrastructure level and at a sw level. SW compliance should be
 
requested to EMI, infrastructure can be fixed</span>
 
  
<span lang="EN-US">&nbsp;</span>
+
== Messaging  ==
 +
Message broker services are not compliant, both at an infrastructure level and at a software level. Software compliance should be requested to EMI, infrastructure can be fixed.
  
 
== <span lang="EN-US">Ops Portal</span>  ==
 
== <span lang="EN-US">Ops Portal</span>  ==
 
+
The sw should compatible, but no official tests were made on the topic.
<span lang="EN-US">The sw should compatible, but
 
no official tests were made on the topic</span>&lt;span lang="EN-US" /&gt;&lt;span lang="EN-US" /&gt;
 
 
 
<br>
 
  
 
== External Resources  ==
 
== External Resources  ==
  
[https://wiki.egi.eu/wiki/Network wiki.egi.eu/wiki/Network]  
+
[[Network| Egi-wiki Network]]
  
[https://w3.hepix.org/ipv6-bis/doku.php?id=ipv6:introduction w3.hepix.org/ipv6-bis/doku.php]  
+
[https://w3.hepix.org/ipv6-bis/doku.php?id=ipv6:introduction Hepix IPv6 pages]  
  
[https://w3.hepix.org/ipv6-bis/doku.php?id=ipv6:testbed w3.hepix.org/ipv6-bis/doku.php]
+
[https://w3.hepix.org/ipv6-bis/doku.php?id=ipv6:testbed Hepix IPv6 Testbed]

Latest revision as of 17:18, 17 February 2021

EGI Inspire Main page


Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.


EGI-JRA1 Tools IPv6 Readiness

Accounting and Metrics Portals at CESGA

ipv6 migration at cesga for the infrastructure should be completed

There are no reason for the portals for being not compliant, but official tests were not performed. Ok to participate to a testbed if created within EGI.

GGUS

In principle is ok, more investigation with network experts are needed

Accounting

-          clients have had their code checked within EMI activities. 

-          repository: unknown. RAL site which hosts is not yet supporting IPv6, more details after investigation with the experts

Both have dependency on broker network.

GOCDB

  • Need to add new IPv6 fields to the Site and Service entities for rendering in the PI.
  • GOCDB itself is not IPv6 capable at the moment, more details after investigation with

the experts

SAM

Probes: it’s up to EMI, we should investigate with them.

SAM side: apache is ipv6 compliant, nagios is compliant, strong dependence with messaging see next point.

Messaging

Message broker services are not compliant, both at an infrastructure level and at a software level. Software compliance should be requested to EMI, infrastructure can be fixed.

Ops Portal

The sw should compatible, but no official tests were made on the topic.

External Resources

Egi-wiki Network

Hepix IPv6 pages

Hepix IPv6 Testbed