Difference between revisions of "EGI-InSPIRE:JRA1 IPv6 Readiness"
(→GGUS) |
|||
Line 371: | Line 371: | ||
compliant, nagios is compliant, strong dependence with messaging see next point</span> | compliant, nagios is compliant, strong dependence with messaging see next point</span> | ||
== | == 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. | |||
both at an infrastructure level and at a | |||
requested to EMI, infrastructure can be fixed | |||
== <span lang="EN-US">Ops Portal</span> == | == <span lang="EN-US">Ops Portal</span> == |
Revision as of 15:34, 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
- <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
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<span lang="EN-US" /><span lang="EN-US" />