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

From EGIWiki
Jump to: navigation, search
(Accounting)
(GOCDB)
Line 363: Line 363:
 
== <span lang="EN-US">GOCDB</span><br>  ==
 
== <span lang="EN-US">GOCDB</span><br>  ==
  
<span lang="EN-US">&lt;span style="mso-spacerun:yes" /&gt;not IPv6 capable at the moment, more details after investigation with
+
<span lang="EN-US">&lt;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>  ==

Revision as of 17:12, 21 October 2011


EGI-JRA1 Tools IPv6 Readiness


Accounitng an d 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 are ok and  tested within EMI activities

-          repository: not capable at the moment, more details after investigation with the experts

GOCDB

<not IPv6 capable at the moment, more details after investigation with the experts

SAM

-          <span style="" />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