Open Stack

On Fri, Nov 27, 2020 at 3:16 PM Dmitry Tantsur <dtantsur at redhat.com> wrote:

> Hi,
>
> On Fri, Nov 27, 2020 at 2:00 PM Sergii Golovatiuk <sgolovat at redhat.com>
> wrote:
>
>> Hi,
>>
>> LZMA causes very high CPU and memory usage for creating images, leaving
>> less resources for other processes. If Ironic is running alongside with
>> other services that may cause significant impact for them. I would leave
>> gzip option as default, would introduce --lzma as well as --gzip and use
>> lzma on 5-10% of our CI resources to test how it goes. Then after a
>> significant amount of testing we could turn it on as default. Proper
>> deprecation should be applied here as well IMHO.
>>
>
>
+1 to make it optional. Five or even ten minutes (per the testing by Arne++
earlier in this thread) is a long time for some of the tripleo jobs which
are running close to the 3 hour limit; for example we had to make some
adjustment [1] recently for the standalone-upgrade job because of timeouts.



> LZMA packing won't happen on ironic nodes. The images are pre-built and
> only unpacked on the target machines.
>
> Or does TripleO build images every time?
>

No the CI jobs use images pulled from the ipa_image_url defined in [2]
(that is for centos8 master, there are equivalent release files & image_url
defined for the stable/*). Those are put there by the periodic buildimage-*
jobs e.g. [3].

thanks, marios

[1]
https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/762674
[2]
https://opendev.org/openstack/tripleo-quickstart/src/commit/fd092aa4b6a902381b3b700fdadb463649686067/config/release/tripleo-ci/CentOS-8/master.yml#L47
[3]
https://review.rdoproject.org/zuul/builds?job_name=periodic-tripleo-centos-8-buildimage-ironic-python-agent-master&job_name=periodic-tripleo-centos-8-buildimage-overcloud-full-master


> Dmitry
>
>
>>
>> чт, 26 нояб. 2020 г. в 17:57, Dmitry Tantsur <dtantsur at redhat.com>:
>>
>>> Hi folks,
>>>
>>> I've been playing with ways to reduce the size of our IPA images. While
>>> package removals can only save us tens of megabytes, switching from gzip to
>>> lzma reduces the size by around a third (from 373M to 217M in my testing).
>>>
>>> What's the caveat? The unpacking time increases VERY substantially. On
>>> my nested virt lab the 217M image took around 5 minutes to unpack. I'm not
>>> sure how much it will impact real bare metal, please feel free to test
>>> https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/764371
>>> and tell me.
>>>
>>> So, what do you think? Switching to lzma by default will likely affect
>>> CI run time (assuming we still have DIB jobs somewhere...) and development
>>> environments, but it will also provide a visible reduction in the image
>>> size (which benefit all environments). Large TripleO images may
>>> particularly benefit from this (but also particularly affected by the
>>> unpacking time).
>>>
>>> Feedback is very welcome.
>>>
>>> Dmitry
>>>
>>> --
>>> Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
>>> Commercial register: Amtsgericht Muenchen, HRB 153243,
>>> Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael
>>> O'Neill
>>>
>>
>>
>> --
>> Sergii Golovatiuk
>>
>> Senior Software Developer
>>
>> Red Hat  <https://www.redhat.com/>
>> <https://www.redhat.com/>
>>
>
>
> --
> Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
> Commercial register: Amtsgericht Muenchen, HRB 153243,
> Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael
> O'Neill
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201130/ccdff6a6/attachment-0001.html>