Re: [ovirt-users] ovirt engine "Configure Local Storage" , why a cluster can have only one host ?
Because vdsm can only manage one storage pool, so you can't have different storage domains on the hosts in your cluster. On 2017-07-07 13:31, 转圈圈 wrote: ovirt engine "Configure Local Storage" ,why a cluster can have only one host ? ___ 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] hosted-Engine setup: hostname 'node01.example.com' doesn't uniquely match the interface selected for the management bridge
Hello,
I'm trying to install Ovirt 4 on a new set of hosts. During "hosted-engine
--deploy" I get the following error: (personal information is replaced with
generic placeholders)
[ INFO ] Stage: Setup validation
[ ERROR ] Failed to execute stage 'Setup validation': hostname
'node01.example.com' doesn't uniquely match the interface 'ens802f1' selected
for the management bridge; it matches also interface with IP
set(['192.168.99.10']). Please make sure that the hostname got from the
interface for the management network resolves only there.
[ INFO ] Stage: Clean up
[ INFO ] Generating answer file
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20160705144908.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: this system is not reliable, please
check the issue, fix and redeploy
Log file is located at
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160705144711-tl98lx.log
That IP "192.168.99.10" doesn't resolve to anything, because I haven't added it
to the DNS server. It's also not in /etc/hosts.
It's just the IP for the storage network that doesn't use DNS at all.
>From the log:
2016-07-05 14:49:08 DEBUG otopi.plugins.gr_he_common.network.bridge
bridge._get_hostname_from_bridge_if:274 Network info: {'netmask':
u'255.255.255.0', 'ipaddr': u'192.168.10.194', 'gateway': u'192.168.10.2'}
2016-07-05 14:49:08 DEBUG otopi.plugins.gr_he_common.network.bridge
bridge._get_hostname_from_bridge_if:310 hostname: 'node01.example.com',
aliaslist: '[]', ipaddrlist: '['192.168.99.10', '192.168.10.194']'
2016-07-05 14:49:08 DEBUG otopi.context context._executeMethod:142 method
exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py",
line 327, in _get_hostname_from_bridge_if
o=other_ip,
RuntimeError: hostname 'node01.example.comh' doesn't uniquely match the
interface 'ens802f1' selected for the management bridge; it matches also
interface with IP set(['192.168.99.10']). Please make sure that the hostname
got from the interface for the management network resolves only there.
2016-07-05 14:49:08 ERROR otopi.context context._executeMethod:151 Failed to
execute stage 'Setup validation': hostname 'node01.example.com' doesn't
uniquely match the interface 'ens802f1' selected for the management bridge; it
matches also interface with IP set(['192.168.99.10']). Please make sure that
the hostname got from the interface for the management network resolves only
there.
The output for dig:
[root@node01 ~]# dig node01.example.com
; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7_2.3 <<>> node01.example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45269
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;node01.example.com. IN A
;; ANSWER SECTION:
node01.example.com. 3600 IN A 192.168.10.194
;; AUTHORITY SECTION:
example.com 900 IN NS dns.example.com.
;; ADDITIONAL SECTION:
dns.example.com. 900 IN A 192.168.10.61
;; Query time: 3 msec
;; SERVER: 192.168.10.61#53(192.168.10.61)
;; WHEN: Die Jul 05 15:14:48 CEST 2016
;; MSG SIZE rcvd: 110
Output for nslookup:
[root@node01 ~]# nslookup 192.168.99.10
Server: 192.168.10.61
Address: 192.168.10.61#53
** server can't find 10.99.168.192.in-addr.arpa.: NXDOMAIN
Why does the setup script think that my hostname resolves to 192.168.99.10?
signature.asc
Description: OpenPGP digital signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Failed to create live snapshot
Hello,
I'm getting the following error when I try to create a snapshot of one VM.
Snapshots of all other VMs work as expected. I'm using oVirt 3.5 on Centos 7.
>Failed to create live snapshot 'fsbu3' for VM 'Odoo'. VM restart is
>recommended. Note that using the created snapshot might cause data
>inconsistency.
I think this is the relevant part of vdsm.log, what strikes me as odd is the
line:
>Thread-1192052::ERROR::2015-11-23 17:18:20,532::vm::4355::vm.Vm::(snapshot)
>vmId=`581cebb3-7729-4c29-b98c-f9e04aa2fdd0`::The base volume doesn't exist:
>{'device': 'disk', 'domainID': 'b4e7425a-53c7-40d4-befc-ea36ed7891fc',
>'volumeID': '9a7fc7e0-60fc-4f67-9f97-2de4bc08f0a7', 'imageID':
>'dfa1d0bf-a1f6-45bb-9574-ab020c0e8c9d'}
The part "The base volume doesn't exist" seems interesting.
Also interesting is that it does create a snapshot, though I don't know if that
snapshot is missing data.
Thread-1192048::DEBUG::2015-11-23
17:18:20,421::taskManager::103::Storage.TaskManager::(getTaskStatus) Entry.
taskID: 21a1c403-f306-40b1-bad8-377d0265ebca
Thread-1192048::DEBUG::2015-11-23
17:18:20,421::taskManager::106::Storage.TaskManager::(getTaskStatus) Return.
Response: {'code': 0, 'message': '1 jobs completed successfully', 'taskState':
'finished', 'taskResult': 'success', 'taskID':
'21a1c403-f306-40b1-bad8-377d0265ebca'}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::taskManager::123::Storage.TaskManager::(getAllTasksStatuses)
Return: {'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}
Thread-1192048::INFO::2015-11-23
17:18:20,422::logUtils::47::dispatcher::(wrapper) Run and protect:
getAllTasksStatuses, Return response: {'allTasksStatus':
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::task::1191::Storage.TaskManager.Task::(prepare)
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::finished: {'allTasksStatus':
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::task::595::Storage.TaskManager.Task::(_updateState)
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::moving from state preparing ->
state finished
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::resourceManager::977::Storage.ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::task::993::Storage.TaskManager.Task::(_decref)
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::ref 0 aborting False
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::__init__::500::jsonrpc.JsonRpcServer::(_serveRequest) Return
'Host.getAllTasksStatuses' in bridge with
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}
Thread-1192048::DEBUG::2015-11-23
17:18:20,423::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,423::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling
message
JsonRpcServer::DEBUG::2015-11-23
17:18:20,424::__init__::506::jsonrpc.JsonRpcServer::(serve_requests) Waiting
for request
Thread-1192049::DEBUG::2015-11-23
17:18:20,426::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,438::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling
message
JsonRpcServer::DEBUG::2015-11-23
17:18:20,439::__init__::506::jsonrpc.JsonRpcServer::(serve_requests) Waiting
for request
Thread-1192050::DEBUG::2015-11-23
17:18:20,441::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,442::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling
message
JsonRpcServer::DEBUG::2015-11-23
17:18:20,443::__init__::506::jsonrpc.JsonRpcServer::(serve_requests) Waiting
for request
Thread-1192051::DEBUG::2015-11-23
17:18:20,445::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,529::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling
message
Thread-1192052::DEBUG::2015-11-23
17:18:20,530::__init__::469::jsonrpc.JsonRpcServer::(_serveRequest) Calling
'VM.snapshot' in bridge with {'vmID': '581cebb3-7729-4c29-b98c-f9e04aa2fdd0',
'snapDrives': [{'baseVolumeID':
Re: [ovirt-users] VM autostart
It should do that automatically. It might take a few seconds until the HA broker has decided which host it should run on, but it should start by itself. Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von lucas castro Gesendet: Samstag, 14. März 2015 14:01 An: users@ovirt.org Betreff: [ovirt-users] VM autostart Someone knows any idea how to get the vm autostart at boot, on a hosted engine deploy ? -- contatos: Celular: ( 99 ) 9143-5954 - Vivo skype: lucasd3castro msn: lucascastrobor...@hotmail.com mailto:lucascastrobor...@hotmail.com ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] New VMs don't have network connection
Hello, New VMs can't access the network anymore, there's no ethernet device. This happens both when generating a new VM from a saved template and when installing a new VM with the blank template. It still works fine with all older VMs, they work properly even after a restart. This happens on both of my nodes. What could be causing this? signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] why is it called vdsm?
Isn't the guest agent already called ovirt-agent? -Ursprüngliche Nachricht- Von:Greg Sheremeta gsher...@redhat.com Gesendet: Fre 13 Februar 2015 18:08 An: users@ovirt.org Betreff: Re: [ovirt-users] why is it called vdsm? Le 13/02/2015 16:49, Francesco Romani a écrit : - Original Message - From: Greg Sheremeta gsher...@redhat.com To: de...@ovirt.org, users users@ovirt.org Sent: Friday, February 13, 2015 3:04:51 PM Subject: [ovirt-users] why is it called vdsm? Why is it called vdsm and not something a little more descriptive and project-related, like ovirt-agent? Well, we could think of a rename for oVirt 4.0 :) Not 100% joking: besides being a bit more google-friendlier, that could solve the packaging troubles and make old-vdsm and new-vdsm-or-whaterver-we-may-call-it trivially parallel installable on a given host. Well, that was going to be my next question -- can we rename it? I like ovirt-agent, but almost anything other than vdsm will be nicer :) From: Nathanaël Blanchet blanc...@abes.fr To: users@ovirt.org Sent: Friday, February 13, 2015 11:04:45 AM Subject: Re: [ovirt-users] why is it called vdsm? for the little story, when I began to use ovirt in 2012, a french google search gave me on the first page a full list of BDSM result, which relies to Bonding for the B letter, but in reality for masochism :) that was very funny but not very serious :) Indeed. In addition to not being descriptive or helpful, vdsm rhymes / sounds like (especially if said quickly) something we shouldn't talk about in a professional setting. This may only be true for native English speakers, and I believe vdsm originated in Israel. It's not a label that would have originated in the US due to it not being work-friendly. That awkwardness aside, ... ovirt-agent will be better for marketing, Google searches, etc. Greg ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] New Environment
Clonezilla works pretty well and it only copies used blocks, so it works fine with thin provisioned virtual disks. -Ursprüngliche Nachricht- Von:Koen Vanoppen vanoppen.k...@gmail.com Gesendet: Don 12 Februar 2015 07:24 An: users@ovirt.org Betreff: [ovirt-users] New Environment Dear all, What is the besst and quickest way to move all vms to a new ovirt environment? (new management host). Storage is located on a SAN. Kind regards, Koen ___ 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] Migration from Xenserver 6.2 to KVM.
-Ursprüngliche Nachricht- Von:Yaniv Dary yd...@redhat.com Gesendet: Die 20 Januar 2015 08:47 An: Kalil de A. Carvalho kali...@gmail.com CC: users@ovirt.org Betreff: Re: [ovirt-users] Migration from Xenserver 6.2 to KVM. --- From: Kalil de A. Carvalho kali...@gmail.com To: users@ovirt.org Sent: Monday, January 19, 2015 7:43:31 PM Subject: [ovirt-users] Migration from Xenserver 6.2 to KVM. Hello all. I work in a company that want test KVM/oVirt. The problem is the current environment running Xenserver 6.2 and is mandatory that we can migrate from the Xenserver to KVM. Research about it I saw that is not supported. I this true? You can use a v2v tool to migrate VMs from Xen to KVM, I believe. Should not be a problem. That only works if it's a GNU/Linux installation running Xen, not with Xenserver. From what I've seen, the reason for this is that Xenserver doesn't include libvirt, so v2v can't connect to it. Best regards. -- Atenciosamente, Kalil de A. Carvalho ___ 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 signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Fake power management?
Yes, pacemaker manages the engine. That part is working fine, the engine restarts on the remaining node without problems. It's just that the guests don't come back up until the powered down node has been fenced manually. -Ursprüngliche Nachricht- Von:Barak Azulay bazu...@redhat.com mailto:bazu...@redhat.com Gesendet: Mon 17 November 2014 11:35 An: Patrick Lottenbach p...@a-bot.ch mailto:p...@a-bot.ch CC: users@ovirt.org mailto:users@ovirt.org Betreff: Re: [ovirt-users] Fake power management? - Original Message - From: mots m...@nepu.moe mailto:m...@nepu.moe To: users@ovirt.org mailto:users@ovirt.org Sent: Friday, November 14, 2014 4:54:08 PM Subject: [ovirt-users] Fake power management? Fake power management? Hello, I'm building a small demonstration system for our sales team to take to a customer so that they can show them our solutions. Hardware: Two Intel NUC's, a 4 port switch and a laptop. Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by pacemaker. Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi. oVirt version: 3.5 OS: CentOS 6.6 The idea is to have our sales representative (or the potential customer himself) randomly pull the plug on one of the NUCs to show that the system stays operational when part of the hardware fails. I assume you are aware that the engine might fence the node it is running on ... Or do you use pacemaker to run the engine as well ? My problem is that I don't have any way to implement power management, so the Engine can't fence nodes and won't restart guests that were running on the node which lost power. In pacemaker I can just configure fencing over SSH or even disable the requirement to do so completely. Is there something similar for oVirt, so that the Engine will consider a node which it can't connect to to be powered down? Regards, mots ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Ubuntu/Debian support?
Hello, 1) I hope this is still an issue, mostly because I would really love to use mandos[1] on the engine, and that only works with Debian/Ubuntu. 2) Can't comment on, I'm just a user, after all. 3) Can't comment on, I'm just a user, after all. 4) Debian GNU/Linux has things in its standard repositories that are useful for very small systems. Examples: drbd and the pacemaker resource agent for iSCSI. 5) See 1) 6) Debian, mostly because of personal preferrence. 7) Engine, I think it would be useful for more users because of mandos. [1]https://wiki.recompile.se/wiki/Mandos Regards, mots -Ursprüngliche Nachricht- Von:Itamar Heim ih...@redhat.com mailto:ih...@redhat.com Gesendet: Mon 17 November 2014 11:00 An: users@ovirt.org mailto:users@ovirt.org Betreff: [ovirt-users] Ubuntu/Debian support? So, a quick non-scientific poll... Motivation: It has been suggested that adding ubuntu or debian distro support could broaden the reach of the oVirt community. To date, there has been some work towards this goal, but it is not coming to a conclusion. Questions that comes to mind: 1) Is this still an issue? 2) Can we afford to dilute the focus we have as it is hard enough to stabilize the currently supported distro's? is it worth the potential impact? 3) Would it have maintainers catering to it so it won't be left behind / delay development? 4) Why bother with host support, ovirt-node can be used? 5) Why bother with engine support, a virtual appliance or a docker image could be used? 6) if we do it, should we focus on Ubuntu or Debian distro first? 7) if we do it, should we focus on host or engine first? Thoughts? Thanks, Itamar ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt-websocket-proxy uses the wrong IP
Thank you for your reply. The engine resolves the node's IP correctly. A few details about the setup: It's a two node cluster with shared, internal storage using DRBD. The storage is managed by pacemaker, so that the node which currently serves as iscsi target gets assigned the additional IP. The Engine/websocket-proxy then always connects to the storage IP when it attempts to connect to the node which currently functions as iscsi target. This only happens in oVirt 3.5, and I was able to fix it by going back to 3.4. Regards, mots -Ursprüngliche Nachricht- Von:Simone Tiraboschi stira...@redhat.com mailto:stira...@redhat.com Gesendet: Mon 17 November 2014 18:11 An: Patrick Lottenbach p...@a-bot.ch mailto:p...@a-bot.ch CC: users@ovirt.org mailto:users@ovirt.org Betreff: Re: [ovirt-users] ovirt-websocket-proxy uses the wrong IP - Original Message - From: mots m...@nepu.moe mailto:m...@nepu.moe To: users@ovirt.org mailto:users@ovirt.org Sent: Saturday, November 15, 2014 10:24:29 PM Subject: [ovirt-users] ovirt-websocket-proxy uses the wrong IP ovirt-websocket-proxy uses the wrong IP Hello, One of my nodes has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is configured to use 10.42.0.101, yet the ovirt-websocket-proxy service tries to connect to 10.42.0.103, where no VNC server is listening. Is there any way I can configure it to use the correct address? [root@engine ˜]# /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --debug start ovirt-websocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=1838 ovirt-websocket-proxy[1838] DEBUG _daemon:404 background=False ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.conf' ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf' ovirt-websocket-proxy[1838] DEBUG _daemon:440 I am a daemon 1838 ovirt-websocket-proxy[1838] DEBUG _setLimits:377 Setting rlimits WebSocket server settings: - Listen on *:6100 The WebSocketProxy is listening on all the available IPs, so no problems on that side. - Flash security policy server - SSL/TLS support - Deny non-SSL/TLS connections - proxying from *:6100 to targets in /dummy 1: 10.42.0.1: new handler Process 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection 1: 10.42.0.1: Version hybi-13, base64: 'True' 1: 10.42.0.1: Path: '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0=' 1: connecting to: 10.42.0.103:5901 The engine is instructing the WebSocket proxy to connect to the host on the wrong IP address. Are you using an all-in-one setup where the engine, KVM and the websocketproxy are on a single machine? Can you please check how the engine machine resolve the host name? 1: handler exception: [Errno 111] Connection refused 1: Traceback (most recent call last): File /usr/lib/python2.6/site-packages/websockify/websocket.py, line 711, in top_new_client self.new_client() File /usr/lib/python2.6/site-packages/websockify/websocketproxy.py, line 183, in new_client connect=True, use_ssl=self.ssl_target, unix_socket=self.unix_target) File /usr/lib/python2.6/site-packages/websockify/websocket.py, line 188, in socket sock.connect(addrs[0][4]) File string, line 1, in connect error: [Errno 111] Connection refused Regards, mots ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Fake power management?
-Ursprüngliche Nachricht- Von:Barak Azulay bazu...@redhat.com mailto:bazu...@redhat.com Gesendet: Mon 17 November 2014 23:30 An: Patrick Lottenbach p...@a-bot.ch mailto:p...@a-bot.ch CC: users@ovirt.org mailto:users@ovirt.org Betreff: Re: AW: [ovirt-users] Fake power management? Well you can hack the solution in the form of replacing the fencing master script to always return success (Eli can help you with that), and define an imaginary fencing device on each host ... meaning that the fencing command will always succeeds. This sounds interesting. It's exactly what I need. But this may be risky ... as you might end up with the same VM running on 2 hosts. As I see it, this would only happen if someone unplugs the network interface. I know this is a way to break the cluster. If someone unplugs the interface, then everything gets started twice anyways thanks to pacemaker being configured to ignore the lack of quorum and it would look silly in front of the customer. And one last note ... when you disconnect one of the hosts in the demo you mentioned, I think you'll be better to disconnect the host that does not run the engine ... It just gets restarted on the remaining node and resumes operation. It even remembers which guests ran on which host. That part is really safe. The storage is configured to only report data as written when the write operation has finished on all (currently online) nodes, disk write caches are turned off in lvm.conf. PostreSQL is resilient enough to survive a crash like this. Or am I missing something that might break? Barak mots - Original Message - From: mots m...@nepu.moe mailto:m...@nepu.moe To: Barak Azulay bazu...@redhat.com mailto:bazu...@redhat.com Cc: users@ovirt.org mailto:users@ovirt.org Sent: Monday, November 17, 2014 12:58:20 PM Subject: AW: [ovirt-users] Fake power management? Yes, pacemaker manages the engine. That part is working fine, the engine restarts on the remaining node without problems. It's just that the guests don't come back up until the powered down node has been fenced manually. -Ursprüngliche Nachricht- Von:Barak Azulay bazu...@redhat.com mailto:bazu...@redhat.com mailto:bazu...@redhat.com mailto:bazu...@redhat.com Gesendet: Mon 17 November 2014 11:35 An: Patrick Lottenbach p...@a-bot.ch mailto:p...@a-bot.ch mailto:p...@a-bot.ch mailto:p...@a-bot.ch CC: users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org Betreff: Re: [ovirt-users] Fake power management? - Original Message - From: mots m...@nepu.moe mailto:m...@nepu.moe mailto:m...@nepu.moe mailto:m...@nepu.moe To: users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org Sent: Friday, November 14, 2014 4:54:08 PM Subject: [ovirt-users] Fake power management? Fake power management? Hello, I'm building a small demonstration system for our sales team to take to a customer so that they can show them our solutions. Hardware: Two Intel NUC's, a 4 port switch and a laptop. Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by pacemaker. Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi. oVirt version: 3.5 OS: CentOS 6.6 The idea is to have our sales representative (or the potential customer himself) randomly pull the plug on one of the NUCs to show that the system stays operational when part of the hardware fails. I assume you are aware that the engine might fence the node it is running on ... Or do you use pacemaker to run the engine as well ? My problem is that I don't have any way to implement power management, so the Engine can't fence nodes and won't restart guests that were running on the node which lost power. In pacemaker I can just configure fencing over SSH or even disable the requirement to do so completely. Is there something similar for oVirt, so that the Engine will consider a node which it can't connect to to be powered down? Regards, mots ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org mailto:Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users target=_blankhttp://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users ; signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Fake power management?
Hello Eli, If I replace /usr/bin/vdsm-tool service-restart vdsmd with echo b /proc/sysrc-trigger, will the Engine consider the node to be fenced and restart the VMs that were running on it on another node? I don't see a mechanism to inform the engine that this was a hard fencing operation and that it's save to restart the guests. Regards, mots -Ursprüngliche Nachricht- Von:Eli Mesika emes...@redhat.com mailto:emes...@redhat.com Gesendet: Son 16 November 2014 03:00 An: Patrick Lottenbach p...@a-bot.ch mailto:p...@a-bot.ch CC: users@ovirt.org mailto:users@ovirt.org Betreff: Re: [ovirt-users] Fake power management? - Original Message - From: Sandro Bonazzola sbona...@redhat.com mailto:sbona...@redhat.com To: mots m...@nepu.moe mailto:m...@nepu.moe , users@ovirt.org mailto:users@ovirt.org Sent: Friday, November 14, 2014 5:15:25 PM Subject: Re: [ovirt-users] Fake power management? Il 14/11/2014 15:54, mots ha scritto: Hello, I'm building a small demonstration system for our sales team to take to a customer so that they can show them our solutions. Hardware: Two Intel NUC's, a 4 port switch and a laptop. Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by pacemaker. Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi. oVirt version: 3.5 OS: CentOS 6.6 Just for curiosity, any reason for using pacemaker instead on oVirt Hosted Engine solution? The idea is to have our sales representative (or the potential customer himself) randomly pull the plug on one of the NUCs to show that the system stays operational when part of the hardware fails. My problem is that I don't have any way to implement power management, so the Engine can't fence nodes and won't restart guests that were running on the node which lost power. In pacemaker I can just configure fencing over SSH or even disable the requirement to do so completely. Is there something similar for oVirt, so that the Engine will consider a node which it can't connect to to be powered down? Well, we are thinking of adding such ability (Fake power management) mainly for testing purpose... Meanwhile, I think I have a work-around that may help you. When we have a connectivity issue with a node, we first try (after a grace period) to restart its VDSM via SSH this is always done before the hard-fencing (restart via the PM card) and can be done no matter if the host has PM configured or not. So basically when a connectivity issue is found, you can custom the SSH command that restarts VDSM to do whatever you want, even a script or a power-down command look at the result of psql -U engine -c select * from vdc_options where option_name ilike 'SshSoftFencingCommand' engine option_id | option_name | option_value | version ---+---+--+- 558 | SshSoftFencingCommand | service vdsmd restart | 3.0 559 | SshSoftFencingCommand | service vdsmd restart | 3.1 560 | SshSoftFencingCommand | service vdsmd restart | 3.2 561 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.3 562 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.4 563 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.5 Please note: 1) change only the value that match your cluster version 2) restart engine so change can take place 3) restore to default value again after you are done Does this may be useful for you ? Regards, mots ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ovirt-websocket-proxy uses the wrong IP
Hello, One of my nodes has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is configured to use 10.42.0.101, yet the ovirt-websocket-proxy service tries to connect to 10.42.0.103, where no VNC server is listening. Is there any way I can configure it to use the correct address? [root@engine ~]# /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --debug start ovirt-websocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=1838 ovirt-websocket-proxy[1838] DEBUG _daemon:404 background=False ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.conf' ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf' ovirt-websocket-proxy[1838] DEBUG _daemon:440 I am a daemon 1838 ovirt-websocket-proxy[1838] DEBUG _setLimits:377 Setting rlimits WebSocket server settings: - Listen on *:6100 - Flash security policy server - SSL/TLS support - Deny non-SSL/TLS connections - proxying from *:6100 to targets in /dummy 1: 10.42.0.1: new handler Process 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection 1: 10.42.0.1: Version hybi-13, base64: 'True' 1: 10.42.0.1: Path: '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0=' 1: connecting to: 10.42.0.103:5901 1: handler exception: [Errno 111] Connection refused 1: Traceback (most recent call last): File /usr/lib/python2.6/site-packages/websockify/websocket.py, line 711, in top_new_client self.new_client() File /usr/lib/python2.6/site-packages/websockify/websocketproxy.py, line 183, in new_client connect=True, use_ssl=self.ssl_target, unix_socket=self.unix_target) File /usr/lib/python2.6/site-packages/websockify/websocket.py, line 188, in socket sock.connect(addrs[0][4]) File string, line 1, in connect error: [Errno 111] Connection refused Regards, mots signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Node hypervisor
Hello, A node is a physical machine which runs your VMs. Typically you have the Engine on one (virtual) machine and multiple physical nodes to run your VMs on. I hope this helps. P.S: Please disregard the other Email, I picked the From address. Regards, mots-Ursprüngliche Nachricht- Von: Harald Wolf ov...@online.de Gesendet: Fre 14 November 2014 14:33 An: users@ovirt.org Betreff: [ovirt-users] Node hypervisor Hi, I am a oVirt newbie. I have installed oVirt Engine using Fedora 20 and the Qick Start Guide it runs fine and manage it per web interface. Now is stuck at 2.2.1 Install oVirt Node. I have installed the node hypervisor and it is working. BUT what is it good for? Whats the purpose of it? Is a ¨node¨ a end user machine that uses a virtual machine? Finally i want a Windows 7 virtualistion. -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Fake power management?
Hello, I'm building a small demonstration system for our sales team to take to a customer so that they can show them our solutions. Hardware: Two Intel NUC's, a 4 port switch and a laptop. Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by pacemaker. Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi. oVirt version: 3.5 OS: CentOS 6.6 The idea is to have our sales representative (or the potential customer himself) randomly pull the plug on one of the NUCs to show that the system stays operational when part of the hardware fails. My problem is that I don't have any way to implement power management, so the Engine can't fence nodes and won't restart guests that were running on the node which lost power. In pacemaker I can just configure fencing over SSH or even disable the requirement to do so completely. Is there something similar for oVirt, so that the Engine will consider a node which it can't connect to to be powered down? Regards, mots signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Fake power management?
Well, I haven't found a way to make sure the Engines storage comes up before the Engine is attemting to start. -Ursprüngliche Nachricht- Von:Sandro Bonazzola sbona...@redhat.com mailto:sbona...@redhat.com Gesendet: Fre 14 November 2014 16:13 An: Patrick Lottenbach p...@a-bot.ch mailto:p...@a-bot.ch ; users@ovirt.org mailto:users@ovirt.org Betreff: Re: [ovirt-users] Fake power management? Il 14/11/2014 15:54, mots ha scritto: Hello, I'm building a small demonstration system for our sales team to take to a customer so that they can show them our solutions. Hardware: Two Intel NUC's, a 4 port switch and a laptop. Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by pacemaker. Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi. oVirt version: 3.5 OS: CentOS 6.6 Just for curiosity, any reason for using pacemaker instead on oVirt Hosted Engine solution? The idea is to have our sales representative (or the potential customer himself) randomly pull the plug on one of the NUCs to show that the system stays operational when part of the hardware fails. My problem is that I don't have any way to implement power management, so the Engine can't fence nodes and won't restart guests that were running on the node which lost power. In pacemaker I can just configure fencing over SSH or even disable the requirement to do so completely. Is there something similar for oVirt, so that the Engine will consider a node which it can't connect to to be powered down? Regards, mots ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
