ea864bff0b
Currently when list servers from all tenants (i.e. --all-tenants is set as 1 when "nova list"), privilege is required. However, computer pollster in ceilometer need to get all instances from all tenants in one host. Granting admin privilege to the pollster is not very secure. All tenants servers list should be policy-based, instead of requiring admin privelege. There is one potential backward compatibility. With all_tenants specified, non-admin accounts will get back owned servers only without this patch, however it will get policy exception now if policy checking failed. IMHO the new behaviour makes more sense. Change-Id: I8f1f064434ab12b6c0cd636f84dfc1b6a9b2fc90 Signed-off-by: Yunhong, Jiang <yunhong.jiang@intel.com>
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMWare, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
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.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy 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 wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
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:
Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at:
-- End of broadcast