[openstack-dev] [FEMDC] meetings suspended until further notice

[lebre . adrien]

Dear all,

Following the exchanges we had during the Vancouver summit, in particular the 
non-sense to maintain/animate two groups targeting similar challenges (ie., the 
FEMDC SIG [1] and the new Edge Computing Working group [2]), FEMDC meetings are 
suspended until further notice.  

If you are interested by Edge Computing discussions, please see information 
available on the new edge wiki page [2]. 

Thanks
ad_ri3n_

[1]https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds
[2]https://wiki.openstack.org/wiki/Edge_Computing_Group

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-sigs] [SIG][Edge-computing][FEMDC] Wed. 16 May - FEMDC IRC Meeting 15:00 UTC

[lebre . adrien]

s/#edge-computing-irc/#edge-computing-group

Sorry for the typo. 
The meeting starts now. 

ad_ri3n_
- Mail original -
> De: "Dimitri Pertin" 
> À: openstack-dev@lists.openstack.org
> Cc: openstack-s...@lists.openstack.org, edge-comput...@lists.openstack.org
> Envoyé: Mardi 15 Mai 2018 17:16:22
> Objet: [Openstack-sigs] [SIG][Edge-computing][openstack-dev][FEMDC] Wed. 16 
> May - FEMDC IRC Meeting 15:00 UTC
> 
> Dear all,
> 
> Here is a gentle reminder regarding the FEMDC meeting that was
> postponed
> from last week to tomorrow: May, the 16th at 15:00 UTC.
> 
> As a consequence, the meeting will be held on #edge-computing-irc
> 
> This meeting will focus on the preparation of the Vancouver summit
> (presentations, F2F sessions, ...). You can already check and fill
> this
> pad with you wishes/ideas:
> https://etherpad.openstack.org/p/FEMDC_Vancouver
> 
> As usually, a draft of the agenda is available at line 550 and you
> are
> very welcome to add any item:
> https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018
> 
> Best regards,
> 
> Dimitri
> 
> 
> 
>  Forwarded Message 
> Subject: [Edge-computing] [FEMDC] IRC meeting postponed to next
> Wednesday
> Date: Wed, 9 May 2018 15:50:45 +0200 (CEST)
> From: lebre.adr...@free.fr
> To: OpenStack Development Mailing List (not for usage questions)
> ,
> openstack-s...@lists.openstack.org,
> edge-comput...@lists.openstack.org
> 
> Dear all,
> Neither Paul-Andre nor me can chair the meeting today so we propose
> to
> postpone it for one week. The agenda will be delivered soon but you
> can
> consider that next meeting will focus on the preparation of the
> Vancouver summit (presentations, F2F meetings...).
> Best regards, ad_ri3n_
> 
> ___
> Edge-computing mailing list
> edge-comput...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> ___
> openstack-sigs mailing list
> openstack-s...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] IRC meeting postponed to next Wednesday

[lebre . adrien]

Dear all, 

Neither Paul-Andre nor me can chair the meeting today so we propose to postpone 
it for one week. 
The agenda will be delivered soon but you can consider that next meeting will 
focus on the preparation of the Vancouver summit (presentations, F2F 
meetings...). 

Best regards, 
ad_ri3n_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] Brainstorming regarding the Vancouver Forum

[lebre . adrien]

Hi all, 

I just created an FEMDC etherpad following the Melvin's email regarding the 
next Forum in Vancouver. 
Please do not hesitate to propose ideas for sessions at the forum : 
https://wiki.openstack.org/wiki/Forum/Vancouver2018


++
Ad_ri3n_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] no meeting this week

[lebre . adrien]

Hi all, 

Most of us are attending the PTG.  
Next meeting should be held on March, the 14th.

ad_ri3n_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] A first step to the gap analysis of the OpenStack code base

[lebre . adrien]

Dear all, 

Following our last exchanges, we had a few discussions regarding the OpenStack 
code base w.r.t the edge challenges. 
Our idea was (i) to identify a couple of requirements (from the simplest one, 
i.e. starting a VM at a specific location, to the most advanced one, i.e. 
interoperability issues between distinct cloud stacks) and (ii) to analyse how 
the OpenStack codebase can fulfil these requirements. 

Our exchanges have been summarised at : 
https://etherpad.openstack.org/p/edge-gap-analysis

Please feel free to comment/complete it. 

Best regards,
On behalf of the FEMDC SiG. 
ad_ri3n_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] Wed. 3 Jan - IRC Meeting Cancelled - Next meeting Wed.17.

[lebre . adrien]

Dear all, 

Due to the Christmas/new year period, the meeting is cancelled. 
Next meeting is scheduled on Wed, the 17th. 

ad_ri3n_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC][EDGE] PTG preparation

[lebre . adrien]

Dear all, 

a few persons have put their name in the edge etherpad, thanks:  
https://etherpad.openstack.org/p/2017_edge_computing_working_sessions (see line 
21). 

in order to finalise the logistic details, I would like to make a first 
proposal for the agenda: 

* Monday afternoon - internal discussion with interested people
- The goal is to prepare/finalize the points we would like to discuss with 
core-devs of other projects (in order to ensure  a fruitful exchanges with 
core-developers). 
* Tuesday morning - discussion with projects' core-devs 
- In order to be able to go through all the major services (i.e. keystone, 
nova, neutron, glance at least), maybe we can divide the morning into different 
sessions
* Tuesday afternoon
- A short session to identify concrete actions and define a roadmap to move 
forward. 

I copy/paste this agenda into a new etherpad: 
https://etherpad.openstack.org/p/edge-ptg-dublin

Please feel free to comment/amend it 
Merry christmas, 
ad_ri3n_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] Edge sessions during the next PTG

[lebre . adrien]

Dear all, 

As briefly discussed during the last telco around edge challenges [1], we have 
the opportunity to have sessions during the next PTG in Dublin. 
If you are interested by such sessions and you plan to attend to the PTG, 
please put your name  and questions/topic you would like to discuss at the 
bottom of [2]. 

Please remind that the PTG is a place to discuss about technical aspects (and 
have the opportunities to exchanges with core-devs of the different projects). 
The objective is to dive into details. For this aim, we would like to identify 
concrete actions we can do before the PTG in order to have fruitful exchanges. 

Best regards, 
ad_ri3n_
PS: I need to inform the foundation about number of participants and how many 
slots we would like to have. Please complete the pad [2] ASAP, thanks ;-)

[1] https://etherpad.openstack.org/p/2017_edge_computing_working_sessions
[2] https://etherpad.openstack.org/p/edge-openstack-related

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] Wed. 22 Nov - IRC Meeting 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our tomorrow meeting at 15:00 UTC 

A draft agenda is available at line 1484, you are very welcome to add any item.
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017

Best regards, 
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] No Meeting today

[lebre . adrien]

Dear all, 

Due to the summit event, our next meeting will be held on Nov, the 22nd. 

Cheers
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] IRC meeting Today 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder of the FEDMC meeting, Today at 15:00 UTC. 
The agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
1237)

Please feel free to complete it

Best,
ad_rien_
PS: Inria's members will not be able to attend our IC meeting (midterm review 
of the Discovery initiative), Paul-Andre will chair the discussion. 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] IRC meeting Today 15:00 UTC

[lebre . adrien]

Dear all, 

Back from the Opendev event on edge infrastructures, I forgot to announce our 
IC meeting, today at 15:00 UTC. 

As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
1157)
Please indicate actions that have been achieved and feel free to add items in 
the Opening discussion Section.

Best,
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] IRC meeting Tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

The agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
1059)
Please indicate actions that have been achieved and feel free to add items in 
the Opening discussion Section.

Best,
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] Meeting Cancelled - Next IRC meeting August, the 30th

[lebre . adrien]

Dear All, 


The today IRC meeting is cancelled (due to the holidays period, most of us are 
unavailable). 
Next meeting will be held on August, the 30th (agenda: TBD on the etherpad as 
usual)

Last but not the least, If you are interested by FEMDC's challenges and you are 
located close to SF, do not hesitate to attend the opendev event next 
September: http://www.opendevconf.com/schedule/


Best, 
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] IRC meeting Tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
991)
Please feel free to add items.

Best,
Ad_rien_
PS: Paul-André will chair the meeting (I'm taking some holidays ;))

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [FEMDC] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
860)
Please feel free to add items.

Best,
Adrien
PS: note that due to the vacation period, I don't know how many persons will be 
present. 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] [FEMDC] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
810)
Please feel free to add items.

Best, 
ad_rien_
PS: as you may have seen, we decided during our last meeting to switch from the 
 [MassivelyDistributed] tag to [FEMDC] (shorter and thus better ;)).

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
675)
Please feel free to add items.

Best, 
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
597)
Please feel free to add items.

Best, 
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master

[lebre . adrien]

- Mail original -
> De: "Curtis" 
> À: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Cc: openst...@lists.openstack.org
> Envoyé: Vendredi 19 Mai 2017 01:43:39
> Objet: Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master
> 
> On Thu, May 18, 2017 at 4:13 PM, Adrian Turjak
>  wrote:
> > Hello fellow OpenStackers,
> >
> > For the last while I've been looking at options for multi-region
> > multi-master Keystone, as well as multi-master for other services
> > I've
> > been developing and one thing that always came up was there aren't
> > many
> > truly good options for a true multi-master backend. Recently I've
> > been
> > looking at Cockroachdb and while I haven't had the chance to do any
> > testing I'm curious if anyone else has looked into it. It sounds
> > like
> > the perfect solution, and if it can be proved to be stable enough
> > it
> > could solve a lot of problems.
> >
> > So, specifically in the realm of Keystone, since we are using
> > sqlalchemy
> > we already have Postgresql support, and since Cockroachdb does talk
> > Postgres it shouldn't be too hard to back Keystone with it. At that
> > stage you have a Keystone DB that could be multi-region,
> > multi-master,
> > consistent, and mostly impervious to disaster. Is that not the holy
> > grail for a service like Keystone? Combine that with fernet tokens
> > and
> > suddenly Keystone becomes a service you can't really kill, and can
> > mostly forget about.
> >
> > I'm welcome to being called mad, but I am curious if anyone has
> > looked
> > at this. I'm likely to do some tests at some stage regarding this,
> > because I'm hoping this is the solution I've been hoping to find
> > for
> > quite a long time.
> 
> I was going to take a look at this a bit myself, just try it out. I
> can't completely speak for the Fog/Edge/Massively Distributed working
> group in OpenStack, but I feel like this might be something they look
> into.
> 

Thanks Curtis for highlighting this. 

Indeed, among the actions we defined during our F2F meeting in Boston, one is 
to investigate the feasibility of using cockroachDB as the backend. We gave 
really preliminary investigations and identify several aspects that we should 
consider (dependence w-r-t postgres, maturity of cockroach code,...)

For your information, we did a PoC one year ago to show that it is possible to 
use a Non SQL backend (i.e Redis in our case) instead of the historical MySQL 
backends. Our goal was to investigate a solution to distribute the storage 
backends accros several nodes/sites. Although it was ``just'' a PoC (i.e., the 
quality of the code was definitely improvable), it demonstrated that using a 
non-SQL backend can make sense (for more information see [1] [2]). Among the 
remarks we got, the fact of loosing the SQL API seemed to be an issue. 

Using new SQL systems such as CockRoach can solve this issue and that's why we 
want to study how this can be done (1./ identify the effort in terms of 
development, 2./ find a way to evaluate performance pros/cons 3./ do the job)

Among the different systems (cockroach, vitess, ...), the important point from 
the FEMDC working group [3] is the fact that we do not want to have centralized 
service. From what I learnt by browsing a few pages of the Vitess website, the 
architecture does not satisfy this aspect. 

In any case, we need to spend more times on these questions before having 
enough materials to get valuable answers.
In others words, if you are interested to deal with such questions, do not 
hesitate to take part in our IRC meetings and follow the mailing list.

Best, 
Ad_rien_


[1] https://hal.inria.fr/hal-01273427/
[2] https://www.openstack.org/summit/austin-2016/summit-schedule/events/7342
[3] https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds


> For standard multi-site I don't know how much it would help, say if
> you only had a couple or three clouds, but more than that maybe this
> starts to make sense. Also running Galera has gotten easier but still
> not that easy.
> 
> I had thought that the OpenStack community was deprecating Postgres
> support though, so that could make things a bit harder here (I might
> be wrong about this).
> 
> Thanks,
> Curtis.
> 
> >
> > Further reading:
> > https://www.cockroachlabs.com/
> > https://github.com/cockroachdb/cockroach
> > https://www.cockroachlabs.com/docs/build-a-python-app-with-cockroachdb-sqlalchemy.html
> >
> > Cheers,
> > - Adrian Turjak
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> --
> Blog: serverascode.com
> 
> 

Re: [openstack-dev] [MassivelyDistributed] Fog / Edge / Massively Distributed Cloud (FEMDC)

[lebre . adrien]

Dear all, Dear Edgar, 

Unless I am mistaken, I didn't see any comments regarding my email. 
I would like to know whether there should be some follow-up actions/messages or 
if the FEMDC Working Group is well established in the OpenStack landscape? 

Thanks, 
Ad_rien_

- Mail original -
> De: "lebre adrien" <lebre.adr...@free.fr>
> À: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org>
> Cc: "Shilla Saebi" <shilla.sa...@gmail.com>, "OpenStack Operators" 
> <openstack-operat...@lists.openstack.org>,
> openst...@lists.openstack.org
> Envoyé: Lundi 8 Mai 2017 20:16:57
> Objet: Re: [openstack-dev] [MassivelyDistributed] Fog / Edge / Massively 
> Distributed Cloud Sessions during the summit
> 
> Dear Edgar,
> 
> As indicated into the WG chairs' session pad [1], the WG was
> previously entitled ``Massively Distributed Cloud''.
> The description appears on the WG wiki page [2] (and I sent an email
> to the user ML a few months ago to ask for the official creation
> [3]).
> 
> After exchanging with the OpenStack foundation folks recently, they
> suggested us to rename the Massively Distributed Clouds WG as the
> Fog/Edge/Massively Distributed Clouds WG.
> The old wiki page [4] refers the new one [5].
> 
> Please let me know whether I miss something (I can update [2] to
> reflect the new name)
> ad_rien_
> 
> [1]
> https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
> [2]
> https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups_and_Teams
> [3]
> http://lists.openstack.org/pipermail/user-committee/2016-September/001232.html
> [4] https://wiki.openstack.org/wiki/Massively_Distributed_Clouds
> [5]
> https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds
> 
> 
> - Mail original -
> > De: "Edgar Magana" <edgar.mag...@workday.com>
> > À: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev@lists.openstack.org>, "OpenStack
> > Operators" <openstack-operat...@lists.openstack.org>,
> > openst...@lists.openstack.org
> > Cc: "Shilla Saebi" <shilla.sa...@gmail.com>
> > Envoyé: Lundi 8 Mai 2017 18:25:12
> > Objet: Re: [openstack-dev] [MassivelyDistributed] Fog / Edge /
> > Massively Distributed Cloud Sessions during the summit
> > 
> > Hello,
> > 
> > In behalf of the User Community I would like to understand if this
> > is
> > considering officially to request to create the Working Group. I
> > could have missed another email request the inclusion but if not, I
> > would like to discuss the goals and objective from the WG. The User
> > Committee will be glad to helping you out if anything needed.
> > 
> > I am cc the rest of the UC members.
> > 
> > Thanks,
> > 
> > Edgar
> > 
> > On 5/5/17, 1:16 PM, "lebre.adr...@free.fr" <lebre.adr...@free.fr>
> > wrote:
> > 
> > Dear all,
> > 
> > A brief email to inform you about our schedule next week in
> > Boston.
> > 
> > In addition to interesting presentations that will deal with
> > Fog/Edge/Massively Distributed Clouds challenges [1], I would
> > like to highlight two important sessions:
> > 
> > * A new Birds of a Feather session ``OpenStack on the Edge'' is
> > now scheduled on Tuesday afternoon [2].
> > This will be the primary call to action covered by Jonathan
> > Bryce
> > during Monday's keynote about Edge Computing.
> > After introducing the goal of the WG, I will give the floor to
> > participants to share their use-case (3/4 min for each
> > presentation)
> > The Foundation has personally invited four large users that are
> > planning for fog/edge computing.
> > This will guide the WG for the future and hopefully get more
> > contributors involved.
> > Moreover, many of the Foundation staff already planned to
> > attend
> > and talk about the in-planning-phase OpenDev event and get
> > input.
> > The etherpad for this session is available at [3].
> > 
> > * Our regular face-to-face meeting for current and new members
> > to
> > discuss next cycle plans is still scheduled on Wednesday
> > afternoon [5]
> > The etherpad for this session is available at [5]
> > 
> > I encourage all of you to attend both sessions.
> > See you in Boston and h

Re: [openstack-dev] [MassivelyDistributed] Fog / Edge / Massively Distributed Cloud Sessions during the summit

[lebre . adrien]

Dear Edgar, 

As indicated into the WG chairs' session pad [1], the WG was previously 
entitled ``Massively Distributed Cloud''. 
The description appears on the WG wiki page [2] (and I sent an email to the 
user ML a few months ago to ask for the official creation [3]). 

After exchanging with the OpenStack foundation folks recently, they suggested 
us to rename the Massively Distributed Clouds WG as the Fog/Edge/Massively 
Distributed Clouds WG. 
The old wiki page [4] refers the new one [5]. 

Please let me know whether I miss something (I can update [2] to reflect the 
new name)
ad_rien_

[1] 
https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
[2] 
https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups_and_Teams
 
[3] 
http://lists.openstack.org/pipermail/user-committee/2016-September/001232.html
[4] https://wiki.openstack.org/wiki/Massively_Distributed_Clouds
[5] https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds


- Mail original -
> De: "Edgar Magana" 
> À: "OpenStack Development Mailing List (not for usage questions)" 
> , "OpenStack
> Operators" , 
> openst...@lists.openstack.org
> Cc: "Shilla Saebi" 
> Envoyé: Lundi 8 Mai 2017 18:25:12
> Objet: Re: [openstack-dev] [MassivelyDistributed] Fog / Edge / Massively 
> Distributed Cloud Sessions during the summit
> 
> Hello,
> 
> In behalf of the User Community I would like to understand if this is
> considering officially to request to create the Working Group. I
> could have missed another email request the inclusion but if not, I
> would like to discuss the goals and objective from the WG. The User
> Committee will be glad to helping you out if anything needed.
> 
> I am cc the rest of the UC members.
> 
> Thanks,
> 
> Edgar
> 
> On 5/5/17, 1:16 PM, "lebre.adr...@free.fr" 
> wrote:
> 
> Dear all,
> 
> A brief email to inform you about our schedule next week in
> Boston.
> 
> In addition to interesting presentations that will deal with
> Fog/Edge/Massively Distributed Clouds challenges [1], I would
> like to highlight two important sessions:
> 
> * A new Birds of a Feather session ``OpenStack on the Edge'' is
> now scheduled on Tuesday afternoon [2].
> This will be the primary call to action covered by Jonathan Bryce
> during Monday's keynote about Edge Computing.
> After introducing the goal of the WG, I will give the floor to
> participants to share their use-case (3/4 min for each
> presentation)
> The Foundation has personally invited four large users that are
> planning for fog/edge computing.
> This will guide the WG for the future and hopefully get more
> contributors involved.
> Moreover, many of the Foundation staff already planned to attend
> and talk about the in-planning-phase OpenDev event and get
> input.
> The etherpad for this session is available at [3].
> 
> * Our regular face-to-face meeting for current and new members to
> discuss next cycle plans is still scheduled on Wednesday
> afternoon [5]
> The etherpad for this session is available at [5]
> 
> I encourage all of you to attend both sessions.
> See you in Boston and have a safe trip
> ad_rien_
> 
> [1]
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openstack.org_summit_boston-2D2017_summit-2Dschedule_global-2Dsearch-3Ft-3Dedge=DwIGaQ=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=OHBOWu_IZimaHf_g66AuXvYldFF594SpFk35-sbkZ6g=qez9zHbrE7PfeS8vjgS2nql6xeYGg5heiAnBNMCy5os=
> [2]
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openstack.org_summit_boston-2D2017_summit-2Dschedule_events_18988_openstack-2Don-2Dthe-2Dedge-2Dfogedgemassively-2Ddistributed-2Dclouds-2Dbirds-2Dof-2Da-2Dfeather=DwIGaQ=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=OHBOWu_IZimaHf_g66AuXvYldFF594SpFk35-sbkZ6g=fnH2yZ09stEM5L-sOWuq79x_fySLwPOZu308ue7TmCU=
> [3]
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_BOS-2DUC-2Dbrainstorming-2DMassivelyDistributed-2DFog-2DEdge=DwIGaQ=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=OHBOWu_IZimaHf_g66AuXvYldFF594SpFk35-sbkZ6g=vJ_TxPslQDoJoV7e_KBxSwyBxhkTAiHbDtVhqsLrZIU=
> [4]
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.openstack.org_summit_boston-2D2017_summit-2Dschedule_events_18671_fogedgemassively-2Ddistributed-2Dclouds-2Dworking-2Dgroup=DwIGaQ=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ=OHBOWu_IZimaHf_g66AuXvYldFF594SpFk35-sbkZ6g=TgruXx4CSs5xxZKdZF151lxc_EpYduii1UzYfZ7Vvbk=
> [5]
> 
> 

[openstack-dev] [MassivelyDistributed] Fog / Edge / Massively Distributed Cloud Sessions during the summit

[lebre . adrien]

Dear all, 

A brief email to inform you about our schedule next week in Boston. 

In addition to interesting presentations that will deal with Fog/Edge/Massively 
Distributed Clouds challenges [1], I would like to highlight two important 
sessions: 

* A new Birds of a Feather session ``OpenStack on the Edge'' is now scheduled 
on Tuesday afternoon [2]. 
This will be the primary call to action covered by Jonathan Bryce during 
Monday's keynote about Edge Computing.
After introducing the goal of the WG, I will give the floor to participants to 
share their use-case (3/4 min for each presentation)
The Foundation has personally invited four large users that are planning for 
fog/edge computing.
This will guide the WG for the future and hopefully get more contributors 
involved.
Moreover, many of the Foundation staff already planned to attend and talk about 
the in-planning-phase OpenDev event and get input. 
The etherpad for this session is available at [3].

* Our regular face-to-face meeting for current and new members to discuss next 
cycle plans is still scheduled on Wednesday afternoon [5]
The etherpad for this session is available at [5]

I encourage all of you to attend both sessions.
See you in Boston and have a safe trip
ad_rien_

[1] 
https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?t=edge
 
[2] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18988/openstack-on-the-edge-fogedgemassively-distributed-clouds-birds-of-a-feather
[3] 
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge
[4] 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18671/fogedgemassively-distributed-clouds-working-group
[5] https://etherpad.openstack.org/p/Massively_distributed_wg_boston_summit
https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [architecture] Arch-WG, we hardly knew ye..

[lebre . adrien]

Dear Clint, Dear all, 

It is indeed unfortunate that the WG ends.

From our side (Inria folks from the Discovery initiative [1]), we had planned 
to join the effort after the Boston Summit as we are currently addressing two 
points that are/were closely related to the Arch WG (at least from our 
understanding): 

* We have been working during this last cycle on the consolidation of the EnOS 
solution [2] (in particular with advice from the performance team). 
EnOS aims to perform OpenStack Performance analyses/profiling.  It is built on 
top of Kolla and integrates Rally and Shaker and more recently  OSProfiler.
We are currently conducting preliminary experiments to draw, in an automatic 
manner, sequence diagrams such as 
https://docs.openstack.org/ops-guide/_images/provision-an-instance.png
We hope it will help our community to understand better the OpenStack 
architecture as well as the interactions between the different services, in 
particular it would help us to follow changes between cycles. 

* We started a discussion regarding the oslo.messaging driver [3]. 
Our goal is, first,  to make a qualitative analysis of AMQP messages (i.e. we 
would like to understand the different AMQP exchanges better) and try to 
identify possible improvements. 
Second, we will do performance analysis of the rabbitMQ under different 
scenarios and, according to gathered results, we will conduct additional 
experiments with alternatives solutions (ZMQ, Qpid, ...)
Please note that this is a preliminary discussion, so we just exchanged between 
a few folks from the Massively Distributed WG. We proposed a session to the 
forum [4] with the goal of opening the discussion more generally to the 
community. 

We are convinced of the relevance of a WG such as the Architecture one, but as 
you probably already know, it is difficult for most of us to join different 
meetings several times per week, and thus rather difficult to gather efforts 
that are done in other WGs. I don't know whether and how we can improve this 
solution but it would make sense. 

In any case,  thanks for giving a first try. 
Ad_rien_ 

[1]: http://beyondtheclouds.github.io
[2]: https://enos.readthedocs.io/en/latest/
[3]: https://etherpad.openstack.org/p/oslo_messaging_discussion 
[4]: http://forumtopics.openstack.org/cfp/details/62

- Mail original -
> De: "Clint Byrum" 
> À: "openstack-dev" 
> Envoyé: Jeudi 6 Avril 2017 19:53:17
> Objet: [openstack-dev] [architecture] Arch-WG, we hardly knew ye..
> 
> I'm going to be blunt. I'm folding the Architecture Working Group
> immediately following our meeting today at 2000 UTC. We'll be using
> the
> time to discuss continuity of the base-services proposal, and any
> other
> draw-down necessary. After that our meetings will cease.
> 
> I had high hopes for the arch-wg, with so many joining us to discuss
> things in Atlanta. But ultimately, we remain a very small group with
> very limited resources, and so I don't think it's the best use of our
> time to continue chasing the arch-wg.
> 
> Thanks everyone for your contributions. See you in the trenches.
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Openstack-operators] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
378)
Please feel free to add items.

Best, 
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
251)
Please feel free to add items.

Best, 
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
185)
Please feel free to add items to the agenda.

Best, 
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

A gentle reminder for our meeting tomorrow. 
As usual, the agenda is available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
136)
Please feel free to add items to the agenda.

Best, 
Ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] Next meeting - Tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

Let me remind you that Massively Distributed Clouds WG meeting is scheduled 
tomorrow afternoon (15:00 UTC time)
Agenda is available at :  
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017(line 
23). 
Feel free to complete it. 

All the best for 2017!
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] Next IRC meeting - Jan 4 2017

[lebre . adrien]

Dear all, 

Due to the vacation period, I propose to cancel our meeting this week. 
The next meeting will be held on Jan, the 4th. 

Season's greetings, 
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC meeting tomorrow 15:00 UTC

[lebre . adrien]

Dear all, 

Let me remind you that Massively Distributed Clouds WG meeting is scheduled 
tomorrow afternoon (15:00 UTC time)
Agenda is available at :  
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2016(line 
77). 
Feel free to complete it. 

Best regards, 
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

[lebre . adrien]

Hi all, 

Agenda available at: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2016
Feel free to add items to the agenda. 

++
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting - Timeslot - 15 UTC Wednesday (odd week)

[lebre . adrien]

Thanks Thierry 

@all: 
Massively distributed IRC meetings every Wednesday (odd week) at 15:00 UTC
The first official meeting will be on Wednesday November, the 23rd. 
The agenda is available at  
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2016

++
ad_rien_

- Mail original -
> De: "Thierry Carrez" 
> À: openstack-dev@lists.openstack.org, openstack-operat...@lists.openstack.org
> Envoyé: Mercredi 9 Novembre 2016 17:31:13
> Objet: Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting - 
> Timeslot ?
> 
> Thierry Carrez wrote:
> > lebre.adr...@free.fr wrote:
> >> After Thierry's cleaning, the possibilities are the following
> >> ones:
> >>
> >> Wednesday 14 UTC (odd week)
> >> Wednesday 17 UTC
> >> Thursday 14 UTC (odd week)
> >> Thursday 16 UTC (even week)
> >> Thursday 17 UTC (even week)
> > 
> > Thursday 15 UTC is also an option.
> > 
> > Also note that Thursday 14 UTC is currently taken. Trying to free
> > up the
> > slot with https://review.openstack.org/#/c/395509 but they may want
> > to
> > keep it.
> 
> A slot just opened for Wednesday 15 UTC, so I revived your original
> proposal[1]. If you're still interested in that one let me know and
> I'll
> approve the change.
> 
> https://review.openstack.org/#/c/393899
> 
> --
> Thierry Carrez (ttx)
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting - Timeslot ?

[lebre . adrien]

Dear all 


After Thierry's cleaning, the possibilities are the following ones: 

Wednesday 14 UTC (odd week)
Wednesday 17 UTC 
Thursday 14 UTC (odd week)
Thursday 16 UTC (even week)
Thursday 17 UTC (even week)

Please add +1 for the slot that is the most convenient from your side. 
I would appreciate to book it ASAP. 

Thanks
ad_rien_
- Mail original -
> De: "Ken Giusti" <kgiu...@gmail.com>
> À: "lebre adrien" <lebre.adr...@free.fr>
> Envoyé: Lundi 7 Novembre 2016 20:00:35
> Objet: Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting
> 
> Wed 17:00 UTC works for me.
> 
> On Mon, Nov 7, 2016 at 11:52 AM,  <lebre.adr...@free.fr> wrote:
> > Dear all,
> >
> > We are still looking for an irc channel for our meeting:
> > https://review.openstack.org/#/c/393899
> > There is no available channels for the slot we selected during our
> > face-to-face meeting in Barcelona.
> >
> > If I'm correct, we have two possibilities:
> > - Determine another slot: the first available slot on Wednesday is
> > at 17:00 UTC.
> > - Ask for the creation of a new IRC channel dedicated to our WG:
> > something line #openstack-massively-distributed
> >
> > Please let me ASAP know whether the first solution is feasible, if
> > not I should see with the Infra team whether we can register the
> > new IRC by Wednesday.
> >
> > Thanks in advance,
> > ad_rien_
> > https://wiki.openstack.org/wiki/Massively_Distributed_Clouds
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> --
> Ken Giusti  (kgiu...@gmail.com)
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] IRC Meeting postponed

[lebre . adrien]

Dear all, 

We are still looking for a final slot for our bi-weekly IRC meeting and thus we 
have to postpone our first meeting to a date to be determined (hopefully next 
week, i.e. Wednesday Nov the 16th).

I will come back to you with the final time as soon as possible. 

Meanwhile, you can give a look to the agenda (proposal) for this first meeting: 
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2016

Comments/remarks welcome
Best regards, 
ad_rien_

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] bi-weekly meeting

[lebre . adrien]

Dear all, 

We are still looking for an irc channel for our meeting: 
https://review.openstack.org/#/c/393899
There is no available channels for the slot we selected during our face-to-face 
meeting in Barcelona. 

If I'm correct, we have two possibilities: 
- Determine another slot: the first available slot on Wednesday is at 17:00 UTC.
- Ask for the creation of a new IRC channel dedicated to our WG: something line 
#openstack-massively-distributed

Please let me ASAP know whether the first solution is feasible, if not I should 
see with the Infra team whether we can register the new IRC by Wednesday. 

Thanks in advance, 
ad_rien_ 
https://wiki.openstack.org/wiki/Massively_Distributed_Clouds

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Massively Distributed] Working sessions in Barcelona

[lebre . adrien]

Dear all

The Massively Distributed Cloud Working Group [1] will meet on Thursday morning 
during the next summit in Barcelona. 
We have three slots. The current proposal is to discuss distributed 
clouds/Fog/Edge use-cases and requirements during the two first ones and to use 
the last one to define concrete actions for the Ocata cycle. 

If you are interested by taking part to the exchanges, please give a look at 
[2] and do not hesitate to complete/amend the agenda proposal. 

Thanks,  
Ad_rien_ 

[1] https://wiki.openstack.org/wiki/Massively_Distributed_Clouds
[2] 
https://etherpad.openstack.org/p/massively_distribute-barcelona_working_sessions

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

[lebre . adrien]

May I suggest to open one (or more) thread(s) with the correct subject(s)? 

There are at least three points discussed here: 

- one related to the proposal of the Massively distributed group
- one related to the Architecture WG with the communication issue between 
services (RPC+Rabbit MQ, REST API..)
- one that mainly focuses on TriCircle. 

While all of them are interesting it is a bit tedious to follow them in one 
large thread.

Regarding the Massively distributed WG (which was the initial topic ;)), I 
replied to some comments that have been done in the pad and I added a new 
action to discuss the single vs multi-endpoint questions. 

Finally regarding the comparison between proposal (the link that has been added 
at the end), I think it is a good idea but that should be done after (or at 
least meanwhile) analyzing the current OpenStack ecosystem. As it has been 
written in some comments of the TriCircle Big Tent application, it is  
important to first identify pro/cons of the federation proposal before we go 
ahead holus-bolus.

My two cents
Ad_rien_ 

- Mail original -
> De: "joehuang" 
> À: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Envoyé: Jeudi 1 Septembre 2016 11:18:17
> Objet: Re: [openstack-dev] [all][massively 
> distributed][architecture]Coordination between actions/WGs
> 
> > What is the REST API for tricircle?
> > When looking at the github I see:
> > ''Documentation: TBD''
> > Getting a feel for its REST API would really be helpful in
> > determine how
> > much of a proxy/request router it is vs being an actual API. I
> > don't
> > really want/like a proxy/request router (if that wasn't obvious,
> > ha).
> 
> For Nova API-GW/Cinder API-GW, Nova API/Cinder API will be accepted
> and forwarded.
> For Neutron with Tricircle Neutron plugin in Tricircle, it's Neutron
> API,
> just like any other Neutron plugin, doesn't change Neutron API.
> 
> Tricircle reuse tempest test cases to ensure the API accepted kept
> consistent
> with Nova/Cinder/Neutron. So no special documentation for these
> APIs(if we
> provide, documentation inconsistency will be introduced)
> 
> Except that, Tricircle Admin API provides its own API to manage
> bottom
> OpenStack instance, the documentation is in review:
> https://review.openstack.org/#/c/356291/
> 
> > Looking at say:
> > https://github.com/openstack/tricircle/blob/master/tricircle/nova_apigw/controllers/server.py
> > That doesn't inspire me so much, since that appears to be more of a
> > fork/join across many different clients, and creating a nova like
> > API
> > out of the joined results of those clients (which feels sort of
> > ummm,
> > wrong). This is where I start to wonder about what the right API is
> > here, and trying to map 1 `create_server` top-level API onto M
> > child
> > calls feels a little off (because that mapping will likely never be
> > correct due to the nature of the child clouds, ie u have to assume
> > a
> > very strict homogenous nature to even get close to this working).
> 
> > Where there other alternative ways of doing this that were
> > discussed?
> 
> > Perhaps even a new API that doesn't try to 1:1 map onto child
> > calls,
> > something along the line of make an API that more directly suits
> > what
> > this project is trying to do (vs trying to completely hide that
> > there M
> > child calls being made underneath).
> 
> > I get the idea of becoming a uber-openstack-API and trying to unify
> > X
> > other other openstacks under that API with this uber-API but it
> > just
> > feels like the wrong way to tackle this.
> 
> > -Josh
> 
> This is an interesting phenomenon here: cloud operators and end users
> often asked for single endpoint for the multi-site cloud. But for
> technology guys often think multi-region mode(each region with
> separate
> endpoint) is not an issue for end user.
> During the Tricircle big-tent application
> https://review.openstack.org/#/c/338796/
> , Anne Gentle commented "Rackspace
> public cloud has had multiple endpoints for regions for years now. I
> know
> from supporting end users for years we had to document it, and
> explain it
> often, but end-users worked with it."  In another comment, "I want to
> be sure
> I'm clear that I want many of the problems solved that you mention in
> your
>  application. In my view, Tricircle has so far been a bit of an
>  isolated effort that
>  I hadn't heard of until now. Hence the amount of discussion and
>  further work
> we may need to get to the end goal, which isn't accepting another
> project but
>  making sure we clearly write down what an acceptable solution means
>  for many,
> many clouds and teams.
> 
> I can't say who is correct or not, the requirement is true or
> false(or fake?). But
> single end point for multi-site cloud provides another choice for the
> end
> user and cloud operators.
> 
> Except that, Tricircle tries to provide quota management over
> 

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

[lebre . adrien]

As promised, I just wrote a first draft at 
https://etherpad.openstack.org/p/massively-distributed_WG_description
I will try to add more content tomorrow in particular pointers towards 
articles/ETSI specifications/use-cases.

Comments/remarks welcome. 
Ad_rien_

PS: Chaoyi, your proposal for f2f sessions in Barcelona sounds good. It is 
probably a bit too ambitious for one summit because the point 3 ''Gaps in 
OpenStack'' looks to me a major action that will probably last more than just 
one summit but I think you gave the right directions !

- Mail original -
> De: "joehuang" 
> À: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Envoyé: Mercredi 31 Août 2016 08:48:01
> Objet: Re: [openstack-dev] [all][massively 
> distributed][architecture]Coordination between actions/WGs
> 
> Hello, Joshua,
> 
> According to Peter's message, "However that still leaves us with the
> need to manage a stack of servers in thousands of telephone
> exchanges, central offices or even cell-sites, running multiple work
> loads in a distributed fault tolerant manner", the number of edge
> clouds may even at thousands level.
> 
> These clouds may be disjoint, but some may need to provide
> inter-connection for the tenant's network, for example, to support
> database cluster distributed in several clouds, the inter-connection
> for data replication is needed.
> 
> There are different thoughts, proposals or projects to tackle the
> challenge, architecture level discussion is necessary to see if
> these design and proposals can fulfill the demands. If there are
> lots of proposals, it's good to compare the pros. and cons, and
> which scenarios the proposal work, which scenario the proposal can't
> work very well.
> 
> So I suggest to have at least two successive dedicated design summit
> sessions to discuss about that f2f, all  thoughts, proposals or
> projects to tackle these kind of problem domain could be collected
> now,  the topics to be discussed could be as follows :
> 
>0. Scenario
>1, Use cases
>2, Requirements  in detail
>3, Gaps in OpenStack
>4, Proposal to be discussed
> 
>   Architecture level proposal discussion
>1, Proposals
>2, Pros. and Cons. comparation
>3, Challenges
>4, next step
> 
> Best Regards
> Chaoyi Huang(joehuang)
> 
> From: Joshua Harlow [harlo...@fastmail.com]
> Sent: 31 August 2016 13:13
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all][massively
> distributed][architecture]Coordination between actions/WGs
> 
> joehuang wrote:
> > Cells is a good enhancement for Nova scalability, but there are
> > some issues in deployment Cells for massively distributed edge
> > clouds:
> >
> > 1) using RPC for inter-data center communication will bring the
> > difficulty in inter-dc troubleshooting and maintenance, and some
> > critical issue in operation. No CLI or restful API or other tools
> > to manage a child cell directly. If the link between the API cell
> > and child cells is broken, then the child cell in the remote edge
> > cloud is unmanageable, no matter locally or remotely.
> >
> > 2). The challenge in security management for inter-site RPC
> > communication. Please refer to the slides[1] for the challenge 3:
> > Securing OpenStack over the Internet, Over 500 pin holes had to be
> > opened in the firewall to allow this to work – Includes ports for
> > VNC and SSH for CLIs. Using RPC in cells for edge cloud will face
> > same security challenges.
> >
> > 3)only nova supports cells. But not only Nova needs to support edge
> > clouds, Neutron, Cinder should be taken into account too. How
> > about Neutron to support service function chaining in edge clouds?
> > Using RPC? how to address challenges mentioned above? And Cinder?
> >
> > 4). Using RPC to do the production integration for hundreds of edge
> > cloud is quite challenge idea, it's basic requirements that these
> > edge clouds may be bought from multi-vendor, hardware/software or
> > both.
> >
> > That means using cells in production for massively distributed edge
> > clouds is quite bad idea. If Cells provide RESTful interface
> > between API cell and child cell, it's much more acceptable, but
> > it's still not enough, similar in Cinder, Neutron. Or just deploy
> > lightweight OpenStack instance in each edge cloud, for example,
> > one rack. The question is how to manage the large number of
> > OpenStack instance and provision service.
> >
> > [1]https://www.openstack.org/assets/presentation-media/OpenStack-2016-Austin-D-NFV-vM.pdf
> >
> > Best Regards
> > Chaoyi Huang(joehuang)
> >
> 
> Very interesting questions,
> 
> I'm starting to think that the API you want isn't really nova,
> neutron,
> or cinder at this point though. At some point it feels like the
> efforts
> you are spending in things like service chaining (there is a south
> 

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

[lebre . adrien]

- Mail original -
> De: "Andrew Laski" 
> À: openstack-dev@lists.openstack.org
> Envoyé: Mardi 30 Août 2016 15:03:35
> Objet: Re: [openstack-dev] [all][massively 
> distributed][architecture]Coordination between actions/WGs
> 
> 
> 
> On Tue, Aug 30, 2016, at 05:36 AM, lebre.adr...@free.fr wrote:
> > Dear all
> > 
> > Sorry my lack of reactivity, I 've been out for the few last days.
> > 
> > According to the different replies, I think we should enlarge the
> > discussion and not stay on the vCPE use-case, which is clearly
> > specific
> > and represents only one use-case among the ones we would like to
> > study.
> > For instance we are in touch with NRENs in France and Poland that
> > are
> > interested to deploy up to one rack in each of their largest PoP in
> > order
> > to provide a distributed IaaS platform  (for further informations
> > you can
> > give a look to the presentation we gave during the last summit [1]
> > [2]).
> > 
> > The two questions were:
> > 1./ Understand whether the fog/edge computing use case is in the
> > scope of
> > the Architecture WG and if not, do we need a massively distributed
> > WG?
> 
> Besides the question of which WG this might fall under is the
> question
> of how any of the work groups are going to engage with the project
> communities. There is a group of developers pushing forward on
> cellsv2
> in Nova there should be some level of engagement between them and
> whomever is discussing the fog/edge computing use case. To me it
> seems
> like there's some level of overlap between the efforts even if
> cellsv2
> is not a full solution. But whatever conversations are taking place
> about fog/edge or large scale distributed use cases seem  to be
> happening in channels that I am not aware of, and I haven't heard any
> other cells developers mention them either.
> 

I can only agree !
Actually we organised an informal exchange with Sylvain Bauza in July in order 
to get additional information regarding the Cell V2 
architecture/implementation.  From our point of view, such changes in the code 
can help us toward our ultimate goal of managing remote DCs in an efficient 
manner (i.e by mitigating for instance the inter-sites traffic). 


> So let's please find a way for people who are interested in these use
> cases to talk to the developers who are working on similar things.

What is your proposal ? any particular ideas in mind?  

Ad_rien_

> 
> 
> > 2./ How can we coordinate our actions with the ones performed in
> > the
> > Architecture WG?
> > 
> > Regarding 1./, according to the different reactions, I propose to
> > write a
> > first draft in an etherpard to present the main goal of the
> > Massively
> > distributed WG and how people interested by such discussions can
> > interact
> > (I will paste the link to the etherpad by tomorrow).
> > 
> > Regarding 2./,  I mentioned the Architecture WG because we do not
> > want to
> > develop additional software layers like Tricircle or other
> > solutions (at
> > least for the moment).
> > The goal of the WG is to conduct studies and experiments to
> > identify to
> > what extent current mechanisms can satisfy the needs of such a
> > massively
> > distributed use-cases and what are the missing elements.
> > 
> > I don't want to give to many details in the present mail in order
> > to stay
> > as consice as possible (details will be given in the proposal).
> > 
> > Best regards,
> > Adrien
> > 
> > [1] https://youtu.be/1oaNwDP661A?t=583 (please just watch the
> > use-case
> > introduction ;  the distribution of the DB  was one possible
> > revision of
> > Nova and according to the cell V2 changes it is probably now
> > deprecated).
> > [2] https://hal.inria.fr/hal-01320235
> > 
> > - Mail original -
> > > De: "Peter Willis" 
> > > À: "OpenStack Development Mailing List (not for usage questions)"
> > > 
> > > Envoyé: Mardi 30 Août 2016 11:24:00
> > > Objet: Re: [openstack-dev] [all][massively
> > > distributed][architecture]Coordination between actions/WGs
> > > 
> > > 
> > > 
> > > Colleagues,
> > > 
> > > 
> > > An interesting discussion, the only question appears to be
> > > whether
> > > vCPE is a suitable use case as the others do appear to be cloud
> > > use
> > > cases. Lots of people assume CPE == small residential devices
> > > however CPE covers a broad spectrum of appliances. Some of our
> > > customers' premises are data centres, some are HQs, some are
> > > campuses, some are branches. For residential CPE we use the
> > > Broadband Forum's CPE Wide Area Network management protocol
> > > (TR-069), which may be easier to modify to handle virtual
> > > machines/containers etc. than to get OpenStack to scale to
> > > millions
> > > of nodes. However that still leaves us with the need to manage a
> > > stack of servers in thousands of telephone exchanges, central
> > > offices or even cell-sites, running multiple work 

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

