Track payload sizing / spec presets (non-DB, future DB option) #2

Open
opened 2025-12-14 18:44:07 +00:00 by jester · 0 comments
Owner

Add a TODO to formalize how container sizing (CPU/RAM/Disk) is represented and evolved.

Current decision:

  • Use frontend/API preset payloads for sizing
  • Apply specs via Proxmox API at create time
  • Do NOT store specs or profiles in DB initially (faster, simpler)

Future consideration:

  • Optionally persist a sizing profile key or allocation metadata in DB for audit/billing
  • Ensure payload construction remains deterministic

This issue is for tracking and documentation, not immediate implementation.

Add a TODO to formalize how container sizing (CPU/RAM/Disk) is represented and evolved. Current decision: - Use frontend/API preset payloads for sizing - Apply specs via Proxmox API at create time - Do NOT store specs or profiles in DB initially (faster, simpler) Future consideration: - Optionally persist a sizing profile key or allocation metadata in DB for audit/billing - Ensure payload construction remains deterministic This issue is for tracking and documentation, not immediate implementation.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jester/zlh-agent#2
No description provided.