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"
Jump to navigation
Jump to search
EGI-JRA1 Tools IPv6 Readiness
GOCDB
| (15 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{EGI-Inspire_menubar}} | |||
[[Category:Deprecated]] | |||
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;" | |||
| style="padding-right: 15px; padding-left: 15px;" | | |||
|[[File:Alert.png]] This article is '''Deprecated''' and should no longer be used, but is still available for reasons of reference. | |||
|} | |||
{{TOC_right}} | |||
<!--[if gte mso 9]><xml> | <!--[if gte mso 9]><xml> | ||
<w:WordDocument> | <w:WordDocument> | ||
| Line 331: | Line 341: | ||
= EGI-JRA1 Tools IPv6 Readiness<br> = | = EGI-JRA1 Tools IPv6 Readiness<br> = | ||
== Accounting and Metrics Portals at CESGA == | |||
ipv6 migration at cesga for the infrastructure should be completed</span><br> | |||
== | |||
the infrastructure should be completed</span><br | |||
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 == | ||
<span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">-<span> </span></span></span>'''<span lang="EN-US">clients</span>'''<span lang="EN-US"> have had their code checked</span> within EMI activities. | <span lang="EN-US" style="mso-ascii-font-family:Calibri;mso-fareast-font-family:Calibri; mso-hansi-font-family:Calibri;mso-bidi-font-family:Calibri"><span style="mso-list:Ignore">-<span> </span></span></span>'''<span lang="EN-US">clients</span>'''<span lang="EN-US"> have had their code checked</span> within EMI activities. | ||
| Line 359: | Line 357: | ||
</span></span></span>'''<span lang="EN-US">repository</span>'''<span lang="EN-US">: unknown. RAL site which hosts is not yet supporting IPv6, more details after investigation with the experts</span> | </span></span></span>'''<span lang="EN-US">repository</span>'''<span lang="EN-US">: unknown. RAL site which hosts is not yet supporting IPv6, more details after investigation with the experts</span> | ||
Both have dependency on broker network. | |||
== <span lang="EN-US">GOCDB</span><br> == | == <span lang="EN-US">GOCDB</span><br> == | ||
* 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 | |||
the experts | the experts | ||
== <span lang="EN-US">SAM</span> == | == <span lang="EN-US">SAM</span> == | ||
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. | |||
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> == | ||
The sw should compatible, but no official tests were made on the topic. | |||
== External Resources == | |||
== External Resources == | |||
[ | [[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] | ||
Latest revision as of 17:18, 17 February 2021
| 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.
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
Both have dependency on broker network.
GOCDB
- 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
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.