8:33 a.m.
Hi,
I believe we should save the REST API behavior and keep using status object instead of
<active>true</active> for vm nics.
We should use:
<status>
<state>active<state>
</status>
Many rest frameworks works around that <status> object in order to verify element
state and we shouldn't change that behavior.
This is true also for hotplug disk
Avi Tal
Red Hat tlv
2:34 a.m.
New subject: [Engine-devel] Vm nic active boolean should be converted to status/state=active
Hi,
I believe we should save the REST API behavior and keep using status
object instead of <active>true</active> for vm nics.
We should use:
<status>
<state>active<state>
</status>
Active is a binary state, why would we need a multi-state representation for it?
Many rest frameworks works around that <status> object in order to
verify element state and we shouldn't change that behavior.
This is true also for hotplug disk
Avi Tal
Red Hat tlv
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
2:47 a.m.
New subject: [Engine-devel] Vm nic active boolean should be converted to status/state=active
Avi Tal
Red Hat tlv
----- Original Message -----
From: "Mike Kolesnik" <mkolesni(a)redhat.com>
To: "Avi Tal" <atal(a)redhat.com>
Cc: engine-devel(a)ovirt.org
Sent: Thursday, June 14, 2012 10:34:32 AM
Subject: Re: [Engine-devel] Vm nic active boolean should be converted
to status/state=active
> Hi,
> I believe we should save the REST API behavior and keep using
> status
> object instead of <active>true</active> for vm nics.
>
> We should use:
> <status>
> <state>active<state>
> </status>
Active is a binary state, why would we need a multi-state
representation for it?
The way i see it (as a REST API user) active/deactive are states just like up/down.
If i would like to verify the nic active state i would go to the nic state just as simple
as it sound.
I can't see any good reason way defining it different then host state or DataCenter
state or even storage state.
>
>
> Many rest frameworks works around that <status> object in order to
> verify element state and we shouldn't change that behavior.
>
> This is true also for hotplug disk
>
> Avi Tal
> Red Hat tlv
>
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
4341
days inactive
4342
days old
2 comments
2 participants
participants (2)
-
Avi Tal -
Mike Kolesnik