[ovirt-users] Re: AWX and error using ovirt as an inventory source

2019-12-13 Thread Nathanaël Blanchet
Okay I got it! 
container version is slightly different from awx-rpm. All happen in awx_web 
container. You must use persistent volume so as to use venv and project data 
over ephemeral container. 
You must use python 3 with ansible 2.9.x 
cd installer && vi inventory 
custom_venv_dir = /opt/my-envs 
project_data_dir = /var/lib/awx/projects 

you can run installer 
ansible-playbook -i inventory install.yml 

check mounts 
docker inspect -f "{{ .Mounts }}" awx_web 
[{bind /opt/my-envs /opt/my-envs rw true rprivate} {bind /var/lib/awx/projects 
/var/lib/awx/projects rw true rprivate}] 

Right from now, you modify the container itself, becareful data are not 
persistent along container lifecycle, so what follows is for POC. You should 
build your own container image with this wanted parameters. 
yum install -y make gcc redhat-rpm-config python3-devel libcurl-devel 
libxml2-devel 
source /opt/my-envs/py36/bin/activate 
pip install psutil 
export PYCURL_SSL_LIBRARY = openssl ; pip install pycurl --compile 
--no-cache-dir 
pip install ansible ovirt-engine-sdk-python centreonapi dnspython 

select the py36 venv into the source to sync and it should work 

De: "Gianluca Cecchi"  
À: "Guillaume Pavese"  
Cc: "Nathanaël Blanchet" , "users"  
Envoyé: Vendredi 6 Décembre 2019 13:40:45 
Objet: Re: [ovirt-users] Re: AWX and error using ovirt as an inventory source 

Actually it seems I was using the wrong container... so explaining why I got 
the not found error about /opt/my-envs/ovirt/lib ... ;-) 

I was working on ansible/awx_web:9.0.1 container, while it seems I have to work 
ansible/awx_task:9.0.1 

After doing same steps on this container I get now this kind of error at the 
end while using apparently the correct virtualenv: 

2.429 INFO Updating inventory 4: MYDC_OVIRT 
3.257 DEBUG Using base command: python /opt/my-envs/ovirt/bin/ansible-inventory 
-i 
/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/plugins/inventory/ovirt4.py
 --playbook-dir 
/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/plugins/inventory 
-v 
3.257 INFO Reading Ansible inventory source: 
/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/plugins/inventory/ovirt4.py
 
3.259 INFO Using VIRTUAL_ENV: /opt/my-envs/ovirt/ 
3.260 INFO Using PATH: 
/opt/my-envs/ovirt/bin:/var/lib/awx/venv/awx/bin:/var/lib/awx/venv/awx/bin:/var/lib/awx/venv/awx/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 
3.260 INFO Using PYTHONPATH: /opt/my-envs/ovirt/lib/python2.7/site-packages: 
Traceback (most recent call last): 
File "/var/lib/awx/venv/awx/bin/awx-manage", line 11, in  
load_entry_point('awx==9.0.1.0', 'console_scripts', 'awx-manage')() 
File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/__init__.py", 
line 158, in manage 
execute_from_command_line(sys.argv) 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/__init__.py",
 line 381, in execute_from_command_line 
utility.execute() 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/__init__.py",
 line 375, in execute 
self.fetch_command(subcommand).run_from_argv(self.argv) 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/base.py",
 line 323, in run_from_argv 
self.execute(*args, **cmd_options) 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/base.py",
 line 364, in execute 
output = self.handle(*args, **options) 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py",
 line 1153, in handle 
raise exc 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py",
 line 1043, in handle 
venv_path=venv_path, verbosity=self.verbosity).load() 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py",
 line 214, in load 
return self.command_to_json(base_args + ['--list']) 
File 
"/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py",
 line 197, in command_to_json 
self.method, proc.returncode, stdout, stderr)) 
RuntimeError: ansible-inventory failed (rc=1) with stdout: 
stderr: 
ansible-inventory 2.9.2 
config file = /etc/ansible/ansible.cfg 
configured module search path = [u'/var/lib/awx/.ansible/plugins/modules', 
u'/usr/share/ansible/plugins/modules'] 
ansible python module location = 
/opt/my-envs/ovirt/lib/python2.7/site-packages/ansible 
executable location = /opt/my-envs/ovirt/bin/ansible-inventory 
python version = 2.7.15 (default, Oct 8 2019, 21:08:29) [GCC 8.2.1 20180905 
(Red Hat 8.2.1-3)] 
Using /etc/ansible/ansible.cfg as config file 
setting up inventory plugins 
[WARNING]: * Failed to parse /var/lib/awx/venv/awx/lib64/python3.6/site- 
packages/awx/plugins/inventory/ovirt4.py with script plugin: Inventory script 
(/var/lib/awx/venv/awx/lib64/python3.6/site- 
packages/awx/plugins/inventory/ovirt4.py) had an execution 

[ovirt-users] Re: Unable to attach ISO domain to Datacenter

2019-12-13 Thread Strahil
What  is the output of  'ls  -lZ /usr/bin/ionice' ?
Here is mine :
-rwxr-xr-x. root root system_u:object_r:bin_t:s0   /usr/bin/ionice

Best Regards,
Strahil NikolovOn Dec 13, 2019 16:58, Ivan Apolonio  
wrote:
>
> Hello. 
>
> I tried to reinstall my whole environment using oficial oVirt ISO image and 
> the same problem occurs. I also tried to give full access to vdsm user in 
> sudoers file and the results are exactly the same. This is the error on 
> showed on oVirt Manager: 
>
> VDSM command AttachStorageDomainVDS failed: Cannot obtain lock: 
> u"id=e65b4f0f-faa1-4cdc-9d2a-ab4fccfec0b0, rc=1, out=[], err=['setsid: failed 
> to execute /usr/bin/ionice: Permission denied']" 
>
> In other hand, the node server's vdsm.log file shows no errors. 
>
> The engine.log still shows the same errors as my previous posts with logs. I 
> don't know what else can I do. 
>
> Please help. 
> Thanks, 
> Ivan
> ___
> 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/J6ZI7A7QTDZMVVOGZLNMPQGVC2A3EJ5R/
___
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/KB37BJGFUXZ26WQ6E4OE2JCULBFHYCYE/


[ovirt-users] Re: kernel parameter "spectre_v2=retpoline"

2019-12-13 Thread Matthias Leopold



Am 12.12.19 um 19:20 schrieb Michal Skrivanek:

On 12 Dec 2019, at 17:38, Matthias Leopold  
wrote:

Hi,

I'm planning to upgrade my installation from CentOS 7.6/oVirt 4.3.5 to CentOS 
7.7/oVirt 4.3.7.
According to
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.7_release_notes/new_features#enhancement_kernel
there's a new default setting for Spectre V2 mitigation in new RHEL 7 installs. 
Shall I switch my hypervisor hosts to this setting when upgrading? Would newly 
installed CentOS 7 oVirt hosts have that kernel parameter?


Doesn’t the same paragraph describe new install vs upgrade behavior?;)
I wouldn’t think Centos is going to be any different .



Thanks, I read that, but thought there might some virtualization/oVirt 
related recommendations or people that already have some experience. 
Probably I should just believe what I read, worry less and trust my own 
expertise...


Matthias
___
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/GBANGZWPP77CDDOSOD7WNQBAUZGE77KZ/


[ovirt-users] Re: Unable to attach ISO domain to Datacenter

2019-12-13 Thread Ivan Apolonio
I was finally able to attach ISO Domain to Datacenter after moving all 
Datacenter's Storage Domains and Hosts to MAINTAINANCE except on the Host where 
I was creating the ISO Domain.

It looks like a bug on oVirt that didn't allow to simply add a ISO Domain after 
all other hosts and Data Domains has been previously added to my Datacenter. 
However, I'm glad I was finally able to attach the ISO Domain to my Datacenter.

Thanks for everyone assistance
___
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/RMUKB7HPIFXVE7DVETTTISUUUWZ7LP4G/


[ovirt-users] Re: How to run oVirt on CentOS 8 (or 8.1 or Stream)

2019-12-13 Thread Sandro Bonazzola
Il giorno dom 8 dic 2019 alle ore 09:14 Nate Revo  ha
scritto:

> I have a system that requires the 4x kernel to run and wanted to run oVirt
> on top of CentOS.   Seems as I'm looking around, rhel/centos 8 support for
> ovirt is slated for v 4.4. What's the progress with running on Centos 8+
> and how do I run ovirt on Centos 8, now.
>
>

You can now try oVirt 4.4 alpha:
https://lists.ovirt.org/archives/list/annou...@ovirt.org/thread/3AZCAGK4XJOWF636KNUU2YDPIREZ5EAM/


> Thanks in advance,
> -Nate Revo
>
> P.S.  Will code for pizza
>
> --
>
> Nathan Revo, RHCE
>
> OpenShift Specialist Solutions Architect
>
> Red Hat NorthWest Strategic 
>
> nr...@redhat.com
> M: 801-885-8182
> 
> ___
> 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/FLFF4LLJPNJNYZEJ5OQYSNBXOKRTMO5E/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
*
___
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/SDT6KEMRSK7OO4N4FYVFIWRJP6PMQHXR/


[ovirt-users] Re: ovirt vdsm and networking

2019-12-13 Thread kim . kargaard
Thank you. 

Managed to add the IP's using that method Dominik and finally managed to set 
the display network to the Student network. 

A related question :)

Our set up is a public facing IP that uses NAT at the firewall to point 
internally to the ovirt engine web app. When users create VM's and click on the 
SPICE console and download the .vv file, the file now points to the public 
facing IP, which I assume is correct as I have set the ovirt engine as the 
websocket proxy. Our remote users will not have access to the internal network 
through a VPN, so they need to be able to use Spice and connect to the VM's. 
So, the firewall would need to take the traffic coming in from the public 
facing IP on port 590(n) and point it to the internal ovirt engine IP, correct? 
Then, the ovirt engine as the websocket proxy would know where to send the 
traffic to match that VM? Have I understood the process correctly?

Kind regards

Kim
___
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/BFQ4OAV4432HWIWQ4HA7ET6MZSB3NHE4/


[ovirt-users] Re: Unable to attach ISO domain to Datacenter

2019-12-13 Thread Ivan Apolonio
Hello.

I tried to reinstall my whole environment using oficial oVirt ISO image and the 
same problem occurs. I also tried to give full access to vdsm user in sudoers 
file and the results are exactly the same. This is the error on showed on oVirt 
Manager:

VDSM command AttachStorageDomainVDS failed: Cannot obtain lock: 
u"id=e65b4f0f-faa1-4cdc-9d2a-ab4fccfec0b0, rc=1, out=[], err=['setsid: failed 
to execute /usr/bin/ionice: Permission denied']"

In other hand, the node server's vdsm.log file shows no errors.

The engine.log still shows the same errors as my previous posts with logs. I 
don't know what else can I do.

Please help.
Thanks,
Ivan
___
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/J6ZI7A7QTDZMVVOGZLNMPQGVC2A3EJ5R/


[ovirt-users] Re: Cannot forward traffic through VXLAN

2019-12-13 Thread k . betsis
> On Thu, Dec 12, 2019 at 4:27 PM  
> 
> 
> Not external logical networks, with vNIC profiles, have no network filter
> during the VM is started (or the vNIC is hotplugged),
> allows any MAC address. This works without any hook required.
> In most simple flow for a lab would be to remove the network filter from
> ovirtmgmt, attach ovirtmgmt to a VM and boot the VM.
> 
Well this is where theory contradicts practice...
Based on what you say layer 2 frames would traverse the VM Network bridge and 
reach VyOS vnic, which they do not.
Layer 2 frames are dropped after leaving the VM and before reaching the VyOS 
vnic.
In theory if the VM bridge did not know where they should be forwarded it 
should broadcast them to all attached ports, which again it is not been done.
So i am not sure if it is a bug, or a feature...
> 
> 
> As I wrote above, layer 2 tunneling from one VM to another should work.
> Are you force to extend the network on layer 2? If not,
> two VMs connected by a tunnel or a VPN might be more straight and would
> even limit layer 2 broadcasts.
I agree Layer 3 would be the best way forward but we need layer 2 extension 
since the firewalls require it for high availability as well and we need pcsd 
VIPs attached to monitored services to have high availability.
___
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/WFV4A4YIDL7TFH2DQ3HYMO6UK5DLIIQT/


[ovirt-users] Re: ovirt vdsm and networking

2019-12-13 Thread Staniforth, Paul
Hi Kim,

   you should be able to from the admin portal for the interfaces 
of your hosts go into setup host networks and change the boot protocol for your 
student network to manual or dhcp.

If you don't want your student VMs having network access to your hosts you 
could configure a separate display network or setup a spice and websocket proxy.


Regards,
   Paul S.



From: kim.karga...@noroff.no 
Sent: 13 December 2019 07:39
To: users@ovirt.org 
Subject: [ovirt-users] ovirt vdsm and networking

Hi,

We are running CentOS and ovirt 4.3.4. We currently have four nodes and have 
set up the networks as follows:

ovirtmanagmeent network - set up as a tagged vlan with a static IP
SAN network - set up as a tagged vlan with a static IP
student network - set up as a tagged vlan
fw network - set up as a tagged vlan

The ovirtmanagement and SAN networks were configured on the CentOS boxes during 
after installing CentOS and before adding the nodes as hosts. The student 
network and the fw network were configured through the ovirt admin panel. 
However, because of this, the student network is not assigned a static IP on 
the nodes and serves the VM's using the DHCP on the firewall. The ovirt 
management network is set as the display network and every time I try to change 
that to the student network, ovirt admin panel tells me that I can't because 
there is no IP address assigned to the student network vlan. I tried using ip 
addr add to add a static IP on the one CentOS node, but this does not get 
picked up by ovirt and of course ovirt controls the actual vlan files on the 
CentOS box through VDSM, so any changes I make there will likely just be 
overwritten.

So, my question is, should I stop VDSM, add the IP to the vlan files on the 
CentOS nodes and then restart VDSM or is there a proper way of solving this? I 
need the Display Network to be set to the student network.

Thank you for any help.

Kim
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fsite%2Fprivacy-policy%2Fdata=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C1c47f39cfcf84994fbd408d77f9ffbfd%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637118197417609430sdata=1fcmXSxHwF1%2FtCP4qBuF7vionTYLJ1BvL8ncy3%2BFu24%3Dreserved=0
oVirt Code of Conduct: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2Fdata=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C1c47f39cfcf84994fbd408d77f9ffbfd%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637118197417619425sdata=8Mn1eai8ynlFi48n%2Baqxde6N6Fr9tleamXfydkbgvyM%3Dreserved=0
List Archives: 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FO5GJRNIPOXJLZ2KEPGZJZZNG57OTTLGI%2Fdata=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7C1c47f39cfcf84994fbd408d77f9ffbfd%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637118197417619425sdata=tINoieIB1L8IQpoVA7dOVar8hVCnF8mNEteawBlCU00%3Dreserved=0
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/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/EE3CECC62DAP6EBVPNXBSHHGL7DKKRU5/


[ovirt-users] Re: ovirt vdsm and networking

2019-12-13 Thread Dominik Holler
On Fri, Dec 13, 2019 at 8:41 AM  wrote:

> Hi,
>
> We are running CentOS and ovirt 4.3.4. We currently have four nodes and
> have set up the networks as follows:
>
> ovirtmanagmeent network - set up as a tagged vlan with a static IP
> SAN network - set up as a tagged vlan with a static IP
> student network - set up as a tagged vlan
> fw network - set up as a tagged vlan
>
> The ovirtmanagement and SAN networks were configured on the CentOS boxes
> during after installing CentOS and before adding the nodes as hosts. The
> student network and the fw network were configured through the ovirt admin
> panel. However, because of this, the student network is not assigned a
> static IP on the nodes and serves the VM's using the DHCP on the firewall.
> The ovirt management network is set as the display network and every time I
> try to change that to the student network, ovirt admin panel tells me that
> I can't because there is no IP address assigned to the student network
> vlan. I tried using ip addr add to add a static IP on the one CentOS node,
> but this does not get picked up by ovirt and of course ovirt controls the
> actual vlan files on the CentOS box through VDSM, so any changes I make
> there will likely just be overwritten.
>
> So, my question is, should I stop VDSM, add the IP to the vlan files on
> the CentOS nodes and then restart VDSM or is there a proper way of solving
> this? I need the Display Network to be set to the student network.
>
>
Please use oVirt Engine to manage the network config of the host.
In the web UI, go to
Compute -> Hosts -> hostname -> Network Interfaces -> Setup Host
Networks ->  click the pencil icon to open the Edit Network window

Did this solve the problem?


> Thank you for any help.
>
> Kim
> ___
> 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/O5GJRNIPOXJLZ2KEPGZJZZNG57OTTLGI/
>
___
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/JKBLKAPJQTD6ZX2MDJZIWBM2OXWAH6JS/


[ovirt-users] Re: oVirt 4.4.0 Alpha release is now available for testing

2019-12-13 Thread Sandro Bonazzola
Il giorno ven 13 dic 2019 alle ore 11:30 Gianluca Cecchi <
gianluca.cec...@gmail.com> ha scritto:

> On Fri, Dec 13, 2019 at 11:19 AM Sandro Bonazzola 
> wrote:
>
>> oVirt 4.4.0 Alpha release is now available for testing
>>
>> The oVirt Project is excited to announce the availability of the alpha
>> release of oVirt 4.4.0 for testing, as of December 13th, 2019
>>
>> This release unleashes an altogether more powerful and flexible open
>> source virtualization solution that encompasses hundreds of individual
>> changes and a wide range of enhancements across the engine, storage,
>> network, user interface, and analytics on top of oVirt 4.3.
>>
>
>  What a nice pre-Christmas present... thanks!
>

Couldn't let Santa Lucia come without a gift!
(For non italian users: https://en.wikipedia.org/wiki/Saint_Lucy%27s_Day )


>
> This release is available now on x86_64 architecture for:
>>
>> * Red Hat Enterprise Linux 7.7 or later (but < 8.0)
>>
>> * CentOS Linux (or similar) 7.7 or later (but < 8.0)
>>
>>
> Probably too early to ask, but does this mean that realistically when
> final 4.4 will be out it will support also 7.7 and not only 8.x based hosts?
>

4.4 will support cluster level 4.2 so you can still use 7.7 based oVirt
4.2/4.3 hosts until you finish to migrate everything to 4.4.
Recomendation will be to move to 4.4 / el8 based hosts ASAP once 4.4 will
go GA.


>
> In case of spare time to test, where is the correct place then to report,
> apart standard bugzilla? ovirt users or devel list?
>

bugzilla is always best place to report bugs. sos reports attached will be
useful to get more data when debugging reported issues.



>
> Thanks again,
> Gianluca
>
>
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
*
___
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/35SJ73S7KWVJEYEKVAC2OMIKTXNFVAZK/


[ovirt-users] Re: oVirt 4.4.0 Alpha release is now available for testing

2019-12-13 Thread Gianluca Cecchi
On Fri, Dec 13, 2019 at 11:19 AM Sandro Bonazzola 
wrote:

> oVirt 4.4.0 Alpha release is now available for testing
>
> The oVirt Project is excited to announce the availability of the alpha
> release of oVirt 4.4.0 for testing, as of December 13th, 2019
>
> This release unleashes an altogether more powerful and flexible open
> source virtualization solution that encompasses hundreds of individual
> changes and a wide range of enhancements across the engine, storage,
> network, user interface, and analytics on top of oVirt 4.3.
>

 What a nice pre-Christmas present... thanks!

This release is available now on x86_64 architecture for:
>
> * Red Hat Enterprise Linux 7.7 or later (but < 8.0)
>
> * CentOS Linux (or similar) 7.7 or later (but < 8.0)
>
>
Probably too early to ask, but does this mean that realistically when final
4.4 will be out it will support also 7.7 and not only 8.x based hosts?

In case of spare time to test, where is the correct place then to report,
apart standard bugzilla? ovirt users or devel list?

Thanks again,
Gianluca
___
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/UGLK3GENMFZGBTHJPEZ7EOTHEHSGNUQ3/


[ovirt-users] oVirt 4.4.0 Alpha release is now available for testing

2019-12-13 Thread Sandro Bonazzola
oVirt 4.4.0 Alpha release is now available for testing

The oVirt Project is excited to announce the availability of the alpha
release of oVirt 4.4.0 for testing, as of December 13th, 2019

This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics on top of oVirt 4.3.

Important notes before you try it

Please note this is an Alpha release.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not to be used in production, and it is not feature
complete.

In particular, please note that upgrades from 4.3 and future upgrades from
this alpha to the final 4.4 release from this version are not supported.

Some of the features included in oVirt 4.4.0 Alpha require content that
will be available in CentOS Linux 8.1 which is currently being built from
Red Hat Enterprise Linux 8.1.

If you want to have a better experience you can test oVirt 4.4.0 Alpha on
Red Hat Enterprise Linux 8.1.

Known Issues

   -

   After installation open the Default cluster and hit “Save”, for any
   other new Cluster using CPU autodetection the dialog needs to be explicitly
   saved after the detection happens, after first host is added. (bug
   https://bugzilla.redhat.com/1770697)
   -

   Migrate, Cluster Upgrade, Export VM buttons cannot be clicked. Fixed in
   ovirt-engine-ui-extensions-1.0.11

Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 7.7 minimal from
http://centos.mirror.garr.it/centos/7.7.1908/isos/x86_64/CentOS-7-x86_64-Minimal-1908.iso

- yum install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- yum update (reboot if needed)

- yum install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8.0 from
http://centos.mirror.garr.it/centos/8.0.1905/isos/x86_64/CentOS-8-x86_64-1905-dvd1.iso
; select minimal installation

- yum config-manager --set-enabled PowerTools

- yum install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- yum update (reboot if needed)

- Attach the host to engine and let it be deployed.

What’s new in oVirt 4.4.0 Alpha?

   -

   Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8),
   for both oVirt Node and standalone CentOS Linux hosts
   -

   Easier network management and configuration flexibility with
   NetworkManager
   -

   VMs based on a more modern Q35 chipset with legacy seabios and UEFI
   firmware
   -

   Support for direct passthrough of local host disks to VMs
   -

   Live migration improvements for High Performance guests.
   -

   New Windows Guest tools installer based on WiX framework now moved to
   VirtioWin project
   -

   Dropped support for cluster level prior to 4.2
   -

   Dropped SDK3 support
   -

   4K disks support
   -

   Exporting a VM to a data domain
   -

   Editing of floating disks
   -

   Integrating ansible-runner into engine, which allows a more detailed
   monitoring of playbooks executed from engine
   -

   Adding/reinstalling hosts are now completely based on Ansible
   -

   The OpenStack Neutron Agent cannot be configured by oVirt anymore, it
   should be configured by TripleO instead




This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8.0)

* CentOS Linux (or similar) 7.7 or later (but < 8.0)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.0 or later

* CentOS Linux (or similar) 8.0 or later

* oVirt Node 4.4 based on CentOS Linux 8.0 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

If you manage more than one oVirt instance, OKD or RDO we also recommend to
try ManageIQ .

In such a case, please be sure  to take the qc2 image and not the ova image.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.0 release highlights:
http://www.ovirt.org/release/4.4.0/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.0/
[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: 

[ovirt-users] Re: Ovirt OVN help needed

2019-12-13 Thread Dominik Holler
On Fri, Dec 13, 2019 at 5:51 AM Strahil  wrote:

> Hi Dominik, All,
>
> I've checked '
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/W6U4XJHNMYMD3WIXDCPGOXLW6DFMCYIM/'
> and the user managed to clear up and start over.
>
> I have removed the ovn-external-provider  from UI, but I forgot to copy
> the data from the fields.
>
> Do you know any refference guide (or any tips & tricks) for adding OVN ?
>

The ovirt-provider-ovn entity can be added to oVirt Engine as a new
provider with
Type: External Network Provider
Network Plugin: oVirt Network Provider for OVN
Provider URL: https://YOUR_ENGINE_FQDNt:9696
Username: admin@internal
Password: admin@interal password
Host Name: YOUR_ENGINE_FQDN
API Port: 35357
API Version: v2.0

Is this the information you need?


> Thanks in advance.
>
> Best Regards,
> Strahil Nikolov
> On Dec 12, 2019 20:49, Strahil  wrote:
>
> Hi Dominik,
>
> Thanks for the reply.
>
> Sadly the openstack module is missing on the engine and I have to figure
> it out.
>
> Can't I just undeploy the ovn and then redeploy it back ?
>
> Best Regards,
> Strahil Nikolov
> On Dec 12, 2019 09:32, Dominik Holler  wrote:
>
> The cleanest way to clean up is to remove all entities on the OpenStack
> Network API on ovirt-provider-ovn, e.g. by something like
>
> https://gist.github.com/dominikholler/19bcdc5f14f42ab5f069086fd2ff5e37#file-list_security_groups-py-L25
> This should work, if not, please report a bug.
>
> To bypass the ovirt-provider-ovn, which is not recommended and might end
> in an inconsistent state, you could use ovn-nbctl .
>
>
>
> On Thu, Dec 12, 2019 at 3:33 AM Strahil Nikolov 
> wrote:
>
> Hi Community,
>
> can someone hint me how to get rid of some ports? I just want to 'reset'
> my ovn setup.
>
> Here is what I have so far:
>
> [root@ovirt1 openvswitch]# ovs-vsctl list interface
> _uuid   : be89c214-10e4-4a97-a9eb-1b82bc433a24
> admin_state : up
> bfd : {}
> bfd_status  : {}
> cfm_fault   : []
> cfm_fault_status: []
> cfm_flap_count  : []
> cfm_health  : []
> cfm_mpid: []
> cfm_remote_mpids: []
> cfm_remote_opstate  : []
> duplex  : []
> error   : []
> external_ids: {}
> ifindex : 35
> ingress_policing_burst: 0
> ingress_policing_rate: 0
> lacp_current: []
> link_resets : 0
> link_speed  : []
> link_state  : up
> lldp: {}
> mac : []
> mac_in_use  : "7a:7d:1d:a7:43:1d"
> mtu : []
> mtu_request : []
> name: "ovn-25cc77-0"
> ofport  : 6
> ofport_request  : []
> options : {csum="true", key=flow, remote_ip="192.168.1.64"}
> other_config: {}
> statistics  : {rx_bytes=0, rx_packets=0, tx_bytes=0, tx_packets=0}
> status  : {tunnel_egress_iface=ovirtmgmt,
> tunnel_egress_iface_carrier=up}
> type: geneve
>
> _uuid   : ec6a6688-e5d6-4346-ac47-ece1b8379440
> admin_state : down
> bfd : {}
> bfd_status  : {}
> cfm_fault   : []
> cfm_fault_status: []
> cfm_flap_count  : []
> cfm_health  : []
> cfm_mpid: []
> cfm_remote_mpids: []
> cfm_remote_opstate  : []
> duplex  : []
> error   : []
> external_ids: {}
> ifindex : 13
> ingress_policing_burst: 0
> ingress_policing_rate: 0
> lacp_current: []
> link_resets : 0
> link_speed  : []
> link_state  : down
> lldp: {}
> mac : []
> mac_in_use  : "66:36:dd:63:dc:48"
> mtu : 1500
> mtu_request : []
> name: br-int
> ofport  : 65534
> ofport_request  : []
> options : {}
> other_config: {}
> statistics  : {collisions=0, rx_bytes=0, rx_crc_err=0,
> rx_dropped=0, rx_errors=0, rx_frame_err=0, rx_over_err=0, rx_packets=0,
> tx_bytes=0, tx_dropped=0, tx_errors=0, tx_packets=0}
> status  : {driver_name=openvswitch}
> type: internal
>
> _uuid   : 1e511b4d-f7c2-499f-bd8c-07236e7bb7af
> admin_state : up
> bfd : {}
> bfd_status  : {}
> cfm_fault   : []
> cfm_fault_status: []
> cfm_flap_count  : []
> cfm_health  : []
> cfm_mpid: []
> cfm_remote_mpids: []
> cfm_remote_opstate  : []
> duplex  : []
> error   : []
> external_ids: {}
> ifindex : 35
> ingress_policing_burst: 0
> ingress_policing_rate: 0
> lacp_current: []
> link_resets : 0
> link_speed  : []
> link_state  : up
> lldp: {}
> mac : []
> mac_in_use  : "1a:85:d1:d9:e2:a5"
> mtu : []
> mtu_request : []
> name: "ovn-566849-0"
> ofport  : 5
>