14:31:41 #startmeeting integration weekly meeting 27/02/2018 14:31:41 Meeting started Tue Feb 27 14:31:41 2018 UTC. The chair is morgan_orange. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:31:41 The meeting name has been set to 'integration_weekly_meeting_27_02_2018' 14:31:50 #chair helenychen 14:31:50 Current chairs: helenychen morgan_orange 14:32:00 #chair gildaslanilis 14:32:00 Current chairs: gildaslanilis helenychen morgan_orange 14:32:17 #chair ntpttr kennypaul electrocucaracha csatari 14:32:17 Current chairs: csatari electrocucaracha gildaslanilis helenychen kennypaul morgan_orange ntpttr 14:35:08 #topic action points follow up 14:35:16 #info AP1: morgan_orange synch with Eric on INT-340 14:35:58 #info study to reduce the size of ONAP (light configuration) done by E.Debeau 14:36:08 #info without considering DCAE 14:36:08 #info most of the VMs can be significantly reduced and ONAP keep on running (in a minimal config) 14:36:08 #info e.g. dns large => small (14 to 1 vCPU) 14:36:08 #info aai1: xlarge => large (14 to 4 vCPU) 14:36:08 #info overall (without DCAE): from 208 vCPU to 37 14:36:08 #info I suggest to create a page to mention the different values 14:36:58 #action eric create a heat-minimum config in the integration repo 14:37:36 #link https://git.onap.org/demo/tree/heat/ONAP 14:37:52 #info AP2: helenychen follow-up with mickael on INT-300 and INT-346 14:37:58 #info done 14:38:06 #info AP4: helenychen follow up on tag mechanism INT-189 14:38:11 #chair gwu 14:38:11 Current chairs: csatari electrocucaracha gildaslanilis gwu helenychen kennypaul morgan_orange ntpttr 14:38:44 ONAP heat template is located in demo repo, demo/heat/ONAP 14:38:57 gwu: I think I found it see above :) 14:39:36 ok, I just got in to IRC so I can't see the history 14:39:55 for the IRC meeting if you want that your statements to be automatically put in the repo you should use info, action, link keyword before your text 14:40:40 #info gildaslanilis mentions that there is work in progress on the standardization of the tagging 14:40:53 #info LF will tag the images as described in the wiki 14:41:39 #link https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process#IndependentVersioningandReleaseProcess-StandardizedDockerTagging 14:42:48 #link p, li { white-space: pre-wrap; } https://jira.onap.org/browse/CIMAN-132 14:42:50 #undo 14:42:50 Removing item from minutes: 14:43:17 #link https://jira.onap.org/browse/CIMAN-132 14:43:51 #info work consisting in creating INFO in repo to manage users in progress 14:44:04 #info trial in progress with some projects 14:44:25 #fino AP4 helenychen check with Dan on INT-254 -Amstredam bug) 14:44:28 #info done 14:44:35 #info AP5 helenychen follow up with Edmund Haselwanter on INT-292 14:44:36 #done 14:44:51 #topic Stabilize Master branch? 14:45:57 gwu: maybe you can summarize the status here... 14:46:04 you will do better than me :) 14:47:49 #info ONAP Beijing release cannot currently deploy; question is when we need the project teams to stabilize the deployments 14:48:12 #info concern on the latest build: CI chain needed to give confidence on the integration 14:48:26 #info 2 chains needed amsterdam (stable) and master (Beijing) 14:50:55 #info lots of changes in master at the moment... 14:52:08 #info components csit currently failing. minimum for M3 would be that the csit tests are OK 14:53:23 #action gildaslanilis follow-up with dmaap => csit tests down since 3 months... 14:54:20 #topic S3P Testing Tools progress 14:55:04 #info internal syncho integration meeting on tooling (advantages/drawbacks) + demo on Locust 14:56:16 #info JMeter great tool but complex to manage and adapt to integration context 14:56:40 #info ran indicates that Locust is much easier to manage especially for end users 14:58:05 #action ran plan a demo for the meeting next week 14:59:17 #info helenychen "S3P testing is key for Beijing" 15:04:10 #Action Luman plan a demo on JProfile 13th of March 15:04:25 #undo 15:04:25 Removing item from minutes: 15:04:33 #action Luman plan a demo on JProfile 13th of March 15:04:55 #info Luman no access to windriver lab so far 15:05:09 #action helenychen follow up China Mobile access to windriver lab 15:08:35 #action george nmap demo to be planned (Connectivy issues with integration lab) 15:08:55 #info question on the flow matrix (ports) nmap is scanning stuff...so it would be interesting what should eb open or npot 15:16:12 #topic Going through Integration M3 Sprint 15:16:22 #link https://jira.onap.org/secure/RapidBoard.jspa?rapidView=81&view=planning.nodetail 15:18:44 #info new use case based on vLB & vDNS in progress (with manaul scaling) 15:43:21 #topic Follow up 15:43:23 #link http://testresults.opnfv.org/onap-testing/ 16:15:32 #info morgan_orange reminds that the request for resources has been sent more than 1 month ago 16:16:05 #info morgan_orange the code shall speak, it can be criticisez, commented, refused but it shall be code centric and not meeting centric 16:16:27 #info helenychen mentioned that some (shy) people are not convinced by the approach 16:17:21 #info typically these people shall express themselves though teh code review not from meeting statement 16:17:32 #info helenychen would like a conf between functest and jenkins 16:17:51 #info morgan_orange explains that it has no sense: jenkins = gitlab = tool to send jobs in CI 16:19:32 #info functest is just a simple framework to run tests (framework, python, bash based ..) in a consistent way. The developers has not to take care of the jenkins, the test results reporting. Functest provides some guidelines so the results, the cases, the projects are consistant accross the diferent projects 16:20:45 #info bitergia has developed some code to extract some info from the DB and create a dedicated testing dashboard in OPNFV 16:21:12 #link https://opnfv.biterg.io/app/kibana#/dashboard/Testing 16:22:43 #info functest is not the only option, it is only one way to create a consistent view. It can coexist with other otpions, but there is no reason to prevent comitting.. 16:22:58 #info hot discussion on who decides what is useful or not in an Open Source community 16:23:47 #info morgan_orange mentioned that the Open Source way is different from the top/down traditional approach. Tha adoption is based on the code and the community not on meeting decisions 16:25:21 #info current status of daily tests on Orange open lab (Amsterdam MR installed with heat triggered using internal gitlab) of the main healthcheck tests http://testresults.opnfv.org/onap-testing/amsterdam/functest/status-heat.html 16:25:34 #topic 16:25:36 #undo 16:25:36 Removing item from minutes: 16:25:40 #topic AoB 16:25:43 #endmeeting