EGI-InSPIRE:JRA1 IPv6 Readiness
|EGI Inspire Main page|
|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.
In principle is ok, more investigation with network experts are needed
- 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.
- 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
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.
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.
The sw should compatible, but no official tests were made on the topic.