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, "Brandon Logan" <brandon.lo...@rackspace.com> wrote: >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 which driver to use (through provider or flavor). If >a Listener, Pool, Member, or Health Monitor is created without a link to >a Load Balancer, then what status does it have? At this point it only >exists in the database and is really just waiting to be provisioned by a >driver/backend. > >Some possibilities discussed: >A new status of QUEUED, PENDING_ACTIVE, SCHEDULED, or some other name >Entities just remain in PENDING_CREATE until provisioned by a driver >Entities just remain in ACTIVE until provisioned by a driver > >Opinions and suggestions? >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev