{"id":445,"date":"2014-01-17T14:43:51","date_gmt":"2014-01-17T14:43:51","guid":{"rendered":"http:\/\/corneliadavis.com\/blog\/?p=445"},"modified":"2014-01-17T14:43:51","modified_gmt":"2014-01-17T14:43:51","slug":"changing-quota-definitions","status":"publish","type":"post","link":"https:\/\/corneliadavis.com\/blog\/2014\/01\/17\/changing-quota-definitions\/","title":{"rendered":"Changing quota definitions"},"content":{"rendered":"

Recently I\u2019ve had several customers ask about whether quota definitions can be changed, both in the OSS product and in PCF. \u00a0The short answer is \u201cyes\u201d. Here\u2019s the longer:<\/p>\n

First, for those of you who might be unfamiliar with quotas, they are assigned to organizations and basically limit consumption within that organization. \u00a0A quota definition sets limits in certain areas, such as memory, number of service instances and so on. \u00a0The Cloud Foundry deployment has any number of named quota definitions defined, and an organization is assigned a single quota_definition.<\/p>\n

Viewing the defined quota_definitions<\/h1>\n

Currently the quota definitions for your elastic runtime deployment are only viewable through the command line client. \u00a0As you surely know, we currently have two clis, the old (v5), which I will henceforth refer to as \u201ccf\u201d or v5, and the new (v6), which I will henceforth refer to as \u201cgcf\u201d or v6. \u00a0To see the list of quota_defitions you can use the following commands:<\/p>\n

cf -t set-quota<\/pre>\n
That is, execute the command with no arguments and you will first be shown a list of the available quota definitions.<\/p>\n
Or with the new cli, first set the env variable CF_TRACE=true and execute:<\/p>\n
gcf quotas<\/pre>\n
In both of the above cases we\u2019ve run with tracing turned on so that you can see the details of the quota definitions. This will be key as you will need to know the format and key names when issuing curl commands described below.<\/p>\n
Setting org quotas<\/h1>\n
Given existing quota definitions, assigning one to an organization is done very simply with the following (v5 and v6) CLI commands:<\/p>\n
cf set-quota --organization myorg --quota-definition trial<\/pre>\n
or<\/p>\n
gcf set-quota myorg trial<\/pre>\n
The final argument in each of these is the name of an existing quota definition.<\/p>\n
Creating, deleting or updating quota definitions<\/h1>\n
Quota definitions themselves are created one of two ways; either at the time that you are deploying the elastic runtime, and\/or post deployment, using the api.<\/p>\n
At deployment time<\/h2>\n
This is done by simply including quota definitions in your deployment manifest properties, for example:<\/p>\n
properties:\n  quota_definitions:\n    free:\n      memory_limit: 0\n      total_services: 0\n    paid:\n      memory_limit: 10240\n      total_services: -1\n    runaway:\n      memory_limit: 102400\n      total_services: -1<\/pre>\n
PCF does not yet expose quota definitions in the Operations Manager (deployer), however, the good news is that regardless of how you deploy the Elastic Runtime, you may edit the quota definitions to your heart\u2019s content after deployment.<\/p>\n
Post deployment<\/h2>\n
To create a new quota definition using the API you simply need to issue a POST to the quota_definitions resource. \u00a0The simplest way to do this is with the (v5) cf curl<\/code> command, as this will include your current token (obtained with a cf login) in the request; if you wish to use your favorite REST client you will have to futz with the auth token yourself. \u00a0Note that v6 does not yet (!)<\/a> support gcf curl<\/code>.<\/p>\n
To craft the appropriate request you will need:<\/p>\n