Re: [ovirt-users] oVirt on a single server

[Yedidyah Bar David]

On Mon, Sep 5, 2016 at 9:37 AM, Nir Soffer  wrote:
> On Mon, Sep 5, 2016 at 8:46 AM, Philip Lo  wrote:
>> I'm running single node hosted engine 4.0.x with local NFS and it runs just
>> fine. Thanks
>>
>> Regards,
>> Philip Lo
>>
>> On 5 Sep 2016, at 5:45 AM, Christophe TREFOIS 
>> wrote:
>>
>> I’m running 3.6 with local NFS for the hosted engine. I have more than one
>> host but they are all isolated and export they storage via local NFS. Setup
>> has been running since 1 year now.
>
> It run fine but it may deadlock :-)
>
> See
> - https://bugzilla.redhat.com/489889
> - https://access.redhat.com/solutions/22231

Indeed, see also:

https://lwn.net/Articles/595652/

>
> Such setup is ok for testing or development.

Another option is iSCSI, which AFAIU does not suffer from this problem.

And yet another option is using nested-kvm to run multiple virtual
"hosts" on a single physical one, and run hosted-engine on them, with
another VM serving nfs or iSCSI storage. This obviously provides lower
performance, but higher flexibility, and is probably ideal for learning
oVirt, testing etc. Obviously you can't create/maintain these hosts
using oVirt itself, but have to use e.g. virsh or virt-manager.

There is a project called lago [1] doing just that, and some of the CI
tests of oVirt already use it to do a full hosted-engine setup.

[1] http://lago.readthedocs.io/en/stable/
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt on a single server

[Christophe TREFOIS]

Oh wow. Well then I guess we are in a bad situation now. Don't really have the 
infra to move to shared storage...

Isn't this the same issue then with NFS over gluster?

Best,

Sent from my iPhone

> On 05 Sep 2016, at 08:37, Nir Soffer  wrote:
> 
>> On Mon, Sep 5, 2016 at 8:46 AM, Philip Lo  wrote:
>> I'm running single node hosted engine 4.0.x with local NFS and it runs just
>> fine. Thanks
>> 
>> Regards,
>> Philip Lo
>> 
>> On 5 Sep 2016, at 5:45 AM, Christophe TREFOIS 
>> wrote:
>> 
>> I’m running 3.6 with local NFS for the hosted engine. I have more than one
>> host but they are all isolated and export they storage via local NFS. Setup
>> has been running since 1 year now.
> 
> It run fine but it may deadlock :-)
> 
> See
> - https://bugzilla.redhat.com/489889
> - https://access.redhat.com/solutions/22231
> 
> Such setup is ok for testing or development.
> 
> Nir


smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt on a single server

[Nir Soffer]

On Mon, Sep 5, 2016 at 8:46 AM, Philip Lo  wrote:
> I'm running single node hosted engine 4.0.x with local NFS and it runs just
> fine. Thanks
>
> Regards,
> Philip Lo
>
> On 5 Sep 2016, at 5:45 AM, Christophe TREFOIS 
> wrote:
>
> I’m running 3.6 with local NFS for the hosted engine. I have more than one
> host but they are all isolated and export they storage via local NFS. Setup
> has been running since 1 year now.

It run fine but it may deadlock :-)

See
- https://bugzilla.redhat.com/489889
- https://access.redhat.com/solutions/22231

Such setup is ok for testing or development.

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

Re: [ovirt-users] oVirt on a single server

[Philip Lo]

I'm running single node hosted engine 4.0.x with local NFS and it runs just 
fine. Thanks

Regards,
Philip Lo

> On 5 Sep 2016, at 5:45 AM, Christophe TREFOIS  
> wrote:
> 
> I’m running 3.6 with local NFS for the hosted engine. I have more than one 
> host but they are all isolated and export they storage via local NFS. Setup 
> has been running since 1 year now.
>  
> Maye you can give it a try?
>  
> Cheers,
> Chris
>  
> From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
> zero four
> Sent: dimanche 4 septembre 2016 22:45
> To: users@ovirt.org
> Subject: [ovirt-users] oVirt on a single server
>  
> My current understanding is that oVirt no longer supports any single-server 
> configuration since the All-In-One install was removed in 3.6.  While the 
> hosted-engine install was supposed to replace it, it requires either 
> networked storage (nfs, iscsi) or Glusterfs.  To my knowledge nfs/iscsi 
> exported to localhost is not supported, so I would need at least 2 machines.  
> Furthermore Gluster requires at least 3 sources of storage for quorum (it 
> would be great if there was an option to acknowledge the risks and continue), 
> meaning a single machine is not practical.
>  
> I understand and acknowledge that oVirt is not targeted towards homelab 
> setups, or at least small homelab setups.  However I believe that having a 
> solid configuration for such use cases would be a benefit to the project as a 
> whole.  It allows oVirt to be much more visible in the homelab community, and 
> more accessible to testing which in turn yields more people who have 
> experience with oVirt.  As it stands most other virtualization products allow 
> for usage (not just a livecd) in a single server environment, although not 
> all features can be used of course.  vSphere, Xenserver, Proxmox, FIFO, and 
> Nutanix all allow an installation on a single server. It appears that 
> oVirt/RHV is the odd-one out - and it honestly shows when you look at what 
> people talk about online - there is a huge gap between even Proxmox and oVirt 
> when it comes to mindshare in the tech community, and it does not favor oVirt.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Documentation

[Brett I. Holcomb]

Thanks for the information.  I haven't done forks or requests with 
Github.  I appreciate the offer and at some point my take you up on it 
but right now I'm swamped and just can't handle one more thing and it 
sounds like the fork/pull is not trival.  I things slow down I'll try 
and get back to you on it.  Right now it's a LibreOffice document that I 
made from the notes I did in a text editor while struggling with the 
install.




On 09/04/2016 06:59 PM, Tom Gamull wrote:
The docs do suck but I would challenge you to submit a pull request. 
 It’s a pain if you haven’t done github forks and pull requests. 
 However, if you do this and it doesn’t get merged, you have every 
right to complain and I’ll be behind you 100%.  I’ve been in your 
shoes and just recently started helping in little bits on some projects.


If you can fork the documents, change them to include your notes, I’d 
be happy to hand hold or explain how to do the pull request (think 
merging your changes back). you can even email me direct if needed.


Tom Gamull


On Sep 4, 2016, at 4:26 PM, Brett I. Holcomb > wrote:


Yeah, its frustrating for sure as I spent a lot of wasted time trying 
to figure out what applied, what didn't, what was out of date and a 
lot of what did apply assumed I already knew parts I needed.   I came 
from VMware and Hyper-V worlds and really like oVirt and what it's 
doing but the documentation can be frustrating for sure.  
Unfortunately, that seems to be the way of a lot of OpenSource and 
along with that very few people like to do documentation and when 
they do it's from the perspective of someone who already knows the 
answers so it really doesn't help a brand new person who has no 
clue.  I had to do several hosted engine installs before I got it 
working (the stupid installer can't recover from an error so it makes 
you start over) on 3.6 (thanks be to VMware Workstation that let me 
start over ).  I took a lot of notes  and when I get time I'll 
post them. I know some will say we should contribute to the docs but 
I know I already have a full schedule with work and family and can't 
do anymore.


I've found this mailing list is the best source of information and 
sometimes they can link to sources we haven't found.  The people in 
this group are really knowledgeable and helpful so until the do get 
updated docs ask here.


On 09/04/2016 04:14 PM, zero four wrote:


As a prospective user of oVirt I have noticed quite a lot of glaring 
problems with the documentation, is it still being maintained? Since 
outdated or incomplete documentation is often worse than nothing, a 
possible solution would be to just link to the official Red Hat 
Virtualization documentation.


Here are some examples I found after looking for less than 5 minutes:

1.

http://www.ovirt.org/documentation/

The top of this web page has two videos from 2012. The left one 
"oVirt Open Virtualization Basics -- Single Machine Install" is a 
guide for the all in one install.  This is misleading as it no 
longer possible to perform an all in one install since 3.6, and in 
general it would appear the oVirt project does not support deploying 
oVirt to a single machine. The right video is a guide on creating 
VMs using the GUI from 2012 which has since changed.


Overall both videos should be removed from the Documentation page as 
they only confuse and mislead new users.  I, and I am sure many 
other users would greatly appreciate more current video guides.


2.

https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install

Under the notes for this there is the following passage:

“Although hosted-engine and engine-setup use different wording for 
the admin password ("'admin@internal' user password" vs "Engine 
admin password"), they are asking for the same thing. If you enter 
different passwords, the hosted-engine setup will fail.”


Why is the wording different?  This appears to be entirely 
unnecessary, and also confusing as to why it is asking for the 
password a second time at all.


3.

https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install

After finishing the hosted engine deployment script the guide states:

“After completing the OS installation on the VM, return to the host 
and continue. The installer on the host will sync with the VM and 
ask for the engine to be installed on the new VM:”


It is unclear how you are expected to access the VM, is the Web UI 
up at this point?  Do you need to use virsh to connect to the VM?  
The guide should be explicit.


4.

https://www.ovirt.org/documentation/quickstart/quickstart-guide/#prerequisites

 I. The documentation discusses Fedora 19, Fedora is currently on 
version 24 and 19 is EOL.


II. Under “Storage and Networking” there is no mention that oVirt 
requires at least 3 GlusterFS bricks to achieve quorum.


III. Under “Virtual Machines” there is no mention of Windows 10, 
Fedora past version 20, or RHEL/CentOS 7.X.




__

Re: [ovirt-users] Documentation

[Tom Gamull]

The docs do suck but I would challenge you to submit a pull request.  It’s a 
pain if you haven’t done github forks and pull requests.  However, if you do 
this and it doesn’t get merged, you have every right to complain and I’ll be 
behind you 100%.  I’ve been in your shoes and just recently started helping in 
little bits on some projects.

If you can fork the documents, change them to include your notes, I’d be happy 
to hand hold or explain how to do the pull request (think merging your changes 
back). you can even email me direct if needed.

Tom Gamull


> On Sep 4, 2016, at 4:26 PM, Brett I. Holcomb  wrote:
> 
> Yeah, its frustrating for sure as I spent a lot of wasted time trying to 
> figure out what applied, what didn't, what was out of date and a lot of what 
> did apply assumed I already knew parts I needed.   I came from VMware and 
> Hyper-V worlds and really like oVirt and what it's doing but the 
> documentation can be frustrating for sure.  Unfortunately, that seems to be 
> the way of a lot of OpenSource and along with that very few people like to do 
> documentation and when they do it's from the perspective of someone who 
> already knows the answers so it really doesn't help a brand new person who 
> has no clue.  I had to do several hosted engine installs before I got it 
> working (the stupid installer can't recover from an error so it makes you 
> start over) on 3.6 (thanks be to VMware Workstation that let me start over 
> ).  I took a lot of notes  and when I get time I'll post them. I know some 
> will say we should contribute to the docs but I know I already have a full 
> schedule with work and family and can't do anymore.
> 
> I've found this mailing list is the best source of information and sometimes 
> they can link to sources we haven't found.  The people in this group are 
> really knowledgeable and helpful so until the do get updated docs ask here.
> 
> On 09/04/2016 04:14 PM, zero four wrote:
>> As a prospective user of oVirt I have noticed quite a lot of glaring 
>> problems with the documentation, is it still being maintained?  Since 
>> outdated or incomplete documentation is often worse than nothing, a possible 
>> solution would be to just link to the official Red Hat Virtualization 
>> documentation.
>> Here are some examples I found after looking for less than 5 minutes:
>> 1. 
>>  http://www.ovirt.org/documentation/ 
>> 
>> The top of this web page has two videos from 2012. The left one "oVirt Open 
>> Virtualization Basics -- Single Machine Install" is a guide for the all in 
>> one install.  This is misleading as it no longer possible to perform an all 
>> in one install since 3.6, and in general it would appear the oVirt project 
>> does not support deploying oVirt to a single machine. The right video is a 
>> guide on creating VMs using the GUI from 2012 which has since changed.
>> Overall both videos should be removed from the Documentation page as they 
>> only confuse and mislead new users.  I, and I am sure many other users would 
>> greatly appreciate more current video guides.
>> 2.
>>  
>> https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install
>>  
>> Under the notes for this there is the following passage:
>>  “Although hosted-engine and engine-setup use different wording for the 
>> admin password   ("'admin@internal' user password" vs "Engine admin 
>> password"), they are asking for the same thing. If you enter different 
>> passwords, the hosted-engine setup will fail.”
>> Why is the wording different?  This appears to be entirely unnecessary, and 
>> also confusing as to why it is asking for the password a second time at all.
>> 3.
>>  
>> https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install
>>  
>> After finishing the hosted engine deployment script the guide states:
>>  “After completing the OS installation on the VM, return to the host and 
>> continue. The installer on the host will sync with the VM and ask 
>> for the   engine to be installed on the new VM:”
>> It is unclear how you are expected to access the VM, is the Web UI up at 
>> this point?  Do you need to use virsh to connect to the VM?  The guide 
>> should be explicit.
>> 4.
>>  
>> https://www.ovirt.org/documentation/quickstart/quickstart-guide/#prerequisites
>>  
>> 
>>  I. The documentation discusses Fedora 19, Fedora is currently on version 24 
>> and 19 is EOL.
>> II. Under “Storage and Networking” th

Re: [ovirt-users] oVirt on a single server

[Christophe TREFOIS]

I’m running 3.6 with local NFS for the hosted engine. I have more than one host 
but they are all isolated and export they storage via local NFS. Setup has been 
running since 1 year now.

 

Maye you can give it a try?

 

Cheers,

Chris

 

From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
zero four
Sent: dimanche 4 septembre 2016 22:45
To: users@ovirt.org
Subject: [ovirt-users] oVirt on a single server

 

My current understanding is that oVirt no longer supports any single-server 
configuration since the All-In-One install was removed in 3.6.  While the 
hosted-engine install was supposed to replace it, it requires either networked 
storage (nfs, iscsi) or Glusterfs.  To my knowledge nfs/iscsi exported to 
localhost is not supported, so I would need at least 2 machines.  Furthermore 
Gluster requires at least 3 sources of storage for quorum (it would be great if 
there was an option to acknowledge the risks and continue), meaning a single 
machine is not practical.

 

I understand and acknowledge that oVirt is not targeted towards homelab setups, 
or at least small homelab setups.  However I believe that having a solid 
configuration for such use cases would be a benefit to the project as a whole.  
It allows oVirt to be much more visible in the homelab community, and more 
accessible to testing which in turn yields more people who have experience with 
oVirt.  As it stands most other virtualization products allow for usage (not 
just a livecd) in a single server environment, although not all features can be 
used of course.  vSphere, Xenserver, Proxmox, FIFO, and Nutanix all allow an 
installation on a single server. It appears that oVirt/RHV is the odd-one out - 
and it honestly shows when you look at what people talk about online - there is 
a huge gap between even Proxmox and oVirt when it comes to mindshare in the 
tech community, and it does not favor oVirt.



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt on a single server

[Nir Soffer]

On Sun, Sep 4, 2016 at 11:45 PM, zero four  wrote:
> My current understanding is that oVirt no longer supports any single-server
> configuration since the All-In-One install was removed in 3.6.  While the
> hosted-engine install was supposed to replace it, it requires either
> networked storage (nfs, iscsi) or Glusterfs.  To my knowledge nfs/iscsi
> exported to localhost is not supported,

nfs exported to localhost may be fragile. iscsi server on your single host
should work.

The best option for single host is local storage, but I don't know if hosted
engine supports it.

> so I would need at least 2 machines.
> Furthermore Gluster requires at least 3 sources of storage for quorum (it
> would be great if there was an option to acknowledge the risks and
> continue), meaning a single machine is not practical.

You can use single glusterfs brick, I think it should work wit hosted engine
setup.

> I understand and acknowledge that oVirt is not targeted towards homelab
> setups, or at least small homelab setups.  However I believe that having a
> solid configuration for such use cases would be a benefit to the project as
> a whole.  It allows oVirt to be much more visible in the homelab community,
> and more accessible to testing which in turn yields more people who have
> experience with oVirt.  As it stands most other virtualization products
> allow for usage (not just a livecd) in a single server environment, although
> not all features can be used of course.  vSphere, Xenserver, Proxmox, FIFO,
> and Nutanix all allow an installation on a single server. It appears that
> oVirt/RHV is the odd-one out - and it honestly shows when you look at what
> people talk about online - there is a huge gap between even Proxmox and
> oVirt when it comes to mindshare in the tech community, and it does not
> favor oVirt.

I agree that it would nice if the all-in-one option was still available, but
someone has to maintain this setup.

For single host, better use virt-manager. You can import the vms later to
ovirt when you want to scale your lab.

If you want to experiment with ovirt, you can use virt-manager to create
several vms - if you enable nested kvm, you can use the vms as your
hosts. This is the standard setup we use for development.

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

Re: [ovirt-users] Documentation

[Nir Soffer]

On Sun, Sep 4, 2016 at 11:14 PM, zero four  wrote:
> As a prospective user of oVirt I have noticed quite a lot of glaring
> problems with the documentation, is it still being maintained?  Since
> outdated or incomplete documentation is often worse than nothing, a possible
> solution would be to just link to the official Red Hat Virtualization
> documentation.
>
> Here are some examples I found after looking for less than 5 minutes:
>
> 1.
>
> http://www.ovirt.org/documentation/
>
> The top of this web page has two videos from 2012. The left one "oVirt Open
> Virtualization Basics -- Single Machine Install" is a guide for the all in
> one install.  This is misleading as it no longer possible to perform an all
> in one install since 3.6, and in general it would appear the oVirt project
> does not support deploying oVirt to a single machine. The right video is a
> guide on creating VMs using the GUI from 2012 which has since changed.
>
> Overall both videos should be removed from the Documentation page as they
> only confuse and mislead new users.  I, and I am sure many other users would
> greatly appreciate more current video guides.
>
> 2.
>
> https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install
>
> Under the notes for this there is the following passage:
>
> “Although hosted-engine and engine-setup use different wording for the admin
> password ("'admin@internal' user password" vs "Engine admin password"), they
> are asking for the same thing. If you enter different passwords, the
> hosted-engine setup will fail.”
>
> Why is the wording different?  This appears to be entirely unnecessary, and
> also confusing as to why it is asking for the password a second time at all.
>
> 3.
>
> https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install
>
> After finishing the hosted engine deployment script the guide states:
>
> “After completing the OS installation on the VM, return to the host and
> continue. The installer on the host will sync with the VM and ask for the
> engine to be installed on the new VM:”
>
> It is unclear how you are expected to access the VM, is the Web UI up at
> this point?  Do you need to use virsh to connect to the VM?  The guide
> should be explicit.
>
> 4.
>
> https://www.ovirt.org/documentation/quickstart/quickstart-guide/#prerequisites
>
>  I. The documentation discusses Fedora 19, Fedora is currently on version 24
> and 19 is EOL.
>
> II. Under “Storage and Networking” there is no mention that oVirt requires
> at least 3 GlusterFS bricks to achieve quorum.
>
> III. Under “Virtual Machines” there is no mention of Windows 10, Fedora past
> version 20, or RHEL/CentOS 7.X.

Thanks for reporting this, you can open an issues for these:
https://github.com/oVirt/ovirt-site/issues

Or even send a fix, check this link at the bottom of the page:
"Edit this page on GitHub"

In the past you could simply edit the page in the wiki, now you
have to send a pull request using github, which is little harder.

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

Re: [ovirt-users] Documentation

[Brett I. Holcomb]

Yeah, its frustrating for sure as I spent a lot of wasted time trying to 
figure out what applied, what didn't, what was out of date and a lot of 
what did apply assumed I already knew parts I needed.   I came from 
VMware and Hyper-V worlds and really like oVirt and what it's doing but 
the documentation can be frustrating for sure.  Unfortunately, that 
seems to be the way of a lot of OpenSource and along with that very few 
people like to do documentation and when they do it's from the 
perspective of someone who already knows the answers so it really 
doesn't help a brand new person who has no clue.  I had to do several 
hosted engine installs before I got it working (the stupid installer 
can't recover from an error so it makes you start over) on 3.6 (thanks 
be to VMware Workstation that let me start over ).  I took a lot of 
notes  and when I get time I'll post them. I know some will say we 
should contribute to the docs but I know I already have a full schedule 
with work and family and can't do anymore.


I've found this mailing list is the best source of information and 
sometimes they can link to sources we haven't found.  The people in this 
group are really knowledgeable and helpful so until the do get updated 
docs ask here.


On 09/04/2016 04:14 PM, zero four wrote:


As a prospective user of oVirt I have noticed quite a lot of glaring 
problems with the documentation, is it still being maintained?  Since 
outdated or incomplete documentation is often worse than nothing, a 
possible solution would be to just link to the official Red Hat 
Virtualization documentation.


Here are some examples I found after looking for less than 5 minutes:

1.

http://www.ovirt.org/documentation/

The top of this web page has two videos from 2012. The left one "oVirt 
Open Virtualization Basics -- Single Machine Install" is a guide for 
the all in one install.  This is misleading as it no longer possible 
to perform an all in one install since 3.6, and in general it would 
appear the oVirt project does not support deploying oVirt to a single 
machine. The right video is a guide on creating VMs using the GUI from 
2012 which has since changed.


Overall both videos should be removed from the Documentation page as 
they only confuse and mislead new users.  I, and I am sure many other 
users would greatly appreciate more current video guides.


2.

https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install

Under the notes for this there is the following passage:

“Although hosted-engine and engine-setup use different wording for the 
admin password ("'admin@internal' user password" vs "Engine admin 
password"), they are asking for the same thing. If you enter different 
passwords, the hosted-engine setup will fail.”


Why is the wording different?  This appears to be entirely 
unnecessary, and also confusing as to why it is asking for the 
password a second time at all.


3.

https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install

After finishing the hosted engine deployment script the guide states:

“After completing the OS installation on the VM, return to the host 
and continue. The installer on the host will sync with the VM and ask 
for the engine to be installed on the new VM:”


It is unclear how you are expected to access the VM, is the Web UI up 
at this point?  Do you need to use virsh to connect to the VM?  The 
guide should be explicit.


4.

https://www.ovirt.org/documentation/quickstart/quickstart-guide/#prerequisites

 I. The documentation discusses Fedora 19, Fedora is currently on 
version 24 and 19 is EOL.


II. Under “Storage and Networking” there is no mention that oVirt 
requires at least 3 GlusterFS bricks to achieve quorum.


III. Under “Virtual Machines” there is no mention of Windows 10, 
Fedora past version 20, or RHEL/CentOS 7.X.




___
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 on a single server

[zero four]

My current understanding is that oVirt no longer supports any single-server
configuration since the All-In-One install was removed in 3.6.  While the
hosted-engine install was supposed to replace it, it requires either
networked storage (nfs, iscsi) or Glusterfs.  To my knowledge nfs/iscsi
exported to localhost is not supported, so I would need at least 2
machines.  Furthermore Gluster requires at least 3 sources of storage for
quorum (it would be great if there was an option to acknowledge the risks
and continue), meaning a single machine is not practical.

I understand and acknowledge that oVirt is not targeted towards homelab
setups, or at least small homelab setups.  However I believe that having a
solid configuration for such use cases would be a benefit to the project as
a whole.  It allows oVirt to be much more visible in the homelab community,
and more accessible to testing which in turn yields more people who have
experience with oVirt.  As it stands most other virtualization products
allow for usage (not just a livecd) in a single server environment,
although not all features can be used of course.  vSphere, Xenserver,
Proxmox, FIFO, and Nutanix all allow an installation on a single server. It
appears that oVirt/RHV is the odd-one out - and it honestly shows when you
look at what people talk about online - there is a huge gap between even
Proxmox and oVirt when it comes to mindshare in the tech community, and it
does not favor oVirt.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Documentation

[zero four]

As a prospective user of oVirt I have noticed quite a lot of glaring
problems with the documentation, is it still being maintained?  Since
outdated or incomplete documentation is often worse than nothing, a
possible solution would be to just link to the official Red Hat
Virtualization documentation.

Here are some examples I found after looking for less than 5 minutes:

1.

http://www.ovirt.org/documentation/

The top of this web page has two videos from 2012. The left one "oVirt Open
Virtualization Basics -- Single Machine Install" is a guide for the all in
one install.  This is misleading as it no longer possible to perform an all
in one install since 3.6, and in general it would appear the oVirt project
does not support deploying oVirt to a single machine. The right video is a
guide on creating VMs using the GUI from 2012 which has since changed.

Overall both videos should be removed from the Documentation page as they
only confuse and mislead new users.  I, and I am sure many other users
would greatly appreciate more current video guides.

2.

https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install

Under the notes for this there is the following passage:

“Although hosted-engine and engine-setup use different wording for the
admin password ("'admin@internal' user password" vs "Engine admin
password"), they are asking for the same thing. If you enter different
passwords, the hosted-engine setup will fail.”

Why is the wording different?  This appears to be entirely unnecessary, and
also confusing as to why it is asking for the password a second time at all.

3.

https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install

After finishing the hosted engine deployment script the guide states:

“After completing the OS installation on the VM, return to the host and
continue. The installer on the host will sync with the VM and ask for
the engine
to be installed on the new VM:”

It is unclear how you are expected to access the VM, is the Web UI up at
this point?  Do you need to use virsh to connect to the VM?  The guide
should be explicit.

4.

https://www.ovirt.org/documentation/quickstart/quickstart-guide/#prerequisites

 I. The documentation discusses Fedora 19, Fedora is currently on version
24 and 19 is EOL.

II. Under “Storage and Networking” there is no mention that oVirt requires
at least 3 GlusterFS bricks to achieve quorum.

III. Under “Virtual Machines” there is no mention of Windows 10, Fedora
past version 20, or RHEL/CentOS 7.X.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] where to get information about wdmd, sanlock logic

[Nir Soffer]

On Sat, Sep 3, 2016 at 1:26 PM, Gianluca Cecchi
 wrote:
>
> Hello,
> is wdmd similar to the old watchdog daemon that was used to kill node (eg in 
> old Oracle 9i RAC environments on Linux)?
> Is it stoppable at all  without having host reboot itself?

Only if not lease is used (see below).

> I see many other daemons on the hypervisor but not so clear the correlation 
> between them and inter-dependency
> Eg
> momd, vdsmd, supervdsmd
> or
> ovirt-ha-agent, ovirt-habroker

supervdsmd is a helper service running as root, used by vdsm to perform
operations that require privileges. Started by systemd if vdsm is started.
If you stop it when vdsm is running, many vdsm operations will fail until
you start it again.

In 4.0 we also have ovirt-imageio-daemon - this is a service used to upload
or download images using http. Started when vdsmd starts. If you stop it
during an upload/download, you will fail the operation, and you will have to
resume it via engine. You will not be able to upload/download images if
the service is stopped.

Adding Martin to explain about momd, ovirt-ha-agent, ovirt-habroker

> Suppose I have an environment with only one host up (eg single host 
> environment but not only; think about a site where due to planned maintenance 
> I have to stop all one at a time), do I have a way to put the host in single 
> user mode without having it automatically reboot itself?

Put the host in maintenance via engine, then all services
can be stopped safely.

> Any docs?

We may have something in ovirt.org.

Here some info regarding vdsm, sanlock and wdmd

- vdsmd - take leases on share storage via sanlock
- sanlock - manage leases on shared storage, uses wdmd to reboot the
  system on fatal failures
- wdmd  -  used by sanlock to multiplex multiple timeouts onto the host
  watchdog timer.

If sanlock has a lease on shared storage (spm lease on the spm host,
or volume lease in the host running hosted engine), you cannot stop
it. If you kill it, it will not pet the host watchdog in time, and the host
watchdog will reboot the machine.

Stopping/killing wdmd may lead to reboot if the host watchdog is used.

To stop sanlock and wdmd safely (for example for upgrade), you must
put the host in maintenance mode via engine. This will release any lease
on shared storage and stop the host watchdog.

You can find more info in sanlock manual:
https://fedorahosted.org/sanlock/

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

Re: [ovirt-users] Hung task finalizing live migration

[Nir Soffer]

On Sun, Sep 4, 2016 at 12:40 PM, Maton, Brett 
wrote:

> How do I fix / kill a hung vdsm task?
>
> It seems to have completed the task but is stuck finalising.
>
> Removing Snapshot Auto-generated for Live Storage Migration
> Validating
> Executing
> (hour glass) Finalizing
>
> Task has been 'stuck' finalising for over 13 hours
>

Can you share engine and vdsm logs since the time the merge was started?

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

[ovirt-users] Hung task finalizing live migration

[Maton, Brett]

How do I fix / kill a hung vdsm task?

It seems to have completed the task but is stuck finalising.

Removing Snapshot Auto-generated for Live Storage Migration
Validating
Executing
(hour glass) Finalizing

Task has been 'stuck' finalising for over 13 hours
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] global vs local maintenance with single host

[Yedidyah Bar David]

On Sat, Sep 3, 2016 at 1:18 PM, Gianluca Cecchi
 wrote:
> Hello,
> how do the two modes apply in case of single host?
> During an upgrade phase, after having upgraded the self hosted engine and
> leaving global maintenance and having checked all is ok, what is the correct
> mode then to put host if I want finally to update it too?

The docs say to put hosts to maintenance from the engine before upgrading them.

This is (also) so that VMs on them are migrated away to other hosts.

With a single host, you have no other hosts to migrate VMs to.

So you should do something like this:

1. Set global maintenance (because you are going to take down the
engine and its vm)
2. Shutdown all other VMs
3. Shutdown engine vm from itself
At this point, you should be able to simply stop HA services. But it
might be cleaner to first set local maintenance. Not sure but perhaps
this might be required for vdsm. So:
4. Set local maintenance
5. Stop HA services. If setting local maintenance didn't work, perhaps
better stop also vdsm services. This stop should obviously happen
automatically by yum/rpm, but perhaps better do this manually to see
that it worked.
6. yum (or dnf) update stuff.
7. Start HA services
8. Check status. I think you'll see that both local and global maint
are still set.
9. Set maintenance to none
10. Check status again - I think that after some time HA will decide
to start engine vm and should succeed.
11. Start all other VMs.

Didn't try this myself.

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

Re: [ovirt-users] oVirt Slides not found

[Yedidyah Bar David]

On Sun, Sep 4, 2016 at 12:36 AM, wodel youchi  wrote:
> Hi,
>
> I am preparing a presentation of oVirt for a new client, it's not the first
> time, but I used to use the presentations from oVirt's slide deck to get the
> recent features, but it seems no slide is available, all links are dead.

Indeed:

https://github.com/oVirt/ovirt-site/issues/77

As mentioned there, you can find the files in:

http://resources.ovirt.org/old-site-files/

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