On May 13, 2014, at 19:00 , Maor Lipchuk wrote:
> The specific verb is not that relevant.
> it's already being done when using FAILED_HOT_SET_NUMBER_OF_CPUS,
> VDS_INITIALIZING, RUN_VM_FAILED or STORAGE_DOMAIN_ERROR (and more)
>
> For general purposes we can use a new audit log such as this:
>
On 05/13/2014 03:16 AM, Jiri Moskovcak wrote:
On 05/12/2014 05:27 PM, Dan Kenigsberg wrote:
On Mon, May 12, 2014 at 02:04:05PM +0200, Jiri Moskovcak wrote:
Jiri, could you describe why you keep your LV active, but not open?
- the setup flow goes approximately like this:
1. create the LVs f
On Tue, May 13, 2014 at 5:43 PM, Dan Kenigsberg wrote:
> On Tue, May 13, 2014 at 05:22:15PM -0300, Amador Pahim wrote:
>> Building vdsm/master in F20, I've got:
>>
>> ./vdsm/virt/migration.py:223:19: E225 missing whitespace around operator
>>
>> In vdsm/virt/migration.py:
>>
>> 218 e.err =
Building vdsm/master in F20, I've got:
./vdsm/virt/migration.py:223:19: E225 missing whitespace around operator
In vdsm/virt/migration.py:
223 -1, -1) # int1, int2$
pep8 is not accepting the negative integer. Instead, it is handling the
minus sign as
On Tue, May 13, 2014 at 05:22:15PM -0300, Amador Pahim wrote:
> Building vdsm/master in F20, I've got:
>
> ./vdsm/virt/migration.py:223:19: E225 missing whitespace around operator
>
> In vdsm/virt/migration.py:
>
> 218 e.err = (libvirt.VIR_ERR_OPERATION_ABORTED, # error code$
> 219
Thanks Malini & Einav :-)
Indeed, the patch only adds the necessary infrastructure; sorting must be
enabled for individual columns (either server-side or client-side sorting).
Currently, sort icon (triangle) is positioned to the left of column header
text. Alternatively, it could be positioned to
The specific verb is not that relevant.
it's already being done when using FAILED_HOT_SET_NUMBER_OF_CPUS,
VDS_INITIALIZING, RUN_VM_FAILED or STORAGE_DOMAIN_ERROR (and more)
For general purposes we can use a new audit log such as this:
RETUNED_VDSM_ERROR_MESSAGE=The error message returned by VDSM w
Vdsm sync call May 13, 2014
===
(Join us every other week, 14:30 GMT, on https://bluejeans.com/35386075901 or
https://www.intercallonline.com/listNumbersByCode.action?confCode=35386075901
)
===
- We had a long descussion about multiple graphic device
Many thanks, Vojtech, for making it happen - it is highly appreciated!
Clarifying that, to my understanding, just the infrastructure is in
place - there aren't any sortable columns in the GUI yet. In order
to turn columns in the GUI to sortable, need to follow Vojtech's
instructions below for ea
Yay Thank you for making this happen. This is a basic need that users have
talked to me about in almost all UX conversations I have had so far!
- Original Message -
From: "Vojtech Szocs"
To: devel@ovirt.org
Sent: Tuesday, May 13, 2014 10:37:51 AM
Subject: [ovirt-devel] Sortable colum
Hey guys,
UI plugin API now supports SystemTreeSelectionChange event, which is fired
whenever "System Tree" selection (currently selected tree node) is changed.
Example usage:
api.register({
SystemTreeSelectionChange: function(selectedNode) {
// See SystemTreeItemType Java enum f
the specific example was CreateStorageDomain, not ConnectStorageDomain.
but anyhow, the problem is a general one: add some more information to the
errors that engine gets from VDSM, without doing too much work. Some of these
errors my fit well into "events", but some will not.
- Original Me
Hey guys,
oVirt UI has been missing column sort functionality for quite a while
now, but here's some good news.
I've just merged patch [1] that adds support for both server-side and
client-side sorting of table columns. This patch adds the necessary
infra/API; column sorting must be enabled per-c
The audit logs are presented in the events tab in the GUI, usually we
print an audit log when we succeed/fail to execute a command and usually
it is more verbal then the CDA messages (Which presented in the dialog
boxes).
Since ConnectStorageDomain is a VDS command which runs in the execute
phase
Maor can you please explain? I'm not familiar with this audit log
- Original Message -
From: "Maor Lipchuk"
To: "Yoav Kleinberger" , "Dan Kenigsberg"
Cc: devel@ovirt.org
Sent: Tuesday, May 13, 2014 5:17:02 PM
Subject: Re: [ovirt-devel] improving VDSM error reporting
I would like to sug
I would like to suggest another solution,
Why not let the audit log present the extra error description.
VDSM can override the existing error message before returning it to the
engine with the extra data.
that way you will not have to add new attributes to the existing API,
and the dialog message
well, we can add the python text, and the UX team will decide under what
circumstances to display it. At least for some users it will add information.
- Original Message -
From: "Dan Kenigsberg"
To: "Yoav Kleinberger"
Cc: devel@ovirt.org
Sent: Tuesday, May 13, 2014 4:08:47 PM
Subject: R
On Tue, May 13, 2014 at 08:31:16AM -0400, Yoav Kleinberger wrote:
> Hi Dan,
> A few points:
>
> 1. I explained the problem using the existing "message" field. An old VDSM
> will have the "meaningless" messages, and when working with a new engine they
> will be displayed to the user.
As I have s
Hi Dan,
A few points:
1. I explained the problem using the existing "message" field. An old VDSM will
have the "meaningless" messages, and when working with a new engine they will
be displayed to the user.
2. The patch you attached generates the message inside the code for a specific
circumstan
On Tue, May 13, 2014 at 06:59:33AM -0400, Yoav Kleinberger wrote:
> Hi all,
>
> This idea was born from this bug: https://bugzilla.redhat.com/730619
>
> If, for example, creating a new storage domain
> fails because there's no space left, the user gets:
>
> "Error creating a storag
Hi all,
This idea was born from this bug: https://bugzilla.redhat.com/730619
If, for example, creating a new storage domain
fails because there's no space left, the user gets:
"Error creating a storage domain"
which is not very helpful, since the real problem (no space) is not rep
Here is BZ for it: https://bugzilla.redhat.com/1097182
On Tue, May 13, 2014 at 12:17 PM, Piotr Kliczewski
wrote:
> I tried to deploy all in one engine (built from master) and noticed
> engine setup failed with:
>
> 2014-05-13 12:42:40 DEBUG otopi.context context._executeMethod:152
> method except
I tried to deploy all in one engine (built from master) and noticed
engine setup failed with:
2014-05-13 12:42:40 DEBUG otopi.context context._executeMethod:152
method exception
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142,
in _executeMeth
On Tue, May 13, 2014 at 10:21 AM, Sandro Bonazzola wrote:
> Il 13/05/2014 10:17, Piotr Kliczewski ha scritto:
>> On Tue, May 13, 2014 at 10:08 AM, Sandro Bonazzola
>> wrote:
>>> Il 13/05/2014 10:03, Piotr Kliczewski ha scritto:
On Tue, May 13, 2014 at 8:58 AM, Sandro Bonazzola
wrote:
- Original Message -
> From: "Enrico Tagliavini"
> To: devel@ovirt.org
> Sent: Thursday, May 8, 2014 1:15:15 PM
> Subject: [ovirt-devel] GFS2 mount via symlink problem
>
> The storage is mounted twice, first by the gfs2 init script and then
> by ovirt. As you can see even if both ovirt an
Il 13/05/2014 10:17, Piotr Kliczewski ha scritto:
> On Tue, May 13, 2014 at 10:08 AM, Sandro Bonazzola
> wrote:
>> Il 13/05/2014 10:03, Piotr Kliczewski ha scritto:
>>> On Tue, May 13, 2014 at 8:58 AM, Sandro Bonazzola
>>> wrote:
Il 13/05/2014 08:42, Piotr Kliczewski ha scritto:
> On M
On Tue, May 13, 2014 at 10:08 AM, Sandro Bonazzola wrote:
> Il 13/05/2014 10:03, Piotr Kliczewski ha scritto:
>> On Tue, May 13, 2014 at 8:58 AM, Sandro Bonazzola
>> wrote:
>>> Il 13/05/2014 08:42, Piotr Kliczewski ha scritto:
On Mon, May 12, 2014 at 5:55 PM, Sandro Bonazzola
wrote:
Il 13/05/2014 10:03, Piotr Kliczewski ha scritto:
> On Tue, May 13, 2014 at 8:58 AM, Sandro Bonazzola wrote:
>> Il 13/05/2014 08:42, Piotr Kliczewski ha scritto:
>>> On Mon, May 12, 2014 at 5:55 PM, Sandro Bonazzola
>>> wrote:
Il 12/05/2014 17:09, Piotr Kliczewski ha scritto:
> I want t
On Tue, May 13, 2014 at 8:58 AM, Sandro Bonazzola wrote:
> Il 13/05/2014 08:42, Piotr Kliczewski ha scritto:
>> On Mon, May 12, 2014 at 5:55 PM, Sandro Bonazzola
>> wrote:
>>> Il 12/05/2014 17:09, Piotr Kliczewski ha scritto:
I want to build log collector rpm and noticed that is failing due
Hi,
can you please create the following repositories?
ovirt-setup: will have ovirt-engine-setup python sources currently shipped
within ovirt-engine in packaging/setup.
Since it will be able to install dwh / reports / websocket on host where
ovirt-engine is not installed
I think that calling it
On 05/12/2014 05:27 PM, Dan Kenigsberg wrote:
On Mon, May 12, 2014 at 02:04:05PM +0200, Jiri Moskovcak wrote:
Jiri, could you describe why you keep your LV active, but not open?
- the setup flow goes approximately like this:
1. create the LVs for the hosted-engine
2. install the engine into
31 matches
Mail list logo
