Re: [ovirt-users] [ovirt-devel] Building vdsm within Fedora

2014-09-24 Thread Sandro Bonazzola
Il 24/09/2014 00:21, Nir Soffer ha scritto:
 - Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Sandro Bonazzola sbona...@redhat.com, de...@ovirt.org, 
 fsimo...@redhat.com, dougsl...@redhat.com
 Cc: users users@ovirt.org
 Sent: Wednesday, September 24, 2014 12:21:18 AM
 Subject: [ovirt-devel] Building vdsm within Fedora

 Since Vdsm was open-sourced, it was built and deployed via
 Fedora.

 Recently [http://gerrit.ovirt.org/31214] vdsm introduced a spec-file
 dependency onf qemu-kvm-rhev, and considered to backport it to the
 ovirt-3.4 brach.

 Requiring qemu-kvm-rhev, which is not part of Fedora's EPEL6 branch,
 violates Fedora's standards.

 So basically we have two options:
 
 4 options...
 

 1. Revert the qemu-kvm-rhev dependency.
 
 Why did we merge a package which is not available on all supported platforms?
 
 2. Drop vdsm from EPEL6 (or completely from Fedora); ship Vdsm only
within the oVirt repositories.
 
 3. Package qemu-kvm-rhev in Fedora

in EPEL. But if you're going to add it to EPEL please ensure it doesn't violate 
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies

 
 This is the root cause, lets fix it.
 
 4. Until 3 is fixed, require qemu-kvm-rhev where it exists,
otherwise on qemu-kvm.

Which is basically 1 only for the fedora packaging, keeping the dep on ovirt 
packaging.


 
 I favor option 2. The Fedora deployment platform served us well for a
 long time, but now that ovirt is maturing, we no longer need it for
 building vdsm. This has the added benefit of removing the need to pass
 through Fedora's ghastly gateway when adding a Vdsm dependency.
 
 This is the wrong direction. We want ovirt in all distributions. You suggest
 to have it in no distribution :-)

I tend to agree with Nir.


 Sandro, what should be done in order to build Vdsm by ovirt, occording
 to the most up-to-date tag in a stable branch?

currently we're using mock for building packages whenever we can use it.
for vdsm I created a yaml job here: http://gerrit.ovirt.org/32512
once it's merged you can build from git tag.

 
 Does anybody object this? If no one does, we would stop updating Vdsm in
 Fedora, and obsolete it in the future.
 
 I do
 
 Nir
 


-- 
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] Raid-5 like gluster method?

2014-09-24 Thread Demeter Tibor
Hi, 

Is there any method in glusterfs, like raid-5? 

I have three node, each node has 5 TB of disk. I would like utilize all of 
space with redundancy, like raid-5. 
If it not possible, can I make raid-6 like redundanci within three node? (two 
brick/node?). 
Thanks in advance, 

Tibor 

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


Re: [ovirt-users] Building vdsm within Fedora

2014-09-24 Thread Federico Simoncelli
- Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Sandro Bonazzola sbona...@redhat.com, de...@ovirt.org, 
 fsimo...@redhat.com, dougsl...@redhat.com
 Cc: Sven Kieske s.kie...@mittwald.de, users users@ovirt.org
 Sent: Tuesday, September 23, 2014 11:21:18 PM
 Subject: Building vdsm within Fedora
 
 Since Vdsm was open-sourced, it was built and deployed via
 Fedora.
 
 Recently [http://gerrit.ovirt.org/31214] vdsm introduced a spec-file
 dependency onf qemu-kvm-rhev, and considered to backport it to the
 ovirt-3.4 brach.
 
 Requiring qemu-kvm-rhev, which is not part of Fedora's EPEL6 branch,
 violates Fedora's standards.
 
 So basically we have two options:
 
 1. Revert the qemu-kvm-rhev dependency.
 2. Drop vdsm from EPEL6 (or completely from Fedora); ship Vdsm only
within the oVirt repositories.
 
 A third option would be to have one rpm, with qemu-kvm-rhev, shipped in
 ovirt, and another without it - shipped in Fedora. I find this overly
 complex and confusing.

I think that until now (centos6) we were using qemu-kvm/qemu-img in the
spec file and then the ovirt repository was distributing qemu-*-rhev
from:

 http://resources.ovirt.org/pub/ovirt-3.4-snapshot/rpm/el6/x86_64/

It this not possible with centos7? Any problem with that?

I find being in fedora a way to keep the spec file and the rpm updated
and as clean as possible.

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


[ovirt-users] oVirt 3.4 entering security/critical fix only phase

2014-09-24 Thread Sandro Bonazzola
Hi,
As you should know, we released oVirt 3.4.4 yesterday.
After this release, only security/critical fixes will be allowed on 3.4 branch 
and only a security/critical update will cause a new oVirt 3.4.z release.
It's time to focus on new features for 3.6.0!
Thanks,

-- 
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


Re: [ovirt-users] [ovirt-announce] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Sven Kieske


On 23/09/14 23:05, Sandro Bonazzola wrote:
 [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes

First, thanks for the new release, but I have one objection to make:

Hidden in the release notes we find:

BZ 1139000 - CVE-2014-3573 ovirt-engine-backend: oVirt Engine: XML
eXternal Entity (XXE) flaw in backend module

So I'd like to discuss if security fixes should not be highlighted
somewhat more?

I'd expect the following:

a) Mention at least that CVEs where fixed in this release in the
announcement.
b) a category security patches (or similar) in the release notes
where these fixes get listed.
c) This new category should be at the top of the release notes.

What do you think?




-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH  Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] hosted engine setup on second host fails

2014-09-24 Thread Jiri Moskovcak

Hi,
it's getting a little too long, so please forgive the top post. The 
engine emits the message Host with the same address already exists. 
only if you trying to add host with the same hostname it doesn't have 
any connection to it's ID, so please check if your hosts have unique 
hostnames (e.g. I ran into this when I didn't get hostname from dhcp and 
both of my hosts were localhost.localdomain).


Regards,
Jirka

On 09/24/2014 07:59 AM, Yedidyah Bar David wrote:

- Original Message -

From: Yedidyah Bar David d...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: Stefan Wendler stefan.wend...@tngtech.com, users@ovirt.org
Sent: Wednesday, September 24, 2014 8:40:58 AM
Subject: Re: [ovirt-users] hosted engine setup on second host fails

- Original Message -

From: Itamar Heim ih...@redhat.com
To: Stefan Wendler stefan.wend...@tngtech.com
Cc: Yedidyah Bar David ybard...@redhat.com, users@ovirt.org
Sent: Tuesday, September 23, 2014 7:07:12 PM
Subject: Re: [ovirt-users] hosted engine setup on second host fails


On Sep 23, 2014 7:03 PM, Stefan Wendler stefan.wend...@tngtech.com wrote:


On 09/23/2014 17:01, Itamar Heim wrote:

On 09/23/2014 05:17 PM, Stefan Wendler wrote:

On 09/22/2014 10:52, Stefan Wendler wrote:

On 09/19/2014 15:58, Itamar Heim wrote:

On 09/19/2014 03:32 PM, Stefan Wendler wrote:

Hi there.

I'm trying to install a hosted-engine on our second node (fist
engine
runs on node1).

But I always get the message:

[ ERROR ] Cannot automatically add the host to the Default cluster:
Cannot add Host. Host with the same address already exists.

I'm not entirely sure what I have to do when this message comes, so
I
just press ENTER:

###
To continue make a selection from the options below:
  (1) Continue setup - engine installation is complete
  (2) Power off and restart the VM
  (3) Abort setup

  (1, 2, 3)[1]:


Is there any other interaction required prior to selecting 1?

In the Web Gui I get the following message:

X Adding new Host hosted_engine_2 to Cluster Default

Here is the console output:

# hosted-engine --deploy
[ INFO  ] Stage: Initializing
  Continuing will configure this host for serving as
hypervisor
and create a VM where you have to install oVirt Engine afterwards.
  Are you sure you want to continue? (Yes, No)[Yes]:
[ INFO  ] Generating a temporary VNC password.
[ INFO  ] Stage: Environment setup
  Configuration files: []
  Log file:
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140919141012-k2lag6.log


  Version: otopi-1.2.3 (otopi-1.2.3-1.el6)
[ INFO  ] Hardware supports virtualization
[ INFO  ] Bridge ovirtmgmt already created
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization

  --== STORAGE CONFIGURATION ==--

  During customization use CTRL-D to abort.
  Please specify the storage you would like to use (nfs3,
nfs4)[nfs3]:
  Please specify the full shared storage connection path
to use
(example: host:/path): some address:/volume1
  The specified storage location already contains a data
domain.
Is this an additional host setup (Yes, No)[Yes]?
[ INFO  ] Installing on additional host
  Please specify the Host ID [Must be integer, default:
  2]:
  The Host ID is already known. Is this a re-deployment
on an
additional host that was previously set up (Yes, No)[Yes]?


I admit I never tried that. Not sure how exactly it's supposed to work.


A bit more details:

Normally, a host is registered only in the engine's database. A hosted
engine is additionally registered in a special hosted-engine metadata
file managed by the ha daemon [1]. The question above appears if the host id
is found in this metadata file. It seems we never check if it's already
in the engine database - the assumption is that if an existing host is
re-purposed as a hosted-engine, it should first be uninstalled - at least
not be in use (no VMs) and removed from its cluster/dc/the engine.

[1] http://www.ovirt.org/images/d/d5/Fosdem-hosted-engine.pdf pages 17-18





  --== SYSTEM CONFIGURATION ==--

[WARNING] A configuration file must be supplied to deploy Hosted
Engine
on an additional host.
  The answer file may be fetched from the first host
using scp.
  If you do not want to download it automatically you can
abort
the setup answering no to the following question.
  Do you want to scp the answer file from the first host?
(Yes,
No)[Yes]:
  Please provide the FQDN or IP of the first host:
node1.domain
  Enter 'root' user password for host node1.domain:
[ INFO  ] Answer file successfully downloaded

  --== NETWORK CONFIGURATION ==--

  The following CPU types are 

Re: [ovirt-users] Building vdsm within Fedora

2014-09-24 Thread Sven Kieske


On 24/09/14 09:13, Federico Simoncelli wrote:
 You probably missed the first part we were using qemu-kvm/qemu-img in
 the spec file. In that case you won't fail in any requirement.
 
 Basically the question is: was there any problem on centos6 before
 committing http://gerrit.ovirt.org/31214 ?

Of course there was a problem, please follow the link in this very
commit to the according bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=1127763

In short: you can not use live snapshots without this updated spec file.

And it's a PITA to install this package by hand, you must track
it's versions yourself etc pp. you basically lose all the stuff
a proper spec file gives you.


PS: I also don't get the we want to get vdsm in every distribution
a) it was never in any distro, it was in epel, which is a third party
repository anyway, so you can just provide it via ovirt repo imho.
b) no one packages vdsm for debian, ubuntu, gentoo, arch, suse,
$nameyourdistro or I completely missed it, so why treat fedora
in a special way? Don't misunderstand me, it would be cool if you
have packages for every distro, or even bsd based stuff, but I think
this is still a long way.
c) will anyone use vdsm without ovirt? is this even possible?
so imho you need ovirt repos anyway?



-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH  Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] sysprep answers

2014-09-24 Thread Omer Frenkel


- Original Message -
 From: Bill Dossett bill.doss...@pb.com
 To: users@ovirt.org
 Sent: Wednesday, September 24, 2014 10:57:28 AM
 Subject: [ovirt-users] sysprep answers
 
 
 
 Hi,
 
 
 
 I’ve managed to get my first templates ready to go…. But I am lacking a
 document that explains how I can add the VMs to my domain. I have sealed the
 template but the ovirt docs seem to stop there and the redhat ones talk
 about using rhevm-config commands.
 
 
 
 I have found the place to set time zone and enter a domain if I edit the
 template, however to add a computer to our domain we need to use a special
 account and I don’t see any way of specifying this.
 
 
 
 Any help or further reading would be appreciated


the user that is used by default is the user that is set for the domain
you can see it with 
# engine-manage-domains list

or directly from the db

# su - postgres -c psql engine -c \select * from vdc_options where 
option_name = 'AdUserName';\
 
if you need to use different user, you can do that with 'run-once' option:
in the webadmin, select the vm, click run once, under 'boot options' mark 
floppy and select sysprep, under 'initial run' select go to sysprep, and select 
'alternate credentials'

in ovirt 3.5 you can also save a custom sysprep file containing any custom data:
Bug 1080002 - OVIRT35 - [RFE] Enable user defined Windows Sysprep file

 
 
 Thanks
 
 
 
 
   
 
 Bill Dossett
 
 Virtualisation Architect
   
 
 Pitney Bowes – Tech Central
 
 6 Hercules Way, 600 Leavesden Park
 
 Watford, WD25 7GS
   
 
 Phone (+44) (0)1923 279353 | VOIP: 54739353
 
 Mobile (+44) (0)7775 908612
   
 
 bill.doss...@pb.com
 
 www.pb.com
 
 
 
 In Engineering? Raise a ticket via Remedy Anywhere [ HERE ] takes less than a
 minute
 
 
 
 ManageIQ User Guide available [ HERE ]
 
 
 
 Check out the ManageIQ Blog for recent enhancements and information [HERE]
 
 
 
 
 
 
 
 
 ___
 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-devel] Building vdsm within Fedora

2014-09-24 Thread Federico Simoncelli
- Original Message -
 From: Sven Kieske s.kie...@mittwald.de
 To: de...@ovirt.org, users users@ovirt.org
 Sent: Wednesday, September 24, 2014 9:44:17 AM
 Subject: Re: [ovirt-devel] Building vdsm within Fedora
 
 On 24/09/14 09:13, Federico Simoncelli wrote:
  You probably missed the first part we were using qemu-kvm/qemu-img in
  the spec file. In that case you won't fail in any requirement.
  
  Basically the question is: was there any problem on centos6 before
  committing http://gerrit.ovirt.org/31214 ?
 
 Of course there was a problem, please follow the link in this very
 commit to the according bugzilla:
 
 https://bugzilla.redhat.com/show_bug.cgi?id=1127763
 
 In short: you can not use live snapshots without this updated spec file.
 
 And it's a PITA to install this package by hand, you must track
 it's versions yourself etc pp. you basically lose all the stuff
 a proper spec file gives you.

As soon as you have the ovirt repository installed there shouldn't be any
reason for you to have any of these problems.

Sandro, is there any reason why the rpm available here:

http://resources.ovirt.org/pub/ovirt-3.4/rpm/el6/x86_64/

are not published here?

http://resources.ovirt.org/releases/3.4/rpm/el6/x86_64/

Is there any additional repository (that provides qemu-*-rhev) that we are
missing from the ovirt.repo file?

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


Re: [ovirt-users] Building vdsm within Fedora

2014-09-24 Thread Sandro Bonazzola
Il 24/09/2014 09:44, Sven Kieske ha scritto:
 
 
 On 24/09/14 09:13, Federico Simoncelli wrote:
 You probably missed the first part we were using qemu-kvm/qemu-img in
 the spec file. In that case you won't fail in any requirement.

 Basically the question is: was there any problem on centos6 before
 committing http://gerrit.ovirt.org/31214 ?

Federico: as we checked a few minutes ago, it seems there's no problem in 
requiring qemu-kvm/qemu-img in the spec file.
Only issue is that if non rhev version is installed a manual yum update is 
required for moving to the rhevm version.


 Of course there was a problem, please follow the link in this very
 commit to the according bugzilla:
 
 https://bugzilla.redhat.com/show_bug.cgi?id=1127763
 
 In short: you can not use live snapshots without this updated spec file.
 
 And it's a PITA to install this package by hand, you must track
 it's versions yourself etc pp. you basically lose all the stuff
 a proper spec file gives you.

Well, since the -rhev package is now available in 3.4, 3.5 and master repos it 
shouldn't be a PITA anymore.



 PS: I also don't get the we want to get vdsm in every distribution
 a) it was never in any distro, it was in epel, which is a third party
 repository anyway, so you can just provide it via ovirt repo imho.
 b) no one packages vdsm for debian, ubuntu, gentoo, arch, suse,
 $nameyourdistro or I completely missed it, so why treat fedora
 in a special way? Don't misunderstand me, it would be cool if you
 have packages for every distro, or even bsd based stuff, but I think
 this is still a long way.
 c) will anyone use vdsm without ovirt? is this even possible?
 so imho you need ovirt repos anyway?
 
 
 


-- 
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


Re: [ovirt-users] [ovirt-devel] Building vdsm within Fedora

2014-09-24 Thread Sandro Bonazzola
Il 24/09/2014 10:35, Federico Simoncelli ha scritto:
 - Original Message -
 From: Sven Kieske s.kie...@mittwald.de
 To: de...@ovirt.org, users users@ovirt.org
 Sent: Wednesday, September 24, 2014 9:44:17 AM
 Subject: Re: [ovirt-devel] Building vdsm within Fedora

 On 24/09/14 09:13, Federico Simoncelli wrote:
 You probably missed the first part we were using qemu-kvm/qemu-img in
 the spec file. In that case you won't fail in any requirement.

 Basically the question is: was there any problem on centos6 before
 committing http://gerrit.ovirt.org/31214 ?

 Of course there was a problem, please follow the link in this very
 commit to the according bugzilla:

 https://bugzilla.redhat.com/show_bug.cgi?id=1127763

 In short: you can not use live snapshots without this updated spec file.

 And it's a PITA to install this package by hand, you must track
 it's versions yourself etc pp. you basically lose all the stuff
 a proper spec file gives you.
 
 As soon as you have the ovirt repository installed there shouldn't be any
 reason for you to have any of these problems.
 
 Sandro, is there any reason why the rpm available here:
 
 http://resources.ovirt.org/pub/ovirt-3.4/rpm/el6/x86_64/
 
 are not published here?
 
 http://resources.ovirt.org/releases/3.4/rpm/el6/x86_64/

this second link points to the previous layout, abandoned since we moved from 
/releases to /pub.
/releases is still around for historical purpose, I think we should consider to 
drop it at some point avoinding confusion or renaming it to something
that make it clear that it shouldn't be used anymore.


 
 Is there any additional repository (that provides qemu-*-rhev) that we are
 missing from the ovirt.repo file?
 


-- 
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] overt viewer on mac osx

2014-09-24 Thread Bill Dossett
Hi,

I got pretty excited when I found out there was a girt-viewer for mac…  if this 
would work, it means I could manange my ovirt stack from my mac without having 
to login to my windows VDI.

I have downloaded and installed per the instructions - and then downloaded the 
console.vv file and run the command line to start the viewer with the 
console.vv - the first time it popped up and then said that spice needed 
authentication… tried my virt-engine password that didn’t work, hit cancel and 
it shut down.  Tried it again and now it just says it can’t determine the 
connection type from uri and I have to quit.

I am running OSX 10.9.4 and apparently this has only been tested on 10.9.1… 
hoping there is a fix to make this work, or am I doing something wrong?  The 
command I am using is

/Applications/RemoteViewer.app/Contents/MacOS/RemoteViewer Downloads/console.vv

and the console.vv is indeed in the Downloads dir off my home dir.

Thanks


Bill Dossett
Virtualisation Architect

Pitney Bowes – Tech Central
6 Hercules Way, 600 Leavesden Park
Watford, WD25 7GS

Phone (+44) (0)1923 279353 | VOIP: 54739353
Mobile (+44) (0)7775 908612

bill.doss...@pb.commailto:bill.doss...@pb.com
www.pb.comhttp://www.pb.com/

In Engineering? Raise a ticket via Remedy Anywhere 
[HEREhttp://teamsite.inside.pb.com/sites/TCPPM/GES/Lists/Create%20Incident/newIncident.aspx]
 takes less than a minute


ManageIQ User Guide available 
[HEREhttps://dl.dropbox.com/u/6219441/ManageIQ%20-%20User%20Manual%20PB%20v4.pdf]

Check out the ManageIQ Blog for recent enhancements and information 
[HERE]http://teamsite.inside.pb.com/sites/TCPPM/GES/manageiq/default.aspx




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


Re: [ovirt-users] [ovirt-devel] Building vdsm within Fedora

2014-09-24 Thread Federico Simoncelli
- Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Federico Simoncelli fsimo...@redhat.com
 Cc: de...@ovirt.org, users users@ovirt.org, Sven Kieske 
 s.kie...@mittwald.de
 Sent: Wednesday, September 24, 2014 11:01:35 AM
 Subject: Re: [ovirt-devel] Building vdsm within Fedora
 
 Il 24/09/2014 10:35, Federico Simoncelli ha scritto:
  - Original Message -
  From: Sven Kieske s.kie...@mittwald.de
  To: de...@ovirt.org, users users@ovirt.org
  Sent: Wednesday, September 24, 2014 9:44:17 AM
  Subject: Re: [ovirt-devel] Building vdsm within Fedora
 
  On 24/09/14 09:13, Federico Simoncelli wrote:
  You probably missed the first part we were using qemu-kvm/qemu-img in
  the spec file. In that case you won't fail in any requirement.
 
  Basically the question is: was there any problem on centos6 before
  committing http://gerrit.ovirt.org/31214 ?
 
  Of course there was a problem, please follow the link in this very
  commit to the according bugzilla:
 
  https://bugzilla.redhat.com/show_bug.cgi?id=1127763
 
  In short: you can not use live snapshots without this updated spec file.
 
  And it's a PITA to install this package by hand, you must track
  it's versions yourself etc pp. you basically lose all the stuff
  a proper spec file gives you.
  
  As soon as you have the ovirt repository installed there shouldn't be any
  reason for you to have any of these problems.
  
  Sandro, is there any reason why the rpm available here:
  
  http://resources.ovirt.org/pub/ovirt-3.4/rpm/el6/x86_64/
  
  are not published here?
  
  http://resources.ovirt.org/releases/3.4/rpm/el6/x86_64/
 
 this second link points to the previous layout, abandoned since we moved from
 /releases to /pub.
 /releases is still around for historical purpose, I think we should consider
 to drop it at some point avoinding confusion or renaming it to something
 that make it clear that it shouldn't be used anymore.

Sven can you let us know if you still have any problem using:

http://resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm
(which should contain the correct ovirt.repo)

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


Re: [ovirt-users] sysprep answers

2014-09-24 Thread Bill Dossett
thank you!

Bill Dossett
Virtualisation Architect

Pitney Bowes – Tech Central
6 Hercules Way, 600 Leavesden Park
Watford, WD25 7GS

Phone (+44) (0)1923 279353 | VOIP: 54739353
Mobile (+44) (0)7775 908612

bill.doss...@pb.commailto:bill.doss...@pb.com
www.pb.comhttp://www.pb.com/

In Engineering? Raise a ticket via Remedy Anywhere 
[HEREhttp://teamsite.inside.pb.com/sites/TCPPM/GES/Lists/Create%20Incident/newIncident.aspx]
 takes less than a minute


ManageIQ User Guide available 
[HEREhttps://dl.dropbox.com/u/6219441/ManageIQ%20-%20User%20Manual%20PB%20v4.pdf]

Check out the ManageIQ Blog for recent enhancements and information 
[HERE]http://teamsite.inside.pb.com/sites/TCPPM/GES/manageiq/default.aspx

On Sep 24, 2014, at 9:30 AM, Omer Frenkel 
ofren...@redhat.commailto:ofren...@redhat.com wrote:



- Original Message -
From: Bill Dossett bill.doss...@pb.commailto:bill.doss...@pb.com
To: users@ovirt.orgmailto:users@ovirt.org
Sent: Wednesday, September 24, 2014 10:57:28 AM
Subject: [ovirt-users] sysprep answers



Hi,



I’ve managed to get my first templates ready to go…. But I am lacking a
document that explains how I can add the VMs to my domain. I have sealed the
template but the ovirt docs seem to stop there and the redhat ones talk
about using rhevm-config commands.



I have found the place to set time zone and enter a domain if I edit the
template, however to add a computer to our domain we need to use a special
account and I don’t see any way of specifying this.



Any help or further reading would be appreciated


the user that is used by default is the user that is set for the domain
you can see it with
# engine-manage-domains list

or directly from the db

# su - postgres -c psql engine -c \select * from vdc_options where 
option_name = 'AdUserName';\

if you need to use different user, you can do that with 'run-once' option:
in the webadmin, select the vm, click run once, under 'boot options' mark 
floppy and select sysprep, under 'initial run' select go to sysprep, and select 
'alternate credentials'

in ovirt 3.5 you can also save a custom sysprep file containing any custom data:
Bug 1080002 - OVIRT35 - [RFE] Enable user defined Windows Sysprep file



Thanks






Bill Dossett

Virtualisation Architect


Pitney Bowes – Tech Central

6 Hercules Way, 600 Leavesden Park

Watford, WD25 7GS


Phone (+44) (0)1923 279353 | VOIP: 54739353

Mobile (+44) (0)7775 908612


bill.doss...@pb.commailto:bill.doss...@pb.com

www.pb.com



In Engineering? Raise a ticket via Remedy Anywhere [ HERE ] takes less than a
minute



ManageIQ User Guide available [ HERE ]



Check out the ManageIQ Blog for recent enhancements and information [HERE]








___
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] [ANN] oVirt 3.5.0 Third Release Candidate is now available for testing

2014-09-24 Thread Sandro Bonazzola
The oVirt team is pleased to announce that the 3.5.0 Third Release Candidate is 
now
available for testing as of Sep 24th 2014.

The release candidate is available now for Fedora 19, Fedora 20 and Red Hat 
Enterprise Linux 6.5
(or similar) and allow you to use Red Hat Enterprise Linux 7 as node and run 
Hosted Engine.

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

The existing repository ovirt-3.5-pre has been updated for delivering this
release without the need of enabling any other repository.
If you're already using oVirt 3.5 repository, please update ovirt-release35 rpm.

Please refer to release notes [1] for Installation / Upgrade instructions.
New oVirt Live, oVirt Guest Tools and oVirt Node ISO will be available soon as 
well[2].

Please note that mirrors may need usually one day before being synchronized.
If you want to be sure to use latest rpms and don't want to wait for the 
mirrors,
you can edit /etc/yum.repos.d/ovirt-3.5.repo commenting the mirror line and
removing the comment on baseurl line.

Please refer to the release notes for known issues in this release.

[1] http://www.ovirt.org/OVirt_3.5_Release_Notes
[2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/


-- 
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] the better way to update vdsm

2014-09-24 Thread Nathanaël Blanchet

Hi all,

I'm about to update to 3.4.4 with the associated vdsm. Updating vdsm 
with yum is trivial, but it usually breaks running vms on the host.

So these are the steps I follow each time:

 * live migrating runnings vms to a another host in the cluster
 * putting the host in maintenance
 * updating vdsm
 * activating the host
 * getting back the vms
 * and so on with the other hosts...

But sometimes it is not enough, I need to reinstall the host so as to 
the host be able to successfully activate.


When getting back the vms on the initial host, I must do it manually to 
load balance vms between the hosts and this is not very convinient.


So my question is : do I update in the right way, or is there any 
recommendations that I didn't find anyway?


Thanks.

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


Re: [ovirt-users] [ovirt 3.4.3] No KDC can be obtained for domain... after using engine-manage-domains edit

2014-09-24 Thread Martin Perina


- Original Message -
 From: Grzegorz Szypa grzegorz.sz...@gmail.com
 To: Martin Perina mper...@redhat.com, users@ovirt.org
 Sent: Wednesday, September 24, 2014 11:19:27 AM
 Subject: Re: [ovirt-users] [ovirt 3.4.3] No KDC can be obtained for domain... 
 after using engine-manage-domains edit
 
 Hi.
 
 It's a little strange, because I can easily attach clients (VMs) to the
 Microsoft AD domain. Only sometimes there are problems with connectivity,
 but I will solve this in two ways: add the DNS suffix or adds a static
 primary DNS, which indicates domain.
 
 /etc/resolv.conf
 nameserver 172.30.30.253# DNS and AD server
 nameserver 172.30.30.1# Router -  DHCP
 search szypa.net
 
 By the way, is also one strange thing:
 
 Every time when I inserted record nameserver 172.30.30.253 to file
 resolv.conf from time to time the file is overwritten / changed (I have
 no idea how) and record nameserver 172.30.30.253 disappears (just as you
 would in general not been added).

It depends what is your network configuration. If you are using static IP,
then network configuration is defined in 
/etc/sysconfig/network-scripts/ifcfg-XXX
(XXX is the name of device) using DNSx params. In you case

DNS1=172.30.30.25
DNS2=172.30.30.1

If you are using DHCP, then /etc/resolv.conf is usually altered on IP address
renewal.


 
 *And in all this is the cause that generates the problem.*
 
 *So I think that the problem are solved, but i do not know how to resolve a
 problem with hidding configuration in /etc/resolv.conf*
 
 Regards,
 
 *Grzegorz Szypa*
 
 
 2014-09-24 8:03 GMT+02:00 Martin Perina mper...@redhat.com:
 
  Hi,
 
  I looked at the logs and you have serious DNS problems:
 
  2014-09-24 07:32:24,984 ERROR
  [org.ovirt.engine.core.bll.adbroker.GetRootDSE]
  (DefaultQuartzScheduler_Worker-15) Failed to query rootDSE for LDAP server
  ldap://szypa.net:389 due to szypa.net:389
  2014-09-24 07:32:24,984 ERROR
  [org.ovirt.engine.core.bll.adbroker.DirectorySearcher]
  (DefaultQuartzScheduler_Worker-15) Failed ldap search server ldap://
  szypa.net:389 using user ov...@szypa.net due to
  javax.naming.CommunicationException: szypa.net:389 [Root exception is
  java.net.UnknownHostException: szypa.net]. We should try the next server
 
  You cannot authenticate your users, because LDAP server ldap://
  szypa.net:389
  cannot be resolved. Are you able to resolve szypa.net on you engine host?
 
 
 
  - Original Message -
   From: Grzegorz Szypa grzegorz.sz...@gmail.com
   To: Martin Perina mper...@redhat.com, users@ovirt.org
   Sent: Wednesday, September 24, 2014 7:32:56 AM
   Subject: Re: [ovirt-users] [ovirt 3.4.3] No KDC can be obtained for
  domain... after using engine-manage-domains edit
  
   ;  DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1  SRV _kerberos._
   tcp.szypa.net
   ;; global options: +cmd
   ;; Got answer:
   ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 65248
   ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
  
   ;; QUESTION SECTION:
   ;_kerberos._tcp.szypa.net.  IN  SRV
  
   ;; AUTHORITY SECTION:
   net.890 IN  SOA a.gtld-servers.net.
   nstld.verisign-grs.com. 1411536712 1800 900 604800 86400
  
   ;; Query time: 28 msec
   ;; SERVER: 172.30.30.1#53(172.30.30.1)
   ;; WHEN: Wed Sep 24 07:32:23 2014
   ;; MSG SIZE  rcvd: 115
 
 
  This looks like that szypa.net domain doesn't exist at all. Do you really
  have
  correct DNS configuration on engine host?
 
  
  
   2014-09-24 7:06 GMT+02:00 Martin Perina mper...@redhat.com:
  
Hi,
   
the error message mean, that we cannot find any KDC servers
in DNS. Could you please post results of the following command:
   
  dig SRV _kerberos._tcp.szypa.net
   
Regarding the errors after oVirt restart, could you please post
your engine.log?
   
Thanks
   
Martin Perina
   
   
- Original Message -
 From: Grzegorz Szypa grzegorz.sz...@gmail.com
 To: fkob...@redhat.com, users@ovirt.org
 Sent: Tuesday, September 23, 2014 3:41:02 PM
 Subject: [ovirt-users] [ovirt 3.4.3] No KDC can be obtained for
domain... after using engine-manage-domains edit

 Hi.

 I have a problem with losting connetction to Windows Active
  Directory.

 Normaly I connect ovirt with AD like this:

 engine-manage-domains add --domain= szypa.net --provider=ad
--user=ovirt
 --add-permissions

 After period time, example when i restart ovirt, connection is lost
becouse i
 cannot add new user created in AD, so i thinking that i refresh conf.
 connection to ad:

 engine-manage-domains edit --domain= szypa.net --provider=ad
--user=ovirt
 --add-permissions

 and i get this error:

 No KDC can be obtained for domain szypa.net

 have any idea?

 I read that this problem is resolved in previous ovirt version

 --
 G.Sz.

 

Re: [ovirt-users] VM autoconfiguration

2014-09-24 Thread J. Mikulec

I spent a day with testing and went into two situations:
- cloud-init set up everything except root password
- cloud-init set up everything except network

What does it mean? Let me explain:

When I remove HWADDR from ifcfg-eth0 in template, everything works 
(network, ssh with key), but can't login through console or ssh with 
password. So I think it is not set.


When I forgot to remove HWADDR line, root password is set but network 
not work ofcourse. I added custom command with runcmd to remove this 
line and restart network - everything works. Stupid hack ...


So root password cloud-init setting depends on network settings. Is this 
cloud-init bug?


Jiri

Dne 23.9.2014 v 8:30 Shahar Havivi napsal(a):

On 22.09.14 19:37, J. Mikulec wrote:

Hello again,

Centos 7:

Everything works except network needs manually restart to work (but config
is done by cloud-init). Is workaround to send custom command through
cloud-init to restart network service?

I think there is an open bug in cloud-init package:
https://bugzilla.redhat.com/1139556


It also neither do not setup resolv.conf nor add DNS settings to ifcfg-eth0
(workaround may be to let this settings in ifcfg-eth0 filled from template)

Jiri

Dne 22.9.2014 v 16:30 Shahar Havivi napsal(a):

On 22.09.14 16:22, J. Mikulec wrote:

Hello,

I followed instructions at
http://www.ovirt.org/Features/Cloud-Init_Integration
It works fine for Fedora, but it not works properly for Centos 6.5 and 7
(for example network settings changed, hostname only in one of them, system
start waiting for password in 6.5 etc.) - which are most common distros for
us.

It seems to be problematically (by design ?) at future.

So - is another alternative of cloud-init (maybe with more coding and
configuring) for automatically assign IP settings, hostname and root
password?

Please post the version and log of cloud-init,
If the version is more then 0.7.2 you can try to downgrade to this version.

   Shahar.


Thanks, Jiri
___
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] overt viewer on mac osx

2014-09-24 Thread Karli Sjöberg
Bill, remember to keep users list when replying.

On Wed, 2014-09-24 at 10:16 +, Bill Dossett wrote:
 ahhh… thanks!  2 minutes was the problem… I tried associating .vv
 files with the RemoteView application, but that doesn’t work, just
 brings up the remote viewer app as though it hadn’t been given a
 console.vv file to configure it… any other way of doing this other
 than going to a terminal and starting it? 

Right, it´s been explained to me in the past:
http://lists.ovirt.org/pipermail/users/2014-January/019963.html

@Christophe

Has there been any updates to this? A newer version perhaps?

/K

 
 
 Thanks again!
 
 Bill Dossett
 Virtualisation Architect
 Pitney Bowes – Tech Central
 6 Hercules Way, 600 Leavesden Park
 Watford, WD25 7GS
 Phone (+44) (0)1923 279353 | VOIP: 54739353
 Mobile (+44) (0)7775 908612
 bill.doss...@pb.com
 www.pb.com
  
 In Engineering? Raise a ticket via Remedy Anywhere [HERE] takes less
 than a minute
  
 ManageIQ User Guide available [HERE]
  
 Check out the ManageIQ Blog for recent enhancements and
 information [HERE]
 
 On Sep 24, 2014, at 10:58 AM, Karli Sjöberg karli.sjob...@slu.se
 wrote:
 
  On Wed, 2014-09-24 at 09:28 +, Bill Dossett wrote:
   Hi Karli, 
   
   
   I am on oVirt Engine Version 3.4.3-1.el6   is that what you mean?
  
  Yepp, that´s what I meant. Well, it´s working for us, though we´re
  still
  running 3.4.1 so that may have changed in later releases?
  
  FYI, the authentication that remote-viewer is referring to is the
  ticket (random gibberish - not the engine password) that
  ovirt-engine generates every time you press for console. That ticket
  has
  a 2 min timeout, so if you download a console.vv and wait more than
  that, the ticket will experired, and you´d have to download a new
  file
  for the authentication to work. Makes sense?
  
  /K
  
   
   
   thanks
   
   Bill Dossett
   Virtualisation Architect
   Pitney Bowes – Tech Central
   6 Hercules Way, 600 Leavesden Park
   Watford, WD25 7GS
   Phone (+44) (0)1923 279353 | VOIP: 54739353
   Mobile (+44) (0)7775 908612
   bill.doss...@pb.com
   www.pb.com
   
   In Engineering? Raise a ticket via Remedy Anywhere [HERE] takes
   less
   than a minute
   
   ManageIQ User Guide available [HERE]
   
   Check out the ManageIQ Blog for recent enhancements and
   information [HERE]
   
   On Sep 24, 2014, at 10:11 AM, Karli Sjöberg karli.sjob...@slu.se
   wrote:
   
On Wed, 2014-09-24 at 09:07 +, Bill Dossett wrote:
 Hi, 
 
 
 I got pretty excited when I found out there was a girt-viewer
 for
 mac…  if this would work, it means I could manange my ovirt
 stack
 from
 my mac without having to login to my windows VDI.
 
 
 I have downloaded and installed per the instructions - and
 then
 downloaded the console.vv file and run the command line to
 start
 the
 viewer with the console.vv - the first time it popped up and
 then
 said
 that spice needed authentication… tried my virt-engine
 password
 that
 didn’t work, hit cancel and it shut down.  Tried it again and
 now
 it
 just says it can’t determine the connection type from uri and
 I
 have
 to quit.
 
 
 I am running OSX 10.9.4 and apparently this has only been
 tested
 on
 10.9.1… hoping there is a fix to make this work, or am I doing
 something wrong?  The command I am using is
 
 
 /Applications/RemoteViewer.app/Contents/MacOS/RemoteViewer
 Downloads/console.vv
 
 and the console.vv is indeed in the Downloads dir off my home
 dir.
 
 
 Thanks
 
 
 
 Bill Dossett
 Virtualisation Architect
 Pitney Bowes – Tech Central
 6 Hercules Way, 600 Leavesden Park
 Watford, WD25 7GS
 Phone (+44) (0)1923 279353 | VOIP: 54739353
 Mobile (+44) (0)7775 908612
 bill.doss...@pb.com
 www.pb.com
 
 In Engineering? Raise a ticket via Remedy Anywhere [HERE]
 takes
 less
 than a minute
 
 ManageIQ User Guide available [HERE]
 
 Check out the ManageIQ Blog for recent enhancements and
 information [HERE]
 
 
 

Hey Bill!

What oVirt version are you on?



-- 

Med Vänliga Hälsningar

---
Karli Sjöberg
Swedish University of Agricultural Sciences Box 7079 (Visiting
Address
Kronåsvägen 8)
S-750 07 Uppsala, Sweden
Phone:  +46-(0)18-67 15 66
karli.sjob...@slu.se
   
   
   
   
   __
   
  
  
  
  -- 
  
  Med Vänliga Hälsningar
  
  ---
  Karli Sjöberg
  Swedish University of Agricultural Sciences Box 7079 (Visiting
  Address
  Kronåsvägen 8)
  S-750 07 Uppsala, Sweden
  Phone:  

Re: [ovirt-users] [oVirt 3.4.3] RDP Browser plug-in - SSO

2014-09-24 Thread Grzegorz Szypa
Hi.

I resolved problem with connection to ovirt via Microsoft AD users, but
it's stiil a problem with sign  / before username.

I attach file  console.rdp generated for ovirt:
and screen from logging in via native rdp

first screen after running console.rdp:

[image: Obraz w treści 1]

and second screen after clicking Inny użytkownik:

[image: Obraz w treści 2]

Have you any idea how to fix it

2014-09-24 10:19 GMT+02:00 Frantisek Kobzik fkob...@redhat.com:

 Hello,

 I don't know windows so much, but according to this [1], you can use both
 formats of username. Could you try logging on manually with both formats?

 Cheers!
 F.

 [1]:
 http://msdn.microsoft.com/en-us/library/windows/desktop/aa380525(v=vs.85).aspx


 - Original Message -
 From: Grzegorz Szypa grzegorz.sz...@gmail.com
 To: Frantisek Kobzik fkob...@redhat.com
 Sent: Tuesday, September 23, 2014 3:48:34 PM
 Subject: Re: [ovirt-users] [oVirt 3.4.3] RDP Browser plug-in - SSO

 Hi.

 In native rdp is still same. But I think it happens because, like this:

 user@domine, example admin@internal user is treated as a user, so if I was
 logged in as a user ov...@szypa.net example, where the domain is szypa.net
 it probably should log in as szypa.net/ovirt me, but I'm not sure.

 But not proof, it now because I have the problem described in this thread:
 [ovirt 3.4.3] No KDC can be obtained for domain... after using engine-man
 age-domains edit


 2014-09-23 12:45 GMT+02:00 Frantisek Kobzik fkob...@redhat.com:

  Hi,
 
  Could you please switch to 'Native' invocation in 'Console options' and
  inspect generated .rdp file? Focus on a line that starts with
  username:s:. What value does it contain?
 
  Also, make sure you don't reload the webpage (e.g. F5) prior to
 connecting
  to the machine - SSO wouldn't work in this case.
 
  Cheers!
  F.
 
 
  - Original Message -
  From: Grzegorz Szypa grzegorz.sz...@gmail.com
  To: users@ovirt.org
  Sent: Sunday, September 21, 2014 10:08:09 PM
  Subject: [ovirt-users] [oVirt 3.4.3] RDP Browser plug-in - SSO
 
  Hi.
 
  I have a little problem with log-in to Windows VMs via SSO. When connect
  to VM in username filed i get a example text /user@domain What going
 on
  wit this sign  / 
 
  --
  G.Sz.
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 



 --
 G.Sz.




-- 
G.Sz.


console.rdp
Description: Binary data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM

2014-09-24 Thread Omer Frenkel


- Original Message -
 From: Gianluca Cecchi gianluca.cec...@gmail.com
 To: users users@ovirt.org
 Sent: Tuesday, September 23, 2014 1:56:07 AM
 Subject: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM
 
 Hello,
 installed a CentOS 6.5 x86_64 vm from iso (create VM and then run once
 connecting CD iso).
 
 System reboot several times and power on from web admin gui and all seems ok.
 
 At a certain point I upload guest-tools iso to my engine for future windows
 VMs.
 Taken ovirt-guest-tools-3.5_5.iso and try to mount it
 
 In engine the downloaded file seems ok and I can loop mount it for test.
 [root@ovirtmgr ~]# mount -o loop ovirt-guest-tools-3.5_5.iso /media
 [root@ovirtmgr ~]# ll /media
 total 19382
 dr-xr-xr-x. 4 root root 2048 Jul 7 13:21 bin
 dr-xr-xr-x. 4 root root 2048 Jul 6 17:25 drivers
 -r--r--r--. 1 root root 19839504 Jul 17 12:49 ovirt-guest-tools-setup.exe
 -r--r--r--. 1 root root 88 Jul 7 13:18 version.txt
 -r--r--r--. 1 root root 2266 Jul 2 16:40 win-driver-license.txt
 [root@ovirtmgr ~]# umount /media
 
 [root@ovirtmgr ~]# md5sum ovirt-guest-tools-3.5_5.iso
 ad98fc5db09183acd1620b5effb5e151 ovirt-guest-tools-3.5_5.iso
 
 Also the uploaded file seems ok
 [root@ovirtmgr ovirt-engine]# md5sum
 /var/lib/exports/iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----/ovirt-guest-tools-3.5_5.iso
 ad98fc5db09183acd1620b5effb5e151
 /var/lib/exports/iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----/ovirt-guest-tools-3.5_5.iso
 
 If I try to connect cd to the running VM from web admin portal I get a window
 with the error:
 
 Error while executing action Change CD: Internal Engine Error
 
 In events:
 Failed to change disk in VM c65new (Host: ovnode04, User: admin).
 
 In engine.log
 2014-09-23 00:33:43,022 INFO [org.ovirt.engine.core.bll.ChangeDiskCommand]
 (ajp--127.0.0.1-8702-5) [22041
 702] Running command: ChangeDiskCommand internal: false. Entities affected :
 ID: 0ce8ebc0-8464-4e9a-b382-1836234b3560 Type: VMAction group CHANGE_VM_CD
 with role type USER
 2014-09-23 00:33:43,028 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
 (ajp--127.0.0.1-8702-5) [22041702] START, IsoPrefixVDSCommand(HostName =
 ovnode04, HostId = 36fec87b-c21f-4157-ab2f-434b67c05cb9,
 storagePoolId=4512e567-f94e-476a-a050-6cd0a15e260a), log id: 26c82fe2
 2014-09-23 00:33:43,028 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
 (ajp--127.0.0.1-8702-5) [22041702] FINISH, IsoPrefixVDSCommand, return:
 /rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----,
 log id: 26c82fe2
 2014-09-23 00:33:43,029 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ChangeDiskVDSCommand]
 (ajp--127.0.0.1-8702-5) [22041702] START, ChangeDiskVDSCommand(HostName =
 ovnode04, HostId = 36fec87b-c21f-4157-ab2f-434b67c05cb9,
 vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,
 diskPath=/rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----/ovirt-guest-tools-3.5_5.iso),
 log id: 12ce4870
 2014-09-23 00:33:43,060 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ChangeDiskVDSCommand]
 (ajp--127.0.0.1-8702-5) [22041702] Failed in ChangeDiskVDS method, for vds:
 ovnode04; host: 192.168.1.74
 2014-09-23 00:33:43,061 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ChangeDiskVDSCommand]
 (ajp--127.0.0.1-8702-5) [22041702] Command ChangeDiskVDSCommand(HostName =
 ovnode04, HostId = 36fec87b-c21f-4157-ab2f-434b67c05cb9,
 vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,
 diskPath=/rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----/ovirt-guest-tools-3.5_5.iso)
 execution failed. Exception: NullPointerException:
 2014-09-23 00:33:43,063 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ChangeDiskVDSCommand]
 (ajp--127.0.0.1-8702-5) [22041702] FINISH, ChangeDiskVDSCommand, log id:
 12ce4870
 2014-09-23 00:33:43,063 ERROR [org.ovirt.engine.core.bll.ChangeDiskCommand]
 (ajp--127.0.0.1-8702-5) [22041702] Command
 org.ovirt.engine.core.bll.ChangeDiskCommand throw Vdc Bll exception. With
 error message VdcBLLException: java.lang.NullPointerException (Failed with
 error ENGINE and code 5001)
 2014-09-23 00:33:43,069 ERROR [org.ovirt.engine.core.bll.ChangeDiskCommand]
 (ajp--127.0.0.1-8702-5) [22041702] Transaction rolled-back for command:
 org.ovirt.engine.core.bll.ChangeDiskCommand.
 2014-09-23 00:33:43,083 ERROR
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
 (ajp--127.0.0.1-8702-5) [22041702] Correlation ID: 22041702, Job ID:
 a6be11b2-bb67-49ec-b3fc-695e8eab36b2, Call Stack: null, Custom Event ID: -1,
 Message: Failed to change disk in VM c65new (Host: ovnode04, User: admin).
 
 No errors in vdsm.log of host and in VM logfile under 

