Re: [ovirt-users] oVirt 3.4 could not install Windows server 08 R2 with virtio / virtio SCSI

[Daniel Helgenberger]

Hello Paul,

I run both windows server 2008r2/2012r2 in oVirt 3.4 (qemu/kvm for that 
matter). 

I can only recommend to try the following procedure in dealing with virtio-blk 
and virtio-scsi:
Install Windows on a IDE drive; add a second image virtio-scsi.
After the installation finishes install the driver for the unknown controller 
you find in device management with 'update driver'
Shutdown the vm, change the boot disk to virtio-scsi or virtio-blk respectively 
and remove the second disk if you like. 

Hope this helps,

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

> Am 05.05.2014 um 17:29 schrieb "Paul.LKW" :
> 
> Hi All:
> I just even tryied to use IDE only and the Windows 08 server R2 still could 
> not find any harddisk, what does this bug exists in version 3.4? does it 
> suitable for production? which one should I report this bug for ?
> 
> Paul.LKW
> 
> 
> 於 4/5/2014 21:17, Paul.LKW 提到:
>> Hi Joop
>> It should be show me the harddisk drive after the driver installed and then 
>> change back to the installation media disc, but the case is it could not 
>> load the driver correctly I could not see the harddisk drive so even I 
>> change back the media disc should be no meaning?
>> 
>> Paul.LKW
>> 
>> 於 2014/5/4 下午8:48，"Joop"  寫道：
>>> Paul.LKW wrote:
 
 Hi All:
 I am new to oVirt and just installed oVirt for a try.
 Any one could install Win Server 08 R2 with virtio or virtio 
 SCSI from oVirt 3.4?
 I am already changed the driver during the installation with 
 virtio-win-0.1-74.iso, however I try what ever driver directory for AMD64 
 it show the device but when I click to select and then click OK, it always 
 say "No new device could be found. Make sure the driver files are correct 
 and located on the driver installation media".
 Does any other see this issue, and know how to solve?
 Many thanks
>>> Did you change back to your W2K8 iso after loading the driver?
>>> The installer displays a very misleading message if you don't have your iso 
>>> back in the cdrom after installing the drivers.
>>> 
>>> Joop
>>> 
>>> ___
>>> 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


smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] "Could not connect host to Data Center" after rebooting, how to resolve?

[Boudewijn Ector]

On 01-05-14 12:48, Boudewijn Ector wrote:
> Gadi Ickowicz schreef op 1-5-2014 7:54:
>> Hi,
>>
>> Could you please attach the vdsm logs for the host for the time around the 
>> logs you pasted from the engine.log?
>>
>> Thanks,
>> Gadi Ickowicz
>>
> Sure I wasn't even aware of the /var/log/vdsm directory...
>
>
>
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,043::BindingXMLRPC::251::vds::(wrapper) client [192.168.1.44] 
>> flowID [61130377]
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,044::task::595::TaskManager.Task::(_updateState) 
>> Task=`217a7d59-fe83-4be5-b7e5-ce19c17a8d82`::moving from state init -> state 
>> preparing
>> vdsm.log.11:Thread-23::INFO::2014-04-30 
>> 15:50:00,044::logUtils::44::dispatcher::(wrapper) Run and protect: 
>> connectStorageServer(domType=1, 
>> spUUID='----', conList=[{'connection': 
>> '192.168.1.44:/raid/ovirt/data', 'iqn': '', 'portal': '', 'user': '', 
>> 'password': '**', 'id': '3021c4ab-5cb8-455b-be5f-2c79b0e3b23b', 'port': 
>> ''}], options=None)
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,048::hsm::2317::Storage.HSM::(__prefetchDomains) nfs local path: 
>> /rhev/data-center/mnt/192.168.1.44:_raid_ovirt_data
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,049::hsm::2341::Storage.HSM::(__prefetchDomains) Found SD uuids: 
>> ('6bee0e2d-961c-453d-a266-e4623f91e162',)
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,050::hsm::2397::Storage.HSM::(connectStorageServer) knownSDs: 
>> {6bee0e2d-961c-453d-a266-e4623f91e162: storage.nfsSD.findDomain, 
>> 5e8c1e89-f2b8-492c-adb8-e9a9e15a79ee: storage.nfsSD.findDomain}
>> vdsm.log.11:Thread-23::INFO::2014-04-30 
>> 15:50:00,050::logUtils::47::dispatcher::(wrapper) Run and protect: 
>> connectStorageServer, Return response: {'statuslist': [{'status': 0, 'id': 
>> '3021c4ab-5cb8-455b-be5f-2c79b0e3b23b'}]}
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,050::task::1185::TaskManager.Task::(prepare) 
>> Task=`217a7d59-fe83-4be5-b7e5-ce19c17a8d82`::finished: {'statuslist': 
>> [{'status': 0, 'id': '3021c4ab-5cb8-455b-be5f-2c79b0e3b23b'}]}
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,050::task::595::TaskManager.Task::(_updateState) 
>> Task=`217a7d59-fe83-4be5-b7e5-ce19c17a8d82`::moving from state preparing -> 
>> state finished
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,050::resourceManager::940::ResourceManager.Owner::(releaseAll) 
>> Owner.releaseAll requests {} resources {}
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,051::resourceManager::977::ResourceManager.Owner::(cancelAll) 
>> Owner.cancelAll requests {}
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,051::task::990::TaskManager.Task::(_decref) 
>> Task=`217a7d59-fe83-4be5-b7e5-ce19c17a8d82`::ref 0 aborting False
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,098::BindingXMLRPC::251::vds::(wrapper) client [192.168.1.44] 
>> flowID [2e8f350]
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,098::task::595::TaskManager.Task::(_updateState) 
>> Task=`dc6f1b1a-1162-4a3d-865d-d9ad9c3603f8`::moving from state init -> state 
>> preparing
>> vdsm.log.11:Thread-23::INFO::2014-04-30 
>> 15:50:00,099::logUtils::44::dispatcher::(wrapper) Run and protect: 
>> connectStorageServer(domType=1, 
>> spUUID='----', conList=[{'connection': 
>> '192.168.1.44:/raid/ovirt/iso', 'iqn': '', 'portal': '', 'user': '', 
>> 'password': '**', 'id': '87de82d7-bc85-41ab-9ca7-3b39a75be919', 'port': 
>> ''}], options=None)
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,104::hsm::2317::Storage.HSM::(__prefetchDomains) nfs local path: 
>> /rhev/data-center/mnt/192.168.1.44:_raid_ovirt_iso
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,105::hsm::2341::Storage.HSM::(__prefetchDomains) Found SD uuids: 
>> ('5e8c1e89-f2b8-492c-adb8-e9a9e15a79ee',)
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,105::hsm::2397::Storage.HSM::(connectStorageServer) knownSDs: 
>> {6bee0e2d-961c-453d-a266-e4623f91e162: storage.nfsSD.findDomain, 
>> 5e8c1e89-f2b8-492c-adb8-e9a9e15a79ee: storage.nfsSD.findDomain}
>> vdsm.log.11:Thread-23::INFO::2014-04-30 
>> 15:50:00,105::logUtils::47::dispatcher::(wrapper) Run and protect: 
>> connectStorageServer, Return response: {'statuslist': [{'status': 0, 'id': 
>> '87de82d7-bc85-41ab-9ca7-3b39a75be919'}]}
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,106::task::1185::TaskManager.Task::(prepare) 
>> Task=`dc6f1b1a-1162-4a3d-865d-d9ad9c3603f8`::finished: {'statuslist': 
>> [{'status': 0, 'id': '87de82d7-bc85-41ab-9ca7-3b39a75be919'}]}
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,106::task::595::TaskManager.Task::(_updateState) 
>> Task=`dc6f1b1a-1162-4a3d-865d-d9ad9c3603f8`::moving from state preparing -> 
>> state finished
>> vdsm.log.11:Thread-23::DEBUG::2014-04-30 
>> 15:50:00,106::resourceManager::940::ResourceManager.Owner::(releaseAll) 
>> Owner.re

