Re: [ovirt-users] Manually assign DC and Cluster to Blank template

2016-02-17 Thread nicolas

El 2016-02-17 22:55, Greg Padgett escribió:

On 02/16/2016 07:56 AM, nico...@devels.es wrote:

Hi,

We upgraded from oVirt 3.5 and 3.6 and deleted the Default cluster, so
now we have the Blank template with no DC and no Cluster, thus our 
users

can't use it.

Is there a way to manually set these two parameters to the current DC
and Cluster values for the Blank template? I tried editing it but see 
no

option to set them.

Thanks.

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



Hi Nicolás,

Removing the default cluster should be ok, since the templates don't
bind VMs to a DC/Cluster--you should be able to specify the DC/Cluster
when creating a VM.

HTH,
Greg


Hi Greg,

I'll elaborate a bit further on the issue. I'm attaching a screenshot of 
the 'Templates' tab on the webadmin pane - As you can see, all of them 
have a Data Center and a Cluster assigned (columns 4 and 5) but the 
Blank template (because we deleted the default DC). Even if this 
template has the 'Everyone' permission, as we're granting permissions to 
our users on the Data Center, they are not able to see the Blank 
template in the list when deploying new machines in the userportal view, 
so currently they necessarily need to choose a template from the list 
which is not Blank, and that's an issue to some of them.


That's why I was wondering if there's a manual way to assign the DC and 
Cluster to the Blank template, even modifying it directly in the DB, so 
the users see it in the userportal.


Any hint is very appreciated.

Regards,

Nicolás___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] UCS Integration (vmfex/SRIOV)

2016-02-17 Thread David LeVene
So I found some additional logs.. and from what I understand it’s trying to 
delete the ovirtmgmt network from libvirt setup.. but there’s no network 
configs in there..

ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist 
in the system")
restore-net::DEBUG::2016-02-18 
15:53:01,883::libvirtconnection::160::root::(get) trying to connect libvirt
restore-net::INFO::2016-02-18 
15:53:02,090::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV 
network device which is not persisted found at: :07:00.0.
restore-net::INFO::2016-02-18 
15:53:02,090::vdsm-restore-net-config::385::root::(restore) starting network 
restoration.
restore-net::DEBUG::2016-02-18 
15:53:02,090::vdsm-restore-net-config::193::root::(_remove_networks_in_running_config)
 Removing all networks ({'ovirtmgmt': {'remove': True}}) and bonds ({}) in 
running config.
restore-net::DEBUG::2016-02-18 
15:53:02,091::api::886::setupNetworks::(setupNetworks) Setting up network 
according to configuration: networks:{'ovirtmgmt': {'remove': True}}, 
bondings:{}, options:{'_inRollback': True, 'connectivityCheck': False}
restore-net::DEBUG::2016-02-18 15:53:02,091::api::890::root::(setupNetworks) 
Validating configuration
restore-net::DEBUG::2016-02-18 
15:53:02,239::api::900::setupNetworks::(setupNetworks) Applying...
restore-net::INFO::2016-02-18 
15:53:02,239::netconfpersistence::73::root::(setBonding) Adding bond0({'nics': 
[], 'options': 'mode=0'})
restore-net::ERROR::2016-02-18 15:53:02,240::__init__::58::root::(__exit__) 
Failed rollback transaction last known good network.
Traceback (most recent call last):
  File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
"system" % network)
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist 
in the system")
restore-net::ERROR::2016-02-18 
15:53:02,240::vdsm-restore-net-config::393::root::(restore) unified restoration 
failed.
Traceback (most recent call last):
  File "/usr/share/vdsm/vdsm-restore-net-config", line 388, in restore
unified_restoration()
  File "/usr/share/vdsm/vdsm-restore-net-config", line 110, in 
unified_restoration
_remove_networks_in_running_config()
  File "/usr/share/vdsm/vdsm-restore-net-config", line 195, in 
_remove_networks_in_running_config
_inRollback=True)
  File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks
"system" % network)
ConfigNetworkError: (27, "Cannot delete network 'ovirtmgmt': It doesn't exist 
in the system")


So.. I manually edited the /etc/sysconfig/network-scripts and setup the device 
& bridge as expected.. but vdsm didn’t like it..  it was still trying to delete 
the ovirtmgmt device.

What I ended up doing in the end is defining the network in virsh (creating 
myself an account via saslpasswd2 -a libvirt USERNAME) then creating the 
ovirtmgmt bridge
# cat vdsm-ovirtmgmt.xml

  vdsm-ovirtmgmt
  
  


#virsh net-define vdsm-ovirtmgmt.xml
#virsh net-start vdsm-ovirtmgmt

Something still wasn’t right here.. so I ended up rebooting the host…  and then 
it was working.. I’m still not entirely sure what I did to fix it.. but it’s 
working now…

I’ll continue on the journey and keep this thread updated incase anyone else 
runs into the same issues!

Cheers
David




From: David LeVene
Sent: Thursday, February 18, 2016 15:22
To: 'Michael Burman' 
Cc: users@ovirt.org
Subject: RE: [ovirt-users] UCS Integration (vmfex/SRIOV)


Hi Michael,



Thanks for this information - it's great, the guide should be updated on the 
ovirt webpage to reflect the information you've provided below.



Just to hopefully help someone else out in the future - we had only 1 vNIC 
defined in the UCS Service Profile, this caused problems when we enabled 
dynamic vnic's on that host.



The resolution was leave the initial interface as it is.. and as a management 
interface and setup another interface for the dynamic vnics. Ensure that your 
"vNIC/vHBA Placement" doesn't change either!



[cid:image001.png@01D16A64.FCDB9D60]



So in this case eth0 = ovirtmgmt bridge, and ovirt device is the vNICs.

When the system reboots after this change I’ve lost my bridge and vdsmd failed 
to start.



I manually setup the first interface again so I can talk to it again and I’ve 
even setup the bridge but I can’t get it working again? Below is what I see 
in the logs. I’ve even tried a re-installation(ovirt maint/reinstall) but no 
joy..



I’ve managed to get this working on 1 host.. but no idea what I did that was 
different!?.. If I remove the vNIC ovirt it starts working as expected - where 
can I find out some more information on what vdsm is doing?



systemd: Started Auxiliary vdsm service for running helper functions as root.

systemd: Starting Auxiliary vdsm service for running helper functions as root...

systemd: Starting Virtualization daemon...

journal: libvirt version: 1.2.17, package: 13.el7_2.2 (CentOS BuildSystem 
, 

Re: [ovirt-users] UCS Integration (vmfex/SRIOV)

2016-02-17 Thread David LeVene
Hi Michael,



Thanks for this information - it's great, the guide should be updated on the 
ovirt webpage to reflect the information you've provided below.



Just to hopefully help someone else out in the future - we had only 1 vNIC 
defined in the UCS Service Profile, this caused problems when we enabled 
dynamic vnic's on that host.



The resolution was leave the initial interface as it is.. and as a management 
interface and setup another interface for the dynamic vnics. Ensure that your 
"vNIC/vHBA Placement" doesn't change either!



[cid:image001.png@01D16A5D.E23F0A20]



So in this case eth0 = ovirtmgmt bridge, and ovirt device is the vNICs.

When the system reboots after this change I’ve lost my bridge and vdsmd failed 
to start.



I manually setup the first interface again so I can talk to it again and I’ve 
even setup the bridge but I can’t get it working again? Below is what I see 
in the logs. I’ve even tried a re-installation(ovirt maint/reinstall) but no 
joy..



I’ve managed to get this working on 1 host.. but no idea what I did that was 
different!?.. If I remove the vNIC ovirt it starts working as expected - where 
can I find out some more information on what vdsm is doing?



systemd: Started Auxiliary vdsm service for running helper functions as root.

systemd: Starting Auxiliary vdsm service for running helper functions as root...

systemd: Starting Virtualization daemon...

journal: libvirt version: 1.2.17, package: 13.el7_2.2 (CentOS BuildSystem 
, 2015-12-09-13:08:22, worker1.bsys.centos.org)

journal: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not 
accessible

systemd: Started Virtualization daemon.

systemd: Starting Virtual Desktop Server Manager network restoration...

vdsm-tool: Traceback (most recent call last):

vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 425, in 

vdsm-tool: restore(args)

vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 388, in restore

vdsm-tool: unified_restoration()

vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 110, in 
unified_restoration

vdsm-tool: _remove_networks_in_running_config()

vdsm-tool: File "/usr/share/vdsm/vdsm-restore-net-config", line 195, in 
_remove_networks_in_running_config

vdsm-tool: _inRollback=True)

vdsm-tool: File "/usr/share/vdsm/network/api.py", line 932, in setupNetworks

vdsm-tool: "system" % network)

vdsm-tool: network.errors.ConfigNetworkError: (27, "Cannot delete network 
'ovirtmgmt': It doesn't exist in the system")

vdsm-tool: Traceback (most recent call last):

vdsm-tool: File "/usr/bin/vdsm-tool", line 219, in main

vdsm-tool: return tool_command[cmd]["command"](*args)

vdsm-tool: File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", 
line 41, in restore_command

vdsm-tool: exec_restore(cmd)

vdsm-tool: File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", 
line 54, in exec_restore

vdsm-tool: raise EnvironmentError('Failed to restore the persisted networks')

vdsm-tool: EnvironmentError: Failed to restore the persisted networks

systemd: vdsm-network.service: main process exited, code=exited, 
status=1/FAILURE

systemd: Failed to start Virtual Desktop Server Manager network restoration.

systemd: Dependency failed for Virtual Desktop Server Manager.

systemd: Dependency failed for MOM instance configured for VDSM purposes.

systemd: Job mom-vdsm.service/start failed with result 'dependency'.

systemd: Job vdsmd.service/start failed with result 'dependency'.

systemd: Unit vdsm-network.service entered failed state.

systemd: vdsm-network.service failed.

systemd-logind: Removed session 5.



Cheers

David



-Original Message-

From: Michael Burman [mailto:mbur...@redhat.com]

Sent: Wednesday, February 17, 2016 16:56

To: David LeVene 
>

Cc: users@ovirt.org

Subject: Re: [ovirt-users] UCS Integration (vmfex/SRIOV)



HI David)



If everything configured properly on your UCS side and you have a working Port 
Profile id/name your next steps should be:



1) Run for example:

engine-config -s 
CustomDeviceProperties="{type=interface;prop={ifacemacspoof=^(true|false)$;queues=[1-9][0-9]*;vmfex=^[a-zA-Z0-9_.-]{2,32}$;SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}" --cver=3.5



- Restart your ovirt-engine service

- with --cver=3.5 you can specify your cluster version level. ^^

- If you don't want that it will overwrite your current attributes, you have to 
send them all as well(like on my example above). ^^



2) Install vdsm-hook-vmfex-dev on your nodes



