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

From EGIWiki
Jump to: navigation, search
m
Line 341: Line 341:
 
being not compliant, but official <span style="mso-spacerun:yes">&nbsp;</span>tests were not performed </span><br>  
 
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>
+
<span lang="EN-US">ok to participate to a <span style="mso-spacerun:yes">&nbsp;</span>testbed if created within EGI</span>  
  
==GGUS==  
+
== GGUS ==
  
 
<span lang="EN-US">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
Line 350: Line 350:
 
<br>  
 
<br>  
  
<br>
+
<br>  
  
 
== <span lang="EN-US">Accounting</span>  ==
 
== <span lang="EN-US">Accounting</span>  ==
Line 359: Line 359:
 
</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>  
  
<span lang="EN-US" />
+
&lt;span lang="EN-US" /&gt;
  
<span lang="EN-US">Both have dependency on broker network.</span>
+
<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>  ==
  
 
<span lang="EN-US">Not IPv6 capable at the moment, more details after investigation with
 
<span lang="EN-US">Not IPv6 capable at the moment, more details after investigation with
the experts</span>
+
the experts</span>  
  
 
== <span lang="EN-US">SAM</span>  ==
 
== <span lang="EN-US">SAM</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" style=""></span><span lang="EN-US">Probes</span>'''<span lang="EN-US">: it’s up to EMI, we
+
<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" style="" /><span lang="EN-US">Probes</span>'''<span lang="EN-US">: it’s up to EMI, we
 
should investigate with them</span>  
 
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 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
 
</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>
+
compliant, nagios is compliant, strong dependence with messaging see next point</span>  
  
 
== <span lang="EN-US">Messaging</span>  ==
 
== <span lang="EN-US">Messaging</span>  ==
Line 388: Line 388:
  
 
<span lang="EN-US">The sw should compatible, but
 
<span lang="EN-US">The sw should compatible, but
no official tests were made on the topic</span>
+
no official tests were made on the topic</span><span lang="EN-US" /><span lang="EN-US" />
 +
 
 +
 
 +
 
 +
== External Resources ==
 +
 
 +
[https://wiki.egi.eu/wiki/Network wiki.egi.eu/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:testbed w3.hepix.org/ipv6-bis/doku.php]

Revision as of 15:50, 15 November 2011


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

<span lang="EN-US" />

Both have dependency on broker network.

GOCDB

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

Broker 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

 

Ops Portal

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


External Resources

wiki.egi.eu/wiki/Network

w3.hepix.org/ipv6-bis/doku.php

w3.hepix.org/ipv6-bis/doku.php