[ovirt-users] user portal permissions

[Jeff Clay]

For some reason, when logged in as a user with a modifed copy role of
UserRole (only has login permssion and VM -> Basic Operations -> Remote Log
In permission) the user can see all of the VM's and has the ability to open
a console, start, shutdown or suspend any of the VM's. I have verified that
all of the VM's only show the SuperUser role in their permissions. I went
through all of the roles and verified that the user is only a member of the
Copy_of_UserRole. The only thing I can think of is that the user is
inheriting permissions from something, but I can't find what it is or
where. Any suggestions?

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

Re: [ovirt-users] inconsistency in json api vs xml/other apis

[Juan Hernandez]

On 05/02/2014 02:44 PM, Sven Kieske wrote:
> Hi,
> 
> there's an inconsistent use of plural
> vs singular form regarding the "vm" collection
> in the apis.
> 
> in json you got a collection named
> "vm" which contains a list of vms.
> in xml and via gui you got a collection
> "vms" which contains a list of vms.
> 
> I just stumbled upon it, as I used
> json api already in 3.3.3.
> and didn't had time to test 3.4 until
> now.
> 

I believe that this inconsistency doesn't exist in 3.4. The result of
listing VMs is the following with JSON:

{
  "vm" : [
{
  "name": "myvm",
  ...
},
{
  "name": "yourvm",
  ...
},
...
  ]
}

The name of the array is "vm", in singular.

With XML the result is the following:


  
myvm
...
  
  
yourvm
...
  
  ...


There are two notable differences in these representations:

1. XML requires a "root" tag, in this case "vms", in plural. This isn't
needed in JSON, and thus it isn't used. In general, all the root tags
for collections will be in plural when using XML and won't be present in
JSON.

2. In XML arrays are represented as a set of tags named in singular,
"vm" in this case, because XML doesn't have the array concept. In JSON
there is only one "vm" element because JSON does have the concept of
array, so the name of the array has to be given only once. The name of
these XML tags and the name of the JSON array will anyhow be the same,
in singular. There may be exceptions where the name is in plural, but
you can consider them bugs, and they will affect both XML and JSON, so
in those cases we will be consistently buggy.

> the upgrade itself went very well, but
> know I have to deal with this api change
> and the other entity renamings done
> in json api.
> 
> what would make this less painful
> would be an consistent way of getting
> the ovirt-version via api, so I could
> easily split my codepath by first
> querying the api version.
> 
> unfortunately also this one got changed
> in json so I'll need to call for every
> version that might be there.
> 

The way to find the version will be stable now that JSON is supported,
you can count on that. So in the future you should be able to get the
version number in a consistent way. What I mean is that we guarantee
that the version info will always appears as follows:

GET /ovirt-engine/api
{
  ...
  "product_info" : {
"vendor" : "ovirt.org",
"version" : {
  "major" : "3",
  "minor" : "4",
  "build" : "0",
  "revision" : "0"
},
"full_version" : "3.4.1-0.0.master.20140430080728.fc20",
"name" : "oVirt Engine"
  },
  ...
}

If you ever see something changing in a backwards incompatible way
there, it will be a bug.

> I understand that part of this problem
> comes from using json when it was not
> "official supported", but at least
> this inconsistence use in different
> apis makes not really much sense to me.
> 
> should I file a BZ for this?
> 

-- 
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Problem to spice connect without portal

[Juan Hernandez]

On 05/02/2014 10:15 AM, Jean-Pierre WEISS wrote:
> Hi,
> 
> I've tried to follow the procedure "How to Connect to SPICE Console
> Without Portal"
> (http://www.ovirt.org/How_to_Connect_to_SPICE_Console_Without_Portal) on
> a Fedora 20 client.
> 
> I can get into the ovirt-shell :
> 
> - ovirt-shell -c -A ./vmvdiserv2.pem -l
> "https://vmvdiserv2.domain.local/ovirt-engine/api"; -u admin@internal
> 
> But when I tried to launch the console (console w7-test-2), I got this
> message :
> 
> - Spice viewer was not found, please install spice first
> 
> So I think I miss something but what ? I've installed virt-viewer and
> spice-xpi (the console works well via portal)
> 

The problem is that the console support in the ovirt-shell is based on
the "spicec" command. This command existed in previous versions of
Fedora, but has been replaced by "virt-viewer", and we don't have
support for that yet.

There are two things that you can do to make this work:

1. Change the type of the display of the VM to VNC. The user experience
won't be as good as with Spice, but you will be able to use it with
ovirt-shell.

2. Use a custom Python script to launch virt-viewer. You can find an
example of that attached to the following mail message:

http://lists.ovirt.org/pipermail/users/2014-February/021638.html
http://lists.ovirt.org/pipermail/users/attachments/20140220/91796ca0/attachment.py

> Here are the installed packages on my client :
> 
> spice-glib.i6860.23-2.fc20
> @updates
> spice-gtk3.i6860.23-2.fc20
> @updates
> spice-protocol.noarch  0.12.6-2.fc20  
> @fedora
> spice-server.i686  0.12.4-3.fc20  
> @anaconda
> spice-vdagent.i686 0.15.0-1.fc20  
> @updates
> spice-xpi.i686 2.8.90-1.fc20  
> @fedora
> 
> ovirt-engine-cli.noarch3.4.0.5-1.fc20 
> @updates
> ovirt-engine-sdk-python.noarch 3.4.0.7-1.fc20 
> @updates
> virt-viewer.i686   0.6.0-1.fc20   
> @updates
> 
> Thanks,
> 
>  
> 
> Jean-Pierre WEISS
> 

-- 
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 3.4 could not install Windows server 08 R2 with virtio / virtio SCSI

[Paul.LKW]

Hi All:
I just even tryied to use IDE only and the Windows 08 server R2 still 
could not find any harddisk, what does this bug exists in version 3.4? 
does it suitable for production? which one should I report this bug for ?


Paul.LKW


於 4/5/2014 21:17, Paul.LKW 提到:


Hi Joop
It should be show me the harddisk drive after the driver installed and 
then change back to the installation media disc, but the case is it 
could not load the driver correctly I could not see the harddisk drive 
so even I change back the media disc should be no meaning?


Paul.LKW

於 2014/5/4 下午8:48，"Joop" > 寫道：


Paul.LKW wrote:


Hi All:
I am new to oVirt and just installed oVirt for a try.
Any one could install Win Server 08 R2 with virtio or virtio
SCSI from oVirt 3.4?
I am already changed the driver during the installation with
virtio-win-0.1-74.iso, however I try what ever driver
directory for AMD64 it show the device but when I click to
select and then click OK, it always say "No new device could
be found. Make sure the driver files are correct and located
on the driver installation media".
Does any other see this issue, and know how to solve?
Many thanks

Did you change back to your W2K8 iso after loading the driver?
The installer displays a very misleading message if you don't have
your iso back in the cdrom after installing the drivers.

Joop

___
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] Ceph

[Nicolas Ecarnot]

Le 01/05/2014 20:58, Dave Neary a écrit :

Hi all,

For my education, how would you like to use Ceph with oVirt?


Hi Dave,

As someone wrote on the mailing list, we would be happy with a 
filesystem that would not be dedicated to oVirt only, and would not rely 
on oVirt only, but which could be easily used by oVirt (and managed, and 
monitored by a web tool).
Our main concern is not performance neither huge petabytes, but 
redundancy, geo replication and _reliability_.


We won't have more than 200 VM and not more than 32 hosts, and not more 
than 100 To of storage, but we would like to know how this could be 
replicated amongst, say, 6 sites.


We still have a long way to go.



Thanks,
Dave.


On 05/01/2014 06:17 PM, Nicolas Ecarnot wrote:

Le 01/05/2014 16:27, Jeremiah Jahn a écrit :

Personally, I'd love to use it. I haven't used it because it hasn't
been part of RedHat's enterprise platform, and didn't want to have to
track updates separately, so we went with gluster for all of our
storage needs as opposed to a mix of both gluster and ceph where
appropriate.


For the exact same reasons, we did not yet choose which way to go
between Ceph and Gluster, wondering which one will lead the market in
the next future.
But we are strongly willing to use their features, whatever the future
mixed enhanced product or name.





On Thu, May 1, 2014 at 2:07 AM, Jiri Moskovcak 
wrote:

Hello oVirt users!

When I read [1] I got curious how much demand for supporting Ceph we can
expect in the near future. So if use it or plan to use it please let us
know.

Have a nice day,
Jirka

[1]
http://www.redhat.com/about/news/press-archive/2014/4/red-hat-to-acquire-inktank-provider-of-ceph

___
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









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

Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages

[Arthur Berezin]

Gilad, this is integral part of HA, For HA to work properly we rely on PM 
mechanism, this feature makes sure PM is available, ie. running existing "Check 
PM" periodically. 

We need to look at integrating a monitoring tool and it's benefits separately. 

Arthur 

- Original Message -

> From: "Gilad Chaplik" 
> To: "Yair Zaslavsky" 
> Cc: "Arthur Berezin" , "users" 
> Sent: Monday, May 5, 2014 12:06:28 PM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> feature pages

> - Original Message -
> > From: "Yair Zaslavsky" 
> > To: "Gilad Chaplik" 
> > Cc: "Arthur Berezin" , "users" 
> > Sent: Monday, May 5, 2014 12:00:10 PM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> >
> >
> >
> > - Original Message -
> > > From: "Gilad Chaplik" 
> > > To: "Arthur Berezin" 
> > > Cc: "users" , "Yair Zaslavsky" 
> > > Sent: Monday, May 5, 2014 11:52:25 AM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature pages
> > >
> > > - Original Message -
> > > > From: "Arthur Berezin" 
> > > > To: "Gilad Chaplik" 
> > > > Cc: "users" , "Yair Zaslavsky" 
> > > > Sent: Monday, May 5, 2014 11:30:24 AM
> > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > -
> > > > feature pages
> > > >
> > > > - Original Message -
> > > >
> > > > > From: "Yair Zaslavsky" 
> > > > > To: "Gilad Chaplik" 
> > > > > Cc: "Arthur Berezin" , "users" 
> > > > > Sent: Monday, May 5, 2014 11:10:10 AM
> > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > Check"
> > > > > -
> > > > > feature pages
> > > >
> > > > > - Original Message -
> > > > > > From: "Gilad Chaplik" 
> > > > > > To: "Yair Zaslavsky" 
> > > > > > Cc: "Arthur Berezin" , "users"
> > > > > > 
> > > > > > Sent: Monday, May 5, 2014 10:57:01 AM
> > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > Check"
> > > > > > -
> > > > > > feature pages
> > > > > >
> > > > > > - Original Message -
> > > > > > > From: "Yair Zaslavsky" 
> > > > > > > To: "Arthur Berezin" 
> > > > > > > Cc: "Gilad Chaplik" , "users"
> > > > > > > 
> > > > > > > Sent: Monday, May 5, 2014 6:39:02 AM
> > > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > > Check"
> > > > > > > -
> > > > > > > feature pages
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > - Original Message -
> > > > > > > > From: "Arthur Berezin" 
> > > > > > > > To: "Gilad Chaplik" 
> > > > > > > > Cc: "users" 
> > > > > > > > Sent: Sunday, May 4, 2014 5:35:59 PM
> > > > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > > > Check"
> > > > > > > > -
> > > > > > > > feature pages
> > > > > > > >
> > > > > > > > In this case engine periodically checks health of hosts' power
> > > > > > > > management
> > > > > > > > as
> > > > > > > > HA relies on it.
> > > > > > > >
> > > > > > > > Arthur
> > > > > > > >
> > > > > > > > - Original Message -
> > > > > > > >
> > > > > > > > > From: "Gilad Chaplik" 
> > > > > > > > > To: "Eli Mesika" 
> > > > > > > > > Cc: "users" , "Arthur Berezin"
> > > > > > > > > 
> > > > > > > > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > > > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management
> > > > > > > > > Health
> > > > > > > > > Check"
> > > > > > > > > -
> > > > > > > > > feature pages
> > > > > > > >
> > > > > > > > > Hi Eli,
> > > > > > > >
> > > > > > > > > Here is my comment :)
> > > > > > > > > Why engine needs to send the status health check, isn't there
> > > > > > > > > any
> > > > > > > > > 3rd
> > > > > > > > > parties
> > > > > > > > > that does it, that we can integrate with?
> > > > > > > > > If found, it probably has /less (known) bugs/more features/
> > > > > > > > > and
> > > > > > > > > it's
> > > > > > > > > already
> > > > > > > > > written, tested, documented, allows further integration and
> > > > > > > > > probably
> > > > > > > > > deals
> > > > > > > > > with scale.
> > > > > > > >
> > > > > > > > > btw, fixed some typos in your pages :-)
> > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Gilad.
> > > > > > >
> > > > > > > Hi, what 3rd party for example do you refer to?
> > > > > > > The PM code already exists at engine,
> > > > > > > And you're also using quartz for scheduling.
> > > > > > >
> > > > > >
> > > > > > Yair,
> > > > > >
> > > > > > You're are raising some good points, but imo the entire host
> > > > > > monitoring
> > > > > > (inc
> > > > > > getVdsStats, etc.) should be externalized.
> > > > > > There are 2 major issues that we still don't cover:
> > > > > > - No HA for monitoring, who checks the hosts when the engine is
> > > > > > down.
> > > > > > - No scale - the engine is a bottle-neck in network and compute.
> > > > > > Although the above is a huge arch change, we need to start
> > > > > > somewhere,
> > > > > > this
>

Re: [ovirt-users] [QE] oVirt 3.4.1 GA status

[Alon Bar-Lev]

- Original Message -
> From: "Sven Kieske" 
> To: "Alon Bar-Lev" , "Sandro Bonazzola" 
> 
> Cc: de...@ovirt.org, Users@ovirt.org, "Martin Betak" , 
> "Jiri Moskovcak" ,
> "Doron Fediuck" , "Juan Hernandez" 
> , "Douglas Schilling Landgraf"
> , "Barak Azulay" 
> Sent: Monday, May 5, 2014 1:00:20 PM
> Subject: Re: [ovirt-users] [QE] oVirt 3.4.1 GA status
> 
> Can I provide any additional
> information to debug this?

No need, if sandro can reproduce this we can close it internally.
Thanks!

> 
> Am 05.05.2014 11:53, schrieb Alon Bar-Lev:
> > There is no ETA as there seems to be no problem within code but within
> > infra as group is being pulled.
> 
> --
> 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] [QE] oVirt 3.4.1 GA status

[Sven Kieske]

Can I provide any additional
information to debug this?

Am 05.05.2014 11:53, schrieb Alon Bar-Lev:
> There is no ETA as there seems to be no problem within code but within infra 
> as group is being pulled.

-- 
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] [QE] oVirt 3.4.1 GA status

[Alon Bar-Lev]

