Add support for enabling consistency group api

Bug #1729675 reported by Benard Okolie
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Cinder Charm
Triaged
Wishlist
Unassigned

Bug Description

In order to get around lp:1647932 we need to be able to modify the policy.json file using juju.

tags: added: canonical-bootstack
Revision history for this message
James Page (james-page) wrote :

I think the feature here is to add support for enabling the consistency group API, rather than to provide direct management of the policy.json (which I remain a -1 on).

Marking as Triaged/Wishlist for now.

summary: - Manage policy.json using juju
+ Add support for enabling consistency group api
Changed in charm-cinder:
status: New → Triaged
importance: Undecided → Wishlist
Seyeong Kim (seyeongkim)
tags: added: sts
Revision history for this message
James Page (james-page) wrote :

I've commented on https://review.openstack.org/#/c/525873 to this effect; enabling support for the CG API should be driven based on the storage backends that form part of the deployment, rather than being a blind configuration option that the user has to enable.

For example, CG's don't have context for our default storage backend (ceph) so it makes no sense to even allow a user to attempt to enable them in this use-case; if say we had a cinder-netapp subordinate charm it *would* make sense to expose CG support on the cinder-netapp charm and use its relation to cinder to instruct the cinder charm to enable the required policy changes.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-cinder (master)

Change abandoned by Seyeong Kim (<email address hidden>) on branch: master
Review: https://review.openstack.org/525873

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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