fmcwebs opened a new issue #4302:
URL: https://github.com/apache/cloudstack/issues/4302
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
* Improvement Request
##### COMPONENT NAME
UI-Backend
##### CLOUDSTACK VERSION
4.14.0
##### CONFIGURATION
Cloudstack and Ceph object storage configuration.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
About this, we have an erasure code pool at ceph, so we can create an image
and then we must specify where the metadata and data pool is located. When we
add the erasure code pool as Storage in Cloudstack we can't set the datapool,
so when we add a VM it shows an error. We asume that Cloudstack do something
like this in Ceph:
_rbd create DISCO --size 4096 -p PoolErasure_
_rbd: create error: (95) Operation not supported_
**And must be:**
_rbd create --size 4096 --data-pool DataPool PoolErasure/DISCO_
Example:
https://documentation.suse.com/ses/6/html/ses-all/cha-ceph-erasure.html#ec-rbd
There is not a field at Cloudstack to set this, so it fails when creating a
VM in this storage.
In replicated ceph configuration is working fine because there is just one
Pool so you don't need to set more options at Cloudstack.
There is a way to set the data pool at cloudstack in other way?.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
