- Devel - oVirt List Archives

[QE] oVirt 3.5.0 Alpha status
by Sandro Bonazzola 14 May '14

14 May '14

Hi, We're going to start composing oVirt 3.5.0 Alpha on 2014-05-16 08:00 UTC from master branches. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1001100 integration NEW Add log gathering for a new ovirt module (External scheduler) 1073944 integration ASSIGNED Add log gathering for a new ovirt module (External scheduler) 1060198 integration NEW [RFE] add support for Fedora 20 Feature freeze has been postponed to 2014-05-30 and the following features should be testable in 3.5.0 Alpha according to Features Status Table [2] Group oVirt BZ Title gluster 1096713 Monitoring (UI plugin) Dashboard (Integrated with Nagios monitoring) infra 1090530 [RFE] Please add host count and guest count columns to "Clusters" tab in webadmin infra 1054778 [RFE] Allow to perform fence operations from a host in another DC infra 1090803 [RFE] Change the "Slot" field to "Service Profile" when cisco_ucs is selected as the fencing type infra 1090511 [RFE] Improve fencing robustness by retrying failed attempts infra 1090794 [RFE] Search VMs based on MAC address from web-admin portal infra 1090793 consider the event type while printing events to engine.log infra 1090796 [RFE] Re-work engine ovirt-node host-deploy sequence infra 1090798 [RFE] Admin GUI - Add host uptime information to the "General" tab infra 1090808 [RFE] Ability to dismiss alerts and events from web-admin portal infra-api 1090797 [RFE] RESTAPI: Add /tags sub-collection for Template resource infra-dwh 1091686 prevent OutOfMemoryError after starting the dwh service. network 1078836 Add a warning when adding display network network 1079719 Display of NIC Slave/Bond fault on Event Log network 1080987 Support ethtool_opts functionality within oVirt storage 1054241 Store OVF on any domains storage 1083312 Disk alias recycling in web-admin portal ux 1064543 oVirt new look and feel [PatternFly adoption] - phase #1 virt 1058832 Allow to clone a (down) VM without snapshot/template virt 1031040 can't set different keymap for vnc via runonce option virt 1043471 oVirt guest agent for SLES virt 1083049 add progress bar for vm migration virt 1083065 EL 7 guest compatibility virt 1083059 "Instance types (new template handling) - adding flavours" virt Allow guest serial number to be configurable virt 1047624 [RFE] support BIOS boot device menu virt 1083129 allows setting netbios name, locale, language and keyboard settings for windows vm's virt 1038632 spice-html5 button to show debug console/output window virt 1080002 [RFE] Enable user defined Windows Sysprep file done Some more features may be included since they were near to be completed on last sync meeting. The table will be updated on next sync meeting scheduled for 2014-05-14. There are still 383 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 321 bugs [4] targeted to 3.5.0. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-05-16 08:00 UTC if needed, otherwise nightly snapshot will be taken. - If you find a blocker bug please remember to add it to the tracker [1] - Please start filling release notes, the page has been created here [5] All users: - You're welcome to join us testing this alpha release and getting involved in oVirt Quality Assurance[6]! [1] http://bugzilla.redhat.com/1073943 [2] http://bit.ly/17qBn6F [3] http://red.ht/1pVEk7H [4] http://red.ht/1rLCJwF [5] http://www.ovirt.org/OVirt_3.5_Release_Notes [6] http://www.ovirt.org/OVirt_Quality_Assurance Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

improving VDSM error reporting
by Yoav Kleinberger 14 May '14

14 May '14

Hi all, This idea was born from this bug: https://bugzilla.redhat.com/730619 If, for example, creating a new storage domain fails because there's no space left, the user gets: "Error creating a storage domain" which is not very helpful, since the real problem (no space) is not reported. "Error creating a storage domain" [i] No space left on device Where [i] is some widget the user can open to see details, or other element the UX team find acceptable. Nir Soffer and I believe a good solution is the following: 1. Currently VDSM sends a dictionary {'status': {'code': code, 'message': msg}}. The code is some number that Engine recognizes and has a localized message for. The msg parameter is ignored by Engine, and contains a default, not informative, string like "Error creating a storage domain" 2. We suggest adding a new key to this dictionary, call it "details", which will contain the string representation of the actual exception thrown in Python (in this case, OSError with the string "[Errno 28] No space left on device" 3. The Engine will look for this key, and display the string inside a "details" section which will be added to the current dialog box. The user gets the usual error indication, but has a small "details" icon, which he can click to see more information. The advantages are: 1. Simple to implement 2. Will improve the situation for any error thrown from Python - the user will get a clearer message. 3. New VDSM with old Engine is not a problem, the engine will not look for this key at all 4. New Engine with old VDSM is also easy to handle: the engine will not display "details" if this key is absent. Disadvatage is that the "details" will be non-localized, but this is natural for technical details. Why not use the existing "msg" field? because a new engine with an old VDSM will display uninformative, duplicate messages for all errors (the current msg field is simply a duplicate of the engine error name). What do you think? Yoav K

4 10

[vdsm] pep8 issue
by Amador Pahim 13 May '14

13 May '14

Building vdsm/master in F20, I've got: ./vdsm/virt/migration.py:223:19: E225 missing whitespace around operator In vdsm/virt/migration.py: 223 -1, -1) # int1, int2$ pep8 is not accepting the negative integer. Instead, it is handling the minus sign as an operator. Quick workaround is change -1 to int("-1"). Is this a known issue? I'm using python-pep8-1.5.4-1.fc20.noarch -- Pahim

1 0

UI plugins :: SystemTreeSelectionChange event
by Vojtech Szocs 13 May '14

13 May '14

Hey guys, UI plugin API now supports SystemTreeSelectionChange event, which is fired whenever "System Tree" selection (currently selected tree node) is changed. Example usage: api.register({ SystemTreeSelectionChange: function(selectedNode) { // See SystemTreeItemType Java enum for all supported values var nodeType = selectedNode.type; // Defined only if selected node has an entity associated var associatedEntity = selectedNode.entity; var associatedEntityId = associatedEntity && associatedEntity.id; } }); More details in UI plugin wiki: http://www.ovirt.org/Features/UIPlugins#System_tree_node_selection Regards, Vojtech

1 0

All-in-one engine setup for 3.5
by Piotr Kliczewski 13 May '14

13 May '14

I tried to deploy all in one engine (built from master) and noticed engine setup failed with: 2014-05-13 12:42:40 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/all-in-one/vdsm.py", line 190, in _closeup **FILTERED**_api = self._waitEngineUp() File "/usr/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/all-in-one/vdsm.py", line 127, in _waitEngineUp except self._ovirtsdk_api.RequestError: AttributeError: 'module' object has no attribute 'RequestError' Can someone help me to understand how to fix this issue? Thanks, Piotr

1 1

Building log collector rpm
by Piotr Kliczewski 13 May '14

13 May '14

I want to build log collector rpm and noticed that is failing due to: + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: ovirt-log-collector-3.5.0-0.0.master.fc19.noarch error: File not found by glob: /home/pkliczewski/rpmbuild/BUILDROOT/ovirt-log-collector-3.5.0-0.0.master.fc19.x86_64/usr/lib/python2.7/site-packages/sos/plugins/*.py* I pulled the code from master few minutes ago. Can someone help to solve this issue? Thanks, Piotr

2 8

New repos request
by Sandro Bonazzola 13 May '14

13 May '14

Hi, can you please create the following repositories? ovirt-setup: will have ovirt-engine-setup python sources currently shipped within ovirt-engine in packaging/setup. Since it will be able to install dwh / reports / websocket on host where ovirt-engine is not installed I think that calling it ovirt-engine-setup doesn't make much sense. ovirt-lib-python: will have python common libraries currently shipped within ovirt-engine in packaging/pythonlib. python suffix is used following http://fedoraproject.org/wiki/Packaging:NamingGuidelines Comments are welcome. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Ovirt-jenkins-question] How to re-trigger the failed gerrit-triggered jobs
by Shi, Xiao-Lei (Bruce, HP Servers-PSC-CQ) 13 May '14

13 May '14

Hi all, There is a findbugs build failure as below. But I checked the Jenkins console log of that job; it seems the failure is not caused by my code. I have rerun the job and it passed. My question is how can I re-trigger the failed Jenkins job and let it removed the "-1" review score on the gerrit. Thanks & Best Regards Shi, Xiao-Lei (Bruce) Hewlett-Packard Co., Ltd. HP Servers Core Platform Software China Telephone +86 23 65683093 Mobile +86 18696583447 Email xiao-lei.shi(a)hp.com -----Original Message----- From: oVirt Jenkins CI Server [mailto:gerrit2@gerrit.ovirt.org] Sent: Tuesday, May 13, 2014 5:21 AM To: Shi, Xiao-Lei (Bruce, HP Servers-PSC-CQ) Cc: Gilad Chaplik; automation(a)ovirt.org; Doron Fediuck; Roy Golan; Eli Mesika; Omer Frenkel; Arik Hadas; Martin Sivák; Eli Mesika; Jiří Moskovčák; Kobi Ianko; Vitor de Lima; Leonardo Bianconi; Gustavo Frederico Temple Pedrosa Subject: Change in ovirt-engine[master]: engine: Numa feature entities oVirt Jenkins CI Server has posted comments on this change. Change subject: engine: Numa feature entities ...................................................................... Patch Set 29: Code-Review-1 Verified-1 Build Unstable http://jenkins.ovirt.org/job/ovirt-engine_master_unit-tests_gerrit/7636/ : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine_master_dao_unit_tests_gerrit/2253/ : SUCCESS http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_gerrit/6944/ : The patch does not pass the findbugs http://jenkins.ovirt.org/job/ovirt_engine_master_compile_checkstyle_gerrit/… : SUCCESS -- To view, visit http://gerrit.ovirt.org/23702 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ifefade432e7955503980bdc6fc5d73ea32818a95 Gerrit-PatchSet: 29 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Xiaolei Shi <xiao-lei.shi(a)hp.com> Gerrit-Reviewer: Arik Hadas <ahadas(a)redhat.com> Gerrit-Reviewer: Doron Fediuck <dfediuck(a)redhat.com> Gerrit-Reviewer: Eli Mesika <elimesika(a)gmail.com> Gerrit-Reviewer: Eli Mesika <emesika(a)redhat.com> Gerrit-Reviewer: Gilad Chaplik <gchaplik(a)redhat.com> Gerrit-Reviewer: Gustavo Frederico Temple Pedrosa <gustavo.pedrosa(a)eldorado.org.br> Gerrit-Reviewer: Jiří Moskovčák <jmoskovc(a)redhat.com> Gerrit-Reviewer: Kobi Ianko <kobi(a)redhat.com> Gerrit-Reviewer: Leonardo Bianconi <leonardo.bianconi(a)eldorado.org.br> Gerrit-Reviewer: Martin Sivák <msivak(a)redhat.com> Gerrit-Reviewer: Omer Frenkel <ofrenkel(a)redhat.com> Gerrit-Reviewer: Roy Golan <rgolan(a)redhat.com> Gerrit-Reviewer: Vitor de Lima <vitor.lima(a)eldorado.org.br> Gerrit-Reviewer: Xiaolei Shi <xiao-lei.shi(a)hp.com> Gerrit-Reviewer: automation(a)ovirt.org Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No

2 1

Help debugging engine.log
by Sandro Bonazzola 12 May '14

12 May '14

the following lines appear after adding the first host to an engine running inside Hosted Engine VM. Can anybody tell what the following lines are meaning? 2014-04-18 17:21:57,223 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-5) [751509c7] FINISH, SetVdsStatusVDSCommand, log id: 6bb07f05 2014-04-18 17:21:57,223 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-4-thread-5) [751509c7] After Installation host hosted_engine_1, VDS 2014-04-18 17:21:57,243 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-4-thread-5) [751509c7] Correlation ID: 751509c7, Job ID: c7abd67c-5655-4ea8-8226-c51eda9c9675, Call Stac k: null, Custom Event ID: -1, Message: Host hosted_engine_1 installed 2014-04-18 17:21:57,255 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-4-thread-5) [751509c7] Lock freed to object EngineLock [exclusiveLocks= key: f609e5f8-1676-4e87-98ec-9477afc27557 value: VDS , sharedLocks= ] 2014-04-18 17:21:58,764 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-3) START, GetHardwareInfoVDSCommand(HostName = hosted_engine_1, HostId = f609e5f 8-1676-4e87-98ec-9477afc27557, vds=Host[hosted_engine_1]), log id: 496d80d8 2014-04-18 17:21:58,834 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-3) FINISH, GetHardwareInfoVDSCommand, log id: 496d80d8 2014-04-18 17:21:58,944 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-3) START, GetHardwareInfoVDSCommand(HostName = hosted_engine_1, HostId = f609e5f8-1676-4e87-98ec-9477afc27557, vds=Host[hosted_engine_1]), log id: 36957393 2014-04-18 17:21:58,971 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-3) FINISH, GetHardwareInfoVDSCommand, log id: 36957393 2014-04-18 17:21:58,989 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-3) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: State was set to Up for host hosted_engine_1. 2014-04-18 17:21:59,058 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-3) START, FullListVdsCommand(HostName = hosted_engine_1, HostId = f609e5f8-1676-4e87-98ec-9477afc27557, vds=Host[hosted_engine_1], vmIds=[950f8a3a-82af-478e-8f99-9cd0556b9cfc]), log id: 16b792bc 2014-04-18 17:21:59,095 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-3) FINISH, FullListVdsCommand, return: [Ljava.util.HashMap;@3a6e1bc2, log id: 16b792bc 2014-04-18 17:21:59,096 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-3) Importing VM HostedEngine as HostedEngine, as it is running on the on Host, but does not exist in the engine. 2014-04-18 17:21:59,122 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-3) VDS::UpdateVmRunTimeInfo Error: found VM on a VDS that is not in the database! 2014-04-18 17:21:59,137 INFO [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (DefaultQuartzScheduler_Worker-3) [3a5f7d19] Running command: InitVdsOnUpCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2014-04-18 17:21:59,144 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetMOMPolicyParametersVDSCommand] (DefaultQuartzScheduler_Worker-3) [3a5f7d19] START, SetMOMPolicyParametersVDSCommand(HostName = hosted_engine_1, HostId = f609e5f8-1676-4e87-98ec-9477afc27557), log id: 36c8962e 2014-04-18 17:21:59,223 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetMOMPolicyParametersVDSCommand] (DefaultQuartzScheduler_Worker-3) [3a5f7d19] FINISH, SetMOMPolicyParametersVDSCommand, log id: 36c8962e 2014-04-18 17:21:59,228 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-3) [3a5f7d19] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to verify Power Management configuration for Host hosted_engine_1. 2014-04-18 17:21:59,389 INFO [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (DefaultQuartzScheduler_Worker-3) [266af7f3] Lock Acquired to object EngineLock [exclusiveLocks= key: HostedEngine value: VM_NAME , sharedLocks= ] 2014-04-18 17:21:59,453 INFO [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (DefaultQuartzScheduler_Worker-3) [266af7f3] Running command: AddVmFromScratchCommand internal: true. Entities affected : ID: 99408929-82cf-4dc7-a532-9d998063fa95 Type: VdsGroups 2014-04-18 17:21:59,707 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-3) [266af7f3] Correlation ID: 266af7f3, Job ID: 2c46a619-bc01-4b85-96bd-d3fc5e073901, Call Stack: null, Custom Event ID: -1, Message: VM HostedEngine was created by <UNKNOWN>. 2014-04-18 17:21:59,714 INFO [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (DefaultQuartzScheduler_Worker-3) [266af7f3] Lock freed to object EngineLock [exclusiveLocks= key: HostedEngine value: VM_NAME , sharedLocks= ] 2014-04-18 17:21:59,718 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler_Worker-3) [5e0dc4d1] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: f609e5f8-1676-4e87-98ec-9477afc27557 Type: VDS 2014-04-18 17:21:59,766 INFO [org.ovirt.engine.core.bll.UpdateVdsGroupCommand] (DefaultQuartzScheduler_Worker-3) [32fd282a] Running command: UpdateVdsGroupCommand internal: true. Entities affected : ID: 99408929-82cf-4dc7-a532-9d998063fa95 Type: VdsGroups 2014-04-18 17:22:00,015 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-3) [32fd282a] Correlation ID: 32fd282a, Call Stack: null, Custom Event ID: -1, Message: Host cluster Default was updated by system 2014-04-18 17:22:00,032 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-3) [4f38fad3] Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: f609e5f8-1676-4e87-98ec-9477afc27557 Type: VDS 2014-04-18 17:22:03,100 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-6) START, FullListVdsCommand(HostName = hosted_engine_1, HostId = f609e5f8-1676-4e87-98ec-9477afc27557, vds=Host[hosted_engine_1], vmIds=[950f8a3a-82af-478e-8f99-9cd0556b9cfc]), log id: 4148c04c 2014-04-18 17:22:03,129 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-6) FINISH, FullListVdsCommand, return: [Ljava.util.HashMap;@5f864ed0, log id: 4148c04c 2014-04-18 17:22:03,131 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-6) Received a console Device without an address when processing VM 950f8a3a-82af-478e-8f99-9cd0556b9cfc devices, skipping device: {alias=console0, specParams={}, device=console, type=console, deviceId=c627f372-2893-4b79-b534-f51c86374d1b} 2014-04-18 17:22:03,131 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-6) Received a memballoon Device without an address when processing VM 950f8a3a-82af-478e-8f99-9cd0556b9cfc devices, skipping device: {alias=balloon0, specParams={model=none}, device=memballoon, type=balloon} 2014-04-18 17:22:03,132 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-6) Empty or NULL values were passed for a VM 950f8a3a-82af-478e-8f99-9cd0556b9cfc device, Device is skipped 2014-04-18 17:53:16,713 INFO [org.ovirt.engine.core.bll.LogoutUserCommand] (ajp-/127.0.0.1:8702-5) [3829e38e] Running command: LogoutUserCommand internal: false. 2014-04-18 17:53:16,725 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-5) [3829e38e] Correlation ID: 3829e38e, Call Stack: null, Custom Event ID: -1, Message: User admin@internal logged out. 2014-04-18 17:54:28,145 INFO [org.ovirt.engine.core.bll.LoginAdminUserCommand] (ajp-/127.0.0.1:8702-4) Running command: LoginAdminUserCommand internal: false. 2014-04-18 17:54:28,149 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-4) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: User admin@internal logged in. 2014-04-18 17:54:28,207 INFO [org.ovirt.engine.core.bll.LoginUserCommand] (ajp-/127.0.0.1:8702-8) Running command: LoginUserCommand internal: false. 2014-04-18 17:54:28,212 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-8) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: User admin@internal logged in. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 6

oVirt Node ISO rpm-wrapper update
by Fabian Deutsch 12 May '14

12 May '14

--=-XY7myqfQdPvMEZ9t/p3A Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=20 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? 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 --=-XY7myqfQdPvMEZ9t/p3A 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 iQIcBAABAgAGBQJTcKsRAAoJEC9+uOgSHVGUxbEQAK2F3zufJIRKGmp+VNcqzDkG +C81XqLodPpC80HXRHzbbDb/rGeA3yqcXGa34L17Nz7OhoBIXnDZIY3/Uzjw0PfG BYPkHZYtWZhR/CFQGRDSrANFb2ucxIbvetOXjKK5fgGhuXP20C8TpC6YxdmnTLcG J3/RysEwluoz6j6MfqN8IgqngMeZfit/uFqLk+E2fMaIexYa6VyM8JBnN9nLL6ck 0z+9FKT4da4jFFH5dgTAyi0Y8DL4mxyvORTqzFqFAv0aMyGHXz94KKchmCn6JaBD 3GfpQbxbFJg0jKj9DtzOkL3kQPvPU5vymnJXbrG/mwHPIWTxfGaHGjSg8p1hfRcG jNDVk8Isg1m4BBMy55aP4xB/KuEr4wNl62YrXUMeQHSAPJHaAWmo72IgJFFXVxcQ mTMTKw7E/4MY3wcJRhFcl/kroE3e6foiuRRjoPDuP6VHMv68d3PcfhduzQpq+rvx KuGBmkcMU99IzyUPYovEMZb4goKuHU6GtRVwnI53HVcnQg53FO2Kixmby3gto8MD xDBCtQkertQuXwIkWbuNArfxu+WkqT2dS2vWhsgvmhpNnvP7lUC0zFptcQvcalIu jn3yk7GjWFIJwndLoXI3klwms8pbs0GNRKEQ9OCxHnTCIzmpmTGU9/bIShwVoHAn M4rT42Cpspd3QPwY0/T6 =L21D -----END PGP SIGNATURE----- --=-XY7myqfQdPvMEZ9t/p3A--

1 0