Region name could not specify for target cloud

Bug #1633345 reported by Istvan Imre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Triaged
Low
Unassigned
python-mistralclient
Confirmed
Low
Istvan Imre

Bug Description

In case of a multi-region cloud, user could not choose between different service catalog of different regions.

To support multi-region clouds new parameter (target-region-name) for mistral client would be needed.

Changed in python-mistralclient:
assignee: nobody → Istvan Imre (istvan.imre)
Revision history for this message
Andras Kovi (akovi) wrote :

The server also needs additional functionality to handle this parameter.

Lingxian Kong (kong)
Changed in python-mistralclient:
milestone: none → 2.1.2
importance: Undecided → Low
status: New → Confirmed
Changed in python-mistralclient:
milestone: 2.1.2 → 2.2.0
no longer affects: mistral (Ubuntu)
no longer affects: mistral (Ubuntu)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on mistral (master)

Change abandoned by Lingxian Kong (<email address hidden>) on branch: master
Review: https://review.openstack.org/414059

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Lingxian Kong (<email address hidden>) on branch: master
Review: https://review.openstack.org/407240

Changed in python-mistralclient:
milestone: 3.1.2 → 3.2.0
Changed in mistral:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.