Monday, 2016-09-05

*** bpokorny has joined #openstack-meeting-400:02
*** sdake has joined #openstack-meeting-400:07
*** bpokorny has quit IRC00:09
*** uck has quit IRC00:11
*** kenhui has quit IRC00:25
*** amitkqed has joined #openstack-meeting-400:26
*** sdake has quit IRC00:39
*** iurygregory has joined #openstack-meeting-400:40
*** uck has joined #openstack-meeting-400:41
*** uck has quit IRC00:46
*** iurygregory has quit IRC00:46
*** markvoelker has joined #openstack-meeting-400:52
*** markvoelker has quit IRC00:57
*** kenhui has joined #openstack-meeting-400:58
*** kenhui has quit IRC00:59
*** limao has joined #openstack-meeting-401:08
*** amotoki has joined #openstack-meeting-401:13
*** Guest62633 has quit IRC01:14
*** gongysh has joined #openstack-meeting-401:18
*** dansmith has joined #openstack-meeting-401:19
*** chigang_ has joined #openstack-meeting-401:20
*** salv-orlando has joined #openstack-meeting-401:21
*** salv-or__ has quit IRC01:24
*** iurygregory has joined #openstack-meeting-401:33
*** caowei has joined #openstack-meeting-401:44
*** yulong|away has quit IRC01:48
*** liwei has joined #openstack-meeting-401:56
*** Kevin_Zheng has joined #openstack-meeting-402:00
*** thorst has joined #openstack-meeting-402:02
*** thorst has quit IRC02:07
*** shihanzhang has quit IRC02:12
*** shihanzhang has joined #openstack-meeting-402:13
*** banix has joined #openstack-meeting-402:18
*** banix has quit IRC02:19
*** uck has joined #openstack-meeting-402:30
*** uck has quit IRC02:34
*** liuyulong has joined #openstack-meeting-402:41
*** amotoki has quit IRC02:46
*** markvoelker has joined #openstack-meeting-402:53
*** markvoelker has quit IRC02:57
*** thorst has joined #openstack-meeting-403:02
*** thorst_ has joined #openstack-meeting-403:03
*** amotoki has joined #openstack-meeting-403:05
*** thorst has quit IRC03:06
*** thorst_ has quit IRC03:07
*** amotoki has quit IRC03:13
*** amitkqed has quit IRC03:27
*** amitkqed has joined #openstack-meeting-403:28
*** liwei has quit IRC03:32
*** liwei has joined #openstack-meeting-403:57
*** amotoki has joined #openstack-meeting-404:01
*** iurygregory has quit IRC04:12
*** uck has joined #openstack-meeting-404:18
*** pbourke has quit IRC04:20
*** pbourke has joined #openstack-meeting-404:20
*** uck has quit IRC04:23
*** JRobinson__ is now known as JRobinson__afk04:26
*** claudiub has joined #openstack-meeting-404:33
*** links has joined #openstack-meeting-404:49
*** JRobinson__afk is now known as JRobinson__04:52
*** markvoelker has joined #openstack-meeting-404:53
*** markvoelker has quit IRC04:58
*** wanghua has quit IRC05:16
*** dkehn_ has quit IRC05:28
*** iurygregory has joined #openstack-meeting-405:34
*** padkrish has joined #openstack-meeting-405:38
*** dkehn_ has joined #openstack-meeting-405:40
*** padkrish has quit IRC05:40
*** matrohon has quit IRC05:48
*** amotoki has quit IRC06:05
*** uck has joined #openstack-meeting-406:06
*** uck has quit IRC06:11
*** nkrinner_afk is now known as nkrinner06:14
*** nkrinner has quit IRC06:15
*** nkrinner has joined #openstack-meeting-406:17
*** prateek has joined #openstack-meeting-406:18
*** pcaruana has joined #openstack-meeting-406:20
*** oshidoshi has joined #openstack-meeting-406:22
*** nkrinner has quit IRC06:25
*** thorst has joined #openstack-meeting-406:33
*** nkrinner has joined #openstack-meeting-406:38
*** JRobinson__ has quit IRC06:41
*** amotoki has joined #openstack-meeting-406:46
*** amotoki has quit IRC06:48
*** amotoki has joined #openstack-meeting-406:48
*** alexchadin has joined #openstack-meeting-406:53
*** markvoelker has joined #openstack-meeting-406:54
*** alexchadin has quit IRC06:55
*** markvoelker has quit IRC06:59
*** zhurong has joined #openstack-meeting-407:04
*** salv-orl_ has joined #openstack-meeting-407:20
*** dtardivel has joined #openstack-meeting-407:22
*** salv-orlando has quit IRC07:23
*** alexchadin has joined #openstack-meeting-407:33
*** sarob has joined #openstack-meeting-407:33
*** sarob has quit IRC07:37
*** vishnoianil has quit IRC07:42
*** matrohon has joined #openstack-meeting-407:52
*** liwei has quit IRC07:53
*** uck has joined #openstack-meeting-407:54
*** alexchadin has quit IRC07:54
*** vishnoianil has joined #openstack-meeting-407:54
*** alexchadin has joined #openstack-meeting-407:55
*** thorst has quit IRC07:58
*** uck has quit IRC07:59
*** prateek has quit IRC08:10
*** liwei has joined #openstack-meeting-408:12
*** dshakhray has joined #openstack-meeting-408:14
*** salv-orlando has joined #openstack-meeting-408:29
*** salv-orl_ has quit IRC08:32
*** thorst has joined #openstack-meeting-408:34
*** liuyulong is now known as liuyulong|away08:38
*** Guest30374 is now known as bradjones08:41
*** bradjones has joined #openstack-meeting-408:41
*** thorst has quit IRC08:41
*** qwebirc44830 has joined #openstack-meeting-408:51
*** lihi has joined #openstack-meeting-408:55
*** markvoelker has joined #openstack-meeting-408:55
*** admcleod_ is now known as admcleod08:56
*** markvoelker has quit IRC09:00
*** oanson has joined #openstack-meeting-409:00
oanson#startmeeting09:01
openstackoanson: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'09:01
oanson#startmeeting Dragonflow09:01
openstackMeeting started Mon Sep  5 09:01:07 2016 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:01
openstackThe meeting name has been set to 'dragonflow'09:01
oansonAll right, who is here for the Dragonflow meeting?09:01
oshidoshio/09:01
lihio/09:01
yuli_s1o/09:02
oansonI was kinda sortsa hoping for more people :)09:02
oshidoshilet's give them a couple more09:02
*** DuanKebo has joined #openstack-meeting-409:03
oansonDuanKebo, hi.09:05
DuanKebohi09:05
oansonWell, let's get started09:07
oanson#topic Roadmap09:07
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:07
oansonSecurity groups is giving us a lot of grief.09:08
oansonFor a while it isn't working on the gate.09:08
oansonDuanKebo, I understand your team is taking this?09:08
DuanKeboIt's duo to kernerl module of ct09:08
DuanKebo*due to09:08
oansonWhat version has to be installed?09:09
DuanKeboas far as i know, introduced by the dpdk patch.09:09
DuanKeboI think we can optimize the install of ovs09:09
oansonDuanKebo, that would be great. How?09:10
DuanKeboovs version 2.5 is ok,09:10
oansonDo you know what kernel version and what modules are needed?09:10
DuanKeboif the right version of ovs is installed, we needn't to uninstall and install it again.09:11
oansonBecause in my environment I have upgraded to the latest kernel (4.7.2) and it still fails.09:11
oshidoshiso, this is a patch to the dragonflow devstack?09:11
oansonAdditionally, in ML2 (I'll go into more details in a second) it failed before the DPDK patch was merged.09:12
DuanKeboi'm using ubuntu 14.0409:12
nick-mahi09:13
oansonnick-ma, Hi09:13
DuanKeboHi09:13
oansonDuanKebo, have you tried locally reverting the dpdk patch and seeing if it solves the issue?09:13
DuanKebothe fialure is caused by not loading contrack module09:14
*** yuanwei has joined #openstack-meeting-409:14
nick-mawhy dpdk patch affect sg?09:14
nick-masorry i dont get.it09:14
oshidoshinick-ma, +1 - neither do i09:14
DuanKeboone second, yuanwei has the details.09:14
oansonDuanKebo, yuanwei, what's the name of the kernel module that needs to be loaded?09:15
yuanweiHello09:15
yuanweiwait a sec09:15
yuanweiI found errors in vswitch log09:17
oansonyuanwei, yes09:17
nick-mai tried several combination of kernel and ovs locally. but they failed. any temp solutions?09:17
*** sambetts|afk is now known as sambetts09:18
oshidoshioanson, i think ovs uses libnetfilter_conntrack09:18
yuanwei2016-08-31T07:47:38.381Z|00011|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_state09:18
yuanwei2016-08-31T07:47:38.381Z|00011|ofproto_dpif|INFO|system@ovs-system: Datapath does not support ct_state09:18
yuanweiDatapath does not support ct_state09:18
yuanweiDatapath does not support ct_state09:18
yuanweiDatapath does not support ct_state09:18
yuanweiI think a old datapath was in the kernel, not the new one09:19
oansonyuanwei, the dpdk patch should only be in effect if it is activated. How did it make a difference?09:19
*** berendt has joined #openstack-meeting-409:21
oansonI would like to move on.09:21
yuanweiI found this patch deleted some codes09:21
oansonDuanKebo, yuanwei, please open a bug about SG, and put all the information you have in there09:22
DuanKeboa temp solution is remove the ovs and reinstall it manually09:22
oansonWe will keep the discussion on the bug, and see if we can find a solution.09:22
oansonDuanKebo, noted. Please add that to the bug report.09:22
oanson#action DuanKebo,yuanwei open bug report on SG and update it with cause and workaround09:23
oansonAbout ML209:23
oansonI have tried setting it up and testing it on my environment.09:23
oansonIt appears to work, but the fullstack tests fail there as well09:23
oansonI also saw Li Ma tried to have the gate test it, and there are many errors there too.09:23
oansonIn my environment, specifically, some issues (but not all) were related to SG, so I will try again with the workaround09:24
oansonDuanKebo, can you guys take ownership on this and iron out the ML2 bugs?09:24
oansonI want to reach a state where ML2 is completely working before the summit09:24
DuanKeboWe have the same puzzles.09:24
oansonI think for now we should add another gate task for ml2 fullstack.09:25
DuanKebothe ml2 pulgin runs successfully on our local envionment.09:25
oansoni.e. have both core plugin and ml2 run on the gate.09:25
DuanKebobut no problem, we can take it.09:25
oshidoshioanson, perhaps try to uninstall OVS and re-install OVS 2.509:25
oansonThis way we can keep tabs on how well ml2 is doing as well.09:25
*** thorst has joined #openstack-meeting-409:26
*** hshan has joined #openstack-meeting-409:26
yuanweihttps://review.openstack.org/#/c/348169/15/devstack/ovs_setup.sh@116  @MaLi those change may cause that error I mentioned09:26
oansonoshidoshi, will try that too09:26
oshidoshioanson, if that works out, the devstack can be updated to do the same (uninstall and reinstall)09:27
oansonoshidoshi, the devstack already does that.09:27
oansonThe location may have to be changed09:27
nick-mayou mean the removing of module09:27
yuanweiyes09:27
nick-mayuanwei: ok, but these lines are always failed in my local env.09:28
nick-mai think we need a more stable solution to reload kernel mmodule.09:28
oansonyes09:29
yuanweiok, I agree, that is only a temp fix09:29
DuanKeboin fact, for system like ubuntu 14.04, we can just use the default ovs, it's already 2.5.009:30
oansonDuanKebo, I think you need to install the cloud:mitaka repository for that.09:30
oansonAnd in Fedora, that's what we do09:31
oansonI think we just need to make sure the conntrack module is loaded before openvswitch09:31
oansonQoS and VLAN reviews are online.09:32
oansonNon-cores, please review them.09:32
oansonThere are a lot of reviews, and only two cores, so we need all the help we can get09:32
oansonEspecially the long ones, e.g. qos, vlan, extra routes09:33
oansonDuanKebo, about extra routes - what about adding routing policy api to Neutron? Is that still interesting?09:33
*** prateek has joined #openstack-meeting-409:33
DuanKeboYes, before we run it stably in df09:34
oansonall right. I'll work something up.09:34
yuanweiPlease also review this patch https://review.openstack.org/#/c/339975/, that is the first patch about allowed address pairs module09:35
nick-maok09:35
oansonyuanwei, this patch has 2 downvotes on it.09:35
yuanweiI will update this patch today09:35
oansonAll right. Then we will review it.09:35
yuanweithanks;)09:36
oansonAny other road-map issues?09:36
DuanKebooanson, you need spend more time reviewing also ^o^09:36
oansonDuanKebo, as I mentioned, there are too many reviews for the number of reviewers.09:36
oansonBut I am doing my best :)09:37
oansonAny other roadmap issues?09:37
nick-mai will also try to spend more time on reviewing.09:37
oansonnick-ma, I think you're the only one who reviews too much :)09:38
*** sarob has joined #openstack-meeting-409:38
oanson#topic Bugs09:38
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"09:38
*** zhurong has quit IRC09:38
yuli_s1sec.09:39
oansonThere is bug 161910109:39
openstackbug 1619101 in DragonFlow "secgroup ofperror flooding in the fullstack ci" [Critical,New] https://launchpad.net/bugs/161910109:39
yuli_s1yes, i wanted to talk about it09:39
oansonIt is critical, and it is SG related. Yuanwei, can I assign it to you?09:39
DuanKebois this the same problem related with the contrack09:40
oansonIs bug 1571551 still experienced by anyone?09:41
openstackbug 1571551 in DragonFlow "Kernel module vport_geneve.ko fails to load on ubuntu" [High,New] https://launchpad.net/bugs/157155109:41
oansonDuanKebo, yes, that's what I thought as well09:41
*** xiaohhui_ has joined #openstack-meeting-409:41
oansonThat's why I am assigning it to you and yuanwei .09:41
oansonAll right, I am bumping 1571551 down to medium. If anyone runs into it, please bump it back up to high.09:41
DuanKeboOK09:41
nick-maok09:42
yuli_s1we need https://bugs.launchpad.net/dragonflow/+bug/157155109:42
openstackLaunchpad bug 1571551 in DragonFlow "Kernel module vport_geneve.ko fails to load on ubuntu" [Medium,New]09:42
DuanKebowe can bypass it by completely reinstall ovs09:42
*** uck has joined #openstack-meeting-409:42
DuanKebobefore it is solved09:42
oansonDuanKebo, yes, but that's a workaround. On the other hand, this is devstack environment, so it's acceptable.09:43
*** sarob has quit IRC09:43
oansonBug 1480672 , which is on Gal09:43
openstackbug 1480672 in DragonFlow "Add Neighbour Discovery handling in local controller" [Medium,Triaged] https://launchpad.net/bugs/1480672 - Assigned to Gal Sagie (gal-sagie)09:43
oansonlihi, I understand you are working on it?09:43
*** zenoway has joined #openstack-meeting-409:43
DuanKeboyes, omer, we still need work on the bug.09:43
lihiyes, I'm on it09:43
oansonDuanKebo, I am just organising to know who works on what.09:44
oansonYou don't have to solve it today.09:44
oansonTomorrow...09:44
oansonlihi, I am assigning it to you, then.09:44
yuli_s1we need another owner for : https://bugs.launchpad.net/dragonflow/+bug/161433409:44
openstackLaunchpad bug 1614334 in DragonFlow "Fail to Install dragonflow" [Medium,New]09:44
lihiOK. Just don't forget to review it on time09:45
DuanKeboyuli, if no one,  I can take it.09:46
*** alexchadin has quit IRC09:46
oansonDuanKebo, about bug 1614334, did you have git installed when this happened?09:46
openstackbug 1614334 in DragonFlow "Fail to Install dragonflow" [Medium,New] https://launchpad.net/bugs/161433409:46
yuli_s1DuanKebo, it is possible that this bug happened because of old libraries09:46
*** alexchadin has joined #openstack-meeting-409:46
oansonyuli_s1, no.09:46
oansonI'll take it. I was just looking at versioning issues this morning, so I may recognise something :)09:47
DuanKeboI think someone else who don't use git may face this problem09:47
*** amotoki has quit IRC09:47
DuanKeboif i git clone the code, it can install successfully.09:47
*** uck has quit IRC09:47
oansonDuanKebo, yes.09:47
DuanKeboyuli, not because of old libs.09:48
oansonThat's what the error message says - it needs access to the remote repository, which it doesn't have with a tarball.09:48
DuanKeboas i have said, when using git clone, it works.09:48
oansonYes09:48
oansonAll right, I'll see what I can find about it.09:48
yuli_s1yesterday i found another issue with performance degradation when creating of hundreds of subnets,09:48
oansonyuli_s1, did you open a bug report?09:49
yuli_s1i have not reported it, i will report it and take it to myself.09:49
oansonVery good.09:49
nick-macontrol plane performance?09:49
oansonAnything else?09:49
oanson#topic Performance09:49
*** openstack changes topic to "Performance (Meeting topic: Dragonflow)"09:50
oansonyuli_s1, any new exciting results?09:50
yuli_s1i was working on performance tests09:50
yuli_s1I have build a following test09:50
yuli_s130+ real servers running full devstack installation09:51
yuli_s1+129 additional df-controllers (each one works with it's own br-int)09:51
yuli_s1(on each server)09:51
yuli_s1in my test I am foing the following09:52
yuli_s1i create a network and 256 subnets for it09:52
yuli_s1currently it takes almost 200 secs to finish the whole tests09:52
yuli_s1yesterday I was checking09:53
DuanKeboAccording to your test, do you think currently, can dragonflow support 4000+ compute nodes? @yuli?09:53
yuli_s1number of rules added to each br-int09:53
yuli_s1when running script that printed me numbers of rules09:53
*** alexchadin has quit IRC09:53
yuli_s1sometimes the counter went down and than up09:54
yuli_s1i suppose, when receiving an update for a network, we recreate dhcp related rules09:54
yuli_s1witch can be a reason for performance degradation09:54
oshidoshiDuanKebo, I think we can support it, but I think we need to run another test first, to measure full-system update when creating ports - it is the more generic use case09:55
DuanKeboyuli, can you report a bug about this?09:55
yuli_s1sure, will do it09:55
DuanKebowhat is full-system update?09:55
yuli_s1DuanKebo, yes09:55
yuli_s1sure09:55
oansonyuli_s1, 256 subnets per server? Or just 1 network with 256 subnets for the entire test?09:56
yuli_s1130 df-controllers per server09:56
oansonBut how many subnets?09:56
yuli_s1in test I create 1 network with 256 subnets09:56
oansonAnd was this core or ML2?09:56
oansonyuli_s1, I see.09:56
yuli_s1sec.09:56
yuli_s1not ml209:57
*** sdake has joined #openstack-meeting-409:57
oansonyuli_s1, I think the test with ML2 is also important - since this will be our standard next version09:58
oanson(hopefully)09:58
yuli_s1sure, I will test it too !09:58
oansonAll right. That's all the time we have09:58
*** limao has quit IRC09:58
oansonLucky no one added an items to the open discussion :)09:58
DuanKebowe'd better test is first. @yuli09:58
yuli_s1ok09:58
oansonAnything else before we finish?09:58
DuanKeboif you have some problem testing it, we can help you09:58
yuli_s1thanks !09:59
yuli_s1DuanKebo, I will try to push the scripts to repository09:59
oansonyuli_s1, that's a great idea!09:59
yuli_s1so you will be able to see the code09:59
nick-malaunchpad blueprints need to be  updated.09:59
oansonnick-ma, yes.09:59
oansonI will go over them for next meeting.10:00
DuanKebook, we will review it.10:00
oansonI think we need more than 2 minutes for them :)10:00
oanson#action oanson Review and summarise blueprints.10:00
oansonAll right. That's our time.10:00
oansonThanks everyone.10:00
oanson#endmeeting10:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:00
openstackMeeting ended Mon Sep  5 10:00:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-09-05-09.01.html10:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-09-05-09.01.txt10:00
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-09-05-09.01.log.html10:00
*** sdake has quit IRC10:01
*** _degorenko|afk is now known as degorenko10:01
*** alexchadin has joined #openstack-meeting-410:03
*** iberezovskiy_off is now known as iberezovskiy10:04
*** amotoki has joined #openstack-meeting-410:05
*** sdake has joined #openstack-meeting-410:07
*** gongysh has quit IRC10:08
*** zenoway has quit IRC10:08
*** zenoway has joined #openstack-meeting-410:12
*** amotoki has quit IRC10:14
*** alexchadin has quit IRC10:14
*** alexchadin has joined #openstack-meeting-410:15
*** qwebirc44830 has quit IRC10:33
*** sdake has quit IRC10:38
*** mbound has joined #openstack-meeting-410:42
*** ihrachys has joined #openstack-meeting-410:43
*** alexchadin has quit IRC10:44
*** mbound has quit IRC10:47
*** vishwanathj has joined #openstack-meeting-410:48
*** markvoelker has joined #openstack-meeting-410:56
*** markvoelker has quit IRC11:00
*** dkb has joined #openstack-meeting-411:09
*** alexchadin has joined #openstack-meeting-411:15
*** sdake has joined #openstack-meeting-411:18
*** amotoki has joined #openstack-meeting-411:18
*** oanson has left #openstack-meeting-411:20
*** sdake has quit IRC11:23
*** uck has joined #openstack-meeting-411:30
*** yuanwei has quit IRC11:31
*** thorst has quit IRC11:34
*** uck has quit IRC11:35
*** thorst has joined #openstack-meeting-411:37
*** caowei has quit IRC11:38
*** liuyulong_ has joined #openstack-meeting-411:41
*** thorst has quit IRC11:41
*** gongysh has joined #openstack-meeting-411:44
*** liuyulong|away has quit IRC11:45
*** amotoki has quit IRC11:46
*** gongysh has quit IRC11:49
*** alexchadin has quit IRC11:50
*** salv-orlando has quit IRC11:51
*** alexchadin has joined #openstack-meeting-411:51
*** salv-orlando has joined #openstack-meeting-411:51
*** markvoelker has joined #openstack-meeting-411:57
*** ishafran has joined #openstack-meeting-411:58
*** dkehn_ has quit IRC12:01
*** markvoelker has quit IRC12:01
*** ivc_ has joined #openstack-meeting-412:01
*** prateek_ has joined #openstack-meeting-412:11
*** prateek has quit IRC12:11
*** parora has joined #openstack-meeting-412:17
*** DuanKebo has quit IRC12:18
*** dkehn_ has joined #openstack-meeting-412:20
*** prateek has joined #openstack-meeting-412:21
*** prateek_ has quit IRC12:21
*** parora has quit IRC12:22
*** kenhui has joined #openstack-meeting-412:25
*** amotoki has joined #openstack-meeting-412:27
*** gongysh has joined #openstack-meeting-412:31
*** ishafran has quit IRC12:33
*** iurygregory has quit IRC12:52
*** iurygregory has joined #openstack-meeting-412:53
*** dkb has quit IRC12:53
*** dkb has joined #openstack-meeting-412:53
*** kenhui has quit IRC13:01
*** zhurong has joined #openstack-meeting-413:02
*** liwei has quit IRC13:03
*** uck has joined #openstack-meeting-413:19
*** alexchadin has quit IRC13:19
*** alexchadin has joined #openstack-meeting-413:20
*** uck has quit IRC13:24
*** lkoranda has quit IRC13:25
*** baoli has joined #openstack-meeting-413:28
*** lkoranda has joined #openstack-meeting-413:28
*** baoli_ has joined #openstack-meeting-413:33
*** baoli has quit IRC13:36
*** links has quit IRC13:38
*** sarob has joined #openstack-meeting-413:40
*** limao has joined #openstack-meeting-413:40
*** gongysh has quit IRC13:42
*** sarob has quit IRC13:44
*** gongysh has joined #openstack-meeting-413:44
*** irenab has quit IRC13:46
*** thorst has joined #openstack-meeting-413:46
*** luis5tb has quit IRC13:52
*** devvesa has joined #openstack-meeting-413:54
*** rbak has joined #openstack-meeting-413:55
*** rbak has quit IRC13:56
*** baoli_ has quit IRC13:56
*** limao has quit IRC13:56
*** baoli has joined #openstack-meeting-413:56
*** vikasc has joined #openstack-meeting-413:57
*** markvoelker has joined #openstack-meeting-413:57
*** vikasc has quit IRC13:58
*** caowei has joined #openstack-meeting-413:58
*** vikasc has joined #openstack-meeting-413:58
*** limao has joined #openstack-meeting-413:58
*** amotoki has quit IRC13:58
*** tonanhngo has joined #openstack-meeting-413:59
*** apuimedo has joined #openstack-meeting-414:00
apuimedo#startmeeting kuryr14:00
openstackMeeting started Mon Sep  5 14:00:55 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: kuryr)"14:00
openstackThe meeting name has been set to 'kuryr'14:00
*** luis5tb has joined #openstack-meeting-414:01
ivc_o/14:01
apuimedoHello and welcome to the first September meeting of Kuryr14:01
apuimedowho's here for the fun?14:01
tonanhngoo/14:01
limaoo/14:01
vikasco/14:01
*** janonymous has joined #openstack-meeting-414:01
apuimedodevvesa: are you gere?14:02
apuimedo*here14:02
*** markvoelker has quit IRC14:03
devvesao/14:03
*** lihi has quit IRC14:03
janonymouso/14:03
apuimedo#info ivc_, tonanhngo, limao, vikasc, devvesa, janonymous and apuimedo in attendance14:04
apuimedo#topic kuryr-lib14:04
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:04
apuimedoSome good work in cleanups for the upcoming release happened in the last week14:04
apuimedo#info all the necessary cleanups for kuryr-lib got merged14:04
apuimedo#link https://review.openstack.org/36197214:05
apuimedo#link https://review.openstack.org/36193714:05
apuimedo#link https://review.openstack.org/36193714:05
apuimedommm14:05
apuimedocrap, I repeated one14:05
apuimedo#link https://review.openstack.org/36207014:05
apuimedonow, on for what's mising14:06
apuimedofor the release14:06
apuimedo#info we are missing the keystonev3 support that I've been working on14:06
*** thorst has quit IRC14:06
*** thorst has joined #openstack-meeting-414:07
apuimedoI'm merging keystone and neutron configuration all inside a neutron section14:07
apuimedoso, like in nova and Neutron, there'll be just on section14:07
apuimedo[neutron]14:07
apuimedothat will contain neutron and neutron auth opts14:07
apuimedothat's all I have on kuryr-lib14:08
tonanhngoI have a question:14:08
apuimedotonanhngo: go ahead14:08
tonanhngoWhen we configure for the VM case, would these config continue to be stored on the VM?14:09
*** claudiub|2 has joined #openstack-meeting-414:09
apuimedono, not this one14:10
apuimedothe only configuration on the VM would be how to reach the kuryr-lib rest server that will then send the calls to neutron14:10
apuimedovikasc is working on that14:10
*** uck has joined #openstack-meeting-414:10
*** uck has quit IRC14:10
apuimedooh, I forgot14:11
*** prateek_ has joined #openstack-meeting-414:11
vikascapuimedo, rpc_server14:11
apuimedovikasc: yes, sorry14:11
*** pablochacin has joined #openstack-meeting-414:12
*** claudiub has quit IRC14:12
apuimedomore questions? topics? under kuryr-lib14:12
apuimedo?14:12
tonanhngook, for Magnum integration, one concern is storing things like account name, password in a config file on the VM14:12
vikascjunst an info14:12
vikasci have updated testing for rest driver in kuryr-lib https://review.openstack.org/#/c/342624/14:12
apuimedotonanhngo: what's the current solution?14:12
apuimedothere should probably be some auth between kuryr-libnetwork remote driver in the VMs and the rpc server14:13
apuimedoeither that, or whitelisting origin addresses14:13
*** irenab has joined #openstack-meeting-414:13
tonanhngoBefore Kuryr, Magnum does not store any service password on the VM14:13
*** prateek has quit IRC14:14
tonanhngoWe leave it to the users to enter these, for security14:14
apuimedotonanhngo: how does the kubernetes load balancer plugin that talks to Neutron work then?14:14
tonanhngoIt uses the user credential14:14
tonanhngobut now, it seems we need to give the services password, like Neutron, rabbit14:15
*** thorst has quit IRC14:15
apuimedowe do not need rabbit on the VMs14:15
tonanhngofor the openvswitch agent?14:16
apuimedothat runs on the host14:16
apuimedonot on the VMs14:16
apuimedothe only credentials would be something so that only the remote driver talks to the kuryr rpc server14:16
tonanhngook good, then is there a security concern in this case?14:16
apuimedowell, we have to decide how to do it14:17
apuimedoit's still undefined14:17
apuimedofirst we have to get it running, then we'll restrict access14:17
tonanhngosounds good, I am just voicing a concern from what we see.14:17
apuimedotonanhngo: and you do well to keep it in our minds14:18
*** gongysh has quit IRC14:18
apuimedotonanhngo: can you remind me how does the Kubernetes on Magnum, which runs on a VM, access the Neutron API server14:19
apuimedowhich runs on the overlay14:19
apuimedo?14:19
tonanhngoThe Kubernetes plugin uses the user credential to authenticate with Keystone and get a session14:19
*** parora has joined #openstack-meeting-414:19
tonanhngothen the client just talks to Neutron in that session14:20
tonanhngoIt requires the service endpoints, so that's what Magnum configures14:20
apuimedoso magnum makes keystone and neutron available in the overlay14:20
tonanhngofor the user credential, Magnum does not handle it.  We leave it to the user to log into the node and type in the credential14:21
*** zhurong has quit IRC14:21
tonanhngoYes, the user VM can access the services14:21
tonanhngoI haven't checked from the Flannel overlay, but I think the pods can reach the services also, but the pods would not have the credential14:22
*** prateek_ has quit IRC14:22
apuimedook. I'll try to set up a devstack to check it out14:22
apuimedothanks tonanhngo14:23
tonanhngoThere is a concern that the pods can reach the config files and get the credential, but we don't deal with that since that's how Kubernetes set it up14:23
vikascthanks tonanhngo14:23
janonymousI guess authentication code is for reference: https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/openstack/openstack.go#L21914:23
tonanhngonp14:23
apuimedo#action apuimedo, vikas to work out the auth remotedriver-> rpc driver14:23
apuimedothanks janonymous14:23
apuimedo#link https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/openstack/openstack.go#L21914:23
apuimedo#topic kuryr-libnetwork14:24
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:24
apuimedo#info the contents of the 'common' package have been moved to the base package as agreed, thanks to vikas' patch https://review.openstack.org/36156714:24
apuimedosome code cleanups as well14:25
apuimedo#link https://review.openstack.org/36285714:25
apuimedo#info sample config file generation is now generated by a script that prevents common mistakes when using oslo-config-generator14:26
apuimedo#link https://review.openstack.org/36424014:26
apuimedothis will prevent the wrong config being generated when you are working on config patches14:26
apuimedo#info limao fixed the MTU bug that meant that MTU was not being retrieved from Neutron14:27
apuimedo#link https://review.openstack.org/#/c/355714/14:27
apuimedo#info Docker 1.9 compat patch was merged as well https://review.openstack.org/35276814:27
apuimedo#info devstack should now be back into a working state14:28
apuimedolimao: did you try https://review.openstack.org/36533614:28
apuimedoI wonder if the job now completes successfully14:28
limaojob has not passed yet14:29
limaoI will check them14:29
apuimedolimao: thanks14:30
*** salv-orl_ has joined #openstack-meeting-414:30
janonymousi will help too..14:30
apuimedo#action limao and janonymous to check the rally jobs14:30
apuimedo:-)14:30
limao:-)14:30
apuimedo#action vikasc apuimedo to review https://review.openstack.org/#/c/363414/114:31
apuimedowe had originally screwed up the move from 2376 to 2375014:32
*** salv-orlando has quit IRC14:32
apuimedoanything else about kuryr-libnetwork?14:32
apuimedoalright, moving on14:33
apuimedo#topic kuryr-kubernetes14:33
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:33
apuimedo#info last Thursday a kuryr-kubernetes videoconf meeting was held14:34
apuimedo#info More information about it can be found on the mailing list14:34
flaper87Are there recordings of that meeting?14:34
apuimedoflaper87: can be provided on demand14:36
apuimedo:-)14:36
apuimedobut I made quite extensive meeting points14:36
*** irenab has quit IRC14:36
apuimedoin the mailing list14:36
vikascapuimedo, agree14:37
*** irenab has joined #openstack-meeting-414:37
apuimedo#info devvesa is working on the python3 upstreaming14:37
apuimedo#info ivc_ is working on a py2/py3 eventlet PoC that matches its features14:37
apuimedowe're reviewing both14:38
*** armax has joined #openstack-meeting-414:38
apuimedo#info There is a new spec proposal for the watcher/translator interaction for kuryr-kubernetes14:38
apuimedo#link https://review.openstack.org/36560014:38
apuimedoI appreciate reviews14:39
devvesastill have to take a deep look, but I like it :)14:39
apuimedospecially from devvesa and ivc_, since they are implementing14:39
apuimedocool14:39
apuimedowe should be studying studying also the Magnum deployment for the kubernetes integration14:40
ivc_+1 devvesa. tho need to take a deeper look at it14:40
apuimedo(what I was saying earlier was more for kuryr-libnetwork)14:40
*** armax has quit IRC14:40
apuimedo#action apuimedo, vikas to review https://review.openstack.org/36375814:40
*** irenab has quit IRC14:40
vikascsure14:40
devvesabtw, this patch introduces kind of first approach14:41
apuimedo#action apuimedo, devvesa, ivc to come up with a functional testing approach for the gates14:41
devvesahttps://review.openstack.org/#/c/363758/14:41
*** irenab has joined #openstack-meeting-414:41
apuimedo#link https://review.openstack.org/#/c/363758/14:41
apuimedothanks limao for getting so fast to testing the libnetwork gates :-)14:42
limao:-)14:42
apuimedoalright, does anybody else have stuff for kubernetes integration?14:42
devvesafor functional testing first we should create a devstack plugin to deploy, right?14:42
apuimedodevvesa: yes14:42
devvesaany volunteer in the room?? :D14:43
apuimedoprobably minikube14:43
apuimedo:-)14:43
ivc_minukube is virtualbox based i'm afraid14:43
devvesaivc_ yes14:43
apuimedooh, sorry, ivc_, I meant hyperkube14:43
apuimedoxD14:43
ivc_or more specifically its vagrant14:43
apuimedoI prefer bare-metal for starters14:44
apuimedoso hyperkube should serve us14:44
devvesaI think this script can run on local14:44
devvesahttps://github.com/kubernetes/kubernetes/blob/master/hack/local-up-cluster.sh14:44
devvesawithout nothing else than Go 1.614:44
devvesaBut I haven't tried so far.14:44
apuimedodevvesa: compiling and running all in the gate may be too resource intensive14:44
ivc_i think we can just go with hyperkube14:44
devvesaWhat's true is that a functional testing is mandatory14:44
janonymous+8gb ram for build , 64bit os14:44
apuimedothat's far too much14:45
devvesa:(14:45
apuimedoI propose devstack plugin with hyperkube14:45
ivc_+1 on that14:45
apuimedoand that the kubelet container mounts the CNI driver on a volume14:45
devvesalast time I looked at, I could not find the command that spawns hyperkube anymore14:45
apuimedoreally?14:45
pablochacinapuimedo: I think it is deprecated14:45
apuimedo#action apuimedo to check hyperkube for signs of life14:45
apuimedopablochacin: that makes me a bit grumpy14:46
devvesa#action apuimedo ask to Kubernetes-dev on Slack :)14:46
apuimedoinstalling Slack again...14:46
apuimedook, ok14:46
apuimedoI'll get to that too14:46
devvesaI can do it, no problem14:46
*** zz_ja has quit IRC14:46
apuimedo#action devvesa to ask about hyperkube on kubernetes-dev slack14:46
ivc_i've got hyperkube-based deployment on my poc. i'll be adding details on that to my research doc14:46
apuimedothanks devvesa14:46
janonymousminikube maybe but not sure14:47
*** zz_ja has joined #openstack-meeting-414:47
apuimedolet's try to come up with the necessary info to take a decision for next Monday ;-)14:47
vikasc+114:47
apuimedo#info next meeting to discuss and decide the testing approach and tools14:47
apuimedoanything else?14:48
irenabapuimedo: yes14:48
irenabjust procedural question about docs location14:48
apuimedo#info Usage docs should go on kuryr-kubernetes / kuryr-libnetwork14:48
irenabshould devrefs be hosted on the kuryr-k8s or kuryr repo?14:49
apuimedo#info specs on openstack/kuryr14:49
irenabapuimedo: thanks14:49
apuimedoif everybody disagrees we can change it though14:49
apuimedoI just want to minimize the effort to add info for now14:49
irenabapuimedo: design on k8s/libnetwork14:49
apuimedoand approving the specs on one place, making it easier to refer to one another seems more comfy to me14:50
apuimedoirenab: please, elaborate14:50
irenabapuimedo: specs are not devrefs14:50
irenabdevrefs are more design14:50
irenabspec are more requirements14:50
apuimedoirenab: the distinction gets a bit lost on me, sorry14:51
apuimedoso probably my last patch is more of a devref14:51
irenabspec is about what and devref is about how14:51
irenabat least its how I get it14:51
apuimedoirenab: I'd be grateful if you could help me understand it with examples of our current doc14:51
apuimedoit can be offline14:51
apuimedoand I'll send an email to the mailing list14:51
devvesawe may need to add new directory for 'why'14:51
apuimedoso we can all wigh in14:51
apuimedoand decide14:51
devvesa(sorry, bad jokes)14:51
apuimedodevvesa: :-)14:52
devvesa(you know I support you, Irena)14:52
irenabapuimedo: sure, but just for now, devrefs are to be in specific or the general kuryr one?14:52
apuimedoirenab: until we take it to the ML yes14:52
apuimedothe current status was all devref and specs go to openstack/kuryr14:52
apuimedobut I agree that the implementation heavy documentation will probably live better in kuryr-libnetwork and kuryr-k8s14:53
irenabas long as there is guideline, it does not matter too much14:53
apuimedo;-)14:53
apuimedoI guess most of us have the four repos cloned in any case14:53
*** caowei has quit IRC14:53
apuimedoso we'll find the better fit14:53
apuimedobut it's not a showstopper, I hope14:53
apuimedobut let's have it fixed soon14:53
apuimedoother questions/comments?14:54
irenabapuimedo: question about new added sub project for storage14:54
apuimedoI'm not getting to the address pairs point in the agenda since icoughlan couldn't attend14:54
apuimedoirenab: go ahead14:54
apuimedo#action gsagie to get fuxi people on the weekly meetings so that they also participate :-)14:55
irenabdoes it  has its own core reviewers? How it is going to be managed, blueprints, specs, etc.?14:55
apuimedoirenab: it does not have its own core reviewers yet14:55
apuimedothe idea, just as with libnetwork and kubernetes14:55
apuimedois that they can get their own cores14:55
apuimedobut kuryr-core people will keep core over the repo as well14:55
apuimedoirenab: oh, sorry, correction, the main developer is a core14:56
apuimedoZhang Ni14:56
irenabapuimedo: and for specs, devrefs, will be the same policy like with k8s/libnetwork?14:56
apuimedoso it would be good if he can join the weekly meetings14:56
apuimedoirenab: we should try to have the same policy for all14:57
irenabapuimedo: makes sense14:57
apuimedoIt should make us be flexible enough14:57
apuimedo#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:57
apuimedoany other open discussion item in these last three minutes?14:57
apuimedoI'd like to remind everybody about the mailing list thread to discuss and propose topics for the summit work sessions14:58
devvesaThanks for the agenda, btw14:58
apuimedodevvesa: you're most welcome14:59
devvesaI think that a reminder and agenda suggestions can provide attention from other projects/people14:59
apuimedoalthough I should have published it the latest on friday14:59
apuimedoindeed14:59
apuimedo#action apuimedo to post the agenda by Thursday and ML reminder so people have time to add items14:59
devvesaWe should kind of improve our visibility. Devstack/functional test is an example that we need collaborators15:00
devvesaHowever, I ignore how to do it15:00
apuimedodevvesa: any proposal?15:00
apuimedoah, ok15:00
apuimedo:-)15:00
apuimedowell, increasing ML communication is the easiest way15:00
apuimedoalso, if you are trying things15:00
devvesayes. and first one15:00
apuimedoplease blog and twit about it!15:00
devvesathat was another idea... but I am afraid I have no time to blog properly15:01
apuimedowe all love to know what everybody else is doing15:01
apuimedodevvesa: then twit ;-)15:01
apuimedofor example15:01
devvesaa blog post is an amount of work considerable15:01
*** luis5tb has quit IRC15:01
*** irenab has quit IRC15:01
devvesaOh, my twitter account is only about cycling :D I'll have to create another account15:01
apuimedogotten #openstack #kuryr #kubernetes python3 upstreaming to work with pod translation15:01
apuimedo:-)15:01
apuimedodevvesa: do it then ;-)15:02
apuimedoor I'll make a kurry logo on bicycle15:02
apuimedoThank you all for joining!15:02
devvesathanks!15:02
apuimedohave a nice and productive week15:02
apuimedo#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Mon Sep  5 15:02:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-09-05-14.00.html15:02
janonymousthanks!15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-09-05-14.00.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-09-05-14.00.log.html15:02
*** nkrinner is now known as nkrinner_afk15:07
*** dkb has quit IRC15:09
*** dkb has joined #openstack-meeting-415:10
*** thorst has joined #openstack-meeting-415:12
*** pablochacin has left #openstack-meeting-415:13
*** baoli has quit IRC15:19
*** thorst has quit IRC15:20
*** caowei has joined #openstack-meeting-415:21
*** caowei has quit IRC15:25
*** armax has joined #openstack-meeting-415:26
*** vishwanathj has quit IRC15:26
*** devvesa has quit IRC15:28
*** pcaruana has quit IRC15:36
*** dshakhray has quit IRC15:41
*** rainya has joined #openstack-meeting-415:42
*** devvesa has joined #openstack-meeting-415:42
*** dcwangmit01 has joined #openstack-meeting-415:44
*** TheJulia_ has joined #openstack-meeting-415:47
*** aimeeu__ has joined #openstack-meeting-415:47
*** csatari_ has joined #openstack-meeting-415:47
*** kozhukalov_ has joined #openstack-meeting-415:47
*** ChrisPriceAB_ has joined #openstack-meeting-415:47
*** dham1_ has joined #openstack-meeting-415:47
*** izaakk_ has joined #openstack-meeting-415:47
*** bnemec has joined #openstack-meeting-415:47
*** patrickeast_ has joined #openstack-meeting-415:47
*** serverascode_ has joined #openstack-meeting-415:47
*** carl_baldwin_ has joined #openstack-meeting-415:47
*** sc68cal_ has joined #openstack-meeting-415:48
*** Kiall_ has joined #openstack-meeting-415:48
*** sulo_ has joined #openstack-meeting-415:48
*** alexchadin has quit IRC15:48
*** arif-ali_ has joined #openstack-meeting-415:48
*** wolsen has quit IRC15:48
*** dham1 has quit IRC15:48
*** ediardo has quit IRC15:48
*** mjturek has quit IRC15:48
*** skath has quit IRC15:48
*** serverascode has quit IRC15:48
*** tdurakov has quit IRC15:48
*** mtreinish has quit IRC15:48
*** margaret has quit IRC15:48
*** briancurtin has quit IRC15:48
*** arif-ali has quit IRC15:48
*** melwitt has quit IRC15:48
*** sweston has quit IRC15:48
*** beekneemech has quit IRC15:48
*** ChrisPriceAB has quit IRC15:49
*** cargonza has quit IRC15:49
*** aimeeu has quit IRC15:49
*** sc68cal has quit IRC15:49
*** patrickeast has quit IRC15:49
*** kozhukalov has quit IRC15:49
*** devvesa has quit IRC15:49
*** carl_baldwin has quit IRC15:49
*** TheJulia has quit IRC15:49
*** sulo has quit IRC15:49
*** csatari has quit IRC15:49
*** Kiall has quit IRC15:49
*** cinerama has quit IRC15:49
*** izaakk has quit IRC15:49
*** fungi has quit IRC15:49
*** harlowja_ has quit IRC15:49
*** dcwangmit01_ has quit IRC15:49
*** arif-ali_ is now known as arif-ali15:49
*** mtreinish has joined #openstack-meeting-415:49
*** cinerama has joined #openstack-meeting-415:49
*** shihanzhang has quit IRC15:49
*** devvesa has joined #openstack-meeting-415:49
*** mjturek has joined #openstack-meeting-415:49
*** tdurakov has joined #openstack-meeting-415:50
*** aimeeu__ is now known as aimeeu15:50
*** shihanzhang has joined #openstack-meeting-415:50
*** carl_baldwin_ is now known as carl_baldwin15:50
*** fungi has joined #openstack-meeting-415:50
*** TheJulia_ is now known as TheJulia15:50
*** izaakk_ is now known as izaakk15:50
*** patrickeast_ is now known as patrickeast15:51
*** devvesa has left #openstack-meeting-415:51
*** melwitt has joined #openstack-meeting-415:51
*** csatari_ is now known as csatari15:51
*** kozhukalov_ is now known as kozhukalov15:52
*** melwitt is now known as Guest7823615:52
*** dham1_ is now known as dham115:52
*** vishwanathj has joined #openstack-meeting-415:54
*** ChrisPriceAB_ is now known as ChrisPriceAB15:54
*** vishwanathj has quit IRC15:54
*** skath has joined #openstack-meeting-415:56
*** serverascode_ is now known as serverascode15:57
*** sarob has joined #openstack-meeting-415:57
*** markvoelker has joined #openstack-meeting-415:58
*** sweston has joined #openstack-meeting-415:58
*** wolsen has joined #openstack-meeting-416:00
*** prateek_ has joined #openstack-meeting-416:01
*** ediardo has joined #openstack-meeting-416:02
*** sarob has quit IRC16:02
*** cargonza has joined #openstack-meeting-416:02
*** markvoelker has quit IRC16:03
*** matrohon has quit IRC16:03
*** briancurtin has joined #openstack-meeting-416:04
*** parora has quit IRC16:04
*** margaret has joined #openstack-meeting-416:05
*** armax has quit IRC16:11
*** itisha has joined #openstack-meeting-416:16
*** thorst has joined #openstack-meeting-416:18
*** thorst has quit IRC16:26
*** ttx has quit IRC16:29
*** ttx has joined #openstack-meeting-416:29
*** spotz_zzz is now known as spotz16:32
*** degorenko is now known as _degorenko|afk16:38
*** oshidoshi has quit IRC16:39
*** sshnaidm is now known as sshnaidm|afk16:44
*** thorst has joined #openstack-meeting-416:44
*** thorst has quit IRC16:49
*** thorst has joined #openstack-meeting-416:50
*** gnuoy has joined #openstack-meeting-416:58
*** neiljerram has joined #openstack-meeting-416:58
*** thorst has quit IRC16:58
*** tonanhngo has quit IRC16:59
*** neiljerram has quit IRC17:01
jamespageo/17:02
gnuoy\o17:02
tinwoodo/17:02
jamespage#startmeeting charms17:03
openstackMeeting started Mon Sep  5 17:03:19 2016 UTC and is due to finish in 60 minutes.  The chair is jamespage. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: charms)"17:03
openstackThe meeting name has been set to 'charms'17:03
jamespagemight be a quiet one today17:03
jamespagehttps://etherpad.openstack.org/p/openstack-charms-weekly-meeting-2016090517:03
jamespage#topic Review ACTION points from previous meeting17:03
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:03
jamespagejamespage include the openstack-on-lxd README as a section in dev guide17:03
jamespagethat's still WIP - I parked it last week for a bit17:04
jamespagejamespage Discuss future of g-ss-s charm17:04
jamespagesome discussion on that - we need to plan for the work to make it part of glance, but right now we need to adopt the current codebase in full as there are alot of challenges atm17:04
jamespagejamespage request Barcelona Design Summit slots17:04
jamespageI requested our slots - we need to plan to fill them17:05
jamespagehttps://etherpad.openstack.org/p/ocata-charm-summit-planning17:05
jamespage#link https://etherpad.openstack.org/p/ocata-charm-summit-planning17:05
jamespage#topic State of Development for next Charm Release17:05
*** ddellav has joined #openstack-meeting-417:05
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:05
gnuoyjamespage, I don;t think the 2nd item on there isn't quiet true17:06
jamespagegnuoy, no?17:06
*** dkb has quit IRC17:06
jamespagewhat's your take?17:06
*** dkb has joined #openstack-meeting-417:06
gnuoyjamespage, oh, I'm getting myself confused. Its the dashboard that can now be related to a db for cookie storage. ignore me17:07
jamespagenp17:07
jamespageokies17:07
jamespageI find myself without the link for high priority bugs...17:07
gnuoyjamespage, we've recently just been asking if anyone is dealing with any nasties17:08
jamespageoh and I'm ahead of things anyway17:08
jamespageok state of development17:08
gnuoyI'm working on generating some cookie-cutter charms to make SDN development easier17:09
jamespagewe're a way off freeze yet but we need to maintain velocity; I need to take a run through the approved specs to see what's still outstanding as well17:09
jamespagegnuoy, +117:09
jamespage#action jamespage to review current newton specs against plan17:09
tinwoodI've simplified how to use charms.openstack to build new charms.17:09
jamespagetinwood, nice work tinwood17:09
tinwoodwell it's WIP still, but very close.17:09
jamespagetinwood, can I action you with charm guide updates when that's landed?17:09
tinwoodyes, happy to.  i was thinking of that too.17:10
*** rainya has quit IRC17:10
jamespage#action tinwood to update charm guide with refactored charms_openstack bits17:10
*** ihrachys has quit IRC17:10
jamespage#topic High Priority Bugs17:10
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:10
jamespageOK I had a nasty one17:10
jamespagebug 161832117:11
openstackbug 1618321 in nova-cloud-controller (Juju Charms Collection) "mysql shared-db relation not creating successfully under certain conditions" [Critical,Fix committed] https://launchpad.net/bugs/1618321 - Assigned to James Page (james-page)17:11
*** sulo_ is now known as sulo17:11
jamespageThat's fixed in the master branch; pending smoke test failure resolution in OSCI before we land the cherry pick for stable branch17:11
jamespageanyone else aware of anything nasty?17:11
tinwoodnope17:11
gnuoyjamespage, how's the, juju hostname too long one?17:11
*** zenoway has quit IRC17:12
jamespagehttps://bugs.launchpad.net/juju/+bug/161560117:13
openstackLaunchpad bug 1615601 in juju "2.0 beta 14 + openstack: generated hostnames exceed 255 byte limit" [High,Triaged]17:13
jamespagestill outstanding afaict17:13
jamespagescheduled for juju 2.0 but alot is17:13
jamespage#topic Openstack Events17:13
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:13
jamespageok so summit not far off17:13
jamespagemy talk submissions got rejected, so just on a panel about distribution methods \o/17:14
jamespageI've submitted out request for fishbowl and workroom sessions17:14
jamespagewe'll see what we get17:14
tinwoodokay.  sounds interesting17:14
jamespageneed to give those some thought - please can people17:14
jamespage#link https://etherpad.openstack.org/p/ocata-charm-summit-planning17:14
jamespageadd to that pad on ideas for discussion for next cycle; I put some in already based on things we need todo across the charms17:15
*** oshidoshi has joined #openstack-meeting-417:16
tinwoodis it a 'anything we can think of' and then whittle it down thing?17:16
jamespageyeah that's ok for now17:16
jamespage#topic Open Discussion17:17
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:17
jamespageokies so anything else?17:17
tinwoodnope, I'm good.17:17
*** rainya has joined #openstack-meeting-417:17
jamespagegnuoy, ?17:17
*** spotz is now known as spotz_zzz17:17
gnuoynot from me17:17
jamespageokies17:17
jamespage#endmeeting17:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:17
openstackMeeting ended Mon Sep  5 17:17:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-09-05-17.03.html17:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-09-05-17.03.txt17:17
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-09-05-17.03.log.html17:17
gnuoythanks jamespage17:17
tinwoodthanks jamespage17:17
*** rainya has quit IRC17:18
*** yamahata has quit IRC17:22
*** armax has joined #openstack-meeting-417:24
*** armax has quit IRC17:24
*** mbound has joined #openstack-meeting-417:25
*** spotz_zzz is now known as spotz17:25
*** armax has joined #openstack-meeting-417:26
*** armax has quit IRC17:27
*** armax has joined #openstack-meeting-417:28
*** armax has quit IRC17:28
*** armax has joined #openstack-meeting-417:30
*** armax has quit IRC17:31
*** ivc_ has left #openstack-meeting-417:32
*** dshakhray has joined #openstack-meeting-417:33
*** armax has joined #openstack-meeting-417:34
*** armax has quit IRC17:34
*** zenoway has joined #openstack-meeting-417:35
*** armax has joined #openstack-meeting-417:36
*** armax has quit IRC17:36
*** armax has joined #openstack-meeting-417:37
*** zenoway has quit IRC17:39
*** armax has quit IRC17:42
*** sambetts is now known as sambetts|afk17:52
*** thorst has joined #openstack-meeting-417:56
*** markvoelker has joined #openstack-meeting-417:59
*** parora has joined #openstack-meeting-418:02
*** thorst has quit IRC18:03
*** markvoelker has quit IRC18:03
*** rainya has joined #openstack-meeting-418:04
*** prateek has joined #openstack-meeting-418:05
*** prateek_ has quit IRC18:05
*** ansmith has joined #openstack-meeting-418:06
*** parora has quit IRC18:07
*** admcleod has quit IRC18:13
*** ansmith has quit IRC18:14
*** admcleod has joined #openstack-meeting-418:14
*** admcleod has quit IRC18:15
*** admcleod has joined #openstack-meeting-418:15
*** prateek has quit IRC18:17
*** bknudson has left #openstack-meeting-418:25
*** pcaruana has joined #openstack-meeting-418:31
*** rainya has quit IRC18:39
*** mbound has quit IRC18:44
*** thorst has joined #openstack-meeting-419:00
*** dkb has quit IRC19:03
*** dkb has joined #openstack-meeting-419:03
*** thorst has quit IRC19:08
*** spotz is now known as spotz_zzz19:13
*** armax has joined #openstack-meeting-419:19
*** armax has quit IRC19:19
*** armax has joined #openstack-meeting-419:21
*** rods has quit IRC19:21
*** oshidoshi has quit IRC19:25
*** armax has quit IRC19:25
*** oshidoshi has joined #openstack-meeting-419:25
*** armax has joined #openstack-meeting-419:27
*** oshidoshi has quit IRC19:30
*** banix has joined #openstack-meeting-419:30
*** pcaruana has quit IRC19:52
*** yamahata has joined #openstack-meeting-419:58
*** sarob has joined #openstack-meeting-419:59
*** markvoelker has joined #openstack-meeting-420:00
*** ativelkov_ has joined #openstack-meeting-420:02
*** FrankZha- has joined #openstack-meeting-420:02
*** margaret_ has joined #openstack-meeting-420:02
*** pbourke_ has joined #openstack-meeting-420:03
*** sarob has quit IRC20:04
*** dshakhray_ has joined #openstack-meeting-420:04
*** markvoelker has quit IRC20:05
*** admcleod_ has joined #openstack-meeting-420:05
*** evrardjp_ has joined #openstack-meeting-420:05
*** thorst has joined #openstack-meeting-420:07
*** banix has quit IRC20:08
*** HenryG_ has joined #openstack-meeting-420:08
*** admcleod has quit IRC20:10
*** dshakhray has quit IRC20:10
*** margaret has quit IRC20:10
*** briancurtin has quit IRC20:10
*** csatari has quit IRC20:10
*** pbourke has quit IRC20:10
*** dolphm has quit IRC20:10
*** evrardjp has quit IRC20:10
*** d34dh0r53 has quit IRC20:10
*** FrankZhang has quit IRC20:10
*** ativelkov has quit IRC20:10
*** HenryG has quit IRC20:10
*** aglarendil has quit IRC20:10
*** alex_didenko has quit IRC20:10
*** meteorfox has quit IRC20:10
*** amit213 has quit IRC20:10
*** pasquier-s has quit IRC20:10
*** ashtokolov has quit IRC20:10
*** Adri2000 has quit IRC20:10
*** raddaoui has quit IRC20:10
*** dpyzhov has quit IRC20:10
*** fkautz has quit IRC20:10
*** cholcombe has quit IRC20:10
*** evrardjp_ is now known as evrardjp20:10
*** margaret_ is now known as margaret20:10
*** dolphm has joined #openstack-meeting-420:10
*** d34dh0r53 has joined #openstack-meeting-420:10
*** briancurtin has joined #openstack-meeting-420:11
*** csatari has joined #openstack-meeting-420:11
*** aglarendil has joined #openstack-meeting-420:11
*** alex_didenko has joined #openstack-meeting-420:11
*** meteorfox has joined #openstack-meeting-420:11
*** amit213 has joined #openstack-meeting-420:11
*** pasquier-s has joined #openstack-meeting-420:11
*** ashtokolov has joined #openstack-meeting-420:11
*** Adri2000 has joined #openstack-meeting-420:11
*** raddaoui has joined #openstack-meeting-420:11
*** dpyzhov has joined #openstack-meeting-420:11
*** fkautz has joined #openstack-meeting-420:11
*** cholcombe has joined #openstack-meeting-420:11
*** fkautz has quit IRC20:12
*** briancurtin has quit IRC20:12
*** csatari has quit IRC20:12
*** raddaoui has quit IRC20:12
*** thorst has quit IRC20:13
*** alex_didenko has quit IRC20:14
*** meteorfox has quit IRC20:14
*** sdake has joined #openstack-meeting-420:15
*** amit213 has quit IRC20:16
*** briancurtin has joined #openstack-meeting-420:18
*** alex_didenko has joined #openstack-meeting-420:24
*** meteorfox has joined #openstack-meeting-420:24
*** sdake has quit IRC20:25
*** csatari has joined #openstack-meeting-420:25
*** briancurtin has quit IRC20:25
*** amit213 has joined #openstack-meeting-420:25
*** fkautz has joined #openstack-meeting-420:26
*** mbound has joined #openstack-meeting-420:26
*** marst has quit IRC20:26
*** briancurtin has joined #openstack-meeting-420:26
*** raddaoui has joined #openstack-meeting-420:27
*** salv-orlando has joined #openstack-meeting-420:29
*** mbound has quit IRC20:30
*** salv-orl_ has quit IRC20:32
*** iurygregory has quit IRC20:34
*** bobh has joined #openstack-meeting-420:34
*** Jeffrey4l has quit IRC20:34
*** Jeffrey4l has joined #openstack-meeting-420:36
*** ansmith has joined #openstack-meeting-420:36
*** dkehn_ has quit IRC20:36
*** ansmith has quit IRC20:40
*** bobh has quit IRC20:54
*** bobh has joined #openstack-meeting-420:56
*** banix has joined #openstack-meeting-420:57
*** berendt has quit IRC20:58
*** banix has quit IRC20:59
*** banix has joined #openstack-meeting-421:00
*** bobh has quit IRC21:15
*** dkb has quit IRC21:19
*** dkb has joined #openstack-meeting-421:19
*** iurygregory has joined #openstack-meeting-421:29
*** thorst has joined #openstack-meeting-421:30
*** sdake has joined #openstack-meeting-421:34
*** thorst has quit IRC21:39
*** banix has quit IRC21:45
*** sdake has quit IRC21:52
*** markvoelker has joined #openstack-meeting-422:00
*** markvoelker has quit IRC22:06
*** dtardivel has quit IRC22:17
*** marst has joined #openstack-meeting-422:21
*** thorst has joined #openstack-meeting-422:36
*** spotz_zzz is now known as spotz22:40
*** claudiub|2 has quit IRC22:44
*** thorst has quit IRC22:45
*** hshan has quit IRC22:52
*** vishwanathj has joined #openstack-meeting-422:55
*** vishwanathj has quit IRC22:55
*** hippiepete has quit IRC22:58
*** dkb has quit IRC23:15
*** dkb has joined #openstack-meeting-423:16
*** limao has quit IRC23:18
*** baoli has joined #openstack-meeting-423:30
*** baoli has quit IRC23:30
*** spotz is now known as spotz_zzz23:32
*** JRobinson__ has joined #openstack-meeting-423:36
*** yamahata has quit IRC23:38
*** thorst has joined #openstack-meeting-423:41
*** gongysh has joined #openstack-meeting-423:46
*** thorst has quit IRC23:49

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!