Hello dev, I was recently looking into an enhancement to the current portal where gateways can define their own maximum values for queue properties (nodes, CPU cores, wall time limit). As of now, the maximum values are set at the SciGap level and there is no provision for gateways to define their own maximum values.
The JIRA Issue associated with the above can be found at https://issues.apache.org/jira/browse/AIRAVATA-2521 The Pull Request created for the above issue can be found at https://github.com/apache/airavata-php-gateway/pull/70 The PR reflects the following changes - - Added the maximum allowed values for the nodes, CPU cores and wall time limit to the pga_config.php.template for reference. - Modified the createSubmit() and editSubmit() methods in ExperiementController.php to validate the entered values for nodes, CPU cores and wall time limit for a given experiment. If invalid, an appropriate message is returned to the view. - Added a new private method - validateQueueData() in ExperiementController.php to perform the validation of the queue values. - Modified the getQueueDatafromResourceId() method in ExperiementUtilities.php to compare the queue's maximum values for nodes, CPU cores and wall time limit with that of the gateway's configuration (found in the pga_config.php file) Have a great weekend! Regards, Sneha Tilak