- Original Message -
> From: "Sandro Bonazzola" 
> To: de...@ovirt.org, Users@ovirt.org, "Martin Betak" , 
> "Jiri Moskovcak" ,
> "Doron Fediuck" , "Alon Bar-Lev" , 
> "Juan Hernandez" ,
> "Douglas Schilling Landgraf" , "Sven Kieske" 
> 
> Cc: "Barak Azulay" , "Doron Fediuck" 
> Sent: Monday, May 5, 2014 10:45:16 AM
> Subject: Re: [ovirt-users] [QE] oVirt 3.4.1 GA status
> 
> Il 02/05/2014 10:02, Sandro Bonazzola ha scritto:
> > Il 02/05/2014 09:52, Sandro Bonazzola ha scritto:
> >> Hi,
> >> We're going to start composing oVirt 3.4.1 GA on 2014-05-07 08:00 UTC from
> >> 3.4.1 branches.
> >>
> >> The bug tracker [1] shows no blocking bugs for the release.
> 
> While testing 3.4.1 RC last week a few bugs have been identified as blockers:
> 
> 1089567   integration ASSIGNEDvdsm sources are not available 
> as tarball
> 1093721   integration NEW upgrade from 3.4.0 to 3.4.1 
> doesn't work anymore

There is no ETA as there seems to be no problem within code but within infra as 
group is being pulled.

> 1093755   infra   NEW [BUG] can't boot vm with 
> cloud-init data submitted as
> json via REST api
> 
> Last one, Bug 1093755, looks like a regression from 3.3.5.
> Since it has been re-targeted to 3.4.2 I removed it was initially from the
> list of blockers for 3.4.1.
> However, since without that we're failing release criteria [6]: MUST: No
> regressions from 3.3 Release
> The bug has been re-targeted to 3.4.1 and re-added to blockers.
> 
> Assignee, please provide an ETA on above bugs and fix them as soon as
> possible
> 
> 
> >> Interest has been raised on the following BZ as nice to have:
> >>
> >> sla  - Bug 1049318 - pending memory not cleared when stopping paused VM
> >> virt - Bug 1073453 - [RFE] add Debian 7 to the list of operating systems
> >> when creating a new vm
> >>
> >> There are still 138 bugs [2] targeted to 3.4.1.
> >> Excluding node and documentation bugs we still have 106 bugs [3] targeted
> >> to 3.4.1.
> >> Please review them as soon as possible and re-target them to a future
> >> release.
> >> Bugs still targeted to 3.4.1 will be re-targeted to 3.4.2 after 3.4.1 GA
> >> release.
> > 
> > Better:
> > Critical bugs will be re-targeted to 3.4.2 after 3.4.1 GA release.
> > All remaining bugs will be re-targeted to 3.5.0.
> > 
> > 
> >>
> >> Maintainers / Assignee:
> >> - Please remember to rebuild your packages before 2014-05-07 08:00 UTC
> >> - If you find a blocker bug please remember to add it to the tracker [1]
> >> - Please update the target to any next release for bugs that won't be in
> >> 3.4.1:
> >>   it will ease gathering the blocking bugs for next releases.
> >> - Please fill release notes, the page has been created here [4]
> >>
> >> All users:
> >> - If you've tested the RC release or if you're testing nightly 3.4
> >> snapshot builds, please add yourself to the test page [5]
> >>
> >>
> >> [1] https://bugzilla.redhat.com/1080483
> >> [2] http://red.ht/1gCFOtH
> >> [3] http://red.ht/1laBSUj
> >> [4] http://www.ovirt.org/OVirt_3.4.1_release_notes
> >> [5] http://www.ovirt.org/Testing/oVirt_3.4.1_testing
> 
> [6] http://www.ovirt.org/OVirt_3.4_release-management#MUST
> 
> 
> >>
> >> 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] How to have this information?

[Sven Kieske]

Hi,

via REST:

https://your-engine.example.com/api/vms/{VM-ID}/statistics

should suite your needs.

HTH

PS: Some digging around should have yielded this result
pretty fast. I believe this was mentioned several times
on the ML.

Check the archives.

Am 05.05.2014 09:45, schrieb Ovirt User:
>   Hello,
> 
> it is possible have :
> 
> - CPU
> - MEMORY
> - NETWORK
> 
> usage of VM's from the manager ? trought API or.. snmpd, or.. .other stuff ?
> 
> I need to develop a web page to show this information to my customers.
> 
> thanks
> Lukas


-- 
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] [ovirt-devel] possible 3.4.1 blocker

[Sven Kieske]

As always, thanks for the fast response.
And thanks for re-adding as a blocker and the clarification.

I still hope the bug is on my side, so 3.4.1 has not to be
delayed much longer.

It would be cool if some REST gurus could review my json
code, and tell me if it is correct, or not.

-- 
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] oVirt 3.5 : "Power Management Health Check" - feature pages

[Gilad Chaplik]

