Open Stack

That sounds great.

I was thinking about how conductor would start intercepting calls
on-behalf of nova-compute.

Any thoughts on that? I could almost see another message topic just for
these types of workflow calls, one that isn't connected to the db calls.

This would make sense to me since u don't want db calls backing up behind
workflow calls (and vice-versa).

Then there is the question of how the conductor manager right now is sort
of solely designed for db calls.

I was thinking there could at least be a separation of the workflow like
management into a workflow manager subclass and then a db manager subclass
for the actions there.

This way the 2 functionalities are kept separated (as they should be).

Thoughts?

On 5/1/13 10:26 AM, "John Garbutt" <john at johngarbutt.com> wrote:

>> On Mon, Apr 29, 2013 at 07:04:28PM +0100, John Garbutt wrote:
>>> - move cold migrate (and resize?) into conductor
>> I'm starting to look at this and I'll probably have a WIP soon and I'll
>>ping you for feedbacks, does it sound ok?
>Sounds good
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev