Commit Graph

1916 Commits

Author SHA1 Message Date
Yikun Jiang
e66443770d Per aggregate scheduling weight
This spec proposes to add ability to allow users to use
``Aggregate``'s ``metadata`` to override the global config options
for weights to achieve more fine-grained control over resource
weights.

blueprint: per-aggregate-scheduling-weight

Change-Id: I6e15c6507d037ffe263a460441858ed454b02504
2019-01-21 11:48:44 +08:00
Matt Riedemann
313becd5ff Cleanup soft (anti)affinity weight multiplier options
This resolves the TODO from Ocata change:

  I8871b628f0ab892830ceeede68db16948cb293c8

By adding a min=0.0 value to the soft affinity
weight multiplier configuration options.

It also removes the deprecated [DEFAULT] group
alias from Ocata change:

  I3f48e52815e80c99612bcd10cb53331a8c995fc3

Change-Id: I79e191010adbc0ec0ed02c9d589106debbf90ea8
2019-01-19 18:03:16 -05:00
Zuul
920ac6d8e1 Merge "Fix up force live migration completion docs" 2018-12-27 23:37:48 +00:00
Zuul
b2f38aa0af Merge "Redirect user/placement to placement docs" 2018-12-25 23:07:21 +00:00
Zuul
53a86b50f2 Merge "Remove "API Service Version" upgrade check" 2018-12-24 23:08:59 +00:00
Zuul
93d067df26 Merge "Remove "Resource Providers" upgrade check" 2018-12-24 23:08:53 +00:00
Zuul
0820a4e3c9 Merge "Add descriptions about microversions" 2018-12-24 23:04:26 +00:00
Zuul
6d78ccdfae Merge "Fix the link to the Placement API Version History" 2018-12-22 01:43:56 +00:00
Zuul
7d5537e0a5 Merge "Add links to summit videos in user/cells.rst" 2018-12-21 23:02:07 +00:00
Zuul
905e25a63d Merge "Fix destination_type attribute in the bdm_v2 documentation" 2018-12-21 11:52:22 +00:00
Zuul
181e3eb174 Merge "nit: Add space to feature support docs" 2018-12-21 11:52:11 +00:00
Takashi NATSUME
b934cf72e9 Add links to summit videos in user/cells.rst
This patch is a follow-up for
I66a2adb3ff75da6e267536f25c2eda5925f2fa87.

Add links to videos recorded at Rocky or Stein summit
in doc/source/user/cells.rst.

Change-Id: Idcc77cf2eee809f3ca99f952f0635213f3bb78eb
2018-12-21 05:29:25 +00:00
Zuul
aea727c4fc Merge "Fix a broken link" 2018-12-21 02:01:47 +00:00
Zuul
91051ef3d3 Merge "doc: Rework 'resize' user doc" 2018-12-20 15:37:33 +00:00
Zuul
7381ec7d7c Merge "Document using service user tokens for long running operations" 2018-12-20 12:42:06 +00:00
zhangbailin
7ba9b8143c nit: Add space to feature support docs
Change-Id: I13c5f9c053f848facbcbd663fc677f4f991d7105
2018-12-20 04:12:13 -05:00
Takashi NATSUME
7d69335671 Fix a broken link
Fix broken links in doc/source/user/cells.rst.
In addition, fix a format of a console code block
in doc/source/admin/pci-passthrough.rst.

Change-Id: I66a2adb3ff75da6e267536f25c2eda5925f2fa87
Closes-Bug: #1808906
2018-12-20 01:43:09 +00:00
Matt Riedemann
63a32c230c Remove "API Service Version" upgrade check
With change I11083aa3c78bd8b6201558561457f3d65007a177
the code for the API Service Version upgrade check no
longer exists and therefore the upgrade check itself
is meaningless now.

Change-Id: I68b13002bc745c2c9ca7209b806f08c30272550e
2018-12-19 20:41:04 -05:00
Matt Riedemann
7737acdc20 Remove "Resource Providers" upgrade check
With placement being extracted from nova, the
"Resource Providers" nova-status upgrade check no
longer works as intended since the placement data
will no longer be in the nova_api database. As a
result the check can fail on otherwise properly
deployed setups with placement extracted.

This check was originally intended to ease the upgrade
to Ocata when placement was required for nova to work,
as can be seen from the newton/ocata/pike references
in the code.

Note that one could argue the check itself as a concept
is still useful for fresh installs to make sure everything
is deployed correctly and nova-compute is properly
reporting into placement, but for it to be maintained
we would have to change it to no longer rely on the
nova_api database and instead use the placement REST API,
which while possible, might not be worth the effort or
maintenance cost.

For simplicity and expediency, the check is simply removed
in this change.

Related mailing list discussion can be found here [1].

[1] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000454.html

Change-Id: I630a518d449a64160c81410245a22ed3d985fb01
Closes-Bug: #1808956
2018-12-19 20:31:36 -05:00
wingwj
4f254696d0 Fix an inaccurate link in nova doc
Fix an inaccurate link in nova doc for pci-passthrough

Change-Id: Ia003dea1bb0ec5c6cd6928ace5a632747efba852
Closes-Bug: 1805902
2018-12-20 09:01:57 +08:00
Matt Riedemann
1a4cc6c96d Document using service user tokens for long running operations
A recent thread in the mailing list [1] reminded me that we
don't have any documentation for the service user token feature
added back in ocata under blueprint use-service-tokens.

This change adds a troubleshooting entry for when using service
user tokens would be useful, and links to it from two known
trouble spots: live migration timeouts and creating images.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001130.html

Change-Id: I1dda889038ffe67d53ceb35049aa1f2a9da39ae8
Closes-Bug: #1809165
2018-12-19 15:31:16 -05:00
Chris Dent
f1e2954508 Redirect user/placement to placement docs
The placement api-ref had a link to user/placement.html in nova. That is
being fixed in Ibfe016f25a29b6810ea09c5d03a01dbf3c53371f but the link
is now loose in the internets, using the 'latest' prefix, so we want to
make sure that what is currently showing as a 404 goes somewhere useful,
in this case the top of the placement docs.

Change-Id: Ib75547ac655e614441dec5e1bcc7784c2b6a070c
2018-12-19 17:56:36 +00:00
Zuul
86a23f417a Merge "Fix a broken-link in nova doc" 2018-12-19 17:27:30 +00:00
Zuul
72d8bf1bf8 Merge "Address nits on I08991796aaced2abc824f608108c0c786181eb65" 2018-12-19 16:40:27 +00:00
wingwj
b4ebca1d02 Fix a broken-link in nova doc
Fix a broken-link in nova doc for pci-passthrough

Change-Id: I350ee26710125f87d2e71df604ec87a38d6e997b
Related-Bug: 1805901
2018-12-19 14:35:34 +00:00
wingwj
b05ca399d8 Fix a broken-link in nova doc
Fix a broken-link in nova doc for pci-passthrough

Change-Id: I27648eb2594874036a8850fce63ff2c4f7f8abc2
Closes-Bug: 1805901
2018-12-19 16:24:58 +08:00
Zuul
e35a1e2e45 Merge "Migrate "reboot an instance" user guide docs" 2018-12-18 16:05:01 +00:00
Stephen Finucane
9cd1fc5794 Address nits on I08991796aaced2abc824f608108c0c786181eb65
- Move deprecated services to the end of the document
- Update incorrect information regarding nova-consoleauth
- Move configuration options that were specified for the wrong service
- Don't give the impression that the serial console is libvirt-only

Change-Id: Ie0fd987a1e5c130b8e31c84910814d5d051f2b31
2018-12-18 11:55:27 +00:00
Stephen Finucane
97cd1ccd3d doc: Rework 'resize' user doc
Remove a lot of noise and make things more generic through use of
variables rather than hardcoded values.

Change-Id: Ief498f902f24e5991cf463323db78729ae6f8d89
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
2018-12-18 10:56:08 +00:00
Matt Riedemann
9de70aed23 Migrate "reboot an instance" user guide docs
This imports the cli-reboot-an-instance end user guide docs from
the openstack-manuals repo [1]. As part of the docs migration
in Pike, these were forgotten. The copied contents come from
the stable/ocata branch of openstack-manuals [2].

There are two minor content changes from the original:

1. The "shutdown_timeout" config option is linked to the docs.

2. The "nova rescue" command usage is replaced with
   "openstack server rescue".

[1] https://docs.openstack.org/ocata/user-guide/cli-reboot-an-instance.html
[2] https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc/user-guide/source/cli-reboot-an-instance.rst

Change-Id: I6701e43fd80fb17df5cc703df766390ab838289a
Partial-Bug: #1714017
2018-12-18 10:56:01 +00:00
Zuul
5d748001c2 Merge "Fail to live migration if instance has a NUMA topology" 2018-12-18 02:56:40 +00:00
Zuul
af9977c71c Merge "Restore nova-consoleauth to install docs" 2018-12-17 16:36:28 +00:00
Zuul
ca1f880890 Merge "Mention size limit on user data in docs" 2018-12-17 16:36:19 +00:00
Takashi NATSUME
9466807dd2 Fix the link to the Placement API Version History
The Placement REST API Version History page has been
created by splitting the Placement doc top page (index.html)
since I66e0c7d18b253b0a5a8fdac65e30b5b3cef37db2.

So the link to the Placement REST API Version History
is updated in the nova doc.

Change-Id: I60701b09ade203b35d4d1281eb32b177543c064a
2018-12-17 06:03:46 +00:00
Takashi NATSUME
09fc91a070 Add descriptions about microversions
This patch is a follow-up patch
for I3e1ca88cac3a52a8b44e26f051a51a6db77a3231.

Add descriptions about microversions in the parameter section
in the API reference guideline.

Change-Id: I266d44cf96945445115b843aacbc29083e21bd8e
2018-12-16 23:29:50 +00:00
Zuul
4022171a61 Merge "libvirt: remove live_migration_progress_timeout config" 2018-12-15 19:33:09 +00:00
Zuul
35ee7edd94 Merge "libvirt: add live migration timeout action" 2018-12-15 19:33:02 +00:00
Zuul
ab7917c88a Merge "Add API ref guideline for body text" 2018-12-15 14:12:04 +00:00
Matt Riedemann
18fbee57b4 Fix up force live migration completion docs
This change does a few things:

* Links live_migration_completion_timeout to the config
  option guide.

* Links the force complete API reference to the feature support
  matrix to see which drivers support the operation.

* Fixes the server status mentioned in the troubleshooting for
  the force complete API reference (a live migrating server
  status is MIGRATING, not ACTIVE). The same text is copied to the
  abort live migration API reference troubleshooting for
  consistency (and since using the server status is more natural than
  the task_state).

* Links to the admin guide for troubleshooting live migration
  timeouts.

Change-Id: I496d3f4b99e3d7e978c7ecb13ab3b67023fcb919
Closes-Bug: #1808579
2018-12-14 15:13:59 -05:00
Yikun Jiang
4c3698c0b6 libvirt: remove live_migration_progress_timeout config
Config option ``libvirt.live_migration_progress_timeout`` was
deprecated in Ocata, and can now be removed.

This patch remove live_migration_progress_timeout and also remove
the migration progress timeout related logic.

Change-Id: Ife89a705892ad96de6d5f8e68b6e4b99063a7512
blueprint: live-migration-force-after-timeout
2018-12-14 14:50:38 -05:00
Yikun Jiang
99a075cc94 libvirt: add live migration timeout action
This patch remove the auto trigger post-copy, and add a new libvirt
configuration 'live_migration_completion_action'.

This option determines what actions will be taken against a VM after
``live_migration_completion_timeout`` expires. This option is set to
'abort' action by default, that means the live migrate operation will
be aborted after completion timeout expires. If option is set to
'force_complete', that means will either pause the VM or trigger
post_copy depending on if post copy is enabled and available.

Note that the progress based post-copy triggering from the libvirt
driver will be removed in next patch [1].

[1] Ife89a705892ad96de6d5f8e68b6e4b99063a7512

Change-Id: I0d286d12e588b431df3d94cf2e65d636bcdea2f8
blueprint: live-migration-force-after-timeout
2018-12-14 14:50:29 -05:00
Stephen Finucane
ae2e5650d1 Fail to live migration if instance has a NUMA topology
Live migration is currently totally broken if a NUMA topology is
present. This affects everything that's been regrettably stuffed in with
NUMA topology including CPU pinning, hugepage support and emulator
thread support. Side effects can range from simple unexpected
performance hits (due to instances running on the same cores) to
complete failures (due to instance cores or huge pages being mapped to
CPUs/NUMA nodes that don't exist on the destination host).

Until such a time as we resolve these issues, we should alert users to
the fact that such issues exist. A workaround option is provided for
operators that _really_ need the broken behavior, but it's defaulted to
False to highlight the brokenness of this feature to unsuspecting
operators.

Change-Id: I217fba9138132b107e9d62895d699d238392e761
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Related-bug: #1289064
2018-12-14 14:08:35 -05:00
Jose Castro Leon
984e45544e Fix destination_type attribute in the bdm_v2 documentation
All the clients using block device mapping are using the attribute
destination_type and the documentation points to dest_type instead.

Change-Id: Iba6e698e826d1a1898fde5cc999592f5821e3ebc
Co-Authored-By: David Moreno Garcia <david.mogar@gmail.com>
Closes-Bug: #1808358
2018-12-13 16:15:23 +01:00
Zuul
2c7aa78980 Merge "Move nova-cells-v1 to experimental queue" 2018-12-11 01:23:35 +00:00
Zuul
08d617084e Merge "Add docs for (initial) allocation ratio configuration" 2018-12-10 15:22:51 +00:00
Zuul
ae3064b7a8 Merge "Note the aggregate allocation ratio restriction in scheduler docs" 2018-12-10 10:11:39 +00:00
Takashi NATSUME
2a3e7affea Add API ref guideline for body text
Add guideline for body text in the API reference.

Change-Id: Ib03b562ffe189f24293eb77dd0c0ed5ec679172a
Partial-Bug: #1793034
2018-12-09 23:46:13 +00:00
Zuul
662bec726d Merge "Remove Placement API reference" 2018-12-09 08:26:05 +00:00
Zuul
5ca357c100 Merge "Use links to placement docs in nova docs" 2018-12-08 10:05:43 +00:00
Matt Riedemann
e02fbb53d5 Move nova-cells-v1 to experimental queue
Cells v1 has been deprecated since Pike. CERN
has been running with cells v2 since Queens.
The cells v1 job used to be the only thing that
ran with nova-network, but we switched the job
to use neutron in Rocky:

  I9de6b710baffdffcd1d7ab19897d5776ef27ae7e

The cells v1 job also suffers from intermittent
test failures, like with snapshot tests.

Given the deprecated nature of cells v1 we should
just move it to the experimental queue so that it
can be run on-demand if desired but does not gate
on all nova changes, thus further moving along its
eventual removal.

This change also updates the cells v1 status doc
and adds some documentation about the different
job queues that nova uses for integration testing.

Change-Id: I74985f1946fffd0ae4d38604696d0d4656b6bf4e
Closes-Bug: #1807407
2018-12-07 10:59:37 -05:00