<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Please, drive new multi projects requirements thru use cases of Product WG.<o:p></o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Arkady<o:p></o:p></p>
<p>-----Original Message-----<br>
From: joehuang [mailto:joehuang@huawei.com] <br>
Sent: Tuesday, August 23, 2016 9:01 PM<br>
To: OpenStack Development Mailing List (not for usage questions) ; openstack-operators
<br>
Cc: discovery-dev@inria.fr<br>
Subject: Re: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs<br>
<br>
Hello, Adrien,<br>
<br>
How about different focus for different working gruop? For example, "massively distributed" working group can focus on identifying the use cases, challenges, issues in current openstack to support such fog/edge computing scenario, and even including the use
cases/scenario from ETSI mobile edge computing (http://www.etsi.org/technologies-clusters/technologies/mobile-edge-computing, https://portal.etsi.org/portals/0/tbpages/mec/docs/mobile-edge_computing_-_introductory_technical_white_paper_v1%2018-09-14.pdf).
For "architecture" working group, how about to focus on dicsussing technology solution/proposal to address these issues/challenges?<br>
<br>
We have discussed/exchanged ideas a lot before/in/after Austin summit. As Tricircle has worked in the multisite area for several cycles, a lots of use cases/challengs/issues also have been identified, the proposal of Tricircle could be one basis to be discussed
in "arhictecture" working group, other proposals are also welcome.<br>
<br>
Best Regards<br>
Chaoyi Huang (joehuang)<br>
<br>
________________________________________<br>
From: lebre.adrien@free.fr [lebre.adrien@free.fr]<br>
Sent: 23 August 2016 18:17<br>
To: OpenStack Development Mailing List; openstack-operators<br>
Cc: discovery-dev@inria.fr<br>
Subject: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs<br>
<br>
Hi Folks,<br>
<br>
During the last summit, we suggested to create a new working group that deals with the massively distributed use case:<br>
How can OpenStack be "slightly" revised to operate Fog/Edge Computing infrastructures, i.e. infrastructures composed of several sites.<br>
The first meeting we did in Austin showed us that additional materials were mandatory to better understand the scope as well as the actions we can perform in this working group.<br>
<br>
After exchanging with different persons and institutions, we have identified several actions that we would like to achieve and that make the creation of such a working group relevant from our point of view.<br>
<br>
Among the list of possible actions, we would like to identify major scalability issues and clarify intra-site vs inter-site exchanges between the different services of OpenStack in a multi-site context (i.e. with the vanilla OpenStack code).<br>
Such information will enable us to better understand how and where each service should be deployed and whether it should be revised.<br>
<br>
We have started an action with the Performance WG with the ultimate goal to analyse how OpenStack behaves from the performance aspect as well as the interactions between the various services in such a context.<br>
<br>
Meanwhile, we saw during this summer the Clynt's proposal about the Architecture WG.<br>
<br>
Although we are very exciting about this WG (we are convinced it will be valuable for the whole community), we are wondering whether the actions we envision in the Massively distributed WG will not overlap the ones (scalability, multi-site operations ...) that
could be performed in the Archictecture WG.<br>
<br>
The goal of this email is to :<br>
<br>
(i) understand whether the fog/edge computing use case is in the scope of the Architecture WG.<br>
<br>
(ii) if not, whether it makes sense to create a working group that focus on scalability and multi-site challenges (Folks from Orange Labs and British Telecom for instance already told us that they are interesting by such a use-case).<br>
<br>
(iii) what is the best way to coordinate our efforts with the actions performed in other WGs such as the Performance and Architecture ones (e.g., actions performed/decisions taken in the Architecture WG can have impacts on the massively distributed WG and thus
drive the way we should perform actions to progress to the Fog/Edge Computing target)<br>
<br>
<br>
According to the feedback, we will create dedicated wiki pages for the massively distributed WG.<br>
Remarks/comments welcome.<br>
<br>
Ad_rien_<br>
Further information regarding the Fog/Edge Computing use-case we target is available at http://beyondtheclouds.github.io<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
</div>
</body>
</html>