16:46:56 #startmeeting synchro Functest/OVNO November 24th 16:46:56 Meeting started Tue Nov 24 16:46:56 2015 UTC. The chair is morgan_orange. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:46:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:46:56 The meeting name has been set to 'synchro_functest_ovno_november_24th' 16:47:02 #Morgan Richomme 16:47:12 can you give an overview of how you run tests in open contrail project? 16:47:15 what tools you use and so on 16:47:19 #info Jose Lausuch 16:47:32 I created an adh hoc meeting for to get some minutes 16:47:39 yes, thanks morgan 16:47:53 status Fuel integrated OpenContrail as far as I know 16:48:00 Juju was alreday supporting it 16:48:13 I can imagine Apex is also working on it 16:48:15 yes, however it needs more work for Fuel 16:48:23 it is non HA deployment I think 16:48:25 so we will have lab running OpenContrail 16:48:30 which is a good news 16:48:33 but just for simplifying things 16:49:00 May Functest help OVNO to run the tescases after the fresh install 16:49:21 I was thinking that you would be looking for a set of scripts similar to what is used for ODL 16:49:27 StuartMackie: can you give us a status on your side (your labs and the test suites) 16:49:50 Create network, create policy, apply policy, create VMs, test connectivity 16:49:50 StuartMackie: right 16:49:56 yes we would like at least the minimum list done for ODL on Arno (create/delete/update port/network/subnet) 16:49:58 something like that 16:50:16 that is the baseline (we do not perform performance tests) 16:50:20 Then in addition, we will do some stuff like apply floating IP, create service chains 16:50:33 for brahmaputra, we are working on exrtending the scope based on upstream tests from ODL 16:50:49 if we could manage together to have even something extended it would be nice 16:50:56 but focusing on having 100% working the basic ones 16:51:08 #info OpenContrail shall be available in most of the installers , if not all 16:51:14 I guess you have also many features to test 16:51:17 #info Functest focusing on basic tests (like ODL for Arno) 16:51:30 #info create/delete/update port/network/subnet 16:51:34 what tools do you use StuartMackie? 16:51:50 #info additional tests may be added (SFC, floating,..) 16:53:03 There are python commands for all OpenContrail features, and some helper tools that take care of Keystone transparently 16:53:42 My thinking is to bundle some of these into scripts/tests with the same names as the ODL ones where possible 16:54:01 my idea is: 16:54:07 What artifacts do you need me to deliver 16:54:24 have 1 script (bash) for automation calling all the underlying python scripts you have for testing 16:54:29 that script would be called from CI 16:54:37 those python scripts I would say 16:54:44 #info There are python commands for all OpenContrail features, and some helper tools that take care of Keystone transparently 16:55:07 are they in a repository somewhere? 16:55:10 so that we can have a look? 16:56:01 hang on - searching... 16:57:00 Take a look at https://github.com/tonyliu0592/orch/blob/master/doc/configuration.md 16:57:35 Not all Contrail features are included, but almost everything that we will need for OPNFV is there 16:58:25 #link https://github.com/tonyliu0592/orch/blob/master/doc/configuration.md 16:58:33 I Was about to info it :) 16:58:34 ok 16:58:41 so the idea would be to clone that repository 16:58:44 and use those scripts 16:58:48 similar as we do for ODL 16:59:07 yes 16:59:10 yes 16:59:29 so what we need to start testing is a beta OPNFV including OpenContrail... 16:59:44 as far as I know there are no lab ready yet 16:59:49 I see things like delete-network and others which is what we wanted :) 16:59:56 not yet 16:59:58 I hope soon 17:00:02 but we can start scripting 17:00:07 yes 17:00:30 There is a new lab being set up in Juniper office in NJ that should come online in next couple of weeks 17:00:31 StuartMackie: do you know if there is any dev lab using Opencontrail at the moment? 17:00:40 ok that is good 17:00:48 I have a lab from Jonas 17:00:49 a dev lab 17:00:53 but not connected to CI 17:00:59 We were supposed to be in one of the Intel pods, but I don't know if that happened 17:01:01 but good to start running some test 17:01:04 dev lab is enough to start testing script manually 17:01:07 yes 17:01:46 StuartMackie: its just running those scripts? 17:01:48 nothing else? 17:01:54 like creating an environment or something? 17:02:06 or is there any requirement about where to run the scripts? 17:02:21 we intend to do it from a docker container on a jumphost 17:02:38 There's another layer on top of the scripts that needs to know the IP address of OpenStack for instance, and set up OpenStack users and projects 17:03:13 we source the credentials in the docker 17:03:33 how many projects/users does it need? 17:03:53 Also, I need to work out how to test inter-VM communications from a jump server, since the Contrail virtual networks need a gateway to connect outside 17:04:15 we have a similar ping 17:04:18 sorry 17:04:20 a similar test case 17:04:21 vPing 17:04:29 where we check the communication between 2 VMs 17:04:38 but we do it in a different way 17:04:56 Actually, you can do everything as admin, but perhaps its cleaner to create a test user 17:04:57 just grabbing the console log and see the output of a VM pinging the other 17:05:08 we run some things as admin 17:05:10 :) 17:05:25 If you already know how to scrape the console, then we can do that 17:05:42 how do you check the connectivity between 2 vms? 17:07:03 Also using ping, but was thinking of a more programmatic approach initiated by the test system. How does vPing know which IP address to ping? 17:07:17 we create 2 ports with specific ips 17:08:44 We could take same approach 17:08:53 ok 17:09:03 would that mean that you have to modify that repository? 17:09:15 which repository? 17:09:18 yours 17:09:38 This would be in the test script? 17:09:42 I mean, the scripts doing all the things 17:09:46 creating VMs and so on 17:09:50 (just wondering) 17:09:50 Sure 17:10:31 ok 17:11:04 default_client_args = [ ('--username', 'admin'), ('--password', 'contrail123'), ('--region', 'RegionOne'), ('--tenant', 'admin'), ('--api-server', '127.0.0.1')] 17:11:15 api server is the open contrail controller ip? 17:12:04 that's right - these defaults are for running on same server as OpenContrail 17:12:10 ok 17:12:49 #info Open Contrail conding automation to be started asap using existing repository with test cases 17:12:57 I think its a good startpoint 17:13:03 don't you think morgan_orange? 17:13:08 we just need a lab soon :) 17:13:14 yes 17:13:29 good to see that approache is no 180 degrees 17:13:33 I'll let you know when the NJ lab is up 17:13:34 hope it will be the same for Onos 17:13:43 yes 17:13:50 good 17:13:58 we need to be in touch 17:14:04 what is your timezone StuartMackie? 17:14:17 and the test script will be available on OVNO repo or on the github used for the command tool 17:14:45 Am in EST. Test scripts will go in OVNO repo 17:14:53 ok clear 17:15:20 so we come to you as soon as we have a lab ready but this task seems realistic :) 17:15:33 I will create a Jira on my side to describe this integration task 17:15:48 I may assign to you to keep the information and follow up in the backlog 17:16:05 but we will perform the integration 17:16:06 Ok 17:16:09 We can do a web session to go through how OpenContrail works if you like, so you can get used to it. 17:16:14 #info tests will be in OVNO repo 17:16:31 #info work to be started when lab with OPNFV/contrail ready 17:16:34 ok 17:16:38 would be great 17:16:52 but automation scripts will be in functest repo 17:16:58 Let's do a session next week - what timezones are you 17:16:59 I mean, the script calling your scripts :) 17:17:01 my colleagues are familiar with Contrail, I will be less ridiculous when discussing with them 17:17:09 we are both CET 17:17:53 we may open the session to the community as I am pretty sure other people will be interested 17:18:27 so its 6 hours differene 17:18:30 difference 17:19:05 9 or 10 New York time is fine for us 17:19:26 yes 17:19:38 I will need to catch up with contrail since then 17:19:42 I have no clue! :) 17:20:59 ok so let's propose a slot OpenContrail for the dummies, we will be there :) 17:21:18 maybe we can end the meeting 17:21:43 Looking for a slot - so many OPNFV meetings 17:21:48 and keep in touch as soon as we can start scripting (we will put you in review of our script (that will run your script)) 17:22:28 Ok - cheers 17:22:58 #action StuartMackie propose a slot to dive into the beauty of OpenContrail 17:23:02 #endmeeting