[openstack-dev] [FEMDC][MassivelyDistributed] Strawman proposal for message bus analysis

Matthieu Simonin matthieu.simonin at inria.fr
Thu Jul 6 14:31:46 UTC 2017


----- Mail original -----
> De: "Paul-Andre Raymond" <paul-andre.raymond at nexius.com>
> À: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Envoyé: Mercredi 5 Juillet 2017 21:48:29
> Objet: Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman proposal for message bus analysis
> 
> Thank you Matt,
> 
> This is very insightful. It helps.
> 
> The second link did not work for me.

Oh yeah that's probably because of the on-going doc migration[1].

[1]: http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html

> 
> In the presentation, it mentioned that the load consisted “Boot and List”
> operations through Rally.
> Did I understand well?

Yes.

> Were those hitting the Openstack UI?

Rally benchmarks put loads the various APIs and gather some metrics about 
the execution (time, failures...)

> Was keystone involved? Was it using Fernet or another sort of token?

Keystone is indeed involved and the token was at that time UUID 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.

Telemetry wasn't set up, I guess this would have killed Rabbit earlier in the tests.
The split between notification and RPC messaging is interesting in this area.

Bye,

Matt

> 
> Regards,
> 
> Paul-Andre
> 
> 
> 
> -----Original Message-----
> From: Matthieu Simonin <matthieu.simonin at inria.fr>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Date: Saturday, July 1, 2017 at 4:42 AM
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at 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.raymond at nexius.com>
>     > À: "OpenStack Development Mailing List (not for usage questions)"
>     > <openstack-dev at 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.simonin at inria.fr>
>     >     Reply-To: "OpenStack Development Mailing List (not for usage
>     >     questions)"
>     >     <openstack-dev at lists.openstack.org>
>     >     Date: Wednesday, June 21, 2017 at 6:54 PM
>     >     To: "OpenStack Development Mailing List (not for usage questions)"
>     >     <openstack-dev at 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" <kgiusti at gmail.com>
>     >         > À: "OpenStack Development Mailing List (not for usage
>     >         > questions)"
>     >         > <openstack-dev at lists.openstack.org>
>     >         > Envoyé: Mercredi 21 Juin 2017 15:23:26
>     >         > Objet: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman
>     >         > proposal for	message 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  (kgiusti at gmail.com)
>     >         > 
>     >         > __________________________________________________________________________
>     >         > OpenStack Development Mailing List (not for usage questions)
>     >         > Unsubscribe:
>     >         > OpenStack-dev-request at 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-request at 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-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 



More information about the OpenStack-dev mailing list