Implement cinder "replication-promote" and "replication-reenable" in OSC
Bug #1645559 reported by
aohuanxuan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-openstackclient |
In Progress
|
Undecided
|
aohuanxuan | ||
Bug Description
The commands in CinderClient are below:
usage: cinder replication-promote <volume>
Promote a secondary volume to primary for a relationship.
Positional arguments:
<volume> Name or ID of the volume to promote. The volume should have the
replica volume created with source-replica argument.
usage: cinder replication-
Sync the secondary volume with primary for a relationship.
Positional arguments:
<volume> Name or ID of the volume to reenable replication. The replication-
status of the volume should be inactive.
And planning to implement them in OSC as:
volume set <volume> [--replication-
| Changed in python-openstackclient: | |
| assignee: | nobody → aohuanxuan (huanxuan-ao) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-openstackclient (master) | #1 |
| Changed in python-openstackclient: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on python-openstackclient (master) | #2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/