Notes on enabling consistency groups in devstack:
http://docs.openstack.org/admin-guide/blockstorage-consistency-groups.html
You'll also need to modify the local cinder policy file.
Though that's not actually enough to make it work since
devstack only provides the LVM volume type and CGs don't
work with LVM. You can attempt to create CGs, but they
will error.
Change-Id: I0ab541c81570cd5f67bb7d04c01bc92bc5cc3ab5
Implements: blueprint reorganise-volumes
Manage will take an existing volume created outside of Openstack and
make it available. Unmanage will remove the visibility of a volume
within Openstack, but will not delete the actual volume.
Change-Id: I6df46f0944015833d1fb94611f9bf520ca8bca8b
Implements: blueprint add-manage-unmanage-volume
This reverts commit ed586a0355fb99a5b1fbeadfc0625f0ceffe8b72.
The quota_class subcommand in python-novaclient was used to set default
quota values so it shouldn't have been removed. As now it is being
restored, the defaults quota panel is being restored too.
Related mailing list thread on the topic:
http://lists.openstack.org/pipermail/openstack-dev/2014-May/035383.html
Resolved merge conflicts by hand in:
openstack_dashboard/api/cinder.py
openstack_dashboard/dashboards/admin/info/tabs.py
openstack_dashboard/dashboards/admin/info/tests.py
Updated translatable segments to match refactors in
openstack_dashboard/dashboards/admin/defaults/workflows.py
openstack_dashboard/dashboards/admin/defaults/tables.py
Fixed most egregious post-merge styling errors in
openstack_dashboard/dashboards/admin/defaults/templates/defaults/index.html
(probably should have been separate, but I just couldn't let it out that way!)
Removed unrelated file that was allowed to be part of the original commit
doc/source/topics/settings.rst
Co-Authored-By: Doug Fish <drfish@us.ibm.com>
Change-Id: Ic4c4ecec843c7ea9afd0db36ce0eb15952da15b3
Partial-Bug: #1299517
Expose the functionality of the 'cinder upload-to-image' command
in the UI. It allows user to upload of a volume whose status is
in-use or available to the Glance image service.
When the volume is in-use, user still wants to uploads that volume
to image, user needs to set force to be True. The force checkbox
only shows when the volume is in-use. Whether it can
succesfully upload the volume to image depends on if the storage
array that volume is created in supports attaching multiple instances
to the volume. Not all arrays supports that. There is no api that
can detect if array supports that before cinder actutally uploads
the volume in-use to image.
The container format is 'bare'. The list of disk formats are
based on the format supportability by both glance and qemu-img.
cinder uses qemu-img for converting the volume to a image.
Implements: blueprint cinder-volume-upload-image
Change-Id: Ie5fc26c260e5f4ef2700c40c8cea6150fdbd522c
Expose the functionality of the 'cinder retype' command in the UI.
It allows user to change the volume type of a volume whose status is
in-use or available when horizon's cinder API version is >= 2.
cinder retype is only supported starting cinder v2.
If enabled_backends is specified in /etc/cinder/cinder.conf,
retype is actually performed by a specific driver.
It depends on the drivers (backends) that are associated
with volume types.
Volume types are set through type-key extra specs.
If enabled_backends in cinder.conf is not specified, volumes are
created by LVM so retype is actually performaned in LVM.
During retype, if cinder finds it can not retype, it will check
if the migration policy is on_demand or never. If the policy is
is never, then cinder does not do anything, otherwise, it will
perform migration. By default, in the horizon retype dialog UI,
migration policy is never which is also the default
of the cinder cli command.
Currently in horizon cinder api default version is 1. In order to
test this functionallity, you need to update
openstack_dashboard/local/local_settings.py to have the "volume"
API to use version 2 so the "Change Volume Type" action menu
shows up for the volume. If local_settings.py is not available, you
need to copy the local_settings.py.example file, change it to
local_settings.py, update other necessary settings and also update
have the API version setting like the followings:
OPENSTACK_API_VERSIONS = {
#"data_processing": 1.1,
#"identity": 3,
"volume": 2
}
Implements: blueprint volume-retype
Change-Id: Id8bc539e1849f5910df34d7b76cc250ec82f9671
The default quota panel has been moved to a tab in the system
info panel.
The update default quotas feature has been removed.
The cinder quota-class methods have been removed to keep consistency.
The test cases and the apis for nova and cinder have been modified
according the change.
This change is done to support the change:
I1110022d6f628d03aaf363da707f2d2ef1600437
Change-Id: I193c7209d9681b6d69afe0d996153ac86850d243
Closes-Bug: #1292589
Adding cinder policy rules file for policy checks. Implementing
rule checks as well. Some cinder API calls actually hit nova, so
adding those calls as well.
Also a couple of improvements to the Horizon policy engine. First,
now providing the token scope project_id and user_id as targets by
default, unless otherwise specified. Most service policy rules
check on or both of these. Second, checking to see if rule exists,
before attempting enforcement. If the rule does not exist, using
the default rule for that service. This now matches what the
service policy engines do.
Implements: blueprint block-rbac
Change-Id: Ifef08b8975280f4e621ba8eebec9d405e1e870a2