The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "EGI-InSPIRE:JRA1 IPv6 Readiness"
(→SAM) |
|||
| Line 365: | Line 365: | ||
== <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. | |||
no official tests were made on the topic | |||
== External Resources == | == External Resources == | ||
Revision as of 16:02, 22 August 2012
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
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.