Re: [ovirt-users] web 404 after reinstall ovirt-engine

2018-01-18 Thread Martin Perina
Hi,

could you please share with us complete engine logs from
/var/log/ovirt-engine and subdirectories?

Thanks

Martin


On Fri, Jan 19, 2018 at 8:35 AM, Arman Khalatyan  wrote:

> looks like your database is not running
> what about if you re-run the engine-setup??
>
>
> Am 19.01.2018 7:11 vorm. schrieb "董青龙" :
>
>> Hi, all
>> I installed ovirt-engine 4.1.8.2 for the second time and I got
>> "successful" after I excuted "engine-setup". But I got "404" when I tried
>> to access webadmin portal using "https://FQDN/ovirt-engine;. By the way,
>> I could access the web after I installed ovirt-engine for the first time.
>> Then I excuted "engine-cleanup" and "yum remove ovirt-engine" and installed
>> ovirt-engine for the second time. I also tried to remove ovirt-engine-dwh
>> and postgresql but after I reinstalled ovirt-engine I still got "404".
>> Can I fix this problem? Hope some can help, thanks!
>> Here are some logs in "/var/log/ovirt-engine/engine.log":
>> ...
>> 2018-01-19 12:56:06,288+08 ERROR [org.ovirt.engine.ui.frontend.
>> server.dashboard.DashboardDataServlet] (ServerService Thread Pool -- 61)
>> [] Could not access engine's DWH configuration table:
>> java.sql.SQLException: javax.resource.ResourceException: IJ000453:
>> Unable to get managed connection for java:/ENGINEDataSource
>> ...
>> Caused by: javax.resource.ResourceException: IJ000453: Unable to get
>> managed connection for java:/ENGINEDataSource
>> ...
>> Caused by: javax.resource.ResourceException: IJ031084: Unable to create
>> connection
>> ...
>> Caused by: org.postgresql.util.PSQLException: FATAL: password
>> authentication failed for user "engine"
>> ...
>> 2018-01-19 12:56:06,292+08 WARN  [org.ovirt.engine.ui.frontend
>> .server.dashboard.DashboardDataServlet] (ServerService Thread Pool --
>> 61) [] No valid DWH configurations were found, assuming DWH database isn't
>> setup.
>> 2018-01-19 12:56:06,292+08 INFO  [org.ovirt.engine.ui.frontend
>> .server.dashboard.DashboardDataServlet] (ServerService Thread Pool --
>> 61) [] Dashboard DB query cache has been disabled.
>>
>>
>>
>>
>> ___
>> 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
>
>


-- 
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] web 404 after reinstall ovirt-engine

2018-01-18 Thread Arman Khalatyan
looks like your database is not running
what about if you re-run the engine-setup??


Am 19.01.2018 7:11 vorm. schrieb "董青龙" :

> Hi, all
> I installed ovirt-engine 4.1.8.2 for the second time and I got
> "successful" after I excuted "engine-setup". But I got "404" when I tried
> to access webadmin portal using "https://FQDN/ovirt-engine;. By the way,
> I could access the web after I installed ovirt-engine for the first time.
> Then I excuted "engine-cleanup" and "yum remove ovirt-engine" and installed
> ovirt-engine for the second time. I also tried to remove ovirt-engine-dwh
> and postgresql but after I reinstalled ovirt-engine I still got "404".
> Can I fix this problem? Hope some can help, thanks!
> Here are some logs in "/var/log/ovirt-engine/engine.log":
> ...
> 2018-01-19 12:56:06,288+08 ERROR [org.ovirt.engine.ui.frontend.
> server.dashboard.DashboardDataServlet] (ServerService Thread Pool -- 61)
> [] Could not access engine's DWH configuration table:
> java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable
> to get managed connection for java:/ENGINEDataSource
> ...
> Caused by: javax.resource.ResourceException: IJ000453: Unable to get
> managed connection for java:/ENGINEDataSource
> ...
> Caused by: javax.resource.ResourceException: IJ031084: Unable to create
> connection
> ...
> Caused by: org.postgresql.util.PSQLException: FATAL: password
> authentication failed for user "engine"
> ...
> 2018-01-19 12:56:06,292+08 WARN  [org.ovirt.engine.ui.
> frontend.server.dashboard.DashboardDataServlet] (ServerService Thread
> Pool -- 61) [] No valid DWH configurations were found, assuming DWH
> database isn't setup.
> 2018-01-19 12:56:06,292+08 INFO  [org.ovirt.engine.ui.
> frontend.server.dashboard.DashboardDataServlet] (ServerService Thread
> Pool -- 61) [] Dashboard DB query cache has been disabled.
>
>
>
>
> ___
> 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] web 404 after reinstall ovirt-engine

2018-01-18 Thread 董青龙
Hi, all
I installed ovirt-engine 4.1.8.2 for the second time and I got 
"successful" after I excuted "engine-setup". But I got "404" when I tried to 
access webadmin portal using "https://FQDN/ovirt-engine;. By the way, I could 
access the web after I installed ovirt-engine for the first time. Then I 
excuted "engine-cleanup" and "yum remove ovirt-engine" and installed 
ovirt-engine for the second time. I also tried to remove ovirt-engine-dwh and 
postgresql but after I reinstalled ovirt-engine I still got "404".
Can I fix this problem? Hope some can help, thanks!
Here are some logs in "/var/log/ovirt-engine/engine.log":
...
2018-01-19 12:56:06,288+08 ERROR 
[org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet] 
(ServerService Thread Pool -- 61) [] Could not access engine's DWH 
configuration table: java.sql.SQLException: javax.resource.ResourceException: 
IJ000453: Unable to get managed connection for java:/ENGINEDataSource
...
Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed 
connection for java:/ENGINEDataSource
...
Caused by: javax.resource.ResourceException: IJ031084: Unable to create 
connection
...
Caused by: org.postgresql.util.PSQLException: FATAL: password authentication 
failed for user "engine"
...
2018-01-19 12:56:06,292+08 WARN  
[org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet] 
(ServerService Thread Pool -- 61) [] No valid DWH configurations were found, 
assuming DWH database isn't setup.
2018-01-19 12:56:06,292+08 INFO  
[org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet] 
(ServerService Thread Pool -- 61) [] Dashboard DB query cache has been disabled.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] The future of backups in oVirt 4.2+

2018-01-18 Thread Zip

On Jan 18, 2018 5:29 PM, "Jayme"  wrote:
> I'm still deciding on storage solutions and have not made up my mind yet.
> GlusterFS may be an option but I'm not sure about performance and maintenance.
> It sounds to me like GlusterFS with secondary replicated gluster volume would
> work quite well as a disaster recovery solution but I'd also need
> historical/incremental backups as well, either of the VMs or at the very least
> some important files within such as production DBs etc, which may be possible
> with a secondary backup method using rsync or something along those lines.

-Gluster has a geo-replication based backup which is very cool and
integrated to oVirt UI.

> 
> It seems to me that there is not a great backup solution for oVirt yet which I
> find hard to believe.  I don't understand why backing up oVirt VMs has to be
> so complicated, compared to other products.  I was hoping that 4.2 would
> change that and allow for easier more resource efficient backing solutions.

-It certainly does. See the DR work (and youtube video).
-Y. 


** I have yet to see a working script that does a VM backup from oVirt 4.2
to NFS storage?? I have spent days testing and trying all the scripts I can
find, most are old and all seem to fail in different ways. I have even coded
my own script using bash/curl/RestAPI and hit a dead end there as well with
not finding any docs on how to backup an inactive disk from a attached
snapshot. You¹d think oVirt would have something better for a DR solution or
at least make it so you dont have to become an oVirt Dev Contributor to be
able to backup your Vms? **

I would love to see a clear example of how to do VM backups from the command
line in a script so I can move on to rolling out oVirt 4.2 ;)

Zip

> 
> On Thu, Jan 18, 2018 at 11:08 AM, Dan Yasny  wrote:
>> If you are using NFS, you might find it easier and more efficient to use a
>> solution outside oVirt.
>> 
>> I've documented an initial attempt at backing up machine images with backy2
>> at 
>> https://dyasny.blogspot.ca/2017/06/exploring-backup-options-for-rhvovirt.html
>> 
>> It is harder to do with block storage and frankly I haven't had the time to
>> get to doing it there, but NFS is simple enough, and what you get is pretty
>> robust, deduplicated backup, in some ways similar to the typical VM backups
>> you get from Veeam and Altaro on other platforms (sans the GUI of course).
>> 
>> 
>> 
>> On Thu, Jan 18, 2018 at 9:59 AM, Jayme  wrote:
>>> I've been running a non-production oVirt setup for a while and plan on
>>> building a more robust oVirt setup for eventual production use.  Part of
>>> that planning of course is backup/disaster recovery options.
>>> 
>>> I've been playing around with a few options to backup oVirt, I'm sure most
>>> of you are aware of them.  The github webfix it python scripts, and starting
>>> to look at bacchus as well although have not set it up or tested bacchus
>>> yet. 
>>> 
>>> The webfix it python script is fairly simple to setup and seems to work ok
>>> as intended, even on 4.2, but it's definitely clunky in terms of having to
>>> snapshot, clone, export.  A lot of resource usage.  I assume bacchus most
>>> likely uses the same method of snapshot/clone/export as well (due to what
>>> was available in oVirt at the time these scripts were written).
>>> 
>>> My concerns with using something like these are:
>>> 
>>> 1. It's using old 3x api -- which is fine for now but probably not with
>>> oVirt 4.3
>>> 2. Inefficient / resource intensive
>>> 3. Using export domain which is depreciated
>>> 
>>> From what I've read in oVirt documentation the Export domain is depreciated.
>>> I assume that this means that instead of a export domain you could instead
>>> create a regular data domain for backups that can be detached and attached
>>> to another environment, is that the correct assumption?
>>> 
>>> I've also read that it might be possible to skip the cloning of the VM part
>>> and export snapshots directly.  Is this now possible in 4.2 or will be in
>>> the future?  if it is possible to perform VM backups without cloning to a
>>> new VM first is anyone aware of any scripts/software that is available now
>>> which takes advantage of that?
>>> 
>>> Essentially all I want is a simple solution to backup my VMs to separate NFS
>>> storage.  If for some reason my main storage crashes I then have the option
>>> to connect that backup NFS storage to a secondary stand alone oVirt instance
>>> and run my VMs from there until the primary oVirt instance is repaired.
>>> What I want to avoid is implementing an older more inefficient solution that
>>> might work for a while but will eventually no longer work due to ovIrt
>>> updates in the future.
>>> 
>>> I know options like active-active failover and georeplication exist but that
>>> may be too complex for my needs although I would be interested in hearing
>>> about how some of you may be 

Re: [ovirt-users] oVirt home lab hardware

2018-01-18 Thread Jamie Lawrence

I'm a bit out of date on the topic, but unless they have changed, avoid the 
NUCs. I bought a couple but gave up on them because of a firmware bug (? 
limitation, at least) that Intel said it won't fix. It causes a lockup on boot 
if a monitor is not connected. I've been told that different models don't have 
that problem, but have also heard of other weird problems. The impression I got 
is that they were meant for being media servers stuck to the back of TVs, and 
other use cases tend to be precluded by unexpected limitations, bugs and 
general strange behavior. Perhaps this was fixed, but I ended up with a bad 
taste in my mouth.

You can pick up dirt-cheap rackmount kit on Ebay. A few R710s or similar can be 
had for a few $hundred and would be absolutely lovely overkill for a home 
network. The downside of this approach at home is going to be power consumption 
and noise, depending on local energy costs and the nature of your dwelling. 
Also, some people may not be that fond of the datacenter look for home decor.

Unless you live in a cheap energy locale/don't pay for your power/enjoy 
malformed space heaters, don't underestimate the cost of running server kit. 
Getting rid of rack mount machines and switches and moving everything to a 
couple machines built with energy consumption in mind cut my electricity costs 
by over half.

-j


> On Jan 18, 2018, at 12:52 PM, Abdurrahman A. Ibrahim 
>  wrote:
> 
> Hello,
> 
> I am planning to buy home lab hardware to be used by oVirt.
> 
> Any recommendations for used hardware i can buy from eBay for example? 
> Also, have you tried oVirt on Intel NUC or any other SMB servers before? 

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


[ovirt-users] Zombie kworker process on node took 100% CPU load

2018-01-18 Thread Andrei V
Hi,

I've got strange problem with oVirt Node 4.2 installed on CentOS 7 with
mainline 4.14 kernel & HP ProLiant ML350.

Kworker process loaded 1 cpu CPU core at 100%, and since it didn't
finish even after several hours, it was clearly a zombie.
I logged into each VM, and powered them off with "shutdown now". From
SPICE console it was seen VMs halted.

However, in oVirt engine web they have been marked with tripple green
down arrow. An attempt to shutdown them completely with oVirt button
resulted in error message something like "Can't shutdown VM because
highly available and can't be moved". Sorry, I forgot to take screenshot.
Its was also impossible to shutdown the node correctly, process freezes.
After restart, everything seem to work correctly.

Anyone have any idea how to cope with this kind of problem?

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


Re: [ovirt-users] oVirt home lab hardware

2018-01-18 Thread Jayme
For rackmount Dell R710's are fairly popular for home labs, they have good
specs and can be found at reasonable prices on ebay.

On Thu, Jan 18, 2018 at 4:52 PM, Abdurrahman A. Ibrahim <
a.rahman.at...@gmail.com> wrote:

> Hello,
>
> I am planning to buy home lab hardware to be used by oVirt.
>
> Any recommendations for used hardware i can buy from eBay for example?
> Also, have you tried oVirt on Intel NUC or any other SMB servers before?
>
> Thanks,
> Ab
>
> ___
> 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] oVirt home lab hardware

2018-01-18 Thread Abdurrahman A. Ibrahim
Hello,

I am planning to buy home lab hardware to be used by oVirt.

Any recommendations for used hardware i can buy from eBay for example?
Also, have you tried oVirt on Intel NUC or any other SMB servers before?

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


Re: [ovirt-users] docker, kubernetes and ovirt

2018-01-18 Thread Roy Golan
On Thu, 18 Jan 2018 at 19:02 Nathanaël Blanchet  wrote:

> And without the kubernetes ui plugin, how can I achieve to use the ovirt
> cloud provider described on the official kubernetes site :
> https://kubernetes.io/docs/getting-started-guides/ovirt/ ?
>
>
I am working currently on updating the ovirt cloudprovider for
kubernetes[1]. The effort is
to create an out-of-tree plugin but I'll push the code into kubernetes so
the internal cloudprovider will work with modern version of ovirt.
Note: this is a work in progress.

Regarding the UI plugin, what exactly do you need? (I remember vaugly that
the old plugin kind of showed a layout of the nodes?)

[1] https://github.com/rgolangh/ovirt-k8s-cloudprovider


>
> Le 18/01/2018 à 17:55, Nathanaël Blanchet a écrit :
> > Hi all,
> >
> > Regarding to this video : https://www.youtube.com/watch?v=JyyST4ZKne8
> > and ovedou.blogspot.fr/2014/03/running-docker-container-in-ovirt.html,
> > it appears that some stuff has been done in integrated docker into ovirt.
> >
> > I'm interested into these two UI plugins : docker-resources (I found
> > it in samples-uiplugins) and the kubernetes one that I didn't find
> > anywhere.
> >
> > Can anyone tell me if the development of that projects are
> > definitively stopped and the reason why?
> >
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
>
> ___
> 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 Node 4.1.8 -> 4.2 upgrade

2018-01-18 Thread Luca 'remix_tj' Lorenzetto
Hi Yuval,

interesting, thank you!

Luca

On Thu, Jan 18, 2018 at 1:26 PM, Yuval Turgeman  wrote:
> Hi Luca,
>
> We updated the FAQ [1] with a small script to help upgrade between major
> releases.
>
> [1] https://www.ovirt.org/node/faq/
>
> On Mon, Jan 15, 2018 at 10:21 AM, Luca 'remix_tj' Lorenzetto
>  wrote:
>>
>>
>>
>> On Thu, Jan 11, 2018 at 2:31 PM, Ryan Barry  wrote:
>>>
>>> Note that, in the case of Node, the ovirt-release RPM should not be
>>> installed. Mostly because it automatically enables a number of per-package
>>> updates (such as vdsm) instead of installing a single image.
>>>
>>> Trimming the repo files so they look like what is shipped in Node
>>> (IgnorePkgs and OnlyPkgs) will pull ovirt-node-ng-image-update.rpm, which is
>>> the only package needing an update.
>>>
>>
>> Hi,
>>
>> i'm upgrading ovirt-node too. I found out that installing ovirt-release
>> file and running yum upgrade wants to upgrade everything. Instead, if i make
>>
>> yum upgrade ovirt-node-ng-image*
>>
>> I get the new image downloaded.
>>
>> So which is the right procedure to upgrade a node? Maybe providing a
>> single command alternative to yum (let's say ovirt-node-upgrade) for
>> upgrading would be better and avoid issues when doing such operation.
>>
>> Luca
>>
>> --
>> "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
>>
>



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


Re: [ovirt-users] hosted-engine unknow stale-data

2018-01-18 Thread Artem Tambovskiy
Hi,

Ok, i decided to remove second host from the cluster.
I reinstalled from webUI it with hosted-engine action UNDEPLOY, and removed
it from the cluster aftewards.
All VM's are fine hosted engine running ok,
But hosted-engine --vm-status still showing 2 hosts.

How I can clean the traces of second host in a correct way?


--== Host 1 status ==--

conf_on_shared_storage : True
Status up-to-date  : True
Hostname   : ovirt1.telia.ru
Host ID: 1
Engine status  : {"health": "good", "vm": "up",
"detail": "up"}
Score  : 3400
stopped: False
Local maintenance  : False
crc32  : 1b1b6f6d
local_conf_timestamp   : 545385
Host timestamp : 545385
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=545385 (Thu Jan 18 21:34:25 2018)
host-id=1
score=3400
vm_conf_refresh_time=545385 (Thu Jan 18 21:34:25 2018)
conf_on_shared_storage=True
maintenance=False
state=GlobalMaintenance
stopped=False


--== Host 2 status ==--

conf_on_shared_storage : True
Status up-to-date  : False
Hostname   : ovirt1.telia.ru
Host ID: 2
Engine status  : unknown stale-data
Score  : 0
stopped: True
Local maintenance  : False
crc32  : c7037c03
local_conf_timestamp   : 7530
Host timestamp : 7530
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=7530 (Fri Jan 12 16:10:12 2018)
host-id=2
score=0
vm_conf_refresh_time=7530 (Fri Jan 12 16:10:12 2018)
conf_on_shared_storage=True
maintenance=False
state=AgentStopped
stopped=True


!! Cluster is in GLOBAL MAINTENANCE mode !!

Thank you in advance!
Regards,
Artem


On Wed, Jan 17, 2018 at 6:47 PM, Artem Tambovskiy <
artem.tambovs...@gmail.com> wrote:

> Hello,
>
> Any further suggestions on how to fix the issue and make HA setup working?
> Can the complete removal of second host (with complete removal ovirt
> configuration files and packages) from cluster and adding it again solve
> the issue? Or it might completly ruin the cluster?
>
> Regards,
> Artem
>
> 16 янв. 2018 г. 17:00 пользователь "Artem Tambovskiy" <
> artem.tambovs...@gmail.com> написал:
>
> Hi Martin,
>>
>> Thanks for feedback.
>>
>> All hosts and hosted-engine running 4.1.8 release.
>> The strange thing : I can see that host ID is set to 1 on both hosts at
>> /etc/ovirt-hosted-engine/hosted-engine.conf file.
>> I have no idea how this happen, the only thing I have changed recently is
>> that I have changed mnt_options in order to add backup-volfile-servers
>> by using hosted-engine --set-shared-config command
>>
>> Both agent and broker are running on second host
>>
>> [root@ovirt2 ovirt-hosted-engine-ha]# ps -ef | grep ovirt-ha-
>> vdsm  42331  1 26 14:40 ?00:31:35 /usr/bin/python
>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker --no-daemon
>> vdsm  42332  1  0 14:40 ?00:00:16 /usr/bin/python
>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent --no-daemon
>>
>> but I saw some tracebacks during the broker start
>>
>> [root@ovirt2 ovirt-hosted-engine-ha]# systemctl status ovirt-ha-broker -l
>> ● ovirt-ha-broker.service - oVirt Hosted Engine High Availability
>> Communications Broker
>>Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service;
>> enabled; vendor preset: disabled)
>>Active: active (running) since Tue 2018-01-16 14:40:15 MSK; 1h 58min
>> ago
>>  Main PID: 42331 (ovirt-ha-broker)
>>CGroup: /system.slice/ovirt-ha-broker.service
>>└─42331 /usr/bin/python 
>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker
>> --no-daemon
>>
>> Jan 16 14:40:15 ovirt2.telia.ru systemd[1]: Started oVirt Hosted Engine
>> High Availability Communications Broker.
>> Jan 16 14:40:15 ovirt2.telia.ru systemd[1]: Starting oVirt Hosted Engine
>> High Availability Communications Broker...
>> Jan 16 14:40:16 ovirt2.telia.ru ovirt-ha-broker[42331]: ovirt-ha-broker
>> ovirt_hosted_engine_ha.broker.listener.ConnectionHandler ERROR Error
>> handling request, data: 'set-storage-domain FilesystemBackend
>> dom_type=glusterfs sd_uuid=4a7f8717-9bb0-4d80-8016-498fa4b88162'
>> Traceback (most
>> recent call last):
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",
>> line 166, in handle
>> 

Re: [ovirt-users] docker, kubernetes and ovirt

2018-01-18 Thread Erekle Magradze

Hi,
Look in OpenShift Origin

Cheers

Erekle


On 01/18/2018 05:57 PM, Nathanaël Blanchet wrote:
And without the kubernetes ui plugin, how can I achieve to use the 
ovirt cloud provider described on the official kubernetes site : 
https://kubernetes.io/docs/getting-started-guides/ovirt/ ?



Le 18/01/2018 à 17:55, Nathanaël Blanchet a écrit :

Hi all,

Regarding to this video : https://www.youtube.com/watch?v=JyyST4ZKne8 
and 
ovedou.blogspot.fr/2014/03/running-docker-container-in-ovirt.html, it 
appears that some stuff has been done in integrated docker into ovirt.


I'm interested into these two UI plugins : docker-resources (I found 
it in samples-uiplugins) and the kubernetes one that I didn't find 
anywhere.


Can anyone tell me if the development of that projects are 
definitively stopped and the reason why?






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


Re: [ovirt-users] docker, kubernetes and ovirt

2018-01-18 Thread Nathanaël Blanchet
And without the kubernetes ui plugin, how can I achieve to use the ovirt 
cloud provider described on the official kubernetes site : 
https://kubernetes.io/docs/getting-started-guides/ovirt/ ?



Le 18/01/2018 à 17:55, Nathanaël Blanchet a écrit :

Hi all,

Regarding to this video : https://www.youtube.com/watch?v=JyyST4ZKne8 
and ovedou.blogspot.fr/2014/03/running-docker-container-in-ovirt.html, 
it appears that some stuff has been done in integrated docker into ovirt.


I'm interested into these two UI plugins : docker-resources (I found 
it in samples-uiplugins) and the kubernetes one that I didn't find 
anywhere.


Can anyone tell me if the development of that projects are 
definitively stopped and the reason why?




--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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


[ovirt-users] docker, kubernetes and ovirt

2018-01-18 Thread Nathanaël Blanchet

Hi all,

Regarding to this video : https://www.youtube.com/watch?v=JyyST4ZKne8 
and ovedou.blogspot.fr/2014/03/running-docker-container-in-ovirt.html, 
it appears that some stuff has been done in integrated docker into ovirt.


I'm interested into these two UI plugins : docker-resources (I found it 
in samples-uiplugins) and the kubernetes one that I didn't find anywhere.


Can anyone tell me if the development of that projects are definitively 
stopped and the reason why?


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

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


Re: [ovirt-users] The future of backups in oVirt 4.2+

2018-01-18 Thread Yaniv Kaul
On Jan 18, 2018 5:29 PM, "Jayme"  wrote:

I'm still deciding on storage solutions and have not made up my mind yet.
GlusterFS may be an option but I'm not sure about performance and
maintenance.  It sounds to me like GlusterFS with secondary replicated
gluster volume would work quite well as a disaster recovery solution but
I'd also need historical/incremental backups as well, either of the VMs or
at the very least some important files within such as production DBs etc,
which may be possible with a secondary backup method using rsync or
something along those lines.


Gluster has a geo-replication based backup which is very cool and
integrated to oVirt UI.


It seems to me that there is not a great backup solution for oVirt yet
which I find hard to believe.  I don't understand why backing up oVirt VMs
has to be so complicated, compared to other products.  I was hoping that
4.2 would change that and allow for easier more resource efficient backing
solutions.


It certainly does. See the DR work (and youtube video).
Y.


On Thu, Jan 18, 2018 at 11:08 AM, Dan Yasny  wrote:

> If you are using NFS, you might find it easier and more efficient to use a
> solution outside oVirt.
>
> I've documented an initial attempt at backing up machine images with
> backy2 at https://dyasny.blogspot.ca/2017/06/exploring-backup-optio
> ns-for-rhvovirt.html
>
> It is harder to do with block storage and frankly I haven't had the time
> to get to doing it there, but NFS is simple enough, and what you get is
> pretty robust, deduplicated backup, in some ways similar to the typical VM
> backups you get from Veeam and Altaro on other platforms (sans the GUI of
> course).
>
>
>
> On Thu, Jan 18, 2018 at 9:59 AM, Jayme  wrote:
>
>> I've been running a non-production oVirt setup for a while and plan on
>> building a more robust oVirt setup for eventual production use.  Part of
>> that planning of course is backup/disaster recovery options.
>>
>> I've been playing around with a few options to backup oVirt, I'm sure
>> most of you are aware of them.  The github webfix it python scripts, and
>> starting to look at bacchus as well although have not set it up or tested
>> bacchus yet.
>>
>> The webfix it python script is fairly simple to setup and seems to work
>> ok as intended, even on 4.2, but it's definitely clunky in terms of having
>> to snapshot, clone, export.  A lot of resource usage.  I assume bacchus
>> most likely uses the same method of snapshot/clone/export as well (due to
>> what was available in oVirt at the time these scripts were written).
>>
>> My concerns with using something like these are:
>>
>> 1. It's using old 3x api -- which is fine for now but probably not with
>> oVirt 4.3
>> 2. Inefficient / resource intensive
>> 3. Using export domain which is depreciated
>>
>> From what I've read in oVirt documentation the Export domain is
>> depreciated.  I assume that this means that instead of a export domain you
>> could instead create a regular data domain for backups that can be detached
>> and attached to another environment, is that the correct assumption?
>>
>> I've also read that it might be possible to skip the cloning of the VM
>> part and export snapshots directly.  Is this now possible in 4.2 or will be
>> in the future?  if it is possible to perform VM backups without cloning to
>> a new VM first is anyone aware of any scripts/software that is available
>> now which takes advantage of that?
>>
>> Essentially all I want is a simple solution to backup my VMs to separate
>> NFS storage.  If for some reason my main storage crashes I then have the
>> option to connect that backup NFS storage to a secondary stand alone oVirt
>> instance and run my VMs from there until the primary oVirt instance is
>> repaired.   What I want to avoid is implementing an older more inefficient
>> solution that might work for a while but will eventually no longer work due
>> to ovIrt updates in the future.
>>
>> I know options like active-active failover and georeplication exist but
>> that may be too complex for my needs although I would be interested in
>> hearing about how some of you may be implementing these features.
>>
>> In summary, I'd trying to figure out what the best backup option may be
>> going forward with oVirt in the future so I can implement the best option
>> from the start rather than having to change it all around in the near
>> future.
>>
>> 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] The future of backups in oVirt 4.2+

2018-01-18 Thread Dan Yasny
On Thu, Jan 18, 2018 at 10:15 AM, Yaniv Kaul  wrote:

>
>
> On Thu, Jan 18, 2018 at 5:08 PM, Dan Yasny  wrote:
>
>> If you are using NFS, you might find it easier and more efficient to use
>> a solution outside oVirt.
>>
>
> But how do you maintain crash consistency? I suspect using oVirt helps, in
> the sense that it enables fsfreeze (VSS). Otherwise, there's a good chance
> of fsck...
> In theory, it can be extended for application-consistency as well[1].
> Y.
>
> [1] https://github.com/guillon/qemu-plugins/blob/
> master/scripts/qemu-guest-agent/fsfreeze-hook.d/mysql-flush.sh.sample
>
>
Indeed, to be a proper solution it requires some work, my old blogpost was
about the initial testing of an external backup solution, which can keep a
consistent set of deduplicated and ordered backups, quite easily restorable
to a PIT, just like you have with many of today's hyper-v and vmware
solutions. What it missing is crash consistency (an API call is required to
qemu-ga and other scripts), VM configuration data (OVF or DOMXML export of
the VM itself, not just the disks), snapshot chain preservation (not sure
it's much of a requirement in a backup solution).

The oVirt backup API is nice, but what it gives you in the end is a full VM
image, instead of incrementals, which is a huge waste of space, unless you
are using deduplicated storage, and those are too expensive to store data
at rest usually.

What I like about backy2 is the fact that it deduplicates on the fly,
without using anything too low level like ZFS, and you only store the
diffs. It also works at the block level, so LVM volumes and files on NFS
are treated the same. The extra features like bitrot prevention and NBD
aren't without use as well. I'm sure with some work it can be made to work.

I've also been looking into a very different approach, e.g. live-migrating
the VM memstate and disks into a backup image, with migration cancelled
when sync is achieved, but that required some serious support from the KVM
folks and I had no time besides a shallow dabble.


>
>> I've documented an initial attempt at backing up machine images with
>> backy2 at https://dyasny.blogspot.ca/2017/06/exploring-backup-optio
>> ns-for-rhvovirt.html
>>
>> It is harder to do with block storage and frankly I haven't had the time
>> to get to doing it there, but NFS is simple enough, and what you get is
>> pretty robust, deduplicated backup, in some ways similar to the typical VM
>> backups you get from Veeam and Altaro on other platforms (sans the GUI of
>> course).
>>
>>
>>
>> On Thu, Jan 18, 2018 at 9:59 AM, Jayme  wrote:
>>
>>> I've been running a non-production oVirt setup for a while and plan on
>>> building a more robust oVirt setup for eventual production use.  Part of
>>> that planning of course is backup/disaster recovery options.
>>>
>>> I've been playing around with a few options to backup oVirt, I'm sure
>>> most of you are aware of them.  The github webfix it python scripts, and
>>> starting to look at bacchus as well although have not set it up or tested
>>> bacchus yet.
>>>
>>> The webfix it python script is fairly simple to setup and seems to work
>>> ok as intended, even on 4.2, but it's definitely clunky in terms of having
>>> to snapshot, clone, export.  A lot of resource usage.  I assume bacchus
>>> most likely uses the same method of snapshot/clone/export as well (due to
>>> what was available in oVirt at the time these scripts were written).
>>>
>>> My concerns with using something like these are:
>>>
>>> 1. It's using old 3x api -- which is fine for now but probably not with
>>> oVirt 4.3
>>> 2. Inefficient / resource intensive
>>> 3. Using export domain which is depreciated
>>>
>>> From what I've read in oVirt documentation the Export domain is
>>> depreciated.  I assume that this means that instead of a export domain you
>>> could instead create a regular data domain for backups that can be detached
>>> and attached to another environment, is that the correct assumption?
>>>
>>> I've also read that it might be possible to skip the cloning of the VM
>>> part and export snapshots directly.  Is this now possible in 4.2 or will be
>>> in the future?  if it is possible to perform VM backups without cloning to
>>> a new VM first is anyone aware of any scripts/software that is available
>>> now which takes advantage of that?
>>>
>>> Essentially all I want is a simple solution to backup my VMs to separate
>>> NFS storage.  If for some reason my main storage crashes I then have the
>>> option to connect that backup NFS storage to a secondary stand alone oVirt
>>> instance and run my VMs from there until the primary oVirt instance is
>>> repaired.   What I want to avoid is implementing an older more inefficient
>>> solution that might work for a while but will eventually no longer work due
>>> to ovIrt updates in the future.
>>>
>>> I know options like active-active failover and georeplication exist but
>>> that 

Re: [ovirt-users] The future of backups in oVirt 4.2+

2018-01-18 Thread Jayme
I'm still deciding on storage solutions and have not made up my mind yet.
GlusterFS may be an option but I'm not sure about performance and
maintenance.  It sounds to me like GlusterFS with secondary replicated
gluster volume would work quite well as a disaster recovery solution but
I'd also need historical/incremental backups as well, either of the VMs or
at the very least some important files within such as production DBs etc,
which may be possible with a secondary backup method using rsync or
something along those lines.

It seems to me that there is not a great backup solution for oVirt yet
which I find hard to believe.  I don't understand why backing up oVirt VMs
has to be so complicated, compared to other products.  I was hoping that
4.2 would change that and allow for easier more resource efficient backing
solutions.

On Thu, Jan 18, 2018 at 11:08 AM, Dan Yasny  wrote:

> If you are using NFS, you might find it easier and more efficient to use a
> solution outside oVirt.
>
> I've documented an initial attempt at backing up machine images with
> backy2 at https://dyasny.blogspot.ca/2017/06/exploring-backup-
> options-for-rhvovirt.html
>
> It is harder to do with block storage and frankly I haven't had the time
> to get to doing it there, but NFS is simple enough, and what you get is
> pretty robust, deduplicated backup, in some ways similar to the typical VM
> backups you get from Veeam and Altaro on other platforms (sans the GUI of
> course).
>
>
>
> On Thu, Jan 18, 2018 at 9:59 AM, Jayme  wrote:
>
>> I've been running a non-production oVirt setup for a while and plan on
>> building a more robust oVirt setup for eventual production use.  Part of
>> that planning of course is backup/disaster recovery options.
>>
>> I've been playing around with a few options to backup oVirt, I'm sure
>> most of you are aware of them.  The github webfix it python scripts, and
>> starting to look at bacchus as well although have not set it up or tested
>> bacchus yet.
>>
>> The webfix it python script is fairly simple to setup and seems to work
>> ok as intended, even on 4.2, but it's definitely clunky in terms of having
>> to snapshot, clone, export.  A lot of resource usage.  I assume bacchus
>> most likely uses the same method of snapshot/clone/export as well (due to
>> what was available in oVirt at the time these scripts were written).
>>
>> My concerns with using something like these are:
>>
>> 1. It's using old 3x api -- which is fine for now but probably not with
>> oVirt 4.3
>> 2. Inefficient / resource intensive
>> 3. Using export domain which is depreciated
>>
>> From what I've read in oVirt documentation the Export domain is
>> depreciated.  I assume that this means that instead of a export domain you
>> could instead create a regular data domain for backups that can be detached
>> and attached to another environment, is that the correct assumption?
>>
>> I've also read that it might be possible to skip the cloning of the VM
>> part and export snapshots directly.  Is this now possible in 4.2 or will be
>> in the future?  if it is possible to perform VM backups without cloning to
>> a new VM first is anyone aware of any scripts/software that is available
>> now which takes advantage of that?
>>
>> Essentially all I want is a simple solution to backup my VMs to separate
>> NFS storage.  If for some reason my main storage crashes I then have the
>> option to connect that backup NFS storage to a secondary stand alone oVirt
>> instance and run my VMs from there until the primary oVirt instance is
>> repaired.   What I want to avoid is implementing an older more inefficient
>> solution that might work for a while but will eventually no longer work due
>> to ovIrt updates in the future.
>>
>> I know options like active-active failover and georeplication exist but
>> that may be too complex for my needs although I would be interested in
>> hearing about how some of you may be implementing these features.
>>
>> In summary, I'd trying to figure out what the best backup option may be
>> going forward with oVirt in the future so I can implement the best option
>> from the start rather than having to change it all around in the near
>> future.
>>
>> 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] The future of backups in oVirt 4.2+

2018-01-18 Thread Yaniv Kaul
On Thu, Jan 18, 2018 at 5:08 PM, Dan Yasny  wrote:

> If you are using NFS, you might find it easier and more efficient to use a
> solution outside oVirt.
>

But how do you maintain crash consistency? I suspect using oVirt helps, in
the sense that it enables fsfreeze (VSS). Otherwise, there's a good chance
of fsck...
In theory, it can be extended for application-consistency as well[1].
Y.

[1]
https://github.com/guillon/qemu-plugins/blob/master/scripts/qemu-guest-agent/fsfreeze-hook.d/mysql-flush.sh.sample


> I've documented an initial attempt at backing up machine images with
> backy2 at https://dyasny.blogspot.ca/2017/06/exploring-backup-
> options-for-rhvovirt.html
>
> It is harder to do with block storage and frankly I haven't had the time
> to get to doing it there, but NFS is simple enough, and what you get is
> pretty robust, deduplicated backup, in some ways similar to the typical VM
> backups you get from Veeam and Altaro on other platforms (sans the GUI of
> course).
>
>
>
> On Thu, Jan 18, 2018 at 9:59 AM, Jayme  wrote:
>
>> I've been running a non-production oVirt setup for a while and plan on
>> building a more robust oVirt setup for eventual production use.  Part of
>> that planning of course is backup/disaster recovery options.
>>
>> I've been playing around with a few options to backup oVirt, I'm sure
>> most of you are aware of them.  The github webfix it python scripts, and
>> starting to look at bacchus as well although have not set it up or tested
>> bacchus yet.
>>
>> The webfix it python script is fairly simple to setup and seems to work
>> ok as intended, even on 4.2, but it's definitely clunky in terms of having
>> to snapshot, clone, export.  A lot of resource usage.  I assume bacchus
>> most likely uses the same method of snapshot/clone/export as well (due to
>> what was available in oVirt at the time these scripts were written).
>>
>> My concerns with using something like these are:
>>
>> 1. It's using old 3x api -- which is fine for now but probably not with
>> oVirt 4.3
>> 2. Inefficient / resource intensive
>> 3. Using export domain which is depreciated
>>
>> From what I've read in oVirt documentation the Export domain is
>> depreciated.  I assume that this means that instead of a export domain you
>> could instead create a regular data domain for backups that can be detached
>> and attached to another environment, is that the correct assumption?
>>
>> I've also read that it might be possible to skip the cloning of the VM
>> part and export snapshots directly.  Is this now possible in 4.2 or will be
>> in the future?  if it is possible to perform VM backups without cloning to
>> a new VM first is anyone aware of any scripts/software that is available
>> now which takes advantage of that?
>>
>> Essentially all I want is a simple solution to backup my VMs to separate
>> NFS storage.  If for some reason my main storage crashes I then have the
>> option to connect that backup NFS storage to a secondary stand alone oVirt
>> instance and run my VMs from there until the primary oVirt instance is
>> repaired.   What I want to avoid is implementing an older more inefficient
>> solution that might work for a while but will eventually no longer work due
>> to ovIrt updates in the future.
>>
>> I know options like active-active failover and georeplication exist but
>> that may be too complex for my needs although I would be interested in
>> hearing about how some of you may be implementing these features.
>>
>> In summary, I'd trying to figure out what the best backup option may be
>> going forward with oVirt in the future so I can implement the best option
>> from the start rather than having to change it all around in the near
>> future.
>>
>> 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] The future of backups in oVirt 4.2+

2018-01-18 Thread Dan Yasny
If you are using NFS, you might find it easier and more efficient to use a
solution outside oVirt.

I've documented an initial attempt at backing up machine images with backy2
at
https://dyasny.blogspot.ca/2017/06/exploring-backup-options-for-rhvovirt.html

It is harder to do with block storage and frankly I haven't had the time to
get to doing it there, but NFS is simple enough, and what you get is pretty
robust, deduplicated backup, in some ways similar to the typical VM backups
you get from Veeam and Altaro on other platforms (sans the GUI of course).



On Thu, Jan 18, 2018 at 9:59 AM, Jayme  wrote:

> I've been running a non-production oVirt setup for a while and plan on
> building a more robust oVirt setup for eventual production use.  Part of
> that planning of course is backup/disaster recovery options.
>
> I've been playing around with a few options to backup oVirt, I'm sure most
> of you are aware of them.  The github webfix it python scripts, and
> starting to look at bacchus as well although have not set it up or tested
> bacchus yet.
>
> The webfix it python script is fairly simple to setup and seems to work ok
> as intended, even on 4.2, but it's definitely clunky in terms of having to
> snapshot, clone, export.  A lot of resource usage.  I assume bacchus most
> likely uses the same method of snapshot/clone/export as well (due to what
> was available in oVirt at the time these scripts were written).
>
> My concerns with using something like these are:
>
> 1. It's using old 3x api -- which is fine for now but probably not with
> oVirt 4.3
> 2. Inefficient / resource intensive
> 3. Using export domain which is depreciated
>
> From what I've read in oVirt documentation the Export domain is
> depreciated.  I assume that this means that instead of a export domain you
> could instead create a regular data domain for backups that can be detached
> and attached to another environment, is that the correct assumption?
>
> I've also read that it might be possible to skip the cloning of the VM
> part and export snapshots directly.  Is this now possible in 4.2 or will be
> in the future?  if it is possible to perform VM backups without cloning to
> a new VM first is anyone aware of any scripts/software that is available
> now which takes advantage of that?
>
> Essentially all I want is a simple solution to backup my VMs to separate
> NFS storage.  If for some reason my main storage crashes I then have the
> option to connect that backup NFS storage to a secondary stand alone oVirt
> instance and run my VMs from there until the primary oVirt instance is
> repaired.   What I want to avoid is implementing an older more inefficient
> solution that might work for a while but will eventually no longer work due
> to ovIrt updates in the future.
>
> I know options like active-active failover and georeplication exist but
> that may be too complex for my needs although I would be interested in
> hearing about how some of you may be implementing these features.
>
> In summary, I'd trying to figure out what the best backup option may be
> going forward with oVirt in the future so I can implement the best option
> from the start rather than having to change it all around in the near
> future.
>
> 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


[ovirt-users] The future of backups in oVirt 4.2+

2018-01-18 Thread Jayme
I've been running a non-production oVirt setup for a while and plan on
building a more robust oVirt setup for eventual production use.  Part of
that planning of course is backup/disaster recovery options.

I've been playing around with a few options to backup oVirt, I'm sure most
of you are aware of them.  The github webfix it python scripts, and
starting to look at bacchus as well although have not set it up or tested
bacchus yet.

The webfix it python script is fairly simple to setup and seems to work ok
as intended, even on 4.2, but it's definitely clunky in terms of having to
snapshot, clone, export.  A lot of resource usage.  I assume bacchus most
likely uses the same method of snapshot/clone/export as well (due to what
was available in oVirt at the time these scripts were written).

My concerns with using something like these are:

1. It's using old 3x api -- which is fine for now but probably not with
oVirt 4.3
2. Inefficient / resource intensive
3. Using export domain which is depreciated

>From what I've read in oVirt documentation the Export domain is
depreciated.  I assume that this means that instead of a export domain you
could instead create a regular data domain for backups that can be detached
and attached to another environment, is that the correct assumption?

I've also read that it might be possible to skip the cloning of the VM part
and export snapshots directly.  Is this now possible in 4.2 or will be in
the future?  if it is possible to perform VM backups without cloning to a
new VM first is anyone aware of any scripts/software that is available now
which takes advantage of that?

Essentially all I want is a simple solution to backup my VMs to separate
NFS storage.  If for some reason my main storage crashes I then have the
option to connect that backup NFS storage to a secondary stand alone oVirt
instance and run my VMs from there until the primary oVirt instance is
repaired.   What I want to avoid is implementing an older more inefficient
solution that might work for a while but will eventually no longer work due
to ovIrt updates in the future.

I know options like active-active failover and georeplication exist but
that may be too complex for my needs although I would be interested in
hearing about how some of you may be implementing these features.

In summary, I'd trying to figure out what the best backup option may be
going forward with oVirt in the future so I can implement the best option
from the start rather than having to change it all around in the near
future.

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


Re: [ovirt-users] 4.1.8: Run Once does not allow me to choose a CD Image to attach

2018-01-18 Thread Alexander Wels
On Wednesday, January 17, 2018 4:20:24 PM EST Derek Atkins wrote:
> Hi,
> 
> On Wed, January 17, 2018 11:13 am, Pavel Novotny wrote:
> > On 16.1.2018 21:05, Derek Atkins wrote:
> >> Hi,
> >> 
> >> I upgraded from 4.0.6 to 4.1.8.  I had created a VM in 4.0.6 but had
> >> never started it nor had I ever run it before I upgraded.  I then
> >> upgraded to 4.1.8 (which went very smoothly), but then I tried to use
> >> the Run Once function to boot up and attach an ISO Image.  However when
> >> I select Run Once, then Boot Options, the "Attach CD" option is
> >> unchecked and wont let me select it like I could in 4.0.6.  If I try to
> >> select the checkbox I see the popup flash but the box remains unchecked.
> > 
> > Hi Derek,
> > 
> > this reminds me UX bug https://bugzilla.redhat.com/1516311
> > It has been filed for 4.2, but it affects also 4.1.x.
> > It happens when the browser window width is less than approx. 1200 px,
> > if it is your case.
> 
> Interesting.  Yes, xwininfo reports a geometry of 1105x883 for my browser
> window.
> 
> What an interesting bug.  Why would it assume it's a mobile view?  and
> even if it IS a mobile view, why disable the functionality?
> 
> At least the Edit dialog still works, but it's still annoying.
> 
> I've added myself to that bug.
> 
> Thanks,
> 
> > -Pavel
> 
> -derek
> 

Looked into it, have a patch pending. The good news is, its easy to work 
around by simply making your browser wider until it decides to change the 
layout. For some reason it decided the height of the container of the field 
was double what it was supposed to be and thus the field (in this case a drop 
down) was on top of the check box and eating the click.

> >> Is this a bug/regression in 4.1.8?
> >> 
> >> I did clear my browser cache thinking that might be it, but no, that
> >> didn't help.
> >> 
> >> The only thing I could do was Edit the VM, go to Boot options, select it
> >> there (which I could do) and then choose the ISO.  THEN I could run it
> >> with the CD attached.
> >> 
> >> Thanks,
> >> 
> >> -derek


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


Re: [ovirt-users] 4.1.8: Run Once does not allow me to choose a CD Image to attach

2018-01-18 Thread Alexander Wels
On Wednesday, January 17, 2018 4:20:24 PM EST Derek Atkins wrote:
> Hi,
> 
> On Wed, January 17, 2018 11:13 am, Pavel Novotny wrote:
> > On 16.1.2018 21:05, Derek Atkins wrote:
> >> Hi,
> >> 
> >> I upgraded from 4.0.6 to 4.1.8.  I had created a VM in 4.0.6 but had
> >> never started it nor had I ever run it before I upgraded.  I then
> >> upgraded to 4.1.8 (which went very smoothly), but then I tried to use
> >> the Run Once function to boot up and attach an ISO Image.  However when
> >> I select Run Once, then Boot Options, the "Attach CD" option is
> >> unchecked and wont let me select it like I could in 4.0.6.  If I try to
> >> select the checkbox I see the popup flash but the box remains unchecked.
> > 
> > Hi Derek,
> > 
> > this reminds me UX bug https://bugzilla.redhat.com/1516311
> > It has been filed for 4.2, but it affects also 4.1.x.
> > It happens when the browser window width is less than approx. 1200 px,
> > if it is your case.
> 
> Interesting.  Yes, xwininfo reports a geometry of 1105x883 for my browser
> window.
> 
> What an interesting bug.  Why would it assume it's a mobile view?  and
> even if it IS a mobile view, why disable the functionality?
> 
> At least the Edit dialog still works, but it's still annoying.
> 
> I've added myself to that bug.
> 
> Thanks,
> 
> > -Pavel
> 
> -derek
> 

The layout is adaptive, It has a large/medium/small/xs layout. Depending on 
the size of the screen it will it will take one of those layouts. I am 
guessing that is a medium layout. And looking at the bug it appears to have 
decided that the labels should be above the fields.

I am fairly certain there is no logic to disable some based on the layout. 
What highly likely is happening is that part of another widget that is 
transparent is on top of the checkbox and eating the clicks and thus nothing 
happens.

With the whole UI rework haven't had the chance to look at this dialog in a 
while. It appeared to be working fine and I had bigger fish to fry. I will 
take a look at the bug and see if I can fix it the issue for you.

> >> Is this a bug/regression in 4.1.8?
> >> 
> >> I did clear my browser cache thinking that might be it, but no, that
> >> didn't help.
> >> 
> >> The only thing I could do was Edit the VM, go to Boot options, select it
> >> there (which I could do) and then choose the ISO.  THEN I could run it
> >> with the CD attached.
> >> 
> >> Thanks,
> >> 
> >> -derek


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


Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

2018-01-18 Thread Yuval Turgeman
Hi Luca,

We updated the FAQ [1] with a small script to help upgrade between major
releases.

[1] https://www.ovirt.org/node/faq/

On Mon, Jan 15, 2018 at 10:21 AM, Luca 'remix_tj' Lorenzetto <
lorenzetto.l...@gmail.com> wrote:

>
>
> On Thu, Jan 11, 2018 at 2:31 PM, Ryan Barry  wrote:
>
>> Note that, in the case of Node, the ovirt-release RPM should not be
>> installed. Mostly because it automatically enables a number of per-package
>> updates (such as vdsm) instead of installing a single image.
>>
>> Trimming the repo files so they look like what is shipped in Node
>> (IgnorePkgs and OnlyPkgs) will pull ovirt-node-ng-image-update.rpm,
>> which is the only package needing an update.
>>
>>
> Hi,
>
> i'm upgrading ovirt-node too. I found out that installing ovirt-release
> file and running yum upgrade wants to upgrade everything. Instead, if i
> make
>
> yum upgrade ovirt-node-ng-image*
>
> I get the new image downloaded.
>
> So which is the right procedure to upgrade a node? Maybe providing a
> single command alternative to yum (let's say ovirt-node-upgrade) for
> upgrading would be better and avoid issues when doing such operation.
>
> Luca
>
> --
> "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 , <
> lorenzetto.l...@gmail.com>
>
> ___
> 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] oVirt 4.2: hostdev passthrough not working any more

2018-01-18 Thread Daniel Helgenberger
Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.

When I was creating the particular VM in 4.1 it was working as expected.

The hostdev from before the upgrades are still present. I tried to
remove them and got an NPE (see below).

As a workaround, is the old hostusb[1] method I know back from 3.x still 
working in the 4.x
line?

AFAICT IOMMU is working

> dmesg | grep -e DMAR -e IOMMU
> [0.00] ACPI: DMAR 7b7e7000 002C6 (v01 HP ProLiant 
> 0001 HP   0001)
> [0.168032] DMAR: Host address width 46
> [0.168034] DMAR: DRHD base: 0x00fbffc000 flags: 0x0
> [0.168047] DMAR: dmar0: reg_base_addr fbffc000 ver 1:0 cap 
> 8d2078c106f0466 ecap f020de
> [0.168050] DMAR: DRHD base: 0x00c7ffc000 flags: 0x1
> [0.168061] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap 
> 8d2078c106f0466 ecap f020de
> [0.168063] DMAR: RMRR base: 0x0079174000 end: 0x0079176fff
> [0.168065] DMAR: RMRR base: 0x00791f4000 end: 0x00791f7fff
> [0.168067] DMAR: RMRR base: 0x00791de000 end: 0x00791f3fff
> [0.168070] DMAR: RMRR base: 0x00791cb000 end: 0x00791dbfff
> [0.168071] DMAR: RMRR base: 0x00791dc000 end: 0x00791ddfff
> [0.168073] DMAR: ATSR flags: 0x0
> [0.168075] DMAR: ATSR flags: 0x0
> [0.168079] DMAR-IR: IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
> [0.168082] DMAR-IR: IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
> [0.168084] DMAR-IR: IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
> [0.168086] DMAR-IR: HPET id 0 under DRHD base 0xc7ffc000
> [0.168088] DMAR-IR: Queued invalidation will be enabled to support x2apic 
> and Intr-remapping.
> [0.169073] DMAR-IR: Enabled IRQ remapping in x2apic mode

Thanks,

[1] https://www.ovirt.org/develop/release-management/features/virt/hostusb/
-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


> 2018-01-17 11:37:51,035+01 INFO  
> [org.ovirt.engine.core.bll.hostdev.RemoveVmHostDevicesCommand] (default 
> task-48) [57a8c14d-fc2c-4846-bc3d-cc4f3e8393f8] Running command: 
> RemoveVmHostDevicesCommand internal: false. Entities affected :  ID: 
> 6132322b-e187-4a83-b8c1-0477bde10497 Type: VMAction group 
> EDIT_ADMIN_VM_PROPERTIES with role type ADMIN
> 2018-01-17 11:37:51,037+01 ERROR 
> [org.ovirt.engine.core.bll.hostdev.RemoveVmHostDevicesCommand] (default 
> task-48) [57a8c14d-fc2c-4846-bc3d-cc4f3e8393f8] Command 
> 'org.ovirt.engine.core.bll.hostdev.RemoveVmHostDevicesCommand' failed: null
> 2018-01-17 11:37:51,037+01 ERROR 
> [org.ovirt.engine.core.bll.hostdev.RemoveVmHostDevicesCommand] (default 
> task-48) [57a8c14d-fc2c-4846-bc3d-cc4f3e8393f8] Exception: 
> java.lang.NullPointerException
>   at 
> org.ovirt.engine.core.bll.hostdev.RemoveVmHostDevicesCommand.executeCommand(RemoveVmHostDevicesCommand.java:64)
>  [bll.jar:]
>   at 
> org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1205)
>  [bll.jar:]
>   at 
> org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1345)
>  [bll.jar:]
>   at 
> org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1987) 
> [bll.jar:]
>   at 
> org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202)
>  [utils.jar:]
>   at 
> org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137)
>  [utils.jar:]
>   at 
> org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105)
>  [utils.jar:]
>   at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1405) 
> [bll.jar:]
>   at 
> org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:412) 
> [bll.jar:]
>   at 
> org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13)
>  [bll.jar:]
>   at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:509) 
> [bll.jar:]
>   at org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:491) 
> [bll.jar:]
>   at org.ovirt.engine.core.bll.Backend.runAction(Backend.java:444) 
> [bll.jar:]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_151]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_151]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_151]
>   at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151]
>   at 
> org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
>   at 
> 

Re: [ovirt-users] No master storage domain, force select?

2018-01-18 Thread Fred Rolland
Hi,

What is the status of the Data Center?
What is the status of the hosts?
Is there a host selected as SPM?

Also attach the engine/vdsm logs.


Thanks,
Fred

On Thu, Jan 18, 2018 at 7:26 AM, Jure Kranjc  wrote:

> Hello,
>
> is there a way to force select master storage domain? I have three data
> domains, we had some storage problems and now none of the domains is
> master. I cannot activate any because I should first activate the master
> one. Any help appreciated.
>
>
>
> ___
> 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] 4.2.0 Unable to create VM disk from VM Portal

2018-01-18 Thread Vrgotic, Marko
Dear Latcho,

I am glad you are also mentioning this.

I moved forward with my 4.2 setup and discovered following possibilities:

1.   To what Michal suggested (although its not an access I would like to 
give to regular users), its possible to create an Admin role allowing 
management/provisioning of only VMs:

a.   Users will be able to login to admin portal, see all the settings, be 
unable to change anything in the setup, except managing VMs and provisioning 
them

b.   It’s a risk for a Hosted_Engine to be deleted by someone not being 
careful – I am still about to investigate if I can protect it by an Affinity 
setting or create special permission jut for the Hosted_Engine

2.   About VM Portal: we for now have to rely on templates:

a.   The only way for users to spawn VMs from VM Portal is to have required 
templates created ahead.

b.   The hostname field will be used by cloud-init to create a hostname and 
that is the only things besides cpu and ram that you can edit from VM Portal

3.   Use of APIs and or Ansible

It would we very nice to have more ability on VM management from VM Portal, so 
that no End Users are allowed to Admin Portal.

I am aware it’s not a complete or most accurate answer to your question, but I 
hope it does bring some clarity to current situation.

--
Met vriendelijke groet / Best regards,
Marko Vrgotic
System Engineer/Customer Care
ActiveVideo

From: Latchezar Filtchev 
Date: Wednesday, 17 January 2018 at 16:44
To: Michal Skrivanek , "Vrgotic, Marko" 

Cc: "users@ovirt.org" 
Subject: RE: [ovirt-users] 4.2.0 Unable to create VM disk from VM Portal

Dear Michal,

Please clarify ‘Perhaps you can use webadmin and limit user’s permissions the 
way you need’. Clean oVirt 4.2 installation have only admin user. Or I am 
wrong? What type of user is webadmin you are talking about?

Thank you!
Best,
Latcho

From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
Michal Skrivanek
Sent: Friday, December 29, 2017 9:47 PM
To: Vrgotic, Marko
Cc: users@ovirt.org
Subject: Re: [ovirt-users] 4.2.0 Unable to create VM disk from VM Portal



On 29 Dec 2017, at 16:20, Vrgotic, Marko 
> wrote:
Dear oVirt community,

I have following setup:
4 servers as glusterfs storage: providing volume 1 for HostedEngine ad volume 2 
for VM Storage
7 Hypervisors
SelfHosted Engine 4.2.0 clean install (not an upgrade)

Problem:
Missing option to add/create VM disk from VM Portal / even as Admin user.

Hi,
there is no disk manipulation in VM Portal



I have tried with Admin suer and creating user “Test” wth PowerUser role.
In both cases there is not option to create or attach disk.

Is the approach changed since 4.2.0?

Yes. The old User Portal where it was possible to fully edit a VM was 
discontinued in 4.2. The new VM Portal doesn’t have that capability yet

Perhaps you can use webadmin and limit user’s permissions the way you need

Thanks,
michal


Am I missing a setting?
Please let me know, I will provide more data if needed.

Kindly awaiting your reply.

--
Met vriendelijke groet / Best regards,
Marko Vrgotic
System Engineer/Customer Care

___
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