This builds on the ProviderTree work in the compute driver and
resource tracker to take the supported capabilities from a driver and
turn those into standard traits on the compute node resource provider.
This is a simple way to expose in a REST API (Placement in this case)
what a compute node, via its driver, supports.
This is also something easy that we can do in lieu of a full-blown
compute capabilities REST API in nova, which we've talked about for
years but never actually done anything about.
We can later build on this to add a request filter which will mark
certain types of boot-from-volume requests as requiring specific
capabilities, like for volume multiattach and tagged devices.
Any traits provided by the driver will be automatically added during
startup or a periodic update of a compute node:
https://pasteboard.co/I3iqqNm.jpg
Similarly any traits later retracted by the driver will be
automatically removed.
However any traits associated with capabilities which are
inappropriately added to or removed from the resource provider by the
admin via the Placement API will not be reverted until the compute
service's provider cache is reset.
The new call graph is shown in this sequence diagram:
https://pasteboard.co/I25qICd.png
Co-Authored-By: Adam Spiers <aspiers@suse.com>
Related to blueprint placement-req-filter
Related to blueprint expose-host-capabilities
Change-Id: I15364d37fb7426f4eec00ca4eaf99bec50e964b6
We could probably do with a more concrete way to specify what services
use a given configuration value, but this is a start.
Change-Id: I23051a48754f2d43867ae9efc28691f766e6c6f3
This uses ironic’s conductor group feature to limit the subset of nodes
which a nova-compute service will manage. This allows for partitioning
nova-compute services to a particular location (building, aisle, rack,
etc), and provides a way for operators to manage the failure domain of a
given nova-compute service.
This adds two config options to the [ironic] config group:
* partition_key: the key to match with the conductor_group property on
ironic nodes to limit the subset of nodes which can be managed.
* peer_list: a list of other compute service hostnames which manage the
same partition_key, used when building the hash ring.
Change-Id: I1b184ff37948dc403fe38874613cd4d870c644fd
Implements: blueprint ironic-conductor-groups
This patch adds the following files:
1) doc/api_samples/os-evacuate/v2.68/server-evacuate-find-host-req.json
2) doc/api_samples/os-evacuate/v2.68/server-evacuate-req.json
which were missing in https://review.openstack.org/#/c/634600/
so that the "tox -e api_samples" can run without errors.
Change-Id: I248b7e172698a9bee155e72215c231da9033540a
Closes-bug: #1817915
This patch fixes comments in the following patches:
* Ie5ea45484a632da77c41bfe2613fa5f1dfbf19ea
* If8a13f74d2b3c99f05365eb49dcfa01d9042fefa
* Ia2e6a65690a1d7f89af0bc32fa8be30ca09472e2
* Ic28ffe9268cb7a94214b029af66ccf9af40a3a78
Change-Id: Ic11d4b002d21f1ddd321b452502e05b152f0ce09
blueprint: bandwidth-resource-provider
Since at least one libvirt capability is already dynamic due to
depending on support being present in QEMU and libvirt, change the
LibvirtDriver.capabilities dictionary from a class variable to an
instance variable. This prevents the risk of one test setting a
capability which bleeds over into other tests, in the same way it was
already done in the PowerVM driver:
https://github.com/openstack/nova-powervm/commit/cc7564549a90a59f2ef27cca14862c33b9a07c25
Change-Id: Ic4c16b23834b43a258be5073e32bcdb9c0421f02
Adds a section in the admin guide with the config options related to
down cells.
Related to blueprint handling-down-cell
Change-Id: I6a6cc71e83896aaccd5dd98bc2ea024d6f22d528
In the next change in the series, we will use nested resource providers
for pGPUs. Accordingly, the allocation will be made on a child RP, not the
root RP.
This change aims to prepare this by allocating the right mediated device from the
same physical device.
Note that given we don't pass allocations when initializing the virt driver, in
case some mdevs are missing, we will recreate them blindly. Next change will
fix it.
Part of blueprint reshape-provider-tree
Part of blueprint vgpu-stein
Change-Id: Ia8f43199f70da9c5867acd9a76c43ca8c2c11c80
os_brick drops support for direct connector classes imports from
os_brick.initiator.connector module.
Remove such imports from ScaleIO driver tests.
Change-Id: I0f809069a46f0084b6ad779b27c88246f8ceef00
This adds some simple unit tests for showing and listing attached
port interfaces where the corresponding VirtualInterface record
does not exist - which is possible for very old port attachments
since we started creating the VirtualInterface record for neutron
ports in the Newton release.
This is a follow up to I09420ff7134874dfe4dc399931c7740e81ecc2d0.
Part of blueprint expose-virtual-device-tags-in-rest-api
Change-Id: If14c4d6e97870de875b5dcd6bf68bd1b56ffad74
This is *mostly* used for nova-network and therefore can be deprecated.
There is one corner case where we could conceivably use this with
neutron and the libvirt driver, but it's only ever going to work with
with Linux bridge, is probably broken and should just be removed in
favour of neutron variants of this functionality. A note is included
detailing this, just in case people do want to spend the time getting to
the bottom of this, but I wouldn't recommend that.
The help text for this option is improved based on information I found
while researching the option and mostly taken from the commit message
for commit 8f1c54ce.
Change-Id: I33607453b3174192a33d9d56e203227bc9237f31
In an effort to try and de-clutter the create() method this
change refactors the code that processes the "networks"
request parameter to a separate method.
Change-Id: I419336ea845bdd11d02ba098d8a6521a730906fd
Matt Riedemann
