This is great!
Thanks :)
On Tue, Dec 15, 2015 at 10:23 AM, Vojtech Szocs wrote:
> Nice work, Alexander!
>
> (GWTP's @ProxyEvent is a convenient mechanism, but as you wrote, it can lead
> to UI code being lazy-loaded too aggresively which hurts UI responsiveness.)
>
> Vojtech
>
On Tue, Dec 15, 2015 at 5:12 PM, Francesco Romani wrote:
> Hi all,
>
> I'm happy to start a weekly summary of what's going on on virt's world (VDSM
> edition).
>
> General topics
> * I've got some mixed feedback about my Vm-on-a-diet effort. I still believe
> that fat
Hi!
I've just posted the patch introducing new set of VM status checking
methods.
https://gerrit.ovirt.org/#/c/50590/
The methods are added to VMStatus class and delegated to VM class. The old
methods are marked as deprecated and we plan to get rid of them soon.
I highly recommend to use these
The oVirt Project is pleased to announce today the general availability of
oVirt 3.6.1.
This latest community release includes several new features, such as:
* Ability to add/remove objects from the PM Proxy Preference list in the
Power Management tab of Edit Host
* Enhanced Cinder Provider ->
- Original Message -
> From: "Shmuel Melamud"
> To: "devel"
> Sent: Tuesday, December 15, 2015 3:41:21 PM
> Subject: [ovirt-devel] New VM status functions - your comments?
>
> Hi!
>
>
Nice, but we cannot enable this until all the tests pass or disabled.
There is no point in broken or flaky functional tests.
On Wed, Dec 16, 2015 at 5:34 PM, Yaniv Bronheim wrote:
> So its not stable. It won't block merges and at least give us report after
> each merge. It
exactly - just posted a patch again that sings all fails as broken .
we'll get the report soon and I'll publish it as well. hope the run will
take less time now
On Wed, Dec 16, 2015 at 6:19 PM, Nir Soffer wrote:
> Nice, but we cannot enable this until all the tests pass or
Hi!
On Tue, Dec 15, 2015 at 5:12 PM, Francesco Romani
wrote:
> - we want to improve the reporting in case of migratio aborted. The
> ultimate goal is to let Engine (thus the User)
> know why a migration failed. To export this information, however, we
> need some cleanup
Hi,
4:23 AM and this paradox is struggling my head...
Can someone please confirm if oVirt supports QCOW2 *base* images?
AFAIK, oVirt only supports QCOW2 for *snapshots* not base images. Base
images must always be in RAW format and there is no way to create QCOW2
disks in Engine [1].
On the
Hello again,
Here is another problem :-)
today I tried to update my installation with the latest packages available,
but after starting engine-setup I get this message :
--== CONFIGURATION PREVIEW ==--
Default SAN wipe after delete : False
Firewall manager
10 matches
Mail list logo