[openstack-dev] [Neutron][LBaaS] Regarding v2 LoadBalancer's status(es)
phillip.toohill at RACKSPACE.COM
Tue Dec 15 05:38:47 UTC 2015
>Yeah this needs to be better documented. I would say all of those
>statuses in the docs pertain to provisioning_status, except for
>INACTIVE, which I'm actually not sure where that is being used. ...
There is this patch to utilize the INACTIVE status: https://review.openstack.org/#/c/255875/
From: Brandon Logan <brandon.logan at RACKSPACE.COM>
Sent: Monday, December 14, 2015 6:25 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Neutron][LBaaS] Regarding v2 LoadBalancer's status(es)
On Mon, 2015-12-14 at 15:19 -0600, Bryan Jones wrote:
> Hi All,
> I had a few issues/questions regarding the statuses
> (provisioning_status and operating_status) of a v2 LoadBalancer. To
> preface these, I am working on the LBaaS v2 support in Heat.
> The first question regards the allowed values for each of
> provisioning_status and operating status. Here it seems the
> documentation is ambiguous.  provides a list of possible statuses,
> but does not mention if they are options for provisioning_status or
> operating_status.  provides much clearer options for each status,
> but does not show the INACTIVE status mention in . Should INACTIVE
> be included in the possible options for one of the statuses, or should
> it be removed from  altogether?
Yeah this needs to be better documented. I would say all of those
statuses in the docs pertain to provisioning_status, except for
INACTIVE, which I'm actually not sure where that is being used. I have
to plead ignorance on this. I was initially thinking operating_status
but I don't see it being used. So that probably needs to just be pulled
out of the docs entirely. The operating_status statuses are listed in
code here . They are pretty self explanatory, except for maybe
DEGRADED. DEGRADED basically means that one or more of its descendants
are in an OFFLINE operating_status. NO_MONITOR means no health monitor
so operating_status can't be evaluated. DISABLED means admin_state_up
on that entity is set to False.
> Second,  also mentions that an error_details attribute will be
> provided if the status is ERROR. I do not see any error_details
> attribute in the LoadBalancer code , so I am wondering where that
> attribute comes from?
This is actually something that was in v1 (status_description) that we
have not added to v2. It would be nice to have but its not there yet.
The docs should be updated to remove this.
> Finally, I'm curious what operations can be performed on the
> LoadBalancer if the operating_status is OFFLINE and the
> provisioning_status is ACTIVE. First is this state possible? And
> second, can the LoadBalancer be manipulated (i.e. add a Listener to
> the LoadBalancer) if it is in this state?
Operations on a load balancer are only restricted based on the
provisioning_status. operating_status is purely for information. If
the load balancer's provisioning status is ACTIVE then you can do any
operation on it, regardless of operating_status.
I don't know of a current scenario where ACTIVE/OFFLINE status is
actually possible for a load balancer, but a driver could decide to do
that, though I'd like to understand that use case first.
> BRYAN JONES
> Software Engineer - OpenStack Development
> Phone: 1-507-253-2620
> E-mail: jonesbr at us.ibm.com
> Find me on: LinkedIn:
> 3605 Hwy 52 N
> Rochester, MN 55901-1407
> United States
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev