andon
From: Jorge Miramontes [jorge.miramon...@rackspace.com]
Sent: Monday, July 07, 2014 12:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do not
exist in a driver backend
Hey Mark,
To add, one reason we
Hey Mark,
To add, one reason we have a DELETED status at Rackspace is that certain
sub-resources are still relevant to our customers. For example, we have a
usage sub-resource which reveals usage records for the load balancer. To
illustrate, a user issues a DELETE on /loadbalancers/ but can still
questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do not
exist in a driver backend
On Jul 4, 2014, at 5:27 PM, Brandon Logan wrote:
> Hi German,
>
> That actually brings up another thing that needs to be done. There is
> no DELETED state. When an
On Jul 4, 2014, at 5:27 PM, Brandon Logan wrote:
> Hi German,
>
> That actually brings up another thing that needs to be done. There is
> no DELETED state. When an entity is deleted, it is deleted from the
> database. I'd prefer a DELETED state so that should be another feature
> we implemen
gt; Sent: Thursday, July 03, 2014 11:59 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do
> not exist in a driver backend
> >
> > +1 to QUEUED status.
> >
> > For
> German
>
> -Original Message-
> From: Jorge Miramontes [mailto:jorge.miramon...@rackspace.com]
> Sent: Thursday, July 03, 2014 11:59 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron][LBaaS] Status of entitie
[mailto:jorge.miramon...@rackspace.com]
Sent: Thursday, July 03, 2014 11:59 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do not
exist in a driver backend
+1 to QUEUED status.
For entities that have the concept of being
+1 to QUEUED status.
For entities that have the concept of being attached/detached why not have
a 'DETACHED' status to indicate that the entity is not provisioned at all
(i.e. The config is just stored in the DB). When it is attached during
provisioning then we can set it to 'ACTIVE' or any of the
If the objects remain in 'PENDING_CREATE' until provisioned it would seem
that the process got stuck in that status and may be in a bad state from
user perspective. I like the idea of QUEUED or similar to reference that
the object has been accepted but not provisioned.
Phil
On 7/3/14 10:28 AM, "B
With the new API and object model refactor there have been some issues
arising dealing with the status of entities. The main issue is that
Listener, Pool, Member, and Health Monitor can exist independent of a
Load Balancer. The Load Balancer is the entity that will contain the
information about w
10 matches
Mail list logo