3) In ovirt engine you can verify that host have the hooks installed under  
'Hosts' main tab - > 'Host Hooks' sub tab You should see there: a) 
before_device_migrate_destination b) before_device_create c) before_nic_hotplug

4) Create new network 

Re: [ovirt-users] "bridge port" error when setting up hosted-engine on 2nd oVirt 3.6.2 node

2016-02-17 Thread Mike DePaulo
That fixed it!

FYI: I actually obtained ovirt-hosted-engine-setup 1.3.3.3 by using
the 2016-02-17 ovirt node iso,
ovirt-node-iso-3.6-0.999.201602171021.el7.centos.iso, which contains
it.

Thank you very much,
-Mike

On Wed, Feb 17, 2016 at 9:26 AM, Simone Tiraboschi  wrote:
> Thanks Mike,
> could you please retry with ovirt-hosted-engine-setup 1.3.3.3 ?
> http://resources.ovirt.org/pub/ovirt-3.6-pre/rpm/el7/noarch/ovirt-hosted-engine-setup-1.3.3.3-1.el7.centos.noarch.rpm
> It should address also that.
>
> thanks,
> Simone
>
>
> On Wed, Feb 17, 2016 at 3:00 PM, Mike DePaulo  wrote:
>>
>> Yes, I am getting the answer files from node 1 (death-star). I've attached
>> it.
>>
>> That variable does not exist in it.
>>
>> On Wed, Feb 17, 2016 at 3:17 AM, Simone Tiraboschi 
>> wrote:
>> >
>> >
>> > On Wed, Feb 17, 2016 at 3:31 AM, Mike DePaulo 
>> > wrote:
>> >>
>> >> I tried the new build, yet the problem persists:
>> >> ovirt-node-iso-3.6-0.999.201602161021.el7.centos.iso
>> >>
>> >> Also, are you sure that commit fixes the same problem? I am not using
>> >> DHCP.
>> >
>> >
>> > Are you using an answerfile?
>> > Can you please check the value of OVEHOSTED_NETWORK/bridgeIf ?
>> >
>> >>
>> >>
>> >> -Mike
>> >>
>> >> On Tue, Feb 16, 2016 at 5:22 PM, Bond, Darryl 
>> >> wrote:
>> >> > I've got the same problem on the second hosted engine server.
>> >> >
>> >> > When you say available in tomorrows build, when will that be
>> >> > available
>> >> > for yum update using the ovirt36-pre repository?
>> >> >
>> >> >
>> >> > Darryl
>> >> >
>> >> > 
>> >> > From: users-boun...@ovirt.org  on behalf of
>> >> > Simone Tiraboschi 
>> >> > Sent: Tuesday, 16 February 2016 4:15 AM
>> >> > To: Yedidyah Bar David
>> >> > Cc: users
>> >> > Subject: Re: [ovirt-users] "bridge port" error when setting up
>> >> > hosted-engine on 2nd oVirt 3.6.2 node
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Feb 15, 2016 at 3:50 PM, Yedidyah Bar David
>> >> > > wrote:
>> >> > On Mon, Feb 15, 2016 at 4:22 PM, Mike DePaulo
>> >> > > wrote:
>> >> >> Hi,
>> >> >>
>> >> >> I am getting the following error when I attempt to setup my 2nd
>> >> >> ovirt
>> >> >> node as a hosted-engine:
>> >> >>
>> >> >> RuntimeError: The selected device None is not a supported bridge
>> >> >> port
>> >> >>
>> >> >> The 1st node is death-star (192.168.1.50)
>> >> >> The 2nd node is starkiller-base (192.168.1.52)
>> >> >>
>> >> >> This is not a production environment; this is my apartment.
>> >> >>
>> >> >> I am able to access the engine's webGUI.
>> >> >>
>> >> >> Both death-star and starkiller-base start out with only eno1 as
>> >> >> their
>> >> >> only NIC.
>> >> >> death-star, by the end of the hosted-engine-setup, had ovirtmgmt
>> >> >> also
>> >> >> (with the same MAC address.)
>> >> >> starkiller-base does not have ovirtmgmt yet.
>> >> >> I am not using VLANs.
>> >> >>
>> >> >> node version: ovirt-node-iso-3.6-0.999.201602121021.el7.centos.iso
>> >> >> engine appliance version:
>> >> >> oVirt-Engine-Appliance-CentOS-x86_64-7-20160126.ova
>> >> >
>> >> > Seems like a bug in [1] - seems like we do not configure the bridge
>> >> > anymore
>> >> > on additional host. But I didn't yet try that myself, I might be
>> >> > missing
>> >> > something. Adding Simone.
>> >> >
>> >> > [1]
>> >> >
>> >> > https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z
>> >> > --
>> >> > Didi
>> >> >
>> >> > Yes, it was a real bug: https://gerrit.ovirt.org/#/c/53428/ should
>> >> > address it.
>> >> > It should be available in tomorrow build.
>> >> >
>> >> > 
>> >> >
>> >> > The contents of this electronic message and any attachments are
>> >> > intended
>> >> > only for the addressee and may contain legally privileged, personal,
>> >> > sensitive or confidential information. If you are not the intended
>> >> > addressee, and have received this email, any transmission,
>> >> > distribution,
>> >> > downloading, printing or photocopying of the contents of this message
>> >> > or
>> >> > attachments is strictly prohibited. Any legal privilege or
>> >> > confidentiality
>> >> > attached to this message and attachments is not waived, lost or
>> >> > destroyed by
>> >> > reason of delivery to any person other than intended addressee. If
>> >> > you have
>> >> > received this message and are not the intended addressee you should
>> >> > notify
>> >> > the sender by return email and destroy all copies of the message and
>> >> > any
>> >> > attachments. Unless expressly attributed, the views expressed in this
>> >> > email
>> >> > do not necessarily represent the views of the company.
>> >> > ___
>> >> > Users mailing list
>> >> > 

Re: [ovirt-users] Manually assign DC and Cluster to Blank template

2016-02-17 Thread Greg Padgett

On 02/16/2016 07:56 AM, nico...@devels.es wrote:

Hi,

We upgraded from oVirt 3.5 and 3.6 and deleted the Default cluster, so
now we have the Blank template with no DC and no Cluster, thus our users
can't use it.

Is there a way to manually set these two parameters to the current DC
and Cluster values for the Blank template? I tried editing it but see no
option to set them.

Thanks.

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



Hi Nicolás,

Removing the default cluster should be ok, since the templates don't bind 
VMs to a DC/Cluster--you should be able to specify the DC/Cluster when 
creating a VM.


HTH,
Greg

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


Re: [ovirt-users] How does VDSM-Fake actually work?

2016-02-17 Thread Nicolás

Hi Roman,

El 16/02/16 a las 10:27, Roman Mohr escribió:
On Fri, Feb 12, 2016 at 12:45 PM, Michal Skrivanek 
> wrote:




On 09 Feb 2016, at 12:15, Nicolás > wrote:

Is there a way to get an account on mojo.redhat.com
 or is it internal? I'm trying to open
the document but credentials are required and I see no option to
create an account.


yes it is

Eldad, would you please move it to ovirt.org 
instead?


I recently played with fakevdsm myself. The result was the patch 
series in [1]. At least an updated README for the result of my patches 
can be found in [2].


Thanks,
michal



El 04/02/16 a las 13:49, emarcian escribió:

Hi,
Seems like you need to change this settings update vdc_options
set option_value='false' where option_name='InstallVds';
follow the instructions here:
https://mojo.redhat.com/docs/DOC-990399

in case you using 3.6 there is a new war (if you run the
simulator as standalone).

-Eldad


On 02/04/2016 03:04 PM, Piotr Kliczewski wrote:

Eldad is working on making it working with engine 3.6. He should be able to
give you information you need.

On Wed, Feb 3, 2016 at 12:33 PM, 
  wrote:

Anything?

El 2016-02-02 10:18, Nicolás escribió:

Hi,

  I'm trying to set up VDSM-Fake
(git://gerrit.ovirt.org/ovirt-vdsmfake.git) for some tests, however,
I'm a bit confused about how does it actually work. As the
instructions say, I was able to build the project with Maven (however,
the org.ovirt.vdsm-jsonrpc-java dependency version had to be changed
to 1.1.5 instead of 1.1.2-SNAPSHOT in pom.xml as this latter is no
longer provided at the repository).

  Once built, I run mvn jetty:run and the server started correctly:


2016-02-02 11:01:51.957:INFO::jetty-6.1.26  [1]
2016-02-02 11:01:52.804:INFO::No  [2] Transaction manager found - if
your webapp requires one, please configure one.
2016-02-02 11:01:53,424 Application initialized.
2016-02-02 11:01:53,442 Opening a Stomp server localhost:54322
2016-02-02 11:01:53.702:INFO::Started  [3]
SelectChannelConnector@0.0.0.0:54321

[INFO] Started Jetty Server
[INFO] Starting scanner at interval of 10 seconds.

  I could indeed verify it's listening on the VDSM port:


[root@host ovirt-vdsmfake]# netstat -atpn | grep 54321
tcp6   0  0
:::54321
:::*LISTEN
44870/java

  So the next step is to add a fake host via REST. I used scripts
provided here [4] and I successfully added the host, however, it
starts installing all the VDSM packages as it were a normal host and
therefore it tries to start vdsmd as well, which throws an error as
the Jetty Server is already listening on the 54321 port. I shut down
the Jetty Server and allowed oVirt Manager to install all the packages
properly, then stopped vdsmd and started the Jetty Server, but
expectedly oVirt Engine fails with message "Host xxx is non
responsive", so what I actually got is a real VDSM host and not a fake
one.

  FWIW, the fake VDSM runs on a different host, ports are reacheable
from the oVirt engine, proper /etc/hosts has been added to the engine
to reach the host, and no further customization of web.xml has been
done.

  I feel like I'm missing something here. Could someone shed some light
on what's wrong?

  Thanks.

  Nicolás



@Nicolas I would recommend you to use the top of my gerrit patches to 
run vdsmake:


  git clone git://gerrit.ovirt.org/ovirt-vdsmfake 


  cd ovirt-vdsmfake
  git fetch git://gerrit.ovirt.org/ovirt-vdsmfake 
 refs/changes/70/53570/2 && 
git checkout FETCH_HEAD


then follow the instructions in the README of the checked out 
repository [3].


Hope that helps.

Best Regards,
Roman


[1] 
https://gerrit.ovirt.org/#/q/status:open+project:ovirt-vdsmfake+branch:master+topic:easy_access

[2] https://gerrit.ovirt.org/#/c/53570/
[3] https://gerrit.ovirt.org/#/c/53570/2/README



I could finally make fakevdsm work with your changes. Maybe I'm missing 
something but this works if the engine and the fake host are run on the 
same server - when I tried to run the fake host on a different host I 
wasn't seeing any responses from the host (the firewall was vanilla 
clean). In any case, I'm ok with both running on the same machine.


Will this be merged into master?

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


[ovirt-users] How to add RAM to Hosted Engine

2016-02-17 Thread DiOrio, Max
Hi There...new oVirt user.  After a bit of a learning curve, I have things set 
up pretty well.  The web console in the hosted engine is running slow, and it's 
spiking memory to 98% frequently, but I only have 4096MB of RAM allocated.  
Currently running oVirt 3.6.

>From the web interface, it doesn't seem possible to add memory to the hosted 
>engine VM.  I can add it via the Edit menu, but then it complains that "This 
>VM is not managed by the engine".

I see that some people have said to edit /etc/ovirt-hosted-engine-ha/vm.conf  
but this file does not exist.  Then I saw someone say that the file is now 
located in /var/run/ovirt-hosted-engine-ha/vm.conf  I do see this here, but I 
can't update the file.  Each time I go to update it, it reverts back to the 
previous config.

I shut down the VM then tried to edit it, same thing.  I put the system in 
global maintenance mode, shut down the vm, then tried to edit it, same thing.

Getting frustrated over what should be a simple task, with nearly no 
documentation available.

Thanks for any help you can provide.

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


Re: [ovirt-users] Understanding direct lun connection: iscsi pass through disks

2016-02-17 Thread Raz Tamir
Hi Arman,
Check this http://www.ovirt.org/Features/Virtio-SCSI




Thanks,
Raz Tamir
Red Hat Israel

On Wed, Feb 17, 2016 at 7:12 PM, Arman Khalatyan  wrote:

> Hi, I am trying to combine performance and virtualisation with direct
> iscsi disks .
> Assuming we have vm with /dev/vda for OS two data disks from
> iscsi01:/dev/sda and iscsi02:/dev/sdb direct lun disks configured over
> ovirt interface.
> The iscsi disks are used as zfs mirror inside the vm.
> When one of the iscsi disks is not available then the whole host goes into
> pause state.
> Are there way to force ovirt do not freeze vm if direct lun is away?
> Thanks,
> Arman
>
> ___
> 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] Understanding direct lun connection: iscsi pass through disks

2016-02-17 Thread Arman Khalatyan
Hi, I am trying to combine performance and virtualisation with direct iscsi
disks .
Assuming we have vm with /dev/vda for OS two data disks from
iscsi01:/dev/sda and iscsi02:/dev/sdb direct lun disks configured over
ovirt interface.
The iscsi disks are used as zfs mirror inside the vm.
When one of the iscsi disks is not available then the whole host goes into
pause state.
Are there way to force ovirt do not freeze vm if direct lun is away?
Thanks,
Arman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Understand CPU Socket Cores and VCPU

2016-02-17 Thread Michal Skrivanek

> On 17 Feb 2016, at 17:36, Taste-Of-IT  wrote:
> 
> Hello,
> i have a general Question about Hardware CPU, Socket, Cores and the VCPU, 
> Cores per VSocket and VScoket for virtual Machines. Example i have a single 
> CPU with 4 Cores and 8 Threads. As far as i understand i should configure the 
> virtual machines with that number of socket as the host has. So in this 
> example with max 1 Socket. How is the possibility in VCPUs and VCores? What 
> is the limit in this example? Can i only run max 4 VMs?

in general - as many sockets as the number of cores you have available, minus a 
couple for the host OS(one or two should be ok)
you can run more, but then they will compete for the core and performance would 
decrease. But if those VMs are not CPU intensive it may very well be ok (you 
just need to disable the default cluster policy which limits the size to number 
of hosts’s cores)

Thanks,
michal

> 
> Thanks for clarifying
> Taste
> ___
> 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] Understand CPU Socket Cores and VCPU

2016-02-17 Thread Taste-Of-IT

Hello,
i have a general Question about Hardware CPU, Socket, Cores and the 
VCPU, Cores per VSocket and VScoket for virtual Machines. Example i have 
a single CPU with 4 Cores and 8 Threads. As far as i understand i should 
configure the virtual machines with that number of socket as the host 
has. So in this example with max 1 Socket. How is the possibility in 
VCPUs and VCores? What is the limit in this example? Can i only run max 
4 VMs?


Thanks for clarifying
Taste
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can't remove snapshot

2016-02-17 Thread Adam Litke

On 17/02/16 11:14 -0500, Greg Padgett wrote:

On 02/17/2016 03:42 AM, Rik Theys wrote:

Hi,

On 02/16/2016 10:52 PM, Greg Padgett wrote:

On 02/16/2016 08:50 AM, Rik Theys wrote:

Hi,

I'm trying to determine the correct "bad_img" uuid in my case.

The VM has two snapshots:

* The "Active VM" snapshot which has a disk that has an actual size
that's 5GB larger than the virtual size. It has a creation date that
matches the timestamp at which I created the second snapshot. The "disk
snapshot id" for this snapshot ends with dc39.

* A "before jessie upgrade" snapshot that has status "illegal". It has
an actual size that's 2GB larger than the virtual size. The creation
date matches the date the VM was initialy created. The disk snapshot id
ends with 6249.

 From the above I conclude that the disk with id that ends with 6249 is
the "bad" img I need to specify.


Similar to what I wrote to Marcelo above in the thread, I'd recommend
running the "VM disk info gathering tool" attached to [1].  It's the
best way to ensure the merge was completed and determine which image is
the "bad" one that is no longer in use by any volume chains.


I've ran the disk info gathering tool and this outputs (for the affected
VM):

VM lena
Disk b2390535-744f-4c02-bdc8-5a897226554b
(sd:a7ba2db3-517c-408a-8b27-ea45989d6416)
Volumes:
24d78600-22f4-44f7-987b-fbd866736249

The id of the volume is the ID of the snapshot that is marked "illegal".
So the "bad" image would be the dc39 one, which according to the UI is
in use by the "Active VM" snapshot. Can this make sense?


It looks accurate.  Live merges are "backwards" merges, so the merge 
would have pushed data from the volume associated with "Active VM" 
into the volume associated with the snapshot you're trying to remove.


Upon completion, we "pivot" so that the VM uses that older volume, and 
we update the engine database to reflect this (basically we 
re-associate that older volume with, in your case, "Active VM").


In your case, it seems the pivot operation was done, but the database 
wasn't updated to reflect it.  Given snapshot/image associations e.g.:


 VM Name  Snapshot Name  Volume
 ---  -  --
 My-VMActive VM  123-abc
 My-VMMy-Snapshot789-def

My-VM in your case is actually running on volume 789-def.  If you run 
the db fixup script and supply ("My-VM", "My-Snapshot", "123-abc") 
(note the volume is the newer, "bad" one), then it will switch the 
volume association for you and remove the invalid entries.


Of course, I'd shut down the VM, and back up the db beforehand.

I'm not terribly familiar with how vdsm handles block storage, but I'd 
image you could then e.g. `lvchange -an` the bad volume's LV, start 
the VM, and verify that the data is current without having the 
to-be-removed volume active, just to make sure everything lines up 
before running the vdsClient verb to remove the volume.


vdsm will reactivate the lv when starting the vm so this check will
not work.  The vm-disk-info.py script is using libvirt to check which
volumes the VM actually has open so if the 'bad' volume is not listed,
then it is not being used and is safe to remove.




Both the "Active VM" and the defective snapshot have an actual size
that's bigger than the virtual size of the disk. When I remove the bad
disk image/snapshot, will the actual size of the "Active VM" snapshot
return to the virtual size of the disk? What's currently stored in the
"Active VM" snapshot?


"Active VM" should now be unused; it previously (pre-merge) was the 
data written since the snapshot was taken.  Normally the larger actual 
size might be from qcow format overhead.  If your listing above is 
complete (ie one volume for the vm), then I'm not sure why the base 
volume would have a larger actual size than virtual size.


Adam, Nir--any thoughts on this?


There is a bug which has caused inflation of the snapshot volumes when
performing a live merge.  We are submitting fixes for 3.5, 3.6, and
master right at this moment.




Would cloning the VM (and removing the original VM afterwards) work as
an alternate way to clean this up? Or will the clone operation also
clone the snapshots?


It would try to clone everything in the engine db, so no luck there.


Regards,

Rik


If indeed the "bad" image (whichever one it is) is no longer in use,
then it's possible the image wasn't successfully removed from storage.
There are 2 ways to fix this:

  a) Run the db fixup script to remove the records for the merged image,
 and run the vdsm command by hand to remove it from storage.
  b) Adjust the db records so a merge retry would start at the right
 place, and re-run live merge.

Given that your merge retries were failing, option a) seems most likely
to succeed.  The db fixup script is attached to [1]; as parameters you
would need to provide the vm name, snapshot name, and the id of the
unused image as verified by the disk info tool.

To remove the stale LV, the vdsm 

Re: [ovirt-users] Can't remove snapshot

2016-02-17 Thread Greg Padgett

On 02/17/2016 03:42 AM, Rik Theys wrote:

Hi,

On 02/16/2016 10:52 PM, Greg Padgett wrote:

On 02/16/2016 08:50 AM, Rik Theys wrote:

Hi,

I'm trying to determine the correct "bad_img" uuid in my case.

The VM has two snapshots:

* The "Active VM" snapshot which has a disk that has an actual size
that's 5GB larger than the virtual size. It has a creation date that
matches the timestamp at which I created the second snapshot. The "disk
snapshot id" for this snapshot ends with dc39.

* A "before jessie upgrade" snapshot that has status "illegal". It has
an actual size that's 2GB larger than the virtual size. The creation
date matches the date the VM was initialy created. The disk snapshot id
ends with 6249.

  From the above I conclude that the disk with id that ends with 6249 is
the "bad" img I need to specify.


Similar to what I wrote to Marcelo above in the thread, I'd recommend
running the "VM disk info gathering tool" attached to [1].  It's the
best way to ensure the merge was completed and determine which image is
the "bad" one that is no longer in use by any volume chains.


I've ran the disk info gathering tool and this outputs (for the affected
VM):

VM lena
 Disk b2390535-744f-4c02-bdc8-5a897226554b
(sd:a7ba2db3-517c-408a-8b27-ea45989d6416)
 Volumes:
 24d78600-22f4-44f7-987b-fbd866736249

The id of the volume is the ID of the snapshot that is marked "illegal".
So the "bad" image would be the dc39 one, which according to the UI is
in use by the "Active VM" snapshot. Can this make sense?


It looks accurate.  Live merges are "backwards" merges, so the merge would 
have pushed data from the volume associated with "Active VM" into the 
volume associated with the snapshot you're trying to remove.


Upon completion, we "pivot" so that the VM uses that older volume, and we 
update the engine database to reflect this (basically we re-associate that 
older volume with, in your case, "Active VM").


In your case, it seems the pivot operation was done, but the database 
wasn't updated to reflect it.  Given snapshot/image associations e.g.:


  VM Name  Snapshot Name  Volume
  ---  -  --
  My-VMActive VM  123-abc
  My-VMMy-Snapshot789-def

My-VM in your case is actually running on volume 789-def.  If you run the 
db fixup script and supply ("My-VM", "My-Snapshot", "123-abc") (note the 
volume is the newer, "bad" one), then it will switch the volume 
association for you and remove the invalid entries.


Of course, I'd shut down the VM, and back up the db beforehand.

I'm not terribly familiar with how vdsm handles block storage, but I'd 
image you could then e.g. `lvchange -an` the bad volume's LV, start the 
VM, and verify that the data is current without having the to-be-removed 
volume active, just to make sure everything lines up before running the 
vdsClient verb to remove the volume.



Both the "Active VM" and the defective snapshot have an actual size
that's bigger than the virtual size of the disk. When I remove the bad
disk image/snapshot, will the actual size of the "Active VM" snapshot
return to the virtual size of the disk? What's currently stored in the
"Active VM" snapshot?


"Active VM" should now be unused; it previously (pre-merge) was the data 
written since the snapshot was taken.  Normally the larger actual size 
might be from qcow format overhead.  If your listing above is complete (ie 
one volume for the vm), then I'm not sure why the base volume would have a 
larger actual size than virtual size.


Adam, Nir--any thoughts on this?


Would cloning the VM (and removing the original VM afterwards) work as
an alternate way to clean this up? Or will the clone operation also
clone the snapshots?


It would try to clone everything in the engine db, so no luck there.


Regards,

Rik


If indeed the "bad" image (whichever one it is) is no longer in use,
then it's possible the image wasn't successfully removed from storage.
There are 2 ways to fix this:

   a) Run the db fixup script to remove the records for the merged image,
  and run the vdsm command by hand to remove it from storage.
   b) Adjust the db records so a merge retry would start at the right
  place, and re-run live merge.

Given that your merge retries were failing, option a) seems most likely
to succeed.  The db fixup script is attached to [1]; as parameters you
would need to provide the vm name, snapshot name, and the id of the
unused image as verified by the disk info tool.

To remove the stale LV, the vdsm deleteVolume verb would then be run
from `vdsClient` -- but note that this must be run _on the SPM host_.
It will not only perform lvremove, but also do housekeeping on other
storage metadata to keep everything consistent.  For this verb I believe
you'll need to supply not only the unused image id, but also the pool,
domain, and image group ids from your database queries.

I hope that helps.

Greg

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1306741




Re: [ovirt-users] cluster's minimum CPU level

2016-02-17 Thread Sahina Bose



On 02/17/2016 09:18 PM, supo...@logicworks.pt wrote:

I have the gluster storage already working on the first cluster.
So, when configure the second cluster, as I understand, I only need to 
Enable Gluster Service on the Cluster?


Your intention is to have hosts with a different CPU level (older) in 
the second cluster. And these hosts will be used to run VMs, IIUC. So 
you only need to Enable Virt service.


Regarding your question, on if the 2 clusters can share the same gluster 
storage domain - I don't know the answer to this.

Nir, Allon - is this supported?




Thanks


*De: *"Sahina Bose" 
*Para: *supo...@logicworks.pt, "Moti Asayag" 
*Cc: *"users" 
*Enviadas: *Quarta-feira, 17 De Fevereiro de 2016 15:37:27
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level



On 02/17/2016 08:00 PM, supo...@logicworks.pt wrote:

Hi,

If I create a second Cluster on the Data Center, can I share the
same Glusterfs storage with the Hosts on the different Clusters?


When creating a second cluster do I need to select "Import existing 
gluster configuration" and than "Enter the details of any server in 
the cluster", the details are about the Gluster storage server?


If you're already managing the gluster nodes in another cluster, 
there's no need to add it again. I'm not sure I understand the setup. 
You need to enable gluster services in the second cluster only if this 
is going to have gluster volumes running on it. To use a gluster 
volume (running on another cluster), there's no need to enable gluster 
service.




Thanks

José



*De: *supo...@logicworks.pt
*Para: *"Moti Asayag" 
*Cc: *"users" 
*Enviadas: *Quinta-feira, 11 De Fevereiro de 2016 11:07:40
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level

Any comments / suggestions?


*De: *supo...@logicworks.pt
*Para: *"Moti Asayag" 
*Cc: *"users" 
*Enviadas: *Segunda-feira, 8 De Fevereiro de 2016 15:28:33
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level

Hi Moti,

Thanks a lot. Do you think we lost functionalities? like server
migration?
The other way should be creating a new cluster, configure the old
hosts on this new cluster. Is possible to share the same GlusterFS
storage between 2 clusters? Is possible to migrate servers and
disks between the 2 clusters?

Regards

José


*De: *"Moti Asayag" 
*Para: *supo...@logicworks.pt
*Cc: *"users" 
*Enviadas: *Segunda-feira, 8 De Fevereiro de 2016 14:35:54
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level

Hi Jose,

The correct way to do it is by:
1. Putting all hosts in maintenance mode
2. Changing the cluster cpu type to the desired one
3. Install the new host
4. Activate the hosts
5. Re-run the vms



On Fri, Feb 5, 2016 at 2:24 PM, > wrote:

Hi,
 I'm trying to add a new old host (Intel(R) Xeon(R) CPU 
X3430  @ 2.40GHz Intel Nehalem Family) to oVirt Engine

Version: 3.5.4.2-1.el7.centos.
But I'm getting this error:
host does not meet the cluster's minimum CPU level. Missing
CPU features : model_SandyBridge


What happen if I lower the cluster CPU type? Do I loose
functionalities? Do I need to shutdown all VMs before change
the cluster CPU type?
Do you see any problem here?

Thanks

José


-- 


Jose Ferradeira
http://www.logicworks.pt


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




-- 
Regards,

Moti


___
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





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


Re: [ovirt-users] cluster's minimum CPU level

2016-02-17 Thread suporte
I have the gluster storage already working on the first cluster. 
So, when configure the second cluster, as I understand, I only need to Enable 
Gluster Service on the Cluster? 

Thanks 

- Mensagem original -

De: "Sahina Bose"  
Para: supo...@logicworks.pt, "Moti Asayag"  
Cc: "users"  
Enviadas: Quarta-feira, 17 De Fevereiro de 2016 15:37:27 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 



On 02/17/2016 08:00 PM, supo...@logicworks.pt wrote: 



Hi, 

If I create a second Cluster on the Data Center, can I share the same Glusterfs 
storage with the Hosts on the different Clusters? 



When creating a second cluster do I need to select " Import existing gluster 
configuration " and than "Enter the details of any server in the cluster", the 
details are about the Gluster storage server? 

If you're already managing the gluster nodes in another cluster, there's no 
need to add it again. I'm not sure I understand the setup. You need to enable 
gluster services in the second cluster only if this is going to have gluster 
volumes running on it. To use a gluster volume (running on another cluster), 
there's no need to enable gluster service. 






Thanks 

José 


- Mensagem original -

De: supo...@logicworks.pt 
Para: "Moti Asayag"  
Cc: "users"  
Enviadas: Quinta-feira, 11 De Fevereiro de 2016 11:07:40 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 

Any comments / suggestions? 

- Mensagem original -

De: supo...@logicworks.pt 
Para: "Moti Asayag"  
Cc: "users"  
Enviadas: Segunda-feira, 8 De Fevereiro de 2016 15:28:33 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 

Hi Moti, 

Thanks a lot. Do you think we lost functionalities? like server migration? 
The other way should be creating a new cluster, configure the old hosts on this 
new cluster. Is possible to share the same GlusterFS storage between 2 
clusters? Is possible to migrate servers and disks between the 2 clusters? 

Regards 

José 

- Mensagem original -

De: "Moti Asayag"  
Para: supo...@logicworks.pt 
Cc: "users"  
Enviadas: Segunda-feira, 8 De Fevereiro de 2016 14:35:54 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 

Hi Jose, 

The correct way to do it is by: 
1. Putting all hosts in maintenance mode 
2. Changing the cluster cpu type to the desired one 
3. Install the new host 
4. Activate the hosts 
5. Re-run the vms 



On Fri, Feb 5, 2016 at 2:24 PM, < supo...@logicworks.pt > wrote: 



Hi, 
I'm trying to add a new old host (Intel(R) Xeon(R) CPU X3430 @ 2.40GHz Intel 
Nehalem Family) to oVirt Engine Version: 3.5.4.2-1.el7.centos. 
But I'm getting this error: 
host does not meet the cluster's minimum CPU level. Missing CPU features : 
model_SandyBridge 


What happen if I lower the cluster CPU type? Do I loose functionalities? Do I 
need to shutdown all VMs before change the cluster CPU type? 
Do you see any problem here? 

Thanks 

José 


-- 

Jose Ferradeira 
http://www.logicworks.pt 


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







-- 
Regards, 
Moti 


___ 
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 




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


Re: [ovirt-users] cluster's minimum CPU level

2016-02-17 Thread Sahina Bose



On 02/17/2016 08:00 PM, supo...@logicworks.pt wrote:

Hi,

If I create a second Cluster on the Data Center, can I share the same 
Glusterfs storage with the Hosts on the different Clusters?


When creating a second cluster do I need to select "Import existing 
gluster configuration" and than "Enter the details of any server in the 
cluster", the details are about the Gluster storage server?


If you're already managing the gluster nodes in another cluster, there's 
no need to add it again. I'm not sure I understand the setup. You need 
to enable gluster services in the second cluster only if this is going 
to have gluster volumes running on it. To use a gluster volume (running 
on another cluster), there's no need to enable gluster service.





Thanks

José



*De: *supo...@logicworks.pt
*Para: *"Moti Asayag" 
*Cc: *"users" 
*Enviadas: *Quinta-feira, 11 De Fevereiro de 2016 11:07:40
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level

Any comments / suggestions?


*De: *supo...@logicworks.pt
*Para: *"Moti Asayag" 
*Cc: *"users" 
*Enviadas: *Segunda-feira, 8 De Fevereiro de 2016 15:28:33
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level

Hi Moti,

Thanks a lot. Do you think we lost functionalities? like server migration?
The other way should be creating a new cluster, configure the old 
hosts on this new cluster. Is possible to share the same GlusterFS 
storage between 2 clusters? Is possible to migrate servers and disks 
between the 2 clusters?


Regards

José


*De: *"Moti Asayag" 
*Para: *supo...@logicworks.pt
*Cc: *"users" 
*Enviadas: *Segunda-feira, 8 De Fevereiro de 2016 14:35:54
*Assunto: *Re: [ovirt-users] cluster's minimum CPU level

Hi Jose,

The correct way to do it is by:
1. Putting all hosts in maintenance mode
2. Changing the cluster cpu type to the desired one
3. Install the new host
4. Activate the hosts
5. Re-run the vms



On Fri, Feb 5, 2016 at 2:24 PM, > wrote:


Hi,
 I'm trying to add a new old host (Intel(R) Xeon(R) CPU  X3430  @
2.40GHz Intel Nehalem Family) to oVirt Engine Version:
3.5.4.2-1.el7.centos.
But I'm getting this error:
host does not meet the cluster's minimum CPU level. Missing CPU
features : model_SandyBridge


What happen if I lower the cluster CPU type? Do I loose
functionalities? Do I need to shutdown all VMs before change the
cluster CPU type?
Do you see any problem here?

Thanks

José


-- 


Jose Ferradeira
http://www.logicworks.pt


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




--
Regards,
Moti


___
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


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


Re: [ovirt-users] cluster's minimum CPU level

2016-02-17 Thread suporte
Hi, 

If I create a second Cluster on the Data Center, can I share the same Glusterfs 
storage with the Hosts on the different Clusters? 
When creating a second cluster do I need to select " Import existing gluster 
configuration " and than "Enter the details of any server in the cluster", the 
details are about the Gluster storage server? 


Thanks 

José 


- Mensagem original -

De: supo...@logicworks.pt 
Para: "Moti Asayag"  
Cc: "users"  
Enviadas: Quinta-feira, 11 De Fevereiro de 2016 11:07:40 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 

Any comments / suggestions? 

- Mensagem original -

De: supo...@logicworks.pt 
Para: "Moti Asayag"  
Cc: "users"  
Enviadas: Segunda-feira, 8 De Fevereiro de 2016 15:28:33 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 

Hi Moti, 

Thanks a lot. Do you think we lost functionalities? like server migration? 
The other way should be creating a new cluster, configure the old hosts on this 
new cluster. Is possible to share the same GlusterFS storage between 2 
clusters? Is possible to migrate servers and disks between the 2 clusters? 

Regards 

José 

- Mensagem original -

De: "Moti Asayag"  
Para: supo...@logicworks.pt 
Cc: "users"  
Enviadas: Segunda-feira, 8 De Fevereiro de 2016 14:35:54 
Assunto: Re: [ovirt-users] cluster's minimum CPU level 

Hi Jose, 

The correct way to do it is by: 
1. Putting all hosts in maintenance mode 
2. Changing the cluster cpu type to the desired one 
3. Install the new host 
4. Activate the hosts 
5. Re-run the vms 



On Fri, Feb 5, 2016 at 2:24 PM, < supo...@logicworks.pt > wrote: 



Hi, 
I'm trying to add a new old host (Intel(R) Xeon(R) CPU X3430 @ 2.40GHz Intel 
Nehalem Family) to oVirt Engine Version: 3.5.4.2-1.el7.centos. 
But I'm getting this error: 
host does not meet the cluster's minimum CPU level. Missing CPU features : 
model_SandyBridge 


What happen if I lower the cluster CPU type? Do I loose functionalities? Do I 
need to shutdown all VMs before change the cluster CPU type? 
Do you see any problem here? 

Thanks 

José 


-- 

Jose Ferradeira 
http://www.logicworks.pt 


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







-- 
Regards, 
Moti 


___ 
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] "bridge port" error when setting up hosted-engine on 2nd oVirt 3.6.2 node

2016-02-17 Thread Simone Tiraboschi
Thanks Mike,
could you please retry with ovirt-hosted-engine-setup 1.3.3.3 ?
http://resources.ovirt.org/pub/ovirt-3.6-pre/rpm/el7/noarch/ovirt-hosted-engine-setup-1.3.3.3-1.el7.centos.noarch.rpm
It should address also that.

thanks,
Simone


On Wed, Feb 17, 2016 at 3:00 PM, Mike DePaulo  wrote:

> Yes, I am getting the answer files from node 1 (death-star). I've attached
> it.
>
> That variable does not exist in it.
>
> On Wed, Feb 17, 2016 at 3:17 AM, Simone Tiraboschi 
> wrote:
> >
> >
> > On Wed, Feb 17, 2016 at 3:31 AM, Mike DePaulo 
> wrote:
> >>
> >> I tried the new build, yet the problem persists:
> >> ovirt-node-iso-3.6-0.999.201602161021.el7.centos.iso
> >>
> >> Also, are you sure that commit fixes the same problem? I am not using
> >> DHCP.
> >
> >
> > Are you using an answerfile?
> > Can you please check the value of OVEHOSTED_NETWORK/bridgeIf ?
> >
> >>
> >>
> >> -Mike
> >>
> >> On Tue, Feb 16, 2016 at 5:22 PM, Bond, Darryl 
> wrote:
> >> > I've got the same problem on the second hosted engine server.
> >> >
> >> > When you say available in tomorrows build, when will that be available
> >> > for yum update using the ovirt36-pre repository?
> >> >
> >> >
> >> > Darryl
> >> >
> >> > 
> >> > From: users-boun...@ovirt.org  on behalf of
> >> > Simone Tiraboschi 
> >> > Sent: Tuesday, 16 February 2016 4:15 AM
> >> > To: Yedidyah Bar David
> >> > Cc: users
> >> > Subject: Re: [ovirt-users] "bridge port" error when setting up
> >> > hosted-engine on 2nd oVirt 3.6.2 node
> >> >
> >> >
> >> >
> >> > On Mon, Feb 15, 2016 at 3:50 PM, Yedidyah Bar David
> >> > > wrote:
> >> > On Mon, Feb 15, 2016 at 4:22 PM, Mike DePaulo
> >> > > wrote:
> >> >> Hi,
> >> >>
> >> >> I am getting the following error when I attempt to setup my 2nd ovirt
> >> >> node as a hosted-engine:
> >> >>
> >> >> RuntimeError: The selected device None is not a supported bridge port
> >> >>
> >> >> The 1st node is death-star (192.168.1.50)
> >> >> The 2nd node is starkiller-base (192.168.1.52)
> >> >>
> >> >> This is not a production environment; this is my apartment.
> >> >>
> >> >> I am able to access the engine's webGUI.
> >> >>
> >> >> Both death-star and starkiller-base start out with only eno1 as their
> >> >> only NIC.
> >> >> death-star, by the end of the hosted-engine-setup, had ovirtmgmt also
> >> >> (with the same MAC address.)
> >> >> starkiller-base does not have ovirtmgmt yet.
> >> >> I am not using VLANs.
> >> >>
> >> >> node version: ovirt-node-iso-3.6-0.999.201602121021.el7.centos.iso
> >> >> engine appliance version:
> >> >> oVirt-Engine-Appliance-CentOS-x86_64-7-20160126.ova
> >> >
> >> > Seems like a bug in [1] - seems like we do not configure the bridge
> >> > anymore
> >> > on additional host. But I didn't yet try that myself, I might be
> missing
> >> > something. Adding Simone.
> >> >
> >> > [1]
> >> >
> https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z
> >> > --
> >> > Didi
> >> >
> >> > Yes, it was a real bug: https://gerrit.ovirt.org/#/c/53428/ should
> >> > address it.
> >> > It should be available in tomorrow build.
> >> >
> >> > 
> >> >
> >> > The contents of this electronic message and any attachments are
> intended
> >> > only for the addressee and may contain legally privileged, personal,
> >> > sensitive or confidential information. If you are not the intended
> >> > addressee, and have received this email, any transmission,
> distribution,
> >> > downloading, printing or photocopying of the contents of this message
> or
> >> > attachments is strictly prohibited. Any legal privilege or
> confidentiality
> >> > attached to this message and attachments is not waived, lost or
> destroyed by
> >> > reason of delivery to any person other than intended addressee. If
> you have
> >> > received this message and are not the intended addressee you should
> notify
> >> > the sender by return email and destroy all copies of the message and
> any
> >> > attachments. Unless expressly attributed, the views expressed in this
> email
> >> > do not necessarily represent the views of the company.
> >> > ___
> >> > 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] "bridge port" error when setting up hosted-engine on 2nd oVirt 3.6.2 node

2016-02-17 Thread Mike DePaulo
Yes, I am getting the answer files from node 1 (death-star). I've attached it.

That variable does not exist in it.

On Wed, Feb 17, 2016 at 3:17 AM, Simone Tiraboschi  wrote:
>
>
> On Wed, Feb 17, 2016 at 3:31 AM, Mike DePaulo  wrote:
>>
>> I tried the new build, yet the problem persists:
>> ovirt-node-iso-3.6-0.999.201602161021.el7.centos.iso
>>
>> Also, are you sure that commit fixes the same problem? I am not using
>> DHCP.
>
>
> Are you using an answerfile?
> Can you please check the value of OVEHOSTED_NETWORK/bridgeIf ?
>
>>
>>
>> -Mike
>>
>> On Tue, Feb 16, 2016 at 5:22 PM, Bond, Darryl  wrote:
>> > I've got the same problem on the second hosted engine server.
>> >
>> > When you say available in tomorrows build, when will that be available
>> > for yum update using the ovirt36-pre repository?
>> >
>> >
>> > Darryl
>> >
>> > 
>> > From: users-boun...@ovirt.org  on behalf of
>> > Simone Tiraboschi 
>> > Sent: Tuesday, 16 February 2016 4:15 AM
>> > To: Yedidyah Bar David
>> > Cc: users
>> > Subject: Re: [ovirt-users] "bridge port" error when setting up
>> > hosted-engine on 2nd oVirt 3.6.2 node
>> >
>> >
>> >
>> > On Mon, Feb 15, 2016 at 3:50 PM, Yedidyah Bar David
>> > > wrote:
>> > On Mon, Feb 15, 2016 at 4:22 PM, Mike DePaulo
>> > > wrote:
>> >> Hi,
>> >>
>> >> I am getting the following error when I attempt to setup my 2nd ovirt
>> >> node as a hosted-engine:
>> >>
>> >> RuntimeError: The selected device None is not a supported bridge port
>> >>
>> >> The 1st node is death-star (192.168.1.50)
>> >> The 2nd node is starkiller-base (192.168.1.52)
>> >>
>> >> This is not a production environment; this is my apartment.
>> >>
>> >> I am able to access the engine's webGUI.
>> >>
>> >> Both death-star and starkiller-base start out with only eno1 as their
>> >> only NIC.
>> >> death-star, by the end of the hosted-engine-setup, had ovirtmgmt also
>> >> (with the same MAC address.)
>> >> starkiller-base does not have ovirtmgmt yet.
>> >> I am not using VLANs.
>> >>
>> >> node version: ovirt-node-iso-3.6-0.999.201602121021.el7.centos.iso
>> >> engine appliance version:
>> >> oVirt-Engine-Appliance-CentOS-x86_64-7-20160126.ova
>> >
>> > Seems like a bug in [1] - seems like we do not configure the bridge
>> > anymore
>> > on additional host. But I didn't yet try that myself, I might be missing
>> > something. Adding Simone.
>> >
>> > [1]
>> > https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z
>> > --
>> > Didi
>> >
>> > Yes, it was a real bug: https://gerrit.ovirt.org/#/c/53428/ should
>> > address it.
>> > It should be available in tomorrow build.
>> >
>> > 
>> >
>> > The contents of this electronic message and any attachments are intended
>> > only for the addressee and may contain legally privileged, personal,
>> > sensitive or confidential information. If you are not the intended
>> > addressee, and have received this email, any transmission, distribution,
>> > downloading, printing or photocopying of the contents of this message or
>> > attachments is strictly prohibited. Any legal privilege or confidentiality
>> > attached to this message and attachments is not waived, lost or destroyed 
>> > by
>> > reason of delivery to any person other than intended addressee. If you have
>> > received this message and are not the intended addressee you should notify
>> > the sender by return email and destroy all copies of the message and any
>> > attachments. Unless expressly attributed, the views expressed in this email
>> > do not necessarily represent the views of the company.
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>
>


answers-20160215004735.conf
Description: Binary data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Pending events in the Tasks tab

2016-02-17 Thread Michal Skrivanek

> On 17 Feb 2016, at 09:27, nico...@devels.es wrote:
> 
> I forgot to attach the screenshot. Here it goes.
> 
> El 2016-02-17 08:25, nico...@devels.es escribió:
>> Hi,
>> We're using oVirt 3.6.2.6, and we're having some events not being
>> cleared from the Tasks tab. I cannot confirm this is only related to
>> creating VM pools, but any created VM pool remains unfinished forever
>> in the Tasks tab. As you may see in the screenshot, there are events
>> that were started in January and are still in the list. Concretely,
>> the unfinished step is always "Finalizing".
>> Has this been reported on Bugzilla?

yeah, hopefully this is all fixed in 3.6.3, right, Shmuel?
I can’t find the bug ATM

Thanks,
michal

>> Is there a way to clear them out even manually?
>> Thanks.
>> Nicolás
>> ___
>> 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] Gluster 3.7.8 from ovirt-3.6-glusterfs-epel breaks vdsm ?

2016-02-17 Thread Sahina Bose

[+gluster-users]

Any known compat issues with gluster 3.7.8-1.el7 client packages and 
glusterfs 3.7.6-1.el7 server?



On 02/17/2016 04:33 PM, Matteo wrote:

Hi,

today I update one node os, in the updates gluster client
packages where upgraded from 3.7.6-1.el7, centos-ovirt36 repository
to 3.7.8-1.el7, ovirt-3.6-glusterfs-epel and after reboot
the node was marked not operational.

looking into the logs, vdsm was failing to get gluster volume information.

the command (ovirt-storage is the gluster storage where the hosted engine is 
kept)

gluster --mode=script volume info --remote-host=gluster1 ovirt-storage --xml

was failing, returning error 2 (and no output)

doing yum downgrade on gluster client packages (back to 3.7.6-1.el7, 
centos-ovirt36) fixed everything.

Data nodes are running glusterfs 3.7.6-1.el7.

The funny thing is that from the ovirt I was able to manually mount the 
glusterfs shares,
only the volume info command was failing, thus breaking vdsm.

Any hint?

regards,
Matteo



___
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 3.6.2 issue when updating to gluster 3.7.8

2016-02-17 Thread Sahina Bose



On 02/17/2016 04:57 PM, Luiz Claudio Prazeres Goncalves wrote:


Hi, I realised that gluster 3.7.8 was released for GA. So I updated 
manually using "yum -y install glusterfs*" gluster get's updated 
normally, but  unfortunately things stopped to work completely. 
ovirt_hosted_engine_ha was not able to connect to my gluster storage 
domain (as you can see below). I'm not using ovirt + gluster in 
hyperconverged way. I have 3 external gluster hosts.



What does the mount log on the hypervisor say? Could you attach that?



As a workaround I've executed "*yum*downgrade glusterfs*" and after 
doing this ovirt started to work again...but as a collateral effect 
now I can't migrate my vm's anymore.  On the vdsm logs I can see the 
following errors when trying to manually migrate a any VM Anyone 
knows how to fix it?


Thread-66055::DEBUG::2016-02-17 
11:05:57,497::migration::453::virt.vm::(stop) 
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::stopping migration 
downtime thread


Thread-66055::ERROR::2016-02-17 
11:05:57,497::migration::208::virt.vm::(_recover) 
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::unable to connect to 
server at 'kvm2.brightsquid.com:49152 
': No route to host


Thread-66055::DEBUG::2016-02-17 
11:05:57,497::stompreactor::389::jsonrpc.AsyncoreClient::(send) 
Sending response


Thread-66056::DEBUG::2016-02-17 
11:05:57,498::migration::450::virt.vm::(run) 
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::migration downtime thread 
exiting


Thread-66055::DEBUG::2016-02-17 
11:05:57,540::__init__::206::jsonrpc.Notification::(emit) Sending 
event {"params": {"notify_time": 4327804740, 
"05681896-a76a-4ae1-879e-8fe5d28634e1": {"status": "Migration 
Source"}}, "jsonrpc": "2.0", "method": 
"|virt|VM_status|05681896-a76a-4ae1-879e-8fe5d28634e1"}


Thread-66055::ERROR::2016-02-17 
11:05:57,541::migration::310::virt.vm::(run) 
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::Failedto migrate


Traceback (most recent call last):

  File "/usr/share/vdsm/virt/migration.py", line 294, in run

self._startUnderlyingMigration(time.time())

  File "/usr/share/vdsm/virt/migration.py", line 364, in 
_startUnderlyingMigration


self._perform_migration(duri, muri)

  File "/usr/share/vdsm/virt/migration.py", line 403, in 
_perform_migration


self._vm._dom.migrateToURI3(duri, params, flags)

  File "/usr/share/vdsm/virt/virdomain.py", line 68, in f

ret = attr(*args, **kwargs)

  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", 
line 124, in wrapper


ret = f(*args, **kwargs)

  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1836, in 
migrateToURI3


if ret == -1: raise libvirtError ('virDomainMigrateToURI3() 
failed', dom=self)


libvirtError: unable to connect to server at 
'kvm2.brightsquid.com:49152 ': No 
route to host


Thread-68::DEBUG::2016-02-17 
11:05:57,652::fileSD::173::Storage.Misc.excCmd::(getReadDelay) 
/usr/bin/taskset --cpu-list 0-39 /usr/bin/dd 
if=/rhev/data-center/mnt/gluster2.brightsquid.com:_home_export_iso/61827b7b-e255-44f5-a791-482a144be29f/dom_md/metadata 
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)


Thread-68::DEBUG::2016-02-17 
11:05:57,662::fileSD::173::Storage.Misc.excCmd::(getReadDelay) 
SUCCESS:  = '0+1 records in\n0+1 records out\n341 bytes (341 B) 
copied, 0.000713967 s, 478 kB/s\n';  = 0











Issue to connect to the gluster storage.
*
Feb 17 01:25:40 kvm2 ovirt-ha-agent: 
INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Connecting storage 
server
Feb 17 01:25:40 kvm2 ovirt-ha-agent: 
INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Connecting storage 
server
Feb 17 01:25:40 kvm2 journal: ovirt-ha-agent 
ovirt_hosted_engine_ha.agent.agent.Agent ERROR Error: 'Connection to 
storage server failed' - trying to restart agent
Feb 17 01:25:40 kvm2 ovirt-ha-agent: 
ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Error: 'Connection to 
storage server failed' - trying to restart agent
Feb 17 01:25:41 kvm2 ovirt-ha-broker: 
INFO:ovirt_hosted_engine_ha.broker.listener.ConnectionHandler:Connection 
established
Feb 17 01:25:41 kvm2 journal: ovirt-ha-broker 
ovirt_hosted_engine_ha.broker.listener.ConnectionHandler ERROR Error 
handling request, data: 'set-storage-domain FilesystemBackend 
dom_type=glusterfs 
sd_uuid=7d376952-312b-4539-b809-a8fa740f7883'#012Traceback (most 
recent call last):#012  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", 
line 166, in handle#012data)#012  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", 
line 299, in _dispatch#012.set_storage_domain(client, sd_type, 
**options)#012  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", 
line 66, in set_storage_domain#012 
 self._backends[client].connect()#012  File 

Re: [ovirt-users] New Installation

2016-02-17 Thread Yaniv Dary
I would recommend centos 7.x.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Wed, Feb 17, 2016 at 10:28 AM, Kadir Sümer  wrote:

> Hi,
>
> I want to start new ovirt installation. 2 Hosts with same configuration,
> FC storage
> For nodes minimal centos 7.x or ovirt node which one is more stable and
> useful ?
>
>
>
>
>
> ___
> 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] [FC22] ovirt-engine-reports missing in 3.6 repos

2016-02-17 Thread Yaniv Dary
Please open a bug on reports docs.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Tue, Feb 16, 2016 at 11:57 AM, David Marzal Canovas <
d...@asambleamurcia.es> wrote:

> Ok, thank you both for the information, I will explore the possibility of
> using another server for the reports.
>
> It may be useful for other if this is mentioned on the web (Fedora is the
> first suggestion I've seen everywhere in the documentation)
>
>
>
> El 2016-02-14 14:46, Yaniv Dary escribió:
>
> You can install DWH and reports on a CentOS 6 VM in the installation and
> connect them to the engine machine.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Sat, Feb 13, 2016 at 3:14 PM, Sandro Bonazzola 
> wrote:
>
>> Sadly reports is not compatible with java 8 so it's not available on
>> fedora 22.
>> Il 12/Feb/2016 12:04, "David Marzal Canovas"  ha
>> scritto:
>>
>>> Hi, I have installed oVirt 3.6 in a production system with FC22.
>>> I want to install the Reports Portal, but I can't find the packages in
>>> the repo.
>>>
>>> FC22: There is no ovirt-engine-reports* , ovirt-engine-dwh
>>> http://resources.ovirt.org/pub/ovirt-3.6/rpm/fc22/noarch/
>>> BUT in el7**, el6* they are availables
>>> http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/
>>>
>>> For oVirt 3.5 the packages exits:
>>>
>>> http://resources.ovirt.org/pub/ovirt-3.5/rpm/fc20/noarch/
>>>
>>> Searching I found in Jenkins:
>>>
>>> http://jenkins.ovirt.org/job/ovirt-reports_master_create-rpms-fc22-x86_64_created/
>>>
>>>
>>> http://jenkins.ovirt.org/job/ovirt-reports_master_create-rpms-fc22-x86_64_merged/
>>>
>>> So I'm not sure if the Reports Portail is only available in a
>>> Centos/RHEV installation or if there is some problem with the sync on the
>>> repos.
>>> There is no documentation with any reference to this in the wiki or the
>>> mailing-list.
>>>
>>> Does anyone know anything about this?
>>> --
>>> David Marzal Cánovas
>>> Servicio de Mecanización e Informática
>>> Asamblea Regional de Murcia
>>> Paseo Alfonso XIII, nº53
>>> 30203 - Cartagena
>>> Tlfno: 968326800
>>> ___
>>> 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
>>
>
> --
> David Marzal Cánovas
> Servicio de Mecanización e Informática
> Asamblea Regional de Murcia
> Paseo Alfonso XIII, nº53
> 30203 - Cartagena
> Tlfno: 968326800
>
> ___
> 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] [Node] Maintenance mode and update

2016-02-17 Thread Yaniv Dary
It is. Updates must be done while host is in maintenance.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Tue, Feb 16, 2016 at 11:31 AM, Lionel Caignec  wrote:

> Hello,
>
> I am concerned about maintenance mode and system updates.
> In which case it is essential to put host in maintenance mode?
> No worries for Content Updates requiring a reboot.
>
> But for example in the case of updates like VDSM* or kvm it seems
> essential, but is it?
>
> --
> Lionel
> ___
> 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] Upgrade patch 3.5 -> 3.6

2016-02-17 Thread Николаев Алексей
  17.02.2016, 10:36, "Yedidyah Bar David" :On Wed, Feb 17, 2016 at 9:09 AM, Николаев Алексей wrote: You must not configure firewall in backup restore procedure. Because EL6 backup uses iptables instead EL7 fresh install uses firewalld.Thanks for pointing that out!Does this mean you actually tried this and that was the only issue? I'm not 100% sure about it. It was on test environment. But EL6 backup don't check firewall software on the host. Note also that EL7 also has iptables, you can use that if you want.You'll have to do something like:yum install iptables-servicessystemctl disable firewalld.servicesystemctl enable iptables.servicesystemctl start iptables.serviceYou'll not have any default /etc/sysconfig/iptables, though. Either createone manually (or find somewhere) or use e.g. system-config-firewall-tui.Best,-- Didi___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] question mark in oVirt - "cannot acquire state change lock"

2016-02-17 Thread p...@email.cz

Hello,
some requested outputs

Vdsm generate a huge count of records in time, so I'm not shure if 
"hang" time is still included .

Problems occured 17-feb-2016 17:00-18:00 when VM shutdown was requested.
But some performance problems occured a day before ( I'm not shure about 
application problem = JAVA = running EBS )


In mail before  I attached pointers to bugs with any workaround

killall -9 libvirtd
rm /var/run/libvirtd.pid
/etc/init.d/libvirt-bin restart

which would solve current situation.
Is this  workaround safe enought?? Will stay VMs running ???

THX for any help, because I can't reboot hypervizor due huge DB traffic 
and no VM migration possibility via oVirt engine. ( mem synchro 
overloaded ?? )


Pa.
PS: logs sent directly to RH.


On 17.2.2016 08:22, Nir Soffer wrote:

On Tue, Feb 16, 2016 at 9:58 PM, p...@email.cz  wrote:

Hello all,
how can I eliminate question mark from "hanged" VM? ( it happened in
shutdown process via oVirt  env. )
Best solution without hypervizor reboot, meaning "power off" , "kill" or
another workaround for that VM .
Will help removing task DB record from oVirt mgmt server - if exists ,
ofcourse ??
Running  gluster 3.7.5 / oVirt 3.5.2 /
libvirt-daemon-kvm-1.2.8-16.el7_1.5.x86_64  on centos 7.1.1503 .

thx a lot.
Pa.

PS: I found similar problem in libvirt library a many years ago ( redhat 5.6
)
https://bugzilla.redhat.com/show_bug.cgi?id=676205
https://bugzilla.redhat.com/show_bug.cgi?id=668438
problem explanation:
http://linux.india365.org/2012/01/libvirt-virsh-cannot-acquire-state-change-lock-error-explained/

This is very interesting, I have seen this error in testing
environment on rhel 7.1 or 7.2.

Can you provide vdsm logs showing the time of the error?

Nir


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


[ovirt-users] Hosted engine storage "locked"

2016-02-17 Thread Ollie Armstrong
Hi,

I've updated from 3.6.1 to 3.6.2 and was hoping that the issue with
the hosted engine storage on FC not being imported would be solved.
It managed to start the import but now my storage has been stuck in
"Locked" for weeks.  None of the options in the web UI are available
except right click "Destroy".

Is there any way to restart the import process so maybe I can keep an
eye on the logs and find the issue?

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


[ovirt-users] [ANN] oVirt 3.6.3 Third Release Candidate is now available for testing

2016-02-17 Thread Sandro Bonazzola
The oVirt Project is pleased to announce the availability
of the Third Release Candidate of oVirt 3.6.3 for testing, as of February
17th, 2016

This release is available now for Fedora 22,
Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and
Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar).

This release supports Hypervisor Hosts running
Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and
Fedora 22.
Highly experimental support for Debian 8.3 Jessie has been added too.

This release candidate includes updated packages for:

   - ovirt-engine


   - ovirt-engine-sdk-python


   - ovirt-engine-sdk-java


   - vdsm


   - vdsm-jsonrpc-java


   - ovirt-hosted-engine-ha


   - ovirt-hosted-engine-setup



This release of oVirt 3.6.3 includes numerous bug fixes.
See the release notes [1] for an initial list of the new features and bugs
fixed.

Please refer to release notes [1] for Installation / Upgrade instructions.
A new oVirt Live ISO will be available soon [2].

Please note that mirrors[3] may need usually one day before being
synchronized.

* Read more about the oVirt 3.6.3 release highlights:
http://www.ovirt.org/OVirt_3.6.3_Release_Notes
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Read more about oVirt Project community events:
http://www.ovirt.org/Upcoming_events

[1] http://www.ovirt.org/OVirt_3.6.3_Release_Notes
[2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/
[3] http://www.ovirt.org/Repository_mirrors#Current_mirrors


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt 3.6.2 issue when updating to gluster 3.7.8

2016-02-17 Thread Luiz Claudio Prazeres Goncalves
Hi, I realised that gluster 3.7.8 was released for GA. So I updated
manually using "yum -y install glusterfs*" gluster get's updated normally,
but  unfortunately things stopped to work completely.
ovirt_hosted_engine_ha was not able to connect to my gluster storage domain
(as you can see below). I'm not using ovirt + gluster in hyperconverged
way. I have 3 external gluster hosts.

As a workaround I've executed "*yum* downgrade glusterfs*" and after doing
this ovirt started to work again...but as a collateral effect now I can't
migrate my vm's anymore.  On the vdsm logs I can see the following errors
when trying to manually migrate a any VM Anyone knows how to fix it?

Thread-66055::DEBUG::2016-02-17
11:05:57,497::migration::453::virt.vm::(stop)
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::stopping migration downtime
thread

Thread-66055::ERROR::2016-02-17
11:05:57,497::migration::208::virt.vm::(_recover)
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::unable to connect to server at
'kvm2.brightsquid.com:49152': No route to host

Thread-66055::DEBUG::2016-02-17
11:05:57,497::stompreactor::389::jsonrpc.AsyncoreClient::(send) Sending
response

Thread-66056::DEBUG::2016-02-17
11:05:57,498::migration::450::virt.vm::(run)
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::migration downtime thread
exiting

Thread-66055::DEBUG::2016-02-17
11:05:57,540::__init__::206::jsonrpc.Notification::(emit) Sending event
{"params": {"notify_time": 4327804740,
"05681896-a76a-4ae1-879e-8fe5d28634e1": {"status": "Migration Source"}},
"jsonrpc": "2.0", "method":
"|virt|VM_status|05681896-a76a-4ae1-879e-8fe5d28634e1"}

Thread-66055::ERROR::2016-02-17
11:05:57,541::migration::310::virt.vm::(run)
vmId=`05681896-a76a-4ae1-879e-8fe5d28634e1`::Failed to migrate

Traceback (most recent call last):

  File "/usr/share/vdsm/virt/migration.py", line 294, in run

self._startUnderlyingMigration(time.time())

  File "/usr/share/vdsm/virt/migration.py", line 364, in
_startUnderlyingMigration

self._perform_migration(duri, muri)

  File "/usr/share/vdsm/virt/migration.py", line 403, in _perform_migration

self._vm._dom.migrateToURI3(duri, params, flags)

  File "/usr/share/vdsm/virt/virdomain.py", line 68, in f

ret = attr(*args, **kwargs)

  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
124, in wrapper

ret = f(*args, **kwargs)

  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1836, in
migrateToURI3

if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed',
dom=self)

libvirtError: unable to connect to server at 'kvm2.brightsquid.com:49152':
No route to host

Thread-68::DEBUG::2016-02-17
11:05:57,652::fileSD::173::Storage.Misc.excCmd::(getReadDelay)
/usr/bin/taskset --cpu-list 0-39 /usr/bin/dd
if=/rhev/data-center/mnt/gluster2.brightsquid.com:_home_export_iso/61827b7b-e255-44f5-a791-482a144be29f/dom_md/metadata
iflag=direct of=/dev/null bs=4096 count=1 (cwd None)

Thread-68::DEBUG::2016-02-17
11:05:57,662::fileSD::173::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
 = '0+1 records in\n0+1 records out\n341 bytes (341 B) copied,
0.000713967 s, 478 kB/s\n';  = 0










Issue to connect to the gluster storage.
*
Feb 17 01:25:40 kvm2 ovirt-ha-agent:
INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Connecting
storage server
Feb 17 01:25:40 kvm2 ovirt-ha-agent:
INFO:ovirt_hosted_engine_ha.lib.storage_server.StorageServer:Connecting
storage server
Feb 17 01:25:40 kvm2 journal: ovirt-ha-agent
ovirt_hosted_engine_ha.agent.agent.Agent ERROR Error: 'Connection to
storage server failed' - trying to restart agent
Feb 17 01:25:40 kvm2 ovirt-ha-agent:
ERROR:ovirt_hosted_engine_ha.agent.agent.Agent:Error: 'Connection to
storage server failed' - trying to restart agent
Feb 17 01:25:41 kvm2 ovirt-ha-broker:
INFO:ovirt_hosted_engine_ha.broker.listener.ConnectionHandler:Connection
established
Feb 17 01:25:41 kvm2 journal: ovirt-ha-broker
ovirt_hosted_engine_ha.broker.listener.ConnectionHandler ERROR Error
handling request, data: 'set-storage-domain FilesystemBackend
dom_type=glusterfs
sd_uuid=7d376952-312b-4539-b809-a8fa740f7883'#012Traceback (most recent
call last):#012  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",
line 166, in handle#012data)#012  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",
line 299, in _dispatch#012.set_storage_domain(client, sd_type,
**options)#012  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
line 66, in set_storage_domain#012self._backends[client].connect()#012
 File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py",
line 456, in connect#012self._dom_type)#012  File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py",
line 108, in get_domain_path#012" in {1}".format(sd_uuid,

[ovirt-users] Gluster 3.7.8 from ovirt-3.6-glusterfs-epel breaks vdsm ?

2016-02-17 Thread Matteo
Hi,

today I update one node os, in the updates gluster client
packages where upgraded from 3.7.6-1.el7, centos-ovirt36 repository
to 3.7.8-1.el7, ovirt-3.6-glusterfs-epel and after reboot
the node was marked not operational.

looking into the logs, vdsm was failing to get gluster volume information.

the command (ovirt-storage is the gluster storage where the hosted engine is 
kept)

gluster --mode=script volume info --remote-host=gluster1 ovirt-storage --xml

was failing, returning error 2 (and no output)

doing yum downgrade on gluster client packages (back to 3.7.6-1.el7, 
centos-ovirt36) fixed everything.

Data nodes are running glusterfs 3.7.6-1.el7.

The funny thing is that from the ovirt I was able to manually mount the 
glusterfs shares,
only the volume info command was failing, thus breaking vdsm.

Any hint?

regards,
Matteo 



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


Re: [ovirt-users] Can't remove snapshot

2016-02-17 Thread Rik Theys
Hi,

On 02/16/2016 10:52 PM, Greg Padgett wrote:
> On 02/16/2016 08:50 AM, Rik Theys wrote:
>> Hi,
>>
>> I'm trying to determine the correct "bad_img" uuid in my case.
>>
>> The VM has two snapshots:
>>
>> * The "Active VM" snapshot which has a disk that has an actual size
>> that's 5GB larger than the virtual size. It has a creation date that
>> matches the timestamp at which I created the second snapshot. The "disk
>> snapshot id" for this snapshot ends with dc39.
>>
>> * A "before jessie upgrade" snapshot that has status "illegal". It has
>> an actual size that's 2GB larger than the virtual size. The creation
>> date matches the date the VM was initialy created. The disk snapshot id
>> ends with 6249.
>>
>>  From the above I conclude that the disk with id that ends with 6249 is
>> the "bad" img I need to specify.
> 
> Similar to what I wrote to Marcelo above in the thread, I'd recommend
> running the "VM disk info gathering tool" attached to [1].  It's the
> best way to ensure the merge was completed and determine which image is
> the "bad" one that is no longer in use by any volume chains.

I've ran the disk info gathering tool and this outputs (for the affected
VM):

VM lena
Disk b2390535-744f-4c02-bdc8-5a897226554b
(sd:a7ba2db3-517c-408a-8b27-ea45989d6416)
Volumes:
24d78600-22f4-44f7-987b-fbd866736249

The id of the volume is the ID of the snapshot that is marked "illegal".
So the "bad" image would be the dc39 one, which according to the UI is
in use by the "Active VM" snapshot. Can this make sense?

Both the "Active VM" and the defective snapshot have an actual size
that's bigger than the virtual size of the disk. When I remove the bad
disk image/snapshot, will the actual size of the "Active VM" snapshot
return to the virtual size of the disk? What's currently stored in the
"Active VM" snapshot?

Would cloning the VM (and removing the original VM afterwards) work as
an alternate way to clean this up? Or will the clone operation also
clone the snapshots?

Regards,

Rik

> If indeed the "bad" image (whichever one it is) is no longer in use,
> then it's possible the image wasn't successfully removed from storage. 
> There are 2 ways to fix this:
> 
>   a) Run the db fixup script to remove the records for the merged image,
>  and run the vdsm command by hand to remove it from storage.
>   b) Adjust the db records so a merge retry would start at the right
>  place, and re-run live merge.
> 
> Given that your merge retries were failing, option a) seems most likely
> to succeed.  The db fixup script is attached to [1]; as parameters you
> would need to provide the vm name, snapshot name, and the id of the
> unused image as verified by the disk info tool.
> 
> To remove the stale LV, the vdsm deleteVolume verb would then be run
> from `vdsClient` -- but note that this must be run _on the SPM host_. 
> It will not only perform lvremove, but also do housekeeping on other
> storage metadata to keep everything consistent.  For this verb I believe
> you'll need to supply not only the unused image id, but also the pool,
> domain, and image group ids from your database queries.
> 
> I hope that helps.
> 
> Greg
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1306741
> 
>>
>> However, I grepped the output from 'lvs' on the SPM host of the cluster
>> and both disk id's are returned:
>>
>> [root@amazone ~]# lvs | egrep 'cd39|6249'
>>24d78600-22f4-44f7-987b-fbd866736249
>> a7ba2db3-517c-408a-8b27-ea45989d6416 -wi-ao   34.00g
>>
>>81458622-aa54-4f2f-b6d8-75e7db36cd39
>> a7ba2db3-517c-408a-8b27-ea45989d6416 -wi---5.00g
>>
>>
>> I expected the "bad" img would no longer be found?
>>
>> The SQL script only cleans up the database and not the logical volumes.
>> Would running the script not keep a stale LV around?
>>
>> Also, from the lvs output it seems the "bad" disk is bigger than the
>> "good" one.
>>
>> Is it possible the snapshot still needs to be merged?? If so, how can I
>> initiate that?
>>
>> Regards,
>>
>> Rik
>>
>>
>> On 02/16/2016 02:02 PM, Rik Theys wrote:
>>> Hi Greg,
>>>

 2016-02-09 21:30 GMT-03:00 Greg Padgett :
> On 02/09/2016 06:08 AM, Michal Skrivanek wrote:
>>
>>
>>> On 03 Feb 2016, at 10:37, Rik Theys 
>>> wrote:
>>>
 I can see the snapshot in the "Disk snapshot" tab of the
 storage. It has
 a status of "illegal". Is it OK to (try to) remove this
 snapshot? Will
 this impact the running VM and/or disk image?
>>
>>
>> No, it’s not ok to remove it while live merge(apparently) is still
>> ongoing
>> I guess that’s a live merge bug?
>
>
> Indeed, this is bug 1302215.
>
> I wrote a sql script to help with cleanup in this scenario, which
> you can
> find attached to the bug along with a description of how to use it[1].
>
> However, Rik, before trying that, would you be able to run the

[ovirt-users] New Installation

2016-02-17 Thread Kadir Sümer
Hi,

I want to start new ovirt installation. 2 Hosts with same configuration, FC
storage
For nodes minimal centos 7.x or ovirt node which one is more stable and
useful ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Pending events in the Tasks tab

2016-02-17 Thread nicolas

I forgot to attach the screenshot. Here it goes.

El 2016-02-17 08:25, nico...@devels.es escribió:

Hi,

We're using oVirt 3.6.2.6, and we're having some events not being
cleared from the Tasks tab. I cannot confirm this is only related to
creating VM pools, but any created VM pool remains unfinished forever
in the Tasks tab. As you may see in the screenshot, there are events
that were started in January and are still in the list. Concretely,
the unfinished step is always "Finalizing".

Has this been reported on Bugzilla?

Is there a way to clear them out even manually?

Thanks.

Nicolás
___
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] Pending events in the Tasks tab

2016-02-17 Thread nicolas

Hi,

We're using oVirt 3.6.2.6, and we're having some events not being 
cleared from the Tasks tab. I cannot confirm this is only related to 
creating VM pools, but any created VM pool remains unfinished forever in 
the Tasks tab. As you may see in the screenshot, there are events that 
were started in January and are still in the list. Concretely, the 
unfinished step is always "Finalizing".


Has this been reported on Bugzilla?

Is there a way to clear them out even manually?

Thanks.

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


Re: [ovirt-users] "bridge port" error when setting up hosted-engine on 2nd oVirt 3.6.2 node

2016-02-17 Thread Simone Tiraboschi
On Wed, Feb 17, 2016 at 3:31 AM, Mike DePaulo  wrote:

> I tried the new build, yet the problem persists:
> ovirt-node-iso-3.6-0.999.201602161021.el7.centos.iso
>
> Also, are you sure that commit fixes the same problem? I am not using DHCP.
>

Are you using an answerfile?
Can you please check the value of OVEHOSTED_NETWORK/bridgeIf ?


>
> -Mike
>
> On Tue, Feb 16, 2016 at 5:22 PM, Bond, Darryl  wrote:
> > I've got the same problem on the second hosted engine server.
> >
> > When you say available in tomorrows build, when will that be available
> for yum update using the ovirt36-pre repository?
> >
> >
> > Darryl
> >
> > 
> > From: users-boun...@ovirt.org  on behalf of
> Simone Tiraboschi 
> > Sent: Tuesday, 16 February 2016 4:15 AM
> > To: Yedidyah Bar David
> > Cc: users
> > Subject: Re: [ovirt-users] "bridge port" error when setting up
> hosted-engine on 2nd oVirt 3.6.2 node
> >
> >
> >
> > On Mon, Feb 15, 2016 at 3:50 PM, Yedidyah Bar David  > wrote:
> > On Mon, Feb 15, 2016 at 4:22 PM, Mike DePaulo  > wrote:
> >> Hi,
> >>
> >> I am getting the following error when I attempt to setup my 2nd ovirt
> >> node as a hosted-engine:
> >>
> >> RuntimeError: The selected device None is not a supported bridge port
> >>
> >> The 1st node is death-star (192.168.1.50)
> >> The 2nd node is starkiller-base (192.168.1.52)
> >>
> >> This is not a production environment; this is my apartment.
> >>
> >> I am able to access the engine's webGUI.
> >>
> >> Both death-star and starkiller-base start out with only eno1 as their
> only NIC.
> >> death-star, by the end of the hosted-engine-setup, had ovirtmgmt also
> >> (with the same MAC address.)
> >> starkiller-base does not have ovirtmgmt yet.
> >> I am not using VLANs.
> >>
> >> node version: ovirt-node-iso-3.6-0.999.201602121021.el7.centos.iso
> >> engine appliance version:
> oVirt-Engine-Appliance-CentOS-x86_64-7-20160126.ova
> >
> > Seems like a bug in [1] - seems like we do not configure the bridge
> anymore
> > on additional host. But I didn't yet try that myself, I might be missing
> > something. Adding Simone.
> >
> > [1]
> https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z
> > --
> > Didi
> >
> > Yes, it was a real bug: https://gerrit.ovirt.org/#/c/53428/ should
> address it.
> > It should be available in tomorrow build.
> >
> > 
> >
> > The contents of this electronic message and any attachments are intended
> only for the addressee and may contain legally privileged, personal,
> sensitive or confidential information. If you are not the intended
> addressee, and have received this email, any transmission, distribution,
> downloading, printing or photocopying of the contents of this message or
> attachments is strictly prohibited. Any legal privilege or confidentiality
> attached to this message and attachments is not waived, lost or destroyed
> by reason of delivery to any person other than intended addressee. If you
> have received this message and are not the intended addressee you should
> notify the sender by return email and destroy all copies of the message and
> any attachments. Unless expressly attributed, the views expressed in this
> email do not necessarily represent the views of the company.
> > ___
> > 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