- Original Message -
> From: "Yair Zaslavsky" 
> To: "Gilad Chaplik" 
> Cc: "Arthur Berezin" , "users" 
> Sent: Monday, May 5, 2014 12:00:10 PM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - 
> feature  pages
> 
> 
> 
> - Original Message -
> > From: "Gilad Chaplik" 
> > To: "Arthur Berezin" 
> > Cc: "users" , "Yair Zaslavsky" 
> > Sent: Monday, May 5, 2014 11:52:25 AM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> > 
> > - Original Message -
> > > From: "Arthur Berezin" 
> > > To: "Gilad Chaplik" 
> > > Cc: "users" , "Yair Zaslavsky" 
> > > Sent: Monday, May 5, 2014 11:30:24 AM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature   pages
> > > 
> > > - Original Message -
> > > 
> > > > From: "Yair Zaslavsky" 
> > > > To: "Gilad Chaplik" 
> > > > Cc: "Arthur Berezin" , "users" 
> > > > Sent: Monday, May 5, 2014 11:10:10 AM
> > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > -
> > > > feature pages
> > > 
> > > > - Original Message -
> > > > > From: "Gilad Chaplik" 
> > > > > To: "Yair Zaslavsky" 
> > > > > Cc: "Arthur Berezin" , "users" 
> > > > > Sent: Monday, May 5, 2014 10:57:01 AM
> > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > Check"
> > > > > -
> > > > > feature pages
> > > > >
> > > > > - Original Message -
> > > > > > From: "Yair Zaslavsky" 
> > > > > > To: "Arthur Berezin" 
> > > > > > Cc: "Gilad Chaplik" , "users"
> > > > > > 
> > > > > > Sent: Monday, May 5, 2014 6:39:02 AM
> > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > Check"
> > > > > > -
> > > > > > feature pages
> > > > > >
> > > > > >
> > > > > >
> > > > > > - Original Message -
> > > > > > > From: "Arthur Berezin" 
> > > > > > > To: "Gilad Chaplik" 
> > > > > > > Cc: "users" 
> > > > > > > Sent: Sunday, May 4, 2014 5:35:59 PM
> > > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > > Check"
> > > > > > > -
> > > > > > > feature pages
> > > > > > >
> > > > > > > In this case engine periodically checks health of hosts' power
> > > > > > > management
> > > > > > > as
> > > > > > > HA relies on it.
> > > > > > >
> > > > > > > Arthur
> > > > > > >
> > > > > > > - Original Message -
> > > > > > >
> > > > > > > > From: "Gilad Chaplik" 
> > > > > > > > To: "Eli Mesika" 
> > > > > > > > Cc: "users" , "Arthur Berezin"
> > > > > > > > 
> > > > > > > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > > > Check"
> > > > > > > > -
> > > > > > > > feature pages
> > > > > > >
> > > > > > > > Hi Eli,
> > > > > > >
> > > > > > > > Here is my comment :)
> > > > > > > > Why engine needs to send the status health check, isn't there
> > > > > > > > any
> > > > > > > > 3rd
> > > > > > > > parties
> > > > > > > > that does it, that we can integrate with?
> > > > > > > > If found, it probably has /less (known) bugs/more features/ and
> > > > > > > > it's
> > > > > > > > already
> > > > > > > > written, tested, documented, allows further integration and
> > > > > > > > probably
> > > > > > > > deals
> > > > > > > > with scale.
> > > > > > >
> > > > > > > > btw, fixed some typos in your pages :-)
> > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Gilad.
> > > > > >
> > > > > > Hi, what 3rd party for example do you refer to?
> > > > > > The PM code already exists at engine,
> > > > > > And you're also using quartz for scheduling.
> > > > > >
> > > > >
> > > > > Yair,
> > > > >
> > > > > You're are raising some good points, but imo the entire host
> > > > > monitoring
> > > > > (inc
> > > > > getVdsStats, etc.) should be externalized.
> > > > > There are 2 major issues that we still don't cover:
> > > > > - No HA for monitoring, who checks the hosts when the engine is down.
> > > > > - No scale - the engine is a bottle-neck in network and compute.
> > > > > Although the above is a huge arch change, we need to start somewhere,
> > > > > this
> > > > > feature sounds like a candidate to introduce it.
> > > > >
> > > > > About the examples:
> > > > > http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/
> > > > > The main goal of the feature if my suggestion is taken, is to select
> > > > > to
> > > > > most
> > > > > appropriate one.
> > > > >
> > > > > Thanks,
> > > > > Gilad.
> > > 
> > > > Well, Nagios is being considered to be used or used by Gluster guys.
> > > > However, it will still require (AFAIK) to code some nagios plugin to
> > > > perfrom
> > > > the health check.
> > > > In addition, you will have to report somehow the state change to
> > > > engine.
> > > > IMHO, this a bit of an overkill (look also at the time that the check
> > > > is
> > > > run
> > > > - once in an hour, so it can't be compared to getVmStats).

Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages

[Yair Zaslavsky]

- Original Message -
> From: "Gilad Chaplik" 
> To: "Arthur Berezin" 
> Cc: "users" , "Yair Zaslavsky" 
> Sent: Monday, May 5, 2014 11:52:25 AM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - 
> feature  pages
> 
> - Original Message -
> > From: "Arthur Berezin" 
> > To: "Gilad Chaplik" 
> > Cc: "users" , "Yair Zaslavsky" 
> > Sent: Monday, May 5, 2014 11:30:24 AM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> > 
> > - Original Message -
> > 
> > > From: "Yair Zaslavsky" 
> > > To: "Gilad Chaplik" 
> > > Cc: "Arthur Berezin" , "users" 
> > > Sent: Monday, May 5, 2014 11:10:10 AM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature pages
> > 
> > > - Original Message -
> > > > From: "Gilad Chaplik" 
> > > > To: "Yair Zaslavsky" 
> > > > Cc: "Arthur Berezin" , "users" 
> > > > Sent: Monday, May 5, 2014 10:57:01 AM
> > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > -
> > > > feature pages
> > > >
> > > > - Original Message -
> > > > > From: "Yair Zaslavsky" 
> > > > > To: "Arthur Berezin" 
> > > > > Cc: "Gilad Chaplik" , "users" 
> > > > > Sent: Monday, May 5, 2014 6:39:02 AM
> > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > Check"
> > > > > -
> > > > > feature pages
> > > > >
> > > > >
> > > > >
> > > > > - Original Message -
> > > > > > From: "Arthur Berezin" 
> > > > > > To: "Gilad Chaplik" 
> > > > > > Cc: "users" 
> > > > > > Sent: Sunday, May 4, 2014 5:35:59 PM
> > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > Check"
> > > > > > -
> > > > > > feature pages
> > > > > >
> > > > > > In this case engine periodically checks health of hosts' power
> > > > > > management
> > > > > > as
> > > > > > HA relies on it.
> > > > > >
> > > > > > Arthur
> > > > > >
> > > > > > - Original Message -
> > > > > >
> > > > > > > From: "Gilad Chaplik" 
> > > > > > > To: "Eli Mesika" 
> > > > > > > Cc: "users" , "Arthur Berezin"
> > > > > > > 
> > > > > > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > > Check"
> > > > > > > -
> > > > > > > feature pages
> > > > > >
> > > > > > > Hi Eli,
> > > > > >
> > > > > > > Here is my comment :)
> > > > > > > Why engine needs to send the status health check, isn't there any
> > > > > > > 3rd
> > > > > > > parties
> > > > > > > that does it, that we can integrate with?
> > > > > > > If found, it probably has /less (known) bugs/more features/ and
> > > > > > > it's
> > > > > > > already
> > > > > > > written, tested, documented, allows further integration and
> > > > > > > probably
> > > > > > > deals
> > > > > > > with scale.
> > > > > >
> > > > > > > btw, fixed some typos in your pages :-)
> > > > > >
> > > > > > > Thanks,
> > > > > > > Gilad.
> > > > >
> > > > > Hi, what 3rd party for example do you refer to?
> > > > > The PM code already exists at engine,
> > > > > And you're also using quartz for scheduling.
> > > > >
> > > >
> > > > Yair,
> > > >
> > > > You're are raising some good points, but imo the entire host monitoring
> > > > (inc
> > > > getVdsStats, etc.) should be externalized.
> > > > There are 2 major issues that we still don't cover:
> > > > - No HA for monitoring, who checks the hosts when the engine is down.
> > > > - No scale - the engine is a bottle-neck in network and compute.
> > > > Although the above is a huge arch change, we need to start somewhere,
> > > > this
> > > > feature sounds like a candidate to introduce it.
> > > >
> > > > About the examples:
> > > > http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/
> > > > The main goal of the feature if my suggestion is taken, is to select to
> > > > most
> > > > appropriate one.
> > > >
> > > > Thanks,
> > > > Gilad.
> > 
> > > Well, Nagios is being considered to be used or used by Gluster guys.
> > > However, it will still require (AFAIK) to code some nagios plugin to
> > > perfrom
> > > the health check.
> > > In addition, you will have to report somehow the state change to engine.
> > > IMHO, this a bit of an overkill (look also at the time that the check is
> > > run
> > > - once in an hour, so it can't be compared to getVmStats).
> > +1
> > These monitoring tools bring a lot of value, and there are some initial
> > integrations that we might want to look into[1][2].
> > But it's an overkill for this RFE - run "PM Check" periodically, in
> > addition
> > to initial PM check at host setup stage.
> > 
> > [1] https://github.com/monitoring-ui-plugin/development
> > [2]
> > http://exchange.nagios.org/directory/Plugins/Operating-Systems/*-Virtual-Environments/Others/check_rhev3/details
> 
> 
> -1 on overkill.
> As I mentioned, proper monitoring is a huge feature; it should be gradually
> introduced, IMO this is a goo

Re: [ovirt-users] How to have this information?

[Ovirt User]

thanks, but i mean how to obtain this information from Ovirt manager layer .. i 
don't want install snmp in the single VM.. because customer can disable it …


Il giorno 05/mag/2014, alle ore 10:38, Meital Bourvine  ha 
scritto:

> Hi,
> 
> You can get the information via snmp - here you can find some useful OIDs [1].
> 
> If I were you, I would have considered monitoring the VMs with zenoss [2] 
> (which uses snmp and already has all relevant OIDs). 
> It has a python api, so for creating the web page - I would have probably use 
> django [3] with zenoss' python api.
> 
> With that being said, there might be a way that I'm not aware about to get 
> this information from ovirt.
> 
> 
> [1] 
> http://kaivanov.blogspot.co.il/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html
> [2] http://www.zenoss.com/
> [3] https://www.djangoproject.com/‎
> 
> - Original Message -
>> From: "Ovirt User" 
>> To: users@ovirt.org
>> Sent: Monday, May 5, 2014 10:45:14 AM
>> Subject: [ovirt-users] How to have this information?
>> 
>> Hello,
>> 
>> it is possible have :
>> 
>> - CPU
>> - MEMORY
>> - NETWORK
>> 
>> usage of VM's from the manager ? trought API or.. snmpd, or.. .other stuff ?
>> 
>> I need to develop a web page to show this information to my customers.
>> 
>> thanks
>> Lukas
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>> 

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

Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages

[Gilad Chaplik]

- Original Message -
> From: "Arthur Berezin" 
> To: "Gilad Chaplik" 
> Cc: "users" , "Yair Zaslavsky" 
> Sent: Monday, May 5, 2014 11:30:24 AM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - 
> feature  pages
> 
> - Original Message -
> 
> > From: "Yair Zaslavsky" 
> > To: "Gilad Chaplik" 
> > Cc: "Arthur Berezin" , "users" 
> > Sent: Monday, May 5, 2014 11:10:10 AM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> 
> > - Original Message -
> > > From: "Gilad Chaplik" 
> > > To: "Yair Zaslavsky" 
> > > Cc: "Arthur Berezin" , "users" 
> > > Sent: Monday, May 5, 2014 10:57:01 AM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature pages
> > >
> > > - Original Message -
> > > > From: "Yair Zaslavsky" 
> > > > To: "Arthur Berezin" 
> > > > Cc: "Gilad Chaplik" , "users" 
> > > > Sent: Monday, May 5, 2014 6:39:02 AM
> > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > -
> > > > feature pages
> > > >
> > > >
> > > >
> > > > - Original Message -
> > > > > From: "Arthur Berezin" 
> > > > > To: "Gilad Chaplik" 
> > > > > Cc: "users" 
> > > > > Sent: Sunday, May 4, 2014 5:35:59 PM
> > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > Check"
> > > > > -
> > > > > feature pages
> > > > >
> > > > > In this case engine periodically checks health of hosts' power
> > > > > management
> > > > > as
> > > > > HA relies on it.
> > > > >
> > > > > Arthur
> > > > >
> > > > > - Original Message -
> > > > >
> > > > > > From: "Gilad Chaplik" 
> > > > > > To: "Eli Mesika" 
> > > > > > Cc: "users" , "Arthur Berezin"
> > > > > > 
> > > > > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > Check"
> > > > > > -
> > > > > > feature pages
> > > > >
> > > > > > Hi Eli,
> > > > >
> > > > > > Here is my comment :)
> > > > > > Why engine needs to send the status health check, isn't there any
> > > > > > 3rd
> > > > > > parties
> > > > > > that does it, that we can integrate with?
> > > > > > If found, it probably has /less (known) bugs/more features/ and
> > > > > > it's
> > > > > > already
> > > > > > written, tested, documented, allows further integration and
> > > > > > probably
> > > > > > deals
> > > > > > with scale.
> > > > >
> > > > > > btw, fixed some typos in your pages :-)
> > > > >
> > > > > > Thanks,
> > > > > > Gilad.
> > > >
> > > > Hi, what 3rd party for example do you refer to?
> > > > The PM code already exists at engine,
> > > > And you're also using quartz for scheduling.
> > > >
> > >
> > > Yair,
> > >
> > > You're are raising some good points, but imo the entire host monitoring
> > > (inc
> > > getVdsStats, etc.) should be externalized.
> > > There are 2 major issues that we still don't cover:
> > > - No HA for monitoring, who checks the hosts when the engine is down.
> > > - No scale - the engine is a bottle-neck in network and compute.
> > > Although the above is a huge arch change, we need to start somewhere,
> > > this
> > > feature sounds like a candidate to introduce it.
> > >
> > > About the examples:
> > > http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/
> > > The main goal of the feature if my suggestion is taken, is to select to
> > > most
> > > appropriate one.
> > >
> > > Thanks,
> > > Gilad.
> 
> > Well, Nagios is being considered to be used or used by Gluster guys.
> > However, it will still require (AFAIK) to code some nagios plugin to
> > perfrom
> > the health check.
> > In addition, you will have to report somehow the state change to engine.
> > IMHO, this a bit of an overkill (look also at the time that the check is
> > run
> > - once in an hour, so it can't be compared to getVmStats).
> +1
> These monitoring tools bring a lot of value, and there are some initial
> integrations that we might want to look into[1][2].
> But it's an overkill for this RFE - run "PM Check" periodically, in addition
> to initial PM check at host setup stage.
> 
> [1] https://github.com/monitoring-ui-plugin/development
> [2]
> http://exchange.nagios.org/directory/Plugins/Operating-Systems/*-Virtual-Environments/Others/check_rhev3/details


-1 on overkill.
As I mentioned, proper monitoring is a huge feature; it should be gradually 
introduced, IMO this is a good starting point.
We can look at it as an overkill _or_ as a jumpborad, that will reduce learning 
curve and future integrations issues.

Gilad.

> 
> > >
> > > >
> > > > >
> > > > > > - Original Message -
> > > > > > > From: "Eli Mesika" 
> > > > > > > To: "users" 
> > > > > > > Cc: "Arthur Berezin" 
> > > > > > > Sent: Sunday, May 4, 2014 12:18:47 PM
> > > > > > > Subject: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > > > Check"
> > > > > > > -
> > > > > > > feature pages
> > > > > > >
> > > > > > > Hi
> > > 

Re: [ovirt-users] How to have this information?

[Meital Bourvine]

Hi,

You can get the information via snmp - here you can find some useful OIDs [1].

If I were you, I would have considered monitoring the VMs with zenoss [2] 
(which uses snmp and already has all relevant OIDs). 
It has a python api, so for creating the web page - I would have probably use 
django [3] with zenoss' python api.

With that being said, there might be a way that I'm not aware about to get this 
information from ovirt.


[1] 
http://kaivanov.blogspot.co.il/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html
[2] http://www.zenoss.com/
[3] https://www.djangoproject.com/‎

- Original Message -
> From: "Ovirt User" 
> To: users@ovirt.org
> Sent: Monday, May 5, 2014 10:45:14 AM
> Subject: [ovirt-users] How to have this information?
> 
> Hello,
> 
> it is possible have :
> 
> - CPU
> - MEMORY
> - NETWORK
> 
> usage of VM's from the manager ? trought API or.. snmpd, or.. .other stuff ?
> 
> I need to develop a web page to show this information to my customers.
> 
> thanks
> Lukas
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages

[Arthur Berezin]

- Original Message -

> From: "Yair Zaslavsky" 
> To: "Gilad Chaplik" 
> Cc: "Arthur Berezin" , "users" 
> Sent: Monday, May 5, 2014 11:10:10 AM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> feature pages

> - Original Message -
> > From: "Gilad Chaplik" 
> > To: "Yair Zaslavsky" 
> > Cc: "Arthur Berezin" , "users" 
> > Sent: Monday, May 5, 2014 10:57:01 AM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> >
> > - Original Message -
> > > From: "Yair Zaslavsky" 
> > > To: "Arthur Berezin" 
> > > Cc: "Gilad Chaplik" , "users" 
> > > Sent: Monday, May 5, 2014 6:39:02 AM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature pages
> > >
> > >
> > >
> > > - Original Message -
> > > > From: "Arthur Berezin" 
> > > > To: "Gilad Chaplik" 
> > > > Cc: "users" 
> > > > Sent: Sunday, May 4, 2014 5:35:59 PM
> > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > -
> > > > feature pages
> > > >
> > > > In this case engine periodically checks health of hosts' power
> > > > management
> > > > as
> > > > HA relies on it.
> > > >
> > > > Arthur
> > > >
> > > > - Original Message -
> > > >
> > > > > From: "Gilad Chaplik" 
> > > > > To: "Eli Mesika" 
> > > > > Cc: "users" , "Arthur Berezin" 
> > > > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health
> > > > > Check"
> > > > > -
> > > > > feature pages
> > > >
> > > > > Hi Eli,
> > > >
> > > > > Here is my comment :)
> > > > > Why engine needs to send the status health check, isn't there any 3rd
> > > > > parties
> > > > > that does it, that we can integrate with?
> > > > > If found, it probably has /less (known) bugs/more features/ and it's
> > > > > already
> > > > > written, tested, documented, allows further integration and probably
> > > > > deals
> > > > > with scale.
> > > >
> > > > > btw, fixed some typos in your pages :-)
> > > >
> > > > > Thanks,
> > > > > Gilad.
> > >
> > > Hi, what 3rd party for example do you refer to?
> > > The PM code already exists at engine,
> > > And you're also using quartz for scheduling.
> > >
> >
> > Yair,
> >
> > You're are raising some good points, but imo the entire host monitoring
> > (inc
> > getVdsStats, etc.) should be externalized.
> > There are 2 major issues that we still don't cover:
> > - No HA for monitoring, who checks the hosts when the engine is down.
> > - No scale - the engine is a bottle-neck in network and compute.
> > Although the above is a huge arch change, we need to start somewhere, this
> > feature sounds like a candidate to introduce it.
> >
> > About the examples:
> > http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/
> > The main goal of the feature if my suggestion is taken, is to select to
> > most
> > appropriate one.
> >
> > Thanks,
> > Gilad.

> Well, Nagios is being considered to be used or used by Gluster guys.
> However, it will still require (AFAIK) to code some nagios plugin to perfrom
> the health check.
> In addition, you will have to report somehow the state change to engine.
> IMHO, this a bit of an overkill (look also at the time that the check is run
> - once in an hour, so it can't be compared to getVmStats).
+1 
These monitoring tools bring a lot of value, and there are some initial 
integrations that we might want to look into[1][2]. 
But it's an overkill for this RFE - run "PM Check" periodically, in addition to 
initial PM check at host setup stage. 

[1] https://github.com/monitoring-ui-plugin/development 
[2] 
http://exchange.nagios.org/directory/Plugins/Operating-Systems/*-Virtual-Environments/Others/check_rhev3/details
 

> >
> > >
> > > >
> > > > > - Original Message -
> > > > > > From: "Eli Mesika" 
> > > > > > To: "users" 
> > > > > > Cc: "Arthur Berezin" 
> > > > > > Sent: Sunday, May 4, 2014 12:18:47 PM
> > > > > > Subject: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > > > -
> > > > > > feature pages
> > > > > >
> > > > > > Hi
> > > > > >
> > > > > > The following wiki pages were added to the "Power Management Health
> > > > > > Check"
> > > > > > feature planned for oVirt 3.5
> > > > > >
> > > > > > http://www.ovirt.org/Features/PMHealthCheck
> > > > > > http://www.ovirt.org/Features/Design/DetailedPMHealthCheck
> > > > > >
> > > > > > Your comments/questions are mostly welcomed.
> > > > > >
> > > > > > Thanks
> > > > > > Eli Mesika
> > > > > > ___
> > > > > > 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

Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages

[Yair Zaslavsky]

- Original Message -
> From: "Gilad Chaplik" 
> To: "Yair Zaslavsky" 
> Cc: "Arthur Berezin" , "users" 
> Sent: Monday, May 5, 2014 10:57:01 AM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - 
> feature  pages
> 
> - Original Message -
> > From: "Yair Zaslavsky" 
> > To: "Arthur Berezin" 
> > Cc: "Gilad Chaplik" , "users" 
> > Sent: Monday, May 5, 2014 6:39:02 AM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> > 
> > 
> > 
> > - Original Message -
> > > From: "Arthur Berezin" 
> > > To: "Gilad Chaplik" 
> > > Cc: "users" 
> > > Sent: Sunday, May 4, 2014 5:35:59 PM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature   pages
> > > 
> > > In this case engine periodically checks health of hosts' power management
> > > as
> > > HA relies on it.
> > > 
> > > Arthur
> > > 
> > > - Original Message -
> > > 
> > > > From: "Gilad Chaplik" 
> > > > To: "Eli Mesika" 
> > > > Cc: "users" , "Arthur Berezin" 
> > > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check"
> > > > -
> > > > feature pages
> > > 
> > > > Hi Eli,
> > > 
> > > > Here is my comment :)
> > > > Why engine needs to send the status health check, isn't there any 3rd
> > > > parties
> > > > that does it, that we can integrate with?
> > > > If found, it probably has /less (known) bugs/more features/ and it's
> > > > already
> > > > written, tested, documented, allows further integration and probably
> > > > deals
> > > > with scale.
> > > 
> > > > btw, fixed some typos in your pages :-)
> > > 
> > > > Thanks,
> > > > Gilad.
> > 
> > Hi, what 3rd party for example do you refer to?
> > The PM code already exists at engine,
> > And you're also using quartz for scheduling.
> > 
> 
> Yair,
> 
> You're are raising some good points, but imo the entire host monitoring (inc
> getVdsStats, etc.) should be externalized.
> There are 2 major issues that we still don't cover:
> - No HA for monitoring, who checks the hosts when the engine is down.
> - No scale - the engine is a bottle-neck in network and compute.
> Although the above is a huge arch change, we need to start somewhere, this
> feature sounds like a candidate to introduce it.
> 
> About the examples:
> http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/
> The main goal of the feature if my suggestion is taken, is to select to most
> appropriate one.
> 
> Thanks,
> Gilad.


Well, Nagios is being considered to be used or used by Gluster guys.
However, it will still require (AFAIK) to code some nagios plugin to perfrom 
the health check.
In addition, you will have to report somehow the state change to engine.
IMHO, this a bit of an overkill (look also at the time that the check is run - 
once in an hour, so it can't be compared to getVmStats).


> 
> > 
> > > 
> > > > - Original Message -
> > > > > From: "Eli Mesika" 
> > > > > To: "users" 
> > > > > Cc: "Arthur Berezin" 
> > > > > Sent: Sunday, May 4, 2014 12:18:47 PM
> > > > > Subject: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > > > feature pages
> > > > >
> > > > > Hi
> > > > >
> > > > > The following wiki pages were added to the "Power Management Health
> > > > > Check"
> > > > > feature planned for oVirt 3.5
> > > > >
> > > > > http://www.ovirt.org/Features/PMHealthCheck
> > > > > http://www.ovirt.org/Features/Design/DetailedPMHealthCheck
> > > > >
> > > > > Your comments/questions are mostly welcomed.
> > > > >
> > > > > Thanks
> > > > > Eli Mesika
> > > > > ___
> > > > > 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] oVirt 3.5 : "Power Management Health Check" - feature pages

[Gilad Chaplik]

- Original Message -
> From: "Yair Zaslavsky" 
> To: "Arthur Berezin" 
> Cc: "Gilad Chaplik" , "users" 
> Sent: Monday, May 5, 2014 6:39:02 AM
> Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - 
> feature  pages
> 
> 
> 
> - Original Message -
> > From: "Arthur Berezin" 
> > To: "Gilad Chaplik" 
> > Cc: "users" 
> > Sent: Sunday, May 4, 2014 5:35:59 PM
> > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > feature pages
> > 
> > In this case engine periodically checks health of hosts' power management
> > as
> > HA relies on it.
> > 
> > Arthur
> > 
> > - Original Message -
> > 
> > > From: "Gilad Chaplik" 
> > > To: "Eli Mesika" 
> > > Cc: "users" , "Arthur Berezin" 
> > > Sent: Sunday, May 4, 2014 5:26:45 PM
> > > Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > feature pages
> > 
> > > Hi Eli,
> > 
> > > Here is my comment :)
> > > Why engine needs to send the status health check, isn't there any 3rd
> > > parties
> > > that does it, that we can integrate with?
> > > If found, it probably has /less (known) bugs/more features/ and it's
> > > already
> > > written, tested, documented, allows further integration and probably
> > > deals
> > > with scale.
> > 
> > > btw, fixed some typos in your pages :-)
> > 
> > > Thanks,
> > > Gilad.
> 
> Hi, what 3rd party for example do you refer to?
> The PM code already exists at engine,
> And you're also using quartz for scheduling.
> 

