Re: [ovirt-devel] ovirt-appliance (today) is 1.5G...

We may also want to do this with Node/RHV-H eventually (since the updates there are already 500MB). I don't think we currently ship deltarpm on RHV-H, but it's a very small addition. The question is whether makedeltarpm can actually do anything meaningful with something which is already a sparsified image wrapped in an RPM, but I'll test... On Sun, Oct 9, 2016 at 6:35 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
FYI
---------- Forwarded message ---------- From: Yaniv Kaul <ykaul@redhat.com> Date: Thu, Oct 6, 2016 at 11:13 AM Subject: [ovirt-devel] ovirt-appliance (today) is 1.5G... To: devel <devel@ovirt.org>
I'm sure it was less just days ago, but now[1] it is again quite big. 4.0's is 'only' 1G in size[2]. Which anyway raises the question - should we provide delta RPMs for it?
Thanks, Y.
[1] http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm /el7/noarch/ovirt-engine-appliance-4.1-20160927.1.el7.centos.noarch.rpm [2] http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el 7/noarch/ovirt-engine-appliance-4.0-20161003.1.el7.centos.noarch.rpm
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

Just a comment -- Cursory testing shows that makedeltarpm is not good at this -- it doesn't know how to examine the contents of the OVA (or they're too different). The delta RPM between 4.0 (~1GB) and 4.1-pre (~1.45GB) is 1.41GB. With or without -r It may take a little more tweaking, but the options for "makedeltarpm" are pretty sparse. We can try talking to the maintainer this week also... On Sun, Oct 9, 2016 at 4:00 PM, Ryan Barry <rbarry@redhat.com> wrote:
We may also want to do this with Node/RHV-H eventually (since the updates there are already 500MB).
I don't think we currently ship deltarpm on RHV-H, but it's a very small addition. The question is whether makedeltarpm can actually do anything meaningful with something which is already a sparsified image wrapped in an RPM, but I'll test...
On Sun, Oct 9, 2016 at 6:35 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
FYI
---------- Forwarded message ---------- From: Yaniv Kaul <ykaul@redhat.com> Date: Thu, Oct 6, 2016 at 11:13 AM Subject: [ovirt-devel] ovirt-appliance (today) is 1.5G... To: devel <devel@ovirt.org>
I'm sure it was less just days ago, but now[1] it is again quite big. 4.0's is 'only' 1G in size[2]. Which anyway raises the question - should we provide delta RPMs for it?
Thanks, Y.
[1] http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm /el7/noarch/ovirt-engine-appliance-4.1-20160927.1.el7.centos.noarch.rpm [2] http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el 7/noarch/ovirt-engine-appliance-4.0-20161003.1.el7.centos.noarch.rpm
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

On Mon, Oct 10, 2016 at 2:18 AM, Ryan Barry <rbarry@redhat.com> wrote:
Just a comment --
Cursory testing shows that makedeltarpm is not good at this -- it doesn't know how to examine the contents of the OVA (or they're too different). The delta RPM between 4.0 (~1GB) and 4.1-pre (~1.45GB) is 1.41GB. With or without -r
Yep - deltarpm uses bsdiff and they struggle to diff so large binary files. If we had a different deliverable - like a tarball - then bsdiff could make sense. But a qcow is not an ideal format for doing a binary diff. Btw a squashfs is also not suitable for bdiff. - fabian
It may take a little more tweaking, but the options for "makedeltarpm" are pretty sparse. We can try talking to the maintainer this week also...
On Sun, Oct 9, 2016 at 4:00 PM, Ryan Barry <rbarry@redhat.com> wrote:
We may also want to do this with Node/RHV-H eventually (since the updates there are already 500MB).
I don't think we currently ship deltarpm on RHV-H, but it's a very small addition. The question is whether makedeltarpm can actually do anything meaningful with something which is already a sparsified image wrapped in an RPM, but I'll test...
On Sun, Oct 9, 2016 at 6:35 AM, Doron Fediuck <dfediuck@redhat.com> wrote:
FYI
---------- Forwarded message ---------- From: Yaniv Kaul <ykaul@redhat.com> Date: Thu, Oct 6, 2016 at 11:13 AM Subject: [ovirt-devel] ovirt-appliance (today) is 1.5G... To: devel <devel@ovirt.org>
I'm sure it was less just days ago, but now[1] it is again quite big. 4.0's is 'only' 1G in size[2]. Which anyway raises the question - should we provide delta RPMs for it?
Thanks, Y.
[1] http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ovirt-en... [2] http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el7/noarch/ovirt-engin...
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Fabian Deutsch <fdeutsch@redhat.com> Associate Manager, RHV Hypervisor Red Hat
participants (2)
-
Fabian Deutsch
-
Ryan Barry