[lebre . adrien]

Dear all 

Sorry my lack of reactivity, I 've been out for the few last days.

According to the different replies, I think we should enlarge the discussion 
and not stay on the vCPE use-case, which is clearly specific and represents 
only one use-case among the ones we would like to study. For instance we are in 
touch with NRENs in France and Poland that are interested to deploy up to one 
rack in each of their largest PoP in order to provide a distributed IaaS 
platform  (for further informations you can give a look to the presentation we 
gave during the last summit [1] [2]).

The two questions were: 
1./ Understand whether the fog/edge computing use case is in the scope of the 
Architecture WG and if not, do we need a massively distributed WG? 
2./ How can we coordinate our actions with the ones performed in the 
Architecture WG? 

Regarding 1./, according to the different reactions, I propose to write a first 
draft in an etherpard to present the main goal of the Massively distributed WG 
and how people interested by such discussions can interact (I will paste the 
link to the etherpad by tomorrow). 

Regarding 2./,  I mentioned the Architecture WG because we do not want to 
develop additional software layers like Tricircle or other solutions (at least 
for the moment). 
The goal of the WG is to conduct studies and experiments to identify to what 
extent current mechanisms can satisfy the needs of such a massively distributed 
use-cases and what are the missing elements.  

I don't want to give to many details in the present mail in order to stay as 
consice as possible (details will be given in the proposal).

Best regards, 
Adrien 

[1] https://youtu.be/1oaNwDP661A?t=583 (please just watch the use-case 
introduction ;  the distribution of the DB  was one possible revision of Nova 
and according to the cell V2 changes it is probably now deprecated). 
[2] https://hal.inria.fr/hal-01320235

- Mail original -
> De: "Peter Willis" 
> À: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Envoyé: Mardi 30 Août 2016 11:24:00
> Objet: Re: [openstack-dev] [all][massively 
> distributed][architecture]Coordination between actions/WGs
> 
> 
> 
> Colleagues,
> 
> 
> An interesting discussion, the only question appears to be whether
> vCPE is a suitable use case as the others do appear to be cloud use
> cases. Lots of people assume CPE == small residential devices
> however CPE covers a broad spectrum of appliances. Some of our
> customers' premises are data centres, some are HQs, some are
> campuses, some are branches. For residential CPE we use the
> Broadband Forum's CPE Wide Area Network management protocol
> (TR-069), which may be easier to modify to handle virtual
> machines/containers etc. than to get OpenStack to scale to millions
> of nodes. However that still leaves us with the need to manage a
> stack of servers in thousands of telephone exchanges, central
> offices or even cell-sites, running multiple work loads in a
> distributed fault tolerant manner.
> 
> 
> Best Regards,
> Peter.
> 
> 
> On Tue, Aug 30, 2016 at 4:48 AM, joehuang < joehu...@huawei.com >
> wrote:
> 
> 
> Hello, Jay,
> 
> > The Telco vCPE and Mobile "Edge cloud" (hint: not a cloud) use
> > cases
> 
> Do you mean Mobile Edge Computing for Mobile "Edge cloud"? If so,
> it's cloud. The introduction slides [1] can help you to learn the
> use cases quickly, there are lots of material in ETSI website[2].
> 
> [1]
> http://www.etsi.org/images/files/technologies/MEC_Introduction_slides__SDN_World_Congress_15-10-14.pdf
> [2]
> http://www.etsi.org/technologies-clusters/technologies/mobile-edge-computing
> 
> And when we talk about massively distributed cloud, vCPE is only one
> of the scenarios( now in argue - ing ), but we can't forget that
> there are other scenarios like vCDN, vEPC, vIMS, MEC, IoT etc.
> Architecture level discussion is still necessary to see if current
> design and new proposals can fulfill the demands. If there are lots
> of proposals, it's good to compare the pros. and cons, and which
> scenarios the proposal work, which scenario the proposal can't work
> very well.
> 
> ( Hope this reply in the thread :) )
> 
> Best Regards
> Chaoyi Huang(joehuang)
> 
> From: Jay Pipes [ jaypi...@gmail.com ]
> Sent: 29 August 2016 18:48
> To: openstack-dev@lists.openstack.org
> 
> 
> Subject: Re: [openstack-dev] [all][massively
> distributed][architecture]Coordination between actions/WGs
> 
> On 08/27/2016 11:16 AM, HU, BIN wrote:
> > The challenge in OpenStack is how to enable the innovation built on
> > top of OpenStack.
> 
> No, that's not the challenge for OpenStack.
> 
> That's like saying the challenge for gasoline is how to enable the
> innovation of a jet engine.
> 
> > So telco use cases is not only the innovation built on top of
> > OpenStack. Instead, telco use cases, e.g. Gluon (NFV networking),
> > 

[openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs

[lebre . adrien]

Hi Folks, 

During the last summit, we suggested to create a new working group that deals 
with the massively distributed use case:
How can OpenStack be "slightly" revised to operate Fog/Edge Computing 
infrastructures, i.e. infrastructures composed of several sites. 
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. 

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. 

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). 
Such information will enable us to better understand how and where each service 
should be deployed and whether it should be revised.  

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. 

Meanwhile, we saw during this summer the Clynt's proposal about the 
Architecture WG.

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.

The goal of this email is to : 

(i) understand whether the fog/edge computing use case is in the scope of 
the Architecture WG. 

(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).

(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)


According to the feedback, we will create dedicated wiki pages for the 
massively distributed WG. 
Remarks/comments welcome. 

Ad_rien_
Further information regarding the Fog/Edge Computing use-case we target is 
available at http://beyondtheclouds.github.io

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

[lebre . adrien]

Hi Dina, 

17:30 UTC means 19:30 in France (Summer time). 
Considering that the meeting lasts in average 30/45 min, it would be great if 
we could find a trade off a bit sooner. What's about 17:00 UTC ?

Thanks,
Adrien

- Mail original -
> De: "Dina Belova" 
> À: "OpenStack Development Mailing List" , 
> "openstack-operators"
> 
> Envoyé: Jeudi 18 Août 2016 21:35:48
> Objet: [Performance][Meeting time] Possible meeting time change: feedback 
> appreciated
> 
> 
> Hey, OpenStackers!
> 
> 
> recently I've got lots comments about current time our Performance
> Team meetings are held on. Right now we're having them 16:00 UTC on
> Tuesdays (9:00 PST) (#openstack-performance IRC channel) and this
> time slot is not that much comfortable for some of the US folks due
> to internal daily meetings.
> 
> 
> The question is: can we move our weekly meeting to 17:30 UTC (10:30
> PST)? It's late a bit for folks from Moscow (20:30), so I'd like to
> collect more feedback.
> 
> 
> Please leave your comments.
> 
> 
> Cheers,
> Dina
> 
> 
> --
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Dina Belova Senior Software Engineer
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Mirantis, Inc.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 525 Almanor Avenue, 4th Floor
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Sunnyvale, CA 94085 Phone: 650-772-8418
> Email: dbel...@mirantis.com
> www.mirantis.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Lookig for suggessions on a new module "cloudlet" in OprnStack under bigtent

[lebre . adrien]

Hi Prakash, 

Maybe you can give a look at the Massively Distributed Group that aims to 
investigate how OpenStack can address the Fog/Edge Computing use-case. The 
inaugural meeting was two days ago: 

Overview
https://etherpad.openstack.org/p/massively-distributed-clouds-overview

Austin meeting
https://etherpad.openstack.org/p/massively-distributed-clouds-inaugural-meeting

If I remind your presentation correctly, there are several connection 
opportunities. 

BR,  
Adrien

- Mail original -
> De: "prakash RAMCHANDRAN" 
> À: openstack-dev@lists.openstack.org
> Envoyé: Jeudi 28 Avril 2016 11:19:54
> Objet: [openstack-dev] Lookig for suggessions on a new module "cloudlet" in 
> OprnStack under bigtent
> 
> 
> 
> 
> Hi all,
> 
> 
> Having attempted to introduce Cloudlet API in Nova for Liberty and
> later trying to bring use case to Product Working Group (PWG) it
> appears we need volunteers and advisors who can help get us a new
> project in Openstack. Any past PTLs who can steer this efforts are
> welcome too to look at this new opportunity to lead and guide us. I
> am open to leading it but would like prople with better skills and
> experience in OpenStack to drive it.
> 
> 
> 
> Driving Cloudlet into Openstack » OpenStack Open Source Cloud
> Computing Software
> 
> 
> 
>   
> 
>   Driving Cloudlet into Openstack » OpenStack Open Source 
> Cloud
>   Computing Sof...
> 
>   
> 
> 
> I am still hopeful in meeting PWG team and let me know the etherpad
> where I can try put my request for Edge cloud or cloudlet before
> coming Friday.
> 
> 
> Thanks
> Prakash
> 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] Massively distributed Clouds Working Group - Inaugural Meeting - This afternoon

[lebre . adrien]

Dear all, 

The inaugural meeting of the Massively Distributed Working Group will be held 
this afternoon at the Hilton  (4:40pm-6:10pm  - Level 6 - Salon)
I remind you that the objective of this working group is to investigate how the 
vanilla OpenStack can support the Fog/Edge Computing use-case. Our goal is not 
to create a new projet but to discuss and propose light/incremental revisions 
to the current code.

Further information available at: 
https://etherpad.openstack.org/p/massively-distributed-clouds. 

Best regards, 
Adrien


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [MassivelyDistributed] - Massively distributed Clouds Working Group - Proposal

[lebre . adrien]

Dear all

We would like to propose the creation of a new working group to deal with the 
massively distributed cloud use-case (aka., the Fog/Edge Computing paradigm). 
The major difference w-r-t existing WGs such as the Large-Scale deployment one, 
is that we would like to address challenges related to the geo-distribution of 
resources and WANwide exchanges (one single cloud/cell but deployed across 
multiple small sites).  Concretely, we want to study how the vanilla OpenStack 
code can support this use-case while minimising the changes on the OpenStack 
internals.

Preliminary works on such an approach have been ongoing since 2014 in the 
context of the French Discovery Initiative (a joint work between Inria and 
Orange Labs): http://beyondtheclouds.github.io 
A presentation of our action as well as preliminary results will be given next 
Monday during the summit: 
https://www.openstack.org/summit/austin-2016/summit-schedule/events/7342
Finally, we opened an etherpad where you can find more information about the 
Massively Distributed working group proposal: 
https://etherpad.openstack.org/p/massively-distributed-clouds

As a starting point, we propose to have a first face-to-face meeting in Austin 
where we can finalise the scope of the WG and define a roadmap and first 
objectives.  
The session will be on Tuesday from 4:40-6:10pm  in the Hilton, Level 6, Salon 
J. 

In addition to informal discussions, we should have up to three 15 min 
presentations regarding on-going works related to such a use-case. Chaoyi Hang 
(Huawei, on the tricircle project) and Craig A. Lee (Aero, on the KeyVOMS 
proposal) already confirmed their talk.
We are waiting for a last invitation regarding the Dragonflow project. 

Last but not the least, if you have ideas regarding how we can make this 
meeting as fruitful as possible or if you would like to discuss particular 
points during this session, please go to the etherpad  to tell us who you are 
and help shape the agenda for the session. 
We look forward to meeting with you in Austin.

Mathieu and Adrien 
Beyonds the clouds, the Discovery initiative
http://beyondtheclouds.github.io

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev