- Original Message -
> From: "Adam Litke"
> To: "Francesco Romani"
> Cc: devel@ovirt.org
> Sent: Wednesday, September 17, 2014 10:32:11 PM
> Subject: Re: [ovirt-devel] [ovirt-users] OVIRT-3.5-TEST-DAY-3: replace
> XML-rpc with JSON-rpc
> >On engine logs I see something alike this: http:
- Original Message -
> From: "Sandro Bonazzola"
> To: devel@ovirt.org
> Sent: Wednesday, September 17, 2014 6:02:37 PM
> Subject: [ovirt-devel] OVIRT-3.5-TEST-DAY-3: Documentation
>
> Hi,
> my assignment for third test day was on Documentation- 3.5 feature pages:
> Check what's missing
On 17/09/14 15:46 -0400, Francesco Romani wrote:
- Original Message -
From: "Francesco Romani"
To: devel@ovirt.org
Cc: "users"
Sent: Wednesday, September 17, 2014 5:33:01 PM
Subject: [ovirt-users] OVIRT-3.5-TEST-DAY-3: replace XML-rpc with JSON-rpc
Everything I tried went OK, and lo
- Original Message -
> From: "Francesco Romani"
> To: devel@ovirt.org
> Cc: "users"
> Sent: Wednesday, September 17, 2014 5:33:01 PM
> Subject: [ovirt-users] OVIRT-3.5-TEST-DAY-3: replace XML-rpc with JSON-rpc
> Everything I tried went OK, and logs look good to me.
>
> I run in a few hi
Hi,
today I had to test how to recover a broken system using backup/restore tool
[1] or disaster recovery procedure [2].
Unfortunately I really had a lot of troubles just trying to setup my test
environment so no good news on that side.
I was using two host: one for the engine, the other as an
Hi everyone
of this test day I played with the new JSON-rpc transport, which is enabled by
default.
I set up from scratch two hypervisors running on RHEL 6.5, while Engine was
running on F19.
I created everything from scratch and tested all the flows I known good enough,
including
less-then-co
Hi,
I followed deployment manual from [1] and configured two DCs with
single cluster each.
During configuration of the UI I noticed that in optimizer result tab there was:
Status: Data refresh failed: undefined
with Martin's help we found that when setting
security.mixed_content.block_active_co
On Wed, Sep 17, 2014 at 09:12:28AM -0400, Oved Ourfali wrote:
>
>
> - Original Message -
> > From: "Sandro Bonazzola"
> > To: "Oved Ourfali"
> > Cc: us...@ovirt.org, devel@ovirt.org
> > Sent: Wednesday, September 17, 2014 4:10:33 PM
> > Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTI
Hi,
my assignment for third test day was on Documentation- 3.5 feature pages: Check
what's missing and what's wrong
the feature documentation looks outdated as far as I've been able to check it.
More in detail:
http://www.ovirt.org/Features/Gluster_Volume_Capacity
test result: failed
bug
Hello,
I tested the support for limiting the use of CPU of VMs. Setting it up
in the GUI worked correctly, but when starting the VM the settings are
ignored. Apparently the reason is a mismatch between the parameters that
the engine sends and what VDSM expects:
https://bugzilla.redhat.com/1142851
- Original Message -
> From: "Sandro Bonazzola"
> To: "Oved Ourfali"
> Cc: us...@ovirt.org, devel@ovirt.org
> Sent: Wednesday, September 17, 2014 4:10:33 PM
> Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0
> status
>
> Il 17/09/2014 15:09, Oved Ourfali h
Il 17/09/2014 15:09, Oved Ourfali ha scritto:
>> Bug ID Whiteboard Status Summary
>> > 1135909infra POST[Event log] Wrong warning about
>> > available swap memory of
>> > host [1023MB], when actually host has [1024MB] memory size
> We're still discussing whether to a
- Original Message -
> From: "Sandro Bonazzola"
> To: devel@ovirt.org, us...@ovirt.org
> Sent: Wednesday, September 17, 2014 2:46:10 PM
> Subject: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 status
>
> Hi,
> We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test D
Hi,
well the message in the topic already explains what is wrong.
This happend already once some days ago and dcaro fixed it, but somehow
this occurs again.
It would be kind of someone could fix it.
Thanks
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Serv
I still think this should block the release.
I don't know why it is targeted to 3.5.1.
This was working in prior releases (custom script via cloud-init)
but it does not in 3.5. so it is a clear regression.
On 17/09/14 13:46, Sandro Bonazzola wrote:
> 1138314 virtNEW Fail to
- Original Message -
> From: "Sandro Bonazzola"
> To: devel@ovirt.org, us...@ovirt.org
> Sent: Wednesday, September 17, 2014 2:46:10 PM
> Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 status
>
> Hi,
> We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day
Hi,
We're going to start composing oVirt 3.4.4 GA on *2014-09-23 08:00 UTC* from
3.4 branch.
Maintainers:
- Please be sure that 3.4 snapshot allow to create VMs before *2014-09-22 15:00
UTC*
- Please be sure that no pending patches are going to block the release before
*2014-09-22 15:00 UTC*
- I
Hi,
We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day
results and oVirt Sync Meeting decisions) on Monday 2014-09-22.
Maintainers:
- Please be sure that 3.5 snapshot satisfy release criteria[9]
- Please be sure that no pending patches are going to block the release
- I
Hey Daniel,
- Original Message -
> Hello Fabian,
>
> I do not know if the feature has made it - can I run a hosted engine
> with node?
Yep - That is one of the things under test :)
The iso below includes hosted engine support, that means, Node contains a page
which you can use to start
Hi,
> Why should an incomplete, thus non working feature get merged?
> Do you also merge incomplete bugfixes?
> One commit should contain one feature or one bugfix, imho?
Let me rephrase your sentence a bit:
One commit should contain one self-contained and isolated change.
But that does not mea
- Original Message -
> From: "Sven Kieske"
> To: devel@ovirt.org
> Sent: Wednesday, September 17, 2014 12:01:50 PM
> Subject: Re: [ovirt-devel] Stable branch gerrit hook and Related-To: bug
>
> Why should an incomplete, thus non working feature get merged?
Adding a feature may require im
- Original Message -
> From: "Yedidyah Bar David"
> To: "Sven Kieske"
> Cc: devel@ovirt.org
> Sent: Wednesday, September 17, 2014 11:08:52 AM
> Subject: Re: [ovirt-devel] Stable branch gerrit hook and Related-To: bug
> > That is not a bad idea, but there is one use case you do not consid
- Original Message -
> From: "Sven Kieske"
> To: devel@ovirt.org
> Sent: Wednesday, September 17, 2014 12:01:50 PM
> Subject: Re: [ovirt-devel] Stable branch gerrit hook and Related-To: bug
>
> Why should an incomplete, thus non working feature get merged?
> Do you also merge incomplete b
Why should an incomplete, thus non working feature get merged?
Do you also merge incomplete bugfixes?
One commit should contain one feature or one bugfix, imho?
I know this can be difficult sometimes, but still, at least
in the master branch this rule should get enforced, maybe create
a staging br
24 matches
Mail list logo