out.
>
> German
>
> -Original Message-
> From: Brandon Logan
> [mailto:brandon.lo...@rackspace.com<mailto:brandon.lo...@rackspace.com>]
> Sent: Tuesday, August 05, 2014 8:27 AM
> To:
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.or
t out.
> >
> > German
> >
> > -Original Message-
> > From: Brandon Logan [mailto:brandon.lo...@rackspace.com]
> > Sent: Tuesday, August 05, 2014 8:27 AM
> > To: openstack-dev@lists.openstack.org
> > Subject: Re: [openstack-dev] [Neutron][LBaaS] &qu
tus discussion - likely high bandwith to work all
> of that out.
>
> German
>
> -Original Message-
> From: Brandon Logan [mailto:brandon.lo...@rackspace.com]
> Sent: Tuesday, August 05, 2014 8:27 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-d
: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron][LBaaS] "status" in entities
Hello Vijay!
Well this is a hold over from v1, but the status is a provisioning status. So
yes, when something is deployed successfully it should be ACTIVE. The
exception to t
Hello Vijay!
Well this is a hold over from v1, but the status is a provisioning
status. So yes, when something is deployed successfully it should be
ACTIVE. The exception to this is the member status, in that it's status
can be INACTIVE if a health check fails. Now this will probably cause
edg
Hi:
I think we had some discussions around 'status' attribute
earlier, I don't recollect the conclusion.
Does it reflect the deployment status?
Meaning, if the status of an entity is ACTIVE, the user has to
infer that the entity is deployed successfully in the backen
