Re: [ovirt-devel] oVirt Node ISO rpm-wrapper update
Il 12/05/2014 13:00, Fabian Deutsch ha scritto:
Hey,
the "wrapper rpm" I am going to talk about is an rpm which contains the Node ISO image which can be used easily with oVirt Engine. yum can be used to update this rpm and retrieve the latest oVirt Node iso for easy consumption.
For some time we did not deliver Node for Engine in a wrapper rpm because a lot of things have changed (see below for the full story).
To get this working again I've been cleaning up the repo and the contained spec.
Th repo layout is now: node-3.0 branch: Builds the base image from scratch
ovirt-3.4 branch: Builds the iso for Engine using edit-node and the base image
Open issues: A repo file needs to be generated on each build which contains all the relevant oVirt repositories.
Sandro, do you have an idea how we can retrieve all list of all relevant oVirt repositories using some curl oneliner?
No, no curl onliner available for that. If you need one, we can provide it.
The repositories are needed by edit-node to pull in the dependencies of ovirt-node-plugin-vdsm (vdsm, gluster, ...).
The changes are _slightly_ tested, and once they are in a better shape we can update Jenkins to use these repos to build the image and rpm for Engine.
Technical background story: The problem was that the basic way of how the oVirt Node for Engine ISO was build was dramatically changed.
Originally the vdsm packages were part of Node's build process. You build the Node and it was usable with Engine.
Now - After we introduced plugins, vdsm was migrated into a plugin (ovirt-node-plugin-vdsm) and the plugin is not part of Node's build process. ISOs we build these days do not contain vdsm specific bits and are called "base images". So if you build Node these days, it is _not_ usable with Engine. Don't Panic.
The ovirt-node-plugin-vdsm is added to the "base image" in a second step using edit-node. This process is now used in ovirt-3.4 branch, where also the spec file for the wrapper-rpm resides.
- fabian
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
--=-Vnh7iLRflli7yaTmPObJ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Montag, den 12.05.2014, 13:13 +0200 schrieb Sandro Bonazzola:
Il 12/05/2014 13:00, Fabian Deutsch ha scritto:
Hey, =20 the "wrapper rpm" I am going to talk about is an rpm which contains the Node ISO image which can be used easily with oVirt Engine. yum can be used to update this rpm and retrieve the latest oVirt Node iso for easy consumption. =20 For some time we did not deliver Node for Engine in a wrapper rpm because a lot of things have changed (see below for the full story). =20 To get this working again I've been cleaning up the repo and the contained spec. =20 Th repo layout is now: node-3.0 branch: Builds the base image from scratch =20 ovirt-3.4 branch: Builds the iso for Engine using edit-node and the base image =20 Open issues: A repo file needs to be generated on each build which= =20 contains all the relevant oVirt repositories. =20 Sandro, do you have an idea how we can retrieve all list of all relevan= t oVirt repositories using some curl oneliner? =20 No, no curl onliner available for that. If you need one, we can provide it.
=20
The repositories are needed by edit-node to pull in the dependencies of ovirt-node-plugin-vdsm (vdsm, gluster, ...). =20 The changes are _slightly_ tested, and once they are in a better shape we can update Jenkins to use these repos to build the image and rpm for Engine. =20 =20 Technical background story: The problem was that the basic way of how the oVirt Node for Engine ISO was build was dramatically changed. =20 Originally the vdsm packages were part of Node's build process. You build the Node and it was usable with Engine. =20 Now - After we introduced plugins, vdsm was migrated into a plugin (ovirt-node-plugin-vdsm) and the plugin is not part of Node's build process. ISOs we build these days do not contain vdsm specific bits and are called "base images". So if you build Node these days, it is _not_ usable with Engine. Don't Panic. =20 The ovirt-node-plugin-vdsm is added to the "base image" in a second ste=
Yes, this would really help us. I opened this ticket to track it: https://fedorahosted.org/ovirt/ticket/136 - fabian p
using edit-node. This process is now used in ovirt-3.4 branch, where also the spec file for the wrapper-rpm resides. =20 - fabian =20 =20 =20
--=-Vnh7iLRflli7yaTmPObJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIbBAABAgAGBQJTc2DZAAoJEC9+uOgSHVGUo2oP9A1NBIquN0/3lmj977MO1VDT L8gjpGck2P+PlEbvAOSslsodqa526huy0+TbP4PrDL4NjwWAi/rMzGO7DGSs8uaP JpeV7yn13DxEdE0c8GlnGITNePoPhNcaqaG9nMgx6AlwWbibeqYgBc9L5W8acNtH Bnregj5iw6mRZ95GW0M1F4ZZvG9fELHoT1QgwQkg+zeDhBHKd4QTSNZaP1KIpotR 2Mg3JYB1e1/1eRmnegcD6pV+idyXT/g6PHjso5LDjaFQssIINFmOJXppgBNAkpFV +PunqS5Mw0wE5fGIkNwNnwxCj7mtaxNz5NEK2hmoZvE3BFWTNi3kG7IMZhhD+gSC OOfAwPqwTBzw5P3Ga8XT+P5SM1YvexACXXBMaNt01mxbqda1imcz5KAxpQadVxDv Zqwnwu+Mur5Bk8XskomjFdwU5r8qFDuAPaNgZF8ifnEVYIrlkV8i4lDrjpwyM9kE 6Vhd6AnuJw/ZtH6jicJx2SDKxfrx/ugxiGN5jI+UUJDxq1tupHXsh68Gs/wEuXTH eQFAAQAZebBWzG3m5dIO4sfacBmwAN7INHP2W4xD3hZpvK+qlfs6xH3pqn2q4k9O T4uXMrXlGSNRlqmgyM6hXf+nzKF4thC0xbb+V3joEN4u6Pd9h+A1CsMeocPbaafH JWj6u9Z0BSWEWx8xs/g= =jGzZ -----END PGP SIGNATURE----- --=-Vnh7iLRflli7yaTmPObJ--
participants (2)
-
Fabian Deutsch -
Sandro Bonazzola