This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I08e284ae1aecb68782993d819badde13d45568d7
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I826899e99ec86cedf0e3d8e3c6f2559407384f52
Story: #2002586
Task: #24310
The new stable upper-constraints file is only available
after the openstack/requirements repository is branched.
This will happen around the RC1 timeframe.
Recheck and merge this change once the requirements
repository has been branched.
The CI system will work with this patch before the requirements
repository is branched because zuul configues the job to run
with a local copy of the file and defaults to the master branch.
However, accepting the patch will break the test configuration
on developers' local systems, so please wait until after the
requirements repository is branched to merge the patch.
Change-Id: I133002dd6c6dcc1c148d23d936883cf4a750f4ac
Devstack deploys nova service with name as 'nova' but in
masakari.conf 'nova_catalog_admin_info' default is
'compute:Compute Service:publicURL' which causes below error
while executing masakari notifications:
EndpointNotFound: publicURL endpoint for compute service named
Compute Service not found.
This patch fixes this issue by changing the default value of config
option 'nova_catalog_admin_info' to 'compute:nova:publicURL'.
NOTE:
In real production deployment of masakari operator has to set the
value of this config option according to the nova service name that
he/she configures.
Closes-Bug: #1746229
Change-Id: I032d85e7e11836a282251885a7f9d4bc76ce7045
TEMPEST_SERVICES global variable is not supported
by devstack since long back.
- I380dd20e5ed716a0bdf92aa02c3730359b8136e4
- I9c24705e494689f09a885eb0a640efd50db33fcf
Service availability of tempest known services will be
set by devstack with local check.
- I02be777bf93143d946ccbb8e9eff637bfd1928d4
masakari does not have tempest plugin so it does
not need to have service register in tempest.
This commit removes the TEMPEST_SERVICES setting.
Change-Id: I30673a3d739e013caec2b8d4a2295d71ab40e491
Related-Bug: #1743688
This patch modifies that masakari-engine ignores '409 Conflict'
when adding reserved_host to aggregate.
Change-Id: I4603df36370154a8168d53b74c551feefc13cb4b
Closes-Bug: #1739383
This patch added implementation so that masakari can evacuate
instances which task_state is not none.
After the instance evacuated, it is recovered with original
vm_state. So if the instance's vm_state was 'stopped', it is
recovered with 'stopped', and if 'error', it is recovered
with 'error'.
Change-Id: I7af8552de0ee77b948a071b7f787514a81ccebc3
Closes-Bug: #1721742
This patch removed unnecessary sleep which existed in host-failure
recovery process.
Change-Id: Ic1df0200c8ddf7d6be7548f1df5b37b74a9ba737
Closes-Bug: #1736906
Added documentation for how to get involved, development qucikstart
and masakari system architecture.
Change-Id: Ie2cbdde7698a79a1b996e485d141eb15dbded4cd
Added api specifications for versions, segments, hosts and
notifications as per OpenStack standards.
Change-Id: Iefc83254e22fc31d1f0d13f52e71d42c63e82b7d
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
Change-Id: I2f61f9767882c74b7fb7b54ec890a5c1b8f03aaf
If system time is adjusted first forward and then backward while a
masakari-engine service is running, then the periodic tasks stops
for the duration of time the system clock was adjusted backward.
This was supposed to be fixed by the following patch to oslo.service
https://review.openstack.org/#/c/286838/ , but the order of imports
in unit tests and production code is different, so masakari services
end up starting with the default eventlet hub, that does not use a
monotonic clock and, thus, is affected by changes of system time.
Testing the change done in the patch is problematic, as it's a
subject of imports order and is not reproduced in functional or
unit tests (oslo_service is always imported earlier than eventlet
hub is initialized, so it just does "the right thing").
The alternative is to make an assertion when services start.
Co-Authored-By: Roman Podoliaka <rpodolyaka@mirantis.com>
Closes-Bug: #1510234
Change-Id: I9d917b3151d9cdf7340a173b5baf98def63c76cd
Recently a commit: 188173a807 got
merged into masakari which replaces a rpc method 'get_transport'
with 'get_rpc_transport'. The 'get_rpc_transport' expects the
oslo.messaging config option 'transport_url' [1] to be present in
the [DEFAULT] section of masakari.conf. The current masakari devstack
script doesn't add 'transport_url' in masakari.conf which results
into failure of devstack installation of masakari.
This patch fixes this issue by using an inbuilt devstack function
'iniset_rpc_backend' to add the 'transport_url' config option in
masakari.conf.
[1] * https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/transport.py#L44
* https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/transport.py#L201
Closes-Bug: #1728544
Change-Id: I75da054c6669aa90dd96c3ede3ae98de74275de2
oslo.context>=2.19.1 outputs 'project' key in context's to_dict
function.
The value of 'project' key is same as 'project_id' key.
So this patch modifies unit testcases according to the above changs.
And, this patch adds oslo.context to requirements.txt.
oslo.context had been installed related to oslo.versioned object
until now.
But, it is better to describe it explicitly because Masakari uses
the library.
Change-Id: Ibebed8a4e5bfd49f192b1cf876b7538f9c057f97
Masakari has never used service_type and service_name of
nova_catalog_admin_info. However, these can be specified
when masakari creates a novalient object.
This patch modified so that masakari uses these.
Change-Id: I7fdd3b47230bea004a9129234c88d20d611814bf
Closes-Bug: #1724764
To enable ssl support for masakari using devstack just
mention 'ENABLED_SERVICES+=,tls-proxy' in local.conf
file.
Change-Id: Ia65d20083c8740d7dbbc38600ffd7de06cf08010
Community has decided to do not translate log messages anymore.
The motivation behind removing translation jobs for log messages
is that when operators encounters any unfamiliar situations(e.g.
nova error, keystone error etc.), searching on the Internet
based on actual log content would have more results than searching
translated log messages.
In this patch I have added hacking rule to check that logs are
not translated.
Change-Id: I90d53d617aac6839c2f2ab119847cbf24a1300e0
DbMigrationError is deprecated and will NOT be thrown in oslo.db
since oslo.db >=4.27.0, DBMigrationError will be thrown instead.
Consumers should catch DBMigrationError instead of DbMigrationError
Depends-On: Iab0566cf9f4552e91fa417e64472fa106e8bc86d
Depends-On: I0ebd69c3d778acb5bec9e136627e345e7fcf2bd3
Change-Id: I8e4968d2f2ed90edc22161db60712896f6e9f024
iso8601.UTC is correct datetime UTC field object.
iso8601 >= 0.1.12 includes only iso8601.UTC for python3
while both UTC and Utc() for python2. Less then 0.1.12
included both UTC and Utc() for both python2/3.
Change-Id: I9b2a8ba5a5ab44c95e68d67e0e3ee8e2c0024b03
Closes-Bug: #1715486
Currently on master error instances are evacuated from failed
compute host and stopped at the destination host after evacuation.
Some operators may not want to evacuate error instances in some
cases like below:
If user is running 1ACT/n SBY application on instances, launching
error instances will cause unexpected effect.
This patch adds a new config option 'ignore_instances_in_error_state'
under [host_failure] section which makes the recovery of error
instances configurable. If this config option set to True, masakari
will skip the recovery of error instances otherwise it will evacuate
error instances from a failed source compute node along with other
instances. The default value for this config option is set to False.
Change-Id: I24f8282357f28544fd1b56f270da22c7329a9f3d
Domain name is needed when using keystone v3 to create keystoneauth
session[1], otherwise the following error will be raised:
InvalidInput: Invalid input received: Expecting to find domain in
project - the server could not comply with the request since it is
either malformed or otherwise incorrect
[1]: https://docs.openstack.org/keystoneauth/latest/authentication-plugins.html#v3-identity-plugins
Change-Id: I557a7107b51ae4ffab15d045a4be6e3ed1940bd8
Closes-bug: #1710570
OpenDev Sysadmins
OpenStack Release Bot