Difference between revisions of "EGI-InSPIRE:JRA1 IPv6 Readiness"
Line 394: | Line 394: | ||
== External Resources == | == External Resources == | ||
[https://wiki.egi.eu/wiki/Network wiki | [https://wiki.egi.eu/wiki/Network Egi-wiki Network] | ||
[https://w3.hepix.org/ipv6-bis/doku.php?id=ipv6:introduction | [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 | [https://w3.hepix.org/ipv6-bis/doku.php?id=ipv6:testbed Hepix IPv6 Testbed] |
Revision as of 15:54, 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
- <span lang="EN-US" 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<span lang="EN-US" /><span lang="EN-US" />