15:00:03 #startmeeting Yardstick work meeting 15:00:03 Meeting started Mon Nov 30 15:00:03 2015 UTC. The chair is anac. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:03 The meeting name has been set to 'yardstick_work_meeting' 15:00:10 #info Ana Cunha 15:00:19 #info Akis Kourtis 15:01:02 #topic vTC in OPNFV Ericsson lab 15:01:29 akiskourtis: have you started testing vTC in the lab? 15:02:22 I am currently waiting to synchronize with Intel on how to run the tests, and also talk to Daniel to fix my access 15:02:42 ok 15:02:58 #info work on-going to enable testing 15:04:34 daniel is trying to log in, irc has problems today 15:04:59 I will talk to him offline via email no worries 15:05:12 ok, let's move on then. 15:05:19 #topic dashboard 15:05:45 #info this was discussed in test&performance meeting last thursday 15:06:32 #info OPNFV testing dashboard will set max 10 graphs per project 15:06:54 #info Daniel Smith 15:07:01 #info I suggested we run a prototype for Yardstick with Grafana 15:07:05 hi daniel 15:07:19 #info no objections to my proposal 15:07:20 * lmcdasm waves 15:07:51 so, we will add 10 graphs to opnfv testing dashboard and all the rest (including also those 10) in grafana 15:08:24 we need to specify what we need for influxdB 15:08:46 do we know which node will be the centralized one? 15:09:08 meaning the grafana one 15:10:25 lmcdasm: do you think we host the grafana node in Montreal lab or we request to LF ? 15:10:37 it depends 15:10:48 if you want a influxDB node (a collector / parser node) 15:11:01 i can prop you one up in the Montreal POD and then you dont have to network from your YS setup to the LF POD 15:11:17 however, if you want those graphs public then that might be tricky 15:11:38 it might be better if you want to maek them public to have a DBnode in the backend and then setup a web front end on the Public OPNFVERICSSON.CA Web GW 15:11:52 (that way people who want to see dont need to have access to the Nodes themselves) 15:12:11 but really - figure out how you want it setup andlet mek now the RAM/CPU/HD you need and Ips and where (maybe drop it in the diagram or something) 15:12:27 and ill build out what you need..i have a granafa server running here that ive been playing with 15:12:36 but i dont know the data sets from YS so i dont know the hook in 15:12:55 i think sounds reasonable, people don't need to have access to the nodes to see the results 15:13:06 and its easier if you want to "show off" 15:13:16 :) 15:13:19 you can jus tpoint people to "www.opnfvericsson.ca/ys/granfana 15:13:23 or something like that 15:13:37 but like i said, lets get a mock up of how we want it to look adn the data flow 15:13:50 and we can worry about front end presentation when we have data going from YS to InfluxDB 15:14:06 (as well there is a RDP gw coming online this week - so access to the lab will be alot easier) 15:14:14 we need to collect data from different labs 15:14:20 hmm. 15:14:21 ok.. 15:14:27 how are you going to do this 15:14:29 a pull or a push 15:14:34 over what protocol? 15:15:03 so, i thought, a centralized influxdB managed by releng, push data from the labs there, and then the grafana node in Montreal ? 15:15:12 that could work 15:15:26 so you would have InfluxDB sit near theJenkins Master (LF probably) 15:15:42 and then we setup a secure connection to a Granafa box (that will PULL) from the inflxDB to make graph queiries? 15:16:31 the question is how often to pull ? we want, eventually, realtime 15:16:38 well. 15:16:44 maybe a way to approach it is like this 15:16:49 in grafana you can set it up, through the graph 15:16:59 firs t- think how often (granularity) you will pull from the other labs 15:17:01 from 1sec to 1 hour, depends on what you want 15:17:36 and then think, are you giong to want to collate or do comparative processing on the lab data before sending it to INFLUXDB 15:17:49 and then from there, is it going to be standard DB queiries that sit and are "on demand" 15:18:00 or do we want something more on the grafana side. 15:18:09 i think that stuff will come after you establigh your connetions 15:18:18 i dont think we "know" how much data we are talking about yet 15:18:34 collate, i think - comparative analysis on grafana side 15:18:35 so might be hard to pick a measurement period until we see the flow of data -but im game to try something simple 15:18:43 like pull from labs every hour 15:18:49 and then do a parse and present every 6 hours 15:18:51 just to start 15:19:01 and then adjust as you see the data come in to make it more relevant 15:19:09 (all suggestions) 15:19:19 sounds good to start, akis: what do you think? 15:19:39 yes I think it is fine 15:20:00 when I setup the vTC I can start sending some test data, and see from there 15:20:08 when everybody joins onboard 15:20:11 we can start sending data from YS in CA also 15:20:22 ok.. 15:20:33 if someone wants to send me the specs for the granfana box, 15:20:44 akis, can you do that? 15:20:46 ill stage it and get the grafana stuf fon there, give it an IP in your YS setup, etc 15:20:58 yes, of course 15:21:02 and then you can figure out the SSH link between LF Box and this one 15:21:07 thx akis! 15:21:24 i have a wish-list on the graphs here: https://etherpad.opnfv.org/p/yardstick_visualization 15:21:50 akis, can you specify the influxdB also ? 15:22:08 #action akiskourtis to specify the grafana box 15:22:23 we need to request from releng 15:22:30 yes, we can have them on the same machine, or should we do them separately? 15:22:41 separate locations 15:22:48 ok good 15:22:51 thanks 15:23:08 #action akiskourtis to specify the influxdB 15:23:24 just to check, do we need influxdB also on each lab? 15:23:45 it is not necessary, we can have on centralized 15:24:17 ok, we push the test results to the centralized, good 15:25:32 if nothing else on this topic, we move on? 15:25:55 #topic milestone D 15:26:09 #info milestone D is tomorrow, Dec 1st 15:26:26 #link https://wiki.opnfv.org/releases/brahmaputra/release_plan/yardstick_milestone_d_report 15:27:02 i think we won't manage all test cases until jan 5, we will continue coding after that 15:27:14 sorry - one question about InfluxDB 15:27:18 if i can ? 15:27:22 yes? sure ! 15:27:58 akis - did you want to setup a influx in Montreal as well to get started and built - i dont know the time for a LF request, but maybe you can also look to setup a central / remote replication (LF --> Montreal INflux) 15:28:04 that might be somethign to think about.. just a comment 15:28:33 you mean timing ? 15:28:44 ya 15:28:50 or perhaps, maybe easier.. make the request to LF 15:28:53 see the response 15:28:58 and if too long we will do something in house 15:28:59 ? 15:29:14 I prefer yes, as the vTC will be in Montreal, so as not to have connectivity troubleshooting 15:29:15 i dont know how "critical" in the project getting this up us 15:29:27 ok 15:29:33 so you let me know and we will get it done! 15:29:34 :) 15:29:40 ok thank you :) 15:30:28 so, we agree to set up a influxdB in Montreal to start with? 15:30:35 yes 15:30:45 perfect ! 15:30:49 i think so - i like the idea of getting a small prototype of all the nodes up and running 15:30:55 in a friendly network that we control first 15:31:04 i like the ieda of not waiting 15:31:07 to make sure we have all the interfaces and how we want it to look/layout down 15:31:13 and then when the other place is ready 15:31:19 you can just port configs / replicate the parts you want 15:31:22 then you arent waiting 15:31:28 (well.. on me a bit maybe :P). 15:32:26 #agreed set up an influxDB in Montreal to start with 15:32:47 #info a request to centralized dB in LF (Releng) will also be placed 15:33:48 anac: have a question about milestone D and SFC 15:34:05 let's get this started, by the your response time, lmcdsm, i need to think faster ! 15:34:22 yes, jose_lausuch ? 15:34:33 SFC is not in the DB yet 15:34:34 http://213.77.62.197/test_projects 15:34:40 I guess we need to include it 15:34:48 or do we assume is it in yardstick reporting? 15:34:57 (I prefer creating a project for SFC though) 15:35:17 yes, i will create a project for all yardstick "companions" 15:35:34 one for each, i mean 15:35:35 will you? 15:35:40 I can do it also right away 15:35:43 but as you wish 15:35:48 because Brady is scared :D 15:35:50 be my guest :) 15:36:32 can you also add IPVSIX, VNFGRAPH, KVM 15:36:42 well, yes I can do that , but I need more info 15:36:53 like wiki url, description of the project and so on 15:36:59 if we want to add also the test cases 15:37:25 we don't have that yet, can't you leave blank for the time being ? 15:37:34 this is not the dashboard, right? 15:37:52 just the list of test cases, or? 15:38:14 yes 15:38:24 but for milestone D everything should be there by today 15:39:08 the test specifications should be frozen, does not mean they are ready ! 15:39:52 i reported there is work to do on the detailed test specs 15:40:52 ok 15:40:59 I know 15:41:05 but the test cases should be ready described 15:41:16 minimum is : slogan+description 15:41:33 that is in jira, but we will have detailed .rst per test case 15:42:16 description of what is to be tested, expected result, param settings 15:42:47 does jira isse count as url you are after? 15:42:51 issue 15:43:21 maybe yes 15:43:33 if the JIRA issue is clear enough 15:43:38 for now we have only wikis :) 15:43:40 but its fine 15:44:07 ok, i can add my other compnion projects 15:44:14 companion 15:44:19 I'll add SFC, since I'm in contact with BRady already 15:44:24 you add the others, ok? 15:44:28 ok 15:44:44 do you want to work on SFC for Yardstick too ? 15:45:15 let me know 15:45:28 #topic other 15:45:36 anything else to discuss? 15:45:46 for now I cannot say yes/no... Im getting stressed with many things 15:45:51 I'll try my best :) 15:46:09 jose_lausuch, take your time 15:46:56 ok, that's all for today, thanks everyone ! 15:47:01 #endmeeting