Re: [openstack-dev] [neutron][lbaas] Object statuses

2015-01-26 Thread Samuel Bercovici
+1 I also prefer option 2 in general with slight inclination to 2-B -Original Message- From: Brandon Logan [mailto:brandon.lo...@rackspace.com] Sent: Friday, January 23, 2015 9:21 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [neutron][lbaas] Object statuses So I am

Re: [openstack-dev] [neutron][lbaas] Object statuses

2015-01-23 Thread Jorge Miramontes
The example you put implicitly assigns the status tree to a load balancer. Is sharing only allowed for sub resources? Or can sub resources be shared across multiple load balancers? If that is the case then I suspect that statuses may be exposed in many different places correct? Cheers, --Jorge

[openstack-dev] [neutron][lbaas] Object statuses

2015-01-22 Thread Brandon Logan
So I am resurrecting this topic now because we put this discussion on a a brief hold, but are now discussing it again and need to decide asap. We've all agreed we need a provisioning_status and operating_status fields. We now need to decide where to show these statuses to the user. Option 1: