[ovirt-users] oVirt 4.4.1 HCI single server deployment failed nested-kvm

[wodel youchi]

Hi,

I am using these versions for my test :
- ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm
- ovirt-node-ng-installer-4.4.1-2020072310.el8.iso

A single HCI server using nested KVM.
The gluster part works now without error, but when I click the
hosted-engine deployment button I get :

*System data could not be retrieved!*
*No valid network interface has been found *
* If you are using Bonds or VLANs Use the following naming conventions: *
- VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128,
enp3s0.50)
- Bond interfaces: bond*number* (for example, bond0, bond1)
- VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50,
bond1.128)
* Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad
* Networking teaming is not supported and will cause errors


>From this log file I get :
cat ovirt-hosted-engine-setup-ansible-get_network_interfaces-.log
2020-07-29 15:27:09,246+0100 DEBUG var changed: host "localhost" var
"otopi_host_net" type "" value: "[
   "enp1s0",
   "enp2s0"
]"
2020-07-29 15:27:09,246+0100 INFO ansible ok {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng
ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost',
'ansible_task': 'Filter unsupported interface types', 'task_duration
': 0}
2020-07-29 15:27:09,246+0100 DEBUG ansible on_any args
 kwargs
2020-07-29 15:27:09,514+0100 INFO ansible task start {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho
sted-engine-setup/ansible/trigger_role.yml', 'ansible_task':
'ovirt.hosted_engine_setup : debug'}
2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args TASK:
ovirt.hosted_engine_setup : debug kwargs is_conditional:False
2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : debug kwargs
2020-07-29 15:27:09,792+0100 INFO ansible ok {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng
ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost',
'ansible_task': '', 'task_duration': 0}
2020-07-29 15:27:09,793+0100 DEBUG ansible on_any args
 kwargs
2020-07-29 15:27:10,059+0100 INFO ansible task start {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho
sted-engine-setup/ansible/trigger_role.yml', 'ansible_task':
'ovirt.hosted_engine_setup : Failed if only teaming devices are availible
'}
2020-07-29 15:27:10,059+0100 DEBUG ansible on_any args TASK:
ovirt.hosted_engine_setup : Failed if only teaming devices are availible
kwargs is_conditional:False
2020-07-29 15:27:10,060+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : Failed if only teaming devices are a
vailible kwargs
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"ansible_play_hosts" type "" value: "[]"
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"ansible_play_batch" type "" value: "[]"
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"play_hosts" type "" value: "[]"
2020-07-29 15:27:10,376+0100 ERROR ansible failed {
   "ansible_host": "localhost",
   "ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
   "ansible_result": {
   "_ansible_no_log": false,
   "msg": "The conditional check

*'(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The
error was: error while evaluating conditional
((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list
object' has no attribute 'ansible_facts'\n\nThe error appears to be in
'/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml':
line 29, column 13, *
but may\nbe elsewhere in the file depending on the exact syntax
problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_ho
st_net\n^ here\n\nThere appears to be both 'k=v' shorthand
syntax and YAML in this task. Only one syntax may be used.\n"
   },
   "ansible_task": "Failed if only teaming devices are availible",
   "ansible_type": "task",
   "status": "FAILED",
   "task_duration": 0
}
2020-07-29 15:27:10,377+0100 DEBUG ansible on_any args
 kwargs
ignor
e_errors:None
2020-07-29 15:27:10,378+0100 INFO ansible stats {
   "ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
   "ansible_playbook_duration": "00:15 Minutes",
   "ansible_result": "type: \nstr: {'localhost': {'ok': 16,
'failures': 1, 'unreachable': 0, 'changed': 1, 'skipped': 2
, 'rescued': 0, 'ignored': 0}}",
   "ansible_type": "finish",
   "status": "FAILED"
}
2020-07-29 15:27:10,378+0100 INFO SUMMARY:
DurationTask Name

[ < 1 sec ] Execute just a specific set of steps
[  00:02  ] Force facts gathering
[  00:01  ] Get all active network interfaces
[ < 1 sec ] Filter bonds with bad naming
[ < 1 sec ] Generate output list
[  00:01  ] Collect interface types
[ < 1 sec ] Get list of Team devices
[ < 

[ovirt-users] oVirt on a Single Server

[webmattr]

Hello,

I can't seem to install the self-hosted engine onto local storage. It gives me 
glustefs, iscsi, fc, and nfs as the available options. I'm using this in a 
home-lab scenario, and don't have budget/etc. for building out a dedicated NAS 
for it, or setting up multiple nodes. I like the look of oVirt, and wanted to 
try it with a couple disposable vm's (plex, and a docker instance I break 
often). My current best-thought for how to make it work is to setup NFS on the 
server, and then point the self-hosted engine at the (local) NFS share. Is 
there a better way to do this that I might be overlooking?*

*Factoring that I don't have the funds to build out a proper storage 
environment, yet.

(and if anyone asks, I did search for a solution to this, but didn't find 
anything super helpful. Mostly I found 5+ year old articles on a similar but 
different scenario).
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OB5AWOMHJZVR5INCPE37YAOVPWMECT2Y/

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

[Yaniv Dary]

I would suggest a local single brick gluster. This will probably be most
simple and you can have a scale out option in this way to replica 3.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Tue, Sep 6, 2016 at 12:54 PM, Yaniv Kaul  wrote:

>
>
> On Tue, Sep 6, 2016 at 12:17 PM, Christophe TREFOIS <
> christophe.tref...@uni.lu> wrote:
>
>> Hi,
>>
>> No, I move VMs around with an Export Storage domain.
>>
>
> If you have enough disk and bandwidth, perhaps it makes more sense to set
> up Gluster as a shared storage?
> And then just pin VMs to specific hosts, instead of separate DCs, etc.?
> Y.
>
>
>> All NFS is exported only to the local machine.
>>
>> Nothing is “shared” between hosts. But because I want to export VMs, we
>> use “shared” storage in oVirt instead of “local”.
>>
>> Best,
>>
>> --
>>
>> Dr Christophe Trefois, Dipl.-Ing.
>> Technical Specialist / Post-Doc
>>
>> UNIVERSITÉ DU LUXEMBOURG
>>
>> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>> Campus Belval | House of Biomedicine
>> 6, avenue du Swing
>> L-4367 Belvaux
>> T: +352 46 66 44 6124
>> F: +352 46 66 44 6949
>> http://www.uni.lu/lcsb
>>
>>
>>
>> 
>> This message is confidential and may contain privileged information.
>> It is intended for the named recipient only.
>> If you receive it in error please notify me and permanently delete the
>> original message and any copies.
>> 
>>
>>
>>
>> > On 06 Sep 2016, at 10:06, Yedidyah Bar David  wrote:
>> >
>> > On Tue, Sep 6, 2016 at 9:53 AM, Christophe TREFOIS
>> >  wrote:
>> >> Personally my use case is that I have 4 machines with different specs
>> and storage sizing. So I setup four DC with 1 host each. Then I have hosted
>> engine on one of the hosts. Storage is local shared via NFS so that I can
>> move VMs around.
>> >
>> > Not sure I fully understand.
>> >
>> > You use each of the 4 machines for both storage and running VMs?
>> > And export nfs on each to all the others?
>> >
>> > So that if a VM needs more CPU/memory then disk IO, you can move
>> > it to another machine and hopefully get better performance even
>> > though the storage is not local?
>> >
>> > I admit that it sounds very reasonable, and agree that doing this
>> > with nfs is easier than with iSCSI. If you don't mind the risk of
>> > local-nfs-mount locks, fine. As others noted, seems like it's quite
>> > a low risk.
>> >
>> >>
>> >> At this point we are not interested necessarily in HA.
>> >>
>> >> Maybe for you that's the definition of a Dev environment as production
>> has other attributes than just the type of storage?
>> >
>> > Dev or Prod is for you to define :-)
>> >
>> > How much time/money do you loose if a machine dies? If a machine
>> > locks up until someone notices and handles?
>> >
>> >>
>> >> Would be nice to hear your thoughts about this.
>> >
>> > As wrote above, sounds reasonable if you understand the risks
>> > and can live with them.
>> >
>> > Looking at the future you might want to check HC:
>> >
>> > https://www.ovirt.org/develop/release-management/features/gl
>> uster/glusterfs-hyperconvergence/
>> >
>> >>
>> >> Kind regards,
>> >> Christophe
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 06 Sep 2016, at 08:45, Yedidyah Bar David  wrote:
>> >>>
>> >>> On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
>> >>>  wrote:
>>  So basically we need at least 2 nodes to enter the realm of testing
>> and maintained?
>> >>>
>> >>> I think some people occasionally use hosted-engine with local
>> >>> iSCSI storage on a single machine. AFAIK it's not tested by CI
>> >>> or often, but patches are welcome - e.g. using lago and
>> >>> ovirt-system-tests.
>> >>>
>> >>> Can you please explain your intentions/requirements?
>> >>>
>> >>> Even if it works, oVirt is not designed for single-machine
>> >>> _production_ use. For that, I think that most people agree that
>> >>> virt-manager is more suitable. oVirt on a single machine is
>> >>> usually for testing/demonstration/learning/etc.
>> >>>
>> 
>>  If we’re talking pure oVirt here.
>> 
>>  --
>> 
>>  Dr Christophe Trefois, Dipl.-Ing.
>>  Technical Specialist / Post-Doc
>> 
>>  UNIVERSITÉ DU LUXEMBOURG
>> 
>>  LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>>  Campus Belval | House of Biomedicine
>>  6, avenue du Swing
>>  L-4367 Belvaux
>>  T: +352 46 66 44 6124
>>  F: +352 46 66 44 6949
>>  http://www.uni.lu/lcsb
>> 
>> 
>> 
>>  
>>  This message is confidential and may contain privileged information.
>>  It is intended for the named recipient only.
>>  If you receive it in error please notify me and permanently delete
>> the original message and any copies.
>>  
>> 
>> 
>> 
>> > On 05 Sep 

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

[Yaniv Kaul]

On Tue, Sep 6, 2016 at 12:17 PM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:

> Hi,
>
> No, I move VMs around with an Export Storage domain.
>

If you have enough disk and bandwidth, perhaps it makes more sense to set
up Gluster as a shared storage?
And then just pin VMs to specific hosts, instead of separate DCs, etc.?
Y.


> All NFS is exported only to the local machine.
>
> Nothing is “shared” between hosts. But because I want to export VMs, we
> use “shared” storage in oVirt instead of “local”.
>
> Best,
>
> --
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124
> F: +352 46 66 44 6949
> http://www.uni.lu/lcsb
>
>
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the
> original message and any copies.
> 
>
>
>
> > On 06 Sep 2016, at 10:06, Yedidyah Bar David  wrote:
> >
> > On Tue, Sep 6, 2016 at 9:53 AM, Christophe TREFOIS
> >  wrote:
> >> Personally my use case is that I have 4 machines with different specs
> and storage sizing. So I setup four DC with 1 host each. Then I have hosted
> engine on one of the hosts. Storage is local shared via NFS so that I can
> move VMs around.
> >
> > Not sure I fully understand.
> >
> > You use each of the 4 machines for both storage and running VMs?
> > And export nfs on each to all the others?
> >
> > So that if a VM needs more CPU/memory then disk IO, you can move
> > it to another machine and hopefully get better performance even
> > though the storage is not local?
> >
> > I admit that it sounds very reasonable, and agree that doing this
> > with nfs is easier than with iSCSI. If you don't mind the risk of
> > local-nfs-mount locks, fine. As others noted, seems like it's quite
> > a low risk.
> >
> >>
> >> At this point we are not interested necessarily in HA.
> >>
> >> Maybe for you that's the definition of a Dev environment as production
> has other attributes than just the type of storage?
> >
> > Dev or Prod is for you to define :-)
> >
> > How much time/money do you loose if a machine dies? If a machine
> > locks up until someone notices and handles?
> >
> >>
> >> Would be nice to hear your thoughts about this.
> >
> > As wrote above, sounds reasonable if you understand the risks
> > and can live with them.
> >
> > Looking at the future you might want to check HC:
> >
> > https://www.ovirt.org/develop/release-management/features/
> gluster/glusterfs-hyperconvergence/
> >
> >>
> >> Kind regards,
> >> Christophe
> >>
> >> Sent from my iPhone
> >>
> >>> On 06 Sep 2016, at 08:45, Yedidyah Bar David  wrote:
> >>>
> >>> On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
> >>>  wrote:
>  So basically we need at least 2 nodes to enter the realm of testing
> and maintained?
> >>>
> >>> I think some people occasionally use hosted-engine with local
> >>> iSCSI storage on a single machine. AFAIK it's not tested by CI
> >>> or often, but patches are welcome - e.g. using lago and
> >>> ovirt-system-tests.
> >>>
> >>> Can you please explain your intentions/requirements?
> >>>
> >>> Even if it works, oVirt is not designed for single-machine
> >>> _production_ use. For that, I think that most people agree that
> >>> virt-manager is more suitable. oVirt on a single machine is
> >>> usually for testing/demonstration/learning/etc.
> >>>
> 
>  If we’re talking pure oVirt here.
> 
>  --
> 
>  Dr Christophe Trefois, Dipl.-Ing.
>  Technical Specialist / Post-Doc
> 
>  UNIVERSITÉ DU LUXEMBOURG
> 
>  LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>  Campus Belval | House of Biomedicine
>  6, avenue du Swing
>  L-4367 Belvaux
>  T: +352 46 66 44 6124
>  F: +352 46 66 44 6949
>  http://www.uni.lu/lcsb
> 
> 
> 
>  
>  This message is confidential and may contain privileged information.
>  It is intended for the named recipient only.
>  If you receive it in error please notify me and permanently delete
> the original message and any copies.
>  
> 
> 
> 
> > On 05 Sep 2016, at 16:31, Fernando Frediani <
> fernando.fredi...@upx.com.br> wrote:
> >
> > Adding Kimchi to oVirt node perhaps may be the easiest option. It
> can be pretty useful for many situations and doesn't need such thing like
> mounting NFS in localhost.
> >
> > It is not nice to not have a All-in-One stable solution anymore as
> this can help with its adoption for later growth.
> >
> > oVirt-Cockpit looks nice and intresting.
> >
> > Fernando
> >
> >
> >> On 05/09/2016 05:18, Barak Korren wrote:
> >>> On 4 September 

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

[Yedidyah Bar David]

On Tue, Sep 6, 2016 at 12:17 PM, Christophe TREFOIS
 wrote:
> Hi,
>
> No, I move VMs around with an Export Storage domain.

OK.

>
> All NFS is exported only to the local machine.
>
> Nothing is “shared” between hosts. But because I want to export VMs, we use 
> “shared” storage in oVirt instead of “local”.

I think you can use nfs export storage domains also in a local-storage DC.

>
> Best,
>
> --
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124
> F: +352 46 66 44 6949
> http://www.uni.lu/lcsb
>
>
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the 
> original message and any copies.
> 
>
>
>
>> On 06 Sep 2016, at 10:06, Yedidyah Bar David  wrote:
>>
>> On Tue, Sep 6, 2016 at 9:53 AM, Christophe TREFOIS
>>  wrote:
>>> Personally my use case is that I have 4 machines with different specs and 
>>> storage sizing. So I setup four DC with 1 host each. Then I have hosted 
>>> engine on one of the hosts. Storage is local shared via NFS so that I can 
>>> move VMs around.
>>
>> Not sure I fully understand.
>>
>> You use each of the 4 machines for both storage and running VMs?
>> And export nfs on each to all the others?
>>
>> So that if a VM needs more CPU/memory then disk IO, you can move
>> it to another machine and hopefully get better performance even
>> though the storage is not local?
>>
>> I admit that it sounds very reasonable, and agree that doing this
>> with nfs is easier than with iSCSI. If you don't mind the risk of
>> local-nfs-mount locks, fine. As others noted, seems like it's quite
>> a low risk.
>>
>>>
>>> At this point we are not interested necessarily in HA.
>>>
>>> Maybe for you that's the definition of a Dev environment as production has 
>>> other attributes than just the type of storage?
>>
>> Dev or Prod is for you to define :-)
>>
>> How much time/money do you loose if a machine dies? If a machine
>> locks up until someone notices and handles?
>>
>>>
>>> Would be nice to hear your thoughts about this.
>>
>> As wrote above, sounds reasonable if you understand the risks
>> and can live with them.
>>
>> Looking at the future you might want to check HC:
>>
>> https://www.ovirt.org/develop/release-management/features/gluster/glusterfs-hyperconvergence/
>>
>>>
>>> Kind regards,
>>> Christophe
>>>
>>> Sent from my iPhone
>>>
 On 06 Sep 2016, at 08:45, Yedidyah Bar David  wrote:

 On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
  wrote:
> So basically we need at least 2 nodes to enter the realm of testing and 
> maintained?

 I think some people occasionally use hosted-engine with local
 iSCSI storage on a single machine. AFAIK it's not tested by CI
 or often, but patches are welcome - e.g. using lago and
 ovirt-system-tests.

 Can you please explain your intentions/requirements?

 Even if it works, oVirt is not designed for single-machine
 _production_ use. For that, I think that most people agree that
 virt-manager is more suitable. oVirt on a single machine is
 usually for testing/demonstration/learning/etc.

>
> If we’re talking pure oVirt here.
>
> --
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124
> F: +352 46 66 44 6949
> http://www.uni.lu/lcsb
>
>
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the 
> original message and any copies.
> 
>
>
>
>> On 05 Sep 2016, at 16:31, Fernando Frediani 
>>  wrote:
>>
>> Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
>> pretty useful for many situations and doesn't need such thing like 
>> mounting NFS in localhost.
>>
>> It is not nice to not have a All-in-One stable solution anymore as this 
>> can help with its adoption for later growth.
>>
>> oVirt-Cockpit looks nice and intresting.
>>
>> Fernando
>>
>>
>>> On 05/09/2016 05:18, Barak Korren wrote:
 On 4 September 2016 at 23:45, zero four  wrote:
 ...
 I understand and acknowledge that oVirt is not targeted towards homelab
 setups, 

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

[Christophe TREFOIS]

Hi,

No, I move VMs around with an Export Storage domain. 

All NFS is exported only to the local machine.

Nothing is “shared” between hosts. But because I want to export VMs, we use 
“shared” storage in oVirt instead of “local”.

Best,

-- 

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
http://www.uni.lu/lcsb




This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  

> On 06 Sep 2016, at 10:06, Yedidyah Bar David  wrote:
> 
> On Tue, Sep 6, 2016 at 9:53 AM, Christophe TREFOIS
>  wrote:
>> Personally my use case is that I have 4 machines with different specs and 
>> storage sizing. So I setup four DC with 1 host each. Then I have hosted 
>> engine on one of the hosts. Storage is local shared via NFS so that I can 
>> move VMs around.
> 
> Not sure I fully understand.
> 
> You use each of the 4 machines for both storage and running VMs?
> And export nfs on each to all the others?
> 
> So that if a VM needs more CPU/memory then disk IO, you can move
> it to another machine and hopefully get better performance even
> though the storage is not local?
> 
> I admit that it sounds very reasonable, and agree that doing this
> with nfs is easier than with iSCSI. If you don't mind the risk of
> local-nfs-mount locks, fine. As others noted, seems like it's quite
> a low risk.
> 
>> 
>> At this point we are not interested necessarily in HA.
>> 
>> Maybe for you that's the definition of a Dev environment as production has 
>> other attributes than just the type of storage?
> 
> Dev or Prod is for you to define :-)
> 
> How much time/money do you loose if a machine dies? If a machine
> locks up until someone notices and handles?
> 
>> 
>> Would be nice to hear your thoughts about this.
> 
> As wrote above, sounds reasonable if you understand the risks
> and can live with them.
> 
> Looking at the future you might want to check HC:
> 
> https://www.ovirt.org/develop/release-management/features/gluster/glusterfs-hyperconvergence/
> 
>> 
>> Kind regards,
>> Christophe
>> 
>> Sent from my iPhone
>> 
>>> On 06 Sep 2016, at 08:45, Yedidyah Bar David  wrote:
>>> 
>>> On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
>>>  wrote:
 So basically we need at least 2 nodes to enter the realm of testing and 
 maintained?
>>> 
>>> I think some people occasionally use hosted-engine with local
>>> iSCSI storage on a single machine. AFAIK it's not tested by CI
>>> or often, but patches are welcome - e.g. using lago and
>>> ovirt-system-tests.
>>> 
>>> Can you please explain your intentions/requirements?
>>> 
>>> Even if it works, oVirt is not designed for single-machine
>>> _production_ use. For that, I think that most people agree that
>>> virt-manager is more suitable. oVirt on a single machine is
>>> usually for testing/demonstration/learning/etc.
>>> 
 
 If we’re talking pure oVirt here.
 
 --
 
 Dr Christophe Trefois, Dipl.-Ing.
 Technical Specialist / Post-Doc
 
 UNIVERSITÉ DU LUXEMBOURG
 
 LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
 Campus Belval | House of Biomedicine
 6, avenue du Swing
 L-4367 Belvaux
 T: +352 46 66 44 6124
 F: +352 46 66 44 6949
 http://www.uni.lu/lcsb
 
 
 
 
 This message is confidential and may contain privileged information.
 It is intended for the named recipient only.
 If you receive it in error please notify me and permanently delete the 
 original message and any copies.
 
 
 
 
> On 05 Sep 2016, at 16:31, Fernando Frediani 
>  wrote:
> 
> Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
> pretty useful for many situations and doesn't need such thing like 
> mounting NFS in localhost.
> 
> It is not nice to not have a All-in-One stable solution anymore as this 
> can help with its adoption for later growth.
> 
> oVirt-Cockpit looks nice and intresting.
> 
> Fernando
> 
> 
>> On 05/09/2016 05:18, Barak Korren wrote:
>>> On 4 September 2016 at 23:45, zero four  wrote:
>>> ...
>>> 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.
>> As others have already mentioned, using the full oVirt  with engine in
>> a single 

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

[Yedidyah Bar David]

On Tue, Sep 6, 2016 at 9:53 AM, Christophe TREFOIS
 wrote:
> Personally my use case is that I have 4 machines with different specs and 
> storage sizing. So I setup four DC with 1 host each. Then I have hosted 
> engine on one of the hosts. Storage is local shared via NFS so that I can 
> move VMs around.

Not sure I fully understand.

You use each of the 4 machines for both storage and running VMs?
And export nfs on each to all the others?

So that if a VM needs more CPU/memory then disk IO, you can move
it to another machine and hopefully get better performance even
though the storage is not local?

I admit that it sounds very reasonable, and agree that doing this
with nfs is easier than with iSCSI. If you don't mind the risk of
local-nfs-mount locks, fine. As others noted, seems like it's quite
a low risk.

>
> At this point we are not interested necessarily in HA.
>
> Maybe for you that's the definition of a Dev environment as production has 
> other attributes than just the type of storage?

Dev or Prod is for you to define :-)

How much time/money do you loose if a machine dies? If a machine
locks up until someone notices and handles?

>
> Would be nice to hear your thoughts about this.

As wrote above, sounds reasonable if you understand the risks
and can live with them.

Looking at the future you might want to check HC:

https://www.ovirt.org/develop/release-management/features/gluster/glusterfs-hyperconvergence/

>
> Kind regards,
> Christophe
>
> Sent from my iPhone
>
>> On 06 Sep 2016, at 08:45, Yedidyah Bar David  wrote:
>>
>> On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
>>  wrote:
>>> So basically we need at least 2 nodes to enter the realm of testing and 
>>> maintained?
>>
>> I think some people occasionally use hosted-engine with local
>> iSCSI storage on a single machine. AFAIK it's not tested by CI
>> or often, but patches are welcome - e.g. using lago and
>> ovirt-system-tests.
>>
>> Can you please explain your intentions/requirements?
>>
>> Even if it works, oVirt is not designed for single-machine
>> _production_ use. For that, I think that most people agree that
>> virt-manager is more suitable. oVirt on a single machine is
>> usually for testing/demonstration/learning/etc.
>>
>>>
>>> If we’re talking pure oVirt here.
>>>
>>> --
>>>
>>> Dr Christophe Trefois, Dipl.-Ing.
>>> Technical Specialist / Post-Doc
>>>
>>> UNIVERSITÉ DU LUXEMBOURG
>>>
>>> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>>> Campus Belval | House of Biomedicine
>>> 6, avenue du Swing
>>> L-4367 Belvaux
>>> T: +352 46 66 44 6124
>>> F: +352 46 66 44 6949
>>> http://www.uni.lu/lcsb
>>>
>>>
>>>
>>> 
>>> This message is confidential and may contain privileged information.
>>> It is intended for the named recipient only.
>>> If you receive it in error please notify me and permanently delete the 
>>> original message and any copies.
>>> 
>>>
>>>
>>>
 On 05 Sep 2016, at 16:31, Fernando Frediani  
 wrote:

 Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
 pretty useful for many situations and doesn't need such thing like 
 mounting NFS in localhost.

 It is not nice to not have a All-in-One stable solution anymore as this 
 can help with its adoption for later growth.

 oVirt-Cockpit looks nice and intresting.

 Fernando


> On 05/09/2016 05:18, Barak Korren wrote:
>> On 4 September 2016 at 23:45, zero four  wrote:
>> ...
>> 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.
> As others have already mentioned, using the full oVirt  with engine in
> a single host scenario can work, but is not currently actively
> maintained or tested.
>
> There are other options originating from the oVirt community however.
>
> One notable option is to use the Cockpit-oVirt plugin [1] which can
> use VDSM to manage VMs on a single host.
>
> Another option is to use the Kimchi project [2] for which discussion
> for making it an oVirt project had taken part in the past [3]. It
> seems that also some work for inclusion in oVirt node was also planned
> at some point [4].
>
> [1]: http://www.ovirt.org/develop/release-management/features/cockpit/
> [2]: https://github.com/kimchi-project/kimchi
> [3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
> [4]: 
> http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/

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

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

[Barak Korren]

On 6 September 2016 at 00:34, Christophe TREFOIS
 wrote:
> So basically we need at least 2 nodes to enter the realm of testing and 
> maintained?
>
> If we’re talking pure oVirt here.

The short answer is yes.

The longer answer is more complex, but first a disclaimer, I'm am
going to describe the situation as I am aware of it, from my point of
view is a Red Hat employee and a member of the oVirt infra team. I'm
an probably not knowledgeable about everything that goes on, for
example there is a fairly large Chinese oVirt community that commits
various efforts of which I know very little.

When I'm taking testing and maintenance, I think we can agree that for
something to be maintained it needs to meet to following criteria:
1. It needs to be tested at least once for every oVirt release
2. Results of that testing need to make their way to the hands of developers.
   Malfunctions should end up as bugs tracked in Bugzilla.

Probably the largest group that does regular testing for oVirt is the
quality engineering group in Red Hat. Red Hat puts a great deal of
resources into oVirt, but those resources are not infinite. And when
the time comes to schedule resources, the needs of paying Red Hat
customers typically come first. Those customers are probably more
likely to be running large data centers.

Another set of regular testing is being done automatically by the
oVirt CI systems. Those tests [1] use Lago [2] to run testing suits
that simulate various situations for oVirt to run in. The smallest
configuration currently tested that way is a 2-node hosted engine
configuration. As all those tests have been written by Red Hat
employees, they tend to focus on what ends up going into RHEV.

It it important to note that not every oVirt feature ends up in RHEV,
but that does not mean that that feature never gets tested. There are
several oVirt features that are very useful for building oVirt-based
testing systems for oVirt itself and as a result get regular testing
as well. Notable examples are nested virtualization and the Glance
support.

The above being said, there is nothing preventing anyone in the
community from creating a test suit for single-host use that will get
run regularly by the oVirt CI system. That kind of effort will require
some degree of commitment to make it work, fix it when it inevitably
breaks, and report what it finds to the developers. There are already
existing tools in the oVirt repos that make building such a test suit
quite straight forward. I will be happy to guid anyone interested in
taking such an effort.

[1]: http://lago.readthedocs.io/en/stable/
[2]: https://gerrit.ovirt.org/#/admin/projects/ovirt-system-tests

-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Christophe TREFOIS]

Personally my use case is that I have 4 machines with different specs and 
storage sizing. So I setup four DC with 1 host each. Then I have hosted engine 
on one of the hosts. Storage is local shared via NFS so that I can move VMs 
around.

At this point we are not interested necessarily in HA.

Maybe for you that's the definition of a Dev environment as production has 
other attributes than just the type of storage?

Would be nice to hear your thoughts about this.

Kind regards,
Christophe 

Sent from my iPhone

> On 06 Sep 2016, at 08:45, Yedidyah Bar David  wrote:
> 
> On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
>  wrote:
>> So basically we need at least 2 nodes to enter the realm of testing and 
>> maintained?
> 
> I think some people occasionally use hosted-engine with local
> iSCSI storage on a single machine. AFAIK it's not tested by CI
> or often, but patches are welcome - e.g. using lago and
> ovirt-system-tests.
> 
> Can you please explain your intentions/requirements?
> 
> Even if it works, oVirt is not designed for single-machine
> _production_ use. For that, I think that most people agree that
> virt-manager is more suitable. oVirt on a single machine is
> usually for testing/demonstration/learning/etc.
> 
>> 
>> If we’re talking pure oVirt here.
>> 
>> --
>> 
>> Dr Christophe Trefois, Dipl.-Ing.
>> Technical Specialist / Post-Doc
>> 
>> UNIVERSITÉ DU LUXEMBOURG
>> 
>> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
>> Campus Belval | House of Biomedicine
>> 6, avenue du Swing
>> L-4367 Belvaux
>> T: +352 46 66 44 6124
>> F: +352 46 66 44 6949
>> http://www.uni.lu/lcsb
>> 
>> 
>> 
>> 
>> This message is confidential and may contain privileged information.
>> It is intended for the named recipient only.
>> If you receive it in error please notify me and permanently delete the 
>> original message and any copies.
>> 
>> 
>> 
>> 
>>> On 05 Sep 2016, at 16:31, Fernando Frediani  
>>> wrote:
>>> 
>>> Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
>>> pretty useful for many situations and doesn't need such thing like mounting 
>>> NFS in localhost.
>>> 
>>> It is not nice to not have a All-in-One stable solution anymore as this can 
>>> help with its adoption for later growth.
>>> 
>>> oVirt-Cockpit looks nice and intresting.
>>> 
>>> Fernando
>>> 
>>> 
 On 05/09/2016 05:18, Barak Korren wrote:
> On 4 September 2016 at 23:45, zero four  wrote:
> ...
> 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.
 As others have already mentioned, using the full oVirt  with engine in
 a single host scenario can work, but is not currently actively
 maintained or tested.
 
 There are other options originating from the oVirt community however.
 
 One notable option is to use the Cockpit-oVirt plugin [1] which can
 use VDSM to manage VMs on a single host.
 
 Another option is to use the Kimchi project [2] for which discussion
 for making it an oVirt project had taken part in the past [3]. It
 seems that also some work for inclusion in oVirt node was also planned
 at some point [4].
 
 [1]: http://www.ovirt.org/develop/release-management/features/cockpit/
 [2]: https://github.com/kimchi-project/kimchi
 [3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
 [4]: 
 http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/
>>> 
>>> ___
>>> 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
> 
> 
> 
> -- 
> Didi


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

[Yedidyah Bar David]

On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
 wrote:
> So basically we need at least 2 nodes to enter the realm of testing and 
> maintained?

I think some people occasionally use hosted-engine with local
iSCSI storage on a single machine. AFAIK it's not tested by CI
or often, but patches are welcome - e.g. using lago and
ovirt-system-tests.

Can you please explain your intentions/requirements?

Even if it works, oVirt is not designed for single-machine
_production_ use. For that, I think that most people agree that
virt-manager is more suitable. oVirt on a single machine is
usually for testing/demonstration/learning/etc.

>
> If we’re talking pure oVirt here.
>
> --
>
> Dr Christophe Trefois, Dipl.-Ing.
> Technical Specialist / Post-Doc
>
> UNIVERSITÉ DU LUXEMBOURG
>
> LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
> Campus Belval | House of Biomedicine
> 6, avenue du Swing
> L-4367 Belvaux
> T: +352 46 66 44 6124
> F: +352 46 66 44 6949
> http://www.uni.lu/lcsb
>
>
>
> 
> This message is confidential and may contain privileged information.
> It is intended for the named recipient only.
> If you receive it in error please notify me and permanently delete the 
> original message and any copies.
> 
>
>
>
>> On 05 Sep 2016, at 16:31, Fernando Frediani  
>> wrote:
>>
>> Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
>> pretty useful for many situations and doesn't need such thing like mounting 
>> NFS in localhost.
>>
>> It is not nice to not have a All-in-One stable solution anymore as this can 
>> help with its adoption for later growth.
>>
>> oVirt-Cockpit looks nice and intresting.
>>
>> Fernando
>>
>>
>> On 05/09/2016 05:18, Barak Korren wrote:
>>> On 4 September 2016 at 23:45, zero four  wrote:
>>> ...
 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.
>>> As others have already mentioned, using the full oVirt  with engine in
>>> a single host scenario can work, but is not currently actively
>>> maintained or tested.
>>>
>>> There are other options originating from the oVirt community however.
>>>
>>> One notable option is to use the Cockpit-oVirt plugin [1] which can
>>> use VDSM to manage VMs on a single host.
>>>
>>> Another option is to use the Kimchi project [2] for which discussion
>>> for making it an oVirt project had taken part in the past [3]. It
>>> seems that also some work for inclusion in oVirt node was also planned
>>> at some point [4].
>>>
>>> [1]: http://www.ovirt.org/develop/release-management/features/cockpit/
>>> [2]: https://github.com/kimchi-project/kimchi
>>> [3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
>>> [4]: 
>>> http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/
>>>
>>
>> ___
>> 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



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

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

[Christophe TREFOIS]

So basically we need at least 2 nodes to enter the realm of testing and 
maintained?

If we’re talking pure oVirt here.

-- 

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
http://www.uni.lu/lcsb




This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  

> On 05 Sep 2016, at 16:31, Fernando Frediani  
> wrote:
> 
> Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
> pretty useful for many situations and doesn't need such thing like mounting 
> NFS in localhost.
> 
> It is not nice to not have a All-in-One stable solution anymore as this can 
> help with its adoption for later growth.
> 
> oVirt-Cockpit looks nice and intresting.
> 
> Fernando
> 
> 
> On 05/09/2016 05:18, Barak Korren wrote:
>> On 4 September 2016 at 23:45, zero four  wrote:
>> ...
>>> 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.
>> As others have already mentioned, using the full oVirt  with engine in
>> a single host scenario can work, but is not currently actively
>> maintained or tested.
>> 
>> There are other options originating from the oVirt community however.
>> 
>> One notable option is to use the Cockpit-oVirt plugin [1] which can
>> use VDSM to manage VMs on a single host.
>> 
>> Another option is to use the Kimchi project [2] for which discussion
>> for making it an oVirt project had taken part in the past [3]. It
>> seems that also some work for inclusion in oVirt node was also planned
>> at some point [4].
>> 
>> [1]: http://www.ovirt.org/develop/release-management/features/cockpit/
>> [2]: https://github.com/kimchi-project/kimchi
>> [3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
>> [4]: 
>> http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/
>> 
> 
> ___
> 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 on a single server

[Fernando Frediani]

Adding Kimchi to oVirt node perhaps may be the easiest option. It can be 
pretty useful for many situations and doesn't need such thing like 
mounting NFS in localhost.


It is not nice to not have a All-in-One stable solution anymore as this 
can help with its adoption for later growth.


oVirt-Cockpit looks nice and intresting.

Fernando


On 05/09/2016 05:18, Barak Korren wrote:

On 4 September 2016 at 23:45, zero four  wrote:
...

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.

As others have already mentioned, using the full oVirt  with engine in
a single host scenario can work, but is not currently actively
maintained or tested.

There are other options originating from the oVirt community however.

One notable option is to use the Cockpit-oVirt plugin [1] which can
use VDSM to manage VMs on a single host.

Another option is to use the Kimchi project [2] for which discussion
for making it an oVirt project had taken part in the past [3]. It
seems that also some work for inclusion in oVirt node was also planned
at some point [4].

[1]: http://www.ovirt.org/develop/release-management/features/cockpit/
[2]: https://github.com/kimchi-project/kimchi
[3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
[4]: http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/



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

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

[Barak Korren]

On 4 September 2016 at 23:45, zero four  wrote:
...
> 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.

As others have already mentioned, using the full oVirt  with engine in
a single host scenario can work, but is not currently actively
maintained or tested.

There are other options originating from the oVirt community however.

One notable option is to use the Cockpit-oVirt plugin [1] which can
use VDSM to manage VMs on a single host.

Another option is to use the Kimchi project [2] for which discussion
for making it an oVirt project had taken part in the past [3]. It
seems that also some work for inclusion in oVirt node was also planned
at some point [4].

[1]: http://www.ovirt.org/develop/release-management/features/cockpit/
[2]: https://github.com/kimchi-project/kimchi
[3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
[4]: http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/

-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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 <christophe.tref...@uni.lu> 
> 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] 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

[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