://bugs.launchpad.net/neutron/+bug/1248423
Thanks
Avishay
From: Salvatore Orlando [mailto:sorla...@nicira.commailto:sorla...@nicira.com]
Sent: Thursday, November 14, 2013 1:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] - Vendor specific
/1248423
Thanks
Avishay
From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: Thursday, November 14, 2013 1:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] - Vendor specific erros
In general, an error state make sense.
I think you might
Thanks
Avishay
*From:* Salvatore Orlando [mailto:sorla...@nicira.com]
*Sent:* Thursday, November 14, 2013 1:15 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Neutron] - Vendor specific erros
In general, an error state make sense
In general, an error state make sense.
I think you might want to send more details about how this state plugs into
the load balancer state machine, but I reckon it is a generally
non-recoverable state which could be reached by any other state; in that
case it would be a generic enough case which
Hi
Some of the DB entities in the LBaaS domain inherit from
HasStatusDescriptionhttps://github.com/openstack/neutron/blob/master/neutron/db/models_v2.py#L40
With this we can set the entity status (ACTIVE, PENDING_CREATE,etc) and a
description for the status.
There are flows in the Radware LBaaS