<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi,<br><br>Following the previous discussions regarding approaches to make several instances of OpenStack collaborative[1], we finally decided to make a research report on the approach we initially proposed during the edge hackathon in Berlin (OSF summit 2018).<br>The document is a short article (~10 pages long)[2] that gives a rather complete overview of the approach. If you are interested to see how mutliple instances of distinct OpenStack can give the illusion of a single system you might be interested to give it a look.<br><br>A brief excerpt:<br>“We propose a novel approach that delivers any collaboration between services of distinct OpenStack once and for all. Our approach eliminates development efforts related to the brokering aspect by leveraging dynamic composition and a Domain Specific Language (DSL).<br>Using these two mechanisms, Admins/DevOps can specify, on a per-request basis, which services from which OpenStacks are required for the collaboration. This information is then interpreted to dynamical recompose services between the different OpenStacks, enabling the execution of single-, cross- or multiple-site requests without code effort.”<br><br>The main idea is, considering several OpenStacks running, to use a DSL to specify which instance of the service (i.e. on which Openstack) the user wants its request to be executed.<br>For instance, to provision a VM on a Nova in Paris using an image from a Glance in New York. You may contact the API either in NewYork or in Paris and perform the following request:<br><br>"openstack server create --image debian --scope { compute: Paris, image: New York }"<br><br>Along with the report comes a proof of concept available on GitLab[3].<br><br>Feel free to get back to us.<br><br>Cheers<br><br>[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013562.html<br>[2] https://hal.inria.fr/hal-02527366/<br>[3] https://gitlab.inria.fr/discovery/openstackoid<br><br></div><div>----<br data-mce-bogus="1"></div><div><br></div><div data-marker="__SIG_PRE__">Marie Delavergne</div></div></body></html>