[ovirt-users] Re: 2021 first ovirt network question

[Gilboa Davara]

Sadly enough we never had more than 20+ concurrent spice connections and
most of them were text consoles. In this case, our 40/10GbE link(s) were
mostly idle.
That said, there's a vast difference between spice displaying VGA
resolution and spice displaying 2K/4K resolution.
Hence my question about the type of VMs and by extension, the resolution
used.

BTW, stupid question: Have you tried running iperf3 (or a similar tool)
between your client machines and the oVirt cluster to verify that indeed
you have 10GbE of usable bandwith?

- Gilboa

On Wed, Jan 6, 2021 at 10:58 AM  wrote:

> Concurrent spice connection.
> Today 75 VM i exist and all use spice connection
>
> Thanks for your interest
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MIXL57E6XTRLUFPZC2OKLVTMDET7XQBV/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HDKCLTPZ2F2O3HJZXIWPIKUGHUKCHZPP/

[ovirt-users] Re: Spliting login pages

[Strahil Nikolov via Users]

Sharon , what about a nginx/apache listening on different virtual hosts
and redirecting (actually proxying) to the correct portal ?
Do you think that it could work  (the certs will not be trusted, but
they can take the exception) ?
Best Regards,Strahil Nikolov
В 17:24 +0200 на 06.01.2021 (ср), Sharon Gratch написа:
> 
> On Wed, Jan 6, 2021 at 11:15 AM  wrote:
> > Hi,
> > 
> > Yes, we can.
> > 
> > But we want to separate them by FQDN
> > 
> > for example;
> > 
> > http:/virtualpc.example.com --> VM Portal
> > 
> > http:/virtualpc-admin.example.com --> Admin Portal
> > 
> > http:/virtualpc-grafana.example.com --> Grafana Portal
> 
> AFAIK this is not supported by oVirt since all should use the engine
> FQDN for accessing the engine.
> You can probably use your own customized URL redirection or set a few
> FQDNs, but It won't solve the problem for separating and it might
> cause other issues, so I won't recommend it.
> 
> > 
> > and normal user must don't have permission access to admin or
> > grafana portal web page
> 
> Sure, so login will fail if a regular user won't have permissions to
> login to webadmin or grafana. This deals with user permissions
> management that should be set correctly. It's not related to FQDNs...
> > ___
> > 
> > Users mailing list -- users@ovirt.org
> > 
> > To unsubscribe send an email to users-le...@ovirt.org
> > 
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > 
> > oVirt Code of Conduct: 
> > https://www.ovirt.org/community/about/community-guidelines/
> > 
> > List Archives: 
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/2J7GQ6ZDXQMGZ3USBJM7HYP5W3JRJLV5/
> > 
> 
> ___Users mailing list -- 
> users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VS4QUWCNVXDL7J623EZPFEZUFO7IUMGQ/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BO5LT7L4U5OC7O57TQFLW65LZLDWWXFE/

[ovirt-users] Re: Spliting login pages

[Sharon Gratch]

On Wed, Jan 6, 2021 at 11:15 AM  wrote:

> Hi,
> Yes, we can.
> But we want to separate them by FQDN
> for example;
> http:/virtualpc.example.com --> VM Portal
> http:/virtualpc-admin.example.com --> Admin Portal
> http:/virtualpc-grafana.example.com --> Grafana Portal
>

AFAIK this is not supported by oVirt since all should use the engine FQDN
for accessing the engine.
You can probably use your own customized URL redirection or set a few
FQDNs, but It won't solve the problem for separating and it might cause
other issues, so I won't recommend it.


> and normal user must don't have permission access to admin or grafana
> portal web page
>

Sure, so login will fail if a regular user won't have permissions to login
to webadmin or grafana. This deals with user permissions management that
should be set correctly. It's not related to FQDNs...

___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2J7GQ6ZDXQMGZ3USBJM7HYP5W3JRJLV5/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VS4QUWCNVXDL7J623EZPFEZUFO7IUMGQ/

[ovirt-users] Re: Hosts are non responsive Ovirt 3.6

[Yedidyah Bar David]

On Wed, Jan 6, 2021 at 5:01 PM Gary Lloyd  wrote:
>
> I ended up cheating in the end.
> I copied vdsmcert.pem and vdsmkey.pem from the host that is still working to 
> the others and did a chown on the files.
> All the hosts are back online without downtime. I must have rebuilt that 
> server a couple of years after the other ones.

Nice hack! :-)

Please note that you take a risk here. The cert includes the hostname,
and now it's not matching the hostname that the client (the engine, in
this case, or another host, e.g. for VM migration) expects. So if some
piece of software checks this, it might fail. Personally, I wouldn't
stay in this state for long.

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OBHFI7Z7L333PFQ6CPHCWHSFVMC3YHZU/

[ovirt-users] Re: Hosts are non responsive Ovirt 3.6

[Gary Lloyd]

I ended up cheating in the end.
I copied vdsmcert.pem and vdsmkey.pem from the host that is still working to 
the others and did a chown on the files.
All the hosts are back online without downtime. I must have rebuilt that server 
a couple of years after the other ones.

Thanks

Gary Lloyd 
IT Infrastructure Manager 
Information and Digital Services 
01782 733063 
Innovation Centre 2 | Keele University | ST5 5NH 
  

-Original Message-
From: Strahil Nikolov  
Sent: 06 January 2021 12:11
To: Gary Lloyd 
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Hosts are non responsive Ovirt 3.6

Have you tried to put a host into maintenance, remove and then readd it ?

You can access all Red Hat solutions with their free developer subscription.



Best Regards,
Strahil Nikolov






В сряда, 6 януари 2021 г., 13:17:42 Гринуич+2, Gary Lloyd  
написа: 





  


Hi please could someone point me in the right direction to renew ssl 
certificates for vdsm to communicate with ovirt 3.6 ?

I’m aware that this version hasn’t been supported for some time, this is a 
legacy environment which we are working towards decommissioning.

 

There seems to be a fix article for RHEV but we don’t have a subscription to 
view this information:

How to update expired RHEV certificates when all RHEV hosts got 
'Non-responsive' - Red Hat Customer Portal

 

These are what the vdsm hosts are showing:

Reactor thread::ERROR::2021-01-06 
11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
 Error during handshake: sslv3 alert certificate expired

 

I have rerun engine-setup but this only seems to have fixed one of the vdsm 
hosts and the others are non responsive.

The others are in different clusters and we have some important services still 
running on these. 

 

Thanks

  

  
  


Gary Lloyd 
  
IT Infrastructure Manager 
  
Information and Digital Services 
  
01782 733063 
  
Innovation Centre 2 | Keele University | ST5 5NH 
  


  

 



___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HT6Z3WHPFTBIVKQYQZBZEXHSO24LPKVS/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EYI5L6Q3QJICSUNVXHDVTMRCLMIH5II3/

[ovirt-users] Re: Ovirt and Vagrant

[Gervais de Montbrun]

I saw that yesterday!

Thanks for the help guys. I'm not a Ruby programmer, so have been poking at 
this on and off for weeks. It looks like the two most recent PR's may have 
solved my two most apparent problems with the plugin.

I want to test more functionality with vagrant (like suspend, halt, resume, 
etc), but 🤞we are fully on track again.

Cheers,
Gervais



> On Jan 6, 2021, at 8:18 AM, Staniforth, Paul 
>  wrote:
> 
> Hello Gervais,
>   update from our developers
> 
> I've just checked the email chain, and it looks like it has since been fixed 
> up stream (https://github.com/myoung34/vagrant-ovirt4/pull/121 
> )
>  but perhaps not included in any gem release yet...
> 
> Regards,
> Paul S.
> From: Staniforth, Paul  >
> Sent: 06 January 2021 10:59
> To: Gervais de Montbrun  >; users@ovirt.org  
> mailto:users@ovirt.org>>
> Subject: Re: [ovirt-users] Ovirt and Vagrant
>  
> Hello Gervais,
>  I have asked our developers who use the plugin and 
> here is the response.
> Regards, 
>  
> Paul S.
> 
> Hi Paul,
> 
> We have had to maintain our own changes to the oVirt Vagrant plugin. Probably 
> we need to start committing to and publishing our own fork.
> 
> Theres an obtuse and broken long one liner that get's the IP addresses, which 
> has always been a bit problematic, and stopped working altogether with the 
> newest release of oVirt we are using.
> 
> Anyway, here are the changes we made to get the IP addresses working with the 
> new versions of oVirt:
> 
> line 58 wait_till_up.rb
>   ip_addr = nil
>   vm_nics_service = server.nics_service
>   nics = vm_nics_service.list
>   nics.each { |nic|
> puts "Waiting on #{nic.mac.address}"
> vm_nics_service.nic_service(nic.id 
> ).reported_devices_service.list.each { |device|
>   device.ips&.each {|ip|
> puts "ip: #{ip.to_s}"
> if ip && ip.version == 'v4' && ip.address
>   ip_addr = ip.address
>   break
> end
>   }
> }
>   }
> 
> Also same in read_ssh.rb:
>  ip_addr = nil
>   vm_nics_service = server.nics_service
>   nics = vm_nics_service.list
>   nics.each { |nic|
> vm_nics_service.nic_service(nic.id 
> ).reported_devices_service.list.each { |device|
>   device.ips&.each {|ip|
> if ip && ip.version == 'v4' && ip.address
>   ip_addr = ip.address
>   break
> end
>   }
> }
>   }
> Sorry it's not the best way to share code, but feel free to pass this along.
> 
> Cheers,
> Cliffe.
> 
> 
> .
> 
> From: Gervais de Montbrun  >
> Sent: 04 January 2021 18:14
> To: users@ovirt.org   >
> Subject: [ovirt-users] Ovirt and Vagrant
>  
> Caution External Mail: Do not click any links or open any attachments unless 
> you trust the sender and know that the content is safe.
> Anyone using vagrant with oVirt 4.4?
> 
> I am trying to get the vagrant plugin working with oVirt, but I am 
> experiencing issues. https://github.com/myoung34/vagrant-ovirt4/issues/120 
> 
> I wonder what other folks are using or if someone has any suggestions to 
> offer.
> 
> We are trying to switch from vSphere to oVirt for internal, developer vm's at 
> my office and we have a successful workflow using vagrant-vsphere plugin. 
> Switching to oVirt should have been a simple step, but the issue I an having 
> is a blocker.
> 
> I built a single hyperconverged server to test with. Everything seems to work 
> fine when I bring up vm's manually in my "cluster." Networking, console, etc 
> all work fine. Ovirt-guest-additions work fine and display the vm's ip in the 
> gui.
> 
> When I try with the vagrant p

[ovirt-users] Re: Ovirt and Vagrant

[Staniforth, Paul]

Hello Gervais,
  update from our developers

I've just checked the email chain, and it looks like it has since been fixed up 
stream 
(https://github.com/myoung34/vagrant-ovirt4/pull/121)
 but perhaps not included in any gem release yet...

Regards,
Paul S.

From: Staniforth, Paul 
Sent: 06 January 2021 10:59
To: Gervais de Montbrun ; users@ovirt.org 

Subject: Re: [ovirt-users] Ovirt and Vagrant

Hello Gervais,
 I have asked our developers who use the plugin and 
here is the response.
Regards,

Paul S.

Hi Paul,

We have had to maintain our own changes to the oVirt Vagrant plugin. Probably 
we need to start committing to and publishing our own fork.

Theres an obtuse and broken long one liner that get's the IP addresses, which 
has always been a bit problematic, and stopped working altogether with the 
newest release of oVirt we are using.

Anyway, here are the changes we made to get the IP addresses working with the 
new versions of oVirt:

line 58 wait_till_up.rb
  ip_addr = nil
  vm_nics_service = server.nics_service
  nics = vm_nics_service.list
  nics.each { |nic|
puts "Waiting on #{nic.mac.address}"

vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { 
|device|
  device.ips&.each {|ip|
puts "ip: #{ip.to_s}"
if ip && ip.version == 'v4' && ip.address
  ip_addr = ip.address
  break
end
  }
}
  }

Also same in read_ssh.rb:
 ip_addr = nil
  vm_nics_service = server.nics_service
  nics = vm_nics_service.list
  nics.each { |nic|

vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { 
|device|
  device.ips&.each {|ip|
if ip && ip.version == 'v4' && ip.address
  ip_addr = ip.address
  break
end
  }
}
  }
Sorry it's not the best way to share code, but feel free to pass this along.

Cheers,
Cliffe.


.


From: Gervais de Montbrun 
Sent: 04 January 2021 18:14
To: users@ovirt.org 
Subject: [ovirt-users] Ovirt and Vagrant


Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

Anyone using vagrant with oVirt 4.4?

I am trying to get the vagrant plugin working with oVirt, but I am experiencing 
issues. 
https://github.com/myoung34/vagrant-ovirt4/issues/120
I wonder what other folks are using or if someone has any suggestions to offer.

We are trying to switch from vSphere to oVirt for internal, developer vm's at 
my office and we have a successful workflow using vagrant-vsphere plugin. 
Switching to oVirt should have been a simple step, but the issue I an having is 
a blocker.

I built a single hyperconverged server to test with. Everything seems to work 
fine when I bring up vm's manually in my "cluster." Networking, console, etc 
all work fine. Ovirt-guest-additions work fine and display the vm's ip in the 
gui.

When I try with the vagrant plugin, there seems to be a communication issue. 
Even though I can see the vm reporting its IP address fine in the ovirt web 
gui, it seems like the vagrant plugin is unable to do the same. The maintainer 
of the code says that he no longer runs oVirt which is why I am reaching out 
here to see if anyone has a suggestion or even an alternative to suggest.

Cheers,
Gervais



To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovi

[ovirt-users] Re: Hosts are non responsive Ovirt 3.6

[Strahil Nikolov via Users]

Have you tried to put a host into maintenance, remove and then readd it ?

You can access all Red Hat solutions with their free developer subscription.



Best Regards,
Strahil Nikolov






В сряда, 6 януари 2021 г., 13:17:42 Гринуич+2, Gary Lloyd  
написа: 





  


Hi please could someone point me in the right direction to renew ssl 
certificates for vdsm to communicate with ovirt 3.6 ?

I’m aware that this version hasn’t been supported for some time, this is a 
legacy environment which we are working towards decommissioning.

 

There seems to be a fix article for RHEV but we don’t have a subscription to 
view this information:

How to update expired RHEV certificates when all RHEV hosts got 
'Non-responsive' - Red Hat Customer Portal

 

These are what the vdsm hosts are showing:

Reactor thread::ERROR::2021-01-06 
11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
 Error during handshake: sslv3 alert certificate expired

 

I have rerun engine-setup but this only seems to have fixed one of the vdsm 
hosts and the others are non responsive.

The others are in different clusters and we have some important services still 
running on these. 

 

Thanks

  

  
  


Gary Lloyd 
  
IT Infrastructure Manager 
  
Information and Digital Services 
  
01782 733063 
  
Innovation Centre 2 | Keele University | ST5 5NH 
  


  

 



___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HT6Z3WHPFTBIVKQYQZBZEXHSO24LPKVS/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ROKPGJAM2TFAYFQPA6SGJTHJ5KP73INJ/

[ovirt-users] Re: Hosts are non responsive Ovirt 3.6

[Yedidyah Bar David]

On Wed, Jan 6, 2021 at 1:17 PM Gary Lloyd  wrote:

> Hi please could someone point me in the right direction to renew ssl
> certificates for vdsm to communicate with ovirt 3.6 ?
>
> I’m aware that this version hasn’t been supported for some time, this is a
> legacy environment which we are working towards decommissioning.
>
>
>
> There seems to be a fix article for RHEV but we don’t have a subscription
> to view this information:
>
> How to update expired RHEV certificates when all RHEV hosts got
> 'Non-responsive' - Red Hat Customer Portal
> 
>
>
>
> These are what the vdsm hosts are showing:
>
> Reactor thread::ERROR::2021-01-06
> 11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
> Error during handshake: sslv3 alert certificate expired
>
>
>
> I have rerun engine-setup but this only seems to have fixed one of the
> vdsm hosts and the others are non responsive.
>
> The others are in different clusters and we have some important services
> still running on these.
>

The "canonical" way is to "Reinstall" or "Enroll Certificates".

I think this will require stopping all VMs on them.

Good luck and best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/V4YYXCWTHP2UJ34MNUOSMXNAMXXIHGV2/

[ovirt-users] Hosts are non responsive Ovirt 3.6

[Gary Lloyd]

Hi please could someone point me in the right direction to renew ssl 
certificates for vdsm to communicate with ovirt 3.6 ?
I'm aware that this version hasn't been supported for some time, this is a 
legacy environment which we are working towards decommissioning.

There seems to be a fix article for RHEV but we don't have a subscription to 
view this information:
How to update expired RHEV certificates when all RHEV hosts got 
'Non-responsive' - Red Hat Customer 
Portal

These are what the vdsm hosts are showing:
Reactor thread::ERROR::2021-01-06 
11:04:59,505::m2cutils::337::ProtocolDetector.SSLHandshakeDispatcher::(handle_read)
 Error during handshake: sslv3 alert certificate expired

I have rerun engine-setup but this only seems to have fixed one of the vdsm 
hosts and the others are non responsive.
The others are in different clusters and we have some important services still 
running on these.

Thanks

[https://lh5.googleusercontent.com/v29r0Xyldsxb-jrbIFBAQIhyVvznLy4FvU0sxq6bMFnEIxeq8_6N-T7R9dqA9Hq_Zis1X732m0C1FE4piYQX_XyJN7nj3rTj1R4NBdpvqi12bqV-sVbVHNB7UT77_Yd5g8hQ5gYR]
Gary Lloyd
IT Infrastructure Manager
Information and Digital Services
01782 733063
Innovation Centre 2 | Keele University | ST5 5NH


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HT6Z3WHPFTBIVKQYQZBZEXHSO24LPKVS/

[ovirt-users] Re: Ovirt and Vagrant

[Staniforth, Paul]

Hello Gervais,
 I have asked our developers who use the plugin and 
here is the response.
Regards,

Paul S.

Hi Paul,

We have had to maintain our own changes to the oVirt Vagrant plugin. Probably 
we need to start committing to and publishing our own fork.

Theres an obtuse and broken long one liner that get's the IP addresses, which 
has always been a bit problematic, and stopped working altogether with the 
newest release of oVirt we are using.

Anyway, here are the changes we made to get the IP addresses working with the 
new versions of oVirt:

line 58 wait_till_up.rb
  ip_addr = nil
  vm_nics_service = server.nics_service
  nics = vm_nics_service.list
  nics.each { |nic|
puts "Waiting on #{nic.mac.address}"

vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { 
|device|
  device.ips&.each {|ip|
puts "ip: #{ip.to_s}"
if ip && ip.version == 'v4' && ip.address
  ip_addr = ip.address
  break
end
  }
}
  }

Also same in read_ssh.rb:
 ip_addr = nil
  vm_nics_service = server.nics_service
  nics = vm_nics_service.list
  nics.each { |nic|

vm_nics_service.nic_service(nic.id).reported_devices_service.list.each { 
|device|
  device.ips&.each {|ip|
if ip && ip.version == 'v4' && ip.address
  ip_addr = ip.address
  break
end
  }
}
  }
Sorry it's not the best way to share code, but feel free to pass this along.

Cheers,
Cliffe.


.


From: Gervais de Montbrun 
Sent: 04 January 2021 18:14
To: users@ovirt.org 
Subject: [ovirt-users] Ovirt and Vagrant


Caution External Mail: Do not click any links or open any attachments unless 
you trust the sender and know that the content is safe.

Anyone using vagrant with oVirt 4.4?

I am trying to get the vagrant plugin working with oVirt, but I am experiencing 
issues. 
https://github.com/myoung34/vagrant-ovirt4/issues/120
I wonder what other folks are using or if someone has any suggestions to offer.

We are trying to switch from vSphere to oVirt for internal, developer vm's at 
my office and we have a successful workflow using vagrant-vsphere plugin. 
Switching to oVirt should have been a simple step, but the issue I an having is 
a blocker.

I built a single hyperconverged server to test with. Everything seems to work 
fine when I bring up vm's manually in my "cluster." Networking, console, etc 
all work fine. Ovirt-guest-additions work fine and display the vm's ip in the 
gui.

When I try with the vagrant plugin, there seems to be a communication issue. 
Even though I can see the vm reporting its IP address fine in the ovirt web 
gui, it seems like the vagrant plugin is unable to do the same. The maintainer 
of the code says that he no longer runs oVirt which is why I am reaching out 
here to see if anyone has a suggestion or even an alternative to suggest.

Cheers,
Gervais



To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/K23F53QKWA4FXRQCD47CDQ322M5DJTEK/

[ovirt-users] Re: Spliting login pages

[ozmen62]

Hi,
Yes, we can.
But we want to separate them by FQDN
for example;
http:/virtualpc.example.com --> VM Portal
http:/virtualpc-admin.example.com --> Admin Portal
http:/virtualpc-grafana.example.com --> Grafana Portal

and normal user must don't have permission access to admin or grafana portal 
web page
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2J7GQ6ZDXQMGZ3USBJM7HYP5W3JRJLV5/

[ovirt-users] Re: 2021 first ovirt network question

[ozmen62]

Concurrent spice connection.
Today 75 VM i exist and all use spice connection

Thanks for your interest
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MIXL57E6XTRLUFPZC2OKLVTMDET7XQBV/

[ovirt-users] Re: How to install and configure the monitoring portal ?

[Yedidyah Bar David]

On Wed, Jan 6, 2021 at 10:17 AM tommy  wrote:
>
> You mean that : It's recommended to inst all VDSM and ovirt engine on 
> separate server ?

Either that, or use hosted-engine.

> Just like hosted engine ? In that way, the engine is installed on vm, and the 
> vdsm is installed on vm hosts.
>
> But, my env not using hosted-engine, I use the standalone mode. Can I 
> separate the VDSM and engine on the standalone mode ?

If you want to use oVirt on a single physical machine, and not use
hosted-engine, you have to create multiple separate VMs on it (using
e.g. virt-install/virt-manager) - one for the engine, one or more
others for hosts, perhaps one for storage, etc.

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DXATIYM37NFNLIF4TQTSUKP7NMVSYLUA/

[ovirt-users] Re: How to install and configure the monitoring portal ?

[tommy]

You mean that : It's recommended to inst all VDSM and ovirt engine on separate 
server ?
Just like hosted engine ? In that way, the engine is installed on vm, and the 
vdsm is installed on vm hosts.

But, my env not using hosted-engine, I use the standalone mode. Can I separate 
the VDSM and engine on the standalone mode ?






-Original Message-
From: ybard...@redhat.com  On Behalf Of Yedidyah Bar David
Sent: Wednesday, January 6, 2021 4:04 PM
To: tommy 
Cc: users 
Subject: Re: [ovirt-users] Re: How to install and configure the monitoring 
portal ?

On Wed, Jan 6, 2021 at 9:32 AM tommy  wrote:
>
> OK, I got it.
>
> But ,after I reconfig, I found that is VDSM.service status is not right.
>
> Is there any problem ?

Sorry, I have no idea.

You seem to run vdsm and engine on the same machine, right? This is called 
all-in-one, and is not supported (used to be, until 3.6, several years ago).

Generally speaking, it's likely due to one of two things that engine-setup 
might have done:

1. changed some configuration

2. updated some packages

You can check its log to see what it did.

>
>
>
>
> [root@ooengh1 ~]# systemctl status vdsmd.service ● vdsmd.service - 
> Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: start-limit) since Wed 2021-01-06 15:25:58 CST; 
> 2min 9s ago
>   Process: 10758 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 10723 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --pre-start (code=exited, status=1/FAILURE)
>
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop 
> Server Manager.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered 
> failed state.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, 
> scheduling restart.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server 
> Manager.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: start request repeated 
> too quickly for vdsmd.service Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: 
> Failed to start Virtual Desktop Server Manager.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered 
> failed state.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]# systemctl start vdsmd.service Job for vdsmd.service 
> failed because the control process exited with error code. See "systemctl 
> status vdsmd.service" and "journalctl -xe" for details.
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]# journalctl -xe
> --
> -- The result is dependency.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start 
> failed with result 'dependency'.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered 
> failed state.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job 
> for unit libvirtd.socket, ignoring: Invalid request descriptor

Perhaps this is the problem? Did libvirtd.socket work before?
Similarly for the others below.

> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job 
> for unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 
> 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd.socket, ignoring: Invalid request descriptor Jan 06 
> 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 
> 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit 
> libvirtd-ro.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 
> ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit 
> libvirtd-admin.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 
> ooengh1.tltd.com systemd[1]: Cannot add dependency job for unit 
> libvirtd.socket, ignoring: Invalid request descriptor Jan 06 15:28:56 
> ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, scheduling 
> restart.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd.socket, ignoring: Unit is masked.

This is probably why it failed, but it's not clear what masked it. If it was 
also masked before engine-setup, then perhaps this isn't the reason for vdsmd's 
failure.

If you want, you can try 'systemctl unmask $UNIT' for one of more of these and 
see if this helps.

If you suspect that this is due to updated packages, perhaps check 'dnf 
history' and 'dnf history info $ID' to see what changed. To revert, you can try 
'dnf history undo $ID'.

Good luck and best regards,
--
Didi

___
Users mailing list -- 

[ovirt-users] Re: How to install and configure the monitoring portal ?

[Yedidyah Bar David]

On Wed, Jan 6, 2021 at 9:32 AM tommy  wrote:
>
> OK, I got it.
>
> But ,after I reconfig, I found that is VDSM.service status is not right.
>
> Is there any problem ?

Sorry, I have no idea.

You seem to run vdsm and engine on the same machine, right? This is
called all-in-one, and is not supported (used to be, until 3.6,
several years ago).

Generally speaking, it's likely due to one of two things that
engine-setup might have done:

1. changed some configuration

2. updated some packages

You can check its log to see what it did.

>
>
>
>
> [root@ooengh1 ~]# systemctl status vdsmd.service
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: start-limit) since Wed 2021-01-06 15:25:58 CST; 
> 2min 9s ago
>   Process: 10758 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --post-stop (code=exited, status=0/SUCCESS)
>   Process: 10723 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
> --pre-start (code=exited, status=1/FAILURE)
>
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop 
> Server Manager.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered 
> failed state.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, 
> scheduling restart.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Stopped Virtual Desktop Server 
> Manager.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: start request repeated too 
> quickly for vdsmd.service
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Failed to start Virtual Desktop 
> Server Manager.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered 
> failed state.
> Jan 06 15:25:58 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]# systemctl start vdsmd.service
> Job for vdsmd.service failed because the control process exited with error 
> code. See "systemctl status vdsmd.service" and "journalctl -xe" for details.
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]#
> [root@ooengh1 ~]# journalctl -xe
> --
> -- The result is dependency.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Job mom-vdsm.service/start 
> failed with result 'dependency'.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Unit vdsmd.service entered 
> failed state.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service failed.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd.socket, ignoring: Invalid request descriptor

Perhaps this is the problem? Did libvirtd.socket work before?
Similarly for the others below.

> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd-ro.socket, ignoring: Invalid request descriptor
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd.socket, ignoring: Invalid request descriptor
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd-ro.socket, ignoring: Invalid request descriptor
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd-ro.socket, ignoring: Invalid request descriptor
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd-admin.socket, ignoring: Invalid request descriptor
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd.socket, ignoring: Invalid request descriptor
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: vdsmd.service holdoff time over, 
> scheduling restart.
> Jan 06 15:28:56 ooengh1.tltd.com systemd[1]: Cannot add dependency job for 
> unit libvirtd.socket, ignoring: Unit is masked.

This is probably why it failed, but it's not clear what masked it. If
it was also masked before engine-setup, then perhaps this isn't the
reason for vdsmd's failure.

If you want, you can try 'systemctl unmask $UNIT' for one of more of
these and see if this helps.

If you suspect that this is due to updated packages, perhaps check
'dnf history' and 'dnf history info $ID' to see what changed. To
revert, you can try 'dnf history undo $ID'.

Good luck and best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TOTFOYY62SDP5SAJOJ4B3JUECJEKP6KP/