f89909658a
We were a bit naughty in Iecbe0eb5717afb0b13ca90d4868a3ca5f9e8902b in that we didn't normalize the storage of Keystone project and user identifiers in the API DB's new consumers table. This means that we will use a whole lot more storage for what ends up being very repetitive data. This patch changes the consumers DB table schema's project_id and user_id columns from VARCHAR(255) to INT data type. This should result in significantly faster queries for usage information since 9X the index records can fit into a single index block in memory (36-byte UUIDs stored in VARCHAR(255) versus 4-byte integers. The more index records we can fit into a single page of memory, the faster both scans and seeks will be. Let's address this now before anything uses the consumers table. Change-Id: I1b7357739f2a7e55c55d3acb9bd604731c4a2b32 blueprint: placement-project-user
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
https://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at: