Comment 4 for bug 1272076
Revision history for this message
| John Griffith (john-griffith) wrote Re: VolumeNotCreated - Instance failed, cinder too slow | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
We need to look at how we do this in Nova. The 66 seconds isn't going to be sufficient in some cases depending on what backend you're using.
The reason for example in your case of LVM:
1 The Cinder volume is created.
2. The image is downloaded from Glance to a temp-file on the cinder node
3. The image is converted to raw and written to the volume
For the 256 MB image I'm kinda sad it's not fast enough, I'd be curious if you timed just the image download in Cinder to see what you come up with? Do a "cinder create --image-id xxxxx 5".
With some setups this process will be pretty quick, but depending on the cinder backend in use, and the load on the system this can end up taking a while. We should probably look at ways to improve how we do this on the Nova side. Time-outs are always tricky though. I would have to look to see if this timeout is already configurable in Nova, if it's not that might be a reasonable temporary solution.
One thing that we're working on in cinder is getting rid of the intermediate temp file to do the convert, but its not simple because you can't do qemu convert in place.