>
> -Sam.
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Eugene Nikanorov [mailto:enikano...@mirantis.com]
> *Sent:* Tuesday, October 29, 2013 11:19 AM
> *To:* OpenStack Development Mailing List
> *Subject:* [openstack-dev] [Neutron][LBaaS] O
[mailto:enikano...@mirantis.com]
Sent: Tuesday, October 29, 2013 11:19 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up
Hi folks,
Currently there are two attributes of vips/pools/members that represent a
status: 'status' and '
Generally loadbalancer will have the following options
enable - configurationally enable
disable - configurationally disable
up - status alive
down - status down
If we have the above it will be meaningful to get actual status of the
object.
Thanks,
-Ravi.
On Tue, Oct 29, 2013 at 4:33 PM, It
Hi,
I think "INACTIVE" is right for resources with admin_statu_up False.
BTW, there are following requirements:
* Change to ACTIVE from PENDING_CREATE/UPDATE when the serives
is available actually. (ie. after lbaas_agent done the job.)
* Reflect a member is alive or not to the 'status' attribut
lopment Mailing List
> *Subject:* [openstack-dev] [Neutron][LBaaS] Object status and
> admin_state_up
>
> ** **
>
> Hi folks,
>
> ** **
>
> Currently there are two attributes of vips/pools/members that represent a
> status: 'status' an
] [Neutron][LBaaS] Object status and admin_state_up
Hi folks,
Currently there are two attributes of vips/pools/members that represent a
status: 'status' and 'admin_state_up'.
The first one is used to represent deployment status and can be PENDING_CREATE,
ACTIVE, PENDING_DELETE,
Hi folks,
Currently there are two attributes of vips/pools/members that represent a
status: 'status' and 'admin_state_up'.
The first one is used to represent deployment status and can be
PENDING_CREATE, ACTIVE, PENDING_DELETE, ERROR.
We also have admin_state_up which could be True or False.
I'd
