[Openstack] Propagation of account state management changes in keystone across all the services

Hi We are looking into how to best architect the propagation of account state management changes in keystone across all the services. For example, when we delete a customer domain and/or its tenants, it is currently a multi-step process with potentially many manual tasks. This is error prone

Re: [Openstack] Propagation of account state management changes in keystone across all the services

Susanne: How much synchronicity is required? Can we broadcast an rpc.cast-style event over AMQP and simply tell each component to react as it sees fit, on its own timeframe? Or does Keystone need to get an ACK from every participant before it can proceed? --Daniel Hardman Chief Solutions

Re: [Openstack] Propagation of account state management changes in keystone across all the services

On 06/25/2013 01:50 PM, Balle, Susanne wrote: Hi We are looking into how to best architect the propagation of account state management changes in keystone across all the services. For example, when we delete a customer domain and/or its tenants, it is currently a multi-step process with