Charms should be able to specify minimum hardware constraints
Bug #1866198 reported by
Tim McNamara
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Charms don't currently have the ability to directly influence the instance selection for their application.
Allowing charms to define their own constraints would provide resource-intensive applications the ability to run well using default settings. It could also allow charms that need very few resources, such as proxy charms, to run at low cost.
tags: |
added: k8s removed: caas |
To post a comment you must log in.
I think things like this are worth treating a bit like series. Charms can indicate a preference and if the operator is ok with that great, but there should be awareness to the operator to help avoid surprise bills of doom where something huge was selected and the operator wasn't expecting it. We've tended to be very very careful with behavior that touches on people's wallets.