Alert.png 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 @

Difference between revisions of "IPv6TestReports"

From EGIWiki
Jump to navigation Jump to search
Line 204: Line 204:

== Detailed Test Reports for each Service  ==

* [[IPv6TestReportGliteCreamCE| '''gLite CREAM CE UMD 2''' ]]
* [[IPv6TestReportGliteCreamCE| '''gLite CREAM CE UMD 2''' ]]

Revision as of 10:57, 13 September 2012

Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Tools menu: Main page Instructions for developers AAI Proxy Accounting Portal Accounting Repository AppDB ARGO GGUS GOCDB
Message brokers Licenses OTAGs Operations Portal Perun EGI Collaboration tools LToS EGI Workload Manager

Testing reports

We gather here all test reports about UMD Components, spanning different test domains:

1. Installation : Has it been possible to install the service using only IPv6 ?
2. Configuration: Was configuration possible using only IPv6 ?
3. Dual Stack : Did switching on the IPv6 stack break anything ?
4. Smoke testing : was is possible to start the services properly using only IPv6 ?
5. Basic Functional Tests: Was the expected basic functionality correctly provided ?
6. Has the system been stressed using IPv6-only ?
(We summarize the services Client/Server behavior in this Table) .

Summary of Initial Assessment Test Results including installation and configuration procedures

Detailed Test Reports for each Service