Re: [Openstack-operators] custom build image is slow

[Paras pradhan]

It does have the virtio drivers and the image file is qcow2 not raw.  To
narrow down the issue this is what I have done.

1) Download CentOS-7-x86_64-GenericCloud.qcow2 from centos.org. Upload to
glance and while creating a volume in cinder volume.log I see 250MB/sec
download speed. This is normal in our case.

2) Now boot the qcow2 using kvm/virt-manager , add packages, poweroff and
upload it to glance , I see 75MB/sec download speed while creating a
volume. If I do virt sparsify it then drops to 30MB/sec.

Not sure why I am seeing this behaviour.

Thanks
Paras.

On Wed, Aug 2, 2017 at 2:25 AM, Van Leeuwen, Robert 
wrote:

> >> how do we install virtio drivers if its missing? How do I verify it on
> the centos cloud image if its there?
>
>
>
> >Unless it’s a very very ancient unsupported version of centos the virt-io
> drivers will be in the kernel package.
>
> >Do a lsmod and look for virtio to check if it is loaded.
>
>
>
> Forgot to mention: I do not think this will have anything to do with the
> upload speed to cinder even if it is not there.
>
>
>
> Cheers,
>
> Robert van Leeuwen
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Van Leeuwen, Robert]

>> how do we install virtio drivers if its missing? How do I verify it on the 
>> centos cloud image if its there?

>Unless it’s a very very ancient unsupported version of centos the virt-io 
>drivers will be in the kernel package.
>Do a lsmod and look for virtio to check if it is loaded.

Forgot to mention: I do not think this will have anything to do with the upload 
speed to cinder even if it is not there.

Cheers,
Robert van Leeuwen
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Van Leeuwen, Robert]

> how do we install virtio drivers if its missing? How do I verify it on the 
> centos cloud image if its there?

Unless it’s a very very ancient unsupported version of centos the virt-io 
drivers will be in the kernel package.
Do a lsmod and look for virtio to check if it is loaded.

Regarding the slower speed of the custom image:
First check if they are really the same file format and one is not secretly a 
raw file:
file centos.qcow2

I would expect the virt-sparsify to be indeed the way to go.
Although I think that cinder will convert it to raw for you and you probably 
want that for ceph (IIRC it is a setting).
It might be that the centos downloaded file is actually RAW so it does not need 
to convert that.

You can also check the cinder server debug log / load or ceph load to see if 
something is bottlenecked during the upload to maybe get a hint to what the 
problem is.

Cheers,
Robert van Leeuwen
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Paras pradhan]

how do we install virtio drivers if its missing? How do I verify it on the
centos cloud image if its there?

On Tue, Aug 1, 2017 at 12:19 PM, Abel Lopez <alopg...@gmail.com> wrote:

> Your custom image is likely missing the virtIO drivers that the cloud
> image has.
>
> Instead of running through the DVD installer, I'd suggest checking out
> diskimage-builder to make custom images for use on Openstack.
>
> On Tue, Aug 1, 2017 at 10:16 AM Paras pradhan <pradhanpa...@gmail.com>
> wrote:
>
>> Also this is what I've noticed with the centos cloud image I downloaded.
>> If I add few packages( around a GB), the sizes goes up to 8GB from 1.3 GB.
>> Running dd if=/dev/zero of=temp;sync;rm temp failed due to the size of
>> the disk on the cloud images which is 10G. zeroing failed with No space
>> left on device.  Any other options?
>>
>> Thanks
>> Paras.
>>
>> On Tue, Aug 1, 2017 at 9:43 AM, Paras pradhan <pradhanpa...@gmail.com>
>> wrote:
>>
>>> I ran virt-sparsify. So before running virt-sparsify it was 6.0GB and
>>> after it is 1.3GB.
>>>
>>> Thanks
>>> Paras.
>>>
>>> On Tue, Aug 1, 2017 at 2:53 AM, Tomáš Vondra <von...@homeatcloud.cz>
>>> wrote:
>>>
>>>> Hi!
>>>>
>>>> How big are the actual image files? Because qcow2 is a sparse format,
>>>> it does not store zeroes. If the free space in one image is zeroed out, it
>>>> will convert much faster. If that is the problem, use „dd if=/dev/zero
>>>> of=temp;sync;rm temp“ or zerofree.
>>>>
>>>> Tomas
>>>>
>>>>
>>>>
>>>> *From:* Paras pradhan [mailto:pradhanpa...@gmail.com]
>>>> *Sent:* Monday, July 31, 2017 11:54 PM
>>>> *To:* openstack-operators@lists.openstack.org
>>>> *Subject:* [Openstack-operators] custom build image is slow
>>>>
>>>>
>>>>
>>>> Hello
>>>>
>>>>
>>>>
>>>> I have two qcow2 images uploaded to glance. One is CentOS 7 cloud image
>>>> downloaded from centos.org.  The other one is custom built using
>>>> CentOS 7.DVD.  When I create cinder volumes from them, volume creation from
>>>> the custom built image it is very very slow.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> CenOS qcow2:
>>>>
>>>>
>>>>
>>>> 2017-07-31 21:42:44.287 881609 INFO cinder.image.image_utils
>>>> [req-ea2d7b12-ae9e-45b2-8b4b-ea8465497d5a
>>>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf
>>>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d
>>>> default] *Converted 8192.00 MB image at 253.19 MB/s*
>>>>
>>>>
>>>>
>>>> Custom built qcow2:
>>>>
>>>> INFO cinder.image.image_utils [req-032292d8-1500-474d-95c7-2e8424e2b864
>>>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf
>>>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d
>>>> default] *Converted 10240.00 MB image at 32.22 MB/s*
>>>>
>>>>
>>>>
>>>> I used the following command to create the qcow2 file
>>>>
>>>> qemu-img create -f qcow2 custom.qcow2 10G
>>>>
>>>>
>>>>
>>>> What am I missing ?
>>>>
>>>>
>>>>
>>>> Thanks
>>>> Paras.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Abel Lopez]

Your custom image is likely missing the virtIO drivers that the cloud image
has.

Instead of running through the DVD installer, I'd suggest checking out
diskimage-builder to make custom images for use on Openstack.

On Tue, Aug 1, 2017 at 10:16 AM Paras pradhan <pradhanpa...@gmail.com>
wrote:

> Also this is what I've noticed with the centos cloud image I downloaded.
> If I add few packages( around a GB), the sizes goes up to 8GB from 1.3 GB.
> Running dd if=/dev/zero of=temp;sync;rm temp failed due to the size of
> the disk on the cloud images which is 10G. zeroing failed with No space
> left on device.  Any other options?
>
> Thanks
> Paras.
>
> On Tue, Aug 1, 2017 at 9:43 AM, Paras pradhan <pradhanpa...@gmail.com>
> wrote:
>
>> I ran virt-sparsify. So before running virt-sparsify it was 6.0GB and
>> after it is 1.3GB.
>>
>> Thanks
>> Paras.
>>
>> On Tue, Aug 1, 2017 at 2:53 AM, Tomáš Vondra <von...@homeatcloud.cz>
>> wrote:
>>
>>> Hi!
>>>
>>> How big are the actual image files? Because qcow2 is a sparse format, it
>>> does not store zeroes. If the free space in one image is zeroed out, it
>>> will convert much faster. If that is the problem, use „dd if=/dev/zero
>>> of=temp;sync;rm temp“ or zerofree.
>>>
>>> Tomas
>>>
>>>
>>>
>>> *From:* Paras pradhan [mailto:pradhanpa...@gmail.com]
>>> *Sent:* Monday, July 31, 2017 11:54 PM
>>> *To:* openstack-operators@lists.openstack.org
>>> *Subject:* [Openstack-operators] custom build image is slow
>>>
>>>
>>>
>>> Hello
>>>
>>>
>>>
>>> I have two qcow2 images uploaded to glance. One is CentOS 7 cloud image
>>> downloaded from centos.org.  The other one is custom built using CentOS
>>> 7.DVD.  When I create cinder volumes from them, volume creation from the
>>> custom built image it is very very slow.
>>>
>>>
>>>
>>>
>>>
>>> CenOS qcow2:
>>>
>>>
>>>
>>> 2017-07-31 21:42:44.287 881609 INFO cinder.image.image_utils
>>> [req-ea2d7b12-ae9e-45b2-8b4b-ea8465497d5a
>>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf
>>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d
>>> default] *Converted 8192.00 MB image at 253.19 MB/s*
>>>
>>>
>>>
>>> Custom built qcow2:
>>>
>>> INFO cinder.image.image_utils [req-032292d8-1500-474d-95c7-2e8424e2b864
>>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf
>>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d
>>> default] *Converted 10240.00 MB image at 32.22 MB/s*
>>>
>>>
>>>
>>> I used the following command to create the qcow2 file
>>>
>>> qemu-img create -f qcow2 custom.qcow2 10G
>>>
>>>
>>>
>>> What am I missing ?
>>>
>>>
>>>
>>> Thanks
>>> Paras.
>>>
>>>
>>>
>>>
>>>
>>
>>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Paras pradhan]

