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

Reply via email to