Develop Resource Detail page

[dsajdak]

There are centers that manage 'condo clusters' that are a mix of purchased and rented compute nodes in partitions made available for exclusive access to a faculty member or their research group. Because these partitions could contain a heterogenous mix of nodes, both in models, and purchase and warranty expiration dates, it is desirable to track this information on the compute node level, rather than on the cluster or cluster partition level.

At UB, we provide each faculty member/research group that purchases private nodes with their own partition in our 'faculty' cluster. Within ColdFront, the 'cluster partition' resource is a child of the parent 'cluster' resource. Taking this a step further, we should create a new resource type 'compute node' that can be used as a child of the parent resource 'cluster partition.' We can then track attributes at the compute node level to include existing attribute types such as ServiceStart (warranty start date), ServiceEnd (decommission date), SerialNumber, and new attribute types: Vendor, Model, RackUnits (total number of 'u' a compute node takes up in a rack), InstallDate, WarrantyExpirationDate.

There are a few things that need to happen to make this possible:

1. Add a new resource type 'compute node' as a default in ColdFront
2. Add new resource attribute types as a default to include: Vendor, Model, RackUnits, InstallDate, WarrantyExpirationDate.
3. Develop 'Resource Detail' page similar to 'Allocation Detail' page which would be linked to from the 'Allocation Detail' page (make resource name next to "Resource in allocation" clickable)

The 'Resource Detail' page would:

1. Be viewable for all users (read only) and system administrators (editable attributes)
2. Display parent resource, resource attributes, child resource(s) and child resource attributes.

• We should consider different ways to display this info. There could be a large number of child resources and attributes so a collapsible view might be most flexible.
• Be able to filter and sort these child resources, based on their attribute values. For example, show all children that have a warranty expiration date in the next 365 days. Show all children with a vendor=Dell. Show all 1u servers.
• Display notification on this page when children have a 'EndDate' in less than 6 months so PIs know they have equipment being decommissioned soon.

3. Tie into the Slurm plugin to display resource-specific submission information. For example, if we have a partition in the faculty cluster named beta, we'd display: To submit to this resource, use the Slurm flags: --cluster=faculty --partition=beta --qos=beta --account=[grabbed from allocation attribute]

Future: tie rack unit numbers into billable form for invoicing co-location fees. We expect other centers to also want to include attributes for pricing of nodes to tie into billing as well.

[dsajdak]

Will also need a page for sys admins similar to the 'allocation requests' which lists all resources with warranties expiring in X days - filterable. Configurable notifications might be desirable as well.

[dsajdak]

We are going to split this large issue into a few smaller ones. The majority of the feature request will be completed with an upcoming PR; however, there are additional things we'd like to add eventually to make this even more useful. Those include:

• Display notification on this page when children have a 'EndDate' in less than 6 months so PIs know they have equipment being decommissioned soon. Notifications for resources #371
• Tie into the Slurm plugin to display resource-specific submission information. For example, if we have a partition in the faculty cluster named beta, we'd display: To submit to this resource, use the Slurm flags: --cluster=faculty --partition=beta --qos=beta --account=[grabbed from allocation attribute] Add Slurm info to allocation detail page #372
• Tie rack unit numbers into billable form for invoicing co-location fees. We expect other centers to also want to include attributes for pricing of nodes to tie into billing as well. Invoice: Form for billing co-location or other fees associated with resources #373