Also this is what I've noticed with the centos cloud image I downloaded. If
I add few packages( around a GB), the sizes goes up to 8GB from 1.3 GB.
Running dd if=/dev/zero of=temp;sync;rm temp failed due to the size of the
disk on the cloud images which is 10G. zeroing failed with No space left on
device.  Any other options?

Thanks
Paras.

On Tue, Aug 1, 2017 at 9:43 AM, Paras pradhan <pradhanpa...@gmail.com>
wrote:

> I ran virt-sparsify. So before running virt-sparsify it was 6.0GB and
> after it is 1.3GB.
>
> Thanks
> Paras.
>
> On Tue, Aug 1, 2017 at 2:53 AM, Tomáš Vondra <von...@homeatcloud.cz>
> wrote:
>
>> Hi!
>>
>> How big are the actual image files? Because qcow2 is a sparse format, it
>> does not store zeroes. If the free space in one image is zeroed out, it
>> will convert much faster. If that is the problem, use „dd if=/dev/zero
>> of=temp;sync;rm temp“ or zerofree.
>>
>> Tomas
>>
>>
>>
>> *From:* Paras pradhan [mailto:pradhanpa...@gmail.com]
>> *Sent:* Monday, July 31, 2017 11:54 PM
>> *To:* openstack-operators@lists.openstack.org
>> *Subject:* [Openstack-operators] custom build image is slow
>>
>>
>>
>> Hello
>>
>>
>>
>> I have two qcow2 images uploaded to glance. One is CentOS 7 cloud image
>> downloaded from centos.org.  The other one is custom built using CentOS
>> 7.DVD.  When I create cinder volumes from them, volume creation from the
>> custom built image it is very very slow.
>>
>>
>>
>>
>>
>> CenOS qcow2:
>>
>>
>>
>> 2017-07-31 21:42:44.287 881609 INFO cinder.image.image_utils
>> [req-ea2d7b12-ae9e-45b2-8b4b-ea8465497d5a e090e605170a778610438bfabad7aa
>> 7764d0a77ef520ae392e2b59074c9f88cf 490910c1d4e1486d8e3a62d7c0ae698e -
>> d67a18e70dd9467db25b74d33feaad6d default] *Converted 8192.00 MB image at
>> 253.19 MB/s*
>>
>>
>>
>> Custom built qcow2:
>>
>> INFO cinder.image.image_utils [req-032292d8-1500-474d-95c7-2e8424e2b864
>> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf
>> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d
>> default] *Converted 10240.00 MB image at 32.22 MB/s*
>>
>>
>>
>> I used the following command to create the qcow2 file
>>
>> qemu-img create -f qcow2 custom.qcow2 10G
>>
>>
>>
>> What am I missing ?
>>
>>
>>
>> Thanks
>> Paras.
>>
>>
>>
>>
>>
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Paras pradhan]

