15:30:09 #startmeeting Performance Team 15:30:10 Meeting started Tue Feb 7 15:30:09 2017 UTC and is due to finish in 60 minutes. The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:30:14 The meeting name has been set to 'performance_team' 15:30:17 hello folks :) 15:30:19 o/ 15:30:25 o/ 15:30:48 spn rcherrueau ad_rien_ rook o/ 15:31:01 DinaBelova: o/ 15:31:06 DinaBelova o/ 15:31:09 in and out today :) 15:31:14 :D 15:31:18 ad_rien_ o/ 15:31:38 ok, it looks like not everyone has joined yet, but still let's get started 15:31:42 #topic Action Items 15:31:47 last time we had several ones 15:32:09 let's start with rook yours :) 15:32:10 rook Neutron API Performance results to performance docs ? :) 15:32:22 ha, work is complete just need to generate the rst 15:32:24 :*( 15:32:28 it is on the backburner 15:32:41 rook heh, so let's keep it for one more week 15:32:47 we can drop it 15:32:59 as i don't see that happening any time soon, ill get to when soon /me hopes 15:33:15 last time spn was wandering what test plan is those data based on 15:33:19 rook ack 15:33:45 #info rook will add Neutron API Performance results to performance docs once the nearest schedule will be clear for him 15:34:00 DinaBelova: what was the question? 15:34:30 rook "what actually is measured for Neutron API performance - what calls and what tools are used" 15:34:45 spn is that correct? 15:34:53 DinaBelova: yes 15:35:08 I wanted to see if I can follow the test plan and try it in-house 15:36:09 some time ago we used http://docs.openstack.org/developer/performance-docs/test_plans/neutron_control_plane/plan.html but I don't know is rook used the same approach 15:36:55 https://review.openstack.org/#/c/412554/ 15:36:59 was the tst plan i wrote 15:37:02 it is more generic 15:37:26 rook: great.. thank u 15:37:34 rook ack, so we just cover all possible API calls with browbeat :) that's fair enough :) 15:37:38 right 15:38:09 ok, so it looks like we may proceed with my action items 15:38:35 regarding reviewing the https://pad.inria.fr/p/sfBMUvWOpKtmfXT8 - ad_rien_ I took a look on abstract at the end of last week and everything was ok, so I just did not ping you 15:39:04 I think it's safe to say it's a good proposal with good chances for being chosen 15:39:12 sorry 15:39:24 I'm back (was tchating with rcherreau) 15:39:27 for what? :) 15:39:29 ah :) 15:39:37 ad_rien_ np, it's ok. 15:39:40 we submitted the proposal yesterday 15:39:43 as expected 15:40:10 sure, let's see how it'll go 15:40:11 from my perspective this proposal looks cool 15:40:28 do not hesitate to vote for the proposal ;) 15:40:29 BTW 15:40:31 :-P 15:40:34 :D sure :D 15:40:36 you can put an action on that :D 15:40:56 more seriously we would like to put additional efforts on ENOS 15:41:09 (We are checking with Orange to see whether we can get additional engineering task force) 15:41:17 our idea would be to put ENOS in the CI 15:41:30 in order to test performance regression tests 15:41:47 s/test/execute performance regression tests 15:41:58 we can discuss that point later 15:42:10 ad_rien_ ack 15:42:21 so regarding last action item on me - share status of workloads testing methodology/results sharing 15:42:28 hello, sorry for being late 15:42:52 sadly I have to announce that Intel folks made whole this methodology proprietary :( so nothing will be shared in terms of workloads testing :( 15:42:57 tovin07 np :) 15:43:25 DinaBelova: can we at least know what was the technology used ? 15:43:35 i.e. kolla based/Kubernetes based ? 15:43:43 or even that point is confidential? 15:44:14 ad_rien_ the thing was to deploy OpenStack resources in very specific configuration with very specific applications covering almost all ares of usual workloads (CPU, RAM, disk intensive) 15:44:21 and then run workloads through those applicaitons 15:44:26 this actually leads us even closer to the SPEC benchmark usage - as it's producing similar results 15:44:44 ok 15:45:16 spn after a conversation with Intel SPEC folks I got a message, that they are not able to share this benchmark somehow 15:45:43 oh.. 15:45:47 what is the problem 15:46:09 spn yeah 15:46:32 I'll try to communicate it a bit further, but the only real option I got is to buy it for Mirantis, that's not really cool 15:46:52 as we wanted to make it possible to run it for all Performance Team members 15:47:21 and that's bunch of companies - not necessary SPEC members 15:47:54 oh.. 15:48:13 spn - so that's most recent news on the SPEC discussion with Intel as well 15:48:43 I don't know if communicating about it with some other company will give more results - who knows 15:48:56 hmm.. 15:49:15 spn do you have any ideas? 15:49:39 in terms of getting spec you mean? 15:49:43 yeah 15:49:59 I am not sure how Dell I got it. I will check and update you next week 15:50:09 spn ack 15:50:30 #action spn find out how Dell was running SPEC Cloud benchmark 15:50:37 ok, so it looks like we may proceed 15:50:39 #topic Current progress on the planned tests 15:51:03 ad_rien_ rcherrueau any news? except the summit talk news? :) 15:51:51 rcherrueau is working on the patch for kolla 15:52:06 * ad_rien_ is looking for the url 15:52:42 #link https://github.com/rcherrueau/kolla-ansible/commit/e37c87f9e0ea3b2bef7de57f9268d2c913c0c7ff multi-region support in kolla - patch 15:52:58 he should send the patch by thursday hopefully 15:53:20 cool, so shortly we should have it in kolla itself :) that will be really nice :) 15:53:32 hopefully 15:53:34 ;) 15:53:50 anything else ad_rien_ ? 15:54:00 Next actions will be to start WANWide evaluations of OpenStack 15:54:09 that's all 15:54:15 ack, thank you sir 15:54:16 for the moment. 15:54:33 you're welcome 15:54:44 akrzos are you around? anything to share on your current experiments? 15:56:09 in the meanwhile: as for Mirantis - we installed k8s to start with stressing its control plane. although, even without any stress we found a tricky issue with kube proxy - https://github.com/kubernetes/kubernetes/issues/38372 15:56:24 its debug actually lead us to the issue in Go language itself 0_o 15:56:29 https://github.com/golang/go/issues/18925 15:57:06 so it's really funny that issues may lay so deeply in the system 15:57:48 therefore no tests were tun yet - we're trying to reproduce this thing again to collect more information for the Go community 15:58:19 it looks like akrzos is not yet here 15:58:39 so it looks like we may jump to the open discussion 15:58:48 #topic Open Discussion 15:59:08 ad_rien_ rook spn tovin07 rcherrueau akrzos anything to cover? 15:59:39 Is there additional presentations that are "performance team tagged"? 15:59:54 in the summit? 15:59:57 yes 16:00:17 I mean does anyone know any other proposal that have been submitted? 16:00:19 from my side: nothing for today 16:00:23 :D 16:00:35 I submitted one for performance monitoring 16:00:47 with redhat folks 16:00:51 Can we have the link? 16:00:51 I've pushed one presentation regarding Perf Team itself with my boss + one more regarding osprofiler with Vipin 16:01:12 I think it might be valuable to keep traces of these submissions. 16:01:21 Especially because it shows that our team is active 16:01:30 afaik there is not yet voting open 16:01:42 so we cannot publish links yet :) 16:01:52 Moreover it is interesting for others to know what are the current actions 16:02:01 (at least from the Inria side we would appreciate to know them) 16:02:15 moreover, I just found that call for speakers is prolonged 0_0 16:02:18 ok the call has been extended untill the 9th 16:02:24 yeah 16:02:25 so we can discuss that point next week. 16:02:30 ad_rien_ sure 16:02:47 #info share links to the perf team presentation once voting will be open for Boston cummit 16:03:41 ok, so it looks like we're done for today 16:03:59 sounds good 16:04:09 thank you folks! 16:04:12 see you next week! 16:04:14 thanks 16:04:16 #endmeeting