Bug 1314099 - virsh requires secret key and mon ip for rbd disk for ceph client
virsh requires secret key and mon ip for rbd disk for ceph client
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt (Show other bugs)
7.2
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Peter Krempa
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-02 18:04 EST by Vasu Kulkarni
Modified: 2016-03-24 09:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-24 09:22:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vasu Kulkarni 2016-03-02 18:04:25 EST
Description of problem:

when defining a RBD disk option using virsh one needs to add monitor_ip and secret key, this option is not required when starting the vm using qemu-kvm cli on ceph client, Also sometimes mon ip's can change, I believe this option should be simplified and one should just provide the rbd disk image name in case of ceph clients.

<disk type='network' device='disk'>
        <source protocol='rbd' name='libvirt-pool/new-libvirt-image'>
                <host name='{monitor-host}' port='6789'/>
        </source>
        <target dev='vda' bus='virtio'/>
</disk>

</source>
<auth username='libvirt'>
        <secret type='ceph' uuid='9ec59067-fdbc-a6c0-03ff-df165c0587b8'/>
</auth>
<target ...

Version-Release number of selected component (if applicable):
1.2.17

How reproducible:
n/a
Comment 2 Peter Krempa 2016-03-24 09:22:39 EDT
I think that would not be a desired thing to do.

Allowing to use the defaults for ceph that are taken from the system-wide config file will make configurations unstable when the config file changes or the machines are migrated to a different host with a different config. Keeping the data in libvirt enforces that the configuration of a VM is stable in regard to external influence.

I'm closing this as WONTFIX.

Note You need to log in before you can comment on or make changes to this bug.