Limes is a quota and usage tracking service. If Limes is deployed in an OpenStack clusters, new domains and projects
start out with zero quota unless someone with the required permissions approves quota for them. (There may be exceptions
for certain auto-created resources, e.g. the default security group in Neutron.)
- You can interact with Limes through:
- the command-line client,
- or you can send requests to the HTTP API directly, as shown in this guide.
- The OpenStack web dashboard Elektra contains an optional Resource Management module that becomes accessible if Limes is deployed in the target OpenStack cluster.
- For each project, quota and usage data will be scraped from each backend service into Limes' database every 30
minutes, or when a user requests an immediate sync via the API. When displaying project data on the API, the time of
the last scrape event will be indicated by the
scraped_atfield. - For each cluster, capacity data is scraped into Limes' database every 15 minutes.
- For each cluster, domain and project data will be collected from Keystone every 3 minutes. This means that, for example, if a new project is created, resource data will become visible in Limes within 3 minutes. However, if the client which creates the project implements the Limes API (e.g. if the project is created in Elektra), Limes will be notified of the new project immediately, and resource data will become visible within a few seconds.
If updated project quotas are not reflected in the backend service, you can try to request an immediate sync via the API or in your client (e.g. via Elektra's "Sync Now" button). Whenever quota is scraped from the backend service, Limes will try to enforce its own quota values in the backend service if the backend quotas diverge.