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
We were using `warning`, and `important` themes to mark deprecations in
various places. We have a `deprecated` role, so this change switches to
use it.
Note that I also found the following files that mentioned deprecation,
but not in a way where using this role seemed appropriate. I'm
recording them here so you know I considered them.
doc/source/admin/configuration/hypervisor-kvm.rst
doc/source/admin/configuration/schedulers.rst
doc/source/cli/index.rst
doc/source/cli/nova-rootwrap.rst
doc/source/contributor/api.rst
doc/source/contributor/code-review.rst
doc/source/contributor/policies.rst
doc/source/contributor/project-scope.rst
doc/source/reference/policy-enforcement.rst
doc/source/reference/stable-api.rst
doc/source/user/feature-classification.rst
doc/source/user/flavors.rst
doc/source/user/upgrade.rst
Change-Id: Icd7613d9886cfe0775372c817e5f3d07d8fb553d
A recent'ish change in openstack-manuals [1] noted the new support for
NUMA topologies when using the Hyper-V driver. As part of this change, a
section was added that describes the configuration steps that were
necessary on Hyper-V hosts before booting instances. However, the way
this section is integrated gives the impression that NUMA support is a
Hyper-V only feature.
Correct this by moving this configuration step to the end of the
document and instead opting to link to it from higher in the doc.
[1] https://review.openstack.org/#/c/424102/
Change-Id: Ic8d9c1b35d52a26374763b5c0e4be79875814569
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
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
Since we have a recorded overview and demo for
volume multi-attach we should link to it from our
docs.
Change-Id: I6e0e243dbb1e1203dd31e820ea12dc7aaa227b64
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
xenapi is going to support pool-based multi-hosts OpenStack
environments, this patch is used to remove dependency to the
old aggregate-based-pools and add support to xenapi pool.
Also include unit test changes.
Updated configuring migrations document:
https://docs.openstack.org/nova/latest/admin/configuring-
migrations.html#configuring-migrations-xenserver-shared-storage
Other related documents will be updated in another patch.
Implements: blueprint live-migration-in-xapi-pool
Change-Id: I2c492c46e85c1df96aa7fdc12cdee0b1c7ba775e
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
In change I1f25300d44b04ca5bcdd9b505319f0d089a9c964, log-config has been
removed and replaced with log_config_append
Change-Id: I7533f6eebfdb5ad5f2594a5436814fcecfc4c583
The metadata service docs were hard to find since they were nested
down in some nova-network admin guide docs, and they were a mix of
end user and admin deployment guide information.
This change splits out the end-user facing content into a user
guide and leaves the deployment-specific information in the admin
guide, and links are updated appropriately.
The admin guide portion also referenced some config options that no
longer exist, so those are also removed and vendordata_providers
is added with a link to the vendordata guide. The options themselves
are cleaned up for their current groups and linked to the config option
docs.
Change-Id: I66035366f3a7ca62ea12d6afa74d13db01ec9f8d
noVNC 1.0.0 has the fix for non-US key mappings so this adds a simple
note when installing the novnc package that at least 1.0.0 should be
used for non-US key map support.
Change-Id: Ia1a84c986025f8a46c1062440faa0deb1d2d73a5
Related-Bug: #1682020
This is the companion doc to the admin guide docs
in cinder:
I77bb849e039e1b44964ac0f30d48b5c16ca41b44
Change-Id: I11f97cf79e0c947b42de69cf8a7f6c1dbdb943a1
Actually, inject_password, inject_key and inject_partition
by libguestfs is only valid for linux guest.
Add some descriptions for these.
TrivialFix
Change-Id: I5b2ef7d677a1d2d47052df5eaf8726cfc02eea1c
Signed-off-by: Chen Hanxiao <chenhx@certusnet.com.cn>
This was originaly copied over from "compute-manage-volumes.rst"
doc in the openstack-manuals repo but it's clearly mostly talking
about managing volumes on the Cinder side, not how they related
to compute server instances. Furthermore, Cinder already has a much
more detailed CLI guide on managing volumes, so this change removes
the content that's not specific to Nova and just links to the Cinder
docs.
Change-Id: I8e1c0d30debfdd4017c6d1a810a7b7dd382cd02d
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
The explanation of NUMA topology feature of nova exited in both
numa.rst and cpu-topologies.rst under doc/source/admin/.
This patch merges them for cleaning up.
Change-Id: I35e23b2e1ac55c74faf4f0542498e45f2957e4d3
The 2.14 microversion makes the --on-shared-storage calculation
happen automatically in the compute service, so we should make a note
of that in the evacuate CLI docs.
Change-Id: I88806897a2412971b3c7488155f17156ae1c7bf9
Zuul