There is currently no way to differentiate a fixed ip from a floating
ip in the servers list. This extension adds the OS-EXT-IPS:type param
so that users can determine if it is a fixed address or a floating
address.
Fixes bug 1117784
DocImpact
Change-Id: I8709a4f2f6792faa3d8e0cdcd330d751ef6633ae
The extended status extension was testing list instead of get and the
extended server attribute extension was misnaming its sample files.
This makes the names of the samples consistent.
Change-Id: I5b6f8d00c85d7817775c190b2a7645a47f8085db
DocImpact: The api sample site may need to be updated as well
Adds an extension for blueprint rebuild-for-ha
Evacuation of VM from a failed host for HA.
New api supports recreate/rebuild modes. With shared storage,
VM is recreated on the target from disk.
Otherwise, rebuild from original image is performed.
DocImpact
Change-Id: Id7e3e68dbaaf74e9314440d98195a92454078fd9
Co-authored-by: Oshrit Feder <oshritf@il.ibm.com>
Implement one workitem for bp:show-availability-zone
This show the availability zone and availability zone of its host in
API: GET /servers/details, GET /server/{uuid}.
When create instance if "availability_zone" doesn't specified, the
"availability_zone" of the instance will be None. But actually the instance
is in a zone which its host is in. So I think show both of them will be fine.
Change-Id: I2d742ee2d291b514bf783fa79293785cca8ea2a5
Modified: doc/api_samples/os-flavor-manage/flavor-create-post-req.json
Deleted final comma for proper syntax
Partially fixes: bug 1088528 (part of the bug requires changes in other repo - done)
Change-Id: I5b0b29b4c720a95d5c4c5d957e77dc2e4c9cf8ee
To mirror the existing get_vnc_console RPC API method, expose a
new get_spice_console RPC API method. The only console type
supported currently is 'spice-html5' which is equivalent to
'novnc'
Blueprint: libvirt-spice
Change-Id: Iab9d3dfc3564a122a8cd2b53d34fdcc725bfa29b
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Enables cells-related functionality such as adding neighbor cells,
listing neighbor cells, and showing the capabilities of the local cell.
Implements blueprint nova-compute-cells
DocImpact
Change-Id: Iacc1e68721a7867aeaf233903cbe6d18f09ad96e
Merging the new os-networks extension upstream broke what was considered
a 'released' extension. This patch returns everything to normal and
renames the os-networks extension to os-tenant-networks
DocImpact
Implements: blueprint tenant-networks
Change-Id: I04b17d08c5760fd73736124b36cab0d383767020
fix the N402 errors that have slipped in in the last 48 hrs since
starting this patch series.
fix an N401 error that our scanner current can't find because it
only looks for doc strings on classes and defs.
this is the xeno's paradox of patch series, but we're getting close.
Change-Id: I4a763bb4c812335d853eae05c72464f18ab93297
Implements: blueprint tenant-networks
Adds a new API extension that supports a more tenant-centric model for
interacting with isolated networks. Additionally, the patch renames the
existing networks extension as os-admin-networks to more fully fit the
self-described implementation. Two new novaclient extensions and a
novaclient change accompany this patch.
DocImpact
Change-Id: Ib90a65c0a92445f86e930fab88ab4495aefff7c7
Fix N402 errors (single line docstring should end in a period)
for nova/api, part of a larger attempt to stop ignoring our own
hacking.py tests.
Fix tests that look at docs in extensions
Change-Id: I89d89d1fcf37c4e7740c36375da4c751d1b621ed
This is the final step in enabling availability_zones using aggregate
metadata. Previously all services had an availability_zone, but the
availability_zone is only used for nova-compute. Services such as
nova-scheduler, nova-network, nova-conductor have always spanned all
availability_zones.
After this change only compute nodes (nova-compute), will have an
availability_zone. In order to preserve current APIs, when running:
* nova host-list (os-hosts)
* euca-describe-availability-zones verbose
* nova-manage service list
Internal services will appear in there own internal availability_zone
(CONF.internal_service_availability_zone)
Internal zone is hidden in euca-describe-availability_zones
(non-verbose)
CONF.node_availability_zone has been renamed to
CONF.default_availability_zone and is only used by the nova-api and
nova-scheduler. CONF.node_availability_zone still works but is
deprecated
DocImpact
Completes blueprint aggregate-based-availability-zones
Change-Id: Ib772df5f9ac2865f20df479f8ddce575a9ce3aff
Instead of implementing availability zones in the service table,
availability zones are implemented using general aggregate metadata.
This patch does not remove availability zones from the service table, a
latter patch will do that.
* In theory supports a single compute node in multiple availability zones
* Drop availability_zone column from Aggregate table (is now a property)
* map aggregate metadata 'availability_zone' so API does not change
Implements blueprint aggregate-based-availability-zones
Change-Id: I2a2ac5bfaa526d639dff5efa392c051347dbd9bb
Password is stored in system_instance_metadata as four items with the
keys 'password_0' through 'password_3'. The extension adds a resource
endpoint with two methods:
GET v2/servers/<uuid>/os-server-password # get_password
DELETE v2/servers/<uuid>/os-server-password # reset_password
get_password retuns:
JSON: {"password": "xxx"}
XML: <?xml version='1.0' encoding='UTF-8'?><password>xxx</password>
Note that this is intended to be an encrypted password set by the
guest. Includes api tests for json and xml. Also includes api samples.
Part of blueprint get-password
Change-Id: I6c03f9c3bc8a2c70403bbb3e57917ab9522d75bd
* Servers in certain states will have network_info but it may change,
(eg. rescheduled build on another host). The extension allows the
operator to hide the address information in those states
* Fixes bug LP 1089092
Change-Id: Ie843e34a41c77903b201b45c5b67a6f75334cb5e
This makes a few minor cleanups and 2 additions to the
coverage extension. First, it adds a new optional field to the
report action: 'html'. This will generate an html report instead
of either the text or xml reports that the extension can
generate.
The second change is that it adds a return for the stop action.
Now upon successful completion of the stop action the directory
where the coverage data files will be returned.
Change-Id: If1aa25fc7237e9bb5100d2a4a8e560f0a68eba61
Adds API support to:
- Disassociate only host from network
- Disassociate only project from network
- Associate network with host (project already supported)
New functionality is added to a new extension networks_associate,
but the original networks extension is modified to allow networks_associate
to extend how it needs to. The original behavior of the networks extension is
preserved (no new functionality, nor change in existing behavior) in
terms of the API presented.
Bumps RPC API version for network RPC server version in order add
the associate function which allows to both associate and disassociate
a network with a host and or tenant. Has overlap with disassociate
and add_network_to_project but these are kept for backwards compatibility
DocImpact
Implmenents: blueprint apis-for-nova-manage
Change-Id: I78fd76e0696d1c872646355ab04d32f051551def
Fixes bug #1062049
There was a typo mapping the security groups resource to floating IPs.
Volumes usage isn't tracked by Nova any more since delete-nova-volume.
Key pairs don't work with the extension because of bug #1089877.
Change-Id: Ifd694b21fef1dc95e67c07dcef0cd6ea3daa8d53