Yair, 

You're are raising some good points, but imo the entire host monitoring (inc 
getVdsStats, etc.) should be externalized.
There are 2 major issues that we still don't cover:
- No HA for monitoring, who checks the hosts when the engine is down.
- No scale - the engine is a bottle-neck in network and compute.
Although the above is a huge arch change, we need to start somewhere, this 
feature sounds like a candidate to introduce it.

About the examples: 
http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-kick-ass/
The main goal of the feature if my suggestion is taken, is to select to most 
appropriate one.

Thanks, 
Gilad.

> 
> > 
> > > - Original Message -
> > > > From: "Eli Mesika" 
> > > > To: "users" 
> > > > Cc: "Arthur Berezin" 
> > > > Sent: Sunday, May 4, 2014 12:18:47 PM
> > > > Subject: [ovirt-users] oVirt 3.5 : "Power Management Health Check" -
> > > > feature pages
> > > >
> > > > Hi
> > > >
> > > > The following wiki pages were added to the "Power Management Health
> > > > Check"
> > > > feature planned for oVirt 3.5
> > > >
> > > > http://www.ovirt.org/Features/PMHealthCheck
> > > > http://www.ovirt.org/Features/Design/DetailedPMHealthCheck
> > > >
> > > > Your comments/questions are mostly welcomed.
> > > >
> > > > Thanks
> > > > Eli Mesika
> > > > ___
> > > > 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] [ovirt-devel] possible 3.4.1 blocker

[Sandro Bonazzola]

Il 05/05/2014 09:28, Sven Kieske ha scritto:
> Am 02.05.2014 17:05, schrieb Sven Kieske:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1093755
> 
> May I ask what the point of RC testing is, when discovered regressions
> get retargeted for the next release?
> 
> I thought the policy was to not release something with a known regression?

Yes, and due to that policy the bug has been re-targeted back to 3.4.1 and 
re-added to the 3.4.1 blocker list.
http://www.ovirt.org/OVirt_3.4_release-management#MUST
MUST: No regressions from 3.3 Release


> This does not encourage users to test release candidates at all, if
> found bugs don't get fixed.

Found bugs will be surely addressed according to above release criteria.
If the bug is identified as blocker (and regressions are blockers) it must be 
fixed before GA.

> 
> Maybe the next RCs can have a greater timeframe, so regressions found
> can get fixed before a release is made GA?

If blockers (including regressions) are found, GA will be postponed until they 
will be fixed.


> Otherwise I don't see a point in testing RCs anymore.
> 
> I did test it as soon as possible after it was announced in order to
> sort out possible regression bugs _before_ 3.4.1 gets released, as
> I'd like to use 3.4.1 in production.

And I really thank you for your testing!


> Can someone please enlighten me, what the release process is?
> 
> I really thought regressions get fixed before a release.
> 
> I'd also be happy if someone can tell me, that it's no regression
> but a fault on my side, so I can fix that.

I can't judge about if the above bug is a real regression or not,
added a comment in the BZ.
I hope to have answered your questions.
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] [QE] oVirt 3.4.1 GA status

[Sandro Bonazzola]

Il 02/05/2014 10:02, Sandro Bonazzola ha scritto:
> Il 02/05/2014 09:52, Sandro Bonazzola ha scritto:
>> Hi,
>> We're going to start composing oVirt 3.4.1 GA on 2014-05-07 08:00 UTC from 
>> 3.4.1 branches.
>>
>> The bug tracker [1] shows no blocking bugs for the release.

While testing 3.4.1 RC last week a few bugs have been identified as blockers:

1089567 integration ASSIGNEDvdsm sources are not available as 
tarball
1093721 integration NEW upgrade from 3.4.0 to 3.4.1 doesn't 
work anymore
1093755 infra   NEW [BUG] can't boot vm with cloud-init 
data submitted as json via REST api

Last one, Bug 1093755, looks like a regression from 3.3.5.
Since it has been re-targeted to 3.4.2 I removed it was initially from the list 
of blockers for 3.4.1.
However, since without that we're failing release criteria [6]: MUST: No 
regressions from 3.3 Release
The bug has been re-targeted to 3.4.1 and re-added to blockers.

Assignee, please provide an ETA on above bugs and fix them as soon as possible


>> Interest has been raised on the following BZ as nice to have:
>>
>> sla  - Bug 1049318 - pending memory not cleared when stopping paused VM
>> virt - Bug 1073453 - [RFE] add Debian 7 to the list of operating systems 
>> when creating a new vm
>>
>> There are still 138 bugs [2] targeted to 3.4.1.
>> Excluding node and documentation bugs we still have 106 bugs [3] targeted to 
>> 3.4.1.
>> Please review them as soon as possible and re-target them to a future 
>> release.
>> Bugs still targeted to 3.4.1 will be re-targeted to 3.4.2 after 3.4.1 GA 
>> release.
> 
> Better:
> Critical bugs will be re-targeted to 3.4.2 after 3.4.1 GA release.
> All remaining bugs will be re-targeted to 3.5.0.
> 
> 
>>
>> Maintainers / Assignee:
>> - Please remember to rebuild your packages before 2014-05-07 08:00 UTC
>> - If you find a blocker bug please remember to add it to the tracker [1]
>> - Please update the target to any next release for bugs that won't be in 
>> 3.4.1:
>>   it will ease gathering the blocking bugs for next releases.
>> - Please fill release notes, the page has been created here [4]
>>
>> All users:
>> - If you've tested the RC release or if you're testing nightly 3.4 snapshot 
>> builds, please add yourself to the test page [5]
>>
>>
>> [1] https://bugzilla.redhat.com/1080483
>> [2] http://red.ht/1gCFOtH
>> [3] http://red.ht/1laBSUj
>> [4] http://www.ovirt.org/OVirt_3.4.1_release_notes
>> [5] http://www.ovirt.org/Testing/oVirt_3.4.1_testing

[6] http://www.ovirt.org/OVirt_3.4_release-management#MUST


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

[ovirt-users] How to have this information?

[Ovirt User]

Hello,

it is possible have :

- CPU
- MEMORY
- NETWORK

usage of VM's from the manager ? trought API or.. snmpd, or.. .other stuff ?

I need to develop a web page to show this information to my customers.

thanks
Lukas

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

Re: [ovirt-users] [ovirt-devel] possible 3.4.1 blocker

[Sven Kieske]

Am 02.05.2014 17:05, schrieb Sven Kieske:
> https://bugzilla.redhat.com/show_bug.cgi?id=1093755

May I ask what the point of RC testing is, when discovered regressions
get retargeted for the next release?

I thought the policy was to not release something with a known regression?

This does not encourage users to test release candidates at all, if
found bugs don't get fixed.

Maybe the next RCs can have a greater timeframe, so regressions found
can get fixed before a release is made GA?

Otherwise I don't see a point in testing RCs anymore.

I did test it as soon as possible after it was announced in order to
sort out possible regression bugs _before_ 3.4.1 gets released, as
I'd like to use 3.4.1 in production.

Can someone please enlighten me, what the release process is?

I really thought regressions get fixed before a release.

I'd also be happy if someone can tell me, that it's no regression
but a fault on my side, so I can fix that.

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