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&hide_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 explained above, when the engine
>> adds a

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 1
>>> [2017-05-13 17:26:27.341260] E [socket.c:2309:socket_conn

[ovirt-users] Permissions to Import VMs

[Peter Wood]

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.

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

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

[Matthias Leopold]

Am 2017-05-15 16:33, schrieb Ryan Barry:

On Mon, May 15, 2017 at 5:00 AM,  wrote:


hi,

do hypervisors, that are running oVirt Node (not standard
CentOS/RHEL),
need internet access for updates or can they be in a private, non
routed
network (and updates happen via engine)? it seems the latter is the
case, but i want to be sure

thx
matthias


Engine isn't very particular about updating in this case. As long as
any repository is configured where 'yum check-update
ovirt-node-ng-image-update' is true, upgrades from engine will work.

In general, otopi's miniyum is a bit smarter than base yum, so
'check-update ...' is not always a reliable mechanism to verify this,
but yes, a local repo in a non-routed network which presents the
update will show an update from engine.


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.


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:


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/show_bug.cgi?id=1369874 (doubling size 
recommendations).


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

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

kernel version is:
3.10.0-514.10.2.el7.x86_64

thanks a lot again
matthias
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Arik Hadas]

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
> >  virt/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 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
>
___
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`

[Leni Kadali Mutungi]

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.

> 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 explained above, when the engine
> adds a host, it copies to it a bundle (tarfile). This bundle is not
> rpm/yum/dnf specific - it should work also on Debian. Normally,
> ovirt-host-deploy (the rpm package) is installed only on the engine
> machine. So if you do not care about the engine side for now, you
> should be able to try adding a Debian host to your engine already -
> just configure offline packager. This might be easier to debug then
> by manually running ovirt-host-deploy.
Well, my aim is to run oVirt *on* Debian, similar to how it is run and
used by users on say Fedora or RHEL/CentOS. So that's what is guiding
me. If your suggestions need to revised in the light of that, do let
me know.

- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Fwd: [Pkg-libvirt-discuss] Packaging oVirt for Debian

[Leni Kadali Mutungi]

Forwarding this so that it is seen on oVirt's mailing list as well. In
future, I'll try to make sure that I mail both the Debian
Virtualization team and the oVirt users insofar as the topic is
relevant to both sides.

-- Forwarded message --
From: Guido Günther 
Date: Mon, 15 May 2017 08:13:52 +0200
Subject: Re: [Pkg-libvirt-discuss] Packaging oVirt for Debian
To: Leni Kadali Mutungi 

On Mon, May 15, 2017 at 05:20:19AM +0300, Leni Kadali Mutungi wrote:
> Hello all. This is where I am so far with the compiling and packaging.
>
> http://lists.ovirt.org/pipermail/users/2017-April/081523.html

Nice you're making progress!

>
> I am now looking for how to enable the virt service and assign an IP
> address that
> ovirt-host-deploy can use.
>
> Also it seems that the yumpackager.py and miniyum.py scripts are
> dependencies for ovirt-host-deploy. So it seems I need to 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, because setting it to not use a package was a short-term
> solution to get it to run successfully.

Have a look at python-apt. That will allow you to write a wrapper
similar to miniyum.py.

>
> So if I could be pointed in the direction of a suitable script that
> would work with Debian's aptitude, apt-get and apt in a similar
> manner, I'd be much obliged.

Please keep them mailing list in cc: so more people get a chance to help
you!
Cheers,
 -- Guido



-- 
- Warm regards
Leni Kadali Mutungi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Michael Poat]

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

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

[Richard W.M. Jones]

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
> 
> .
> 
> 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.

(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.)

(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?

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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Arik Hadas]

On Mon, May 15, 2017 at 6:11 PM, Derek Atkins  wrote:

> Hi,
>
> Arik Hadas  writes:
>
> > 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.
>
> Sounds like a great plan.
>
> What's the chance that the export would enable an OVA that could be
> loaded back into VMware?
>

I'm afraid that would be too costly.
As far as I know, there are pretty good conversion tools for converting VMs
from KVM to VMware today [1] (which, btw, I consider to be a strength as
Eduardo mentioned before. we certainly not in favor of vendor lock-in). It
would only make sense for them to support converting the OVA we produce,
much like we extended virt-v2v for converting VMware's OVA not long ago -
and I'm pretty sure they won't object to do this, they have all the
building blocks - getting a VM as a single archive that complies with the
OVA standard should make it easy for them).

[1] https://www.youtube.com/watch?v=DJedam7TJWo (the relevant part starts
at 14:40)


>
> > Thanks,
> > Arik
>
> -derek
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Derek Atkins]

Hi,

Arik Hadas  writes:

> 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.

Sounds like a great plan.

What's the chance that the export would enable an OVA that could be
loaded back into VMware?

> Thanks,
> Arik

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
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 5:00 AM,  wrote:

>
> hi,
>
> do hypervisors, that are running oVirt Node (not standard CentOS/RHEL),
> need internet access for updates or can they be in a private, non routed
> network (and updates happen via engine)? it seems the latter is the
> case, but i want to be sure
>
> thx
> matthias


Engine isn't very particular about updating in this case. As long as any
repository is configured where 'yum check-update
ovirt-node-ng-image-update' is true, upgrades from engine will work.

In general, otopi's miniyum is a bit smarter than base yum, so
'check-update ...' is not always a reliable mechanism to verify this, but
yes, a local repo in a non-routed network which presents the update will
show an update from engine.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt-engine4, 404 - Not Found

[Martin Perina]

Hi David,

according to logs you are not able to connect to database. Looking at the
error you probably have misconfigured PotsgreSQL authentication. Please
take a look at [1] how PostgreSQL instance need to be configured if you
have selected manual PostgreSQL configuration.

Martin Perina


[1]
http://www.ovirt.org/documentation/install-guide/appe-Preparing_a_Local_Manually-Configured_PostgreSQL_Database_for_Use_with_the_oVirt_Engine/


On Mon, May 15, 2017 at 2:43 PM, David David  wrote:

> Hello
>
> Centos7.
>
> Fresh install engine 4.1
> Getting "404 - Not Found", while entering in webUI main page using https.
>
> how to fix it?
>
> engine.log in attachment.
>
>
> ___
> 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] Setting up GeoReplication

[Jim Kusznir]

I tried to create a gluster volume on the georep node by running:

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

I got back an error saying replica must be > 1.  So I tried to create it
again:

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.

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 1
>> [2017-05-13 17:26:27.341260] E [socket.c:2309:socket_connect_finish]
>> 0-glusterfs: connection to ::1:24007 failed (Connection refused
>> )
>> [2017-05-13 17:26:27.341846] E [glusterfsd-mgmt.c:1908:mgmt_rpc_notify]
>> 0-glusterfsd-mgmt: failed to connect with remote-host: local
>> host (Transport endpoint is not connected)
>> [2017-05-13 17:26:31.335849] I [MSGID: 101190]
>> [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread
>> with index 2
>> [2017-05-13 17:26:31.337545] I [MSGID: 114020] [client.c:2356:notify]
>> 0-engine-client-0: parent translators are ready, attempting co
>> nnect on transport
>> [2017-05-13 17:26:31.344485] I [MSGID: 114020] [client.c:2356:notify]
>> 0-engine-client-1: parent translators are ready, attempting co
>> nnect on transport
>> [2017-05-13 17:26:31.345146] I [rpc-clnt.c:1965:rpc_clnt_reconfig]
>> 0-engine-client-0: changing port to 49157 (from 0)
>> [2017-05-13 17:26:31.350868] I [MSGID: 114020] [client.c:2356:notify]
>> 0-engine-client-2: parent translators are ready, attempting co
>> nnect on transport
>> [2017-

[ovirt-users] Removing *250GB Disk from Gluster SD - Error

[Sven Achtelik]

Hi All,

I was trying to remove a  ~250GB Disk from a Gluster SD and the engine has gone 
crazy. The Storage latency went up dramatically, which caused a change of the 
spm and everything to get unresponsive for about 10-30 seconds. How do I remove 
such a big disk in a way that this doesn't happen again ? I anyone running 
gluster on with a caching option ? The Bricks are on a raid 5+0 and should be 
pretty fast. Are there any values that can be tuned in the Engine - maybe for 
the acceptance of a little more storage latency ?

Thank you,

Sven

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

[ovirt-users] ovirt-engine4, 404 - Not Found

[David David]

Hello

Centos7.

Fresh install engine 4.1
Getting "404 - Not Found", while entering in webUI main page using https.

how to fix it?

engine.log in attachment.
2017-05-15 16:14:57,877+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file 
'/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf'.
2017-05-15 16:14:57,878+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] The file '/etc/ovirt-engine/engine.conf' doesn't exist or isn't 
readable. Will return an empty set of properties.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/10-setup-database.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file 
'/etc/ovirt-engine/engine.conf.d/10-setup-dwh-database.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/10-setup-java.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/10-setup-jboss.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/10-setup-pki.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/11-setup-sso.conf'.
2017-05-15 16:14:57,879+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file 
'/etc/ovirt-engine/engine.conf.d/20-setup-jboss-overlay.conf'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file 
'/etc/ovirt-engine/engine.conf.d/50-ovirt-engine-extension-aaa-jdbc.conf'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Loaded file '/etc/ovirt-engine/engine.conf.d/50-ovirt-web-ui.conf'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'AAA_JAAS_KEYTAB_FILE' is ''.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'AAA_JAAS_PRINCIPAL_NAME' is ''.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'AAA_JAAS_TICKET_CACHE_FILE' is ''.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'AAA_JAAS_USE_KEYTAB' is 'false'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'AAA_JAAS_USE_TICKET_CACHE' is 'false'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'AAA_KRB5_CONF_FILE' is ''.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DASHBOARD_CACHE_UPDATE' is 'true'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DASHBOARD_INVENTORY_CACHE_UPDATE_INTERVAL' is '60'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DASHBOARD_UTILIZATION_CACHE_UPDATE_INTERVAL' is 
'300'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DWH_DB_DATABASE' is 'ovirt_engine_history'.
2017-05-15 16:14:57,880+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DWH_DB_DRIVER' is 'org.postgresql.Driver'.
2017-05-15 16:14:57,881+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DWH_DB_HOST' is 'localhost'.
2017-05-15 16:14:57,881+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool 
-- 40) [] Value of property 'DWH_DB_PASSWORD' is '***'.
2017-05-15 16:14:57,881+04 INFO  
[org.ovirt.engine.core.uutils.config.ShellLikeC

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

[Yaniv Kaul]

On Mon, May 15, 2017 at 10:43 AM, Eduardo Mayoral  wrote:

> As a user I must say this is a very welcome feature. I appreciate a lot
> that oVirt already makes it very easy to import VMs from VMWare .
>
> Allowing to export oVirt machines in OVA format, which as of today is the
> "lingua franca" of VM migrations offers a nice and clear path out of oVirt.
> Having an easy way to migrate out of oVirt makes me MORE likely to keep on
> using oVirt, not less.
>

There is some confusion around the OVA format that I'd like to clarify. OVA
is a very flexible format, in the sense that it's essentially an XML to
describe the VM, but the content within may be (and practically is)
whatever one feels like. A concrete example is a NIC - it can be (in
VMware's case) a vmxnet3 and in our case virtio-net driver. So the fact
there's a single XML that describes a VM has absolutely no assurance of an
interchangeability.
oVirt, via virt-v2v integration, took the additional step to actually
perform a conversion from VMware format and drivers and specs to KVM and
oVirt.

The other way is left as an exercise for the reader, I'm afraid.

The goal of this feature, among others, is to more easily share VMs and
templates between setups for example.
Y.


Eduardo Mayoral Jimeno (emayo...@arsys.es)
> Administrador de sistemas. Departamento de Plataformas. Arsys internet.+34 
> 941 620 145 ext. 5153 <+34%20941%2062%2001%2045>
>
> On 14/05/17 15:56, 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 listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> 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] Building ovirt-host-deploy gives `configure: error: otopi-devtools required but missing`

[Yedidyah Bar David]

On Wed, May 10, 2017 at 5:37 PM, Leni Kadali Mutungi
 wrote:
> Sorry for the silence. I've been doing some tinkering. I did what
> Jason did i.e. `./configure --enable-java-sdk --with-maven
> --with-otopi-sources=/home/user/otopi` since that's where I had
> checked out otopi. ./configure is able to locate where the
> otopi-bundle file is (/usr/share/otopi directory for me) with the
> options above. If you try to use the options `--otopi-bundle` or
> `--with-otopi-bundle`, you'll get a unrecognized option from
> ./configure.
>
> I then ran `sudo ovirt-host-deploy/src/bin/ovirt-host-deploy` at my
> command prompt and got the same error as that which Jason got.
> # ./src/bin/ovirt-host-deploy
> [ INFO  ] Stage: Initializing
>   Continuing will configure this host for serving as
> hypervisor. Are you sure you want to continue? (yes/no) yes
> [ INFO  ] Stage: Environment setup
>   Configuration files: []
>   Log file: /tmp/ovirt-host-deploy-20170425170102-6mdsx6.log
>   Version: otopi-1.7.0_master ()
>   Version: ovirt-host-deploy-1.7.0_master ()
> [ INFO  ] Stage: Environment packages setup
> [ ERROR ] Failed to execute stage 'Environment packages setup':
> Packager install not implemented
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
>
> Difference being that I wasn't doing the compilation as root, I was
> using sudo for elevated privileges. Looking at the log file, I saw the
> following errors:
> 2017-05-07 07:21:37,011+0300 DEBUG
> otopi.plugins.otopi.packagers.yumpackager yumpackager._boot:184 Cannot
> initialize miniyum
> Traceback (most recent call last):
>   File "/home/user/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py",
> line 176, in _boot
> self._refreshMiniyum()
>   File "/home/user/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py",
> line 134, in _refreshMiniyum
> constants.PackEnv.YUM_ENABLED_PLUGINS
>   File "/home/user/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py",
> line 61, in _getMiniYum
> from otopi import miniyum
>   File "/home/user/otopi/src/otopi/miniyum.py", line 17, in 
> import rpmUtils.miscutils
>
> Traceback (most recent call last):
>   File "/home/user/otopi/src/otopi/context.py", line 132, in _executeMethod
> method['method']()
>   File 
> "/home/user/ovirt-host-deploy/src/bin/../plugins/ovirt-host-deploy/vdsm/vdsmid.py",
> line 84, in _packages
> self.packager.install(('dmidecode',))
>   File "/home/user/otopi/src/otopi/packager.py", line 98, in install
> raise NotImplementedError(_('Packager install not implemented'))
> NotImplementedError: Packager install not implemented
>
> So as a workaround, I used the instructions in the README to create a
> file called /etc/ovirt-host-deploy.conf.d/50-offline-packager.conf to
> suppress this reaction.
> Contains the following instructions:
>
>   [environment:init]
>   ODEPLOY/offlinePackager=bool:True
>   PACKAGER/yumpackagerEnabled=bool:False
>
> This allowed it to run further than it did for Jason (and myself when
> I tried it out). The new error message I got was:
> user@localhost:~$ sudo ovirt-host-deploy/src/bin/ovirt-host-deploy
> [sudo] password for user:
> [ INFO  ] Stage: Initializing
>   Continuing will configure this host for serving as
> hypervisor. Are you sure you want to continue? (yes/no) y
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> ['/etc/ovirt-host-deploy.conf.d/50-fakevmstats.conf',
> '/etc/ovirt-host-deploy.conf.d/50-faqemu.conf',
> '/etc/ovirt-host-deploy.conf.d/50-offline-packager.conf']
>   Log file: /tmp/ovirt-host-deploy-20170509143602-zo5v24.log
>   Version: otopi-1.7.0_master ()
>   Version: ovirt-host-deploy-1.7.0_master ()
> [ INFO  ] Stage: Environment packages setup
> [ INFO  ] Stage: Programs detection
> [ INFO  ] Stage: Environment customization
> [ INFO  ] Kdump unsupported
> [ INFO  ] Stage: Setup validation
> [WARNING] Cannot validate host name settings, reason: resolved host
> does not match any of the local addresses
> [WARNING] Grubby not present - not setting kernel arguments.
> [ ERROR ] Failed to execute stage 'Setup validation': 'VIRT/enable'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
>
> Looking at the log file showed the following errors:
>
> 2017-05-09 14:36:02,309+0300 DEBUG otopi.context
> context._executeMethod:128 Stage boot METHOD
> otopi.plugins.otopi.packagers.yumpackager.Plugin._boot
> 2017-05-09 14:36:02,316+0300 DEBUG
> otopi.plugins.otopi.packagers.yumpackager yumpackager._boot:184 Cannot
> initialize miniyum
> Traceback (most recent call last):
>   File 
> "/home/herabus/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py",
> line 176, in _boot
> self._refreshMiniyum()
>   File 
> "/home/herabus/otopi/src/bin/../plugins/otopi/packagers/yumpackager.py",
> line 134, in _refreshMiniyum
> constants.PackEnv.YUM_ENABLED

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

[Luca 'remix_tj' Lorenzetto]

Hello Matthias,

as far as i know oVirt Node wants to download updates trough yum, like
standard RHEL/CentOS. So internet connection is required. If you don't
want to provide internet access to the nodes, i suggest you to mirror
the repository on a local machine.

Luca

On Mon, May 15, 2017 at 9:52 AM, Matthias Leopold
 wrote:
> hi,
>
> do hypervisors, that are running oVirt Node (not standard CentOS/RHEL), need
> internet access for updates or can they be in a private, non routed network
> (and updates happen via engine)? it seems the latter is the case, but i want
> to be sure
>
> thx
> matthias
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)

"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)

Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Internet access for oVirt Nodes?

[Matthias Leopold]

hi,

do hypervisors, that are running oVirt Node (not standard CentOS/RHEL), 
need internet access for updates or can they be in a private, non routed 
network (and updates happen via engine)? it seems the latter is the 
case, but i want to be sure


thx
matthias

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

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

[Eduardo Mayoral]

As a user I must say this is a very welcome feature. I appreciate a lot
that oVirt already makes it very easy to import VMs from VMWare .

Allowing to export oVirt machines in OVA format, which as of today is
the "lingua franca" of VM migrations offers a nice and clear path out of
oVirt. Having an easy way to migrate out of oVirt makes me MORE likely
to keep on using oVirt, not less.

Eduardo Mayoral Jimeno (emayo...@arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153

On 14/05/17 15:56, 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

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

Re: [ovirt-users] ovirt 4.1: migrate vm to node 2 results in lost connectivity

[Sandro Bonazzola]

On Mon, May 15, 2017 at 9:33 AM, yayo (j)  wrote:

>
> 2017-05-11 17:08 GMT+02:00 Sandro Bonazzola :
>
>> Can you be a bit more specific? Is it a Hosted Engine deployment?
>> Hyperconverged? Using oVirt Node for nodes?
>>
>
> Hi and sorry for delay, It's an hosted engine deployment Hyperconverged
> with gluster 2 node + 1 arbiter ... We have used the official repository
> for ovirt on centos 7 ... Is this answering to your question about node ?
>

Thanks, I added some people who may help with this issue.



>
> Thank you
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA 

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

Re: [ovirt-users] ovirt 4.1: migrate vm to node 2 results in lost connectivity

[yayo (j)]

2017-05-11 17:08 GMT+02:00 Sandro Bonazzola :

> Can you be a bit more specific? Is it a Hosted Engine deployment?
> Hyperconverged? Using oVirt Node for nodes?
>

Hi and sorry for delay, It's an hosted engine deployment Hyperconverged
with gluster 2 node + 1 arbiter ... We have used the official repository
for ovirt on centos 7 ... Is this answering to your question about node ?

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

Re: [ovirt-users] Docker images for oVirt engine

[Juan Hernández]

On 05/15/2017 05:24 AM, Leni Kadali Mutungi wrote:
> Managed to run the OpenShift cluster well enough. When I went into the
> ovirt-containers directory and tried to run `make build`, I got the
> following error:
> 
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/home/herabus/ovirt-containers/tools"" go get ${godep}; \
> done
> /bin/sh: 2: go: Permission denied
> Makefile:40: recipe for target 'tools/bin/build' failed
> make: *** [tools/bin/build] Error 127
> 
> So I ran `sudo make build` instead and got the following error:
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/tools"" go get ${godep}; \
> done
> /bin/sh: 2: go: not found
> Makefile:40: recipe for target 'tools/bin/build' failed
> make: *** [tools/bin/build] Error 127
> 
> Running `sudo make deploy` gave me this error:
> 
> for godep in gopkg.in/ini.v1 ; do \
> GOPATH=""/tools"" go get ${godep}; \
> done
> /bin/sh: 2: go: not found
> Makefile:40: recipe for target 'tools/bin/deploy' failed
> make: *** [tools/bin/deploy] Error 127
> 

The tool that builds and deploy the containers to the OpenShift cluster
is a program written in Go. It is compiled when you run 'make ...'. That
means that you need to have the go development environment installed.
For example, in CentOS or Fedora:

  yum -y install golang

Once you have it installed, try again 'make build' and 'make deploy'.

I'll try to update the documentation to explain that.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] can i Extend volume from replica 2 to replica 3 with arbiter

[Ravishankar N]

-- Forwarded message --
From: *Khalid Jamal* >

Date: Sat, May 13, 2017 at 10:51 PM
Subject: [ovirt-users] can i Extend volume from replica 2 to replica 3 
with arbiter

To: users@ovirt.org 


Dear Team

i need you advice for convert our volume replica 2 to replica 3 with 
arbiter but important thing it's production environments , i try to 
convert the same name of volume in replica 2 to convert is to the 
replica 3 to avoid losing vm's or any data that's what i do it :



# gluster volume create gfs1 replica 3 arbiter 1 s1:/export/sdb1/br1 
s2:/export/sdb1/br1 s3:/export/sdb1/br1 s1:/export/sdc1/br1 
s2:/export/sdc1/br1 s3:/export/sdc1/br1 s4:/export/sdb1/br1 
s5:/export/sdb1/br1 s6:/export/sdb1/br1 s4:/export/sdc1/br1 
s5:/export/sdc1/br1 s6:/export/sdc1/br1


that's the result :


volume create: gfs1: failed: Volume gfs1 already exists


If you are converting an existing replica 2 to arbiter, you would need 
to use the `add-brick` command. The syntax is given here: 
https://review.gluster.org/#/c/14126/8//COMMIT_MSG

Hope that helps,
Ravi


i try to change the name but without any success what shall i do.


best regards



Eng khalid jamal
System Admin@IT Department
Earthlink Telecom

Email: khalid.ja...@earthlinktele.com 


No: 3355
skype: engkhalid21986
NO : 07704268321


___
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