Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-31 Thread Samuel Bercovici
[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 'admin_state_up

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-31 Thread Eugene Nikanorov
[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

[openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-29 Thread Eugene Nikanorov
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

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-29 Thread Avishay Balderman
] [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, ERROR. We also have

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-29 Thread Eugene Nikanorov
] [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

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-29 Thread Itsuro ODA
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' attribute

Re: [openstack-dev] [Neutron][LBaaS] Object status and admin_state_up

2013-10-29 Thread Ravi Chunduru
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,