Add support to execute workflows on arbitrary clouds

Registered by Andras Kovi on 2016-05-26

Mistral is configured to execute workflows on a specific cloud (VIM (Virtual
Infrastructure Manager) in ETSI MANO terms). In order to execute workflows on a
different cloud one needs to start a new Mistral instance with the cloud
specific configuration. When Mistral is used in standalone mode, this is an
undesired overhead and can cause unpredictable resource usage patterns.

This blueprint proposes to extend the workflow execution parameters to make it
possible to target a specific cloud without modifying the configuration of the
Mistral service.

rakhmerov: Just an addition. This is also needed for scenarios when we want to
manage/orchestrate activities happening in different clouds, aka cross-cloud
orchestration.

Blueprint information

Status:
Complete
Approver:
Renat Akhmerov
Priority:
High
Drafter:
Andras Kovi
Direction:
Approved
Assignee:
None
Definition:
New
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
None
Started by
Renat Akhmerov
Completed by
Renat Akhmerov

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-multi-vim-support,n,z

Addressed by: https://review.openstack.org/319868
    Execute workflows on targeted cloud

Addressed by: https://review.openstack.org/330469
    Use client credentials to retrieve service list

Gerrit topic: https://review.openstack.org/#q,topic:bp/bp,n,z

Addressed by: https://review.openstack.org/339349
    Add target parameters to REST API

Addressed by: https://review.openstack.org/351536
    Add target-* parameters to python-mistralclient

Addressed by: https://review.openstack.org/356567
    Update documentation for multi-vim-support

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.