- Original Message -
From: Livnat Peer lp...@redhat.com
To: Simon Grinberg si...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Thursday, July 5, 2012 8:58:20 AM
Subject: Re: [Engine-devel] Fwd: Problem in REST API handling/displaying of
logical networks
On 04/07/12 19:49
-devel] Fwd: Problem in REST API
handling/displaying of logical networks
On 03/07/12 21:28, Itamar Heim wrote:
On 07/03/2012 10:30 AM, Livnat Peer wrote:
On 02/07/12 17:35, Mike Kolesnik wrote:
Hi All,
I would like to hear opinions about a behaviour that I think
On 07/05/2012 10:51 AM, Livnat Peer wrote:
Actually the API has the same concept as you suggest for storage
domains.
At the top level you don't have a status field, but under data
center level, where it's valid then you get the status property.
Same should go for networks.
The status
On 07/05/2012 11:40 AM, Livnat Peer wrote:
On 05/07/12 11:31, Michael Pasternak wrote:
On 07/05/2012 10:51 AM, Livnat Peer wrote:
Actually the API has the same concept as you suggest for storage
domains.
At the top level you don't have a status field, but under data
center level, where it's
- Original Message -
From: Michael Pasternak mpast...@redhat.com
To: Livnat Peer lp...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, Simon Grinberg
si...@redhat.com
Sent: Thursday, July 5, 2012 11:31:41 AM
Subject: Re: [Engine-devel] Fwd: Problem in REST API handling
On 05/07/12 11:56, Michael Pasternak wrote:
On 07/05/2012 11:40 AM, Livnat Peer wrote:
On 05/07/12 11:31, Michael Pasternak wrote:
On 07/05/2012 10:51 AM, Livnat Peer wrote:
Actually the API has the same concept as you suggest for storage
domains.
At the top level you don't have a status
-devel] Fwd: Problem in REST API handling/displaying of
logical networks
On 07/05/2012 10:51 AM, Livnat Peer wrote:
Actually the API has the same concept as you suggest for
storage
domains.
At the top level you don't have a status field, but under
data
center level, where it's valid
On 07/05/2012 12:19 PM, Livnat Peer wrote:
I'll give you one scenario and I'm sure there are lot more:
delete all unused networks
not strong enough use case in my opinion
i do see sense in this, and based on my experience of
closing ~5 bugs on this for SD and explaining like
On 07/05/2012 01:38 PM, Livnat Peer wrote:
On 05/07/12 13:23, Mike Kolesnik wrote:
On 07/05/2012 12:19 PM, Livnat Peer wrote:
I'll give you one scenario and I'm sure there are lot more:
delete all unused networks
not strong enough use case in my opinion
i do see sense in this, and
On 07/05/2012 01:43 PM, Mike Kolesnik wrote:
- Original Message -
On 05/07/12 13:23, Mike Kolesnik wrote:
On 07/05/2012 12:19 PM, Livnat Peer wrote:
I'll give you one scenario and I'm sure there are lot more:
delete all unused networks
not strong enough use case in my opinion
Comments inline
- Original Message -
From: Mike Kolesnik mkole...@redhat.com
To: engine-devel engine-devel@ovirt.org
Sent: Monday, July 2, 2012 5:35:52 PM
Subject: [Engine-devel] Fwd: Problem in REST API handling/displaying of
logical networks
Hi All,
I would
On 07/03/2012 09:51 AM, Avi Tal wrote:
...
Why do we keep holding this Top level collection instead of having each network
related under his datacenter (/api/datacenter/id/networks)???
why do we keep VMs as top level? they only exist in data center...
why do we keep Clusters as top level?
On 07/03/2012 10:00 AM, Itamar Heim wrote:
On 07/03/2012 09:51 AM, Avi Tal wrote:
...
Why do we keep holding this Top level collection instead of having
each network related under his datacenter
(/api/datacenter/id/networks)???
why do we keep VMs as top level? they only exist in data
On 02/07/12 17:35, Mike Kolesnik wrote:
Hi All,
I would like to hear opinions about a behaviour that I think is
problematic in
REST API handling of logical networks.
-- Intro --
Today in the REST API we are exposing two collections for logical
network related entities.
First is a top
On 07/03/2012 10:06 AM, Yaniv Kaul wrote:
On 07/03/2012 10:00 AM, Itamar Heim wrote:
On 07/03/2012 09:51 AM, Avi Tal wrote:
...
Why do we keep holding this Top level collection instead of having each
network related under his datacenter (/api/datacenter/id/networks)???
why do we keep VMs
- Original Message -
From: Itamar Heim ih...@redhat.com
To: Avi Tal a...@redhat.com
Cc: Mike Kolesnik mkole...@redhat.com, engine-devel
engine-devel@ovirt.org
Sent: Tuesday, July 3, 2012 10:00:38 AM
Subject: Re: [Engine-devel] Fwd: Problem in REST API handling/displaying
in REST API handling/displaying of
logical networks
On 07/03/2012 09:51 AM, Avi Tal wrote:
...
Why do we keep holding this Top level collection instead of having
each network related under his datacenter
(/api/datacenter/id/networks)???
why do we keep VMs as top level? they only exist in data center
Hi All,
I would like to hear opinions about a behaviour that I think is problematic in
REST API handling of logical networks.
-- Intro --
Today in the REST API we are exposing two collections for logical
network related entities.
First is a top level collection which is out of any
18 matches
Mail list logo
