https://review.openstack.org/#/c/383617/ updates the retry policy
and is a huge change for some of the workflows. Hence, adding a
releasenote.
Change-Id: I86d88d80c3fbcba098d41671f3131f68d10fac03
Due to how microversioning works in the Ironic client, it is not possible
to use API features introduced in API version 1.10 and later from Mistral,
as the default version is 1.9 (mid-Liberty). This change bumps the required
API version to 1.22 (Newton final).
See the following link for the full API version history:
http://docs.openstack.org/developer/ironic/dev/webapi-version-history.html
Change-Id: I1c605fc00efe5fe8956d6547ea5e85e6e1172c9b
User now could define the region for the openstack actions.
It could be done via API in X-Region-Name and X-Target-Region-Name
in case of multi-vim feature is used.
*API change*
X-Region-Name: Header added to execution create
X-Target-Region-Name: Header added to execution create
Change-Id: Icbf63962a481c1282b95359894fa6245e0e97bac
Related-Bug: #1633345
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Note that this repository might not get translated release notes - or
no translations at all - but we add the entry here nevertheless to
prepare for it.
Change-Id: Iccf6d4dcd310d7834fc0259f47e3b04c8951cb72
In order to support automatically updating the release notes when we
create stable branches, we want the pages to be in a standard order.
This patch updates the order to be reverse chronological, so the most
recent notes appear at the top.
Change-Id: Ib364dcc8eb31275a31c83b68d7914263b183e393
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add an API that gets an ad-hoc action DSL and validates it.
This is done in the same way workflows are validated today.
Change-Id: Ibbb949ef38befae1ef83a2a56cda4c817ceb41d4
Implements: blueprint validate-ad-hoc-action-api
- New service actions support, remove the separated ones.
- Workflow sharing feature.
- Usage of workflow UUID.
Change-Id: Ia082fc0b70dbad62e1224e8ebe252677d5372c3a
Release note has been added for pre-installed
mistral docker image.
Change-Id: Iaaeb381e515c0ed8cd45efad245dde257731ce05
Partially-implements: blueprint mistral-docker-image
The state of a workflow execution was not updated even when all task
executions were completed if some tasks finished at the same time as
other tasks.
Because we were using our connections with transaction isolation
level = REPEATABLE_READ - Each process was using a snapshot of the DB
created at the first read statement in that transaction.
When a task finished and evaluated the state of all the other tasks
it did not see the up-to-date state of those tasks - and so, because
not all tasks were completed - the task did not change the workflow
execution state.
Similar behavior happened with multiple action executions under same
task. On completion, each action execution checked the status of the
other action executions and did not see the up-to-date state of these
action execution - causing task execution to stay in RUNNING state.
Change-Id: I12f66134d92b8ed39df9d6128d7de5ee49aa8623
Closes-Bug: #1518012
Closes-Bug: #1513456