On Tue, Jun 12, 2018 at 4:53 AM, Wladimir Mutel wrote:
> Jason Dillaman wrote:
>
>>> One more question, how should I set profile 'rbd-read-only'
>>> properly
>>> ? I tried to set is for 'client.iso' on both 'iso' and 'jerasure21'
>>> pools,
>>> and this did not work. Set profile on both p
Jason Dillaman wrote:
One more question, how should I set profile 'rbd-read-only' properly
? I tried to set is for 'client.iso' on both 'iso' and 'jerasure21' pools,
and this did not work. Set profile on both pools to 'rbd', it worked. But I
don't want my iso imaged to be accidentally m
On Wed, Jun 6, 2018 at 4:48 PM, Wladimir Mutel wrote:
> Jason Dillaman wrote:
>
The caps for those users looks correct for Luminous and later
clusters. Any chance you are using data pools with the images? It's
just odd that you have enough permissions to open the RBD image but
Jason Dillaman wrote:
The caps for those users looks correct for Luminous and later
clusters. Any chance you are using data pools with the images? It's
just odd that you have enough permissions to open the RBD image but
cannot read its data objects.
Yes, I use erasure-pool as data-po
On Wed, Jun 6, 2018 at 3:02 PM, Wladimir Mutel wrote:
> Jason Dillaman wrote:
>>
>> The caps for those users looks correct for Luminous and later
>> clusters. Any chance you are using data pools with the images? It's
>> just odd that you have enough permissions to open the RBD image but
>> cannot
Jason Dillaman wrote:
The caps for those users looks correct for Luminous and later
clusters. Any chance you are using data pools with the images? It's
just odd that you have enough permissions to open the RBD image but
cannot read its data objects.
Yes, I use erasure-pool as data-pool
The caps for those users looks correct for Luminous and later
clusters. Any chance you are using data pools with the images? It's
just odd that you have enough permissions to open the RBD image but
cannot read its data objects.
On Wed, Jun 6, 2018 at 2:46 PM, Wladimir Mutel wrote:
> Jason Dillama
Jason Dillaman wrote:
Can you run "rbd --id libvirt --pool libvirt win206-test-3tb " w/o error? It sounds like your CephX caps for
client.libvirt are not permitting read access to the image data
objects.
I tried to run 'rbd export' with these params,
but it said it was unable to
Can you run "rbd --id libvirt --pool libvirt win206-test-3tb " w/o error? It sounds like your CephX caps for
client.libvirt are not permitting read access to the image data
objects.
On Wed, Jun 6, 2018 at 2:18 PM, Wladimir Mutel wrote:
>
> Dear all,
>
> I installed QEMU, libvirtd
Dear all,
I installed QEMU, libvirtd and its RBD plugins and now trying
to make QEMU use my Ceph storage. I created 'iso' pool
and imported Windows installation image there (rbd import).
Also I created 'libvirt' pool and there, created 2.7-TB image
10 matches
Mail list logo