When discussing for the blueprint placement-claims we had a consensus on
using reserved values for helping operators to provide overhead limits
for all the instances.
Since we only had 2 opts for RAM and disk, we missed a possible CPU one.
This patch is adding that one.
Change-Id: Ic3162f0ab39a703798b4a2a7e860fed628da1e7e
Partially-Implements: blueprint placement-claims
the guideline include a broken links
nova/api/openstack/rest_api_version_history.rst need to be
nova/api/openstack/compute/rest_api_version_history.rst
Change-Id: I54f4796382865081654f2ab471fd67274d84bb89
This commit removes nova-cert which has been deprecated since change
Id7a1fc943cbe6d860a50d3cc776717b55351004b. The APIs have been hard coded
to return a 410 whenever they're called now. For the API ref a new
section for obsolete apis is added to the bottom of the page and the
certificates api ref is moved there.
Implements bp remove-nova-cert
Change-Id: I2c78a0c6599b92040146cf9f0042cff8fd2509c3
This is an integer that defaults to zero. This can be used by API services
to efficiently filter out records that have already been mapped by a
HostMapping. This is an integer instead of a boolean in case we later need
to do some other sort of mapping of these records and need to distinguish
yet another level of mapped-ness.
Note this also removes some tests from TestNewtonBlocker which can no longer
work with the new ComputeNode model since they attempt to use it to create
compute nodes at a schema older than needed for this new field. The point of
the test was to verify, in Newton, that the blocker migration caught the thing
we needed to catch. It doesn't need to be in master anymore and certainly
is not worth the acrobatics that would be required to keep it working. (Note
that we haven't even had such tests for many of our blocker migrations)
Related to blueprint discover-hosts-faster
Change-Id: I902d75efb0bbe177680d7211c23235f42497e3fe
The get_inventory() method implementation for the Ironic driver
in Pike started hard-coding the allocation ratio for VCPU,
MEMORY_MB and DISK_GB inventory on compute node resource providers,
effectively ignoring these configuration options used in the
ResourceTracker.
This patch adds a note about that so people deploying Ironic don't
have to worry about these options. It also fixes a couple of weird
random apostrophes.
Change-Id: Icaf94a7dc97a1d297d68b7633802aaf131d76471
Firstly, _find_base_file was differentiating between 2 different types
of 'non-original', but the caller was then treating them identically.
This differentiation was obviously redundant.
However, the caller was using them to populate originals. Note that
_scan_base_files has been called previously, and therefore originals
is already correctly populated. This means that _find_base_file does
not need to identify 'originals' at all.
Additionally, originals is only tracked at all so that 'originals' and
'non-originals' can be aged with different frequencies. This doesn't
really make any sense anyway, so this is a small step towards removing
a redundant config variable.
Change-Id: I893cfe23b48ee135ac6c14870d50d7f734c25247
_handle_base_image was handling a variety of circumstances which, due
to its context, can never occur. We rename the method to _mark_in_use
to reflect what it actually does, and remove all the dead code
including the tests for it.
Change-Id: Iee3c824efdafbcdaa34e26b969a2164dd0f8b933
This patch simply adds contextual comments to _handle_base_image
pointing out the various conditionals which, due to their context, are
either guaranteed to be always True or always False. We clean this
function up in a subsequent patch.
Change-Id: Ib986dd495eb14d368e6ff2abbad1b28d1872b3a5
The referenced commit was merged without any feedback from the people
working on the cellsv2 stuff and doesn't really make a lot of sense. The
cell0 record is pretty much the only one you _can_ delete and re-create
if needed.
This reverts commit 17b9f83778.
Change-Id: I9c6559cd2abce678ea72c5d5888d989fba3975f3
Includes floating_ip_dns.py, floating_ip_pools.py, floating_ips_bulk.py,
and floating_ip.py.
blueprint policy-docs
Change-Id: Ib4807c83e3f7dc88b6b6b71293937b79caf976ce
We have signaled many times the use of API extensions to change the API
has been deprecated, including:
04f8612aa9
This patch ensures we no longer check any of the discoverable rules when
compiling the list of extensions to list in the API. This stops users
from being able to use policy to hide certain API extensions. This was
never that useful, but now you can't turn any extensions off and we
report the API version number, it is basically useless.
Note the change in the policy cmd unit test is to ensure now there are
no rules that use the ANY rule, we correctly check we return an empty
list of rules that match.
blueprint remove-discoverable-policy-rules
Change-Id: I61d8063708731133177534888ba7f5f05a6bd901
Takashi NATSUME