Clearly nobody really uses the "application/vnd.openstack.image"
links in the returned results from GET /v2/{tenant}/images
REST API call, since the link URI returned in it is wrong.
Glance URIs do *not* contain a project or tenant in the URI
structure like Nova's REST API URIs do, but _get_alternate_link()
method of the image ViewBuilder tacks it on improperly:
Change-Id: I4ccb5628569c60026a1772df0794ac0271c48db3
Closes-Bug: #1343080
Add a new nova scheduler weighter, sort the filter
hosts according to host io ops number, aims to
booting instances on light workload hosts.
DocImpact: Adds io_ops_weight_multiplier to [DEFAULT]
group of nova.conf and an new default schedule weigher.
Change-Id: Ib3c9184f10b2ebe6b1230365a51b5542dffd447c
Implements: blueprint io-ops-weight
Ports os-networks-associate extension and adapts it to the
v2.1/v3 API framework. API behaviour is identical.
- unittest code modified to share testing with both v2/v2.1
- Adds expected error decorators for API methods
Partially implements blueprint v2-on-v3-api
Change-Id: I6ccf9613abf999784c548fb058522ac60db7f052
Ports os-tenant-networks extension and adapts it to the v2.1/v3 API
framework. API behaviour is identical.
- unittest code modified to share testing with both v2/v2.1
- Adds expected error decorators for API methods
Partially implements blueprint v2-on-v3-api
Change-Id: I340c9b1312a3477c63d28f19df9611c95e67cde6
This patch ports floating_ip_pools extention from v2 to v2.1,
and have v2 unit test cases shared between v2.1 and v2.
Partially implements blueprint v2-on-v3-api
Change-Id: I0b34358db08a29e76a59b22a0992abc88296058d
Ports os-networks extension and adapts it to the v2.1/v3 API
framework. API behaviour is identical.
- unittest code modified to share testing with both v2/v2.1
- Adds expected error decorators for API methods
Partially implements blueprint v2-on-v3-api
Change-Id: I94b7b476cbb02725a396725a379417b64afd58a7
This patch ports couldpipe extension from v2 to v2.1,
and have v2 unit test cases shared between v2.1 and v2.
Partially implements blueprint v2-on-v3-api
Change-Id: Id40c637c0fc207e97b1d094805eb0cee6e9cd9c9
This patch removes the baremetal virt driver from nova, which was
deprecated in Juno. It does not aim to perform any of the refactoring
we need to do now that the driver is gone, but is intended as a clean
removal of all the baremetal code itself.
Of specific note are the api_samples tests. We didn't have samples to
test the ironic proxy code, so I removed the baremetal ones for show
and index, resetting that extension back to "untested" status as if it
was new.
Tests that stub out ironic interactions and re-introduce those tests
should be added after this patch.
Change-Id: Ia76e41a8a3b7230701872ae7a1975edc3d9ea847
This patch ports v2 disk_config extension to v2.1.
Unittest code modified to share testing with both v2/v2.1.
API sample file and their tests have been added.
Also added extension point of server resize V3.
Partially implements blueprint v2-on-v3-api
Change-Id: Id2aace8121a310f8c86c6a9cc532bd1074d653c4
Ports v2 fping extension and adapts it to the v2.1/v3 API
framework. API behaviour is identical.
- unittest code modified to share testing with both v2/v2.1
- Adds expected error decorators for API methods
Partially implements blueprint v2-on-v3-api
Change-Id: I8dc4ede46826bf6062097a3b4ba6be9a09a1bd12
The nova-manage flavor sub-command was deprecated in Juno milestone-1
via commit a601556684 with a note that it
will be removed in Kilo.
This removes it.
Change I4e2399f2fbab2c20299dd62c104b9220c1d36fb2 is to remove the
related Tempest tests.
Change-Id: I1798c8a0697009b3dcebeb818580c8323880e395
Document what APIs nova considers to be public contracts, anything not
in this list should be considered a private API.
Clarify the 'API' section to make sure its clear we are talking about
the REST API.
Change-Id: If71adc7a9d5dc1bde79f75d10e67500f6f92b81f
There is an option "disk_allocation_ratio" in DiskFilter instead of
a typo "disk_allocation_ration".
This patch fixes the typo on filter_scheduler.rst.
Change-Id: Iad4951fbdca97eccb956c42270bfc170fc7c7dac
When using serial console we are expecting using a plain websocket
so we should to return the 'ws://' scheme as the default one, also
it makes no sense to handle webserving content since currently
nothing has been implemented in favor of this case.
DocImpact: The 'base_url' option serial_console has been updated
Closes-Bug: #1373950
Change-Id: I0d0e4f7060febec5e0a357cd3e8c05486f2afaa5
The syntax suggested for adding hooks to nova via setup.py entrypoints is:
entry_points = {
'nova.hooks': [
'resize_hook': your_package.hooks.YourHookClass,
]
},
But this is incorrect. The proper syntax for an entry_points entry is:
entry_points = {
'nova.hooks': [
'resize_hook=your_package.hooks:YourHookClass',
]
},
Change-Id: Id7bc6891dc542d4317e82e15300c7293eb0d17a0
Closes-bug: #1374666
This patch port extended_ips/extended_ips_mac extension to V2.1
There are difference between V2 and V3 server show/index &
server address index API response listed below-
'address' field of V2->V3 API response-
"OS-EXT-IPS:type" -> "type"
"OS-EXT-IPS-MAC:mac_addr" -> "mac_addr"
Reverting those attribute same as V2 to work with V2.1
Closes-Bug: #1368495
Partially implements blueprint v2-on-v3-api
Change-Id: I44902b0402115d1b6e833975e6c2f020ac5ab7c3
There were broken links on the following class
'AggregateNumInstancesFilter', 'RamWeigher' in
document filter_scheduler.html. Fix these broken
links.
Change-Id: I3cac48a6ad466a32a88c23c9f128e66dae5889ee
Closes-Bug: #1363955
Don't list entire api/autoindex under Developer Docs, we already have a
model index link at the bottom of the page, showing the entire
autoindex on the home page is makes the page overwhelming.
Change-Id: I25c5b50412881b55aa745ce3da2c22466e879fcf
At the nova mid-cycle we agreed that while specs have made our blueprint
process significantly better, we think the current approach still leaves
much to be desired. This document is the outcome of the discussion at
the mid-cycle on how we want to manage blueprints in Kilo.
This proposal is being placed in devref, as we want to use gerrit's
workflow (two core reviews, inline comments, revisions etc) and this is
a document for developers.
Introduce the idea of project priorities.
Change-Id: I7075a130c01be22f3ee5315d4a65b8e524b5a1ad
* Devref mentioned 10.10 instead of 14.04 as the tested ubuntu
environment
* Point to our official git mirror instead of github
Change-Id: I4514faeaebe200a2f616bc37fca02c2927edf599
This second change in a sequence that adds new quota values
for server groups. This part adds the new V2 API extensions
to make the new quota values visible and changeable, and updates
the unit tests to check both V2 cases.
Note that Tempest changes https://review.openstack.org/#/c/112474/
is required to get a clean run as it checks for a specific
set of values.
The quota checks themselves are covered in a subsequent
dependent change.
Implements: blueprint server-group-quotas
DocImpact
Change-Id: I78974602d4be04deaf173b3e43f2dab92e8f4171
This patch adds the basic NUMA filter that will take the proposed
instance topology and try to match it against that of a host.
The matching will be done in the following manner:
* Filter will try to match the exact NUMA cells of the instance to those
of the host. It *will not* attempt to pack the instance onto the host.
* It will consider the standard over-subscription limits for each cell,
and provide limits to the compute host accordingly.
* If instance has no topology defined, it will be considered for any host.
* If instance has a topology defined, it will be considered only for NUMA
capable hosts.
DocImpact
Change-Id: I8788dde69524c8a32a41ce31a96c89f9b09e91ce
Blueprint: virt-driver-numa-placement
At the nova mid-cycle we agreed that while specs have made our
process significantly better, we think the current approach still leaves
much to be desired. This document is the outcome of the discussion at
the mid-cycle on how we want to manage blueprints in kilo.
This proposal is being placed in devref, as we want to use gerrit's
workflow (two core reviews, inline comments, revisions etc) and this is
a document for developers.
It turns out adding the specs requirement to blueprints adds a
non-trivial amount of overhead, revisit when a blueprint and spec is
needed to minimize overhead in cases where it isn't helpful.
Change-Id: Iaaadc26f3f51ee091419beaa12e0508623eed99e
Remove intersphinx from the docs build as it triggers network calls that
occasionally fail, and we don't really use intersphinx (links other
sphinx documents out on the internet)
This also removes the requirement for internet access during docs build.
This causes docs jobs to fail because we error out on warnings.
Change-Id: I71e941e2a639641a662a163c682eb86d51de42fb
Related-Bug: #1368910
"revertResize/confirmResize" server actions were missed for V2.1 API.
This patch converts "revertResize/confirmResize" server action
for V2.1 API
The differences between v2 and v3 are described on the wiki page
https://wiki.openstack.org/wiki/NovaAPIv2tov3.
Change-Id: I24bdb5b28fafeb60ea7b4ff044b12a519498e592
Closes-Bug: #1367642
Server groups can be used to control the affinity and anti-affinity
scheduling policy for a group of servers (instances). Whilst this is
a useful mechanism for users such scheduling decisions need to be
balanced by a deployers requirements to make effective use of the
available capacity.
This change adds quota values to constrain the number and size of
server groups a user can create.
Two new quota values are be introduced to limit the number of server
groups and the number of servers in a server group. These will follow
the existing pattern for quotas in that:
* They are defined by config values, which also include the default
value
* They can be defined per project or per user within a project
* A value of -1 for either quota will be treated as unlimited
* Defaults can be set via the quota groups API
* Values may be changed at any time but will only take effect at the next
server group or server create. Reducing the quota will not affect any
existing groups, but new servers will not be allowed into group
that have become over quota.
This is part one of a linked sequences of changes that implement the
new quotas - split to make the reviews easier.
This part adds the definition of the new quota values, but leaves the
V2 API unchanged. The V2.1 API is updated as it shows all quota values.
The second part adds the new V2 API extension to make the new quota
values visible and changeable. At this point a Tempest change is
required to get a clean run as it checks for a specific set of
values.
The third part implements the quota checks themselves.
Thanks to Cyril Roelandt for supplying some of the unit tests.
Co-authored-by: Cyril Roelandt <cyril.roelandt@enovance.com>
Implements: blueprint server-group-quotas
DocImpact
Change-Id: Ib281e43eabfbd176454bde7f0622d46fb04fcb79
jichenjc