fuel-dev team mailing list archive

[Roman Alekseenkov <ralekseenkov@xxxxxxxxxxxx>]

Ilya,

Thank you for digging into this. I believe we can easily set
"can_set_mount_point" to false in 4.0 to avoid issues. What would be your
recommendation?

Micah, Andrew,

This is the latest issue escalated by University of Hawaii, I believe. Make
sure you team follows the discussion on fuel-dev@.

Thanks,
Roman

On Thursday, December 19, 2013, Ilya Shakhat wrote:

> Hi,
>
> I've got an issue related to configuration of attached volume device name
> in Horizon. That option is not supported by all hypervisors (see
> https://bugs.launchpad.net/nova/+bug/1075971,
> https://bugs.launchpad.net/nova/+bug/1217874 ) and in Icehouse it is
> hidden by default. The visibility of that option is configured by section
> in local_settings.py (
> https://github.com/openstack/horizon/blob/stable/havana/openstack_dashboard/local/local_settings.py.example
> ):
>
> OPENSTACK_HYPERVISOR_FEATURES = {
>     'can_set_mount_point': True,
> }
>
> However In Icehouse the same option is:
>
> # The Xen Hypervisor has the ability to set the mount point for volumes
> # attached to instances (other Hypervisors currently do not). Setting
>
> # can_set_mount_point to True will add the option to set the mount point
> # from the UI.
> OPENSTACK_HYPERVISOR_FEATURES = {
>     'can_set_mount_point': False,
>     'can_set_password': True,
> }
>
> What will be the default value of that option in upcoming Fuel 4.0?
>
> Thanks,
> Ilya
>
> PS. Two more patches related to the same issue with device attachment:
>
>    - https://review.openstack.org/#/c/60261/ - merged into Horizon on Dec
>    12th, it adds a notice "Actual device name may differ due hypervisor
>    settings."
>    - https://review.openstack.org/#/c/60257/4 - on review, the patch
>    introduces warning when hypervisor is not able to attach volume with
>    specified name
>
>
>