[ovirt-users] oVIRT 4 / OVN / Communication issues of instances between nodes.

2016-12-02 Thread Devin Acosta
Note: When I configured vdsm-tool ovn-config, I passed it the IP address of
the OVN-Controller which is using the ovirtmgmt network, which is just one
of the NIC's on the nodes.

I am opening up new thread as this I feel differs a bit from my original
request. I have OVN which I believe is deployed correctly. I have noticed
that if instances get spun up on the same oVIRT node they can all talk
without issues to one another, however if one instance gets spun up on
another node even if it has the same (OVN network/subnet), it can't ping or
reach other instances in the subnet. I noticed that the OVN-Controller of
the instance that can't talk is logging:

2016-12-02T22:50:54.907Z|00181|pinctrl|INFO|DHCPOFFER 00:1a:4a:16:01:5c
10.10.10.4
2016-12-02T22:50:54.908Z|00182|pinctrl|INFO|DHCPACK 00:1a:4a:16:01:5c
10.10.10.4
2016-12-02T22:50:55.695Z|00183|ofctrl|INFO|Dropped 7 log messages in last
10 seconds (most recently, 0 seconds ago) due to excessive rate
2016-12-02T22:50:55.695Z|00184|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:51:10.705Z|00185|ofctrl|INFO|Dropped 6 log messages in last
15 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:51:10.705Z|00186|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:51:20.710Z|00187|ofctrl|INFO|Dropped 4 log messages in last
10 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:51:20.710Z|00188|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:51:35.718Z|00189|ofctrl|INFO|Dropped 5 log messages in last
15 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:51:35.718Z|00190|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:51:45.724Z|00191|ofctrl|INFO|Dropped 3 log messages in last
10 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:51:45.724Z|00192|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:51:55.730Z|00193|ofctrl|INFO|Dropped 5 log messages in last
10 seconds (most recently, 0 seconds ago) due to excessive rate
2016-12-02T22:51:55.730Z|00194|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:52:10.738Z|00195|ofctrl|INFO|Dropped 5 log messages in last
15 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:52:10.739Z|00196|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:52:20.744Z|00197|ofctrl|INFO|Dropped 3 log messages in last
10 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:52:20.744Z|00198|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:52:35.752Z|00199|ofctrl|INFO|Dropped 5 log messages in last
15 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:52:35.752Z|00200|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)
2016-12-02T22:52:45.758Z|00201|ofctrl|INFO|Dropped 4 log messages in last
10 seconds (most recently, 5 seconds ago) due to excessive rate
2016-12-02T22:52:45.758Z|00202|ofctrl|INFO|dropping duplicate flow:
table_id=32, priority=150, reg10=0x2/0x2, actions=resubmit(,33)

>From the OVN-Controller:

[root@dev001-022-002 ~]# ovn-nbctl show
switch ddb3b92f-b359-4b59-a41a-ebae6df7fe9a (devins-net)
port 6b289418-8b8e-42b4-8334-c71584afcd3e
addresses: ["00:1a:4a:16:01:5c dynamic"]
port 71ef81f1-7c20-4c68-b536-d274703f7541
addresses: ["00:1a:4a:16:01:61 dynamic"]
port 91d4f4f5-4b9f-42c0-aa2c-8a101474bb84
addresses: ["00:1a:4a:16:01:5e dynamic"]

Do I need to do something special in order to allow communication between
nodes of instances on same OVN network?

Output of ovs-vsctl show from node3:

61af799c-a621-445e-8183-23dcb38ea3cc
Bridge br-int
fail_mode: secure
Port "ovn-456949-0"
Interface "ovn-456949-0"
type: geneve
options: {csum="true", key=flow, remote_ip="172.10.10.74"}
Port "ovn-c0dc09-0"
Interface "ovn-c0dc09-0"
type: geneve
options: {csum="true", key=flow, remote_ip="172.10.10.73"}
Port br-int
Interface br-int
type: internal
ovs_version: "2.6.90"

-- 

Devin Acosta
Red Hat Certified Architect, LinuxStack
602-354-1220 || de...@linuxguru.co
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt Websockets Proxy - noVNC

2016-12-02 Thread Bill Bill
Hello,

Attempting to get noVNC working however, it immediately disconnects with the 
error:

Server disconnected (code: 1006)

I’ve imported the certificate into the browser, but still doesn’t work. The 
status of the websockets proxy service is below. Am I missing something? I’m 
not sure what this means by bad certificate OR if that is why noVNC isn’t 
working.

///

● ovirt-websocket-proxy.service - oVirt Engine websockets proxy
   Loaded: loaded (/usr/lib/systemd/system/ovirt-websocket-proxy.service; 
enabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-12-02 15:53:39 EST; 19min ago
Main PID: 3414 (ovirt-websocket)
   CGroup: /system.slice/ovirt-websocket-proxy.service
   └─3414 /usr/bin/python 
/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py 
--systemd=notify start

Dec 02 15:53:46 ovirtcontrol ovirt-websocket-proxy.py[3414]: 
ovirt-websocket-proxy[3443] INFO msg:871 10.10.10.51: non-SSL connection 
received but disallowed
Dec 02 15:53:46 ovirtcontrol ovirt-websocket[3444]: 2016-12-02 15:53:46,690 
ovirt-websocket-proxy: INFO msg:871 10.10.10.51: non-SSL connection received 
but disallowed
Dec 02 15:53:46 ovirtcontrol ovirt-websocket-proxy.py[3414]: 
ovirt-websocket-proxy[3444] INFO msg:871 10.10.10.51: non-SSL connection 
received but disallowed
Dec 02 15:53:46 ovirtcontrol ovirt-websocket[3445]: 2016-12-02 15:53:46,750 
ovirt-websocket-proxy: INFO msg:871 10.10.10.51: non-SSL connection received 
but disallowed
Dec 02 15:53:46 ovirtcontrol ovirt-websocket-proxy.py[3414]: 
ovirt-websocket-proxy[3445] INFO msg:871 10.10.10.51: non-SSL connection 
received but disallowed
Dec 02 15:53:57 ovirtcontrol ovirt-websocket[3447]: 2016-12-02 15:53:57,292 
ovirt-websocket-proxy: INFO msg:871 handler exception: [SSL: 
SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:1936)
Dec 02 15:53:57 ovirtcontrol ovirt-websocket-proxy.py[3414]: 
ovirt-websocket-proxy[3447] INFO msg:871 handler exception: [SSL: 
SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:1936)
Dec 02 16:09:14 ovirtcontrol ovirt-websocket-proxy.py[3414]: 
ovirt-websocket-proxy[4033] INFO msg:871 10.10.10.51: non-SSL connection 
received but disallowed
Dec 02 16:12:16 ovirtcontrol ovirt-websocket[4144]: 2016-12-02 16:12:16,326 
ovirt-websocket-proxy: INFO msg:871 handler exception: [SSL: 
SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:1936)
Dec 02 16:12:16 ovirtcontrol ovirt-websocket-proxy.py[3414]: 
ovirt-websocket-proxy[4144] INFO msg:871 handler exception: [SSL: 
SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:1936)


Sent from Mail for Windows 10

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


Re: [ovirt-users] Create cinder disk via python sdk

2016-12-02 Thread Logan Kuhn
Thank you

That is exactly what I needed.  Do you know if there is more comprehensive
documentation for the 4.x Python sdk?

Regards,
Logan Kuhn

On Fri, Dec 2, 2016 at 7:35 AM, Ondra Machacek  wrote:

> On 12/02/2016 02:00 PM, Logan Kuhn wrote:
>
>> Hi
>>
>> As part of migrating from KVM to Ceph, I'm trying to create a Cinder
>> disk via the python sdk.  This is what I have so far and it fails with
>> the message that the cinder type null doesn't exist:
>>
>> disk_attachment = disk_attachments_service.add(
>> types.DiskAttachment(
>> disk=types.Disk(
>> name = 'API_Disk_Cinder_test',
>> format=types.DiskFormat.RAW,
>> provisioned_size=12 * 2**30,
>> storage_domains=[
>> types.StorageDomain(
>> name='ovirt2-cinder',
>> ),
>> ],
>> openstack_volume_type=types.OpenStackVolumeType(
>> 'ceph',
>>
>
> ^Here you should have:
>
>   name='ceph',
>
> Python SDK is using named arguments, so be carefull what you are
> actually sending.
>
>
>> openstack_volume_provider=types.OpenStackVolumeProvider('ovirt2-cinder'),
>>
>
> ^Here you should have:
>
>
> openstack_volume_provider=types.OpenStackVolumeProvider(name
> ='ovirt2-cinder'),
>
> )
>> ),
>> interface=types.DiskInterface.VIRTIO,
>> bootable=False,
>> active=True,
>> ),
>> )
>>
>> Doing it similarly with an NFS backend works so I know the connection
>> details are correct, so I didn't bother including them.
>>
>> Regards,
>>
>>
>> ___
>> 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] VM "Operating System" Type -- No Love for CentOS or Fedora?

2016-12-02 Thread Logan Kuhn
disclaimer: not a member of the ovirt project

It's probably because CentOS and Fedora are both under the Red Hat umbrella
of operating systems the same way that Kubuntu and Lubuntu and others are
under the Ubuntu umbrella.

Regards,
Logan Kuhn


On Fri, Dec 2, 2016 at 2:21 PM, Beckman, Daniel <
daniel.beck...@ingramcontent.com> wrote:

>
>
> When you edit the “operating system” type of a VM under the General
> section, there are a plethora of operating systems listed, including
> FreeBSD, Debian, SUSE, and older variants of Ubuntu. But there are two
> glaring exceptions: CentOS and Fedora. Is this by design?
>
>
>
> It’s worth noting that plain KVM, vSphere, and just about every other VM
> platform supports these (Red Hat sponsored) operating systems. But not
> oVirt. Why?
>
>
>
> Sincerely confused,
>
> Daniel
>
> ___
> 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] VM "Operating System" Type -- No Love for CentOS or Fedora?

2016-12-02 Thread Beckman, Daniel

When you edit the “operating system” type of a VM under the General section, 
there are a plethora of operating systems listed, including FreeBSD, Debian, 
SUSE, and older variants of Ubuntu. But there are two glaring exceptions: 
CentOS and Fedora. Is this by design?

It’s worth noting that plain KVM, vSphere, and just about every other VM 
platform supports these (Red Hat sponsored) operating systems. But not oVirt. 
Why?

Sincerely confused,
Daniel
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt 4.05 windows balloon service installation wrong path

2016-12-02 Thread Beckman, Daniel
On a somewhat related note, whenever I setup a Windows 2012 R2 VM and then 
install oVirt Tools (the standard one from the oVirt repo -- 
oVirt-toolsSetup_4.0-1.fc23.iso), the oVirt Guest Service fails to start. To 
get things working I have to follow this procedure:
Open Device Manager, right click on each device with a question mark (lacking a 
driver), select "update driver software", "browse my computer", specify your CD 
drive (usually D:\), then hit Next and it should pick up the appropriate driver 
for each device. After that, go to Services (also accessible under Computer 
Management) and try starting oVirt Tools – it show now start OK. Back in the 
oVirt web interface, you should notice there is now information about the VM's 
IP and installed applications.

It’s an old issue – I had to follow the same workaround back in oVirt 3.6 with 
the oVirt 3.x tools. Is there a bug open on this?

Best,
Daniel

From:  on behalf of Pavel Gashev 
Date: Thursday, December 1, 2016 at 11:46 AM
To: Simone Tiraboschi , Andrea Ghelardi 
, Lev Veyde 
Cc: "users@ovirt.org" 
Subject: Re: [ovirt-users] ovirt 4.05 windows balloon service installation 
wrong path

Please note it works like this on all server versions of Windows 
(w2k3/w2k8/w2k12/w2k16).
Also the guest tools installer doesn’t install the QEMU service, so it’s 
necessary to run
C:\Program Files (x86)\oVirt Guest Tools\drivers\guest-agent\qemu-ga-x86.exe
manually.

From:  on behalf of Simone Tiraboschi 

Date: Thursday 1 December 2016 at 20:12
To: Andrea Ghelardi , Lev Veyde 
Cc: "users@ovirt.org" 
Subject: Re: [ovirt-users] ovirt 4.05 windows balloon service installation 
wrong path



On Thu, Dec 1, 2016 at 5:00 PM, Andrea Ghelardi 
> wrote:
Hello team,
FYI standard installation of Guest tool on Windows server O.S. is somehow 
flawed.
It setups a windows service named “BalloonService” with path
C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\w2k8R2\amd64\blnsvr.exe

Unfortunately, the real path created on filesystem is
C:\Program Files (x86)\oVirt Guest Tools\drivers\Balloon\2k8R2\amd64\blnsvr.exe
(please note the missing “w” after \Baloon\ )

Thanks for the report Andrea, checking...


The easy workaround is to run this command on a “run as admin” cmd shell:
sc config BalloonService binpath= "C:\Program Files (x86)\oVirt Guest 
Tools\drivers\Balloon\2k8R2\amd64\blnsvr.exe" DisplayName= "Baloon Service 
Ovirt 4" start= auto

I suggest to fix either the command that create path during installation or the 
one which setup the service

cheers

Andrea Ghelardi

+39 050 2203 71 | www.iongroup.com | 
a.ghela...@iontrading.com
Via San Martino, 52 – 56125 Pisa - ITALY

This email and any attachments may contain information which is confidential 
and/or privileged. The information is intended exclusively for the addressee 
and the views expressed may not be official policy, but the personal views of 
the originator. If you are not the intended recipient, be aware that any 
disclosure, copying, distribution or use of the contents is prohibited. If you 
have received this email and any file transmitted with it in error, please 
notify the sender by telephone or return email immediately and delete the 
material from your computer. Internet communications are not secure and ION 
Trading is not responsible for their abuse by third parties, nor for any 
alteration or corruption in transmission, nor for any damage or loss caused by 
any virus or other defect. ION Trading accepts no liability or responsibility 
arising out of or in any way connected to this email.

[N_HBlu_small]
Automation through innovation


___
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 4 and Neutron

2016-12-02 Thread Alexander Wels
On Friday, December 2, 2016 11:44:48 AM EST Devin Acosta wrote:
> Marcin,
> 
> I installed the OVN-Central on a dedicated VM that lives on the ovirtmgmt
> network, I also installed the OVN-Provider on this same instance. I then
> installed the OVN-Controllers on all 3 of my oVirt Nodes, with the OVN
> provider driver, and configured the vdsm ovn-controller {central-ip}
> {ovirt-node-ip} on each of the boxes. It appears to be running but what I
> am noticing is that the ovs-vswitchd process is pegged at 100% on all the
> oVirt nodes.
> 
> So for instance from oVirt Node 3 (IP 75) the ovs-vsctl shows the IPs for
> the other 2 nodes in it's configuration. It seems to be that way across all
> 3 nodes, they know about the other nodes in the cluster. I was able to
> create a network inside of oVIRT using the external provider. After i
> create a subnet inside oVirt I do get an error at the top but seems to be
> ok?
> 

I can't help you with the OVN stuff, but the error at the top indicates some 
kind of bug in the UI code. If you haven't done so already can you install the 
web admin symbol maps and restart your engine

yum install ovirt-engine-webadmin-portal-debuginfo

Then recreate the issues. Then the UI.log on the engine machine will contain a 
deobfuscated stack trace that can help us in determining the cause of the UI 
issue.

> 
> [image: Inline image 2]
> 
> (Output from Node3 IP 75, of: ovs-vsctl show)
> 
> 61af799c-a621-445e-8183-23dcb38ea3cc
> Bridge br-int
> fail_mode: secure
> Port "ovn-c0dc09-0"
> Interface "ovn-c0dc09-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="172.10.10.73"}
> Port "ovn-456949-0"
> Interface "ovn-456949-0"
> type: geneve
> options: {csum="true", key=flow, remote_ip="172.10.10.74"}
> Port br-int
> Interface br-int
> type: internal
> ovs_version: "2.6.90"
> 
> 
> 
> Example where the (ovs-vswitchd) is running at 100% on all 3 oVirt Nodes.
> 
>   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
>  1768 root  10 -10   49680  10808   9388 R 100.0  0.0  24:48.85
> ovs-vswitchd
> 
> 
> [root@ovirt01 openvswitch]# tail -f ovs-vswitchd.log
> 2016-12-02T18:27:12.174Z|00604|poll_loop|INFO|Dropped 557231 log messages
> in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
> 2016-12-02T18:27:12.174Z|00605|poll_loop|INFO|wakeup due to 0-ms timeout at
> vswitchd/bridge.c:3031 (100% CPU usage)
> 2016-12-02T18:27:18.174Z|00606|poll_loop|INFO|Dropped 536053 log messages
> in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
> 2016-12-02T18:27:18.174Z|00607|poll_loop|INFO|wakeup due to 0-ms timeout at
> vswitchd/bridge.c:3031 (100% CPU usage)
> 2016-12-02T18:27:24.174Z|00608|poll_loop|INFO|Dropped 536369 log messages
> in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
> 2016-12-02T18:27:24.174Z|00609|poll_loop|INFO|wakeup due to 0-ms timeout at
> vswitchd/bridge.c:3031 (100% CPU usage)
> 2016-12-02T18:27:30.174Z|00610|poll_loop|INFO|Dropped 532134 log messages
> in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
> 2016-12-02T18:27:30.174Z|00611|poll_loop|INFO|wakeup due to 1-ms timeout at
> vswitchd/bridge.c:3031 (100% CPU usage)
> 2016-12-02T18:27:36.174Z|00612|poll_loop|INFO|Dropped 531659 log messages
> in last 6 seconds (most recently, 0 seconds ago) due to excessive rate
> 2016-12-02T18:27:36.174Z|00613|poll_loop|INFO|wakeup due to 0-ms timeout at
> vswitchd/bridge.c:3031 (99% CPU usage)
> 
> 
> One other thing that I notice is that when I got to Provision a Virtual
> Machine from the Main Data Center, my Networks don't show under the NIC
> where I could select them? Am I missing something on this?
> 
> Thanks very much for your help.
> 
> Devin Acosta
> 
> On Fri, Dec 2, 2016 at 5:16 AM, Marcin Mirecki  wrote:
> > Devin,
> > 
> > > I presume the OVN Controller should just be some VM that is on the
> > > ovirtmgmt network, or is there a preferred place to install the OVN
> > > controller software?
> > 
> > Please note the difference between OVN-Central and OVN-Controller:
> > OVN-Central is the central part of OVN, storing the logical configuration
> > and controlling the many OVN-Controllers
> > OVN-Controller is the piece of software which resides on the ovirt-hosts,
> > and manages the local OVS setup on the host.
> > 
> >  OVN-Central
> >
> >/   |  \
> >   
> >   /|   \
> >  
> >  / |\
> > 
> > /  | \
> > 
> > OVN-ControllerOVN-Controller   OVN-Controller
> > 
> > 
> > OVN-central can be installed anywhere , as long as it can communicate with
> > the engine and all the hosts.
> > During development we install it along 

Re: [ovirt-users] Problem with adding more users - engine-manage-domains is missing

2016-12-02 Thread Martin Kozl
Thank you very much, this really helped, the old versions and tutorials
confused me.

Have a great day,

Martin Kozl

2016-11-30 12:51 GMT+01:00 Martin Perina :

>
>
> On Wed, Nov 30, 2016 at 12:05 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Wed, Nov 30, 2016 at 12:02 PM, Ondra Machacek 
>> wrote:
>>
>>> On 11/29/2016 01:47 PM, Martin Kozl wrote:
>>>
 Hello,

 I am not really sure this is the right way to contact oVirt support or
 anything like that, but I would like to ask about something I have a
 problem with.

 I have my oVirt server up and running, virtualiaztion works fine,
 console is wokring and everything so the next logical step would be
 adding more users, because I am still stuck with admin user and nothing
 else. I've done my research and discovered you need to use
 engin-manage-domains to add extra domain which would host users for you
 and then you just load them in your oVirt enviroment and assign roles to
 them. However, on my server, nothing like engine-manage-domains exists,
 it only shows "command not found". I googled and found out that this
 service is automaticly isntalled when you install oVirt engine, but
 nothing like that happened on my server. I tried to reinstall, but the
 service is still missing. When installing, there are no fails or missing
 repositories. What are my options? Also, do I need another server for
 the storage of users or can it be running on the same IP as host and
 oVirt?

>>>
>>> engine-manage-domains has been depracated in 3.5 and completelly
>>> removed in 4.0.
>>>
>>>
>>
> ​Here are detailed description and usage examples of ovirt-aaa-jdbc-tool:
>
> http://www.ovirt.org/develop/release-management/features/infra/aaa-jdbc/
> ​
> If course it's possible define multiple profile server by aaa-jdbc so you
> don't to use internal for you users if you wish.
>
> Martin
>
> If in oVirt 4.0 you can refer also to similar steps as described here for
>> RHEV and for adding "internal" local domain users, configure other local
>> domains, or external providers (ldap, AD..):
>> https://access.redhat.com/documentation/en/red-hat-virtualiz
>> ation/4.0/paged/administration-guide/chapter-15-users-and-roles
>>
>> HIH,
>> Gianluca
>>
>>
>> ___
>> 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] Help! My hosted engine lost his nic!

2016-12-02 Thread Cristian Mammoli
Sorry for the repost, I don't know if the previous message got to the 
list...


Hi, I upgraded an oVirt installation a month ago to the latest 3.6.7. 
Before it was 3.6.0 if I remember correctly.

Everything went fine so far for a month or so.

A couple of days ago the the default gateway got rebooted and the 
physical server hosting the HE decided to shut down the vm because it 
could not ping the gateway.

The other host restarted the hevm but it now has *no nic*.
As a workaround I attached a virtio nic via virsh but every time the vm 
gets restarted the nic get lost


After a bit of troubleshooting and digging this is what I found:

This is the /var/run/ovirt-hosted-engine-ha/vm.conf which, as far as I 
understand, gets extracted from the HE storage domain


emulatedMachine=pc
vmId=497f5e4a-0c76-441a-b72e-724d7092d07e
smp=2
memSize=6144
spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir 


vmName=HostedEngine
display=vnc
devices={index:0,iface:virtio,format:raw,bootOrder:1,address:{slot:0x06,bus:0x00,domain:0x,type:pci,function:0x0},volumeID:bb3218ba-cbe9-4cd0-b50b-931deae992f7,imageID:d65b82e2-2ad1- 

4f4f-bfad-0277c37f2808,readonly:false,domainID:2c3585cc-b7bc-4881-85b3-aa6514991a26,deviceId:d65b82e2-2ad1-4f4f-bfad-0277c37f2808,poolID:----,device:disk, 


shared:exclusive,propagateErrors:off,type:disk}
devices={index:2,iface:ide,shared:false,readonly:true,deviceId:8c3179ac-b322-4f5c-9449-c52e3665e0ae,address:{controller:0,target:0,unit:0,bus:1,type:drive},device:cdrom,path:,type:disk} 

devices={device:cirrus,alias:video0,type:video,deviceId:a99468b6-02d4-4a77-8f94-e5df806030f6,address:{slot:0x02,bus:0x00,domain:0x,type:pci,function:0x0}} 

devices={device:virtio-serial,type:controller,deviceId:b7580676-19fb-462f-a61e-677b65ad920a,address:{slot:0x03,bus:0x00,domain:0x,type:pci,function:0x0}} 

devices={device:usb,type:controller,deviceId:c63092b3-7bd8-4b54-bcd3-51f34dce478a,address:{slot:0x01,bus:0x00,domain:0x,type:pci,function:0x2}} 

devices={device:ide,type:controller,deviceId:c77c2c01-6ccc-404b-b8d6-5a7f0631a52f,address:{slot:0x01,bus:0x00,domain:0x,type:pci,function:0x1}} 



