On Tuesday 08 May 2012 10:45 AM, Itamar Heim wrote:
On 05/07/2012 11:52 PM, Ayal Baron wrote:
- Original Message -
On 05/07/2012 07:06 PM, Shireesh Anjal wrote:
On Monday 07 May 2012 02:06 AM, Ayal Baron wrote:
- Original Message -
i can't see any justification for the
On 07/05/12 21:33, Adam Litke wrote:
The current APIs for retrieving all task information do not actually return
all
task information. I would like to introduce a new API that corrects this and
other issues with the current API while preserving backwards compatibility
with
ovirt-engine
cc-ing engine-devel.
Oved
- Original Message -
From: Hans de Goede hdego...@redhat.com
To: Oved Ourfalli ov...@redhat.com
Cc: Dave Allan dal...@redhat.com, Jiri Denemark jdene...@redhat.com,
Michal Privoznik
mpriv...@redhat.com, Itamar Heim ih...@redhat.com, Igor Lvovsky
Hi, all
When I access the REST API like this
import urllib2
theurl = 'http://9.181.129.112:8080/api'
username = 'admin@internal'
password = 'abcd1234'
# a great password
passman = urllib2.HTTPPasswordMgrWithDefaultRealm()
passman.add_password('ENGINE',
- Original Message -
From: Dan Kenigsberg dan...@redhat.com
To: Oved Ourfalli ov...@redhat.com, Dave Allan dal...@redhat.com
Cc: Dave Allan dal...@redhat.com, Jiri Denemark jdene...@redhat.com,
Michal Privoznik
mpriv...@redhat.com, Itamar Heim ih...@redhat.com, Igor Lvovsky
On 05/07/2012 08:13 PM, Itamar Heim wrote:
On 05/07/2012 07:06 PM, Shireesh Anjal wrote:
On Monday 07 May 2012 02:06 AM, Ayal Baron wrote:
- Original Message -
i can't see any justification for the 'gluster' prefix,
as this is only additional /service/ provided by the project,
and
On 05/08/2012 12:00 PM, Eoghan Glynn wrote:
1) what's the name you'd give this parameter? job-id? batch-id?
flow-id? command-id? correlation-id???
job-id will confuse us with engine's job-id which is a single
command
today.
correleation-id is pretty long and confusing as implies on
On Tue, May 08, 2012 at 10:50:49AM +0300, Doron Fediuck wrote:
On 07/05/12 21:33, Adam Litke wrote:
The current APIs for retrieving all task information do not actually return
all
task information. I would like to introduce a new API that corrects this
and
other issues with the