110c12b414
Current policy tests override rule with string "project:non_fake" and try to tests whether policy is failed on project_id enforcement or not. But with that string as rule, policy will always fail irrespective of same project_id or different. Because rule for project_id should be string like "project_id:non_fake" or "project_id:%(project_id)s" This patch fix those tests for only those APIs where instance's user_id and project_id are being passed as policy target. Other tests will be taken care while doing project_id enforcement at API layer. Below tests are being fixed- - test_lock_server - test_pause_server - test_rescue - test_suspend_server - test_serversV21: rebuild tests Other tests are already taken care with user_id enforcement patch set. Partially implements blueprint user_id_based_policy_enforcement Change-Id: I377ef4ef438d5ef7e2c591a8317a02bc99575783
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:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://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:
http://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: