Re: [openstack-dev] [Edge-computing] [FEMDC] Brainstorming regarding the Vancouver Forum

[Paul-Andre Raymond]

I have added a couple of points and links.

 
Paul-André
--
 
On 3/15/18, 9:46 AM, "lebre.adr...@free.fr"  wrote:

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_

___
Edge-computing mailing list
edge-comput...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing


__
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] [FEMDC] IRC Meeting today 15:00 UTC

[Paul-Andre Raymond]

Below is the link to the etherpad for our meeting.



On 9/27/17, 10:01 AM, "Paul-Andre Raymond" <paul-andre.raym...@b-yond.com> 
wrote:

Dear all, 

A gentle reminder for our meeting today (an hour from now). 
I believe today will be a short meeting.
Draft agenda was prepared by our friends from INRIA at   
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
1237)

Please feel free to add items.

Best, 

 
Paul-André
--
 




__
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

[Paul-Andre Raymond]

Dear all, 

A gentle reminder for our meeting today (an hour from now). 
I believe today will be a short meeting.
Draft agenda was prepared by our friends from INRIA at   
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 
1237)

Please feel free to add items.

Best, 

 
Paul-André
--
 


__
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] [FEMDC][MassivelyDistributed] Strawman proposal for message bus analysis

[Paul-Andre Raymond]

Thank you Matt,

This is very insightful. It helps.

The second link did not work for me.

In the presentation, it mentioned that the load consisted “Boot and List” 
operations through Rally. 
Did I understand well?
Were those hitting the Openstack UI?
Was keystone involved? Was it using Fernet or another sort of token?

Intuitively, I expected 
- the big driver for performance on mariadb would be authentication tokens. And 
fernet would allow to control that.
- The big driver for performance on rabbitmq would be ceilometer, and it is not 
clear from your presentation that any telemetry data hit the message queue.

Regards,

Paul-Andre



-Original Message-
From: Matthieu Simonin <matthieu.simo...@inria.fr>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Saturday, July 1, 2017 at 4:42 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman proposal 
for message bus analysis

Hi Paul-André,

This was without ceilometer. Nova + Neutron were consuming a lot of 
connections.
Some charts are available in the Barcelona presentation[1] and the 
performance docs[2].
In the latter you'll find some telemetry related tests.

[1]: 
https://www.openstack.org/assets/presentation-media/Chasing-1000-nodes-scale.pdf
[2]: https://docs.openstack.org/developer/performance-docs/

Best,

Matt

    ----- Mail original -
> De: "Paul-Andre Raymond" <paul-andre.raym...@nexius.com>
> À: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
> Envoyé: Vendredi 30 Juin 2017 18:42:04
> Objet: Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman 
proposal for message bus analysis
> 
> Hi Matthieu,
> 
> You mentioned 15000 connections with 1000 compute nodes.
> Was that mostly Nova? Was ceilometer involved?
> I would be curious to know how much AMQP traffic is Control 
related
> (e.g. spinning up VMs) vs how much is telemetry related in a 
typical
> openstack deployment.
> Do we know that?
> 
> I have also left some comments in the doc.
> 
> Paul-Andre
> 
> 
> -Original Message-
> From: Matthieu Simonin <matthieu.simo...@inria.fr>
> Reply-To: "OpenStack Development Mailing List (not for usage 
questions)"
> <openstack-dev@lists.openstack.org>
> Date: Wednesday, June 21, 2017 at 6:54 PM
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman
> proposal for  message bus analysis
> 
> Hi Ken,
> 
> Thanks for starting this !
> I've made a first pass on the epad and left some notes and 
questions
> there.
> 
> Best,
> 
> Matthieu
> - Mail original -
> > De: "Ken Giusti" <kgiu...@gmail.com>
> > À: "OpenStack Development Mailing List (not for usage 
questions)"
> > <openstack-dev@lists.openstack.org>
> > Envoyé: Mercredi 21 Juin 2017 15:23:26
> > Objet: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman
> > proposal formessage bus analysis
> > 
> > Hi All,
> > 
> > Andy and I have taken a stab at defining some test scenarios for
> > anal the
> > different message bus technologies:
> > 
> > https://etherpad.openstack.org/p/1BGhFHDIoi
> > 
> > We've started with tests for just the oslo.messaging layer to
> > analyze
> > throughput and latency as the number of message bus clients - 
and
> > the bus
> > itself - scale out.
> > 
> > The next step will be to define messaging oriented test 
scenarios
> > for an
> > openstack deployment.  We've started by enumerating a few of the
> > tools,
> > topologies, and fault conditions that need to be covered.
> > 
> > Let's use this epad as a starting poin

Re: [openstack-dev] [FEMDC] Use Cases

[Paul-Andre Raymond]

Following our discussion today, I have added a slide (see slide 11) in the 
google docs about  not underestimating the importance of networking for our use 
cases.
Specifically, to fully describe a use case, It would be useful to flesh out the 
following aspects.

The performance of a specific use case will depend specifically on how 
networking implementation is done in Edge Node.
1- Do we use Neutron or something else? (e.g. Tricircle)
2- Is networking in Edge node at L2, or is it done at L3?
3- Is there a need for encryption (between edge and central nodes)? Is there a 
performance impact (e.g. MTU)?
4- How is Control plane separated from User Plane?



This completes an action I took today.

Regards,

Paul-Andre



From: Paul-André Raymond 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, July 5, 2017 at 12:53 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [FEMDC] Use Cases

All,

I look forward to continue discussions on how to structure use cases during our 
FEMDC call today.

You will find some slides on google doc that describe my thinking.
https://docs.google.com/presentation/d/1sBczuC2Wu1d_misBmPahLPdvyhOI4QuVy129EHunuUM/edit#slide=id.g1f7f1a38ce_2_102


You will see in there that I feel a use case should include:


  1.  A Deployment Scenario (e.g. NFV or Edge or Federation)
  2.  A Service Use Case  (e.g. IOT, or Mobility or AR or …)
  3.  Openstack component distribution use case  (Regions or Cells or other)
  4.  User plane use case (e.g. Failure scenario)
  5.  Control Plane Use case (e.g. node commissioning or decommissioning)

Please let me know your comments.

Paul-Andre


__
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] Use Cases

[Paul-Andre Raymond]

All,

I look forward to continue discussions on how to structure use cases during our 
FEMDC call today.

You will find some slides on google doc that describe my thinking.
https://docs.google.com/presentation/d/1sBczuC2Wu1d_misBmPahLPdvyhOI4QuVy129EHunuUM/edit#slide=id.g1f7f1a38ce_2_102


You will see in there that I feel a use case should include:


  1.  A Deployment Scenario (e.g. NFV or Edge or Federation)
  2.  A Service Use Case  (e.g. IOT, or Mobility or AR or …)
  3.  Openstack component distribution use case  (Regions or Cells or other)
  4.  User plane use case (e.g. Failure scenario)
  5.  Control Plane Use case (e.g. node commissioning or decommissioning)

Please let me know your comments.

Paul-Andre


__
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] [FEMDC][MassivelyDistributed] Strawman proposal for message bus analysis

[Paul-Andre Raymond]

Hi Matthieu,

You mentioned 15000 connections with 1000 compute nodes.
Was that mostly Nova? Was ceilometer involved?
I would be curious to know how much AMQP traffic is Control related 
(e.g. spinning up VMs) vs how much is telemetry related in a typical openstack 
deployment.
Do we know that?

I have also left some comments in the doc.

Paul-Andre


-Original Message-
From: Matthieu Simonin 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, June 21, 2017 at 6:54 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman 
proposal formessage bus analysis

Hi Ken,

Thanks for starting this !
I've made a first pass on the epad and left some notes and questions 
there.

Best,

Matthieu
- Mail original -
> De: "Ken Giusti" 
> À: "OpenStack Development Mailing List (not for usage questions)" 

> Envoyé: Mercredi 21 Juin 2017 15:23:26
> Objet: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman 
proposal formessage bus analysis
> 
> Hi All,
> 
> Andy and I have taken a stab at defining some test scenarios for anal 
the
> different message bus technologies:
> 
> https://etherpad.openstack.org/p/1BGhFHDIoi
> 
> We've started with tests for just the oslo.messaging layer to analyze
> throughput and latency as the number of message bus clients - and the 
bus
> itself - scale out.
> 
> The next step will be to define messaging oriented test scenarios for 
an
> openstack deployment.  We've started by enumerating a few of the 
tools,
> topologies, and fault conditions that need to be covered.
> 
> Let's use this epad as a starting point for analyzing messaging - 
please
> feel free to contribute, question, and criticize :)
> 
> thanks,
> 
> 
> 
> --
> 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 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