Monday, 2016-04-04

*** zz_dimtruck is now known as dimtruck00:04
*** aditi has quit IRC00:08
*** dimtruck is now known as zz_dimtruck00:27
*** klindgren has joined #openstack-performance00:44
*** markvoelker has joined #openstack-performance00:47
*** bapalm has joined #openstack-performance01:51
*** harshs has joined #openstack-performance02:11
*** harshs has quit IRC03:07
*** arnoldje has joined #openstack-performance03:07
*** harshs has joined #openstack-performance03:13
*** markvoelker has quit IRC03:14
*** markvoelker has joined #openstack-performance04:15
*** suro-patz has joined #openstack-performance04:19
*** markvoelker has quit IRC04:21
*** suro-patz has quit IRC04:32
*** arnoldje has quit IRC04:51
*** xek has quit IRC04:59
*** xek has joined #openstack-performance05:00
*** harshs has quit IRC06:34
*** suro-patz has joined #openstack-performance06:51
*** suro-patz has quit IRC07:28
*** rpodolyaka_afk is now known as rpodolyaka08:36
*** lezbar has joined #openstack-performance08:38
*** lezbar has quit IRC08:38
*** lezbar has joined #openstack-performance08:39
*** haukebruno has joined #openstack-performance09:06
DinaBelovarook - we (at Mirantis) did not manage to take a very close look on the Heat. Can you please share your details about the issues you faced?09:29
*** openstackgerrit has quit IRC10:48
*** openstackgerrit has joined #openstack-performance10:48
*** zz_dimtruck is now known as dimtruck11:34
*** markvoelker has joined #openstack-performance12:15
*** rfolco has joined #openstack-performance12:25
openstackgerritAlexandr Nevenchannyy proposed openstack/performance-docs: [WIP]Add test results for zookeeper service  https://review.openstack.org/30002912:25
rookDinaBelova Has Mirantis considered looking at TripleO?12:56
rookDinaBelova ^ Would be a good way to expose some of the issues.12:56
*** asingh has joined #openstack-performance13:04
*** dougs has joined #openstack-performance13:11
*** fredli has joined #openstack-performance13:13
*** bizarrodan is now known as dansmith13:35
*** dimtruck is now known as zz_dimtruck14:02
*** asingh has quit IRC14:12
*** regXboi has joined #openstack-performance14:20
*** asingh has joined #openstack-performance14:21
*** hieulq has joined #openstack-performance14:24
*** zz_dimtruck is now known as dimtruck14:30
*** harshs has joined #openstack-performance14:32
*** asingh has quit IRC14:35
openstackgerritAlexandr Nevenchannyy proposed openstack/performance-docs: [WIP]Add test results for zookeeper service  https://review.openstack.org/30002914:41
*** arnoldje has joined #openstack-performance14:42
*** rmart04 has joined #openstack-performance14:42
*** asingh has joined #openstack-performance14:46
*** harshs has quit IRC14:58
DinaBelovarook - probably some of the teams... Performance and scale team - nope15:00
rookDinaBelova cool15:00
rookDinaBelova short version is that heat-engine consumes around 20GB of ram w/ a Stack that is > 100 nodes.15:00
DinaBelovahehe, it's interesting15:01
DinaBelovaI remember we tried Heat Rally scenarios and Shaker against 200 nodes lab15:01
DinaBelovaShaker (that uses Heat) made a stack with 100 VMs there15:01
DinaBelovaI need to find the atop stuff from that envs15:02
DinaBelovasad that ilyashakhat is not around now15:02
dougsDinaBelova: Interesting, did you observe how the Heat RAM requirement scaled with the number of nodes?15:08
*** asingh has quit IRC15:08
DinaBelovadougs we (should) have this data from the MOS testing we done ~6 months ago, plus we're going to repeat some of the scenarios on 200+ nodes this time as well15:09
DinaBelovaI'll need to find this data, but I believe we should have some15:09
* DinaBelova adds this to my todo list, will try to find this before tomorrows IRC meeting15:09
dougsDinaBelova, thanks!15:10
DinaBelovadougs np15:10
*** asingh has joined #openstack-performance15:16
*** asingh has quit IRC15:17
*** aditi has joined #openstack-performance15:19
*** fredli has quit IRC15:21
*** asingh has joined #openstack-performance15:31
*** asingh has quit IRC15:36
*** asingh has joined #openstack-performance15:38
*** asingh has quit IRC15:43
*** aditi has quit IRC15:43
*** asingh has joined #openstack-performance15:43
*** aditi has joined #openstack-performance15:46
*** harlowja_at_home has joined #openstack-performance15:47
*** asingh has quit IRC15:58
*** asingh has joined #openstack-performance15:59
*** hieulq has quit IRC16:01
*** haukebruno has quit IRC16:09
*** suro-patz has joined #openstack-performance16:28
*** harshs has joined #openstack-performance16:31
*** suro-patz1 has joined #openstack-performance16:34
*** suro-patz has quit IRC16:35
*** anevenchannyy has joined #openstack-performance16:38
*** harlowja_at_home has quit IRC16:39
*** asingh has quit IRC16:48
rookDinaBelova you guys might be interested what we are doing wrt Performance/Scale16:48
DinaBelovarook indeed16:48
rookWe are building (attempting) to build a platform to do Performance and Scale Testing.16:48
rookDinaBelova it uses Rally, Shaker and PerfKit right now.16:48
rookLooking to add more connectors.16:48
DinaBelovarook what are you using to build it? is that only for OpenStack?16:49
rookDinaBelova we have a set of ansible playbooks that stand up Graphite/Grafana for viz/metric store and setsup collectd on each node in the cloud.16:49
DinaBelovaa-ha16:49
rookDinaBelova Right now, the metric gathering piece is psuedo generic.16:49
DinaBelovarook very interesting16:49
DinaBelovado you have somewhere docs for this platform?16:50
rookWe are looking at ElasticSearch now to store Rally results... that way we can compare results.16:50
rookfor example, looking at Keystone configured with different process/thread count16:50
rookand running Rally scenarios against that.16:50
rookstore the metrics in Elastic, then use Kibana to viz the results.16:50
rookcomparing different process/thread (wsgi) configurations.16:51
*** asingh has joined #openstack-performance16:52
DinaBelovarook -  i thought rally team had trends BP for implementing runs comparison in Rally itself?16:53
DinaBelovaboris-42, andreykurilin__ ? ^^16:53
rookDinaBelova sure, but I want this indexed in Elastic.16:53
rookRally has zero concept of the cloud.16:53
rookwith each index I will be passing metadata with details of the cloud.16:54
rookHow things were configured during the Rally scenario run.... for example, the thread/process count...16:54
DinaBelovarook well, I think it's still discussible with Rally community not to build new projects where we can extend old ones16:54
DinaBelovaplus Rally is having deployment model16:54
rookAmount of memory & number of processors... etc16:54
rookDinaBelova we consume Rally... so whatever they have, we can have :)16:55
rookDinaBelova PerfKit has decent workloads being added as well... IMHO different than Rally.16:55
rookDinaBelova Using the Rally Plugin Framework we could comibne Rally+PerfKit.16:55
DinaBelovarook I just want to make sure that all good stuff you'll be doing will end up in the projects most logically created for this :)16:56
rookDinaBelova are there regular meetings the perf/scale team has?16:56
DinaBelovatomorrow at 16:00 UTC16:56
rookDinaBelova Sure - I don't think it has a place in Rally...16:56
DinaBelovaTuesdays 16:00 UTC16:56
DinaBelovaplease add your item here https://wiki.openstack.org/wiki/Meetings/Performance16:56
DinaBelovalet's discuss what do you have now16:57
DinaBelovawe need a collaborative effort anyway16:57
*** aditi has quit IRC16:58
rookDinaBelova I'll make a attempt to attend :)16:58
DinaBelovarook cool, thanks :)16:58
rookI do agree - if we can push back upstream we will!16:58
DinaBelovarook ++16:59
rookRight now we are just taking *best of breeds* and integrate them into our workflow.16:59
DinaBelovarook please consider what we can do to push all the good stuff you're working on back to community17:00
DinaBelova:)17:00
rookDinaBelova Sure - Most of our stuff is on github17:01
DinaBelovarook link please :)17:01
rookhttps://github.com/jtaleric/browbeat17:01
*** rmart04 has quit IRC17:03
DinaBelovaack17:04
DinaBelovalemme take a look at this before tomorrow17:04
*** aditi has joined #openstack-performance17:14
*** aditi has quit IRC17:18
*** harshs has quit IRC18:24
*** harshs has joined #openstack-performance18:26
*** asingh has quit IRC20:00
*** asingh has joined #openstack-performance20:00
*** harshs has quit IRC20:01
*** suro-patz1 has quit IRC20:03
*** fredli has joined #openstack-performance20:54
*** dimtruck has quit IRC21:16
*** ngoracke has quit IRC21:16
*** nicholasgoracke has joined #openstack-performance21:16
*** dimtruck has joined #openstack-performance21:16
*** suro-patz has joined #openstack-performance21:21
*** harshs has joined #openstack-performance21:25
*** regXboi has quit IRC21:44
*** suro-patz has quit IRC22:00
*** harshs has quit IRC22:04
*** suro-patz has joined #openstack-performance22:05
*** harshs has joined #openstack-performance22:05
*** manjeets has left #openstack-performance22:06
*** arnoldje has quit IRC22:15
*** harshs has quit IRC22:18
*** harshs has joined #openstack-performance22:21
*** dimtruck is now known as zz_dimtruck22:35
*** markvoelker has quit IRC22:37
*** rfolco has quit IRC23:34
boris-42rook: so we are working on data plane testings23:37
boris-42rook: so we will have the same tests in rally =)23:37
boris-42rook: now we have really flexible reporting that allows us to store all data23:37
*** markvoelker has joined #openstack-performance23:37
boris-42rook: btw we have fianlly mechanism for exporting results from rally to other systems23:38
boris-42rook: like put the data to elastic search23:38
boris-42rook: if you are interested ping me=)23:38
boris-42rook: so some parts you can move natively to rally23:39
*** suro-patz has quit IRC23:53

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!