Rafael is right. I'm talking about the excplicit limit which with (cpu
cores limit, ram limit) allows limiting account.
E.g.
We have
- low cpu VM offering: 4 cores / 1000 MHz / 4 GB RAM
- high cpu offering: 1 core / 3400 MHz / 2 GB RAM
Without MHz parameter it's impossible enforce an user can crea
I believe he is talking about something different.
The Quota plugin is used to manage users' resources indirectly. Meaning,
instead of assigning the limit of resource a user can allocate/use, the
administrator/operator assigns a monetary value to users. Then, the user
has the freedom to use as muc
Ivan,
Is the feature you are suggesting not just a slightly different version of the
quota service – which afaik is already in place?
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quota+Service+-+FS
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 09/01/2018, 12:58, "Rafael Weingä
Very interesting proposal. I even thought it already existed, but it is not
there yet.
+1
On Mon, Jan 8, 2018 at 6:32 AM, Ivan Kudryavtsev
wrote:
> Hello, community.
>
> We are going to implement the feature which enables limiting accounts and
> domains for cumulative MHz available. Thus creati
Hello, community.
We are going to implement the feature which enables limiting accounts and
domains for cumulative MHz available. Thus creating VMs will take that
limit into account calculating VM MHz as core_count * core_frequency. May
be some other people wanted a feature like that or have consi
