[ovirt-users] oVirt 3.5 test day 2 results: foreman advanced integration feature
Hi, In the second ovirt test day I've retested the foreman advanced integration. Using the instructions on the wiki page I was able to test part of the feature: * Adding foreman provider and test connectivity with certificates import * Present discovered hosts by foreman * Present provisioned hosts by foreman * Add discovered hosts by foreman (reached to Installing OS phase only due to environmental issues). Since the host provisioning wasn't completed, I haven't reach to test the foreman--ovirt connectivity which should have trigger the host installation. I've filed a couple of bugs which I encountered during the testing: Bug 1124870 - Provision of a host without compute resources fails with NPE Bug 1124878 - Set Root password text label is not aligned with its caption Bug 1124891 - [oVirt][Foreman] Root password length should be validated Bug 1124887 - [RFE][oVirt][Foreman] Improve error messages when action fails on foreman server In addition I've updated the feature page which missed a required package to be installed on the foreman server. Regards, Moti - Forwarded Message - From: Moti Asayag masa...@redhat.com To: de...@ovirt.org Sent: Thursday, July 3, 2014 5:17:11 PM Subject: ovirt test day report - ovirt - foreman advanced integration feature Hi, I assigned myself to the ovirt-foreman advanced integration feature [1] in the first ovirt 3.5 test day. The setup required for testing that environment is a bit complex (foreman, isolated network, extending the foreman with extra plugins). I faced environmental issues most of the day, mainly regarding foreman installation and configuration. I provided specific feedback regarding the installed setup missing steps to Yaniv, the feature owner, which will incorporate them into the feature page. I haven't reached into a point where i can provision a host via foreman into ovirt, but I plan to get back to it in the second ovirt test day (or even before). [1] http://www.ovirt.org/Features/AdvancedForemanIntegration Regards, Moti ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt 3.5 test day 2 results: foreman advanced integration feature
On 07/31/2014 10:49 AM, Moti Asayag wrote: Hi, In the second ovirt test day I've retested the foreman advanced integration. Using the instructions on the wiki page I was able to test part of the feature: * Adding foreman provider and test connectivity with certificates import * Present discovered hosts by foreman * Present provisioned hosts by foreman * Add discovered hosts by foreman (reached to Installing OS phase only due to environmental issues). Since the host provisioning wasn't completed, I haven't reach to test the foreman--ovirt connectivity which should have trigger the host installation. I've filed a couple of bugs which I encountered during the testing: Bug 1124870 - Provision of a host without compute resources fails with NPE Bug 1124878 - Set Root password text label is not aligned with its caption Bug 1124891 - [oVirt][Foreman] Root password length should be validated Bug 1124887 - [RFE][oVirt][Foreman] Improve error messages when action fails on foreman server In addition I've updated the feature page which missed a required package to be installed on the foreman server. Regards, Moti Hi, I tested this feature also. I was able to get things going by manually installing vdsm because something goes wrong with my puppet classes. Filed one ovirt bug: 1124842 https://bugzilla.redhat.com/show_bug.cgi?id=1124842 - using Use Foreman Hosts Providers disables Address field in New host dialog And one foreman bug: Bug #6839: Conflict DHCP records when using the Use Foreman Hosts ProvidersProvisioned Hosts of ovirt 3.5 http://projects.theforeman.org/issues/6839#change-23847 Also I agree with Bug 1124887 - [RFE][oVirt][Foreman] Improve error messages when action fails on foreman server, I had to go look in the foreman logs a lot to see things configured incorrect. The error in ovirt is just that the connection doesn't work. But it appears most of it is working correctly. Kind regards, Jorick Astrego Netbulae B.V. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5 test day 2 results
Hi, I tested 557125 - internationalize exitMessage; use meaningful exitCode These are the tests I made : power off from inside the guest - VM testexitmessage is down. Exit message: User shut down from within the guest ID 61 power off from inside the admin portal - VM testexitmessage powered off by admin (Host: yanivs) (Reason: Not Specified). ID 33 shotdown from inside the admin portal - VM shutdown initiated by admin on VM testexitmessage (Host: yanivs) (Reason: Not Specified) ID73 VM testexitmessage is down. Exit message: User shut down from within the guest ID61 shotdown from inside the guest - VM testexitmessage is down. Exit message: User shut down from within the guest ID 61 reboot from guest - no exit reason. In espanol shotdown from inside the admin portal - VM shutdown initiated by admin on VM testexitmessage (Host: yanivs) (Reason: Not Specified). ID 73 VM testexitmessage is down. Exit message: User shut down from within the guest ID 61 In Deutsch power off from inside the admin portal - VM testexitmessage powered off by admin (Host: yanivs) (Reason: Not Specified). ID 33 Conclutions: 1. I don't see translations for local langueges for the events in the admin portal. 2. In case of shotdown from inside the admin portal we get 2 messages instead of one. The second one(ID61) is incorrect. Best regards, --- Shirly Radco BI Software Engineer Red Hat Israel Ltd. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5 test day 2 results - NUMA
Hi,
I tried to test NUMA feature. Unfortunately the feature has no UI yet,
so I tested just db content and REST API calls:
1) Two NUMA hosts added to 3.5 cluster with shared NFS storage using webadmin
2) Database:
a) Both hosts have is_numa_supported=true, auto_numa_balancing=1 in
vds_dynamic table
b) Both hosts have 2 records in numa_nodes tables (consistent with numactl
info)
c) Both hosts have 24 records in numa_node_cpu_map, 12 per numa node
(consistent with numactl info)
3) REST API:
a) URL /ovirt-engine/api/hosts/{HOST_ID} contains numa related data:
auto_numa_statusenable/auto_numa_status
numa_supportedtrue/numa_supported
b) URL /ovirt-engine/api/hosts/{HOST_ID}/numanodes works (consistent with
numactl info)
c) URL /ovirt-engine/api/hosts/{HOST_ID}/numanodes/{NODE_ID}/statistics
works
4) Installed two VMs (one RHEL 6, one RHEL 7), both requires 16GB of RAM, with
balloon enabled
and 8GB guarantied.
5) Database:
a) Both vms have numatune_mode=preferred in vm_static
6) REST API for VM related data:
a) URL /ovirt-engine/api/vms/{VM_ID} contains numa related data:
numa_tune_modepreferred/numa_tune_mode
b) URL /ovirt-engine/api/vms/{VM_ID}/numanodes works, but returns only:
vm_numa_nodes/
6) VMs migration between hosts worked fine
Martin Perina
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt 3.5 test day 2 results - NUMA
- Original Message -
From: Martin Perina mper...@redhat.com
To: de...@ovirt.org, Users@ovirt.org List users@ovirt.org
Sent: Wednesday, July 30, 2014 1:26:49 PM
Subject: [ovirt-users] oVirt 3.5 test day 2 results - NUMA
Hi,
I tried to test NUMA feature. Unfortunately the feature has no UI yet,
so I tested just db content and REST API calls:
1) Two NUMA hosts added to 3.5 cluster with shared NFS storage using webadmin
2) Database:
a) Both hosts have is_numa_supported=true, auto_numa_balancing=1 in
vds_dynamic table
b) Both hosts have 2 records in numa_nodes tables (consistent with
numactl info)
c) Both hosts have 24 records in numa_node_cpu_map, 12 per numa node
(consistent with numactl info)
3) REST API:
a) URL /ovirt-engine/api/hosts/{HOST_ID} contains numa related data:
auto_numa_statusenable/auto_numa_status
numa_supportedtrue/numa_supported
b) URL /ovirt-engine/api/hosts/{HOST_ID}/numanodes works (consistent with
numactl info)
c) URL /ovirt-engine/api/hosts/{HOST_ID}/numanodes/{NODE_ID}/statistics
works
4) Installed two VMs (one RHEL 6, one RHEL 7), both requires 16GB of RAM,
with balloon enabled
and 8GB guarantied.
5) Database:
a) Both vms have numatune_mode=preferred in vm_static
6) REST API for VM related data:
a) URL /ovirt-engine/api/vms/{VM_ID} contains numa related data:
numa_tune_modepreferred/numa_tune_mode
b) URL /ovirt-engine/api/vms/{VM_ID}/numanodes works, but returns only:
vm_numa_nodes/
thanks for the elaborate report, few question:
What was reported in the element?
Did you pin the nodes?
6) VMs migration between hosts worked fine
VM migration with/out numa pinning?
Martin Perina
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5 test day 2 results - spice-html5 button to show debug console/output window - 1108599
Hi, I had to test the presence of a button to show the debug output for the spice-html5 console. I created a setup with two host (the first with the engine in all-in-one fashion and the second with just a websocket proxy). I launched a VM and I tried to open the spice-html5 console. The new button is present and it's able to toggle an element with some text. The main issue is that also if everything is ok, it shows a lot of noise warnings about unimplemented functions and similar stuff (see fig_ok.png). If I enable a firewall to isolate the websocket proxy instead I can read only Websocket.onerror and, at least on my perception, it's not so useful to debug the cause (see fig_fault.png). So the button is there but we should double check what to show on errors. ciao, Simone ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5 test day 2 results
Hi everyone, Hi tested again http://www.ovirt.org/Features/WebSocketProxy_on_a_separate_host What happened on tast day 1 * found minor packaging issues * stopped earlier facing SSL issues, had a followup the day after an managed to have the feature working. This time things got better, and again the feature works as expected. The packaging issues are gone, but I still had UX annoyances along the way. I followed instructions on the wiki page above. Platform: F20 hypervisor host F20 engine host F19 websocket proxy (Didn't had time to test on different platforms because local bandwith issues eat lot of time just to install things) Installation went fine. websocket proxy setup is maybe a bit clumsy (I mean the text mode wizard), but it is bearable (I don't mind at all, but someone else can...); for some reasons (I cannot exclude an error from mine) engine got configured to use localhost as websocket proxy. To fix this I edited the engine config (update on DBMS), but then faced this error on proxy side: Jul 29 17:13:14 shinji ovirt-websocket-proxy.py[17004]: 1: handler exception: [Errno 1] _ssl.c:504: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher to redo the websocket setup I removed (actually renamed) /etc/pki/ovirt-engine and rerun setup. After that everything worked fine Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 8: connecting to: 192.168.1.53:5900 (using SSL) Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 5: 192.168.1.177: SSL/TLS (wss://) WebSocket connection Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 5: 192.168.1.177: Version hybi-13, base64: 'False' Jul 29 17:26:52 shinji ovirt-websocket-proxy.py[17180]: 5: 192.168.1.177: Path: '/eyJ2YWxpZFRvIjoiMjAxNDA3MjkxNTIx [...] 192.168.1.53 is the hypervisor host I used Now the point is maybe I did some mistakes or overlooked some configuration steps (maybe blindly hit return instead of changing a default), but I suggest to improve the docs/wiki to document how to fix common gotchas and/or to reconfigure things. Bests, -- Francesco Romani RedHat Engineering Virtualization R D Phone: 8261328 IRC: fromani ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5 test day 2 results
I once again tested 1091863 Accept vlan devices identified by any name Steps to Reproduce: - Change Host to maintenance mode. - Add a vlan with alternative name to the Host: # ip link add dev eth1.myvlan10 link eth1 name eth1.myvlan10 type vlan id 10 - Activate the Host. It works perfectly. Thanks, Greg Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gsher...@redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