As you can see there is no nic, and there is no nic in the qemu-kvm 
command-line:
qemu 23290 1 14 00:23 ?01:44:26 /usr/libexec/qemu-kvm 
-name HostedEngine -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off 
-cpu qemu64,-svm -m 6144 -realtime mlock=off -s
mp 2,sockets=2,cores=1,threads=1 -uuid 
497f5e4a-0c76-441a-b72e-724d7092d07e -smbios 
type=1,manufacturer=oVirt,product=oVirt 
Node,version=7-2.1511.el7.centos.2.10,serial=4C4C4544-004B-571
0-8044-B9C04F5A3732,uuid=497f5e4a-0c76-441a-b72e-724d7092d07e 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-HostedEngine/monitor.sock,serve
r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc 
base=2016-11-30T23:23:26,driftfix=slew -global 
kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -boot strict=on 
-device
 piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x3 
-drive file=/var/run/vdsm/storage/2c3585cc-b7bc-4881-85b3-aa6514
991a26/d65b82e2-2ad1-4f4f-bfad-0277c37f2808/bb3218ba-cbe9-4cd0-b50b-931deae992f7,if=none,id=drive-virtio-disk0,format=raw,serial=d65b82e2-2ad1-4f4f-bfad-0277c37f2808,cache=none,werror=st 

op,rerror=stop,aio=native -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 
-drive if=none,id=drive-ide0-1-0,readonly=on,format=raw
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 
-chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/497f5e4a-0c76-441a-b72e-724d7092d07e.com.redhat.rhevm
.vdsm,server,nowait -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm 
-chardev socket,id=charchannel1,path=/var/lib/libvirt/qem
u/channels/497f5e4a-0c76-441a-b72e-724d7092d07e.org.qemu.guest_agent.0,server,nowait 
-device 
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest
_agent.0 -chardev 
socket,id=charchannel2,path=/var/lib/libvirt/qemu/channels/497f5e4a-0c76-441a-b72e-724d7092d07e.org.ovirt.hosted-engine-setup.0,server,nowait 
-device virtserialport,bus
=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=org.ovirt.hosted-engine-setup.0 
-vnc 0:0,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -msg 
timestamp=on


I extracted the vm.conf from the storage domain and the nic is there:
mId=497f5e4a-0c76-441a-b72e-724d7092d07e
memSize=6144
display=vnc
devices={index:2,iface:ide,address:{ controller:0, target:0,unit:0, 
bus:1, 
type:drive},specParams:{},readonly:true,deviceId:857b98b3-cf43-4c2d-8061-e7f105234a65,path:,device:cdrom,shared 


:false,type:disk}

[ovirt-users] Create cinder disk via python sdk

2016-12-02 Thread Logan Kuhn
Hi

As part of migrating from KVM to Ceph, I'm trying to create a Cinder disk
via the python sdk.  This is what I have so far and it fails:

disk_attachment = disk_attachments_service.add(
types.DiskAttachment(
disk=types.Disk(
name = 'API_Disk_Cinder_test',
format=types.DiskFormat.RAW,
provisioned_size=12 * 2**30,
storage_domains=[
types.StorageDomain(
name='ovirt-cinder',
),
types.OpenStackVolumeType('cinder')
],
),
interface=types.DiskInterface.VIRTIO,
bootable=False,
active=True,
),
)

Doing it similarly with an NFS backend works so I know the connection
details are correct, so I didn't bother including them.

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


[ovirt-users] oVirt Community Newsletter: November 2016

2016-12-02 Thread Brian Proffitt
oVirt's development is continuing on pace, as the calendar year draws to a
close and we get ready for a new year of development, evangelism, and
making virtual machine management a simple process for everyone.

Here's what happened in November of 2016:

-
Software Releases
-

oVirt 4.0.6 Third Release Candidate is now available
http://bit.ly/2gOxaDm

oVirt 4.1.0 First Beta Release is now available for testing
http://bit.ly/2gOtRfa


In the Community


Testing ovirt-engine changes without a real cluster
http://www.ovirt.org/blog/2016/11/testing-ovirt-changes-without-cluster/

Request for oVirt Ansible modules testing feedback
http://bit.ly/2gOByCg


Deep Dives and Technical Discussions


Important Open Source Cloud Products [German]
http://bit.ly/2gOvWbd

Red Hat IT runs OpenShift Container Platform on Red Hat Virtualization and
Ansible
http://red.ht/2ekHcLV

Keynote: Blurring the Lines: The Continuum Between Containers and VMs
[Video]
http://bit.ly/2gOzutT

Quick Guide: How to Plan Your Red Hat Virtualization 4.0 Deployment
http://red.ht/2emiQkN

A Decade of KVM [Chinese]
http://bit.ly/2gOAuyp

Expansion of iptables Rules for oVirt 4.0 [Russian]
http://bit.ly/2gOBaUf

-- 
Brian Proffitt
Principal Community Analyst
Open Source and Standards
@TheTechScribe
574.383.9BKP
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Help! My hosted engine lost his nic!

2016-12-02 Thread Simone Tiraboschi
On Fri, Dec 2, 2016 at 5:03 PM, Cristian Mammoli  wrote:

> Out of desperation i added the missing section int the OVF I extracted and
> "tarred" it back to the storage domain. The nic now is back...
>

Unfortunately I've to tell you that the engine will periodically rewrite
the OVF_STORE based on the configuration of the VM in its DB so in
principle also this one is just a temporary solution.


>
> I don't know if the query you suggested still make sense now... :/
> Anyway I don't have any nic in the gui even now
>
> [root@ovengine ~]#  sudo -u postgres psql engine -c "select * from
> vm_device where type='interface' and vm_id='497f5e4a-0c76-441a-b72e
> -724d7092d07e'"
> could not change directory to "/root"
>   device_id   | vm_id |   type
> | device |   address|
> boot_order | spec_params | is_managed | is_plugged | is_readonly |
>  _create_date  | _update_date | alias | custom_properties | snaps
> hot_id | logical_name | is_using_scsi_reservation
> --+-
> -+---++-
> -++-
> +++-+---
> +--+---+---+--
> ---+--+---
>  6207e0d7-4dc9-406d-ab99-3facf45788f4 | 497f5e4a-0c76-441a-b72e-724d7092d07e
> | interface | bridge | {slot=0x04, bus=0x00, domain=0x, type=pci,
> function=0x0} |  0 | { } | f  | t  | f
>  | 2016-12-02 01:46:42.999885+01 |  | net0 |
>|
>|  | f
> (1 row)
>


But this seams fine now.
Adding Roy on this.


>
> [root@ovengine ~]# sudo -u postgres psql engine -c "select * from vms
> where vm_guid='497f5e4a-0c76-441a-b72e-724d7092d07e'"
> could not change directory to "/root"
>vm_name| mem_size_mb | num_of_io_threads | nice_level | cpu_shares
> |   vmt_guid   | os | description |
> free_text_comment | vds_group_id | creation_date
> | auto_startup | is_stateless | is_smartcard_enabled |
> is_delete_protected | sso_method  |
>  dedicated_vm_for_vds | fail_back | default_boot_sequence | vm_type |
> vm_pool_spice_proxy | vds_group_name | transparent_hugepages |
> trusted_service |   storage_pool_id| storage_pool_name
> |   vds_group_description| vds_group_spice_proxy | vmt_name |
> vmt_mem_size_mb | vmt_os |
>  vmt_creation_date| vmt_child_count | vmt_num_of_sockets |
> vmt_cpu_per_socket | vmt_threads_per_cpu | vmt_num_of_cpus |
> vmt_description | status | vm_ip | vm_ip_inet_array | vm_host
> | vm_pid | last_start_time | guest_cur_user_name | console_cur_user_name |
> guest_os  | co
> nsole_user_id | guest_agent_nics_hash | run_on_vds  |
> migrating_to_vds | app_list | vm_pool_name | vm_pool_id |
>   vm_guid| num_of_monitors | single_qxl_pci |
> allow_console_reconnect | is_initialized | num_of_sockets | cpu_per_socket
> | threads_per_cpu | usb_policy | acpi_enable | session | num_of_cpus |
> quota_id | quota_name | quota_enforcement_type | kvm_enable | boot_sequence
> | utc_diff | last_
> vds_run_on | client_ip | guest_requested_memory | time_zone | cpu_user |
> cpu_sys | memory_usage_history |
> cpu_usage_history
> | network_usage_history  | elapsed_time |
> usage_network_percent | disks_usage  |
> usage_mem_percent | migration_progress_percent | usage_cpu_percent |
> run_on_vds_name |vds_group_cpu_name| de
> fault_display_type | priority | iso_path | origin |
> vds_group_compatibility_version | initrd_url | kernel_url | kernel_params
> | pause_status | exit_message | exit_status | migration_support |
> predefined_properties | userdefined_properties | min_allocated_mem |
>  hash | cpu_pinning | db_generatio
> n | host_cpu_flags | tunnel_migration | vnc_keyboard_layout |
> is_run_and_pause | created_by_user_id | last_watchdog_event |
> last_watchdog_action | is_run_once |  vm_fqdn  | cpu_name |
> emulated_machine | current_cd | reason | exit_reason | instance_type_id |
> image_type_id | architecture | original_temp
> late_id | original_template_name |   last_stop_time   |
> migration_downtime | template_version_number | serial_number_policy |
> custom_serial_number | is_boot_menu_enabled | guest_cpu_count |
> next_run_config_exists | numatune_mode | is_spice_file_transfer_enabled |
> is_spice_copy_paste_enabled |
>cpu_profile_id| is_auto_converge | is_migrate_compressed |
> custom_emulated_machine | custom_cpu_name | spice_port | spice_tls_port |
> spice_ip | vnc_port | vnc_ip | guest_agent_status |
> guest_mem_buffered | guest_mem_cached 

Re: [ovirt-users] Help! My hosted engine lost his nic!

2016-12-02 Thread Cristian Mammoli
Out of desperation i added the missing section int the OVF I extracted 
and "tarred" it back to the storage domain. The nic now is back...


I don't know if the query you suggested still make sense now... :/
Anyway I don't have any nic in the gui even now

[root@ovengine ~]#  sudo -u postgres psql engine -c "select * from 
vm_device where type='interface' and 
vm_id='497f5e4a-0c76-441a-b72e-724d7092d07e'"

could not change directory to "/root"
  device_id   | vm_id |   
type| device |   
address| boot_order | spec_params | 
is_managed | is_plugged | is_readonly | _create_date  | 
_update_date | alias | custom_properties | snaps

hot_id | logical_name | is_using_scsi_reservation
--+--+---++--++-+++-+---+--+---+---+--
---+--+---
 6207e0d7-4dc9-406d-ab99-3facf45788f4 | 
497f5e4a-0c76-441a-b72e-724d7092d07e | interface | bridge | {slot=0x04, 
bus=0x00, domain=0x, type=pci, function=0x0} |  0 | { 
} | f  | t  | f   | 2016-12-02 
01:46:42.999885+01 |  | net0 |   |

   |  | f
(1 row)

[root@ovengine ~]# sudo -u postgres psql engine -c "select * from 
vms where vm_guid='497f5e4a-0c76-441a-b72e-724d7092d07e'"

could not change directory to "/root"
   vm_name| mem_size_mb | num_of_io_threads | nice_level | 
cpu_shares |   vmt_guid   | os | description | 
free_text_comment | vds_group_id | 
creation_date| auto_startup | is_stateless | 
is_smartcard_enabled | is_delete_protected | sso_method  |
 dedicated_vm_for_vds | fail_back | default_boot_sequence | vm_type | 
vm_pool_spice_proxy | vds_group_name | transparent_hugepages | 
trusted_service |   storage_pool_id| 
storage_pool_name |   vds_group_description| 
vds_group_spice_proxy | vmt_name | vmt_mem_size_mb | vmt_os |
 vmt_creation_date| vmt_child_count | vmt_num_of_sockets | 
vmt_cpu_per_socket | vmt_threads_per_cpu | vmt_num_of_cpus | 
vmt_description | status | vm_ip | vm_ip_inet_array | 
vm_host  | vm_pid | last_start_time | guest_cur_user_name | 
console_cur_user_name |  guest_os  | co
nsole_user_id | guest_agent_nics_hash | run_on_vds  | 
migrating_to_vds | app_list | vm_pool_name | vm_pool_id |
  vm_guid| num_of_monitors | single_qxl_pci | 
allow_console_reconnect | is_initialized | num_of_sockets | 
cpu_per_socket | threads_per_cpu | usb_policy | acpi_enable | session | 
num_of_cpus | quota_id | quota_name | quota_enforcement_type | 
kvm_enable | boot_sequence | utc_diff | last_
vds_run_on | client_ip | guest_requested_memory | time_zone | cpu_user | 
cpu_sys | memory_usage_history 
|cpu_usage_history
| network_usage_history  | elapsed_time | 
usage_network_percent | disks_usage  | 
usage_mem_percent | migration_progress_percent | usage_cpu_percent | 
run_on_vds_name |vds_group_cpu_name| de
fault_display_type | priority | iso_path | origin | 
vds_group_compatibility_version | initrd_url | kernel_url | 
kernel_params | pause_status | exit_message | exit_status | 
migration_support | predefined_properties | userdefined_properties | 
min_allocated_mem | hash | cpu_pinning | db_generatio
n | host_cpu_flags | tunnel_migration | vnc_keyboard_layout | 
is_run_and_pause | created_by_user_id | last_watchdog_event | 
last_watchdog_action | is_run_once |  vm_fqdn  | cpu_name | 
emulated_machine | current_cd | reason | exit_reason | instance_type_id 
| image_type_id | architecture | original_temp
late_id | original_template_name |   last_stop_time   | 
migration_downtime | template_version_number | serial_number_policy | 
custom_serial_number | is_boot_menu_enabled | guest_cpu_count | 
next_run_config_exists | numatune_mode | is_spice_file_transfer_enabled 
| is_spice_copy_paste_enabled |
   cpu_profile_id| is_auto_converge | is_migrate_compressed 
| custom_emulated_machine | custom_cpu_name | spice_port | 
spice_tls_port | spice_ip | vnc_port | vnc_ip | 
guest_agent_status | guest_mem_buffered | guest_mem_cached | 
guest_mem_free |small_icon_id |
 large_icon_id | provider_id | 
console_disconnect_action | guest_timezone_offset | guest_timezone_name 
| guestos_arch | guestos_codename | guestos_distribution |   
guestos_kernel_version   | guestos_type | guestos_version


Re: [ovirt-users] oVirt Hosted Engine Deployment Issues (and fixed!)

2016-12-02 Thread Jonathan Woytek
I've made some headway on this last night. Since I'm bootstrapping a new
network here, there are some temporary patches in place that will go away
once virtualization is running and some additional services can be spun up.
Nameservice is one of those temporary patches, as is inter-network routing.
I could dig queries on the host where I was deploying the hosted engine, so
I thought all was well. The hosted engine lives on a different network,
though, and I thought all of the routes were in place for it to get to
nameservice, but I found one missing this morning.

The error messages for these have made a lot more sense, though, so that
makes life easier!

jonathan


On Fri, Dec 2, 2016 at 8:28 AM, Tom Gamull  wrote:

> I had some similar issues (also with IPV6 which I haven’t retried
> lately).  I ended up double checking /etc/resolv.conf and just dropping an
> entry there and also ensuring the name servers were present in the ifcfg
> files.  This did the trick.  Depending on how you configure LACP, sometimes
> the DNS seems to magically disappear when ovirt creates the ovirtmgmt
> bridge interface.  If you are having an issue, it’s likely that interface.
>
> The other thing that “may” be occurring is IPv6 is being used for DNS and
> you don’t have an IPv6 DNS server (or it’s not routing correctly).  You can
> verify that by disabling IPv6 (you have to use sysctl, ifcfg options won’t
> completely do it). If that works, then IPv6 was the issue.
>
> Tom
>
> On Dec 2, 2016, at 4:18 AM, Simone Tiraboschi  wrote:
>
>
>
> On Fri, Dec 2, 2016 at 3:11 AM, Jonathan Woytek 
> wrote:
>
>> Hello all. I've been trying to get a hosted-engine style deployment up
>> and running on a small three-hypervisor cluster for prototyping some things
>> before they get moved into a production environment. My hypervisors each
>> have a 802.3ad bonded interface with several VLANs trunked over the link.
>> The network is not currently connected to the internet, but can be for
>> updates and the like. There is DNS available and correctly configured.
>>
>> I struggled for a few days trying to get the hosted engine to deploy
>> correctly. Some issues I encountered were minor documentation issues (and
>> mostly just me misinterpreting something that was written). For example,
>> when choosing an image source, I could choose cdrom, file, or something
>> else, and I tried to choose file (thinking "image file", since I had an ISO
>> to use for building the engine vm). Of course, it would bomb because it
>> wanted me to give it a preconfigured engine file, NOT an ISO. I eventually
>> figured I'd just get the appliance engine file, and went that route (and,
>> in that case, that part worked!).
>>
>> Then, it started to bomb consistently right after starting the network
>> configuration step. It turned out that the motherboards I had (Supermicro)
>> did not have UUIDs encoded on them--they were blank. As a result, the vdi
>> step was failing to gather the information it needed, but it kept dying
>> with error messages that were pretty difficult to decipher. I eventually
>> stumbled across the UUID as "None" in the return block, which finally led
>> me to dmidecode to verify that the UUID was blank. Then I had to figure out
>> how to actually get the UUID set. I found an AMI utility that helped me get
>> them set to something, though it didn't actually set them correctly. In the
>> meantime, Supermicro helpfully replied to my support request with a link to
>> a utility they provide to do the same thing (though I wish that had been
>> documented somewhere on their site!).
>>
>> UUIDs finally set, I started to work through a few other issues, and
>> finally came to the point where it was gathering some network information
>> before going to do the next step, and now it kept dying saying that the
>> hostname was not unique, then it listed every IP address configured on the
>> system (and there were several). DNS was working, and pointed to the
>> correct IP address for the hostname. The hostname was set correctly. I
>> could not get this to resolve. I got frustrated and posted on twitter. A
>> few nice people here saw it and recommended that I join the mailing list.
>> That's why I'm here now.
>>
>> Before I posted here, though, I wanted to try again when I was fresh and
>> not having dealt with all of the previous problems. My first attempt was to
>> drop the hostname into /etc/hosts, thinking maybe the install wasn't
>> consulting DNS or was confused because there were several IP addresses.
>>
>> BINGO. This fixed the "not unique" address problem!
>>
>> ... now I just had to go and clean up a botched installation because it
>> also couldn't find the hostname for the hosted engine (also in DNS, but I
>> just put it in /etc/hosts to hopefully get around whatever issue that is).
>>
>> So.. long story short.. Thanks for good software and for being so willing
>> to support it, and thanks for 

Re: [ovirt-users] Create cinder disk via python sdk

2016-12-02 Thread Ondra Machacek

On 12/02/2016 02:00 PM, Logan Kuhn wrote:

Hi

As part of migrating from KVM to Ceph, I'm trying to create a Cinder
disk via the python sdk.  This is what I have so far and it fails with
the message that the cinder type null doesn't exist:

disk_attachment = disk_attachments_service.add(
types.DiskAttachment(
disk=types.Disk(
name = 'API_Disk_Cinder_test',
format=types.DiskFormat.RAW,
provisioned_size=12 * 2**30,
storage_domains=[
types.StorageDomain(
name='ovirt2-cinder',
),
],
openstack_volume_type=types.OpenStackVolumeType(
'ceph',


^Here you should have:

  name='ceph',

Python SDK is using named arguments, so be carefull what you are
actually sending.



openstack_volume_provider=types.OpenStackVolumeProvider('ovirt2-cinder'),


^Here you should have:


openstack_volume_provider=types.OpenStackVolumeProvider(name='ovirt2-cinder'),


)
),
interface=types.DiskInterface.VIRTIO,
bootable=False,
active=True,
),
)

Doing it similarly with an NFS backend works so I know the connection
details are correct, so I didn't bother including them.

Regards,


___
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 Hosted Engine Deployment Issues (and fixed!)

2016-12-02 Thread Tom Gamull
I had some similar issues (also with IPV6 which I haven’t retried lately).  I 
ended up double checking /etc/resolv.conf and just dropping an entry there and 
also ensuring the name servers were present in the ifcfg files.  This did the 
trick.  Depending on how you configure LACP, sometimes the DNS seems to 
magically disappear when ovirt creates the ovirtmgmt bridge interface.  If you 
are having an issue, it’s likely that interface.

The other thing that “may” be occurring is IPv6 is being used for DNS and you 
don’t have an IPv6 DNS server (or it’s not routing correctly).  You can verify 
that by disabling IPv6 (you have to use sysctl, ifcfg options won’t completely 
do it). If that works, then IPv6 was the issue.

Tom

> On Dec 2, 2016, at 4:18 AM, Simone Tiraboschi  wrote:
> 
> 
> 
> On Fri, Dec 2, 2016 at 3:11 AM, Jonathan Woytek  > wrote:
> Hello all. I've been trying to get a hosted-engine style deployment up and 
> running on a small three-hypervisor cluster for prototyping some things 
> before they get moved into a production environment. My hypervisors each have 
> a 802.3ad bonded interface with several VLANs trunked over the link. The 
> network is not currently connected to the internet, but can be for updates 
> and the like. There is DNS available and correctly configured. 
> 
> I struggled for a few days trying to get the hosted engine to deploy 
> correctly. Some issues I encountered were minor documentation issues (and 
> mostly just me misinterpreting something that was written). For example, when 
> choosing an image source, I could choose cdrom, file, or something else, and 
> I tried to choose file (thinking "image file", since I had an ISO to use for 
> building the engine vm). Of course, it would bomb because it wanted me to 
> give it a preconfigured engine file, NOT an ISO. I eventually figured I'd 
> just get the appliance engine file, and went that route (and, in that case, 
> that part worked!).
> 
> Then, it started to bomb consistently right after starting the network 
> configuration step. It turned out that the motherboards I had (Supermicro) 
> did not have UUIDs encoded on them--they were blank. As a result, the vdi 
> step was failing to gather the information it needed, but it kept dying with 
> error messages that were pretty difficult to decipher. I eventually stumbled 
> across the UUID as "None" in the return block, which finally led me to 
> dmidecode to verify that the UUID was blank. Then I had to figure out how to 
> actually get the UUID set. I found an AMI utility that helped me get them set 
> to something, though it didn't actually set them correctly. In the meantime, 
> Supermicro helpfully replied to my support request with a link to a utility 
> they provide to do the same thing (though I wish that had been documented 
> somewhere on their site!). 
> 
> UUIDs finally set, I started to work through a few other issues, and finally 
> came to the point where it was gathering some network information before 
> going to do the next step, and now it kept dying saying that the hostname was 
> not unique, then it listed every IP address configured on the system (and 
> there were several). DNS was working, and pointed to the correct IP address 
> for the hostname. The hostname was set correctly. I could not get this to 
> resolve. I got frustrated and posted on twitter. A few nice people here saw 
> it and recommended that I join the mailing list. That's why I'm here now. 
> 
> Before I posted here, though, I wanted to try again when I was fresh and not 
> having dealt with all of the previous problems. My first attempt was to drop 
> the hostname into /etc/hosts, thinking maybe the install wasn't consulting 
> DNS or was confused because there were several IP addresses. 
> 
> BINGO. This fixed the "not unique" address problem! 
> 
> ... now I just had to go and clean up a botched installation because it also 
> couldn't find the hostname for the hosted engine (also in DNS, but I just put 
> it in /etc/hosts to hopefully get around whatever issue that is). 
> 
> So.. long story short.. Thanks for good software and for being so willing to 
> support it, and thanks for putting up with reading this whole thing. Now, if 
> someone can explain why DNS isn't being consulted for host names correctly, 
> that would be super... :) 
> 
> 
> It should be, absolutely.
> Would you like to share a log from one of your failure attempts?
> 
>  
> jonathan
> 
> 
> -- 
> Jonathan Woytek
> http://www.dryrose.com 
> KB3HOZ
> PGP:  462C 5F50 144D 6B09 3B65  FCE8 C1DC DEC4 E8B6 AABC
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org

[ovirt-users] Request for oVirt Ansible modules testing feedback

2016-12-02 Thread Ondra Machacek

Hello all,

I would like to kindly ask everyone who is Ansible or oVirt user for
testing of the new Ansible oVirt modules. For everyone who is familiar
with the Ansible and oVirt, this[1] describes the steps you need to do,
to setup oVirt modules library and start using those modules (Most of 
those modules will be available in Ansible 2.3, some of them are already 
in 2.2).


If you have any issue setting this up, please contact me, I will do the
best to help you.

If you have an issue, which you think is a bug, please open an issue
here[2]. Please note that Ansible is merging it's repositories, so since
next week it will actually be stored here[3]. If you are missing
anything please open an issue as well, or just contact me, and I will
do fix it. You are also very welcome to sent PR with fixes.

For those who don't have testing environment which can test against,
I've created an Vagrant project which will deploy you the oVirt instance
using Ansible playbooks. You can find how to use it here[4].

The repository also contains few examples[5], so you don't have to
copy-paste them from the source.

Thanks all for reading this and any feedback,
Ondra

[1] https://github.com/machacekondra/ovirt-tests/releases/tag/0.1
[2] https://github.com/ansible/ansible-modules-extras/issues
[3] https://github.com/ansible/ansible
[4] https://github.com/machacekondra/ovirt-tests
[5] https://github.com/machacekondra/ovirt-tests/tree/master/examples
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Create cinder disk via python sdk

2016-12-02 Thread Logan Kuhn
Hi

As part of migrating from KVM to Ceph, I'm trying to create a Cinder disk
via the python sdk.  This is what I have so far and it fails with the
message that the cinder type null doesn't exist:

disk_attachment = disk_attachments_service.add(
types.DiskAttachment(
disk=types.Disk(
name = 'API_Disk_Cinder_test',
format=types.DiskFormat.RAW,
provisioned_size=12 * 2**30,
storage_domains=[
types.StorageDomain(
name='ovirt2-cinder',
),
],
openstack_volume_type=types.OpenStackVolumeType(
'ceph',

openstack_volume_provider=types.OpenStackVolumeProvider('ovirt2-cinder'),
)
),
interface=types.DiskInterface.VIRTIO,
bootable=False,
active=True,
),
)

Doing it similarly with an NFS backend works so I know the connection
details are correct, so I didn't bother including them.

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


Re: [ovirt-users] oVirt 4 and Neutron

2016-12-02 Thread Marcin Mirecki
Devin,

> I presume the OVN Controller should just be some VM that is on the
> ovirtmgmt network, or is there a preferred place to install the OVN
> controller software?

Please note the difference between OVN-Central and OVN-Controller:
OVN-Central is the central part of OVN, storing the logical configuration and 
controlling the many OVN-Controllers
OVN-Controller is the piece of software which resides on the ovirt-hosts, and 
manages the local OVS setup on the host.

 OVN-Central
   /   |  \
  /|   \
 / |\
/  | \
OVN-ControllerOVN-Controller   OVN-Controller


OVN-central can be installed anywhere , as long as it can communicate with the 
engine and all the hosts.
During development we install it along the ovirt engine for convinience.

OVN-Controller must be installed on every ovirt host.


>I then also assume I install the OVN agents onto all
> the oVirt Nodes.

Short answer: Yes

Longe answer: If you plan not to use external networks on some clusters, you
can skip its hosts.
You can choose the clusters which support the external network by assigning the
network to clusters.

> I see
> that when you go to add the External Provider, does OVN Controller use
> authentication, is there any information I would need to have besides
> knowing which node it's on in order to add it to external provider?

For now it is only the url of the provider.
The provider is still under development, authentication is still just an
empty mock.

>Would I
> need to have any bridges or OVS configured on the nodes for this to work or
> just install the services and get them configured and it just works?

We are using the default 'br-int' bridge which OVN is using. All should be 
configured
when OVS/OVN is installed.

Let me know if I can help with anything else.
Marcin



- Original Message -
> From: "Devin Acosta" 
> To: "Marcin Mirecki" 
> Cc: "users" , "Yaniv Dary" 
> Sent: Thursday, December 1, 2016 6:19:07 PM
> Subject: Re: [ovirt-users] oVirt 4 and Neutron
> 
> I have manually created the RPM's successfully, I just want to clarify a
> few items so I make sure I'm deploying this according to best practice.
> 
> I presume the OVN Controller should just be some VM that is on the
> ovirtmgmt network, or is there a preferred place to install the OVN
> controller software? I then also assume I install the OVN agents onto all
> the oVirt Nodes. My take on this is that this OVN replaces the more complex
> Neutron/OVS installation, and makes for a more simple deployment.  I see
> that when you go to add the External Provider, does OVN Controller use
> authentication, is there any information I would need to have besides
> knowing which node it's on in order to add it to external provider? Would I
> need to have any bridges or OVS configured on the nodes for this to work or
> just install the services and get them configured and it just works?
> 
> 
> Your assistance is appreciated.
> 
> On Thu, Dec 1, 2016 at 3:54 AM, Marcin Mirecki  wrote:
> 
> > Devin,
> >
> > The openvswitch OVN packages must be build manually at the moment. It is
> > still not available either in the repos, nor as a download.
> > For now please use the procedure attached below to build the OVN rpm's.
> >
> > I am not sure where 'firewalld-system' comes from. Is it not
> > 'firewalld-filesystem'?
> > This should be available from the standard repo.
> >
> > The ovirt-provider-ovn is being developed quite actively, and the blogpost
> > is already somewhat outdated (even though it's not even a month old). I
> > will try to update it asap.
> >
> > Thanks,
> > Marcin
> >
> >
> > BUILDING PROVIDER RPMS:
> > --
> >   git clone https://gerrit.ovirt.org/ovirt-provider-ovn
> >   make rpm
> >
> >
> >
> >
> > BUILDING OVN RPMS:
> > --
> >
> > Clone the repository:
> >
> >   git clone https://github.com/openvswitch/ovs
> >
> > Install the following packages, as they are need to build ovn:
> >
> >   yum -y install gcc make python-devel openssl-devel kernel-devel graphviz
> > kernel-debug-devel autoconf automake rpm-build redhat-rpm-config rpm-build
> > rpmdevtools bash-completion autoconf automake libtool PyQt4 groff
> > libcap-ng-devel python-twisted-core python-zope-interface graphviz
> > openssl-devel selinux-policy-devel
> >
> > Build the ovn rpms:
> >
> >   cd ovs
> >   ./boot.sh
> >   ./configure
> >   make dist
> >   cp openvswitch-.tar.gz $HOME/rpmbuild/SOURCES
> >   cd $HOME/rpmbuild/SOURCES
> >   tar xzf openvswitch-.tar.gz
> >   cd openvswitch-
> >   rpmbuild -bb rhel/openvswitch-fedora.spec
> >
> > The built rpms will reside here: ~/rpmbuild/RPMS/x86_64/
> >
> > 
> >
> >
> >
> >
> >
> >
> >
> > - Original Message -
> > > From: "Yaniv Dary" 
> > > To: 

Re: [ovirt-users] can not use iscsi storage type on ovirtandGlusterfshyper-converged environment

2016-12-02 Thread 胡茂荣
I find supervdsm  used " /usr/sbin/dmsetup status" :


MainProcess|jsonrpc.Executor/2::DEBUG::2016-12-02 
17:12:16,372::supervdsmServer::92::SuperVdsm.ServerCallback::(wrapper) call 
getPathsStatus with () {}
MainProcess|jsonrpc.Executor/2::DEBUG::2016-12-02 
17:12:16,373::devicemapper::154::Storage.Misc.excCmd::(_getPathsStatus) 
/usr/bin/taskset --cpu-list 0-7 /usr/sbin/dmsetup status (cwd None)
MainProcess|jsonrpc.Executor/2::DEBUG::2016-12-02 
17:12:16,377::devicemapper::154::Storage.Misc.excCmd::(_getPathsStatus) 
SUCCESS:  = '';  = 0
MainProcess|jsonrpc.Executor/2::ERROR::2016-12-02 
17:12:16,378::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper) Error in 
getPathsStatus



