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

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

Reply via email to