Compute Environments page in Seqera Platform should show more details
evaluating
F
Flamingo pink Python
Since AWS only allows 50 CE's per account (which translates to 25 usable CE's for Seqera Platform / Tower), the management of Computer Environments becomes really important. However, the current Compute Environments page is kinda sparse, only listing the Name, Status, Last Active, and ID, of each CE. It would be helpful if more details were viewable from the Compute Environments page, details for each CE such as
- how many pipelines are using it
- which pipelines are using it
- important attributes such as usage of Wave / Fusion, EBS AutoScale, types of EC2 instances, inclusion of GPU
Hopefully some sort of compact-view could be developed to show these or other important attributes in the page for each CE.
One of the real-world needs for this, is trying to consolidate CE's, to identify which have overlapping settings, and which might not be needed. Right now its pretty difficult to navigate this with the current UI.
Rob Newman
evaluating
Rob Newman
acknowledged
Rob Newman
Merged in a post:
Compute environment dashboard to monitor status
S
Spicy Galliform
The compute environment page is a record of the compute environment as it was created. Monitoring, logging and diagnosing a compute environment must be performed entirely on the cloud provider console.
It would be really useful if Seqera Platform had a way of investigating the current status of a compute environment, including enabled/disabled, number and size of nodes, number of running pipelines on them, tasks (including status). This would help us better identify if a compute environment is healthy and identify faults early.
Additionally, it could be extended to include graphs over time, like performance (task duration), efficiency (% resources used) and costs.
Relates to https://seqera.canny.io/feature-requests/p/pre-flight-checks-to-compare-requested-resources-to-available-aws-batch-resource which is basically step 1 of this feature.
S
Spicy Galliform
Cropping out the sensitive details, but here is Azure Batch Explorer which has quite a nice view: