January 2017 - Devel - oVirt List Archives

Proposal to move master to fc25 or rawhide
by Sandro Bonazzola 26 Jan '17

26 Jan '17

Hi, since we're in the beginning of the 4.2 cycle I'd like to propose to switch master from fc24 to fc25 or to rawhide, being fc26 going GA on 2017-06-06. What do you think? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

[ANN] oVirt 4.1.0 First Release Candidate is now available
by Sandro Bonazzola 26 Jan '17

26 Jan '17

The oVirt Project is pleased to announce the availability of the First Release candidate of oVirt 4.1.0 for testing, as of January 23rd, 2016 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the first release candidate of the 4.1 release series. 4.1.0 brings more than 250 enhancements and more than 700 bugfixes, including more than 300 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 24 (tech preview) * oVirt Node 4.1 See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Live iso is already available[5] - oVirt Node NG iso is already available[5] - Hosted Engine appliance is already available A release management page including planned schedule is also available[4] Additional Resources: * Read more about the oVirt 4.1.0 release highlights: http://www.ovirt.org/release/4.1.0/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.0/ [4] http://www.ovirt.org/develop/release-management/releases/4.1/release-manage… [5] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 7

master is broken
by Yedidyah Bar David 25 Jan '17

25 Jan '17

On Wed, Jan 25, 2017 at 4:07 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: packaging: spec: Require ansible > ...................................................................... > > > Patch Set 2: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… : FAILURE rpmbuild.log says: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project vdsbroker: Compilation failure [ERROR] /home/jenkins/workspace/ovirt-engine_master_upgrade-from-4.0_el7_merged/tmp_repo/ovirt-engine-4.2.0/backend/manager/modules/vdsbroker/src/main/java/org/ovirt/engine/core/vdsbroker/builder/vminfo/LibvirtVmXmlBuilder.java:[1022,45] error: cannot find symbol Can someone please check? Thanks. > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc24-x86_6… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/34… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_merge… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc24-x86_64/2… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc25-x86_64/4… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… : FAILURE > > -- > To view, visit https://gerrit.ovirt.org/71138 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: Ic68c5394f824f0533b42fb32374d29e56c56fa1e > Gerrit-PatchSet: 2 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

2 1

hotplug_nic test has failed
by Gil Shinar 25 Jan '17

25 Jan '17

