Re: [ovirt-users] ovirtmgmt network out of sync

[Alex R]

Hi Michael, thanks for the suggestion.  When I use the GUI I get the error

"Error while executing action HostSetupNetworks: Network is currently being
used"

The network is in use by the engine, that is why I asked if there is a was
to sync via the CLI.

This problem happened after I did the latest upgraded and the host had lost
the /etc/sysconfig/netowrk-scripts/ifcfg-ovirtmgmt file.  So I recreated
the file and I thought alll was well except I cannot open a from outside of
the host and engine network (10.3.1.0/24).

source 10.3.5.0/24 cannot open console on at the destination 10.3.1.0/24.
The error I get is:

"Unable to connect to the graphic server /tmp/mozilla_digger0/console.vv
could not connect to 10.3.1.7:Socket I/O timed out"

I have already verified that the iptables rules are open and I have
verified that ASA that is between the network is not blocking by doing both
a packet-tracer and reviewing the logs.

I think the problem is this "out-of-sync" network issue?

-Alex


On Tue, May 16, 2017 at 10:12 PM, Michael Burman  wrote:

> Hello Alex,
>
> - Have you tried to sync it using the 'Sync All Networks' button in the
> UI?
> It's located under 'Hosts' main tab > select the host > 'Network
> Interfaces' sub tab > 'Sync All Networks' button.
>
> - Can you please go to the 'Setup Host Networks' dialog(located under the
> same path^^) and hoover on top of ovirtmgmt network? a tooltip should
> pop-up and it should let you know what is the reason that the network is
> being out-of-sync. Engine probably complaining about a difference between
> the configuration on the host and the DC.
> - How did you end up with this situation? what happened before the network
> become out-of-sync? did it happened after the hosted-engine deploy was
> done?
>
> Best regards,
>
> On Wed, May 17, 2017 at 12:10 AM, Alex R  wrote:
>
>> No one has suggestions on how I can sync the ovirtmgmt network?  Is more
>> information needed?
>>
>>
>> On May 12, 2017 10:43 AM, "Alex R"  wrote:
>>
>>> Hi,
>>>
>>> I upgraded to the latest version (users@ovirt.org) a few weeks ago and
>>> ever since then I cannot open a console unless I am on the local network (
>>> 10.3.1.0/24).  I think it is related to the Ovirtmgmt interface being
>>> "out-of-sync".
>>>
>>> If I try to fix it in the gui, I get an error:
>>>
>>> "Error while executing action HostSetupNetworks: Network is currently
>>> being used"
>>>
>>> This is because the hosted engine in on the ovirtmgmt network.
>>>
>>> Is there a way I can fix this via cli?  This is a single host with a
>>> hosted engine.  I use it for development only.
>>>
>>> Thank you.
>>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Michael Burman
> RedHat Israel, RHV-M Network QE
>
> Mobile: 054-5355725
> IRC: mburman
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirtmgmt network out of sync

[Michael Burman]

Hello Alex,

- Have you tried to sync it using the 'Sync All Networks' button in the
UI?
It's located under 'Hosts' main tab > select the host > 'Network
Interfaces' sub tab > 'Sync All Networks' button.

- Can you please go to the 'Setup Host Networks' dialog(located under the
same path^^) and hoover on top of ovirtmgmt network? a tooltip should
pop-up and it should let you know what is the reason that the network is
being out-of-sync. Engine probably complaining about a difference between
the configuration on the host and the DC.
- How did you end up with this situation? what happened before the network
become out-of-sync? did it happened after the hosted-engine deploy was
done?

Best regards,

On Wed, May 17, 2017 at 12:10 AM, Alex R  wrote:

> No one has suggestions on how I can sync the ovirtmgmt network?  Is more
> information needed?
>
>
> On May 12, 2017 10:43 AM, "Alex R"  wrote:
>
>> Hi,
>>
>> I upgraded to the latest version (users@ovirt.org) a few weeks ago and
>> ever since then I cannot open a console unless I am on the local network (
>> 10.3.1.0/24).  I think it is related to the Ovirtmgmt interface being
>> "out-of-sync".
>>
>> If I try to fix it in the gui, I get an error:
>>
>> "Error while executing action HostSetupNetworks: Network is currently
>> being used"
>>
>> This is because the hosted engine in on the ovirtmgmt network.
>>
>> Is there a way I can fix this via cli?  This is a single host with a
>> hosted engine.  I use it for development only.
>>
>> Thank you.
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Michael Burman
RedHat Israel, RHV-M Network QE

Mobile: 054-5355725
IRC: mburman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirtmgmt network out of sync

[Alex R]

No one has suggestions on how I can sync the ovirtmgmt network?  Is more
information needed?


On May 12, 2017 10:43 AM, "Alex R"  wrote:

> Hi,
>
> I upgraded to the latest version (users@ovirt.org) a few weeks ago and
> ever since then I cannot open a console unless I am on the local network (
> 10.3.1.0/24).  I think it is related to the Ovirtmgmt interface being
> "out-of-sync".
>
> If I try to fix it in the gui, I get an error:
>
> "Error while executing action HostSetupNetworks: Network is currently
> being used"
>
> This is because the hosted engine in on the ovirtmgmt network.
>
> Is there a way I can fix this via cli?  This is a single host with a
> hosted engine.  I use it for development only.
>
> Thank you.
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Internet access for oVirt Nodes?

[Ryan Barry]

On Mon, May 15, 2017 at 1:09 PM, Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:

> thanks, i guess configuring repositories in oVirt Node can only be
> achieved when using Foreman/Satellite integration, is that correct? i've
> just started to use oVirt Node and i'm beginning to realize that things are
> a _little_ bit different compared to a standard linux host.
>

Well, yes/no. We whitelist which packages are able to be updated from the
oVirt repositories and disable the base centos repositories, but you can
easily change "enabled=0" to "enabled=1" in any of them, or add your own
repos just like you would with CentOS.

In general, I'd recommend not including updates for any packages which are
part of Node itself, but that decision is yours to make.


>
> this brings me to another update related question:
> right now oVirt Nodes in my test environment can connect to the internet
> and there recently was an update available which i applied through the
> engine gui, which seemed to finish successfully. i remember wondering how i
> could check what actually changend, there was eg. no kernel change IIRC.
> today i discovered that on both updated hosts /tmp/imgbased.log exists and
> ends in an error:
>

Node is still an A/B image, so you'd need to reboot in order to see a new
kernel, if it's part of a new image.


>
> subprocess.CalledProcessError: Command '['lvcreate', '--thin',
> '--virtualsize', u'8506048512B', '--name', 
> 'ovirt-node-ng-4.1.1.1-0.20170406.0',
> u'HostVG/pool00']' returned non-zero exit status 5
>
> i have to mention i manually partitioned my oVirt Node host when i
> installed it from the installer ISO (because i want to use software raid).
> i used partitioning recommendations from https://bugzilla.redhat.com/sh
> ow_bug.cgi?id=1369874 (doubling size recommendations).
>

As long as you're thinly provisioned, this should update normally,, though
I have to say that I haven't tried software RAID.


>
> did my oVirt Node update complete successfully?
> how can i check this?
> why was there an lvcreate error?
>

I'll try to reproduce this, but attempting the lvcreate by hand may give
some usable debugging information.


>
> 'imgbase layout' says:
> ovirt-node-ng-4.1.1.1-0.20170406.0
>  +- ovirt-node-ng-4.1.1.1-0.20170406.0+1
>

If 'imgabase layout' only shows these, then it's likely that it didn't
update. Node uses LVM directly, so "lvm lvs" may show a new device, but
from the command above, I'm guessing it wasn't able to create it. I'd
suspect that it wasn't able to create it because it's the same version, and
LVM sees a duplicate LV. Can you attach your engine log (or the yum log
from the host) so we can see what it pulled?


>
> kernel version is:
> 3.10.0-514.10.2.el7.x86_64
>
> thanks a lot again
>




-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Regenerating SSL keys

[Jamie Lawrence]

> On May 14, 2017, at 3:35 AM, Yedidyah Bar David  wrote:

> In addition to Yaniv's explanation below, can you explain why it was
> bad? That is, what software/process was broken by it? Please note that
> this is the CN of the CA's cert, not of the individual certs its signs
> (such as the one for the web server for https) - these have the FQDN
> you supplied to engine-setup as their CN.

You're absolutely right; my apologies for that red herring. I confused myself 
after too long at the keyboard.

>> The 5 random digits are supposed to be OK, and are actually a feature - it
>> ensures uniqueness if you re-generate (most likely reinstall your Engine),
>> as otherwise some browsers fail miserably if a CA cert mismatches what they
>> know.
>> 
>> SAN is being worked on - we are aware of Chrome 58 now requiring it.
>> I sincerely hope to see it in 4.1.2 (see https://bugzilla.redhat.com/1449084
>> ).
> 
> Indeed, and see my comment 5 there for how to add SAN to an existing
> setup, _after_ you upgrade to 4.1.2 when it's out.

Great, that's handy.

> See also:
> 
> https://www.ovirt.org/documentation/how-to/networking/changing-engine-hostname/

Thanks for the pointer! That was the missing piece for me; my Google-fu failed 
to uncover it. I think I have what I need.

Thanks again to both of you,

-j
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Feature: enhanced OVA support

[Adam Litke]

Great feature!  I am glad to see you plan to use the existing imageio
framework for transferring data.

Will you allow export of VMs from a particular snapshot?  I guess that's
how you'll have to do it if you want to support export of running VMs.

I think you should definitely have a comment in the ovf to indicate that an
OVA was generated by a oVirt.  People will try to use this new feature to
import random OVAs from who knows where.  I'd also recommend adding a
version to this comment:  or
perhaps even a schema version in case you need to deal with compatibility
issues in the future.

I agree with Yaniv Kaul that we should offer to sparsify the VM to optimize
it for export.  We should also return compressed data.  When exporting,
does it make sense to cache the stored OVA file in some sort of ephemeral
storage (host local is fine, storage domain may be better) in order to
allow the client to resume or restart an interrupted download without
having to start from scratch?


On Sun, May 14, 2017 at 9:56 AM, Arik Hadas  wrote:

> Hi everyone,
>
> We would like to share our plan for extending the currently provided
> support for OVA files with:
> 1. Support for uploading OVA.
> 2. Support for exporting a VM/template as OVA.
> 3. Support for importing OVA that was generated by oVirt (today, we only
> support those that are VMware-compatible).
> 4. Support for downloading OVA.
>
> This can be found on the feature page
> 
> .
>
> Your feedback and cooperation will be highly appreciated.
>
> Thanks,
> Arik
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Adam Litke
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt nested in VMware

[Gianluca Cecchi]

On Tue, May 16, 2017 at 3:17 PM, Mark Duggan  wrote:

> Just bumping this in case anyone has any ideas as to what I might be able
> to do to potentially get this to work.
>
>
Hello,
I found some information about my lab in 2013.
I have verified I was using 5.1 so not exactly 5.5.
For that lab, where I ran Openstack Grizzly (and then IceHouse in a second
step), I was able to use nested VMs inside the virtual Hypervisors (based
on Qemu/KVM).
At that time I followed these two guides from virtuallyghetto for 5.0 and
5.1, that are still available.
It seems I didn't find a specific update for 5.5, so it could be that the
guide for 5.1 is still ok for 5.5.
Can you verify if you followed the same steps in configuring vSphere?
Note that the guides are for nesting Hyper-V but I used the same guidelines
to have a nested Qemu-KVM based hypervisor setup:

The guide for 5.0
http://www.virtuallyghetto.com/2011/07/how-to-enable-support-for-nested-64bit.html


The guide for 5.1
http://www.virtuallyghetto.com/2012/08/how-to-enable-nested-esxi-other.html

One important new setup thing for the 5.1 version was the step 3) in
section 

Step 3 - You will need to add one additional .vmx parameter which tells the
underlying guestOS (Hyper-V) that it is not running as a virtual guest
which in fact it really is. The parameter is hypervisor.cpuid.v0 = FALSE

HIH,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt nested in VMware

[Mark Duggan]

Just bumping this in case anyone has any ideas as to what I might be able
to do to potentially get this to work.

On 12 May 2017 at 13:57, Mark Duggan  wrote:

> Thanks Gianluca,
>
> So I installed the engine into a separate VM, and didn't go down the
> hosted-engine path, although if I was to look at this with physical hosts,
> this seems like a really good approach.
>
> To answer Michal's question from earlier, the nested VM inside the oVirt
> Hypervisors has been up for 23+ hours and it has not progressed past the
> Bios.
> Also, with respect to the vdsm-hooks, here's a list.
>
> Dumpxml attached (hopefully with identifying information removed)
>
> vdsm-hook-nestedvt.noarch
> vdsm-hook-vmfex-dev.noarch
> vdsm-hook-allocate_net.noarch
> vdsm-hook-checkimages.noarch
> vdsm-hook-checkips.x86_64
> vdsm-hook-diskunmap.noarch
> vdsm-hook-ethtool-options.noarch
> vdsm-hook-extnet.noarch
> vdsm-hook-extra-ipv4-addrs.x86_64
> vdsm-hook-fakesriov.x86_64
> vdsm-hook-fakevmstats.noarch
> vdsm-hook-faqemu.noarch
> vdsm-hook-fcoe.noarch
> vdsm-hook-fileinject.noarch
> vdsm-hook-floppy.noarch
> vdsm-hook-hostusb.noarch
> vdsm-hook-httpsisoboot.noarch
> vdsm-hook-hugepages.noarch
> vdsm-hook-ipv6.noarch
> vdsm-hook-isolatedprivatevlan.noarch
> vdsm-hook-localdisk.noarch
> vdsm-hook-macbind.noarch
> vdsm-hook-macspoof.noarch
> vdsm-hook-noipspoof.noarch
> vdsm-hook-numa.noarch
> vdsm-hook-openstacknet.noarch
> vdsm-hook-pincpu.noarch
> vdsm-hook-promisc.noarch
> vdsm-hook-qemucmdline.noarch
> vdsm-hook-qos.noarch
> vdsm-hook-scratchpad.noarch
> vdsm-hook-smbios.noarch
> vdsm-hook-spiceoptions.noarch
> vdsm-hook-vhostmd.noarch
> vdsm-hook-vmdisk.noarch
> vdsm-hook-vmfex.noarch
>
> I'm running ESXi 5.5. For the hypervisor VMs I've set the "Expose Hardware
> Assisted Virtualization to the guest OS"
>
> Hypervisor VMs are running CentOS 7.3
>
> [image: Inline images 1]
>
> On 12 May 2017 at 09:36, Gianluca Cecchi 
> wrote:
>
>>
>>
>> On Fri, May 12, 2017 at 1:06 PM, Michal Skrivanek <
>> michal.skriva...@redhat.com> wrote:
>>
>>>
>>> > On 11 May 2017, at 19:52, Mark Duggan  wrote:
>>> >
>>> > Hi everyone,
>>> >
>>> > From reading through the mailing list, it does appear that it's
>>> possible to have the ovirt nodes/hosts be VMware virtual machines, once I
>>> enable the appropriate settings on the VMware side. All seems to have gone
>>> well, I can see the hosts in the ovirt interface, but when I attempt to
>>> create and start a VM it never gets past printing the SeaBios version and
>>> the machine UUID to the screen/console. It doesn't appear to try to boot
>>> from the hard disk or an ISO that I've attached.
>>> >
>>> > Has anyone else encountered similar behaviour?
>>>
>>> I wouldn’t think you can even get that far.
>>> It may work with full emulation (non-kvm) but we kind of enforce it in
>>> oVirt so some changes are likely needed.
>>> Of course even if you succeed it’s going to be hopelessly slow. (or
>>> maybe it is indeed working and just runs very slow)
>>>
>>> Nested on a KVM hypervisor runs ok
>>>
>>> Thanks,
>>> michal
>>>
>>>
>> In the past I was able to get an Openstack Icehouse environment running
>> inside vSphere 5.x for a POC (on poweful physical servers) and performance
>> of nested VMs inside the virtual compute nodes was acceptable.
>> More recently I configured a standalone ESXi server 6.0 U2 on a Nuc6 with
>> 32Gb of ram and 2 ssd disks and on it I have now running 2 kinds of
>> environments (just verified they are still on after some months I abandoned
>> them to their destiny... ;-)
>>
>> 1) an ESXi VM acting as a single oVirt host (4.1.1 final or pre, I don't
>> remember) with self hosted engine (that itself becomes an L2 VM) and also
>> another VM (CentOS 6.8)
>> See here a screenshot of the web admin gui with a spice console open
>> after connecting to the engine:
>> https://drive.google.com/file/d/0BwoPbcrMv8mvanpTUnFuZ2FURms
>> /view?usp=sharing
>>
>> 2) a virtual oVirt gluster environment based on 4.0.5 with 3 Virtual
>> Hosts (with one as arbiter node if I remember correctly)
>>
>> On this second environment I have ovirt01, virt02 and ovirt03 VMs:
>>
>> [root@ovirt02 ~]# hosted-engine --vm-status
>>
>>
>> --== Host 1 status ==--
>>
>> Status up-to-date  : True
>> Hostname   : ovirt01.localdomain.local
>> Host ID: 1
>> Engine status  : {"reason": "vm not running on this
>> host", "health": "bad", "vm": "down", "detail": "unknown"}
>> Score  : 3042
>> stopped: False
>> Local maintenance  : False
>> crc32  : 2041d7b6
>> Host timestamp : 15340856
>> Extra metadata (valid at timestamp):
>> metadata_parse_version=1
>> metadata_feature_version=1
>> timestamp=15340856 (Fri May 12 14:59:17 2017)
>> host-id=1
>> score=3042
>> 

Re: [ovirt-users] Permissions to Import VMs

[Arik Hadas]

On Mon, May 15, 2017 at 11:36 PM, Peter Wood  wrote:

> Hi,
>
> I have a group of local users with permissions to create VMs, templates,
> and VMs from templates. They are allowed to work only in one of the
> clusters in the datacenter.
>
> Now I want one of the local users to be able to import VMs and convert
> them into templates and I just can't find the recipe for that.
>
> The group has these permissions:
>
> LocalUsersGroup -> [PowerUserRole] -> DEV1 (Cluster)
> LocalUsersGroup -> [PowerUserRole] -> SAN (Storage)
> LocalUsersGroup -> [TemplateCreator] -> OFFICE (Datacenter)
>
> LocalUserA is part of LocalUsersGroup and should be able to:
>   - Import a VM
>   - Convert the VM to a template for everyone to use
>   - Delete the VM
>
> I tried this: LocalUserA -> [VmImporterExporter] -> System
>
> LocalUserA can now import VMs and convert them to templates but it can't
> delete the imported VMs. For some reason [UserVmManager] role is not
> assigned to LocalUserA on the VMs that were imported.
>

Right, that seems to be a bug. The import operation should set the user
that executes it with UserVmManager role on the imported VM, just like add
VM does for regular VM creation.
Could you please file a bug?


>
> Before I start messing around I'd appreciate somebody's else opinion on
> how this should be done.
>
>
Thank you for your time,
>
> -- Peter
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] migration of a VM: fails

[cmc]

Hi,

Just trying to place in maintenance mode for a version upgrade, and
one VM fails to migrate. The other 20-odd move over successfully. In
/var/log/libvirt/qemu/, the VM's log on the source reports:

2017-05-16 09:48:06.339+: initiating migration
2017-05-16T09:52:25.498932Z qemu-kvm: socket_writev_buffer: Got err=32
for (131328/18446744073709551615)
2017-05-16 09:52:47.311+: initiating migration
2017-05-16T09:57:06.755402Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 09:57:55.109+: initiating migration
2017-05-16T10:02:14.143221Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:02:59.497+: initiating migration
2017-05-16T10:07:18.542872Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:08:03.896+: initiating migration
2017-05-16T10:12:23.206731Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:13:08.941+: initiating migration
2017-05-16T10:17:27.861843Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:18:13.690+: initiating migration
2017-05-16T10:22:32.929689Z qemu-kvm: socket_writev_buffer: Got err=32
for (69803/18446744073709551615)
2017-05-16 10:23:19.846+: initiating migration
2017-05-16T10:27:39.175724Z qemu-kvm: socket_writev_buffer: Got err=32
for (69776/18446744073709551615)
2017-05-16 10:28:25.141+: initiating migration
2017-05-16T10:28:35.620070Z qemu-kvm: socket_writev_buffer: Got err=32
for (65753/18446744073709551615)
2017-05-16 10:29:10.678+: initiating migration
2017-05-16T10:33:29.718527Z qemu-kvm: socket_writev_buffer: Got err=32
for (53477/18446744073709551615)
2017-05-16 10:38:35.517+: initiating migration


On the destination host, it reports:

2017-05-16T10:33:29.598425Z qemu-kvm: Unknown combination of migration flags: 0
2017-05-16T10:33:29.599524Z qemu-kvm: error while loading state
section id 2(ram)
2017-05-16T10:33:29.601978Z qemu-kvm: load of migration failed: Invalid argument
2017-05-16 10:33:29.808+: shutting down

In the engine log:

2017-05-16 11:57:28,675+01 INFO
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(DefaultQuartzScheduler5) [f8aa18b3-97b9-48e2-a681-cf3aaed330a5] VM
'4921c5f5-7748-47eb-a90c-8e9ecbd91bcf'(pete_win7) was unexpectedly
detected as 'MigratingTo' on VDS
'424e6317-ad68-459b-bf88-7292e26710ae'(kvm-ldn-02) (expected on
'e050c27f-8709-404c-b03e-59c0167a824b')


It stays in 'preparing for maintenance mode' on the GUI for the host,
and reports errors on the status pane below, but then it reports that
the host has successfully been put into maintenance mode, even though
the VM is still showing as in migration. After more time has elapsed,
it reports a failure again, and then eventually the host will again
report it is in maintenance mode, and so on.

When I hit 'cancel migration' it reports that the migration has been
successfully cancelled in the status pane at the bottom, but then
shows it still in migration in the upper window. When I select the VM
itself, it reports it is "Migrating From: 99%". If I cancel the
migration here, it actually does cancel the migration properly.

The VM itself is up and running ok.

Version of oVirt is 4.1.0.4-1.el7

Thanks in advance for any help. Please let me know if you need any full logs.

Regards,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Smtp configuration for notification

[wodel youchi]

Hi,

When we install the vm engine, in the configuration process we are asked to
give an smtp server and email addresses for notification but then nothing.
When we looked to the event notification configuration we found this
file ovirt-engine-notifier.conf and we thought that the first configuration
was there but since the notification service was disabled notifications
were not working, but No, there was no configuration on that file we had to
modify it and now notifications are working.
The question is : is the first smtp configuration used ? If yes, when? Can
we test it ? And if we want to modify it, where the configuration is stored
?

Regards
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Backup ovirt engine

[Simone Tiraboschi]

On Mon, May 15, 2017 at 5:04 PM,  wrote:

>
> I'm not sure how to backup the Ovirt engine to an external hard drive. I plan 
> on updating to Ovirt 3.6 (as I currently have 3.5), then centOS 7 (currently 
> using centOS 6), and after updating the Ovirt 3.6 to 4.0, but I want to have 
> a backup file on an external drive before going through with the updates.
>
>
The right tool is engine-backup

You should reach 3.6/el6 and then follow this guide to get 4.0/el7:
https://www.ovirt.org/documentation/migration-engine-36-to-40/


>
> Thanks
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt + Citrix Xenserver support?

[Shahar Havivi]

Please note that the Xen that you can import are Xen VMs on RHEL5.x

On Thu, May 11, 2017 at 6:14 PM, Sandro Bonazzola 
wrote:

>
>
> On Tue, May 9, 2017 at 12:29 PM, santosh bhabal 
> wrote:
>
>> Hello Experts,
>>
>> I am new to Ovirt community.
>>
>
> Hi, welcome to the oVirt community!
>
>
>
>> Apology if this question has asked earlier.
>> I just wanted to know that does Ovirt support Citrix Xenserver or not?
>>
>
> Sadly oVirt doesn't support Xen. There was an attempt in the past to
> support it, see http://www.ovirt.org/documentation/how-to/xen/ but it has
> been abanoned.
>
> However, we support conversion of VMs from Xen to oVirt (see
> http://www.ovirt.org/develop/release-management/features/
> virt/virt-v2v-integration/ )  so you can setup an oVirt datacenter next
> to the Xen one and move VMs to oVirt / KVM.
>
>
>
>>
>> Reagrds
>> Santosh.
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
>
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Self-Hosted Engine Deploy - CephFS Not a Storage Option

[Martin Sivak]

Hi,

I do not think there is any active effort to bring Ceph support to
hosted engine. Care to open an RFE in the bugzilla?

But we do not have any Ceph experts on the oVirt team at the moment so
I can't promise anything... Is there maybe a way to export Ceph using
some kind of proxy (multipath iscsi for example) that could be used
before the proper support is added?

Best regards

--
Martin Sivak
SLA / oVirt

On Mon, May 15, 2017 at 8:50 PM, Michael Poat  wrote:
> Hello,
>
> I currently have a 30 node ~200TB Raw Ceph storage primarily used as a
> CephFS POSIX Complaint storage for my enclave. Currently I am working on
> setting up a dual node High Availability ovirt 4.1 cluster. Considering
> avoiding any single points of failure, I would like to use CephFS as my
> storage domains and want to use the Self-Hosed Engine feature.
>
> When setting up the Self-Hosted Engine and reaching the steps for
> "Configuring Storage",  POSIX Compliant FS or CephFS is not an option...
>
> Prompt:
>
>  During customization use CTRL-D to abort.
>  Please specify the storage you would like to use (glusterfs, iscsi, fc,
> nfs3, nfs4)[nfs3]:
>
> Is there a work around for this or any future POSIX FS/CephFS Support for
> the Self-Hosted-Engine setup? I was able to create CephFS Domains within
> Ovirt and they work great. I was also wondering if it would be possible to
> migrate the self-hosted VM to the CephFS storage but this would require
> shutting down the VM itself, sort of a catch-22.
>
> Thanks,
>
> -Michael
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ovirt-devel] Feature: enhanced OVA support

[Yaniv Kaul]

On Mon, May 15, 2017 at 10:52 PM, Arik Hadas  wrote:

>
>
> On Mon, May 15, 2017 at 8:05 PM, Richard W.M. Jones 
> wrote:
>
>> On Sun, May 14, 2017 at 04:56:56PM +0300, Arik Hadas wrote:
>> > Hi everyone,
>> >
>> > We would like to share our plan for extending the currently provided
>> > support for OVA files with:
>> > 1. Support for uploading OVA.
>> > 2. Support for exporting a VM/template as OVA.
>> > 3. Support for importing OVA that was generated by oVirt (today, we only
>> > support those that are VMware-compatible).
>> > 4. Support for downloading OVA.
>> >
>> > This can be found on the feature page
>> > > rt/enhance-import-export-with-ova/>
>> > .
>> >
>> > Your feedback and cooperation will be highly appreciated.
>>
>> The plan as stated seems fine, but I have some reservations which I
>> don't think are answered by the page:
>>
>> (1) How will oVirt know the difference between an OVA generated
>> by oVirt and one generated by VMware (or indeed other sources)?
>> A VMware OVF has an XML comment:
>>
>> 
>>
>> but not any official metadata that I could see.
>
>
> So that's something that we have not decided on yet.
> Indeed, we need some indication of the system that generated the OVA and
> it makes sense to have it inside the OVF. I thought about a field that is
> part of the VM configuration, like the "origin" field of VMs in
> ovirt-engine. Having a comment like you mentioned is also an option.
>
>
>>
>> (By the way, I don't think importing via virt-v2v vs directly will be
>> any quicker.  The v2v conversion / device installation takes only a
>> fraction of the time.  Most of the time is consumed doing the format
>> conversion from VMDK to qcow2.  However you are correct that when you
>> know that the source is oVirt/KVM, you should not run virt-v2v.)
>>
>
> Note that the disks within the OVA will be of type qcow2. So not only that
> no v2v conversion / device installation is needed, but also no format
> conversion will be needed on the import and upload flows.
>
>
>>
>> (2) I think you're going to have a lot of fun generating OVAs which
>> work on VMware.  As Yaniv says, the devices aren't the same so you'd
>> be having to do some virt-v2v -like driver installation / registry
>> modification.  Plus the OVF file is essentially a VMware data dump
>> encoded as XML.  OVF isn't a real standard.  I bet there are a million
>> strange corner cases.  Even writing VMDK files is full of pitfalls.
>>
>> VMware has a reasonable V2V import tool (actually their P2V tooling is
>> very decent).  Of course it's proprietary, but then so is their
>> hypervisor.  Maybe oVirt can drive their tools?
>>
>
> No no, that fun is not part of the plan :)
> The OVAs we'll generate are supposed to contain:
> 1. OVF - it should be similar to the one virt-v2v generates for oVirt
> (that is similar to the one we use internally in oVirt for snapshots and
> for backup within storage domains, i.e., OVF-stores). We will definitely
> need some extensions, like an indication that the OVA was generated by
> oVirt. We may make some tweaks here and there, like removing network
> interfaces from the list of resources. But we already are generally aligned
> with what the specification says about OVFs.
>
> 2. qcow2 disks - thus, no conversion (device installation) and no format
> conversion will be needed (we may consider to convert them to raw later on,
> since they are expected to be the base volumes of the disks, not sure it
> worth the effort though).
>

I wonder if it's worth looking into several options when exporting:
1. Run virt-sysprep with 'harmless' operations such as
'abrt-data,backup-files,crash-data,tmp-files'

> 2. Run virt-sparsify on the disks.
3. Convert to compressed qcow2. In most cases it certainly can have a
significant saving (1:2 should be reasonable, but some can get 1:6 even) of
disk space (and later, file transfer times, etc).
If we are already converting, we can also convert from qcow2 to qcow2v3
(compat 0.1 to compat 1.1).

Y.


> I will add this to the feature page.
>
> We are aware to the fact that with this design, the OVAs could not be
> directly consumed by others, like VMware. But this could make it easier for
> them to make the needed conversion - they won't need to query the VM
> configuration from oVirt and won't need to lookup the disks inside oVirt's
> storage domains. Anyway, we assume that this conversion is done by other
> tools.
>
>
>> Rich.
>>
>> --
>> Richard Jones, Virtualization Group, Red Hat
>> http://people.redhat.com/~rjones
>> Read my programming and virtualization blog: http://rwmj.wordpress.com
>> Fedora Windows cross-compiler. Compile Windows programs, test, and
>> build Windows installers. Over 100 libraries supported.
>> http://fedoraproject.org/wiki/MinGW
>>
>
>
> ___
> Devel mailing list
> de...@ovirt.org
> 

[ovirt-users] Backup ovirt engine

[andrewzabomb]

I'm not sure how to backup the Ovirt engine to an external hard drive. I plan 
on updating to Ovirt 3.6 (as I currently have 3.5), then centOS 7 (currently 
using centOS 6), and after updating the Ovirt 3.6 to 4.0, but I want to have a 
backup file on an external drive before going through with the updates. 


Thanks
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`

[Barak Korren]

On 16 May 2017 at 09:51, Yedidyah Bar David  wrote:
>
> Re (1.), you should also note that currently, the engine is not even
> packaged properly for Fedora/CentOS. I know this sounds weird, as everyone
> uses the packages we provide, but it's true - these packages are not
> compliant with Fedora's packaging guidelines. Why? Because we use maven
> for building the engine, and package also many dependencies simply as
> a result of maven getting them from maven central. See also:
>
> https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605_resolved=0
>

I guess we could walk the middle ground here for DEBs just like we do
for RMPs no? Which means - have java dependency bundle packages and
release from resources.ovirt.org...

I would love to see a discussion on what it would take to get DEBs
through the CI system. I guess we would need some sort of
'build-artifacts.sh.deb' (Or deb8? dep9? not sure what is the
convention for Debian version shorthands), some Debian build slaves
and Debian equivalents of mock_runner.sh and repoan.


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`

[Yedidyah Bar David]

On Tue, May 16, 2017 at 9:51 AM, Yedidyah Bar David  wrote:
> On Mon, May 15, 2017 at 10:42 PM, Leni Kadali Mutungi
>  wrote:
>> On 5/15/17, Yedidyah Bar David  wrote:
>>
>>> Now is the time to explain something.
>>>
>>> ovirt-host-deploy is not designed to be ran manually like you try.
>>>
>>> You will get the exact same error if you try to do this on CentOS or
>>> Fedora.
>>>
>>> The normal way it works is that the engine "bundles" it in a tarball,
>>> copies it to the target host using ssh, untars it there and runs it.
>>>
>>> It then talks with it - the engine sends some stuff, host-deploy replies,
>>> etc.
>>>
>> I'm guessing this means I can now move on to building ovirt-engine.
>
> That would be great, but:
>
> 1. It will require a lot of work, mostly probably of packaging in Debian
> dependencies of the engine that are not yet there.
>
> 2. You'll be mostly walking the unwalked path. Most of the work on Debian
> support so far was on the hosts' side.
>
> Re (1.), you should also note that currently, the engine is not even
> packaged properly for Fedora/CentOS. I know this sounds weird, as everyone
> uses the packages we provide, but it's true - these packages are not
> compliant with Fedora's packaging guidelines. Why? Because we use maven
> for building the engine, and package also many dependencies simply as
> a result of maven getting them from maven central. See also:
>
> https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605_resolved=0

I now see (as I expected) that Debian has a similar policy:

https://wiki.debian.org/Java/MavenRepoSpec

Of course, you can still try to mostly follow the current rpm/maven
packaging, and have eventually something working. But Debian will
not accept it. To make Debian do accept it, you'll probably need to
"solve" the above bug first, for Debian. But perhaps Debian has better
tools for that than Fedora, so it might require less work :-)

>
> Best,
>
>>
>>> The protocol they use is described in otopi, in the file README.dialog.
>>>
>>> otopi has (currently) two "dialects" - "human" (default) and "machine".
>>> The engine and ovirt-host-deploy talk using the machine dialog.
>>>
>>> To make ovirt-host-deploy talk with you using the machine dialog,
>>> you should run it with:
>>>
>>> ovirt-host-deploy DIALOG/dialect=str:machine
>>>
>>> To make it let you configure it, run it with:
>>>
>>> ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True
>>>
>>> To know what it expects at each stage, I suggest to have a look at an
>>> ovirt-host-deploy log generated on el7 or fedora.
>>>
>> This is very useful; will definitely try this out.
>>> Anyway, congrats for a nice progress!
>> Thanks. I wouldn't have come this far without the community's help and
>> the documentation.
>>
 I tried starting the libvirtd service to see if that would make the
 VIRT/enable error go away or at least satisfy the requirements of
 ovirt-host-deploy, but it didn't seem to work.
>>>
>>> If you check such a log file, you'll see there (among other things):
>>>
>>> DIALOG:SEND   **%QStart: CUSTOMIZATION_COMMAND
>>> DIALOG:SEND   ###
>>> DIALOG:SEND   ### Customization phase, use 'install' to proceed
>>> DIALOG:SEND   ### COMMAND>
>>> DIALOG:SEND   **%QHidden: FALSE
>>> DIALOG:SEND   ***Q:STRING CUSTOMIZATION_COMMAND
>>> DIALOG:SEND   **%QEnd: CUSTOMIZATION_COMMAND
>>> DIALOG:RECEIVEenv-query -k VIRT/enable
>>> DIALOG:SEND   **%QStart: VIRT/enable
>>> DIALOG:SEND   ###
>>> DIALOG:SEND   ### Please specify value for 'VIRT/enable':
>>> DIALOG:SEND   ### Response is VALUE VIRT/enable=type:value or
>>> ABORT VIRT/enable
>>> DIALOG:SEND   ***Q:VALUE VIRT/enable
>>> DIALOG:SEND   **%QEnd: VIRT/enable
>>> DIALOG:RECEIVEVALUE VIRT/enable=bool:true
>>>
>>> "SEND" is what the host-deploy sends, "RECEIVE" is what the engine
>>> replies.
>>>
>>> So host-deploy sent a prompt asking for a customization command,
>>> the engine sent the command 'env-query -k VIRT/enable', host-deploy
>>> then asked the engine to provide a value for 'VIRT/enable', and the
>>> engine replied 'VIRT/enable=bool:true'.
>>>
>> Okay. Will try to look into this as well.
>>
 The other errors seem
 to be related to not having an IP address that ovirt-host-deploy can
 recognize. To package this for Debian, I would need to find the
 equivalent of yumpackager.py for aptitude/apt-get/apt, since it seems
 to be a dependency required by ovirt-host-deploy.
>>>
>>> As I said, you can ignore it for now. But IMO this isn't specific
>>> to Debian - search a bit and you'll find other similar cases.
>> Alright. Good to know. :)
>>
>>>

 TL;DR: How to enable the virt service and assign an IP address that
 ovirt-host-deploy can use.
 Write/Find a python script that is equivalent to yumpackager.py and
 miniyum.py so that that dependency for ovirt-host-deploy is 

Re: [ovirt-users] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`

[Yedidyah Bar David]

On Mon, May 15, 2017 at 10:42 PM, Leni Kadali Mutungi
 wrote:
> On 5/15/17, Yedidyah Bar David  wrote:
>
>> Now is the time to explain something.
>>
>> ovirt-host-deploy is not designed to be ran manually like you try.
>>
>> You will get the exact same error if you try to do this on CentOS or
>> Fedora.
>>
>> The normal way it works is that the engine "bundles" it in a tarball,
>> copies it to the target host using ssh, untars it there and runs it.
>>
>> It then talks with it - the engine sends some stuff, host-deploy replies,
>> etc.
>>
> I'm guessing this means I can now move on to building ovirt-engine.

That would be great, but:

1. It will require a lot of work, mostly probably of packaging in Debian
dependencies of the engine that are not yet there.

2. You'll be mostly walking the unwalked path. Most of the work on Debian
support so far was on the hosts' side.

Re (1.), you should also note that currently, the engine is not even
packaged properly for Fedora/CentOS. I know this sounds weird, as everyone
uses the packages we provide, but it's true - these packages are not
compliant with Fedora's packaging guidelines. Why? Because we use maven
for building the engine, and package also many dependencies simply as
a result of maven getting them from maven central. See also:

https://bugzilla.redhat.com/showdependencytree.cgi?id=1168605_resolved=0

Best,

>
>> The protocol they use is described in otopi, in the file README.dialog.
>>
>> otopi has (currently) two "dialects" - "human" (default) and "machine".
>> The engine and ovirt-host-deploy talk using the machine dialog.
>>
>> To make ovirt-host-deploy talk with you using the machine dialog,
>> you should run it with:
>>
>> ovirt-host-deploy DIALOG/dialect=str:machine
>>
>> To make it let you configure it, run it with:
>>
>> ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True
>>
>> To know what it expects at each stage, I suggest to have a look at an
>> ovirt-host-deploy log generated on el7 or fedora.
>>
> This is very useful; will definitely try this out.
>> Anyway, congrats for a nice progress!
> Thanks. I wouldn't have come this far without the community's help and
> the documentation.
>
>>> I tried starting the libvirtd service to see if that would make the
>>> VIRT/enable error go away or at least satisfy the requirements of
>>> ovirt-host-deploy, but it didn't seem to work.
>>
>> If you check such a log file, you'll see there (among other things):
>>
>> DIALOG:SEND   **%QStart: CUSTOMIZATION_COMMAND
>> DIALOG:SEND   ###
>> DIALOG:SEND   ### Customization phase, use 'install' to proceed
>> DIALOG:SEND   ### COMMAND>
>> DIALOG:SEND   **%QHidden: FALSE
>> DIALOG:SEND   ***Q:STRING CUSTOMIZATION_COMMAND
>> DIALOG:SEND   **%QEnd: CUSTOMIZATION_COMMAND
>> DIALOG:RECEIVEenv-query -k VIRT/enable
>> DIALOG:SEND   **%QStart: VIRT/enable
>> DIALOG:SEND   ###
>> DIALOG:SEND   ### Please specify value for 'VIRT/enable':
>> DIALOG:SEND   ### Response is VALUE VIRT/enable=type:value or
>> ABORT VIRT/enable
>> DIALOG:SEND   ***Q:VALUE VIRT/enable
>> DIALOG:SEND   **%QEnd: VIRT/enable
>> DIALOG:RECEIVEVALUE VIRT/enable=bool:true
>>
>> "SEND" is what the host-deploy sends, "RECEIVE" is what the engine
>> replies.
>>
>> So host-deploy sent a prompt asking for a customization command,
>> the engine sent the command 'env-query -k VIRT/enable', host-deploy
>> then asked the engine to provide a value for 'VIRT/enable', and the
>> engine replied 'VIRT/enable=bool:true'.
>>
> Okay. Will try to look into this as well.
>
>>> The other errors seem
>>> to be related to not having an IP address that ovirt-host-deploy can
>>> recognize. To package this for Debian, I would need to find the
>>> equivalent of yumpackager.py for aptitude/apt-get/apt, since it seems
>>> to be a dependency required by ovirt-host-deploy.
>>
>> As I said, you can ignore it for now. But IMO this isn't specific
>> to Debian - search a bit and you'll find other similar cases.
> Alright. Good to know. :)
>
>>
>>>
>>> TL;DR: How to enable the virt service and assign an IP address that
>>> ovirt-host-deploy can use.
>>> Write/Find a python script that is equivalent to yumpackager.py and
>>> miniyum.py so that that dependency for ovirt-host-deploy is satisfied
>>> as well.
>>
>> Last one will indeed be very interesting, but isn't mandatory for you
>> to continue, if your stated goal is to have a Debian host managed by
>> an oVirt engine. You can manually install all your stuff on the host,
>> and use offlinepackager so that host-deploy will not try to install
>> stuff for you. You'll then have a harder first-time-install, and
>> will miss checking for updates etc. For these you'll indeed need to
>> write something like debpackager, and probably minideb as well -
>> engine-setup uses it directly, as otopi's packager isn't enough for it.
>>
>> I'd like to mention another point. As 

Re: [ovirt-users] Setting up GeoReplication

[Sahina Bose]

On Mon, May 15, 2017 at 7:40 PM, Jim Kusznir  wrote:

> I tried to create a gluster volume on the georep node by running:
>
> gluster volume create engine-rep replica 1 georep.nwfiber.com:/mnt/gluste
> r/engine-rep
>
> I got back an error saying replica must be > 1.  So I tried to create it
> again:
>

"replica 1" is not required on command when you're not replicating to
another server.
So,

gluster volume create engine-rep georep.nwfiber.com:/mnt/gluster/engine-rep




> gluster volume create engine-rep replica 2 
> georep.nwfiber.com:/mnt/gluster/engine-rep
> server2.nwfiber.com:/mnt/gluster/engine-rep
>
> where server2 did not exist.  That failed too, but I don't recall the
> error message.
>
> gluster is installed, but when I try and start it with the init script, it
> fails to start with a complaint about reading the block file; my googling
> indicated that's the error you get until you've created a gluster volume,
> and that was the first clue to me that maybe I needed to create one first.
>
> So, how do I create a replica 1 volume?
>
>
> Thinking way ahead, I have a related replica question:  Currently my ovirt
> nodes are also my gluster nodes (replica 2 arbitrar 1).  Eventually I'll
> want to pull my gluster off onto dedicated hardware I suspect.  If I do so,
> do I need 3 servers, or is a replica 2 sufficient?  I guess I could have an
> ovirt node continue to be an arbitrar...  I would eventually like to
> distribute my ovirt cluster accross multiple locations with the option for
> remote failover (say location A looses all its network and/or power; have
> important VMs started at location B in addition to location B's normal
> VMs).  I assume at this point the recommended arch would be:
>
> 2 Gluster servers at each location
> Each location has a gluster volume for that location, and is georep for
> the other location (so all my data will physically exist on 4 gluster
> servers).  I probably won't have more than 2 or 3 ovirt hosts at each
> location, so I don't expect this to be a "heavy use" system.
>

To move to a dedicated gluster setup, 2 gluster servers + 1 oVirt node
holding the arbiter brick should work.

Distributed or stretch cluster does not work off the bat yet. If a volume
is geo-replicated to another location, the destination volume cannot be a
storage domain in a cluster, as geo-replication needs the destination
volume data to be in sync with master.
Another option is for the master volume/cluster is spread across
geographies - but this requires the network latency to be very low in order
for this to work as all operations are synchronous in gluster.
We're working on features in both gluster and Ovirt to support the
stretched cluster requirements.


> Am I on track?  I'd be interested to learn what others suggest for this
> deployment model.
>
> On Sun, May 14, 2017 at 11:09 PM, Sahina Bose  wrote:
>
>> Adding Aravinda
>>
>> On Sat, May 13, 2017 at 11:21 PM, Jim Kusznir 
>> wrote:
>>
>>> Hi All:
>>>
>>> I've been trying to set up georeplication for a while now, but can't
>>> seem to make it work.  I've found documentation on the web (mostly
>>> https://gluster.readthedocs.io/en/refactor/Administr
>>> ator%20Guide/Geo%20Replication/), and I found http://blog.gluster.org/
>>> 2015/09/introducing-georepsetup-gluster-geo-replication-setup-tool/
>>>
>>> Unfortunately, it seems that some critical steps are missing from both,
>>> and I can't figure out for sure what they are.
>>>
>>> My environment:
>>>
>>> Production: replica 2 + arbitrator running on my 3-node oVirt cluster, 3
>>> volumes (engine, data, iso).
>>>
>>> New geo-replication: Raspberry Pi3 with USB hard drive shoved in some
>>> other data closet off-site.
>>>
>>> I've installed rasbian-lite, and after much fighting, got
>>> glusterfs-*-3.8.11 installed.  I've created my mountpoint (USB hard drive,
>>> much larger than my gluster volumes), and then ran the command.  I get this
>>> far:
>>>
>>> [OK] georep.nwfiber.com is Reachable(Port 22)
>>> [OK] SSH Connection established r...@georep.nwfiber.com
>>> [OK] Master Volume and Slave Volume are compatible (Version: 3.8.11)
>>> [NOT OK] Unable to Mount Gluster Volume georep.nwfiber.com:engine-rep
>>>
>>> Trying it with the steps in the gluster docs also has the same problem.
>>> No long files are generated on the slave.  Log files on the master include:
>>>
>>> [root@ovirt1 geo-replication]# more georepsetup.mount.log
>>> [2017-05-13 17:26:27.318599] I [MSGID: 100030] [glusterfsd.c:2454:main]
>>> 0-glusterfs: Started running glusterfs version 3.8.11 (args:
>>>  glusterfs --xlator-option="*dht.lookup-unhashed=off" --volfile-server
>>> localhost --volfile-id engine -l /var/log/glusterfs/geo-repli
>>> cation/georepsetup.mount.log --client-pid=-1 /tmp/georepsetup_wZtfkN)
>>> [2017-05-13 17:26:27.341170] I [MSGID: 101190]
>>> [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread
>>> with index