HEROES scenarios Sample Clauses

HEROES scenarios. The following are the main scenarios contemplated when integrating EAR in the HEROES project: • HPC centres where EAR is in production (fully deployed). In this case, we would like to support, at least, these two types of jobs: o Traditional HPC jobs: Normal state, where users launch a job through the job scheduler and EAR is fully operational. o Jobs executed with Singularity: Similar to the previous case, but the entire environment is virtualized through Singularity. • HPC centres where EAR is not installed: o Traditional HPC jobs: Users still launch a job through the job scheduler, but EAR is missing some key components (EARD) and it needs to operate with reduced functionality. o Jobs executed with singularity containers [ 6] : Similar to the previous case, but the entire environment is virtualized through Singularity. • Cloud: Data centres or HPC centres where everything is virtualized. Access to hardware functionalities is very restricted and information about the hardware where jobs are running is difficult or impossible to gather. Only the first case, HPC data centres with traditional HPC jobs, were already supported before HEROES. All the other use cases have been evaluated during the project and EAR has been extended to support them. The last scenario is the only one with very limited functionality supported. In the project we are using AWS cloud instances where it is not possible to measure any performance counter, even at the process level, and no actions concerning power or CPU frequency can be performed. Currently we are working on a power model based on the application utilization to provide some hint on power consumption. 4 EAR extensions for HEROES Three types of extensions have been implemented to support HEROES deployment and execution. First set of extensions are related to the deployment of the software. Before the project some options were manually set during the generation of Makefiles and configuration files. Second set of extensions are related to the initialization of the XXXX. As already commented, before the project the XXXX was designed to be executed in a fully deployed environment and was disabled automatically if it was not the case. The extensions implemented create a kind of dummy environment with required data types and settings to support XXXX and it is executed with the existing features. Finally, the code itself of the XXXX and auxiliary libraries have been extended to support limited systems where some (or all) of the ...