- Users - oVirt List Archives

How to create a new Gluster volume
by Gianluca Cecchi 07 Jul '17

07 Jul '17

Hello, I'm trying to create a new volume. I'm in 4.1.2 I'm following these indications: http://www.ovirt.org/documentation/admin-guide/chap-Working_with_Gluster_St… When I click the "add brick" button, I don't see anything in "Brick Directory" dropdown field and I cannot manuall input a directory name. On the 3 nodes I already have formatted and mounted fs [root@ovirt01 ~]# df -h /gluster/brick3/ Filesystem Size Used Avail Use% Mounted on /dev/mapper/gluster-export 50G 33M 50G 1% /gluster/brick3 [root@ovirt01 ~]# The guide tells 7. Click the Add Bricks button to select bricks to add to the volume. Bricks must be created externally on the Gluster Storage nodes. What does it mean with "created externally"? The next step from os point would be volume creation but it is indeed what I would like to do from the gui... Thanks, Gianluca

2 4

Cloning VM on NFS Leads to Locked Disks
by Charles Tassell 06 Jul '17

06 Jul '17

Hi Everyone, I'm having some issues with my oVirt 4.1 (fully updated to latest release as of yesterday) cluster. When I clone a VM the disks of both the original and the clone stay in the locked state, and the only way I can resolve it is to go into the database on the engine and run "update images set imagestatus=1 where imagestatus=2;" I'm using NFS4 as a datastore and the disks seem to copy fine (file sizes match and everything), but the locking worries me. To clone the VM I just shut the source VM down and then right click on it and select "Clone" I've attached the full VDSM log from my last attempt, but here is the excerpt of the lines just referencing the two disks (d73206ed-89ba-48a9-82ff-c107c1af60f0 is the original VMs disk and 670a7b20-fecd-45c6-af5c-3c7b98258224 is the clone.) 2017-05-10 11:36:20,120-0300 INFO (jsonrpc/2) [dispatcher] Run and protect: copyImage(sdUUID=u'20423d5e-188c-4e10-9893-588ceb81b354', spUUID=u'00000001-0001-0001-0001-000000000311', vmUUID='', srcImgUUID=u'd73206ed-89ba-48a9-82ff-c107c1af60f0', srcVolUUID=u'bba1813d-9e91-4e37-bed7-40beedda8051', dstImgUUID=u'670a7b20-fecd-45c6-af5c-3c7b98258224', dstVolUUID=u'013d8855-4e49-4984-8266-6a5e9437dff7', description=u'', dstSdUUID=u'20423d5e-188c-4e10-9893-588ceb81b354', volType=8, volFormat=5, preallocate=2, postZero=u'false', force=u'false', discard=False) (logUtils:51) 2017-05-10 11:36:20,152-0300 INFO (jsonrpc/2) [storage.Image] image d73206ed-89ba-48a9-82ff-c107c1af60f0 in domain 20423d5e-188c-4e10-9893-588ceb81b354 has vollist [u'bba1813d-9e91-4e37-bed7-40beedda8051'] (image:319) 2017-05-10 11:36:20,169-0300 INFO (jsonrpc/2) [storage.Image] sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 imgUUID=d73206ed-89ba-48a9-82ff-c107c1af60f0 chain=[<storage.fileVolume.FileVolume object at 0x278e450>] (image:249) 2017-05-10 11:36:20,292-0300 INFO (tasks/0) [storage.Image] sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 imgUUID=d73206ed-89ba-48a9-82ff-c107c1af60f0 chain=[<storage.fileVolume.FileVolume object at 0x302c6d0>] (image:249) 2017-05-10 11:36:20,295-0300 INFO (tasks/0) [storage.Image] sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 vmUUID= srcImgUUID=d73206ed-89ba-48a9-82ff-c107c1af60f0 srcVolUUID=bba1813d-9e91-4e37-bed7-40beedda8051 dstImgUUID=670a7b20-fecd-45c6-af5c-3c7b98258224 dstVolUUID=013d8855-4e49-4984-8266-6a5e9437dff7 dstSdUUID=20423d5e-188c-4e10-9893-588ceb81b354 volType=8 volFormat=RAW preallocate=SPARSE force=False postZero=False discard=False (image:765) 2017-05-10 11:36:20,305-0300 INFO (tasks/0) [storage.Image] copy source 20423d5e-188c-4e10-9893-588ceb81b354:d73206ed-89ba-48a9-82ff-c107c1af60f0:bba1813d-9e91-4e37-bed7-40beedda8051 vol size 41943040 destination 20423d5e-188c-4e10-9893-588ceb81b354:670a7b20-fecd-45c6-af5c-3c7b98258224:013d8855-4e49-4984-8266-6a5e9437dff7 apparentsize 41943040 (image:815) 2017-05-10 11:36:20,306-0300 INFO (tasks/0) [storage.Image] image 670a7b20-fecd-45c6-af5c-3c7b98258224 in domain 20423d5e-188c-4e10-9893-588ceb81b354 has vollist [] (image:319) 2017-05-10 11:36:20,306-0300 INFO (tasks/0) [storage.Image] Create placeholder /rhev/data-center/00000001-0001-0001-0001-000000000311/20423d5e-188c-4e10-9893-588ceb81b354/images/670a7b20-fecd-45c6-af5c-3c7b98258224 for image's volumes (image:149) 2017-05-10 11:36:20,392-0300 INFO (tasks/0) [storage.Volume] Request to create RAW volume /rhev/data-center/00000001-0001-0001-0001-000000000311/20423d5e-188c-4e10-9893-588ceb81b354/images/670a7b20-fecd-45c6-af5c-3c7b98258224/013d8855-4e49-4984-8266-6a5e9437dff7 with size = 20480 sectors (fileVolume:439) 2017-05-10 11:37:58,453-0300 INFO (tasks/0) [storage.VolumeManifest] sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 imgUUID=670a7b20-fecd-45c6-af5c-3c7b98258224 volUUID = 013d8855-4e49-4984-8266-6a5e9437dff7 legality = LEGAL (volume:393)

2 7

How to reset volume info in storage domain metadata LV
by Kuko Armas 06 Jul '17

06 Jul '17

Recently I got a disk snapshot marked as illegal in an VM due to a failed live merge I fixed the snapshot manually with qemu-img rebase, now qemu-img check shows everything OK I also set the imagestatus to OK in the engine database, as shown below engine=# select image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active from images where image_group_id='c35ccdc5-a256-4460-8dd2-9e639b8430e9'; image_guid | parentid | imagestatus | vm_snapshot_id | volume_type | volume_format | active --------------------------------------+--------------------------------------+-------------+--------------------------------------+------------- +---------------+-------- 07729f62-2cd2-45d0-993a-ec8d7fbb6ee0 | 00000000-0000-0000-0000-000000000000 | 1 | 7ae58a5b-eacf-4f6b-a06f-bda1d85170b5 | 1 | 5 | f ee733323-308a-40c8-95d4-b33ca6307362 | 07729f62-2cd2-45d0-993a-ec8d7fbb6ee0 | 1 | 2ae07078-cc48-4e20-a249-52d3f44082b4 | 2 | 4 | t But when I try to boot the VM it still fails with this error in the SPM Thread-292345::ERROR::2017-07-06 14:20:33,155::task::866::Storage.TaskManager.Task::(_setError) Task=`2d262a05-5a03-4ff9-8347-eaa22b6e143c`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 873, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 49, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 3227, in prepareImage raise se.prepareIllegalVolumeError(volUUID) prepareIllegalVolumeError: Cannot prepare illegal volume: ('ee733323-308a-40c8-95d4-b33ca6307362',) Thread-292345::DEBUG::2017-07-06 14:20:33,156::task::885::Storage.TaskManager.Task::(_run) Task=`2d262a05-5a03-4ff9-8347-eaa22b6e143c`::Task._run: 2d262a05-5a03-4ff9-8347-eaa22b6e143c (u'146dca57-05fd-4b3f-af8d-b253a7ca6f6e', u'00000001-0001-0001-0001-00000000014d', u'c35ccdc5-a256-4460-8dd2-9e639b8430e9', u'ee733323-308a-40c8-95d4-b33ca6307362') {} failed - stopping task Just before that error I see this operation in the log: /usr/bin/taskset --cpu-list 0-23 /usr/bin/dd iflag=direct skip=11 bs=512 if=/dev/146dca57-05fd-4b3f-af8d-b253a7ca6f6e/metadata count=1 If I run it manually I get this: [root@blade6 ~]# /usr/bin/taskset --cpu-list 0-23 /usr/bin/dd iflag=direct skip=11 bs=512 if=/dev/146dca57-05fd-4b3f-af8d-b253a7ca6f6e/metadata count=1 DOMAIN=146dca57-05fd-4b3f-af8d-b253a7ca6f6e VOLTYPE=LEAF CTIME=1497399380 FORMAT=COW IMAGE=c35ccdc5-a256-4460-8dd2-9e639b8430e9 DISKTYPE=2 PUUID=07729f62-2cd2-45d0-993a-ec8d7fbb6ee0 LEGALITY=ILLEGAL MTIME=0 POOL_UUID= SIZE=209715200 TYPE=SPARSE DESCRIPTION= EOF So I guess the volume info is cached in the storage domain's metadata LV, and it's still in ILLEGAL status there Is there a way to force ovirt to update the information in the metadata LV? Of course I've thought of updating manually with dd, with it seems too risky (and scary) to do it in production Salu2! -- Miguel Armas CanaryTek Consultoria y Sistemas SL http://www.canarytek.com/

1 0

[ANN] oVirt 4.1.3 Release is now available
by Lev Veyde 06 Jul '17

06 Jul '17

The oVirt Project is pleased to announce the availability of the oVirt 4.1.3 Release, as of July 6th, 2017 This update is the third in a series of stabilization updates to the 4.1 series. 4.1.3 brings 20 enhancements and 138 bugfixes, including 76 high or urgent severity fixes, on top of oVirt 4.1 series 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 * oVirt Node 4.1 * Fedora 24 (tech preview) See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live has been already built [4] - oVirt Node will be available soon [4] Additional Resources: * Read more about the oVirt 4.1.3 release highlights:http://www.ovirt.org/release/4.1.3/ * 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.3/ [4] http://resources.ovirt.org/pub/ovirt-4.1/iso/ -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Installation problem - missing dependencies?
by Paweł Zaskórski 06 Jul '17

06 Jul '17

Hi everyone! I'm trying to install oVirt on fresh CentOS 7 (up-to-date). According to documentation i did: # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm # yum install ovirt-engine Unfortunately, I'm getting an error: --> Finished Dependency Resolution Error: Package: ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-engine-cli >= 3.6.2.0 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-engine-dwh-setup >= 4.0 Error: Package: ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-iso-uploader >= 4.0.0 Error: Package: ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-engine-wildfly >= 10.1.0 Error: Package: ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-engine-wildfly-overlay >= 10.0.0 Error: Package: ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-imageio-proxy Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-imageio-proxy-setup Error: Package: ovirt-engine-4.1.3.5-1.el7.centos.noarch (ovirt-4.1) Requires: ovirt-engine-dashboard >= 1.0.0 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest My enabled repos: # yum --noplugins repolist | awk 'FNR > 1 {print $1}' | head -n-1 base/7/x86_64 centos-opstools-release/7/x86_64 extras/7/x86_64 ovirt-4.1/7 ovirt-4.1-centos-gluster38/x86_64 ovirt-4.1-epel/x86_64 ovirt-4.1-patternfly1-noarch-epel/x86_64 ovirt-centos-ovirt41/7/x86_64 sac-gdeploy/x86_64 updates/7/x86_64 virtio-win-stable Did I miss something? From which repository come packages like ovirt-engine-dashboard or ovirt-engine-dwh-setup? Thank you in advance for your help! Best regards, Paweł

2 3

Configure an ovirt 4.1 hosted engine using SAS storage (aka DAS storage)
by yayo (j) 06 Jul '17

06 Jul '17

Hi all, I'm tring to install a new cluster ovirt 4.1 (Centos 7) configured to use a SAN that expose LUN via SAS . When I start to deploy ovirt and the engine using "hosted-engine --deploy" the only options I have are: (glusterfs, iscsi, fc, nfs3, nfs4) There is no option for "local" storage (that are not local naturally, but are multipath device exposed by SAN via LUN) Can you help me? What is the right configuration? Thank you

1 1

Networking and oVirt 4.1
by Gabriel Stein 05 Jul '17

05 Jul '17

