Platform Testing and Quality Strategy Sample Clauses
Platform Testing and Quality Strategy. Multiple layers of controls are applied to the Platform to ensure that its quality is maintained.
Platform Testing and Quality Strategy. The HPC Platform provides a federated infrastructure with supercomputers at four HPC centres, Cloud storage and high-fidelity visualisation systems. All hardware components are connected with a secure network, either through the PRACE network or via dedicated connections (see Annex A: Platform Architectural Diagram for details). The logical connection of the infrastructure components is realised by an LDAP based account management and a UNICORE installation at all sites. Most supercomputer users usually login to the system using SSH from the command line. Therefore, most of the software components of the HPC Platform are not integrated into the Collaboratory but instead installed on the supercomputer(s) and/or available for download, depending on the target architecture (HPC and/or local computers). For this reason, and because many of the software components are also funded from other sources, the HPC Platform is using a three-step testing and quality strategy:
1) The HPC Platform team supports users in implementing complex workflows like the ones described in Annex J: User Projects and tests these workflows together with the users (see Annex I: User feedback received in M18-M30 for software and services). The HPC Platform uses this co-design approach to assess the status and quality of Platform services, if the related documentation is well written and sufficient, and if the (user) interfaces provided for the services work correctly. The availability of the infrastructure and the status of the Platform services are tested by a team consisting of members from WP7.5 “High Performance Platform: operation and integrations” on a regular basis, taking into account feedback from HPC Platform users. This mainly concerns the HPC Core Platform Services that are described in Annex A: Platform Architectural Diagram.
2) Software & Services of the outer layer (see Annex A: Platform Architectural Diagram) are first tested by the developers themselves. HPC users who are directly logged in to the supercomputer typically report software bugs and issues to the development teams; the necessary contact details are published in the Guidebook. More details about the testing and quality processes established by the software development teams in the HPC Platform are available in the table in Annex H: Quality and testing strategies for software and services.
3) The HPC Platform provides a contact form (▇▇▇▇▇://▇▇▇-▇▇▇-▇▇▇▇▇▇▇▇.▇▇- ▇▇▇▇▇▇▇.▇▇/?▇▇▇▇_▇▇=▇▇▇; also available from the ...
