Add ability to choose a size of the virtual env size #258
Description
Request
Naming convention
Here is a group chat: https://chatgpt.com/gg/v/69c7ea46b47481a0bfd888f5fa6e1714?token=ljKKKiaPHiWD_93XgIUI4g about the naming convention.
| Shape | vCPU | Memory | Use Case |
|---|---|---|---|
| nano | 0.25 | 0.5 GB | sidecars, tiny workers |
| micro | 0.5 | 1 GB | lightweight APIs |
| small | 1 | 2 GB | standard services |
| medium | 1 | 4 GB | memory-heavy APIs |
| large | 2 | 8 GB | backend services |
| xlarge | 4 | 16 GB | compute + memory |
| 2xlarge | 8 | 32 GB | heavy processing |
Temporary Request
For plain Linux containers, memory is enforced with cgroups, so the limit on a running container can be changed by the runtime or orchestrator
UI
Commands in the container
mieos request 1h ram 32gb
mieos request 3d disk 30gb
mieos request 30m cpu +3
These are examples of requested in a temporary burst of 1h of ram, 3 days of disk, and 30 minutes of cpu.
If after the time expires and the resources cannot be released, the owner of the container will be bugged by the hour for 24 hours and then the container will just be restarted to release the resources.