This adds a request filter that, if enabled, allows us to use placement
to select hosts in the desired availability zone by looking up the uuid
of the associated host aggregate and using that in our query for
allocation candidates. The deployer needs the same sort of mirrored
aggregate setup as the tenant filter, and documentation is added here to
make that clear.
Related to blueprint placement-req-filter
Change-Id: I7eb6de435e10793f5445724d847a8f1bf25ec6e3
1. Beginning with the Queens release, the keystone install guide
recommends running all interfaces on the same port. This patch
updates the install guide to reflect that change.
2. update the deprecated neutron auth options
Change-Id: I5c0a6389b759153bae06fa43846f03ac083c3db4
ExactCoreFilter, ExactDiskFilter and ExactRamFilter were deprecated
for removal in the Pike release [1] and are now being removed.
Now scheduling will use the custom resource class defined for each
baremetal node to make its selection.
[1] I843353427c90142a366ae9ca63ee4298b4f3ecd4
Change-Id: Ie25a5f6c28c20f589016791970da8d5849ec291c
xenapi is going to support pool-based multi-hosts OpenStack
environments, aggregate-based-pools support was removed in
change I2c492c46e85c1df96aa7fdc12cdee0b1c7ba775e.
This patch is used to update related OpenStack documents.
Change-Id: I9a1244fb23aea99eb246325d5655ab005dca42b4
Implements: blueprint live-migration-in-xapi-pool
Since BFV instances don't have a specific image attached to them, the
filter will consider them as not having a specific image, hence not
isolated. Correcting the doc.
Change-Id: Ib235fca1365ee7a38b94600960ee3947f448c4a9
There were several things wrong with this doc since the migration
in-tree in pike, which are handled here:
- Updated options to use the current names.
- Any mention of the periodic_task_interval option is removed
since this doc is really about the FilterScheduler, and the
periodic task interval is only used by the CachingScheduler to
cache and refresh hosts, something the FilterScheduler doesn't do.
The note about service_down_time is already covered in the help
text for the periodic_task_interval option.
- Removed a broken (and oddly placed) link to the block storage
docs; it's unclear why the compute scheduler docs need to randomly
link to the block storage docs for schedluing (maybe that was
super legacy from the nova-volume days).
- Fixed a broken link to the 'evacuate instances' docs.
This change does not get into details for the individual filters
or weighers, only the overview and filter scheduler description.
Change-Id: Ie5bb9781e1997ad12521b5df5245a78b587a4a20
Closes-Bug: #1749235
This copies similar wording from the Filter Scheduler docs [1]
and applies it in the scheduler configuration guide for the
NUMATopologyFilter.
[1] https://docs.openstack.org/nova/latest/user/filter-scheduler.html
Change-Id: I247ddc8bb344a6821ddeb4ce18f38591dec481ee
The docs were using variable names from the filter code rather
than the actual config options.
Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
Related-Bug: #1746483
Deprecated in Pike:
I660e0316b11afcad65c0fe7bd167ddcec9239a8b
This filter relies on the flavor.id primary key which will
change as (1) flavors were migrated to the API database and
(2) when a flavor is changed by deleting and re-creating the
flavor.
Also, as noted in blueprint put-host-manager-instance-info-on-a-diet,
this is one step forward in getting us to a point where the only
thing that the in-tree filters care about in the HostState.instances
dict is the instance uuid (for the affinity filters). Which means
we can eventually stop RPC casting all instance information from
all nova-compute services to the scheduler for every instance create,
delete, move or periodic sync task - we only would need to send the
list of instance UUIDs. That should help with RPC traffic in a large
and busy deployment.
Change-Id: Icb43fe2ef5252d2838f6f8572c7497840a9797a1
The TrustedFilter and the related trusted_computing config options
were deprecated in Pike:
If6e53feeb97e6050c1eb7962110ed89504c952fc
Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com>
Change-Id: I0a7ab3a4fb2cfad567a8644bed4de574393ee11a
The arguments of nova CLI commands related to host aggregate
(I93f44a12b6d5a91b448f6f8d238311d58bf40c01) are fixed.
The host APIs have been deprecated since microversion 2.43.
So remove description related to nova host commands.
And add description about nova hypervisor commands.
Change-Id: Ibf78865844da6f007b610f12430df4866076f00b
Closes-Bug: #1726658
This patch is follow-up for
I48d7c77a6e0eaaf0efe66f848f45ae99007577e1.
The hyperlink style is fixed.
Add a note that it need be updated for os-xenapi latest version.
Add a reference to nova policies.
TrivialFix
Change-Id: I274fb6b7ea0bb2ea81faaa68d783edbaa8ed06c3
commit 2fe96819c2
fixed the default filter settings and in doc we should
do it accordingly
Related-Bug: 1709328
Change-Id: I8a7b25e70e1d111f5a0d1db9213a58354cf9e5b1
Import the following files from the former config-reference [1]:
api.rst
cells.rst
fibre-channel.rst
hypervisor-basics.rst
hypervisor-hyper-v.rst
hypervisor-kvm.rst
hypervisor-lxc.rst
hypervisor-qemu.rst
hypervisor-virtuozzo.rst
hypervisor-vmware.rst
hypervisor-xen-api.rst
hypervisor-xen-libvirt.rst
hypervisors.rst
index.rst
iscsi-offload.rst
logs.rst
resize.rst
samples/api-paste.ini.rst
samples/index.rst
samples/policy.yaml.rst
samples/rootwrap.conf.rst
schedulers.rst
The below files are skipped as they're already included, in slightly
different forms, in the nova documentation.
config-options.rst
nova-conf-samples.rst
nova-conf.rst
nova.conf
Part of bp: doc-migration
Change-Id: I145e38149bf20a5e068f8cfe913f90c7ebeaad36
Zuul