Hi all, I'm installing oVirt for the first time and I'm having some issues with the Networking. Setup: OS: CentOS 7 Mininal 3 Bare Metal Servers(1 for Engine, 2 for Nodes). Network: Nn Trunk Interfaces with VLANs and Bridges. e.g.: trunk.100, VLAN: 100, Bridge: vmbr100. IPV4 only. I have already a VLAN for MGMNT, without DHCP Server(not needed for oVirt, but explaining my setup). Networking works as expected, I can ping/ssh each host without problems. On the two nodes, I have a Interface named ovirtmgmt and dhcp... Question 1: What kind of configuration can I use here? Can I set static IPs from VLAN MGMNT and put everything from oVirt on that VLAN? oVirt doens't have a Internal DHCP Server for Nodes, or? Question 2: Should I leave oVirt to Setup it(ovirtmgmt Interface) for me? Problems: I configured the Engine with the IP 1.1.1.1, and I reach the web interface with https://FQDN( which is IP: 1.1.1.1) But, when I add a Host to the Cluster, I have some errors: "Host XXXX does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt'" Question 3: I saw that Engine tries to call dhclient and Setup an IP for it, but could I have static IPs? Where can I configure it? * vdsm.log *2017-07-03 15:15:01,772+0200 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.getCapabilities succeeded in 0.11 seconds (__init__:533)2017-07-03 15:15:01,808+0200 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getHardwareInfo succeeded in 0.01 seconds (__init__:533)2017-07-03 15:15:06,870+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:06,871+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:10,059+0200 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:11,643+0200 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:12,270+0200 INFO (jsonrpc/3) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:12,271+0200 INFO (jsonrpc/3) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:12,277+0200 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call Host.getStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:21,915+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:21,916+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:25,078+0200 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:27,273+0200 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:28,330+0200 INFO (jsonrpc/6) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:28,330+0200 INFO (jsonrpc/6) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:28,337+0200 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:36,960+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:36,960+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:40,096+0200 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:43,280+0200 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:44,408+0200 INFO (jsonrpc/1) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:44,408+0200 INFO (jsonrpc/1) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:44,415+0200 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getStats succeeded in 0.01 seconds (__init__:533)2017-07-03 15:15:52,006+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:15:52,006+0200 INFO (periodic/3) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)2017-07-03 15:15:55,115+0200 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:15:59,287+0200 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:533)2017-07-03 15:16:00,465+0200 INFO (jsonrpc/4) [dispatcher] Run and protect: repoStats(options=None) (logUtils:51)2017-07-03 15:16:00,465+0200 INFO (jsonrpc/4) [dispatcher] Run and protect: repoStats, Return response: {} (logUtils:54)* * supervdsm.log *MainProcess|jsonrpc/7::DEBUG::2017-07-03 15:15:01,661::supervdsmServer::93::SuperVdsm.ServerCallback::(wrapper) call network_caps with () {}MainProcess|jsonrpc/7::DEBUG::2017-07-03 15:15:01,693::commands::69::root::(execCmd) /usr/bin/taskset --cpu-list 0-23 /sbin/ip route show to 0.0.0.0/0 <http://0.0.0.0/0> table main (cwd None)MainProcess|jsonrpc/7::DEBUG::2017-07-03 15:15:01,697::commands::93::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0MainProcess|jsonrpc/7::DEBUG::2017-07-03 15:15:01,748::commands::69::root::(execCmd) /usr/bin/taskset --cpu-list 0-23 /usr/sbin/tc qdisc show (cwd None)MainProcess|jsonrpc/7::DEBUG::2017-07-03 15:15:01,753::commands::93::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0MainProcess|jsonrpc/7::DEBUG::2017-07-03 15:15:01,754::supervdsmServer::100::SuperVdsm.ServerCallback::(wrapper) return network_caps with {'bridges': {'vmbr200': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.200'], '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': '50', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '525', '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': '500'}}, 'vmbr201': {'ipv6autoconf': True, 'addr': '172.30.0.11', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '172.30.255.254', 'dhcpv4': False, 'netmask': '255.255.0.0', 'ipv4defaultroute': True, 'stp': 'on', 'ipv4addrs': ['1.1.1.1/16' <http://1.1.1.1/16'>], 'mtu': '1500', 'ipv6gateway': 'fe80::be5f:f4ff:fe52:96c1', 'ports': ['em1.201'], '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': '0', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', 'topology_change_detected': '0', 'priority': '32768', 'multicast_membership_interval': '26000', 'root_path_cost': '100', 'root_port': '1', 'multicast_querier': '0', 'multicast_startup_query_count': '2', 'nf_call_iptables': '0', 'topology_change': '0', 'hello_time': '200', 'root_id': '8000.0013725e0ff1', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '627', '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': '500'}}, 'vmbr202': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.202'], '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': '50', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '525', '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': '500'}}, 'vmbr210': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.210'], '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': '51', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '526', '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': '500'}}, 'vmbr206': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.206'], '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': '50', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '526', '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': '500'}}, 'vmbr260': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.260'], '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': '51', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '526', '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': '500'}}, 'vmbr207': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.207'], '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': '51', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '526', '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': '500'}}, 'vmbr208': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.208'], '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': '51', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.b8ac6f90cb99', 'bridge_id': '8000.b8ac6f90cb99', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '526', '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': '500'}}, 'vmbr101': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': [], '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': '51', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max': '512', 'stp_state': '1', '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.000000000000', 'bridge_id': '8000.000000000000', 'topology_change_timer': '0', 'ageing_time': '30000', 'nf_call_ip6tables': '0', 'gc_timer': '527', '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': '500'}}, 'vmbr100': {'ipv6autoconf': True, 'addr': '', 'dhcpv6': False, 'ipv6addrs': [], 'gateway': '', 'dhcpv4': False, 'netmask': '', 'ipv4defaultroute': False, 'stp': 'on', 'ipv4addrs': [], 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['em1.100'], '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': '49', 'multicast_querier_interval': '25500', 'max_age': '2000', 'hash_max':* Thanks in Advance! Best Regards, Gabriel

2 1

Upgrading HC from 4.0 to 4.1
by Gianluca Cecchi 05 Jul '17

05 Jul '17

Hello, I'm going to try to update to 4.1 an HC environment, currently on 4.0 with 3 nodes in CentOS 7.3 and one of them configured as arbiter Any particular caveat in HC? Are the steps below, normally used for Self Hosted Engine environments the only ones to consider? - update repos on the 3 hosts and on the engine vm - global maintenance - update engine - update also os packages of engine vm - shutdown engine vm - disable global maintenance - verify engine vm boots and functionality is ok Then - update hosts: preferred way will be from the gui itself that takes care of moving VMs, maintenance and such or to proceed manually? Is there a preferred order with which I have to update the hosts, after updating the engine? Arbiter for first or as the latest or not important at all? Any possible problem having disaligned versions of glusterfs packages until I complete all the 3 hosts? Any known bugs passing from 4.0 to 4.1 and related glusterfs components? Thanks in advance, Gianluca

3 10

How can a Responsive website benefit your business?
by gajla parvin 05 Jul '17

05 Jul '17

--_000_PN1PR01MB0221DC7E1719654599CA5D3CF4D40PN1PR01MB0221INDP_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello Sir/Mam, By the end of 2017, the number of customers using mobile devices to browse = the Web is projected to reach 5 billion people because customers are lookin= g for your business on their mobile phones, it=92s the perfect opportunity = to expand your online presence with a mobile website. How can a mobile website benefit your business? When customers are looking for a business on their mobile devices, it=92s n= ot because they=92re casually shopping or researching. They=92re searching = for a particular product or service because they have a pressing need to lo= cate that product or service. So when you have a mobile website that appear= s during a user=92s search-and-find mission, you let your customers know th= at you=92re open and ready for business . . . right at the moment they need= you. We offer a new mobile website service that makes it easy for mobile users t= o find your business online. With our service, you can: Launch a mobile website in weeks: With our intuitive user interface, we ca= n create a mobile website for your business in weeks. Leverage your current website address: Our technology detects when custome= rs are using a mobile device and then presents your mobile website to them = using the same domain address. That=92s way, there=92s no need to choose a = new website address for your business. Optimize your website for mobile users: A screen with easy-to-read icons h= elps users quickly navigate to the information they need. Maximize your business presence: Because mobile users can search for your = business anywhere, anytime, a mobile website gives your business 24=D77 exp= osure. OUR PROCESS: =95 STEP 1 =96 PLANNING =95 STEP 2 =96 DESIGN =95 STEP 3 =96 CODING =95 STEP 4 =96 CONTENT =95 STEP 5 - WEBSITE SETUP =95 STEP 6 =96 REVIEW =95 STEP 7 - TESTING & LAUNCH =95 STEP 8 - HANDOVER & SUPPORT Some of the Web Design & Development services that we offer: =95 HTML5 & CSS3 Coding =95 AJAX & JQuery Development =95 PHP Web Development =95 Responsive Web Design =95 Mobile Web Design =95 Content Management Systems &Framework. If you=92re ready to make your mobile website now, please email us back. Thanks & Regards Marketing Executive Note: - If this is something you are interested, please respond to this ema= il. If this is not your interest, don't worry, we will not email you again. --_000_PN1PR01MB0221DC7E1719654599CA5D3CF4D40PN1PR01MB0221INDP_ Content-Type: text/html; charset="Windows-1252" Content-ID: <5BDB643C688FD0419571BB962A90AD82(a)INDPRD01.PROD.OUTLOOK.COM> Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)"> <style>  </style> </head> <body lang=3D"EN-US"> <div class=3D"Section1"> Hello Sir/Mam,<o:p></o:p> By the end of 2017, the number of customers using mobile devices = to browse the Web is projected to reach 5 billion people because customers = are looking for your business on their mobile phones, it=92s the perfect opportunity to expand your online presence with a mobil= e website.<o:p></o:p> How can a mobile website benefit your business= ?<o:p></o:p> <o:p> </o:p></= span> When customers are = looking for a business on their mobile devices, it=92s not because they=92r= e casually shopping or researching. They=92re searching for a particular pr= oduct or service because they have a pressing need to locate that product or service. So when you have a mobile website = that appears during a user=92s search-and-find mission, you let your custom= ers know that you=92re open and ready for business . . . right at the momen= t they need you.<o:p></o:p> We offer a new mobi= le website service that makes it easy for mobile users to find your busines= s online. With our service, you can:<o:p></o:p> <o:p> </o:p></= span> Launch a mobile website in weeks:  With our intuitive user interface, we can creat= e a mobile website for your business in weeks.<o:p></o:p> <o:p> </o:p></= span> Leverage your current website address:<spa= n style=3D"color:#333399">  Our technology detects when customers are = using a mobile device and then presents your mobile website to them using t= he same domain address. That=92s way, there=92s no need to choose a new website address for your business.<o:p></o:p></spa= n> <o:p> </o:p></= span> Optimize your website for mobile users:<sp= an style=3D"color:#333399">  A screen with easy-to-read icons helps us= ers quickly navigate to the information they need.<o:p></o:p> <o:p> </o:p= > Maximize your business presence:  Because mobile users can search for your busines= s anywhere, anytime, a mobile website gives your business 24=D77 exposure.<= /span><o:p></o:p> O= UR PROCESS:<o:p></o:p>         &= nbsp;   =95   STEP 1 =96 = PLANNING<o:p></o:p>    &= nbsp;        =95   STEP 2 =96 = DESIGN<o:p></o:p>    &= nbsp;        =95   STEP 3 =96 = CODING<o:p></o:p>    &= nbsp;        =95   STEP 4 =96 = CONTENT<o:p></o:p>    &= nbsp;        =95   STEP 5 - WE= BSITE SETUP<o:p></o:p>    &= nbsp;        =95   STEP 6 =96 = REVIEW<o:p></o:p>    &= nbsp;        =95   STEP 7 - TE= STING & LAUNCH<o:p></o:p>    &= nbsp;        =95   STEP 8 - HA= NDOVER & SUPPORT<o:p></o:p> <o:p> </o:p></= span> S= ome of the Web Design & Development services that we offer:<o:p>= </o:p>    &= nbsp;        =95    HTML5 & CSS3 Coding<o:p></o= :p>    &= nbsp;        =95    AJAX = & JQuery Development<o:p></o:p>    &= nbsp;        =95    PHP W= eb Development<o:p></o:p>    &= nbsp;        =95    Respo= nsive Web Design<o:p></o:p>    &= nbsp;        =95    Mobil= e Web Design         <o:p></o:= p>    &= nbsp;        =95    Conte= nt Management Systems &Framework.<o:p></o:p> <o:p> </o:p></= span> If you=92re ready to make your mobile website now, please email us = back.<o:p></o:p> Thanks & Regards Marketing Executive Note: - If this is something you are interested, please respond to t= his email. If this is not your interest, don't worry, we will not email you= again.<o:p></o:p></span= > </div> </body> </html> --_000_PN1PR01MB0221DC7E1719654599CA5D3CF4D40PN1PR01MB0221INDP_--

1 0

Best practices for LACP bonds on oVirt
by Vinícius Ferrão 05 Jul '17

05 Jul '17

Hello, I’m deploying oVirt for the first time and a question has emerged: what is the good practice to enable LACP on oVirt Node? Should I create 802.3ad bond during the oVirt Node installation in Anaconda, or it should be done in a posterior moment inside the Hosted Engine manager? In my deployment we have 4x GbE interfaces. eth0 and eth1 will be a LACP bond for management and servers VLAN’s, while eth1 and eth2 are Multipath iSCSI disks (MPIO). Thanks, V.

7 21