08:59:12 #startmeeting Dragonflow 08:59:12 Meeting started Mon Dec 7 08:59:12 2015 UTC and is due to finish in 60 minutes. The chair is gsagie. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:59:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:59:15 The meeting name has been set to 'dragonflow' 08:59:34 ok, welcome everyone to our first IRC meeting 09:00:13 We are going to talk about areas we are working for the next version and hopefully more people will join in later meetings 09:00:27 #topic testing 09:00:45 Yuli, Shlomo you are starting to look at functional testing right? 09:00:59 Yep 09:01:44 ok, there is one bug that Shlomo is looking at and got a bit complicated, i will look at it to see whats going on 09:02:21 As we discussed for the first stage we are going to work on writing tests that add logical elements to Neutron and verify that they are configured correctly in the DB 09:02:45 #action Yuli_s to start creating functional testing of Neutron plugin and DB client 09:03:34 #action Shlomo_N implement functional tests leveraging the work Yuli done 09:03:55 I am currently looking at how to run these tests in the gate with a working devstack 09:04:02 and Rally, which is our next step 09:04:15 #action gsagie look at Rally and how to run tests on the gate with devstack 09:04:25 we need to fix the gate errors first 09:04:28 #action gsagie Make tempest testing work 09:04:47 gampel: yes, but this is currently non voting and i will work on it but it may take some time 09:05:21 can we run the test on top of it even if it failed 09:05:21 Billy: Can you please share what are you working on? 09:05:45 gampel: the plan is to create a different job for that, and when its stable we can make it voting 09:06:32 Ok got it 09:06:37 BillyXu 09:06:59 we will start security group function this week. 09:07:47 BillyXu: ok, did you manage to setup a working Dragonflow do you need any help? 09:08:15 no problem for dragonflow setup 09:08:20 BillyXu: did you see the spec folder with the DNAT spce example, you would have to follow the same with SG 09:08:34 an problems, I'll contact with you. 09:09:06 if any problems, I'll contact with you. 09:09:06 Billy: ok that is great, its an important task for us 09:09:35 #action BillyXu create SG spec/design and get familiar with what is needed in the code 09:09:47 BillyXu: you can join #openstack-dragonflow if you need any help 09:10:18 ok, no problem. 09:10:19 We have also updated alot of documentation to the repository, you can read and understand the project more 09:10:31 sure 09:10:38 #link http://docs.openstack.org/developer/dragonflow/distributed_dragonflow.html 09:10:47 #link Dragonflow docs http://docs.openstack.org/developer/dragonflow/distributed_dragonflow.html 09:11:15 Billy: The time for this IRC meeting is ok for you two? 09:11:49 this time is ok for raofei and me. 09:12:17 ok great, let him know he can also come online and feel free to ask 09:13:04 #topic DB integration 09:13:12 we are going to land two new DB I hope this week dima is working on RethinkDB and Ahron the RamCloud 09:13:14 he failed to login irc meeting. he is trying now. 09:13:39 #info RAMCloud integration to merge this week 09:13:48 i saw the patch is ready 09:14:12 gampel: We might want to also look at packaging in conjunction to stabilize things 09:14:30 I think it is , i will ask dima and ahron to join the IRC meeting next week 09:14:55 #action gampel talk with Aharon and Dima to join the IRC Meeting 09:15:05 gsagie: i agree Shlomo all ready opened a bug for the Ramcloud missing packages 09:15:33 gampel: yeah, thats missing requierments, i was talking about a Dragonflow package 09:15:55 Shlomo_N: what packages are missing for RAMCloud? 09:16:40 gsagie: I found only two packages, but I want to install it again on clean env. and make sure there are no other packages. 09:17:40 gsagie: do you mean pip packaging for Dragonflow or devstack 09:17:50 gampel: maybe also RDO 09:18:16 gsagie: i see i will look into this and report for next meeting 09:18:35 #action gampel to look at RDO packaging 09:19:10 Shlomo_N: okie, we might need to install these packages in RAMCloud script 09:19:16 #topic open discussion 09:19:27 Anyone has any other topic to add or want to raise something? 09:19:35 Yoli, Shlomo: can you give a brief of the new bugs found 09:20:12 I found strange bug with traceroute 09:20:37 Yuli_s: can you share the link number 09:20:49 sec. 09:20:58 Welcome Raofei 09:21:10 Hi Gsagie 09:21:13 https://bugs.launchpad.net/dragonflow/+bug/1521629 09:21:13 Launchpad bug 1521629 in DragonFlow "traceroute packet delay" [Undecided,New] 09:24:20 ok, i will take a look at this bug and report to next meeting 09:24:33 #action gsagie to look at https://bugs.launchpad.net/dragonflow/+bug/1521629 for next meeting 09:24:34 Launchpad bug 1521629 in DragonFlow "traceroute packet delay" [Undecided,New] 09:24:52 Yuli_s: any other Major bugs found this week ? 09:25:17 I think we should improve the rejoin for supporting RAMCloud, look @ this bug: https://bugs.launchpad.net/dragonflow/+bug/1522029 09:25:17 Launchpad bug 1522029 in DragonFlow "rejoin-stack isn't supports RAMCloud" [Undecided,New] - Assigned to Li Ma (nick-ma-z) 09:25:46 gampel: nop 09:26:25 #topic no-dhcp-agent 09:26:36 #topic DHCP agent 09:27:04 This week we landed the patch that allow us to run without the q-dhcp agent 09:27:43 #info Dragonflow running without q-dhcop agent 09:27:47 currently it support only ipv4 ditst dhcp 09:28:25 If you need IPV6 dhcp the dhcp agent must be installed 09:28:45 i will add a new BP to support SDN based IPV6 application 09:29:11 ipv6-sdn-dhcp-app 09:29:28 #action gampel register bp to support IPV6 DHCP (ipv6-sdn-dhcp-app) 09:29:49 gampel: i think we also need to move most of the tasks from Trello to blue prints, i will do it 09:30:02 #action gsagie convert Dragonflow Trello to launchpad bps/bugs 09:30:11 we need to make sure to test in the next weeks both deployments with q-dhcp and without 09:30:46 I will register a spec for dhcp ipv6 app as well 09:30:59 #action gampel register a spec for dhcp ipv6 app 09:31:28 gampel: added that action :) 09:31:37 only the person that started the meeting can use the commands i believe 09:31:50 ops sorry 09:32:47 #topic Questions? 09:32:54 I think dhcp maybe need to enhance also. current dhcp app support DHCP_DISCOVER/DHCP_OFFER/DHCP_REQUEST/DHCP_ACK, maybe also need to support release/decline msg etc 09:32:54 so anything else? :) 09:33:35 milo_raofei_: good point, we should document this. You are working with Billy on the security groups for first stage? 09:33:58 milo_raofei_: this is a good idea can you please submit a bug 09:34:20 sure. I will raise a bug. 09:34:31 #action milo_raofei_ add a bug about missing functionality and suggestions for current DHCP (release/decline msgs) 09:34:56 yes, i work with billy 09:35:22 okie, we are at #openstack-dragonflow or in email if you need any help 09:36:07 I think that all the missing parts for the security groups design are there (in Ryu and OVS) and its an interesting task :) 09:36:24 ok, anything else from anyone? 09:36:52 thank you. I will join 09:37:36 yes. we are interested in security group and NAT based on latest ovs. 09:37:57 I think that NAT support is not there yet 09:38:00 okie, i think there is another person that also want to work on Kuryr? 09:38:45 I think he did not join i will talk with him to join next week 09:38:58 okie 09:39:31 maybe he is here kexiaodong 09:39:38 I want to join kuryr. 09:39:54 kexiaodong: hi 09:40:12 hi gampel 09:40:39 kexiaodong: a very good first task will be to integrate dragonflow with kuryr 09:41:14 kexiaodong: we can talk about Kuryr more offline, are you available to start working on it? 09:41:20 kexiaodong will working on kuryr. 09:41:20 he will consider dragonflow intergated with kuryr 09:41:35 okie 09:41:49 #action kexiaodong to look at integrating Dragonflow with Kuryr 09:42:07 kexiaodong also work together with me. 09:43:07 ok, welcome BillyXu, Raofei and Kexiaodong 09:43:18 to the Dragonflow/Kuryr team :) 09:43:25 thanks. 09:43:37 gampel: anything else? 09:43:47 nop thank you very much 09:43:55 no, thanks. 09:44:04 ok thanks everyone for joining! 09:44:08 #endmeeting