Go to file
Chris Dent 979b066be4 Add root and parent provider uuid to group by clause
Without the group by, postgres complains with:

  column "root_rp.uuid" must appear in the GROUP BY clause or be
  used in an aggregate function

which is a common complaint between mysql and postgresql. After
that is fixed, it complains about parent_rp.uuid.

This problem was discovered using my placedock container[1] with
a postgres database. The change that causes this to be necessary
must be relatively recent as this wasn't happening last week.

The problem can show up when the outer join to the root_rp and
parent_rp copies of the resource_providers table can only produce
a single row. The joins to those aliased tables are what is
upsetting postgresql.

[1] https://hub.docker.com/r/cdent/placedock/

Closes-Bug: 1765204
Change-Id: I9fb3db0d7e025fff8836d01f60bb035fb1c59758
2018-04-19 14:30:19 +01:00
2017-08-07 16:00:10 +01:00
2017-11-24 16:51:12 -05:00
2014-05-07 12:14:26 -07:00
2017-11-24 16:51:12 -05:00
2012-02-08 19:30:39 -08:00
2018-01-12 17:05:11 +08:00
2010-05-27 23:05:26 -07:00
2017-09-07 15:42:31 +02:00
2018-03-24 20:27:11 +08:00
2018-04-11 21:35:49 +08:00
2017-03-02 11:50:48 +00:00
2017-03-02 14:30:16 +08:00

Team and repository tags

image

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, OpenStack Ironic and PowerVM.

Use the following resources to learn more.

API

To learn how to use Nova's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

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:

Other Information

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at:

Description
OpenStack Compute (Nova)
Readme 1.6 GiB
Languages
Python 97.6%
Smarty 2.3%
Shell 0.1%