problem :
how can I change  Storage.Misc.excCmd _getPathsStatus  " /usr/bin/taskset 
--cpu-list 0-7 /usr/sbin/dmsetup status"  to :


   /usr/bin/taskset --cpu-list 0-7 /usr/sbin/dmsetup status  --target multipah 


  I think add iscsi type storage ,  if supervdsm scan mulitpah will solve my 
problem .(my environment have other dm devices, use "dmsetup status" will show 
them, and vdsm get dm path status will occur error )



so I changed some as follow :
 (1)
   I  define EXT_DMSETUP_STATUS   in  
/usr/lib/python2.7/site-packages/vdsm/constants.py : 


/usr/lib/python2.7/site-packages/vdsm/constants.py:EXT_DMSETUP = 
'/usr/sbin/dmsetup'
/usr/lib/python2.7/site-packages/vdsm/constants.py:EXT_DMSETUP_STATUS = 
"/usr/sbin/dmsetup status --target multipath"


 (2)
 /usr/share/vdsm/storage/devicemapper.py add :
from vdsm.constants import EXT_DMSETUP_STATUS


and changed  getPathsStatus cmd  to " EXT_DMSETUP_STATUS" :


def _getPathsStatus():
cmd = [EXT_DMSETUP_STATUS]# before : 
cmd=[EXT_DMSETUP,"status"]

rc, out, err = misc.execCmd(cmd)
===





 but log in supervdsm log also not change . Please help me ,how to change code 
to let supervdsm exec "/usr/sbin/dmsetup status --target multipath"   in 
function  getPathsStatus() 。






 
-- Original --
From:  "胡茂荣";
Date:  Fri, Nov 25, 2016 05:44 PM
To:  "Sahina Bose"; 
Cc:  "Maor Lipchuk"; "Jeff Nelson"; 
"users"; 
Subject:  Re: [ovirt-users] can not use iscsi storage type on 
ovirtandGlusterfshyper-converged environment

 



===---

   ###vdsm or supervdsm log  report :

MainProcess|jsonrpc.Executor/7::ERROR::2016-11-01 
11:07:00,178::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper) Error in 
getPathsStatus

MainProcess|jsonrpc.Executor/4::ERROR::2016-11-01 
11:07:20,964::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper) Error in 
getPathsStatus

   some code info >
[root@horeba storage]# pwd
/usr/share/vdsm/storage


[root@horeba storage]# grep "getPathsStatus" -R ./
./devicemapper.py:def _getPathsStatus():
./devicemapper.py:def getPathsStatus():
./devicemapper.py:return getProxy().getPathsStatus()
./multipath.py:pathStatuses = devicemapper.getPathsStatus()



def _getPathsStatus():
cmd = [EXT_DMSETUP, "status"]
rc, out, err = misc.execCmd(cmd)
if rc != 0:
raise Exception("Could not get device statuses")


res = {}
for statusLine in out:
try:
devName, statusLine = statusLine.split(":", 1)
except ValueError:
if len(out) == 1:
# return an empty dict when status output is: No devices found
return res
else:
raise


for m in PATH_STATUS_RE.finditer(statusLine):
devNum, status = m.groups()
physdevName = findDev(*[int(i) for i in devNum.split(":")])
res[physdevName] = {"A": "active", "F": "failed"}[status]


return res
def getPathsStatus():
return getProxy().getPathsStatus()

=
  and flashcache dm device will error  when use getPathsStatus() function .  
could change code not check flashcache dm device ?

dmsetup info --->
[root@horebc ~]# dmsetup status
flash_sdb: 0 976771072 flashcache stats: 
reads(1388761), writes(15548965)
read hits(1235671), read hit percent(88)
write hits(6539144) write hit percent(42)
dirty write hits(21372) dirty write hit percent(0)
replacement(147711), write replacement(524881)
write invalidates(0), read invalidates(1)
pending enqueues(810), pending inval(810)
metadata dirties(15196370), metadata cleans(15196322)
metadata batch(30087377) metadata ssd writes(305315)
cleanings(15196322) fallow cleanings(48187)
no room(337139) front merge(716153) back merge(14391395)

Re: [ovirt-users] oVirt Hosted Engine Deployment Issues (and fixed!)

2016-12-02 Thread Simone Tiraboschi
On Fri, Dec 2, 2016 at 3:11 AM, Jonathan Woytek  wrote:

> Hello all. I've been trying to get a hosted-engine style deployment up and
> running on a small three-hypervisor cluster for prototyping some things
> before they get moved into a production environment. My hypervisors each
> have a 802.3ad bonded interface with several VLANs trunked over the link.
> The network is not currently connected to the internet, but can be for
> updates and the like. There is DNS available and correctly configured.
>
> I struggled for a few days trying to get the hosted engine to deploy
> correctly. Some issues I encountered were minor documentation issues (and
> mostly just me misinterpreting something that was written). For example,
> when choosing an image source, I could choose cdrom, file, or something
> else, and I tried to choose file (thinking "image file", since I had an ISO
> to use for building the engine vm). Of course, it would bomb because it
> wanted me to give it a preconfigured engine file, NOT an ISO. I eventually
> figured I'd just get the appliance engine file, and went that route (and,
> in that case, that part worked!).
>
> Then, it started to bomb consistently right after starting the network
> configuration step. It turned out that the motherboards I had (Supermicro)
> did not have UUIDs encoded on them--they were blank. As a result, the vdi
> step was failing to gather the information it needed, but it kept dying
> with error messages that were pretty difficult to decipher. I eventually
> stumbled across the UUID as "None" in the return block, which finally led
> me to dmidecode to verify that the UUID was blank. Then I had to figure out
> how to actually get the UUID set. I found an AMI utility that helped me get
> them set to something, though it didn't actually set them correctly. In the
> meantime, Supermicro helpfully replied to my support request with a link to
> a utility they provide to do the same thing (though I wish that had been
> documented somewhere on their site!).
>
> UUIDs finally set, I started to work through a few other issues, and
> finally came to the point where it was gathering some network information
> before going to do the next step, and now it kept dying saying that the
> hostname was not unique, then it listed every IP address configured on the
> system (and there were several). DNS was working, and pointed to the
> correct IP address for the hostname. The hostname was set correctly. I
> could not get this to resolve. I got frustrated and posted on twitter. A
> few nice people here saw it and recommended that I join the mailing list.
> That's why I'm here now.
>
> Before I posted here, though, I wanted to try again when I was fresh and
> not having dealt with all of the previous problems. My first attempt was to
> drop the hostname into /etc/hosts, thinking maybe the install wasn't
> consulting DNS or was confused because there were several IP addresses.
>
> BINGO. This fixed the "not unique" address problem!
>
> ... now I just had to go and clean up a botched installation because it
> also couldn't find the hostname for the hosted engine (also in DNS, but I
> just put it in /etc/hosts to hopefully get around whatever issue that is).
>
> So.. long story short.. Thanks for good software and for being so willing
> to support it, and thanks for putting up with reading this whole thing.
> Now, if someone can explain why DNS isn't being consulted for host names
> correctly, that would be super... :)
>
>
It should be, absolutely.
Would you like to share a log from one of your failure attempts?



> jonathan
>
>
> --
> Jonathan Woytek
> http://www.dryrose.com
> KB3HOZ
> PGP:  462C 5F50 144D 6B09 3B65  FCE8 C1DC DEC4 E8B6 AABC
>
> ___
> 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