Re: [ovirt-users] overt viewer on mac osx

2014-09-24 Thread cferg...@redhat.com
On Wed, Sep 24, 2014 at 10:38:59AM +, Karli Sjöberg wrote:
 Bill, remember to keep users list when replying.
 
 On Wed, 2014-09-24 at 10:16 +, Bill Dossett wrote:
  ahhh… thanks!  2 minutes was the problem… I tried associating .vv
  files with the RemoteView application, but that doesn’t work, just
  brings up the remote viewer app as though it hadn’t been given a
  console.vv file to configure it… any other way of doing this other
  than going to a terminal and starting it? 
 
 Right, it´s been explained to me in the past:
 http://lists.ovirt.org/pipermail/users/2014-January/019963.html
 
 @Christophe
 
 Has there been any updates to this? A newer version perhaps?

Nope. If someone can provide me with some C code snippet which can be
used to properly handle this, I can look at adding this to the current
build. An alternative would be a wrapper script.

Christophe


pgpsnIgsZTasC.pgp
Description: PGP signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] the better way to update vdsm

2014-09-24 Thread Daniel Helgenberger
Hello Nathanaël,

I think the supposed way to upgrade would be:

* (hosted-engine only) put cluster in global maintenance if running
hosted-enfgine
* upgrade Engine using engine-setup (this *should* detect product updates)
* (hosted-engine only) disable global maintenance
* Put host in maintenance mode (witch will migrate VMs automatically)
* Click 'reinstall host' in Engine (this step will will invoke yum update?)
* Activate host

continue with the other hosts


If there are kernel updates, I usually update them as well in the
process (involving manual yum).

Can anyone clarify if 'reinstall host' invokes yum? Thanks!


On 24.09.2014 11:41, Nathanaël Blanchet wrote:
 Hi all,

 I'm about to update to 3.4.4 with the associated vdsm. Updating vdsm with yum 
 is 
 trivial, but it usually breaks running vms on the host.
 So these are the steps I follow each time:

   * live migrating runnings vms to a another host in the cluster
   * putting the host in maintenance
   * updating vdsm
   * activating the host
   * getting back the vms
   * and so on with the other hosts...

 But sometimes it is not enough, I need to reinstall the host so as to the 
 host 
 be able to successfully activate.

 When getting back the vms on the initial host, I must do it manually to load 
 balance vms between the hosts and this is not very convinient.

 So my question is : do I update in the right way, or is there any 
 recommendations that I didn't find anyway?

 Thanks.


-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


[ovirt-users] Is it possible to add ISCSI over iser?

2014-09-24 Thread Arman Khalatyan
Hi,
I am trying to attach my new storage domain over iser.
My server always gets that request is tcp/ip not rdma.
Simple work around is login from hosts over iser.
Would be good to add a possibility to select the protocol of
iscsi:tcp/iser/srp.

Thanks,
Arman

PS
for those who was struggling with same trouble:
1) on hosts:
add lines in /etc/rdma/rdma.conf
# Load iSER module
ISER_LOAD=YES
2) *service rdma restart (or modprobe ib_iser*
3)* iscsiadm -m discovery -t st -p 10.10.10.31 -I iser*
4) *iscsiadm -m node --login*

5) check if disks are there
*iscsiadm -m session -o show*
lssci
[1228:0:0:0] storage IET  Controller   0001  -
[1228:0:0:1] diskIET  VIRTUAL-DISK 0001  /dev/sde
* lsblk /dev/sde*
NAME MAJ:MIN RM
 SIZE RO TYPE  MOUNTPOINT
sde8:64   0
36.4T  0 disk
ââ100090001 (dm-8)   253:80
36.4T  0 mpath
  ââ18b70b0d--4944--4c73--970d--87a1af353b9f-metadata (dm-9) 253:90
 512M  0 lvm
  ââ18b70b0d--4944--4c73--970d--87a1af353b9f-ids (dm-10) 253:10   0
 128M  0 lvm
  ââ18b70b0d--4944--4c73--970d--87a1af353b9f-leases (dm-11)  253:11   0
 2G  0 lvm
  ââ18b70b0d--4944--4c73--970d--87a1af353b9f-outbox (dm-12)  253:12   0
 128M  0 lvm
  ââ18b70b0d--4944--4c73--970d--87a1af353b9f-inbox (dm-13)   253:13   0
 128M  0 lvm
  ââ18b70b0d--4944--4c73--970d--87a1af353b9f-master (dm-14)  253:14   0
 1G  0 lvm
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Problem Refreshing/Using ovirt-image-repository / 3.5 RC2

2014-09-24 Thread InterNetX - Juergen Gotteswinter
Am 23.09.2014 um 10:11 schrieb Federico Simoncelli:
 - Original Message -
 From: Oved Ourfali ov...@redhat.com
 To: j...@internetx.com, Federico Simoncelli fsimo...@redhat.com
 Cc: users@ovirt.org, Allon Mureinik amure...@redhat.com
 Sent: Tuesday, September 23, 2014 9:56:28 AM
 Subject: Re: [ovirt-users] Problem Refreshing/Using ovirt-image-repository / 
 3.5 RC2

 - Original Message -
 From: InterNetX - Juergen Gotteswinter j...@internetx.com
 To: users@ovirt.org
 Sent: Tuesday, September 23, 2014 10:41:41 AM
 Subject: Re: [ovirt-users] Problem Refreshing/Using ovirt-image-repository
 / 3.5   RC2

 Am 23.09.2014 um 09:32 schrieb Oved Ourfali:


 - Original Message -
 From: InterNetX - Juergen Gotteswinter j...@internetx.com
 To: users@ovirt.org
 Sent: Tuesday, September 23, 2014 10:29:07 AM
 Subject: [ovirt-users] Problem Refreshing/Using ovirt-image-repository /
 3.5   RC2

 Hi,

 when trying to refresh the ovirt glance repository i get a 500 Error
 Message


 Operation Canceled

 Error while executing action: A Request to the Server failed with the
 following Status Code: 500


 engine.log says:

 2014-09-23 09:23:08,960 INFO
 [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand]
 (ajp--127.0.0.1-8702-10) [7fffb4bd] Running command:
 TestProviderConnectivityCommand internal: false. Entities affected :
 ID: aaa0----123456789aaa Type: SystemAction group
 CREATE_STORAGE_POOL with role type ADMIN
 2014-09-23 09:23:08,975 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
 (ajp--127.0.0.1-8702-10) [7fffb4bd] Correlation ID: 7fffb4bd, Call
 Stack: null, Custom Event ID: -1, Message: Unrecognized audit log type
 has been used.
 2014-09-23 09:23:20,173 INFO
 [org.ovirt.engine.core.bll.aaa.LogoutUserCommand]
 (ajp--127.0.0.1-8702-11) [712895c3] Running command: LogoutUserCommand
 internal: false.
 2014-09-23 09:23:20,184 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
 (ajp--127.0.0.1-8702-11) [712895c3] Correlation ID: 712895c3, Call
 Stack: null, Custom Event ID: -1, Message: User admin logged out.
 2014-09-23 09:23:20,262 INFO
 [org.ovirt.engine.core.bll.aaa.LoginAdminUserCommand]
 (ajp--127.0.0.1-8702-6) Running command: LoginAdminUserCommand internal:
 false.


 All these message are good... no error here.
 Can you attach the full engine log?


 imho there is nothing else related to this :/ i attached the log
 starting from today. except firing up a test vm nothing else happened
 yet (and several tries refreshing the image repo)


 I don't see a refresh attempt in the log, but i'm not familiar enough with
 that.
 Federico - can you have a look?
 
 I don't see any reference to glance or error 500 in the logs. My impression
 is that the error 500 is between the ui and the engine... have you tried to
 force-refresh the ovirt webadmin page?
 
 You can try and use the rest-api to check if the listing is working there.
 


for the records - problem solved. how? dunno, after upgrading to rc3
everything is working like a charm
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Can not configure with simple LDAP.

2014-09-24 Thread Fumihide Tani

Hi, Alon,

I have updated the oVirt 3.5 RC2 to the newest RC3 today.

From my CentOS6.5 based oVirt Engine server and the oVirt Host server,
# yum clean all
# yum update
Then rebooted these servers.

But my LDAP problem is continued and same result as before.

When I login to the oVirt User Portal,
User Name: tani
Password: (OpenLDAP's userPassword)
Domain: rxc05271.com

UI displays General command validation failure.

Please advice.

Thanks,
Fumihide Tani

(2014/09/22 22:20), Alon Bar-Lev wrote:

The version of engine you are using is probably out of date and unsynced with 
latest ldap package (20140821064931).
Please make sure you take latest from[1]
Thanks!

[1] http://resources.ovirt.org/pub/ovirt-3.5-snapshot/

- Original Message -

From: Fumihide Tani rxc05...@nifty.com
To: Alon Bar-Lev alo...@redhat.com
Cc: users@ovirt.org
Sent: Monday, September 22, 2014 3:42:52 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Hi, Alon,

Your requested engine.log attached.

Also, I tried to login to web user portal by tani

User Name: tani
Password:(OpenLDAP userPassword)
Domain: rxc05271.com

cause: General command validation failure.

Attated log includes login by Fumihide first, tani second.

Very thanks,


(2014/09/22 21:24), Alon Bar-Lev wrote:

- Original Message -

From: Fumihide Tani rxc05...@nifty.com
To: Alon Bar-Lev alo...@redhat.com
Cc: users@ovirt.org
Sent: Monday, September 22, 2014 3:06:39 PM
Subject: Re: [ovirt-users] Can not configure with simple LDAP.

Sorry, I misunderstood.

This is outputs after LDAP user logged in.

Please attach log as files, not inline, easier to handle.

2014-09-22 21:01:32,638 DEBUG
[org.ovirt.engineextensions.aaa.ldap.Framework] (ajp--127.0.0.1-8702-4)
SearchRequest: SearchRequest(baseDN='dc=rxc05271,dc=com', scope=SUB,
deref=NEVER, sizeLimit=0, timeLimit=0,
filter='(objectClass=uidObject)(uid=*)(uid=Fumihide)', attrs={entryUUID,
uid, displayName, memberOf, department, givenName, sn, title, mail},
controls={SimplePagedResultsControl(pageSize=100, isCritical=false)})
2014-09-22 21:01:32,640 DEBUG
[org.ovirt.engineextensions.aaa.ldap.Framework] (ajp--127.0.0.1-8702-4)
SearchResult: SearchResult(resultCode=0 (success), messageID=3,
entriesReturned=0, referencesReturned=0,
responseControls={SimplePagedResultsControl(pageSize=0,
isCritical=false)})

From the above I see that a search was issued:

(objectClass=uidObject)(uid=*)(uid=Fumihide)

And no result returned.

Per previous output:
---
# tani, Users, rxc05271.com
dn: uid=tani,ou=Users,dc=rxc05271,dc=com
objectClass: inetOrgPerson
objectClass: uidObject
uid: tani
cn: Fumihide Tani
givenName: Fumihide
mail: t...@rxc05271.com
sn: Tani
userPassword:: a3VtaXRhbg==
---

Your user name is tani and not Fumihide.

Alon









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


Re: [ovirt-users] the better way to update vdsm

2014-09-24 Thread Daniel Helgenberger
Replying to my own mail since upgrading opportunities are not many.
Considering the procdure mentioned worked very well, it needs some
refinement.
On 24.09.2014 13:30, Daniel Helgenberger wrote:
 Hello Nathanaël,

 I think the supposed way to upgrade would be:
Here you need to insert:
# yum update engine-setup on the engine
(and for a new major version also new .repo files)
this is necessary since the engine-setup utility cannot upgrade itself
(though this might be doable;  RFE? :)

 * (hosted-engine only) put cluster in global maintenance if running
 hosted-enfgine
 * upgrade Engine using engine-setup (this *should* detect product updates)
 * (hosted-engine only) disable global maintenance
 * Put host in maintenance mode (witch will migrate VMs automatically)
This did not work for the hosted engine VM for some reason; I migrated
it manually. Is this intentional?
 * Click 'reinstall host' in Engine (this step will will invoke yum update?)
 * Activate host

 continue with the other hosts


 If there are kernel updates, I usually update them as well in the
 process (involving manual yum).

 Can anyone clarify if 'reinstall host' invokes yum? Thanks!
It will run yum update; but only on oVirt packages. One might want to
run it again to update all other system packages. Again, this makes sense.


 On 24.09.2014 11:41, Nathanaël Blanchet wrote:
 Hi all,

 I'm about to update to 3.4.4 with the associated vdsm. Updating vdsm with 
 yum is 
 trivial, but it usually breaks running vms on the host.
 So these are the steps I follow each time:

   * live migrating runnings vms to a another host in the cluster
   * putting the host in maintenance
   * updating vdsm
   * activating the host
   * getting back the vms
   * and so on with the other hosts...

 But sometimes it is not enough, I need to reinstall the host so as to the 
 host 
 be able to successfully activate.

 When getting back the vms on the initial host, I must do it manually to load 
 balance vms between the hosts and this is not very convinient.

 So my question is : do I update in the right way, or is there any 
 recommendations that I didn't find anyway?

 Thanks.


-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Daniel Helgenberger
Thanks Sandro,

upgrading went really well and my datacenter is running 3.4.4 just fine.

I suppose [1] is still in this release? Any change this will be
backported from 3.5?

Cheers!

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1130045
On 23.09.2014 23:06, Sandro Bonazzola wrote:
 The oVirt development team is pleased to announce the general
 availability of oVirt 3.4.4 as of Sep 23th 2014. This release
 solidifies oVirt as a leading KVM management application and open
 source alternative to VMware vSphere.

 oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
 (or similar).

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

 The existing repository ovirt-3.4 has been updated for delivering this
 release without the need of enabling any other repository, however since we
 introduced package signing you need an additional step in order to get
 the public keys installed on your system if you're upgrading from an older 
 release.
 Please refer to release notes [1] for Installation / Upgrade instructions.

 Please note that mirrors will need a couple of days before being synchronized.
 If you want to be sure to use latest rpms and don't want to wait for the 
 mirrors,
 you can edit /etc/yum.repos.d/ovirt-3.4.repo commenting the mirror line and
 removing the comment on baseurl line.

 A new oVirt Live ISO will be available too[2].

 [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
 [2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso


-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] Cannon have a non-VLAN VM network and VLAN-tagged networks on one interface.

2014-09-24 Thread Lior Vernia
Hi Nathan,

Sorry I missed this earlier. Yes, this is easily doable in Linux, it's
an additional constraint we've enforced in oVirt due to some security
concerns.

It has come up a few times though and is discussed to be enabled in
oVirt - you could perhaps weigh in on Itamar's RFI for 3.6 thread to
push this for the coming version.

Yours, Lior.

On 16/09/14 16:39, Nathan Stratton wrote:
 Why not? It works fine, all our hosts have ovirtmgmt without a vlan and
 all other networks with a vlan. At least with RHEL, there is nothing
 wrong with the following:
 
 [root@virt02a network-scripts]# more ifcfg-cogent 
 TYPE=Bridge
 DEVICE=cogent
 VLAN=yes
 BOOTPROTO=none
 MTU=1500
 [root@virt02a network-scripts]# more ifcfg-ovirtmgmt 
 TYPE=Bridge
 DEVICE=ovirtmgmt
 BOOTPROTO=none
 IPADDR=10.71.1.15
 NETMASK=255.255.255.0
 GATEWAY=10.71.1.1
 ONBOOT=yes
 DEFROUTE=no
 MTU=1500
 [root@virt02a network-scripts]# more ifcfg-private 
 TYPE=Bridge
 DEVICE=private
 BOOTPROTO=none
 IPADDR=10.71.0.15
 NETMASK=255.255.255.0
 GATEWAY=10.71.0.1
 ONBOOT=yes
 DEFROUTE=yes
 MTU=9000
 [root@virt02a network-scripts]# more ifcfg-cogent 
 TYPE=Bridge
 DEVICE=cogent
 VLAN=yes
 BOOTPROTO=none
 MTU=1500
 [root@virt02a network-scripts]# more ifcfg-comcast 
 TYPE=Bridge
 DEVICE=comcast
 VLAN=yes
 BOOTPROTO=none
 MTU=1500
 [root@virt02a network-scripts]# more ifcfg-eth2.100 
 DEVICE=eth2.100
 VLAN=yes
 ONBOOT=yes
 TYPE=Ethernet
 BRIDGE=private
 MTU=9000
 [root@virt02a network-scripts]# more ifcfg-eth2.201
 DEVICE=eth2.201
 VLAN=yes
 ONBOOT=yes
 TYPE=Ethernet
 BRIDGE=cogent
 [root@virt02a network-scripts]# more ifcfg-eth2.202
 DEVICE=eth2.202
 VLAN=yes
 ONBOOT=yes
 TYPE=Ethernet
 BRIDGE=comcast
 [root@virt02a network-scripts]# more ifcfg-eth2
 DEVICE=eth2
 ONBOOT=yes
 TYPE=Ethernet
 BRIDGE=ovirtmgmt
 MTU=9000
 
 

 nathan stratton | vp technology | broadsoft, inc | +1-240-404-6580 |
 www.broadsoft.com http://www.broadsoft.com
 
 
 ___
 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] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Daniel Helgenberger
Hello Sandro,

this is the upstream 'working' bug, the original bug was flagged
duplicate and posted for the 3.4 branch:
https://bugzilla.redhat.com/show_bug.cgi?id=1124451

Cheers


On 24.09.2014 16:05, Sandro Bonazzola wrote:
 Il 24/09/2014 15:48, Daniel Helgenberger ha scritto:
 Thanks Sandro,

 upgrading went really well and my datacenter is running 3.4.4 just fine.

 Nice to read that :-)


 I suppose [1] is still in this release? Any change this will be
 backported from 3.5?

 Cheers!

 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1130045
 As far as I know, that bug is on ioprocess package which doesn't exist in 3.4.
 CCing some people, maybe then can answer you.


 On 23.09.2014 23:06, Sandro Bonazzola wrote:
 The oVirt development team is pleased to announce the general
 availability of oVirt 3.4.4 as of Sep 23th 2014. This release
 solidifies oVirt as a leading KVM management application and open
 source alternative to VMware vSphere.

 oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
 (or similar).

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

 The existing repository ovirt-3.4 has been updated for delivering this
 release without the need of enabling any other repository, however since we
 introduced package signing you need an additional step in order to get
 the public keys installed on your system if you're upgrading from an older 
 release.
 Please refer to release notes [1] for Installation / Upgrade instructions.

 Please note that mirrors will need a couple of days before being 
 synchronized.
 If you want to be sure to use latest rpms and don't want to wait for the 
 mirrors,
 you can edit /etc/yum.repos.d/ovirt-3.4.repo commenting the mirror line and
 removing the comment on baseurl line.

 A new oVirt Live ISO will be available too[2].

 [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
 [2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso



-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] hosted engine setup on second host fails

2014-09-24 Thread Stefan Wendler
Oh well. I think this is fixed. I upgraded to 3.4.4 and the message
seems to be gone. the agents are running :)

Thank you very much !!! :)


On 09/24/2014 15:23, Stefan Wendler wrote:
 Okay, I'm truncating the previous mails here
 
 Davids hint was the solution. I had the ovirt hosts already added to the
 cluster and tried to do the hosted-engine-ha setup on them.
 
 After removing the hosts from the cluster and putting the data domain to
 maintenance mode I was able to deploy an all other nodes. I now have a
 HA'd hosted engine. Which can also be migrated \o/
 
 Maybe that is something that could be stated in the documentation more
 clearly?
 
 Unfortunately now I have a new problem. The agents crash rapidly after
 startup. The error is the following:
 (/var/log/ovirt-hosted-engine-ha/agent.log)
 
 AttributeError: 'NoneType' object has no attribute 'iteritems'
 
 And the whole output here - The agents have been started and I tried a
 migration of the hosted engine from ovirt host 1 to host 2 which
 succeeded. But the agents crashed afterwards:
 
 MainThread::INFO::2014-09-24
 15:09:24,839::agent::52::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
 ovirt-hosted-engine-ha agent 1.1.5 started
 MainThread::INFO::2014-09-24
 15:09:24,871::hosted_engine::223::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname)
 Found certificate common name: 10.8.2.101
 MainThread::INFO::2014-09-24
 15:09:25,081::hosted_engine::367::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker)
 Initializing ha-broker connection
 MainThread::INFO::2014-09-24
 15:09:25,082::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Starting monitor ping, options {'addr': '10.8.2.1'}
 MainThread::INFO::2014-09-24
 15:09:25,083::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Success, id 25293072
 MainThread::INFO::2014-09-24
 15:09:25,083::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Starting monitor mgmt-bridge, options {'use_ssl': 'true', 'bridge_name':
 'ovirtmgmt', 'address': '0'}
 MainThread::INFO::2014-09-24
 15:09:25,086::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Success, id 25294160
 MainThread::INFO::2014-09-24
 15:09:25,086::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Starting monitor mem-free, options {'use_ssl': 'true', 'address': '0'}
 MainThread::INFO::2014-09-24
 15:09:25,088::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Success, id 25293968
 MainThread::INFO::2014-09-24
 15:09:25,088::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Starting monitor cpu-load-no-engine, options {'use_ssl': 'true',
 'vm_uuid': 'e1ca293f-09e0-4d2e-8915-221839af1489', 'address': '0'}
 MainThread::INFO::2014-09-24
 15:09:25,089::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Success, id 25360400
 MainThread::INFO::2014-09-24
 15:09:25,089::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Starting monitor engine-health, options {'use_ssl': 'true', 'vm_uuid':
 'e1ca293f-09e0-4d2e-8915-221839af1489', 'address': '0'}
 MainThread::INFO::2014-09-24
 15:09:25,091::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
 Success, id 25509776
 MainThread::INFO::2014-09-24
 15:09:25,091::hosted_engine::391::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker)
 Broker initialized, all submonitors started
 MainThread::INFO::2014-09-24
 15:09:25,125::hosted_engine::476::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_sanlock)
 Ensuring lease for lockspace hosted-engine, host id 2 is acquired (file:
 /rhev/data-center/mnt/10.8.2.12:_volume1_engine-store/e313da39-594c-46b5-95c9-c445889c745c/ha_agent/hosted-engine.lockspace)
 MainThread::INFO::2014-09-24
 15:09:25,134::state_machine::153::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh)
 Global metadata: {'maintenance': False}
 MainThread::INFO::2014-09-24
 15:09:25,134::state_machine::158::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh)
 Host 10.8.2.100 (id 1): {'live-data': True, 'extra':
 'metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=1411564164
 (Wed Sep 24 15:09:24
 2014)\nhost-id=1\nscore=2400\nmaintenance=False\nstate=EngineUp\n',
 'hostname': '10.8.2.100', 'host-id': 1, 'engine-status': {'health':
 'good', 'vm': 'up', 'detail': 'up'}, 'score': 2400, 'maintenance':
 False, 'host-ts': 1411564164}
 MainThread::INFO::2014-09-24
 15:09:25,134::state_machine::158::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh)
 Host 10.8.2.102 (id 3): {'live-data': False, 'extra':
 'metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=1411562496
 (Wed Sep 24 14:41:36
 

Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Bob Doolittle

Cool!

However, the instructions for upgrading a Hosted Engine setup look 
suspiciously out of date and divergent from the instructions for 
upgrading standalone engine (e.g. you never run engine-setup??).


Is this page accurate:
http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine

I just fixed a bunch of egregious typos on the page myself - all of the 
hosted-engine invocation lines were incorrect (e.g. hosted-engine 
--set-maintenance=global instead of the now-corrected syntax: 
hosted-engine --set-maintenance --mode=global). This makes me somewhat 
cautious about the rest of the page content I'm afraid.


Is it accurate to say that when upgrading a Hosted Engine setup you 
basically just upgrade the packages (while carefully orchestrating which 
services are up at the time), and never run engine-setup?


If that page *is* accurate, why is engine-setup required for upgrading a 
standalone engine?


Thanks,
Bob

On 09/23/2014 05:05 PM, Sandro Bonazzola wrote:

The oVirt development team is pleased to announce the general
availability of oVirt 3.4.4 as of Sep 23th 2014. This release
solidifies oVirt as a leading KVM management application and open
source alternative to VMware vSphere.

oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
(or similar).

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

The existing repository ovirt-3.4 has been updated for delivering this
release without the need of enabling any other repository, however since we
introduced package signing you need an additional step in order to get
the public keys installed on your system if you're upgrading from an older 
release.
Please refer to release notes [1] for Installation / Upgrade instructions.

Please note that mirrors will need a couple of days before being synchronized.
If you want to be sure to use latest rpms and don't want to wait for the 
mirrors,
you can edit /etc/yum.repos.d/ovirt-3.4.repo commenting the mirror line and
removing the comment on baseurl line.

A new oVirt Live ISO will be available too[2].

[1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
[2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso



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


[ovirt-users] [oVirt 3.4.3] How to unlock HA in Creator VMs

2014-09-24 Thread Grzegorz Szypa
Hi experts.

How to unlock HA option in VMs creator, like in screen:

[image: Obraz w treści 1]

becouse I would configuring auto-start VMs after reboot/shutdown Physical
Server and configuring auto-suspeding VMs before
reboote/restart/shutdown.Physical Server

Is it possible?

Have anybody idea?


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


Re: [ovirt-users] Building vdsm within Fedora

2014-09-24 Thread Daniel Helgenberger

On 24.09.2014 10:57, Sandro Bonazzola wrote:
 Il 24/09/2014 09:44, Sven Kieske ha scritto:

 On 24/09/14 09:13, Federico Simoncelli wrote:
 You probably missed the first part we were using qemu-kvm/qemu-img in
 the spec file. In that case you won't fail in any requirement.

 Basically the question is: was there any problem on centos6 before
 committing http://gerrit.ovirt.org/31214 ?
 Federico: as we checked a few minutes ago, it seems there's no problem in 
 requiring qemu-kvm/qemu-img in the spec file.
 Only issue is that if non rhev version is installed a manual yum update is 
 required for moving to the rhevm version.
Indeed, I was about to complain in this thread myself ;) - Also, a 'yum
install qemu-kvm-rhev' might be more ovirt-way and works the same.
 Of course there was a problem, please follow the link in this very
 commit to the according bugzilla:

 https://bugzilla.redhat.com/show_bug.cgi?id=1127763

 In short: you can not use live snapshots without this updated spec file.

 And it's a PITA to install this package by hand, you must track
 it's versions yourself etc pp. you basically lose all the stuff
 a proper spec file gives you.
 Well, since the -rhev package is now available in 3.4, 3.5 and master repos 
 it shouldn't be a PITA anymore.



 PS: I also don't get the we want to get vdsm in every distribution
 a) it was never in any distro, it was in epel, which is a third party
 repository anyway, so you can just provide it via ovirt repo imho.
 b) no one packages vdsm for debian, ubuntu, gentoo, arch, suse,
 $nameyourdistro or I completely missed it, so why treat fedora
 in a special way? Don't misunderstand me, it would be cool if you
 have packages for every distro, or even bsd based stuff, but I think
 this is still a long way.
 c) will anyone use vdsm without ovirt? is this even possible?
 so imho you need ovirt repos anyway?





-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Sandro Bonazzola
Il 24/09/2014 16:37, Bob Doolittle ha scritto:
 Cool!
 
 However, the instructions for upgrading a Hosted Engine setup look 
 suspiciously out of date and divergent from the instructions for upgrading
 standalone engine (e.g. you never run engine-setup??).
 
 Is this page accurate:
 http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine
 
 I just fixed a bunch of egregious typos on the page myself - all of the 
 hosted-engine invocation lines were incorrect (e.g. hosted-engine
 --set-maintenance=global instead of the now-corrected syntax: hosted-engine 
 --set-maintenance --mode=global).

thanks!

 This makes me somewhat cautious about
 the rest of the page content I'm afraid.
 
 Is it accurate to say that when upgrading a Hosted Engine setup you basically 
 just upgrade the packages (while carefully orchestrating which services
 are up at the time), and never run engine-setup?

No, the engine must be updated as for a standalone engine by running the same 
update procedure:
- enable the new repo if needed (3.3 - 3.4 or 3.4 - 3.5)
- yum update
- engine-setup

 
 If that page *is* accurate, why is engine-setup required for upgrading a 
 standalone engine?

engine-setup is needed in order to upgrade the engine.
I've updated a bit 
http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine, hopefully 
should answer your questions.


 
 Thanks,
 Bob
 
 On 09/23/2014 05:05 PM, Sandro Bonazzola wrote:
 The oVirt development team is pleased to announce the general
 availability of oVirt 3.4.4 as of Sep 23th 2014. This release
 solidifies oVirt as a leading KVM management application and open
 source alternative to VMware vSphere.

 oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
 (or similar).

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

 The existing repository ovirt-3.4 has been updated for delivering this
 release without the need of enabling any other repository, however since we
 introduced package signing you need an additional step in order to get
 the public keys installed on your system if you're upgrading from an older 
 release.
 Please refer to release notes [1] for Installation / Upgrade instructions.

 Please note that mirrors will need a couple of days before being 
 synchronized.
 If you want to be sure to use latest rpms and don't want to wait for the 
 mirrors,
 you can edit /etc/yum.repos.d/ovirt-3.4.repo commenting the mirror line and
 removing the comment on baseurl line.

 A new oVirt Live ISO will be available too[2].

 [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
 [2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso

 


-- 
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] integration of overt with CloudForms

2014-09-24 Thread Bill Dossett
Hi,

I’m finally at the point that I think I would like to try and add my 
ovirt-engine to our commercial CloudForms portal… I seem to be reading that it 
is supported - but when adding the provider it asks for the api port for ovirt 
and I don’t know what that is… does anyone know if it works?  and if so what 
the API port for ovirt-engine is?  and anything else that I can read about it 
doing would be greatly appreciated

Thanks!

Bill Dossett
Virtualisation Architect

Pitney Bowes – Tech Central
6 Hercules Way, 600 Leavesden Park
Watford, WD25 7GS

Phone (+44) (0)1923 279353 | VOIP: 54739353
Mobile (+44) (0)7775 908612

bill.doss...@pb.commailto:bill.doss...@pb.com
www.pb.comhttp://www.pb.com/

In Engineering? Raise a ticket via Remedy Anywhere 
[HEREhttp://teamsite.inside.pb.com/sites/TCPPM/GES/Lists/Create%20Incident/newIncident.aspx]
 takes less than a minute


ManageIQ User Guide available 
[HEREhttps://dl.dropbox.com/u/6219441/ManageIQ%20-%20User%20Manual%20PB%20v4.pdf]

Check out the ManageIQ Blog for recent enhancements and information 
[HERE]http://teamsite.inside.pb.com/sites/TCPPM/GES/manageiq/default.aspx




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


Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Sandro Bonazzola
Il 24/09/2014 16:14, Daniel Helgenberger ha scritto:
 Hello Sandro,
 
 this is the upstream 'working' bug, the original bug was flagged
 duplicate and posted for the 3.4 branch:
 https://bugzilla.redhat.com/show_bug.cgi?id=1124451

The bugs was opened against 3.4 and targeted to 3.6.
Then it has been identified as a duplicate of a bug on ioprocess for 3.5 and 
fixed.
Looks like assignee did not mark this for being backported to 3.4.z.
Other than that, waiting for assignee reply to the thread.

 
 Cheers
 
 
 On 24.09.2014 16:05, Sandro Bonazzola wrote:
 Il 24/09/2014 15:48, Daniel Helgenberger ha scritto:
 Thanks Sandro,

 upgrading went really well and my datacenter is running 3.4.4 just fine.

 Nice to read that :-)


 I suppose [1] is still in this release? Any change this will be
 backported from 3.5?

 Cheers!

 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1130045
 As far as I know, that bug is on ioprocess package which doesn't exist in 
 3.4.
 CCing some people, maybe then can answer you.


 On 23.09.2014 23:06, Sandro Bonazzola wrote:
 The oVirt development team is pleased to announce the general
 availability of oVirt 3.4.4 as of Sep 23th 2014. This release
 solidifies oVirt as a leading KVM management application and open
 source alternative to VMware vSphere.

 oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
 (or similar).

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

 The existing repository ovirt-3.4 has been updated for delivering this
 release without the need of enabling any other repository, however since we
 introduced package signing you need an additional step in order to get
 the public keys installed on your system if you're upgrading from an older 
 release.
 Please refer to release notes [1] for Installation / Upgrade instructions.

 Please note that mirrors will need a couple of days before being 
 synchronized.
 If you want to be sure to use latest rpms and don't want to wait for the 
 mirrors,
 you can edit /etc/yum.repos.d/ovirt-3.4.repo commenting the mirror line and
 removing the comment on baseurl line.

 A new oVirt Live ISO will be available too[2].

 [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
 [2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso


 


-- 
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


Re: [ovirt-users] [oVirt 3.4.3] How to unlock HA in Creator VMs

2014-09-24 Thread Daniel Helgenberger
Hello Grzegorz,

can you please verify you have the following:
- in resource allocation tab, no CPU pinning
- in host tab, allow 'automatic migration' or 'automatic and manual
migration'

Only if auto migrate is active, you may activate high availability.

On 24.09.2014 16:39, Grzegorz Szypa wrote:
 Hi experts.

 How to unlock HA option in VMs creator, like in screen:

 Obraz w treści 1

 becouse I would configuring auto-start VMs after reboot/shutdown Physical 
 Server 
 and configuring auto-suspeding VMs before reboote/restart/shutdown.Physical 
 Server

 Is it possible?

 Have anybody idea?


 Regards,
 Grzegorz Szypa

-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Daniel Helgenberger

On 24.09.2014 16:52, Sandro Bonazzola wrote:
 Il 24/09/2014 16:14, Daniel Helgenberger ha scritto:
 Hello Sandro,

 this is the upstream 'working' bug, the original bug was flagged
 duplicate and posted for the 3.4 branch:
 https://bugzilla.redhat.com/show_bug.cgi?id=1124451
 The bugs was opened against 3.4 and targeted to 3.6.
 Then it has been identified as a duplicate of a bug on ioprocess for 3.5 and 
 fixed.
 Looks like assignee did not mark this for being backported to 3.4.z.
Thanks for the info Sandro.
IMHO this is a major issue and *should* be backported if possible to
3.4.x (right now I have a cron job restarting vdsmd once a week). I'll
add a comment on BZ to make sure ;)

 Other than that, waiting for assignee reply to the thread.

 Cheers


 On 24.09.2014 16:05, Sandro Bonazzola wrote:
 Il 24/09/2014 15:48, Daniel Helgenberger ha scritto:
 Thanks Sandro,

 upgrading went really well and my datacenter is running 3.4.4 just fine.

 Nice to read that :-)


 I suppose [1] is still in this release? Any change this will be
 backported from 3.5?

 Cheers!

 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1130045
 As far as I know, that bug is on ioprocess package which doesn't exist in 
 3.4.
 CCing some people, maybe then can answer you.


 On 23.09.2014 23:06, Sandro Bonazzola wrote:
 The oVirt development team is pleased to announce the general
 availability of oVirt 3.4.4 as of Sep 23th 2014. This release
 solidifies oVirt as a leading KVM management application and open
 source alternative to VMware vSphere.

 oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
 (or similar).

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

 The existing repository ovirt-3.4 has been updated for delivering this
 release without the need of enabling any other repository, however since 
 we
 introduced package signing you need an additional step in order to get
 the public keys installed on your system if you're upgrading from an 
 older release.
 Please refer to release notes [1] for Installation / Upgrade instructions.

 Please note that mirrors will need a couple of days before being 
 synchronized.
 If you want to be sure to use latest rpms and don't want to wait for the 
 mirrors,
 you can edit /etc/yum.repos.d/ovirt-3.4.repo commenting the mirror line 
 and
 removing the comment on baseurl line.

 A new oVirt Live ISO will be available too[2].

 [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
 [2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso



-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Bob Doolittle

On 09/24/2014 10:47 AM, Sandro Bonazzola wrote:

Il 24/09/2014 16:37, Bob Doolittle ha scritto:

If that page *is* accurate, why is engine-setup required for upgrading a 
standalone engine?

engine-setup is needed in order to upgrade the engine.
I've updated a bit 
http://www.ovirt.org/Hosted_Engine_Howto#Upgrade_Hosted_Engine, hopefully 
should answer your questions.


I am using Fedora 19 for host and engine.

When I try to follow these instructions I get to the point of restarting 
VDSM on the host, and get:


# service vdsm restart
Redirecting to /bin/systemctl restart  vdsm.service
Failed to issue method call: Unit vdsm.service failed to load: No such file or 
directory. See system logs and 'systemctl status vdsm.service' for details.


VDSM was still running, but systemctl did not think so:

# systemctl stop vdsm
Failed to issue method call: Unit vdsm.service not loaded.


So instead at that point I shut down the engine (init 0) and rebooted 
the engine-hosting host.


Things came up cleanly at that point.

-Bob

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


[ovirt-users] 3.4: VDSM Memory consumption

2014-09-24 Thread Daniel Helgenberger
Hi Dan,

just to get this right, you yourself pointed me to the BZ. I was looking
at the duplicate, since the metadata tags 3.4. Sorry my lack of
knowlage, I really have no idea whatever there is an ioprocess python
binding in 3.4 or not - I just see vdsmd resident size growing in 3.4.
The top output below was from 3.4.3; I just upgraded to 3.4.4. But
clearly vdsmd should not use 10GB RAM?

Thanks!
On 01.09.2014 18:08, Dan Kenigsberg wrote:
 On Mon, Sep 01, 2014 at 03:30:53PM +, Daniel Helgenberger wrote:
 Hello,

 in my LAB cluster I run into OOM conditions frequently because of a huge
 VDSM process. The memory stats from my nodes right now:

 Node A; running one VM:
   PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND 
  3465 vdsm   0 -20 18.6g 9.8g 8244 S 32.1 50.3  27265:21 vdsm
  
  
  7439 qemu  20   0 5641m 4.1g 4280 S 22.9 20.9  12737:08 qemu-kvm
  
  
  2912 root  15  -5 2710m  35m 5968 S  0.0  0.2   0:04.76 supervdsmServer 

 Node B, running 3 VMs including HosedEngine:
   PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND 
 9079 vdsm   0 -20  9.9g 5.0g 7496 S 49.7 43.0  11858:06 vdsm 
  
 
  3347 qemu  20   0 7749m 1.8g 5264 S  4.3 15.8   3:25.71 qemu-kvm
  
  
 18463 qemu  20   0 3865m 415m 5516 R  1.6  3.5 359:15.24 qemu-kvm
  
  
 11755 qemu  20   0 3873m 276m 5336 S 80.5  2.3  21639:39 qemu-kvm

 Basically VDSM consumes more then all my VMs.

 I thought of VDSM as a 'supervisor' process for qemu-kvm?

 I attached recend vdsm logs as well as a screen shot.
 Thanks for your report. It sounds like

 Bug 1130045 - Very high memory consumption

 which we believe is due to python-ioprocess.


-- 
Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN


www.m-box.de  www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

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


Re: [ovirt-users] hosted engine setup on second host fails

2014-09-24 Thread Itamar Heim
Seems we should consider not adding the host if already there. Please open a 
bug.
Though I really hope in 3.6 to see this done from the gui

On Sep 24, 2014 4:23 PM, Stefan Wendler stefan.wend...@tngtech.com wrote:

 Okay, I'm truncating the previous mails here 

 Davids hiOkay, I'm truncating the previous mails here

Davids hint was the solution. I had the ovirt hosts already added to the
cluster and tried to do the hosted-engine-ha setup on them.

After removing the hosts from the cluster and putting the data domain to
maintenance mode I was able to deploy an all other nodes. I now have a
HA'd hosted engine. Which can also be migrated \o/

Maybe that is something that could be stated in the documentation more
clearly?

Unfortunately now I have a new problem. The agents crash rapidly after
startup. The error is the following:
(/var/log/ovirt-hosted-engine-ha/agent.log)

AttributeError: 'NoneType' object has no attribute 'iteritems'

And the whole output here - The agents have been started and I tried a
migration of the hosted engine from ovirt host 1 to host 2 which
succeeded. But the agents crashed afterwards:

MainThread::INFO::2014-09-24
15:09:24,839::agent::52::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
ovirt-hosted-engine-ha agent 1.1.5 started
MainThread::INFO::2014-09-24
15:09:24,871::hosted_engine::223::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname)
Found certificate common name: 10.8.2.101
MainThread::INFO::2014-09-24
15:09:25,081::hosted_engine::367::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker)
Initializing ha-broker connection
MainThread::INFO::2014-09-24
15:09:25,082::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Starting monitor ping, options {'addr': '10.8.2.1'}
MainThread::INFO::2014-09-24
15:09:25,083::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Success, id 25293072
MainThread::INFO::2014-09-24
15:09:25,083::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Starting monitor mgmt-bridge, options {'use_ssl': 'true', 'bridge_name':
'ovirtmgmt', 'address': '0'}
MainThread::INFO::2014-09-24
15:09:25,086::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Success, id 25294160
MainThread::INFO::2014-09-24
15:09:25,086::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Starting monitor mem-free, options {'use_ssl': 'true', 'address': '0'}
MainThread::INFO::2014-09-24
15:09:25,088::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Success, id 25293968
MainThread::INFO::2014-09-24
15:09:25,088::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Starting monitor cpu-load-no-engine, options {'use_ssl': 'true',
'vm_uuid': 'e1ca293f-09e0-4d2e-8915-221839af1489', 'address': '0'}
MainThread::INFO::2014-09-24
15:09:25,089::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Success, id 25360400
MainThread::INFO::2014-09-24
15:09:25,089::brokerlink::126::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Starting monitor engine-health, options {'use_ssl': 'true', 'vm_uuid':
'e1ca293f-09e0-4d2e-8915-221839af1489', 'address': '0'}
MainThread::INFO::2014-09-24
15:09:25,091::brokerlink::137::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
Success, id 25509776
MainThread::INFO::2014-09-24
15:09:25,091::hosted_engine::391::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker)
Broker initialized, all submonitors started
MainThread::INFO::2014-09-24
15:09:25,125::hosted_engine::476::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_sanlock)
Ensuring lease for lockspace hosted-engine, host id 2 is acquired (file:
/rhev/data-center/mnt/10.8.2.12:_volume1_engine-store/e313da39-594c-46b5-95c9-c445889c745c/ha_agent/hosted-engine.lockspace)
MainThread::INFO::2014-09-24
15:09:25,134::state_machine::153::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh)
Global metadata: {'maintenance': False}
MainThread::INFO::2014-09-24
15:09:25,134::state_machine::158::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh)
Host 10.8.2.100 (id 1): {'live-data': True, 'extra':
'metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=1411564164
(Wed Sep 24 15:09:24
2014)\nhost-id=1\nscore=2400\nmaintenance=False\nstate=EngineUp\n',
'hostname': '10.8.2.100', 'host-id': 1, 'engine-status': {'health':
'good', 'vm': 'up', 'detail': 'up'}, 'score': 2400, 'maintenance':
False, 'host-ts': 1411564164}
MainThread::INFO::2014-09-24
15:09:25,134::state_machine::158::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh)
Host 10.8.2.102 (id 3): {'live-data': False, 'extra':
'metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=1411562496
(Wed Sep 24 14:41:36

Re: [ovirt-users] 3.4: VDSM Memory consumption

2014-09-24 Thread Dan Kenigsberg
 On 01.09.2014 18:08, Dan Kenigsberg wrote:
  On Mon, Sep 01, 2014 at 03:30:53PM +, Daniel Helgenberger wrote:
  Hello,
 
  in my LAB cluster I run into OOM conditions frequently because of a huge
  VDSM process. The memory stats from my nodes right now:
 
  Node A; running one VM:
PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND 
   3465 vdsm   0 -20 18.6g 9.8g 8244 S 32.1 50.3  27265:21 vdsm  
 
   
   7439 qemu  20   0 5641m 4.1g 4280 S 22.9 20.9  12737:08 qemu-kvm  
 
   
   2912 root  15  -5 2710m  35m 5968 S  0.0  0.2   0:04.76 
  supervdsmServer 
 
  Node B, running 3 VMs including HosedEngine:
PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND 
  9079 vdsm   0 -20  9.9g 5.0g 7496 S 49.7 43.0  11858:06 vdsm   
 
  
   3347 qemu  20   0 7749m 1.8g 5264 S  4.3 15.8   3:25.71 qemu-kvm  
 
   
  18463 qemu  20   0 3865m 415m 5516 R  1.6  3.5 359:15.24 qemu-kvm  
 
   
  11755 qemu  20   0 3873m 276m 5336 S 80.5  2.3  21639:39 qemu-kvm
 
  Basically VDSM consumes more then all my VMs.
 
  I thought of VDSM as a 'supervisor' process for qemu-kvm?
 
  I attached recend vdsm logs as well as a screen shot.
  Thanks for your report. It sounds like
 
  Bug 1130045 - Very high memory consumption
 
  which we believe is due to python-ioprocess.

On Wed, Sep 24, 2014 at 03:39:25PM +, Daniel Helgenberger wrote:
 Hi Dan,
 
 just to get this right, you yourself pointed me to the BZ. I was looking
 at the duplicate, since the metadata tags 3.4. Sorry my lack of
 knowlage, I really have no idea whatever there is an ioprocess python
 binding in 3.4 or not - I just see vdsmd resident size growing in 3.4.
 The top output below was from 3.4.3; I just upgraded to 3.4.4. But
 clearly vdsmd should not use 10GB RAM?

I'm sorry to have mislead you. The bug I refered to was indeed due to
ioprocess, and caused a very dramatic memory leak in 3.5. We have yet
another memory leak in 3.5.0, when managing gluster blocks
Bug 1142647 - supervdsm leaks memory when using glusterfs

3.4.z does not use ioprocess, and do not have that gluster bug, so you
are seeing completely different and much older.

These leaks are not so easy to debug - but they are important. I'd love
if you open a BZ about it. Please specify the rate of the leak, when
does it happen (when a host has VMs? when a host is polled by Engine? On
nfs? iscsi?

What's `lsof -p pid-of-fat-vdsm`?

I think that Francesco has some debug patches to help nail it down - he
can provide smarter questions.

Dan.

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


Re: [ovirt-users] [ANN] oVirt 3.4.4 Release is now available

2014-09-24 Thread Dan Kenigsberg
On Wed, Sep 24, 2014 at 02:58:59PM +, Daniel Helgenberger wrote:
 
 On 24.09.2014 16:52, Sandro Bonazzola wrote:
  Il 24/09/2014 16:14, Daniel Helgenberger ha scritto:
  Hello Sandro,
 
  this is the upstream 'working' bug, the original bug was flagged
  duplicate and posted for the 3.4 branch:
  https://bugzilla.redhat.com/show_bug.cgi?id=1124451
  The bugs was opened against 3.4 and targeted to 3.6.
  Then it has been identified as a duplicate of a bug on ioprocess for 3.5 
  and fixed.
  Looks like assignee did not mark this for being backported to 3.4.z.
 Thanks for the info Sandro.
 IMHO this is a major issue and *should* be backported if possible to
 3.4.x (right now I have a cron job restarting vdsmd once a week). I'll
 add a comment on BZ to make sure ;)

Toni can correct me, but I believe that he reprorted
Bug 1124451 - vdsm leaks memory
on a setup using ioprocess; that's why I've marked it as a dup of
Bug 1130045 - Very high memory consumption

Apparently, we have another memory leak, besides the one(s) instroduced
in the 3.5 branch. It's not a new one - certainly not new to 3.4.4.

I think it would be best to report a fresh one, with a precise vdsm
version, and further info I requested in a parallel thread.

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


Re: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM

2014-09-24 Thread Gianluca Cecchi
On Wed, Sep 24, 2014 at 12:58 PM, Omer Frenkel ofren...@redhat.com wrote:



 - Original Message -
  From: Gianluca Cecchi gianluca.cec...@gmail.com
  To: users users@ovirt.org
  Sent: Tuesday, September 23, 2014 1:56:07 AM
  Subject: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM

  No errors in vdsm.log of host and in VM logfile under
 /var/log/libvirt/qemu
  on hypervisor.
 

 do you see the call for changeCD in vdsm?
 it looks like the call somehow failed
 does it happens all the time?


Hello,
I have only created a CentOS 6.5 VM and an ubuntu 14.04.1 VM both 64 bit.
Both have the problem.
See vdsm.log compressed here:
https://drive.google.com/file/d/0BwoPbcrMv8mvRzlvcjdzd0Q5Q00/edit?usp=sharing

mount attempt around 19:47 and I actually see this in vdsm.log; previously
I searched for ERROR messages only, but it seems it is identified as a
WARNING level message):

Thread-837731::DEBUG::2014-09-24
19:47:21,928::__init__::467::jsonrpc.JsonRpcServer::(_serveRequest) Calling
'VM.changeCD' in bridge with {u'driveSpec':
u'/rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----/ovirt-guest-tools-3.5_5.iso',
u'vmID': u'168470b1-b7eb-4dab-8fa4-6b744e2ad738'}
Thread-837731::INFO::2014-09-24
19:47:21,931::clientIF::331::vds::(prepareVolumePath) prepared volume path:
/rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/----/ovirt-guest-tools-3.5_5.iso
Thread-837731::WARNING::2014-09-24
19:47:21,951::clientIF::361::vds::(teardownVolumePath) Drive is not a vdsm
image: None
Traceback (most recent call last):
  File /usr/share/vdsm/clientIF.py, line 354, in teardownVolumePath
if vm.isVdsmImage(drive):
  File /usr/share/vdsm/virt/vm.py, line 112, in isVdsmImage
return all(k in drive for k in required)
  File /usr/share/vdsm/virt/vm.py, line 112, in genexpr
return all(k in drive for k in required)
TypeError: argument of type 'NoneType' is not iterable


I see also these kind of messages

Thread-838408::WARNING::2014-09-24
19:57:20,583::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,583::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,583::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,583::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,583::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,584::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,584::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,584::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,584::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,584::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,585::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,585::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,585::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,585::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,585::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,586::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,586::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,586::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,586::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,586::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,586::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,587::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,587::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,587::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24
19:57:20,587::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
Thread-838408::WARNING::2014-09-24
19:57:20,587::Bridge::448::root::(fieldClone) fieldClone: type - deviceType
Thread-838408::WARNING::2014-09-24

[ovirt-users] Template Independent vs Dependent

2014-09-24 Thread J. Mikulec

Hello,

if I create VM from template through web manager, it shows in General - 
Template Clone/Independent. When created through REST API, it shows 
Thin/Dependent. When it is Thin/Dependent, it is not possible to 
remove used template but VM creation is much faster. I would like to 
have more info about this but cannot find any. So I cannot find how to 
create Independent with REST API.


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


[ovirt-users] ipv6 FTP not enabled on resources ?

2014-09-24 Thread R P Herrold

I get this message trying to mirror some content off
resources.ovirt.org

The following error was encountered while trying to retrieve 
the URL: ftp://resources.ovirt.org/pub/ovirt-3.3/rpm/el6/

Connection to 2600:3c01::f03c:91ff:fe93:4b0d failed.

The system returned: (111) Connection refused

Is ip6tables not opened, or the anon. ftpd not listening on 
ipv6?  if not, could it please be enabled?  It is not possible 
to readily mirror content off through http ...

Thanks

-- Russ herrold

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


Re: [ovirt-users] overt viewer on mac osx

2014-09-24 Thread Paul Heinlein

On Wed, 24 Sep 2014, Bill Dossett wrote:

I have downloaded and installed per the instructions - and then 
downloaded the console.vv file and run the command line to start the 
viewer with the console.vv - the first time it popped up and then 
said that spice needed authentication… tried my virt-engine password 
that didn’t work, hit cancel and it shut down.  Tried it again and 
now it just says it can’t determine the connection type from uri and 
I have to quit.


I am running OSX 10.9.4 and apparently this has only been tested on 
10.9.1… hoping there is a fix to make this work, or am I doing 
something wrong?  The command I am using is


If you're willing to use VNC instead of SPICE, the attached python 
script will parse console.vv and pass the relevant information to the 
Mac Screen Sharing application (or whatever app you use to open vnc:// 
URLs).


Once you've downloaded console.vv, just run the script. By default, 
the script will look for ~/Downloads/console.vv, but that can be 
changed on the command line.


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W#!/usr/bin/python
#
# oVirt Engine 3.3 will send a user requesting a console a little
# ini-style file with the host/port/password information necessary
# for connecting to a VM via VNC. On a Mac, that file (typically
# named console.vv) is useless as-is. This script parses console.vv
# and passes a vnc:// URL to /usr/bin/open.
#
# A reasonable console.vv file will look something like this:
#
# [virt-viewer]
# type=vnc
# host=your.host.com
# port=5907
# password=ZOrRmRBNlzaK
# delete-this-file=1
# title=VNC
#
# From that file, this script will create a vnc url. The Mac
# Screen Sharing application will accept an old-style URL with
# a username:password prepended to the hostname; oVirt doesn't
# provide a username, so we leave that blank. In the example
# above, the resulting URL would be
#
#   vnc://:zorrmrbnl...@your.host.com:5907
#
# Since ovirt-assigned vnc passwords expire after 120 seconds, this
# script by default will delete the ini file after parsing it.
#
# ==

import ConfigParser, argparse, subprocess, sys, os.path

# open(1) knows how to deal with various file and string types
opener = /usr/bin/open
# define the correct section name in console.vv
header = virt-viewer
# the default location of the ini file; this can be overridden
# by passing the filename to the script
defaultvv = os.path.expandvars( ${HOME}/Downloads/console.vv )

# set up the ArgumentParser
parser = argparse.ArgumentParser(
  description='Parse and execute virt-viewer VNC ini file',
  epilog='The console.vv file must have a [virt-viewer] heading, a type=vnc 
entry, and entries for host, port, and password to parse correctly.')
parser.add_argument( '-k', '--keep', action='store_true',
  help='keep vvfile after parsing (default is to delete it)')
parser.add_argument( 'vvfile',
  nargs='?',
  default=defaultvv,
  help='console.vv file from oVirt (default: ~/Downloads/console.vv)')
args = parser.parse_args()

# make sure the file is readable
if not os.path.isfile(args.vvfile):
  sys.stderr.write( args.vvfile +  is not readable or doesn't exist.\n )
  parser.print_usage(file=sys.stderr)
  sys.exit()

### parse the config file
c = ConfigParser.ConfigParser()
try:
  c.read( args.vvfile )
except ConfigParser.Error:
  sys.stderr.write( args.vvfile +  doesn't parse correctly.\n )
  sys.stderr.write( Are you sure you got it from the right place?\n )
  sys.exit()

# make sure we have a virt-viewer section
try:
  c.has_section( header )
except ConfigParser.NoSectionError:
  sys.stderr.write( Cannot find necessary [ + header + ] section.\n )
  sys.exit()

# make sure that, within the virt-viewer section, there's a type=vnc
# option
try:
  c.has_option( header, 'type' )
except ConfigParser.NoOptionError:
  sys.stderr.write( Cannot find necessary 'type' option.\n )
  sys.exit()

if not 'vnc' == c.get( header, 'type' ):
  sys.stderr.write( 'type' option option is not 'vnc'.\n )
  sys.exit()

# grab the hostname.
try:
  rhost = c.get( header, 'host' )
except ConfigParser.NoOptionError:
  sys.stderr.write( Cannot find host definition.\n )
  sys.exit()

# grab the port value, make sure it's an integer, and test that it's
# roughly in the correct range (5900-5950) for VNC sessions
try:
  strport = c.get( header, 'port' )
except ConfigParser.NoOptionError:
  sys.stderr.write( Cannot find port definition.\n )
  sys.exit()

try:
  rport = int(strport)
except ValueError:
  sys.stderr.write( The listed port is not an integer.\n )
  sys.exit()

if rport  5900:
  sys.stderr.write( The port ( + strport + ) is an unexpected number.\n )
  sys.exit()
if rport  5950:
  sys.stderr.write( The port ( + strport + ) is an unexpected number.\n )
  sys.exit()

# grab the password
try:
  rpass = c.get( header, 'password' )
except ConfigParser.NoOptionError:
  sys.stderr.write( Cannot find password definition.\n )
  sys.exit()

# 

[ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-24 Thread Gianluca Cecchi
Hello,
after upgrading engine and hypervisor to rc3 I get this message when trying
to start VM:

VM vm_name is down with error. Exit message: internal error internal error
NUMA memory tuning in 'preferred' mode only supports single node.

hypervisor is Intel blade MFS5520VI with

processor: 15
vendor_id: GenuineIntel
cpu family: 6
model: 26
model name: Intel(R) Xeon(R) CPU   X5570  @ 2.93GHz
stepping: 5
cpu MHz: 2927.000
cache size: 8192 KB
physical id: 1
siblings: 8
core id: 3
cpu cores: 4
apicid: 23
initial apicid: 23
fpu: yes
fpu_exception: yes
cpuid level: 11
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca
sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
bogomips: 5851.73
clflush size: 64
cache_alignment: 64
address sizes: 40 bits physical, 48 bits virtual
power management:

Did anything change from rc2 to rc3 regarding this?

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


Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3

2014-09-24 Thread Gianluca Cecchi
On Thu, Sep 25, 2014 at 1:58 AM, Gianluca Cecchi gianluca.cec...@gmail.com
wrote:

 Hello,
 after upgrading engine and hypervisor to rc3 I get this message when
 trying to start VM:

 VM vm_name is down with error. Exit message: internal error internal error
 NUMA memory tuning in 'preferred' mode only supports single node.

 hypervisor is Intel blade MFS5520VI with

 processor: 15
 vendor_id: GenuineIntel
 cpu family: 6
 model: 26
 model name: Intel(R) Xeon(R) CPU   X5570  @ 2.93GHz
 stepping: 5
 cpu MHz: 2927.000
 cache size: 8192 KB
 physical id: 1
 siblings: 8
 core id: 3
 cpu cores: 4
 apicid: 23
 initial apicid: 23
 fpu: yes
 fpu_exception: yes
 cpuid level: 11
 wp: yes
 flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
 cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
 aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca
 sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
 bogomips: 5851.73
 clflush size: 64
 cache_alignment: 64
 address sizes: 40 bits physical, 48 bits virtual
 power management:

 Did anything change from rc2 to rc3 regarding this?

 Gianluca



If it can be of any help, both engine and node are CentOS 6.5 and on node I
have this output from numactl command:

[root@ovnode04 vdsm]# numactl --show
policy: default
preferred node: current
physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
cpubind: 0 1
nodebind: 0 1
membind: 0 1

[root@ovnode04 vdsm]# numactl --hardware
available: 2 nodes (0-1)
node 0 cpus: 0 2 4 6 8 10 12 14
node 0 size: 8128 MB
node 0 free: 7567 MB
node 1 cpus: 1 3 5 7 9 11 13 15
node 1 size: 8192 MB
node 1 free: 7747 MB
node distances:
node   0   1
  0:  10  21
  1:  21  10


In engine.log:
2014-09-25 01:58:18,050 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(org.ovirt.thread.pool-8-thread-16) [21714fa2]
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand
kvmEnable=true,keyboardLayout=en-us,nice=0,pitReinjection=false,displayNetwork=ovirtmgmt,copyPasteEnable=true,timeOffset=7200,transparentHugePages=true,vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,acpiEnable=true,custom={device_fc07dfb4-c33c-4302-915f-fcafcbaf201fdevice_814694f2-e3d9-4808-87d1-1576acbb6b39device_8e5365f1-1027-498e-9453-0289278434d4device_ef937c2a-c7ca-4405-98d8-72387b983ed7=VmDevice
{vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,
deviceId=ef937c2a-c7ca-4405-98d8-72387b983ed7, device=spicevmc,
type=CHANNEL, bootOrder=0, specParams={}, address={bus=0, controller=0,
type=virtio-serial, port=3}, managed=false, plugged=true, readOnly=false,
deviceAlias=channel2, customProperties={}, snapshotId=null},
device_fc07dfb4-c33c-4302-915f-fcafcbaf201f=VmDevice
{vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,
deviceId=fc07dfb4-c33c-4302-915f-fcafcbaf201f, device=ide, type=CONTROLLER,
bootOrder=0, specParams={}, address={slot=0x01, bus=0x00, domain=0x,
type=pci, function=0x1}, managed=false, plugged=true, readOnly=false,
deviceAlias=ide0, customProperties={}, snapshotId=null},
device_fc07dfb4-c33c-4302-915f-fcafcbaf201fdevice_814694f2-e3d9-4808-87d1-1576acbb6b39device_8e5365f1-1027-498e-9453-0289278434d4=VmDevice
{vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,
deviceId=8e5365f1-1027-498e-9453-0289278434d4, device=unix, type=CHANNEL,
bootOrder=0, specParams={}, address={bus=0, controller=0,
type=virtio-serial, port=2}, managed=false, plugged=true, readOnly=false,
deviceAlias=channel1, customProperties={}, snapshotId=null},
device_fc07dfb4-c33c-4302-915f-fcafcbaf201fdevice_814694f2-e3d9-4808-87d1-1576acbb6b39=VmDevice
{vmId=0ce8ebc0-8464-4e9a-b382-1836234b3560,
deviceId=814694f2-e3d9-4808-87d1-1576acbb6b39, device=unix, type=CHANNEL,
bootOrder=0, specParams={}, address={bus=0, controller=0,
type=virtio-serial, port=1}, managed=false, plugged=true, readOnly=false,
deviceAlias=channel0, customProperties={},
snapshotId=null}},spiceSslCipherSuite=DEFAULT,memSize=2048,smp=2,emulatedMachine=rhel6.5.0,vmType=kvm,memGuaranteedSize=1365,display=qxl,smartcardEnable=false,bootMenuEnable=false,numaTune={mode=preferred,
nodeset=0,1},spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard,smpCoresPerSocket=1,maxVCpus=16,devices=[{address={bus=0x00,
domain=0x, type=pci, slot=0x02, function=0x0}, specParams={ram=65536,
vram=32768, heads=1}, device=qxl, type=video,
deviceId=544e064e-f2df-40c8-89e3-9311cc82af45}, {shared=false, iface=ide,
index=2, address={unit=0, bus=1, target=0, controller=0, type=drive},
specParams={path=}, path=, device=cdrom, type=disk, readonly=true,
deviceId=00fd82da-3da6-45c1-b18b-54e3ccb52c9b}, {shared=false, index=0,
volumeID=72821a56-1806-4b8f-bd73-7b5ef4f3c12f, propagateErrors=off,
format=cow, type=disk, iface=scsi, bootOrder=1, address={unit=0, bus=0,
target=0,