This feature will allow user to monitor mistral services and important metrics like operations related to tasks, executions, workflows, etc.
1. Added Monitoring server which can run similar to other mistral components by enabling monitoring and recovery jobs config options.
2. Monitoring plugin can collect metrics from the mistral and publish it in the Prometheus compatible format.
3. By using this monitoring plugin user can attach monitoring tools to the Mistral like Prometheus and Grafana to view metrics in a dashboard.
4. Added recovery jobs to recover from different failing or stucked conditions for eg. removing frozen named locks, refresh state of tasks stucked in waiting state long time, expired sub workflow tasks, stucked workflows, etc.
Implements: blueprint add-mistral-monitoring-plugin
Change-Id: Idbb6de9084504448befb9e346da4f458eb6c5a17
Currently tox jobs are broken because python-glareclient can't be
installed with the latest constraints.
The conflict is caused by:
python-cinderclient 8.3.0 depends on PrettyTable>=0.7.2
python-glanceclient 3.6.0 depends on PrettyTable>=0.7.1
python-glareclient 0.5.3 depends on PrettyTable<0.8 and >=0.7.1
...
The user requested (constraint) prettytable===2.5.0
The Glare project has been unmaintained for a while[1]. It does not
support any of the current tested runtime and is considered to be
incompatible with recent OpenStack releases.
Because of these points, this change removes dependency on Glare.
Deprecation step is skipped to unblock CI jobs.
Also, this change removes the broken lower constraints job. It was
removed from Mistral a while ago[2] from the Mistral repo.
[1] https://opendev.org/x/glare
[2] https://review.opendev.org/c/openstack/mistral/+/770525
Change-Id: Ib6c138e3ce72ce775e29db80a076b9ade37ddaa0
* In the recent version 2.3.0 of mistral-lib there has been added
the new serialization mechanism for actions since the communication
schema between Mistral engine and Mistral remote executor will soon
require it (once merged). All classes for OpenStack actions are
eventually dynamically generated based on the static classes like
NovaAction, HeatAction etc., so to make the serialization work
correctly we have to take this into account. The newly added class
OpenStackActionSerializer takes care of that.
Change-Id: I8d7e2db0b17fb8f055f77363667ca4ab2c501b34
Properly sets up the mistral-extra repository with packaging and testing
setup, in order to add gating in CI.
Change-Id: I204745785e63cc8b1ae47da5cc59eda6da18b722
Depends-On: I5e75914e500837babdeb358a76ec7d90c56f61ac
* "examples" file tree should not be Python packages
* Examples should have their own dependencies, if needed, not centralized
Next steps:
* Prepare a layout for storing OpenStack actions
Depends-on: Id8e5d55e34ec3b3d555b5482e13f99c2561e871e
Partially implements: blueprint mistral-custom-actions-api
Change-Id: Ic5b0f655686361ee00bdb70ea13bc66ce0769f90
argparse was external in python 2.6 but not anymore, remove it from
requirements.
This should help with pip 8.0 that gets confused in this situation.
Installation of the external argparse is not needed.
Change-Id: Ib7e74912b36c1b5ccb514e31fac35efeff57378d