I ran virt-sparsify. So before running virt-sparsify it was 6.0GB and after
it is 1.3GB.

Thanks
Paras.

On Tue, Aug 1, 2017 at 2:53 AM, Tomáš Vondra <von...@homeatcloud.cz> wrote:

> Hi!
>
> How big are the actual image files? Because qcow2 is a sparse format, it
> does not store zeroes. If the free space in one image is zeroed out, it
> will convert much faster. If that is the problem, use „dd if=/dev/zero
> of=temp;sync;rm temp“ or zerofree.
>
> Tomas
>
>
>
> *From:* Paras pradhan [mailto:pradhanpa...@gmail.com]
> *Sent:* Monday, July 31, 2017 11:54 PM
> *To:* openstack-operators@lists.openstack.org
> *Subject:* [Openstack-operators] custom build image is slow
>
>
>
> Hello
>
>
>
> I have two qcow2 images uploaded to glance. One is CentOS 7 cloud image
> downloaded from centos.org.  The other one is custom built using CentOS
> 7.DVD.  When I create cinder volumes from them, volume creation from the
> custom built image it is very very slow.
>
>
>
>
>
> CenOS qcow2:
>
>
>
> 2017-07-31 21:42:44.287 881609 INFO cinder.image.image_utils
> [req-ea2d7b12-ae9e-45b2-8b4b-ea8465497d5a e090e605170a778610438bfabad7aa
> 7764d0a77ef520ae392e2b59074c9f88cf 490910c1d4e1486d8e3a62d7c0ae698e -
> d67a18e70dd9467db25b74d33feaad6d default] *Converted 8192.00 MB image at
> 253.19 MB/s*
>
>
>
> Custom built qcow2:
>
> INFO cinder.image.image_utils [req-032292d8-1500-474d-95c7-2e8424e2b864
> e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf
> 490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d
> default] *Converted 10240.00 MB image at 32.22 MB/s*
>
>
>
> I used the following command to create the qcow2 file
>
> qemu-img create -f qcow2 custom.qcow2 10G
>
>
>
> What am I missing ?
>
>
>
> Thanks
> Paras.
>
>
>
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] custom build image is slow

[Tomáš Vondra]

Hi!

How big are the actual image files? Because qcow2 is a sparse format, it does 
not store zeroes. If the free space in one image is zeroed out, it will convert 
much faster. If that is the problem, use „dd if=/dev/zero of=temp;sync;rm temp“ 
or zerofree.

Tomas

 

From: Paras pradhan [mailto:pradhanpa...@gmail.com] 
Sent: Monday, July 31, 2017 11:54 PM
To: openstack-operators@lists.openstack.org
Subject: [Openstack-operators] custom build image is slow

 

Hello

 

I have two qcow2 images uploaded to glance. One is CentOS 7 cloud image 
downloaded from centos.org.  The other one is custom built using CentOS 7.DVD.  
When I create cinder volumes from them, volume creation from the custom built 
image it is very very slow.

 

 

CenOS qcow2:

 

2017-07-31 21:42:44.287 881609 INFO cinder.image.image_utils 
[req-ea2d7b12-ae9e-45b2-8b4b-ea8465497d5a 
e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf 
490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d default] 
Converted 8192.00 MB image at 253.19 MB/s

 

Custom built qcow2:

INFO cinder.image.image_utils [req-032292d8-1500-474d-95c7-2e8424e2b864 
e090e605170a778610438bfabad7aa7764d0a77ef520ae392e2b59074c9f88cf 
490910c1d4e1486d8e3a62d7c0ae698e - d67a18e70dd9467db25b74d33feaad6d default] 
Converted 10240.00 MB image at 32.22 MB/s

 

I used the following command to create the qcow2 file

qemu-img create -f qcow2 custom.qcow2 10G

 

What am I missing ?

 

Thanks
Paras.

 

 

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators