Feature: filter crn can with based on vm resources #268
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pr adds add :
Related ClickUp, GitHub or Jira tickets : ALEPH-
Self proofreading checklist
Changes
This pull request enhances the filtering capabilities of the CRN (Compute Resource Node) service by allowing users to filter nodes based on specific VM resource requirements (CPU, memory, disk). To support this, new data models for system usage and VM resources have been introduced, and the filtering logic has been updated accordingly.
Filtering and API Enhancements
VmResourcesmodel to specify VM requirements (vCPUs, memory in MiB, disk in MiB), and updated thefilter_crnmethod to accept this as an optional parameter. The method now filters nodes based on available resources, ensuring that only nodes meeting the specified criteria are returned. [1] [2] [3] [4]Data Model Additions
CpuLoad,CoreFrequencies,CpuInfo,MemoryInfo,DiskInfo,UsagePeriod,SystemUsage) to represent detailed system usage statistics for CRNs. These are now included in theCRNmodel as an optionalsystem_usagefield, enabling resource-based filtering. [1] [2] [3]