Hi Bartosz, one thing that is still not clear to me: In the discussion at the summit and in your updated architecture on the wiki it talks about two Heat engines, one in each region, and on-top only the dashboard. So what entity will really do the cross region orchestration? In the discussions I heard people talking about the heat client doing it. But wouldn't that duplicate functionality that is inside the engine into the client, i.e. the client would become an orchestrator itself then? Regards, Thomas Bartosz Górski <bartosz.gorski at ntti3.com> wrote on 14.11.2013 15:58:39: > From: Bartosz Górski <bartosz.gorski at ntti3.com> > To: openstack-dev at lists.openstack.org, > Date: 14.11.2013 16:05 > Subject: [openstack-dev] [Heat] Continue discussing multi-region orchestration > > Hi all, > > At summit in Hong Kong we had a design session where we discussed adding > multi-region orchestration support to Heat. During the session we had > really heated discussion and spent most of the time on explaining the > problem. I think it was really good starting point and right now more > people have better understanding for this problem. I appreciate all the > suggestions and concerns I got from you. I would like to continue this > discussion here on the mailing list. > > I updated the etherpad after the session. If I forgot about something or > wrote something that is not right feel free a please tell me about it. > > References: > [1] Blueprint: > https://wiki.openstack.org/wiki/Heat/Blueprints/Multi_Region_Support_for_Heat > [2] Etherpad: > https://etherpad.openstack.org/p/icehouse-summit-heat-multi-region-cloud > [3] Patch with POC version: https://review.openstack.org/#/c/53313/ > > > Best, > Bartosz Górski > NTTi3 > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >