With Mitaka. When opening "Volume consistency groups" with the following URL in dashboard, it gives an error as "Error: Unable to retrieve volume consistency groups."
http://<dashboard_vip>/project/volumes/?tab=volumes_and_snapshots__cgroups_tab
/var/log/apache2/error.log
[Wed Apr 19 12:45:56.936280 2017] [wsgi:error] [pid 48241:tid 140295558567680] Recoverable error: Policy doesn't allow consistencygroup:get_all to be performed. (HTTP 403) (Request-ID: req-2eaacdc2-25c6-43ce-b4de-f0fafcac3ceb)
According to the /etc/cinder/policy.json, no one allows to see consistencygroup. It would be nice if the charm allows to modify policy.json to enable the "volume consistency groups" feature: https://docs.openstack.org/admin-guide/blockstorage-consistency-groups.html
"consistencygroup:create" : "group:nobody",
"consistencygroup:delete": "group:nobody",
"consistencygroup:update": "group:nobody",
"consistencygroup:get": "group:nobody",
"consistencygroup:get_all": "group:nobody",
"consistencygroup:create_cgsnapshot" : "group:nobody",
"consistencygroup:delete_cgsnapshot": "group:nobody",
"consistencygroup:get_cgsnapshot": "group:nobody",
"consistencygroup:get_all_cgsnapshots": "group:nobody",
Rather than add yet-another- config- toggle to the openstack dashboard charm, I'd prefer to deal with this via the service-discovery spec we have in-flight for the queens development cycle; cinder can use this feature to expose whether consistency-groups are supported to any service in the cloud, including the dashboard, which can then enable/disable features accordingly.