I have found the following exception in VDSM log: *MainProcess|jsonrpc/0::DEBUG::2017-01-24 10:13:50,303::supervdsm_server::101::SuperVdsm.ServerCallback::(wrapper) return network_caps with {'bridges': {'ovirtmgmt': {'ipv6autoconf': True, 'addr': '192.168.201.2', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '192.168.201.1', 'dhcpv4': True, 'netmask': '255.255.255.0', 'ipv4defaultroute': True, 'stp': 'off', 'ipv4addrs': ['192.168.201.2/24' <http://192.168.201.2/24'>], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['eth0'], 'opts': {'multicast_last_member_count': '2', 'hash_elasticity': '4', 'multicast_query_response_interval': '1000', 'group_fwd_mask': '0x0', 'multicast_snooping': '1', 'multicast_startup_query_interval': '3125', 'hello_timer': '15', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '0', 'topology_change_detected': '0', 'priority': '32768', 'multicast_membership_interval': '26000', 'root_path_cost': '0', 'root_port': '0', 'multicast_querier': '0', 'multicast_startup_query_count': '2', 'nf_call_iptables': '0', 'topology_change': '0', 'hello_time': '200', 'root_id': '8000.5452c0a8c902', 'bridge_id': '8000.5452c0a8c902', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '20299', 'nf_call_arptables': '0', 'group_addr': '1:80:c2:0:0:0', 'multicast_last_member_interval': '100', 'default_pvid': '1', 'multicast_query_interval': '12500', 'tcn_timer': '0', 'multicast_router': '1', 'vlan_filtering': '0', 'forward_delay': '0'}}}, 'bondings': {}, 'nameservers': ['192.168.201.1'], 'nics': {'eth3': {'ipv6autoconf': True, 'addr': '192.168.202.212', 'ipv6gateway': 'fe80::5054:ff:fe65:57d6', 'dhcpv6': False, 'ipv6addrs': [], 'mtu': '1500', 'dhcpv4': True, 'netmask': '255.255.255.0', 'ipv4defaultroute': False, 'ipv4addrs': ['192.168.202.212/24' <http://192.168.202.212/24'>], 'hwaddr': '54:52:c0:a8:ca:03', 'speed': 0, 'gateway': '192.168.202.1'}, 'eth2': {'ipv6autoconf': True, 'addr': '192.168.202.211', 'ipv6gateway': '::', 'dhcpv6': False, 'ipv6addrs': [], 'mtu': '1500', 'dhcpv4': True, 'netmask': '255.255.255.0', 'ipv4defaultroute': False, 'ipv4addrs': ['192.168.202.211/24' <http://192.168.202.211/24'>], 'hwaddr': '54:52:c0:a8:ca:02', 'speed': 0, 'gateway': '192.168.202.1'}, 'eth1': {'ipv6autoconf': True, 'addr': '192.168.200.143', 'ipv6gateway': '::', 'dhcpv6': False, 'ipv6addrs': [], 'mtu': '1500', 'dhcpv4': True, 'netmask': '255.255.255.0', 'ipv4defaultroute': False, 'ipv4addrs': ['192.168.200.143/24' <http://192.168.200.143/24'>], 'hwaddr': '54:52:c0:a8:c8:02', 'speed': 0, 'gateway': '192.168.200.1'}, 'eth0': {'ipv6autoconf': False, 'addr': '', 'ipv6gateway': '::', 'dhcpv6': False, 'ipv6addrs': [], 'mtu': '1500', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'ipv4addrs': [], 'hwaddr': '54:52:c0:a8:c9:02', 'speed': 0, 'gateway': ''}}, 'supportsIPv6': True, 'vlans': {}, 'networks': {'ovirtmgmt': {'dhcpv6': False, 'iface': 'ovirtmgmt', 'ipv6autoconf': True, 'addr': '192.168.201.2', 'bridged': True, 'ipv6addrs': [], 'switch': 'legacy', 'gateway': '192.168.201.1', 'dhcpv4': True, 'netmask': '255.255.255.0', 'ipv4defaultroute': True, 'stp': 'off', 'ipv4addrs': ['192.168.201.2/24' <http://192.168.201.2/24'>], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['eth0']}}} ifup/VLAN100_Network::DEBUG::2017-01-24 10:13:53,048::commands::93::root::(execCmd) FAILED: <err> = 'Running scope as unit 0e9c5843-c89e-499b-9057-1d70ea366504.scope.\n/etc/sysconfig/network-scripts/ifup-eth: line 297: 16535 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}\nCannot find device "VLAN100_Network"\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\n'; <rc> = 1 ifup/VLAN100_Network::ERROR::2017-01-24 10:13:53,049::concurrent::189::root::(run) FINISH thread <Thread(ifup/VLAN100_Network, started daemon 140683650258688)> failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 185, in run ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 910, in _exec_ifup _exec_ifup_by_name(iface.name <http://iface.name>, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 896, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '') ConfigNetworkError: (29, 'Determining IPv6 information for VLAN100_Network... failed.')* Can someone please assist (logs for engine and vdsm [1])? [1] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4935/artif… Thanks Gil

2 2

Invitation: DeepDive: SPDM shared storage management (infrastructure/... @ Wed Feb 15, 2017 6pm - 7pm (IST) (devel@ovirt.org)
by laravot＠redhat.com 25 Jan '17

25 Jan '17

You have been invited to the following event. Title: DeepDive: SPDM shared storage management (infrastructure/copy scale out/progress reporting) When: Wed Feb 15, 2017 6pm – 7pm Jerusalem Where: https://redhat.bluejeans.com/laravot Calendar: devel(a)ovirt.org Who: * laravot(a)redhat.com - organizer * devel(a)ovirt.org * users(a)ovirt.org * rhevm-qe-dept Event details: https://www.google.com/calendar/event?action=VIEW&eid=Ym9kazZyZHVjbjdjZzl2c… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Redundant stomp connection for SPM
by Roy Golan 24 Jan '17

24 Jan '17

For each SPM host the engine creates a different stomp connection (See JsonRpcIIrsServer.java) . This also means another client connection to maintain on the SPM machine. What is the reason we still have it and what does it guarantee? Please add any info here prior to opening a bug to remove it for 4.2.

3 3

Thread pools and ManageExecutorService
by Roy Golan 24 Jan '17

24 Jan '17

Java EE 7 included ManageExecutorService in its spec. Using Wildfly (as certified EE 7 container) we can use it to replace our own ThreadPoolUtil implementation and (possibly) Quarz usage. Managed executor service is a thread pool resource, manage by the container and can be controlled via JMX or the startup ovirt-egine.xml.in facility. This means that it could be tweaked at runtime as well. The service has configured thread factory and queue as well, all described by the xml In the engine we are using mutli pools, with little to no capabilities of tweaking them - ThreadPoolUtil - our general threading facade - SchedulerThreadPool - the pool we create to pass to quarz - HostUpdatesCheckerService.java - internal pool - CommandExecutor - coco's pool EE gave us a standard way to handle threads, with runtime configuration and ability to @inject it into the code, this means once again less code with using something the platform already supplies with real tuninig abilities. I know #infra has an item quarts, this should be considered as well. Following this thread, if there is no suitable bug already, I'll open one for this. Some code snippets: @Resource private ManagedExecutorService mes; ... Future f = mes.submit(() -> doThis()) The configuration in ovirt-engine.xml.in (already there today!): <managed-executor-services> <managed-executor-service name="default" jndi-name="java:jboss/ee/concurrency/executor/default" context-service="default" thread-factory="default" hung-task-threshold="60000" core-threads="5" max-threads="25" keepalive-time="5000" queue-length="1000000" reject-policy="RETRY_ABORT" /> </managed-executor-services> Please head here for wildfly docs [1] and here [2] to see a simple example (from one of the members of the EG of EE, recommended blog in general) [1] https://docs.jboss.org/author/display/WFLY8/EE+Concurrency+Utilities+Config… [2] http://www.adam-bien.com/roller/abien/entry/injecting_an_executorservice_wi…

4 4

API model documentation is broken?
by Yaniv Kaul 24 Jan '17

24 Jan '17

Just below [1], something is a bit messed up. TIA, Y. [1] http://ovirt.github.io/ovirt-engine-api-model/master/#services/attached_sto…

2 1

Updated Invitation: Next-generation Node package persistence for oVirt 4.1 @ Thu Jan 26, 2017 9am - 10am (MST) (devel@ovirt.org)
by rbarry＠redhat.com 24 Jan '17

24 Jan '17

This event has been changed. Title: Next-generation Node package persistence for oVirt 4.1 oVirt Node is a composed hypervisor image which can be used to provision virtualization hosts for use with oVirt out of the box, with no additional package installation necessary. oVirt Node is upgraded via yum in an A/B fashion, but the installation of a completely new image means that packages which have been installed on a previous version of the hypervisor were lost on upgrades, or required reinstallation. With oVIrt 4.1, oVirt Node will cache and reinstall packages installed with yum or dnf onto the new image, ensuring that customizations made by users or administrators are kept. The advantages of keeping packages across upgrades: - ability to persistently modify oVirt Node with additions for tooling or support - removes the need to build a brand-new image with a modified kickstart to modify oVirt Node - simplified management Session outline: - Next-generation oVirt Node overview - yum API overview - oVIrt Node integration with yum/dnf to persist RPMs across upgrades Session link: https://www.youtube.com/watch?v=VAznsxvZpuk Feature Page: https://www.ovirt.org/develop/release-management/features/node/node-next-pe… When: Thu Jan 26, 2017 9am – 10am Mountain Time - Arizona (changed) Where: https://www.youtube.com/watch?v=tpAVkBEDdVg Calendar: devel(a)ovirt.org Who: * rbarry(a)redhat.com - organizer * users(a)ovirt.org * devel(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=dWxlaW1rMmI0MHJybHZsO… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Updated Invitation: Next-generation Node package persistence for oVirt 4.1 @ Thu Jan 26, 2017 8am - 9am (MST) (devel@ovirt.org)
by rbarry＠redhat.com 24 Jan '17

24 Jan '17

This event has been changed. Title: Next-generation Node package persistence for oVirt 4.1 oVirt Node is a composed hypervisor image which can be used to provision virtualization hosts for use with oVirt out of the box, with no additional package installation necessary. oVirt Node is upgraded via yum in an A/B fashion, but the installation of a completely new image means that packages which have been installed on a previous version of the hypervisor were lost on upgrades, or required reinstallation. With oVIrt 4.1, oVirt Node will cache and reinstall packages installed with yum or dnf onto the new image, ensuring that customizations made by users or administrators are kept. The advantages of keeping packages across upgrades: - ability to persistently modify oVirt Node with additions for tooling or support - removes the need to build a brand-new image with a modified kickstart to modify oVirt Node - simplified management Session outline: - Next-generation oVirt Node overview - yum API overview - oVIrt Node integration with yum/dnf to persist RPMs across upgrades Session link: https://www.youtube.com/watch?v=VAznsxvZpuk Feature Page: https://www.ovirt.org/develop/release-management/features/node/node-next-pe… When: Thu Jan 26, 2017 8am – 9am Mountain Time - Arizona (changed) Where: https://www.youtube.com/watch?v=tpAVkBEDdVg (changed) Calendar: devel(a)ovirt.org Who: * rbarry(a)redhat.com - organizer * users(a)ovirt.org * devel(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=dWxlaW1rMmI0MHJybHZsO… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0