| *** mhen_ is now known as mhen | 01:17 | |
| *** rlandy|out is now known as rlandy | 10:37 | |
| *** lifeless_ is now known as lifeless | 13:51 | |
| bl0m1 | Hello, I have noticed when creating cinder volumes from image the entire volume is written by cinder. This does not happen when creating an empty volume. Is there any way to configure this? I use solidfire as a backend. | 14:46 |
|---|---|---|
| bl0m1 | The short problem is when creating a volume that is around 1,5 TB or larger server creation times out since the volume takes over 300 seconds to become available. When inspecting the process closer the volume is created and attached to the cinder api container, then cinder writes the entire disc and in the end applies the image. | 14:46 |
| bl0m1 | The wierd thing is that the process happening before the image is written (when cinder prepares/checks?) the volume takes roughly around the same time even if I provision a disc with double the IOPS. | 14:46 |
| bl0m1 | I'm running Openstack train with latest cinder commit | 14:46 |
| frickler | bl0m1: maybe try to ask in the #openstack-cinder channel or send a mail to the mailing-list if you don't get an answer | 14:55 |
| lowercase | bl0m1: Train is in extended maintenance, it would be best if you were to upgrade. | 15:40 |
| lowercase | bl0m1: sounds like you could configure your instances to thinly provision your vms | 15:42 |
| lowercase | bl0m1: https://docs.openstack.org/cinder/latest/contributor/thin_provisioning.html | 15:42 |
| *** rlandy is now known as rlandy|brb | 19:24 | |
| *** rlandy|brb is now known as rlandy | 20:07 | |
| *** timburke__ is now known as timburke | 20:46 | |
| bl0m1 | Thanks alot for your replies, I will look into the thin provisioning tomorrow or checking the cinder channel/mailing list :) | 21:05 |
| *** rlandy is now known as rlandy|out | 21:32 | |
| *** EugenMayer4 is now known as EugenMayer | 21:39 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!