+1 to QUEUED status.
On Fri, Jul 4, 2014 at 5:27 PM, Brandon Logan brandon.lo...@rackspace.com
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
On Jul 4, 2014, at 5:27 PM, Brandon Logan brandon.lo...@rackspace.com 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
Hi,
For logical objects that were deleted but the backend did not execute on, there
is a PENDING_DELETE state.
So currently there is PENDING_CREATE -- CREATE, PENDING_UPDATE--UPDATE and
PENDING_DELETE--object is removed from the database.
If an error occurred that the object is in ERROR state.
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/id but can
I'll +1 UNBOUND or DEFERRED status. QUEUED does have a kind of implication
that it will be provisioned without any further action whereas UNBOUND or
DEFERRED imply that another action must take place for it to actually be
provisioned.
Thanks,
Brandon
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 implement afterwards.
Thanks,
Brandon
On Thu, 2014-07-03 at 23:02
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
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,
+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
Hi Jorge,
+1 for QUEUED and DETACHED
I would suggest to make the time how long we keep entities in DELETED state
configurable. We use something like 30 days, too, but we have made it
configurable to adapt to changes...
German
-Original Message-
From: Jorge Miramontes
10 matches
Mail list logo
