The original design is to save instance evacuations information
for host failure notification. For later new features, there will
be instance migrations information for host restored notification.
It is more compatible to use vm move (vmove) object, wihch
include 'type' filed to show it is one evacuation or migration.
Blueprint: vm-evacuations-for-host-recovery
Change-Id: Ic0d1283bebbc562cfd20e004cb9b6ed309d0fd28
Use allowlist_externals for rm.
Also, make sure the behaviour is consistent across tox versions
and always skip the installation of the dummy local package
(skip_install for 3, skipsdist does this already for 4).
Change-Id: Iacf9cda958ce410d30a258843e276f902c499e0b
The documentation is writting the date in its copyright. This is
considered bad practice, because this kills reproducibility. If
you don't know about reproducible build, please read on:
https://reproducible-builds.org/
Change-Id: I5a837a94468ce151e6dc24a01c238cd98d67e99b
This spec introduces a new host monitor by consul. It monitors host
heartbeat via management, tenant and storage connectivity. Only in the
case of defined HA strategy, it will trigger host recovery, for example,
storage interface disconnected.
Change-Id: If81a6a9543513acf199afe6a17dceb1544657272
Implements: bp host-monitor-by-consul
When large scale hosts failed in the same time, there would be
not enough resources to recovery all the instances. So it needs
a priority to determine which one to evacuate firstly. Moreover,
the user even wants to recall the instances to the original host
after host recovery. So it needs to keep some necessary information
aboud evacuations for new features.
Change-Id: I7c87c8d4a2ab5898d1b0d046a1377fe1ed7c79ee
Blueprint: vm-evacuations-for-host-recovery
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I1a7054a3fff7a4af9c4f9eb734099483d909ecb8
If the platform has a bad network stability, judging from pacemaker and
corosync, the host status would swing between up and down. It would
result in host recovery, which is not expected.
Repeated check is more reliable than once check to determine host
status.
Change-Id: I61a4a05f912c764d77bca87f5a297b6da42b9ae7
Implements: bp retry-check-when-host-failure
If 'enable' of one failover segment is set False, all notifications
which belong to this failover segment will be ignored, so that
no recovery flow executes.
Change-Id: I418aaa9c34826dd908363d91e0df718f55721536
Implements: bp enable-to-segment
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I2dea97815d5f4cd40d120256e91787e078a9cc40
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Use newer openstackdocstheme and Sphinx versions
- Remove install_command from tox.ini, the default is fine
Change-Id: I43c3b5653289753da4fb1d2b6db5b03336b42d67
Add the sphinx-build for this project, remove 'oslosphinx' and add
'penstackdocstheme' to support python3.
Closes-Bug: #1836551
Change-Id: I0aac32c27436671841becada6e6da238c0913631
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I466ef0b323140c936d8c83b5c206b15030a683c7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
