Monday, 2016-02-15

*** thorst has joined #openstack-meeting-400:05
*** thorst has quit IRC00:05
*** iyamahat has joined #openstack-meeting-400:15
*** reedip_away is now known as reedip00:15
*** baoli has joined #openstack-meeting-400:16
*** salv-orlando has quit IRC00:21
*** yamamoto_ has joined #openstack-meeting-400:27
*** baoli has quit IRC00:27
*** baoli has joined #openstack-meeting-400:28
*** woodard has joined #openstack-meeting-400:32
*** yamamoto_ has quit IRC00:33
*** sdake has quit IRC00:42
*** woodard has quit IRC00:43
*** iceyao has joined #openstack-meeting-400:51
*** markvoelker has joined #openstack-meeting-400:55
*** baoli has quit IRC00:58
*** sdake has joined #openstack-meeting-400:58
*** baoli has joined #openstack-meeting-400:58
*** markvoelker has quit IRC01:00
*** emagana has quit IRC01:02
*** dingboopt has joined #openstack-meeting-401:03
*** thorst has joined #openstack-meeting-401:06
*** May-meimei has joined #openstack-meeting-401:07
*** bobh has joined #openstack-meeting-401:11
*** thorst has quit IRC01:14
*** emagana has joined #openstack-meeting-401:17
*** emagana has quit IRC01:21
*** stanchan has quit IRC01:22
*** salv-orlando has joined #openstack-meeting-401:29
*** baohua has joined #openstack-meeting-401:30
*** salv-orlando has quit IRC01:31
*** sdake_ has joined #openstack-meeting-401:34
*** sdake has quit IRC01:36
*** ajmiller has joined #openstack-meeting-401:43
*** ajmiller_ has joined #openstack-meeting-401:44
*** Jeffrey4l has joined #openstack-meeting-401:47
*** emagana has joined #openstack-meeting-401:47
*** ajmiller has quit IRC01:47
*** emagana has quit IRC01:52
*** sdake_ has quit IRC01:53
*** ajmiller_ has quit IRC01:56
*** zhurong has joined #openstack-meeting-401:56
*** ajmiller_ has joined #openstack-meeting-401:56
*** baoli has quit IRC02:01
*** baoli has joined #openstack-meeting-402:02
*** thorst has joined #openstack-meeting-402:12
*** bobh has quit IRC02:13
*** emagana has joined #openstack-meeting-402:18
*** thorst has quit IRC02:19
*** kebray has joined #openstack-meeting-402:20
*** xingchao has joined #openstack-meeting-402:21
*** iyamahat has quit IRC02:21
*** emagana has quit IRC02:22
*** bobh has joined #openstack-meeting-402:23
*** xingchao has quit IRC02:25
*** baoli has quit IRC02:26
*** sdake has joined #openstack-meeting-402:31
*** DuanKebo has joined #openstack-meeting-402:35
*** baoli has joined #openstack-meeting-402:35
*** baoli has quit IRC02:45
*** baoli has joined #openstack-meeting-402:47
*** emagana has joined #openstack-meeting-402:48
*** emagana has quit IRC02:52
*** markvoelker has joined #openstack-meeting-402:56
*** yamamoto_ has joined #openstack-meeting-402:59
*** MarkAtwood has quit IRC02:59
*** MarkAtwood has joined #openstack-meeting-403:00
*** ajmiller_ has quit IRC03:00
*** markvoelker has quit IRC03:00
*** DuanKebo has quit IRC03:01
*** bobh has quit IRC03:11
*** zhurong has quit IRC03:15
*** zhurong has joined #openstack-meeting-403:16
*** thorst has joined #openstack-meeting-403:18
*** emagana has joined #openstack-meeting-403:19
*** emagana has quit IRC03:23
*** thorst has quit IRC03:25
*** baoli has quit IRC03:28
*** baoli has joined #openstack-meeting-403:35
*** coolsvap|away is now known as coolsvap03:36
*** zhurong has quit IRC03:40
*** zhurong has joined #openstack-meeting-403:40
*** baoli has quit IRC03:48
*** emagana has joined #openstack-meeting-403:49
*** cfarquhar has quit IRC03:52
*** bobh has joined #openstack-meeting-403:53
*** cfarquhar has joined #openstack-meeting-403:54
*** cfarquhar has quit IRC03:54
*** cfarquhar has joined #openstack-meeting-403:54
*** emagana has quit IRC03:54
*** coolsvap is now known as coolsvap|away03:59
*** baoli has joined #openstack-meeting-404:01
*** xingchao has joined #openstack-meeting-404:04
*** coolsvap|away is now known as coolsvap04:13
*** kbyrne has quit IRC04:19
*** kbyrne has joined #openstack-meeting-404:19
*** emagana has joined #openstack-meeting-404:19
*** thorst has joined #openstack-meeting-404:22
*** emagana has quit IRC04:23
*** baoli has quit IRC04:26
*** xingchao has joined #openstack-meeting-404:26
*** dims has joined #openstack-meeting-404:28
*** thorst has quit IRC04:30
*** dims has quit IRC04:30
*** baoli has joined #openstack-meeting-404:34
*** baoli has quit IRC04:38
*** salv-orlando has joined #openstack-meeting-404:44
*** SimonChung1 has joined #openstack-meeting-404:45
*** SimonChung has quit IRC04:46
*** salv-orlando has quit IRC04:49
*** emagana has joined #openstack-meeting-404:50
*** emagana has quit IRC04:55
*** markvoelker has joined #openstack-meeting-404:56
*** sdake has quit IRC04:57
*** neelashah has quit IRC04:59
*** markvoelker has quit IRC05:00
*** daneyon_ has joined #openstack-meeting-405:01
*** daneyon has quit IRC05:02
*** kebray has quit IRC05:07
*** mfedosin has joined #openstack-meeting-405:13
*** xingchao has quit IRC05:18
*** bobh has quit IRC05:18
*** emagana has joined #openstack-meeting-405:20
*** david-lyle has quit IRC05:21
*** mfedosin has quit IRC05:22
*** emagana has quit IRC05:25
*** thorst has joined #openstack-meeting-405:28
*** zhurong has quit IRC05:34
*** thorst has quit IRC05:34
*** bpokorny has joined #openstack-meeting-405:36
*** zhurong has joined #openstack-meeting-405:47
*** bpokorny has quit IRC05:47
*** emagana has joined #openstack-meeting-405:51
*** irenab has quit IRC05:51
*** nkrinner has joined #openstack-meeting-405:51
*** julim has quit IRC05:52
*** emagana has quit IRC05:55
*** bobh has joined #openstack-meeting-406:02
*** paul-carlton1 has joined #openstack-meeting-406:02
*** bpokorny has joined #openstack-meeting-406:07
*** bobh has quit IRC06:08
*** cartik has joined #openstack-meeting-406:09
*** paul-carlton1 has quit IRC06:17
*** emagana has joined #openstack-meeting-406:21
*** amotoki has joined #openstack-meeting-406:22
*** sdake has joined #openstack-meeting-406:25
*** emagana has quit IRC06:26
*** salv-orlando has joined #openstack-meeting-406:30
*** thorst has joined #openstack-meeting-406:31
*** harshs has left #openstack-meeting-406:38
*** thorst has quit IRC06:39
*** sdake has quit IRC06:39
*** irenab has joined #openstack-meeting-406:39
*** emagana has joined #openstack-meeting-406:52
*** emagana has quit IRC06:57
*** markvoelker has joined #openstack-meeting-406:57
*** bpokorny has quit IRC06:58
*** markvoelker has quit IRC07:02
*** markvan has quit IRC07:03
*** mattt has quit IRC07:03
*** sbadia has quit IRC07:03
*** krotscheck has quit IRC07:03
*** nihilifer has quit IRC07:03
*** mentat has quit IRC07:03
*** SergeyLukjanov has quit IRC07:03
*** mancdaz has quit IRC07:03
*** markvan has joined #openstack-meeting-407:03
*** mentat has joined #openstack-meeting-407:04
*** mattt1 has joined #openstack-meeting-407:04
*** nihilifer has joined #openstack-meeting-407:04
*** SergeyLukjanov has joined #openstack-meeting-407:04
*** krotscheck has joined #openstack-meeting-407:04
*** sbadia has joined #openstack-meeting-407:05
*** bobh has joined #openstack-meeting-407:05
*** bobh has quit IRC07:09
*** emagana has joined #openstack-meeting-407:22
*** javeriak has joined #openstack-meeting-407:25
*** javeriak has quit IRC07:26
*** javeriak has joined #openstack-meeting-407:26
*** emagana has quit IRC07:27
*** gampel has joined #openstack-meeting-407:28
*** javeriak has quit IRC07:32
*** javeriak has joined #openstack-meeting-407:33
*** dshakhray has joined #openstack-meeting-407:37
*** thorst has joined #openstack-meeting-407:37
*** thorst has quit IRC07:45
*** salv-orlando has quit IRC07:47
*** cartik has quit IRC07:48
*** May-meimei has quit IRC07:49
*** hdaniel has joined #openstack-meeting-407:49
*** iceyao has quit IRC07:52
*** iceyao has joined #openstack-meeting-407:52
*** emagana has joined #openstack-meeting-407:53
*** emagana has quit IRC07:57
*** May-meimei has joined #openstack-meeting-408:01
*** emagana has joined #openstack-meeting-408:04
*** bobh has joined #openstack-meeting-408:06
*** dtardivel has joined #openstack-meeting-408:10
*** bobh has quit IRC08:10
*** iceyao_ has joined #openstack-meeting-408:11
*** reedip is now known as reedip_away08:13
*** iceyao has quit IRC08:14
*** mbound has joined #openstack-meeting-408:20
*** Jeffrey4l has quit IRC08:30
*** zeih has joined #openstack-meeting-408:31
*** shz has quit IRC08:32
*** shihanzhang has joined #openstack-meeting-408:33
*** saggi has joined #openstack-meeting-408:33
*** numans has joined #openstack-meeting-408:34
*** dshakhray has quit IRC08:35
*** emagana has quit IRC08:38
*** Jeffrey4l has joined #openstack-meeting-408:42
*** thorst has joined #openstack-meeting-408:43
*** cartik has joined #openstack-meeting-408:46
*** thorst has quit IRC08:49
*** Shlomo_N has joined #openstack-meeting-408:54
*** zhurong has quit IRC08:57
*** gsagie has joined #openstack-meeting-408:58
*** markvoelker has joined #openstack-meeting-408:58
*** salv-orlando has joined #openstack-meeting-408:59
*** salv-orlando has quit IRC08:59
*** salv-orlando has joined #openstack-meeting-408:59
gsagie#startmeeting dragonflow09:00
openstackMeeting started Mon Feb 15 09:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is gsagie. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: dragonflow)"09:00
openstackThe meeting name has been set to 'dragonflow'09:00
gsagieHello everyone, who is here for the meeting?09:00
*** oanson has joined #openstack-meeting-409:00
dingboopto/09:00
gampelHi gsagie09:00
*** raofei has joined #openstack-meeting-409:00
Shlomo_Nhi, I am here09:01
oansonHi09:01
gsagie#info gampel, dingboopt, Shlomo_n, raofei, oanson, gsagie in meeting09:01
Shlomo_NYuli will absent 2day09:01
gsagieokie09:02
gsagiegampel: Any chance to remind to DuanKebo? ;)09:02
gampelOK09:02
raofeiDuankebo is offline09:02
gsagie#topic big-tent09:02
*** openstack changes topic to "big-tent (Meeting topic: dragonflow)"09:02
*** markvoelker has quit IRC09:03
*** DuanKebo has joined #openstack-meeting-409:03
gsagieJust to update everyone, we have applied to become a formal project09:03
Shlomo_Ncongrats09:03
gsagieas part of the big-tent and not as part of the Neutron stadium, the patch can be reviewed here: https://review.openstack.org/#/c/277153/09:03
gsagieShlomo_N: its just a request, not an approval yet09:03
raofeigood!09:03
gsagie#topic security groups and port security09:04
*** openstack changes topic to "security groups and port security (Meeting topic: dragonflow)"09:04
DuanKeboCongradulations!09:04
gsagiedingboopt: you have been working on that up until the security groups application, would you mind to update?09:04
dingbooptI have install flow related to sg using ryu lib09:04
dingbooptand everythin is ok09:05
dingbooptutil now09:05
gsagieok good, so we are missing only the application right now, right?09:05
dingbooptand I have already write some code09:05
dingbooptyes09:05
dingbooptI have already write some app code09:05
gsagieok good, when you can please upload it to the repository, its important we do all testing with it09:05
dingbooptand some test09:05
gsagiegood job!09:05
dingbooptthis week09:05
dingbooptI will upload some code09:06
gsagieregarding port security, we need allowed address pairs right?09:06
dingbooptyes09:06
gsagieok, and you also working on that application right?09:06
gsagiewe have anything open there?09:06
*** bobh has joined #openstack-meeting-409:06
dingbooptcurrently I focus on security group09:06
gsagiegampel: we need to merge this spec : https://review.openstack.org/#/c/263019/09:06
dingbooptapp09:06
gsagiefor port security , i think we have an agreement there, but please review09:07
gampelOk i will review it09:07
gsagiedingboopt: ok cool09:07
gsagie#action dingboopt upload security groups patch for review09:07
dingbooptok, I will review this bp09:07
dingbooptok09:07
gsagie#action gampel, dingboopt review port security patch09:07
gsagieanything else on this subject?09:08
dingbooptno09:08
gsagieShlomo_N will need to start adding some specific scenarios to the scale testing09:08
gsagieso we can test security groups performance09:08
gsagietalked with him about some scenarios, we should add them to the specs as well and also add to openstack-performance09:08
gsagie#topic DB consistency09:09
*** openstack changes topic to "DB consistency (Meeting topic: dragonflow)"09:09
gsagienick-ma is not here, he is back tommorow09:09
gampelI suggest we talk about this in our channel with him09:09
gsagiewe have some solution based on nick-ma ideas that we would like to go with09:09
gsagieand we will talk with him after the meeting and update the spec accordingly so everyone can review09:09
gsagieand comment09:09
gsagie#action gampel,gsagie,nick-ma update DB consistency spec09:10
gsagieDuanKebo: we want you to also be part of this conversation obviously09:10
gsagieDuanKebo: tommorow will be ok with you?09:11
DuanKeboOK no09:11
DuanKebono problem09:11
gampelthe idea is to have two phase commit and relay on df db swap and replace atomic operation09:11
*** bobh has quit IRC09:11
gsagieok great, we also need you guys feedback of course as some ideas/comments are also based on hujie spec as well09:11
gsagie#topic publish-subscribe09:12
*** openstack changes topic to "publish-subscribe (Meeting topic: dragonflow)"09:12
dingbooptall key-value db support swap and replace atomic operation?09:12
gsagiedingboopt: we are going to have this as a requierment, but yes09:12
dingbooptgot it09:12
gsagiegampel: would like to update regarding the publish subscribe?09:12
gampelyes the first patch should merge today please review09:13
gampellink: https://review.openstack.org/#/c/263322/09:13
gampelthis will take care the neutron server api publishers09:13
gsagie#link https://review.openstack.org/#/c/263322/  publish subscribe spec09:13
gampelthe chassis's  will be in this phase sent via the same publishers in the flowing patch09:14
gampel#link: https://review.openstack.org/#/c/280079/09:14
gsagieok, thanks for taking care of that long patch gampel, certainly a hard part of our solution09:14
gampelwe will add this week a patch for the publisher discovery09:15
gampelcurrently it is configuration on the DF controller side (list of publishers)09:15
gsagieDuanKebo: important you guys review and understand it, because i think you will need to do something very similar in Redis09:16
gampelreliability will come next , and it will relay on the DB consistency adding version per object09:16
*** markvan has quit IRC09:16
*** markvan has joined #openstack-meeting-409:16
gampelPlease all try to reveiw today so we could move it into control  scale testing09:16
*** hdaniel has quit IRC09:16
*** hdaniel has joined #openstack-meeting-409:16
gsagieokie, anyone has any questions or issues to raise regarding this?09:17
*** dtardivel has quit IRC09:17
*** dtardivel has joined #openstack-meeting-409:17
*** numans has quit IRC09:17
*** numans has joined #openstack-meeting-409:17
*** raofei has quit IRC09:17
*** raofei has joined #openstack-meeting-409:17
gsagie#topic ovsdb monitor09:17
*** openstack changes topic to "ovsdb monitor (Meeting topic: dragonflow)"09:17
gsagie#link https://review.openstack.org/#/c/274332/09:17
*** DuanKebo has quit IRC09:17
raofeiok, we ill review them.09:17
*** DuanKebo_ has joined #openstack-meeting-409:17
gsagiewb DuanKebo09:18
gsagieregarding ovsdb monitor, i reviewed it, https://review.openstack.org/#/c/274332/09:18
DuanKebo_Yes, just offlined.09:18
gsagiehas few comments, but i think after the fix we can merge it09:18
gsagieand start sending code09:18
gsagiehujie here?09:18
gsagie#link ovsdb monitor https://review.openstack.org/#/c/274332/09:18
gsagieDuanKebo: just needs to make sure hujie fix the small comments on the patch and start sending code for this, i think we all agree what needs to be done there09:19
DuanKebo_Yes09:20
DuanKebo_He is coding now09:20
gsagieokie, thanks09:20
DuanKebo_he also will update the spec09:20
gsagie#action hujie fix ovsdb monitor spec and upload code to repository09:20
gsagie#topic controller reliability09:20
*** openstack changes topic to "controller reliability (Meeting topic: dragonflow)"09:20
gsagie#link https://review.openstack.org/#/c/274334/ controller reliability09:21
gsagieheshan : would like to update?09:21
gsagiehshan09:21
DuanKebo_one second09:21
*** hshan has joined #openstack-meeting-409:21
gsagiehi hshan :)09:21
gsagiewe are talking about your controller reliability spec09:22
hshanhi gsagie:)09:22
hshanokay09:22
gsagiei like your idea to change the cookie field and use this, added some comments on the review for you to consider09:22
gsagiebut i think that everything is solved right? as you will have a "sync finish" notification sent09:22
gsagieon all cases09:22
gsagieis there anything open you would like to discuss about?09:23
*** dshakhray has joined #openstack-meeting-409:23
DuanKebo_he is typing09:24
hshansync process should delete flows, so the sync process need to be a dragonflow app09:24
gsagiehshan: okie, so we need to define an "API" for this application that recieve a sync finished call09:25
gsagieand also adds to all applications something that tells them the cookie ide09:25
gsagieright?09:25
hshanyes09:25
*** klamath_ has joined #openstack-meeting-409:26
gsagieokie, you will also need to change some code for existing applications that use the cookie id already09:26
gsagiedo you need any help ?09:26
gampelwe can add it to the DF Ryu base class09:26
hshanagree with you09:26
gsagiegampel: good idea, but he will still need to change some applications that already use the cookie id for something else09:27
hshanI've make some modification locally09:27
gsagie(i think DHCP uses it as well)09:27
gampelno it does not09:27
gsagiegampel: you dont use it for packet ins to controller?09:27
*** crinkle_ has joined #openstack-meeting-409:27
gampelI use the metadata  but i will look into it and and comment in the spec09:28
gsagieokie09:28
gsagiehshan: please let us know if you need any help as your patch might get complicated, maybe not09:28
gsagiebut please update us if you see any problem as we need to fix it fast :)09:28
gsagie#topic selective proactive09:28
*** openstack changes topic to "selective proactive (Meeting topic: dragonflow)"09:28
*** crinkle has quit IRC09:28
*** jwagner has quit IRC09:28
*** bapalm has quit IRC09:28
*** DuanKebo_ has quit IRC09:28
*** klamath has quit IRC09:28
*** elemoine- has quit IRC09:28
*** mattymo has quit IRC09:28
*** DuanKebo has joined #openstack-meeting-409:28
hshanokay09:28
gampel hshan: try to spit it into smaller patches09:29
gsagie#link selective proactive https://review.openstack.org/#/c/275199/09:29
*** mattymo has joined #openstack-meeting-409:29
hshanokay, i will09:29
gsagieDuanKebo: welcome back :) how is selective proactive going on?09:29
*** jwagner has joined #openstack-meeting-409:29
DuanKeboI start writing code now.09:29
*** bapalm has joined #openstack-meeting-409:29
*** elemoine has joined #openstack-meeting-409:30
DuanKeboI need to add a topology module.09:30
gsagieok great, please fix few small comments on spec so we can merge it, but i think its in good shape09:30
gsagieDuanKebo: maybe we should talk about this, why do you need another module?09:30
*** baohua has quit IRC09:30
DuanKeboYes, I have saught your comments09:30
DuanKebofix them today.09:30
gsagieok, thanks09:30
gsagiei think we need to see if we really need another module or we can manage it simpler in the controller (with the ovsdb monitor part)09:31
DuanKeboIf we put this function in controller09:32
DuanKeboI worry about that the controller become too big09:32
DuanKeboand complex.09:32
gsagieDuanKebo: ok agree, when you have just the structure maybe it will be good to upload patch for review09:33
gsagieso we can understand your plans09:33
DuanKeboOK09:33
DuanKeboanother problem09:33
gsagie?09:33
DuanKeboI need to receive sorthbound message09:33
DuanKebosuch as port online event.09:34
DuanKeboCurrently, controller can't receive them.09:34
gsagieyes, we need to add this09:34
DuanKeboOnly app can09:34
gsagieso the controller can recieve port notifications from the ovsdb monitor09:34
gampelthis again can be added to the base df Ryu class09:34
gsagiei can add this connection09:35
gsagiegampel: its not something we want in the application09:35
gsagiei think09:35
DuanKeboYes, another way is we register the module to dispacher09:35
gsagieDuanKebo: i think this should be send to the same queue the controller is listening for DB updates and sent to your module09:35
gsagiesince this is a DB update from the switch..09:36
gsagieDuanKebo: yeah, good idea we can use the dispatcher09:36
gsagiefor this09:36
gampelI am not sure, you do not think the application should be notified ?09:36
DuanKeboYour idea also can achieve the target.09:37
gsagiegampel: we are talking about the part that recognize a port, fetch all tenant information (register notification) and then call the apps09:37
DuanKeboHi gampel, could you give more details?09:37
gsagiein the end, the apps will be notified09:38
gsagieand of course they will still need to get the port up/ down, which we now bring from OpenFlow09:38
gsagiewhat i talked with DuanKebo and the team is that we dont really need the openflow part when we have OVSDB monitor09:38
gampelI see so i agree that the best way will be via the queue and add a action09:38
gsagieits little more efficient09:38
gsagieDuanKebo: once you upload the code and the OVSDB monitor we can see whats the best way to connect them, i will work on this with you09:39
gsagieits a problem i am sure we can solve :)09:39
DuanKeboYes.09:40
gsagie#action DuanKebo,gsagie work on how the ovsdb monitor communicate with topology module and send events09:40
gsagie#topic distributed DNAT09:40
*** openstack changes topic to "distributed DNAT (Meeting topic: dragonflow)"09:40
gsagieraofei: saw your patch good work!09:40
gsagie#link distributed dnat https://review.openstack.org/#/c/279434/09:40
gsagiegampel left some comments, please see if you can address them and we can merge this09:41
gsagieanything open?09:41
gampelraofei: you have to merge your testing with the new destructor patch09:41
raofeidue to the merge conflict, it will be done today09:41
raofeiyes, I have merge the latest code from master09:41
gsagie#action raofei address comments on patch and continue for dnat application09:42
gsagieok thanks raofei, good work09:42
raofeithe changed code will be committed today.09:42
gsagie#topic redis db09:42
*** openstack changes topic to "redis db (Meeting topic: dragonflow)"09:42
gsagieDuanKebo: anything needed on this topic?09:42
DuanKeboIt is ok09:43
DuanKeboor sorry09:43
DuanKeboone second09:43
gampelDuanKebo: are you planning to add a new redis pubsub driver or just use the internal redis DB notification09:43
DuanKeboon open issues to discuss.09:43
DuanKeboWe will use the sub/pub arch09:44
DuanKeboand add a redis sub/pub driver for it09:44
gampel DuanKebo:  let me know if you need my help09:44
gsagieokie great09:44
gsagie#topic testing09:44
*** openstack changes topic to "testing (Meeting topic: dragonflow)"09:44
gsagieShlomo_N is working on scale testing here, we will publish results as soon as we have something for current code, but of course we want all the features in before we do the serious testing09:45
gsagieYuli is working on the API/DB control plane performance part09:45
gsagieShlomo_N: anything to add?09:45
Shlomo_NI have done the performance testing for L3-centralized agent.09:46
Shlomo_NNow I am working on data plane performance testing of DVR.09:46
Shlomo_NI am doing these tests for reference to DragonFlow performance09:46
gsagieoanson has added an infrastructure so we can simulate and perform pipeline testing using tap devices that simulate neutron ports and define policies on the expected behaivour09:46
gsagie#link https://review.openstack.org/#/c/275714/ testing infrastructure09:47
gsagieoanson is here if you have any question how to use it, he is adding documentation09:47
gsagieoanson: right?09:47
oansonDocumentation has already been added09:47
oansonNow waiting for additional comments and review09:47
*** thorst has joined #openstack-meeting-409:47
gampelis there any one else working on scale testing control/data ?09:47
gsagieok cool, so please everyone working on new patches/features, see how you can build tests with this09:47
gsagieDuanKebo: also wanted to mention thank you for the good work you guys are doing, i think we have agreement on most specs and we can continue with uploading code to all the features09:48
gsagieso thanks!09:48
gsagieDuanKebo, dingboopt, raofei: anyone doing scale testing?09:49
*** hshan has quit IRC09:49
DuanKeboThank you for your help!09:49
gsagieI think Kun mentioned we suppose to get the hardware in hangzhou after the holiday09:49
gsagie#topic open discussion09:50
*** openstack changes topic to "open discussion (Meeting topic: dragonflow)"09:50
gsagieAnything else by anyone?09:50
*** DuanKebo has quit IRC09:50
gsagie:(09:50
gampelomer: do you want to present your mcast spec09:51
gsagiedingboopt, raofei: good work you two :) i think we have good progress on your work09:51
oansonok09:51
oansonI have uploaded a spec to add and IGMP and multicast application.09:51
oansonThe spec is available for review here: https://review.openstack.org/#/c/278400/09:52
gsagie#link IGMP support in Dragonflow spec https://review.openstack.org/#/c/278400/09:52
oansonIt is planned to make the virtual routers multicast-enabled routers, and support *smart* multicast routing09:52
dingbooptthe servers have not arrived09:52
oansonThis means that multicast packets will be sent only to group members, and only to compute nodes containing group members.09:52
oansonI am adding now a few finishing touches gsagie asked, hopefully to be finished today.09:53
gsagieok, good work oanson09:53
gsagiecertainly an interesting feature for Dragonflow09:53
gsagiemore interesting if we can combine it with the physical infrastructure09:53
gampeldingboopt: :'( we relay  need to start scale testing on large infrastructure as soon as possible09:54
gsagieokie thanks everyone09:54
*** mattt1 has left #openstack-meeting-409:54
gsagieand please stop by in #openstack-dragonflow if anything is needed09:54
gsagieanything else gampel?09:54
*** thorst has quit IRC09:55
gampelnop thank you every one09:55
gsagiethanks and see you all next week!09:55
gsagie#endmeeting09:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:55
openstackMeeting ended Mon Feb 15 09:55:58 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-02-15-09.00.html09:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-02-15-09.00.txt09:56
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-02-15-09.00.log.html09:56
*** Shlomo_N has left #openstack-meeting-409:56
*** gsagie has left #openstack-meeting-409:58
*** oanson has left #openstack-meeting-409:59
*** prithiv has joined #openstack-meeting-409:59
*** prithiv has quit IRC09:59
*** prithiv has joined #openstack-meeting-410:00
*** MarkAtwood has quit IRC10:02
*** MarkAtwood has joined #openstack-meeting-410:03
*** salv-orl_ has joined #openstack-meeting-410:03
*** yamamoto_ has quit IRC10:03
*** MarkAtwo_ has joined #openstack-meeting-410:04
*** salv-orlando has quit IRC10:06
*** emagana has joined #openstack-meeting-410:06
*** MarkAtwood has quit IRC10:08
*** GB21 has joined #openstack-meeting-410:10
*** javeriak_ has joined #openstack-meeting-410:17
*** DuanKebo has joined #openstack-meeting-410:20
*** javeriak has quit IRC10:21
*** tkaczynski has joined #openstack-meeting-410:23
*** javeriak_ has quit IRC10:28
*** marcusvrn_ has joined #openstack-meeting-410:32
*** cartik has quit IRC10:33
*** prithiv has quit IRC10:34
*** Jeffrey4l has quit IRC10:45
*** paul-carlton1 has joined #openstack-meeting-410:45
*** dshakhray has quit IRC10:49
*** DuanKebo has quit IRC10:50
*** piet has joined #openstack-meeting-410:51
*** thorst has joined #openstack-meeting-410:52
*** javeriak has joined #openstack-meeting-410:54
*** DuanKebo has joined #openstack-meeting-410:57
*** piet has quit IRC10:58
*** piet has joined #openstack-meeting-410:58
*** markvoelker has joined #openstack-meeting-410:59
*** thorst has quit IRC11:00
*** markvoelker has quit IRC11:04
*** javeriak has quit IRC11:06
*** Jeffrey4l has joined #openstack-meeting-411:08
*** bobh has joined #openstack-meeting-411:08
*** ihrachys has joined #openstack-meeting-411:09
*** yamamoto_ has joined #openstack-meeting-411:10
*** bobh has quit IRC11:13
*** piet has quit IRC11:17
*** cartik has joined #openstack-meeting-411:17
*** emagana has quit IRC11:27
*** chem has joined #openstack-meeting-411:29
*** emagana has joined #openstack-meeting-411:29
*** yamamoto_ has quit IRC11:29
*** yamamoto_ has joined #openstack-meeting-411:30
*** prithiv has joined #openstack-meeting-411:30
*** emagana has quit IRC11:33
*** yamamoto_ has quit IRC11:34
*** emagana has joined #openstack-meeting-411:35
*** _degorenko|afk is now known as degorenko11:38
*** emagana has quit IRC11:39
*** nkrinner has quit IRC11:39
*** emagana has joined #openstack-meeting-411:40
*** piet has joined #openstack-meeting-411:44
*** GB21 has quit IRC11:47
*** piet has quit IRC11:51
*** piet has joined #openstack-meeting-411:52
*** piet has quit IRC11:58
*** thorst has joined #openstack-meeting-411:58
*** yamamoto has joined #openstack-meeting-411:58
*** yamamoto has quit IRC11:59
*** yamamoto has joined #openstack-meeting-411:59
*** piet has joined #openstack-meeting-411:59
*** paul-carlton1 has quit IRC11:59
*** prithiv has quit IRC12:02
*** thorst has quit IRC12:05
*** iceyao_ has quit IRC12:08
*** piet has quit IRC12:08
*** iceyao has joined #openstack-meeting-412:08
*** emagana has quit IRC12:09
*** bobh has joined #openstack-meeting-412:09
*** piet has joined #openstack-meeting-412:10
*** piet has quit IRC12:10
*** piet has joined #openstack-meeting-412:11
*** GB21 has joined #openstack-meeting-412:13
*** bobh has quit IRC12:14
*** dshakhray has joined #openstack-meeting-412:14
*** cartik has quit IRC12:15
*** piet has quit IRC12:20
*** emagana has joined #openstack-meeting-412:20
*** sdake has joined #openstack-meeting-412:21
*** emagana has quit IRC12:25
*** markvoelker has joined #openstack-meeting-412:29
*** thorst has joined #openstack-meeting-412:30
*** markvoelker has quit IRC12:34
*** chhavi has joined #openstack-meeting-412:34
*** coolsvap is now known as coolsvap|away12:36
*** GB21 has quit IRC12:36
*** thorst has quit IRC12:36
*** marcusvrn_ has quit IRC12:37
*** DuanKebo has quit IRC12:38
*** javeriak has joined #openstack-meeting-412:41
*** dims_ has joined #openstack-meeting-412:42
*** baoli has joined #openstack-meeting-412:43
*** xingchao has joined #openstack-meeting-412:44
*** baoli has quit IRC12:47
*** baoli has joined #openstack-meeting-412:48
*** baoli has quit IRC12:48
*** MarkAtwo_ has quit IRC12:49
*** xingchao has quit IRC12:49
*** javeriak_ has joined #openstack-meeting-412:50
*** emagana has joined #openstack-meeting-412:51
*** javeriak has quit IRC12:52
*** baoli has joined #openstack-meeting-412:52
*** cdelatte has quit IRC12:53
*** baoli has quit IRC12:54
*** emagana has quit IRC12:56
*** thorst has joined #openstack-meeting-412:57
*** baoli has joined #openstack-meeting-413:00
*** baoli_ has joined #openstack-meeting-413:02
*** jmckind has joined #openstack-meeting-413:02
*** salv-orl_ has quit IRC13:04
*** zhurong has joined #openstack-meeting-413:04
*** baoli has quit IRC13:05
*** piet has joined #openstack-meeting-413:06
*** bobh has joined #openstack-meeting-413:10
*** cdelatte has joined #openstack-meeting-413:11
*** baoli_ has quit IRC13:14
*** baoli has joined #openstack-meeting-413:14
*** bobh has quit IRC13:15
*** xingchao has joined #openstack-meeting-413:15
*** prithiv has joined #openstack-meeting-413:16
*** baoli_ has joined #openstack-meeting-413:17
*** vhoward has joined #openstack-meeting-413:18
*** emagana has joined #openstack-meeting-413:18
*** baoli has quit IRC13:20
*** emagana has quit IRC13:20
*** shakamunyi has quit IRC13:20
*** emagana has joined #openstack-meeting-413:20
*** xingchao has quit IRC13:21
*** woodard has joined #openstack-meeting-413:24
*** woodard has quit IRC13:24
*** piet has quit IRC13:24
*** woodard has joined #openstack-meeting-413:24
*** jmckind has quit IRC13:25
*** paul-carlton1 has joined #openstack-meeting-413:27
*** piet has joined #openstack-meeting-413:27
*** markvoelker has joined #openstack-meeting-413:30
*** dims_ has quit IRC13:33
*** dims has joined #openstack-meeting-413:33
*** markvoelker has quit IRC13:35
*** yamamoto has quit IRC13:35
*** yamamoto has joined #openstack-meeting-413:36
*** paul-carlton1 has quit IRC13:37
*** zhurong has quit IRC13:39
*** salv-orlando has joined #openstack-meeting-413:40
*** bobh has joined #openstack-meeting-413:40
*** alexchadin has joined #openstack-meeting-413:41
*** bobh has quit IRC13:43
*** bobh has joined #openstack-meeting-413:43
*** yamamoto has quit IRC13:46
*** yamamoto has joined #openstack-meeting-413:46
*** prithiv has quit IRC13:47
*** piet has quit IRC13:48
*** alexchadin has quit IRC13:48
*** javeriak_ has quit IRC13:48
*** prithiv has joined #openstack-meeting-413:50
*** yamamoto has quit IRC13:51
*** yamamoto has joined #openstack-meeting-413:51
*** klamath_ is now known as klamath13:52
*** yamamoto has quit IRC13:52
*** piet has joined #openstack-meeting-413:52
*** dims has quit IRC13:53
*** yamamoto has joined #openstack-meeting-413:53
*** marcusvrn_ has joined #openstack-meeting-413:54
*** yamamoto has quit IRC13:55
*** yamamoto has joined #openstack-meeting-413:56
*** dims has joined #openstack-meeting-413:57
*** delattec has joined #openstack-meeting-413:58
*** yamamoto has quit IRC14:00
*** dims has quit IRC14:00
*** cdelatte has quit IRC14:01
*** dims has joined #openstack-meeting-414:02
*** neelashah has joined #openstack-meeting-414:05
*** paul-carlton1 has joined #openstack-meeting-414:07
*** GB21 has joined #openstack-meeting-414:08
*** bobh has quit IRC14:09
*** iceyao has quit IRC14:09
*** fawadkhaliq has joined #openstack-meeting-414:10
*** piet has quit IRC14:11
*** piet has joined #openstack-meeting-414:19
*** mbound_ has joined #openstack-meeting-414:20
*** fawadk has joined #openstack-meeting-414:21
*** marcusvrn__ has joined #openstack-meeting-414:21
*** piet has quit IRC14:21
*** woodard has quit IRC14:21
*** woodard has joined #openstack-meeting-414:22
*** piet has joined #openstack-meeting-414:22
*** piet has quit IRC14:24
*** fawadk has quit IRC14:24
*** fawadkhaliq has quit IRC14:24
*** marcusvrn_ has quit IRC14:24
*** saggi has quit IRC14:24
*** mbound has quit IRC14:24
*** sbadia has quit IRC14:24
*** marcusvrn__ is now known as marcusvrn_14:24
*** fawadkhaliq has joined #openstack-meeting-414:24
*** piet has joined #openstack-meeting-414:25
*** sbadia has joined #openstack-meeting-414:25
*** saggi has joined #openstack-meeting-414:25
*** banix has joined #openstack-meeting-414:25
*** fawadkhaliq has quit IRC14:26
*** piet has quit IRC14:26
*** fawadkhaliq has joined #openstack-meeting-414:26
*** piet has joined #openstack-meeting-414:27
*** salv-orlando has quit IRC14:27
*** dims has quit IRC14:28
*** piet has quit IRC14:30
*** yamamoto has joined #openstack-meeting-414:31
*** zeih has quit IRC14:32
*** zeih_ has joined #openstack-meeting-414:32
*** piet has joined #openstack-meeting-414:32
*** dims has joined #openstack-meeting-414:36
*** piet has quit IRC14:39
*** piet has joined #openstack-meeting-414:40
*** ninag has joined #openstack-meeting-414:44
*** irenab has quit IRC14:46
*** paul-carlton1 has quit IRC14:46
*** piet has quit IRC14:47
*** emagana has quit IRC14:48
*** gsagie_ has joined #openstack-meeting-414:50
*** sigmavirus24_awa is now known as sigmavirus2414:52
*** delattec has quit IRC14:52
*** Jeffrey4l has quit IRC14:53
*** piet has joined #openstack-meeting-414:53
*** javeriak has joined #openstack-meeting-414:55
*** javeriak has joined #openstack-meeting-414:56
*** salvorlando has joined #openstack-meeting-414:57
*** piet has quit IRC14:57
*** piet has joined #openstack-meeting-414:57
*** avarner_ has joined #openstack-meeting-414:58
*** dims has quit IRC14:59
salvorlandoAloha?15:00
*** rbak has joined #openstack-meeting-415:00
*** apuimedo has joined #openstack-meeting-415:00
apuimedo#startmeeting kuryr15:00
openstackMeeting started Mon Feb 15 15:00:53 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: kuryr)"15:00
openstackThe meeting name has been set to 'kuryr'15:00
gsagie_Hello all15:01
apuimedoHello and welcome to yet another kuryr weekly meeting15:01
apuimedowho's here for the show?15:01
salvorlandoMe15:01
fawadkhaliqo/15:02
salvorlandoBut I am here to watch the show!15:02
apuimedosalvorlando: I have a couple of questions to ask you :P15:02
apuimedoso don't sit too far back15:02
*** sdake has quit IRC15:02
*** prithiv has quit IRC15:02
apuimedo#info gsagie_ salvorlando fawadkhaliq and apuimedo are here for the meeting15:03
*** piet has quit IRC15:03
apuimedothanks for joining15:03
apuimedo#topic announcements15:03
*** openstack changes topic to "announcements (Meeting topic: kuryr)"15:03
apuimedoAfter the recent discussion in the neutron community about what should and should not be in the Neutron big stadium, we will be submitting the request for Kuryr to be a project on the big tent15:04
apuimedoproposing Gal Sagie as PTL15:04
fawadkhaliqexcellent!15:05
apuimedoand we'll request a design room for the Austin summit15:05
apuimedo:-)15:05
*** prithiv has joined #openstack-meeting-415:05
*** mspreitz has joined #openstack-meeting-415:05
gsagie_yeah, i think that the last day of the last summit was probably the most effective one when we managed to all sit together15:05
salvorlandoYou will probably have more luck winning the euromillioms15:05
gsagie_so hopefully we will have more time this summit15:05
gsagie_salvorlando: why? what is the criteria to have a room?15:06
fawadkhaliqsalvorlando: rofl15:06
apuimedosalvorlando: we have a a failsafe plan!15:06
apuimedoKFC design room15:06
apuimedo:D15:06
fawadkhaliqapuimedo: KFC design room ftw!15:06
apuimedo#link: https://vimeopro.com/midokura/73491533115:06
*** piet has joined #openstack-meeting-415:06
apuimedoI made a webinar last week15:06
apuimedoit shows the communication with lbaas and container <-> VMs15:07
gsagie_cool15:07
apuimedosalvorlando: I need more information on surrendering the email domain to the foundation, do you have some contact I could use for that?15:08
fawadkhaliqapuimedo: very cool, thanks for sharing15:08
gsagie_apuimedo: which domain? kuryr.org?15:08
gsagie_:(15:08
apuimedoyes, salvorlando suggested that I should give control of it to the foundation15:09
apuimedoI created it to have cool links for the demos15:09
apuimedolike http://webinar.kuryr.org:8000/15:09
apuimedo:-)15:09
*** GB21 has quit IRC15:10
apuimedowhich has two containers running behind a load balancer15:10
salvorlandoI was joking btw15:10
*** fawadkhaliq has quit IRC15:10
apuimedooh, I thought it was a requirement salvorlando15:10
apuimedoyou totally got me!15:10
*** dims has joined #openstack-meeting-415:10
apuimedook, just so you all know, if any of you want to use the domain for demos, just shoot me an email15:11
apuimedoand I'll add the necessary dns entries15:11
*** fawadkhaliq has joined #openstack-meeting-415:11
apuimedo#topic deployment15:11
*** openstack changes topic to "deployment (Meeting topic: kuryr)"15:11
apuimedo#info apuimedo setn https://review.openstack.org/#/c/279320/15:12
apuimedodarned typo...15:12
*** avarner_ has quit IRC15:12
*** avarner has joined #openstack-meeting-415:12
apuimedoanyway15:12
*** yamamoto has quit IRC15:12
apuimedosalvorlando: fawadkhaliq: gsagie_: I'd like to hear more about how you bind15:13
*** avarner has quit IRC15:13
apuimedoto make sure that I'm not overlooking anything for the container15:13
*** avarner_ has joined #openstack-meeting-415:13
apuimedoto make the common base container as complete as possible15:13
*** javeriak_ has joined #openstack-meeting-415:14
apuimedoI'll probably be submitting an ovs one soon15:14
*** javeriak has quit IRC15:14
gsagie_apuimedo: what do you mean an ovs one? you have one container per backend?15:14
*** GB21 has joined #openstack-meeting-415:15
gsagie_or better one Dockerfile15:15
*** javeriak has joined #openstack-meeting-415:15
apuimedothere should be kuryr/libnetwork:midonet kuryr/libnetwork:ovs kuryr/libnetwork:ovn15:15
apuimedoor dragonflow/kuryr:1.0.015:16
apuimedobut what I meant is that yes, vendors should have their own dockerfile15:16
*** emagana has joined #openstack-meeting-415:16
apuimedothat does a "from kuryr/libnetwork:1.0.0"15:16
apuimedoand adds a layer with their binding dependencies15:16
*** galstrom_zzz is now known as galstrom15:16
fawadkhaliqapuimedo: for PLUMgrid/iovisor, it will follow similar mechanism as you have in there. I will review and comment.15:16
*** spotz_zzz is now known as spotz15:16
apuimedogsagie_: in your case, df-db would be added15:17
apuimedofawadkhaliq: very well15:17
*** galstrom is now known as galstrom_zzz15:17
*** galstrom_zzz is now known as galstrom15:17
apuimedothe design suggestion, of course, is that the neutron agent is on a separate container15:17
apuimedowhere possible15:17
gsagie_apuimedo: sounds good, the only thing i am wondering is how for example if we take ovn/dragonflow the code inside the container will perform the binding to OVS15:17
gsagie_in the compute node15:17
*** paul-carlton1 has joined #openstack-meeting-415:17
apuimedogsagie_: we run the kuryr container on the host networking namespace15:18
apuimedoso ovs-vsctl works fine15:18
apuimedo;-)15:18
apuimedothis I already tested15:18
gsagie_okie cool15:18
apuimedofawadkhaliq: will that split containerization work for you guys?15:18
*** javeriak_ has quit IRC15:19
apuimedosalvorlando: I'll be checking kolla this coming weekend15:19
fawadkhaliqapuimedo: I will have to check that. Let me report back.15:19
salvorlandoApuimedo your approach to containers make sebse15:19
apuimedogotta talk with SamYaple15:19
*** avarner has joined #openstack-meeting-415:19
apuimedofawadkhaliq: very well15:20
salvorlandoLet me know if I can help with kolla15:20
*** avarner_ has quit IRC15:20
apuimedosalvorlando: alright, so for that, since kolla only has ovs, I'll get ready the ovs version of the container15:20
apuimedosalvorlando: or do you have ovn kolla support?15:20
gsagie_i think that reaching ovn support from ova should be fairly easy15:21
gsagie_ovs15:21
apuimedogsagie_: well, not so much, you'd need kolla to deploy all the components that ovn uses15:22
apuimedoprobably15:22
apuimedothe extra agents and stuff15:22
*** javeriak has quit IRC15:22
apuimedoanyway, let's try to get ovs+kolla in the coming two weeks15:22
apuimedo:-)15:22
gsagie_okie15:22
apuimedo#action salvorlando apuimedo to try ovs + kolla15:23
salvorlandoThanks apuimedo :-)15:23
apuimedo(+kuryr, ofc)15:23
apuimedo#topic nested15:24
*** openstack changes topic to "nested (Meeting topic: kuryr)"15:24
apuimedofawadkhaliq: the floor is yours15:24
fawadkhaliqapuimedo: thanks15:24
fawadkhaliqI addressed most of the early comments.15:24
fawadkhaliqmagnum folks have provided some feedback15:24
*** julim has joined #openstack-meeting-415:25
apuimedofawadkhaliq: in the review?15:25
*** andymccr has quit IRC15:25
fawadkhaliqI would like to discuss one point here that taku and I discussed last week as well, needed broader audience15:25
fawadkhaliqapuimedo: correct.15:25
apuimedofawadkhaliq: raise it, raise it ;-)15:25
fawadkhaliqthe ask is to support networking via Kuryr when native container tools are used instead of magnum API. For example Docker, Kub CLI etc.15:26
*** piet has quit IRC15:26
apuimedofawadkhaliq: oh, you mean that you deploy a bay15:26
fawadkhaliqWhile is possible and I have a way to make it work, it would take us back to the path of making Kuryr agent communicate via management plane to other endpoints :(15:26
*** andymccr has joined #openstack-meeting-415:26
fawadkhaliqso heres what I am thinking..15:26
apuimedoand you want to get the containers networked whether the user goes through magnum api or swarm/k8s, right?15:27
mspreitzsome of us plan to use Neutron and Docker without Magnum15:27
fawadkhaliqapuimedo: correct15:27
*** avarner_ has joined #openstack-meeting-415:27
apuimedomspreitz: welcome ;-)15:27
gsagie_fawad: but i thought the plan was to integrate with the COE's themselves and not with Magnum15:27
fawadkhaliqmspreitz: https://review.openstack.org/#/c/269039/ please review :-)15:27
*** avarner has quit IRC15:28
gsagie_What information do you need from Magnum?15:28
fawadkhaliqgsagie_: COE via magnum currently :)15:28
apuimedogsagie_: well, my idea was, and fawadkhaliq I'll appreciate that you tel lme if I'm talking nonsense, that we have:15:28
fawadkhaliqgsagie_: two paths. 1. if we bypass Magnum, then Kuryr agent communicates with other OpenStack endpoints. 2. If we go via Magnum API, we may be able to avoid it.15:29
apuimedo1. Magnum deploy the bay controller nodes with information as to where to reach Neutron and that such communication is allowed15:29
fawadkhaliqso if we are okay with this communication, then we can update and make it happen.15:30
*** ajmiller has joined #openstack-meeting-415:30
apuimedo2. We have an integration with bay types that speaks with neutron and does the ipam and port management15:30
apuimedo3. the worker nodes just get minimal information like what is the vlan to connect to15:30
mspreitzI am trying to connect containers to Neutron networks without any VMs in sight.  Is anybody else here interested in that?15:31
*** ajmiller_ has joined #openstack-meeting-415:31
fawadkhaliqapuimedo: the idea is similar, except that more information is passed via Magnum15:31
gsagie_mspreitz: this is not the use case we talking now15:31
fawadkhaliqhowever..15:31
fawadkhaliqapuimedo: I see your point and I see this communication seems reasonable to us..15:31
gsagie_fawadkhaliq, apuimedo: ok that make sense, but now why would anyone want to run this without Magnum? and if they do why is this different then a regular "bare metal" integration with Docker/Kubernetes?15:31
fawadkhaliqgiven that, let's update15:32
apuimedomspreitz: yes, that comes just after this topic ;-)15:32
apuimedowe went with nested first today15:32
apuimedogsagie_: it's not to run it without magnum15:32
*** GB21 has quit IRC15:32
apuimedoit's to let the magnum user consume the k8s/swarm api instead of the magnum one for service creation15:32
fawadkhaliqapuimedo: +1, Magnum does one step and then rest can be done via native tools.15:33
apuimedodid I get it right fawadkhaliq ?15:33
gsagie_okie got it now15:33
fawadkhaliqapuimedo: correct. essentially a hybrid workflow still gets consumer the network.15:33
apuimedo:-)15:33
fawadkhaliqso I wanted to make sure you guys are onboard, before I propose the change.15:34
fawadkhaliqLooks we are all on the same page with this15:34
*** blahRus has joined #openstack-meeting-415:34
fawadkhaliqso I will go ahead15:34
apuimedofawadkhaliq: can you summarize the change in one sentence?15:34
apuimedo(I'll put it in info comment)15:34
*** ajmiller has quit IRC15:34
fawadkhaliqapuimedo: goal is to facilitate networking even when native tools are used.15:35
fawadkhaliqapuimedo: that would require Kuryr agent to have communication with other OpenStack endpoints.15:35
apuimedo#info nested goal: to provide networking whether magnum users consume magnum or bay specific apis15:35
gsagie_fawadkhaliq: i personally think, without giving it enough thought that this is the correct path either way15:35
fawadkhaliqapuimedo: +115:35
apuimedofawadkhaliq: I think the communication can be very minimal and we should keep it like that15:36
apuimedofor swarm it may be more complicated, but for k8s probably only the controller nodes will need it15:36
fawadkhaliqapuimedo: gsagie_, I am concerned about the security aspects on this communication. But thats something we can improve and can evolve.15:36
gsagie_yep, the end points should only do the binding similar to our Kubernetes integration plan15:37
apuimedofawadkhaliq: exactly15:37
fawadkhaliqthats all on nested.15:37
fawadkhaliqvery useful discussion :-)15:37
apuimedo#info: agreement to limit access to the management as much as possible15:37
apuimedo#topic k8s integration15:38
*** openstack changes topic to "k8s integration (Meeting topic: kuryr)"15:38
apuimedomspreitz: here we go ;-)15:38
apuimedothanks fawadkhaliq15:38
fawadkhaliqapuimedo: welcome15:38
*** itisha has joined #openstack-meeting-415:38
apuimedoalright then15:39
apuimedoWe do not have Irena here15:39
gsagie_or banix ?15:39
apuimedomspreitz: did you move forward with the plan to make cni call libnetwork?15:39
banixgsagie_: hi15:39
mspreitzI have a draft on which I am working15:40
gsagie_ohh hi :)15:40
*** piet has joined #openstack-meeting-415:40
mspreitzHope to get it running today15:40
apuimedomspreitz: :O15:40
banixhave been sick all week. getting back to things....15:40
fawadkhaliqbanix: sorry to hear. hope you feel well.15:40
apuimedoare you having a network configured in CNI vendor on each worker machine15:40
gsagie_banix: happy to hear you recovering15:41
apuimedoand then having the cni driver call docker libnetwork attaching?15:41
apuimedobanix: take care ;-)15:41
mspreitzIt will be more interesting to me once Kuryr can connect to existing networks instead of make new ones.15:41
*** yamamoto has joined #openstack-meeting-415:41
mspreitzMy CNI plugin calls `docker network`15:42
gsagie_mspreitz: yes thats deafeningly something we had in mind to do15:42
mspreitzThe `docker network create` needs to be done just once, thanks to Kuryr.15:42
apuimedomspreitz: good point15:42
banixapuimedo: gsagie_ fawadkhaliq thansk (and sorry for the interruption)15:43
apuimedomspreitz: couldn't you create the networks as part of the deployment?15:43
apuimedoyou add a worker node, you do a docker network create15:43
mspreitzapuimedo: I am not sure I understand the question.15:43
mspreitzwhich networks, which deployment?15:43
mspreitzNetworks are not per worker node15:44
apuimedomspreitz: which network topology are you using15:44
apuimedo?15:44
apuimedonetwork per service?15:44
mspreitzI am taking baby steps15:44
apuimedoand what are the reasons you need to connect to pre-existing networks15:44
apuimedo?15:44
mspreitzthe one I want to take first is to connect containers to a provider network15:45
mspreitzBut I can't yet, Kuryr won't connect to that.15:45
apuimedoaha15:45
apuimedo:-)15:45
apuimedothanks mspreitz15:45
*** piet has quit IRC15:45
mspreitzMy next step would be to have a tenant network per K8s namespace, probably15:45
mspreitzThat is not the way k8s wants to go15:45
mspreitzit's just a possible next baby step.15:46
apuimedomspreitz: is it okay for your draft to hack it?15:46
apuimedothe first step15:46
apuimedowhat I mean is15:46
apuimedodo `docker network create myprovidernet`15:46
apuimedoyou'll get a uuid15:46
apuimedoyou delete the network that is created in neutron with that uuid15:47
apuimedoand update the provider network name to have that uuid15:47
apuimedoIt would be very useful to know if that would work15:47
mspreitzOh, rename the pre-existing provider nework.  Hadn't thought of that15:47
mspreitzI can give it a try.15:47
apuimedomspreitz: I have a hunch that it should work15:47
apuimedoif it does15:47
apuimedoprobably connecting to existing networks will be a bit easier in "hacky mode"15:48
mspreitzI suppose you folks can tell me: will future libnetwork calls to Kuryr, to attach containers, find the Neutron network by nUetron network name or by UUID?15:48
gsagie_apuimedo: maybe you can add an action for me to add this support15:48
apuimedomspreitz: yes, you'll pass --neutron-net a450ae64-6464-44ee-ab20-a5e710026c4715:49
gsagie_i don't think it should be too hard to add, i will write a spec15:49
apuimedowell, more as a tag15:49
mspreitzdoes `--neutron-net` take a name or a UUID?15:49
gsagie_mspreitz: we can support both15:49
apuimedogsagie_: it can be a workaround while we can't put darned tags on resources15:49
apuimedomspreitz: uuid15:50
gsagie_mspreitz: we meant to use the tags in Neutron once this feature is completed15:50
banixgsagie_: i have the code that does that15:50
banixthere is one issue that we need to deal with15:50
apuimedobanix: you mean the name change?15:50
gsagie_apuimedo: we can just do according to the name right now15:50
gsagie_i think thats what banix has15:50
banixi meant using existing networks15:50
gsagie_use existing network by Neutron name15:50
apuimedogsagie_: you should not do it by name if you are then changing the current name :P15:51
banixthe issue is right now we rely on neutron network name15:51
mspreitzIf work has to be done, I'd rather see banix  go for the jugular15:51
apuimedoexactly15:51
banixand for an existing neutron network for the rest of our code to work, we have to set its name to what we want; not desrirable but it works15:51
apuimedobanix: yes, that's what I proposed mspreitz15:51
gsagie_banix: or keep the mapping internally15:51
gsagie_or in a DB15:52
*** gampel has quit IRC15:52
banixi think once we have the tagging, things will look much cleaner15:52
apuimedogsagie_: I'd rather knock my teeth out than adding a DB to Kuryr :P15:52
gsagie_heh ok15:52
apuimedoKuryr is parasitic by nature15:52
banixgsagie_: yesh, have been trying to see how use the docker kv but doesnt look promising15:52
apuimedoit should use the DBs of what it connects to15:52
apuimedobanix: the inflight restriction is a bit damning there15:53
banixdo you guys agree neutron tagging will solve this problem?15:53
apuimedobanix: wholeheartedly15:53
mspreitzWhat is "the inflight restriction" ?15:53
banixthe blueprint there seems almost approved; has one +2 last i checked15:53
apuimedomspreitz: in docker libnetwork you can't access a kv resource in the same operation that is creating it15:54
gsagie_yes15:54
apuimedoso, for example, let's say that we are creating a network to connect to a Neutron net15:54
mspreitzI understand15:54
apuimedokuryr receives the call to the network creation15:54
mspreitzyes, that's a pain15:54
apuimedobut it can't go to the kv to modify it to add data15:54
apuimedomspreitz: indeed15:54
apuimedowhen I feel hacky, I'd add deferred actions xD15:55
apuimedothat are executed just after we return15:55
*** irenab has joined #openstack-meeting-415:55
mspreitzthat's a real pain for any higher level automation15:55
apuimedobut then I think, well, tags should be coming soon to neutron15:55
apuimedomspreitz: and raceful15:55
apuimedoand you'd lose it if the kuryr daemon restarts15:55
mspreitzlike you said, "hacky"15:56
apuimedoanyway, mspreitz let us know if the hacky way works15:56
apuimedothe one of renaming15:56
apuimedo#topic general15:56
*** openstack changes topic to "general (Meeting topic: kuryr)"15:56
mspreitzhmm, I thought I was just told it will not15:56
*** daneyon_ has quit IRC15:56
apuimedomspreitz: banix said that changing the name in neutron will work15:56
*** daneyon has joined #openstack-meeting-415:56
mspreitz`docker network attach` will cause Kuryr to find a Neutron network by its Neutron UUID, right?15:56
apuimedomspreitz: by docker network id15:57
apuimedo(which maps to the neutron name)15:57
mspreitzSo it will look up the network in Neutron by Neutron network name?15:57
apuimedo(while we don't have neutron resource tags)15:57
banixmspreitz: what apuimedo said15:58
apuimedomspreitz: docker network attach dockernetname15:58
mspreitzThen I'll give it a try15:58
apuimedodockernetname -> dockernetid -> (to be found on neutron net name)15:58
apuimedoanybody has anything more for the alst two minutes?15:58
*** apuimedo has quit IRC15:58
banixlooking at the log of this meeting i see Kola being mentioned; hui kang has worked on this15:58
banixunfortunately he had to leave for a family emergency last week; i will check with him and see where he is15:59
*** daneyon has quit IRC15:59
banixSee what you did. Toni got upset!15:59
*** daneyon has joined #openstack-meeting-416:00
*** lazy_prince has joined #openstack-meeting-416:01
*** krtaylor has quit IRC16:01
banixany co chairs to close the call?16:01
fawadkhaliqanyone else going to end the meeting :-)16:01
fawadkhaliq#endmeeting16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
openstackMeeting ended Mon Feb 15 16:02:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-02-15-15.00.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-02-15-15.00.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-02-15-15.00.log.html16:02
salvorlandoAdieuuu16:02
fawadkhaliqDone16:02
*** mrhillsman has quit IRC16:02
*** mspreitz has quit IRC16:03
*** paul-carlton1 has quit IRC16:04
*** daneyon_ has joined #openstack-meeting-416:04
*** apuimedo has joined #openstack-meeting-416:04
apuimedogsagie_: did somebody end the kurr meeting? My computer lost power16:05
apuimedo*kuryr16:05
fawadkhaliqapuimedo: i did ;-)16:05
apuimedothanks fawadkhaliq !16:05
fawadkhaliqapuimedo: npp16:05
*** numans has quit IRC16:06
*** kebray has joined #openstack-meeting-416:07
*** daneyon has quit IRC16:07
*** mbound_ has quit IRC16:08
*** avarner_ has quit IRC16:09
*** gsagie_ has quit IRC16:09
*** avarner_ has joined #openstack-meeting-416:09
*** prithiv has quit IRC16:11
*** sdake has joined #openstack-meeting-416:12
*** zeih_ has quit IRC16:13
*** krtaylor has joined #openstack-meeting-416:15
*** yhvh has joined #openstack-meeting-416:15
*** chhavi has quit IRC16:15
*** prithiv has joined #openstack-meeting-416:17
*** devananda has joined #openstack-meeting-416:17
*** prithiv has quit IRC16:18
*** piet has joined #openstack-meeting-416:20
*** prithiv has joined #openstack-meeting-416:21
*** lazy_prince has quit IRC16:29
*** mbound has joined #openstack-meeting-416:31
*** chhavi has joined #openstack-meeting-416:32
*** jed56 has quit IRC16:33
*** hdaniel has quit IRC16:40
*** salvorlando has quit IRC16:40
*** piet has quit IRC16:41
*** mbound has quit IRC16:45
*** iyamahat has joined #openstack-meeting-416:46
*** armax has joined #openstack-meeting-416:47
*** cdelatte has joined #openstack-meeting-416:50
*** ajmiller_ has quit IRC16:51
*** piet has joined #openstack-meeting-416:51
*** cartik has joined #openstack-meeting-416:56
*** avarner_ has quit IRC17:01
*** avarner has joined #openstack-meeting-417:01
*** dims_ has joined #openstack-meeting-417:03
*** dims has quit IRC17:04
*** ihrachys has quit IRC17:06
*** piet has quit IRC17:06
*** salv-orlando has joined #openstack-meeting-417:06
*** kebray has quit IRC17:09
*** julim has quit IRC17:11
*** salv-orlando has quit IRC17:11
*** ihrachys has joined #openstack-meeting-417:22
*** kebray has joined #openstack-meeting-417:22
*** ihrachys has quit IRC17:23
*** ihrachys has joined #openstack-meeting-417:23
*** javeriak has joined #openstack-meeting-417:24
*** kebray has quit IRC17:24
*** kebray has joined #openstack-meeting-417:26
*** javeriak_ has joined #openstack-meeting-417:26
*** javeriak has quit IRC17:28
*** krtaylor has quit IRC17:30
*** brucet has joined #openstack-meeting-417:31
*** krtaylor has joined #openstack-meeting-417:32
*** markvoelker has joined #openstack-meeting-417:32
*** irenab_ has joined #openstack-meeting-417:34
*** irenab has quit IRC17:35
*** irenab_ is now known as irenab17:35
*** salv-orlando has joined #openstack-meeting-417:36
*** markvoelker has quit IRC17:37
*** javeriak has joined #openstack-meeting-417:37
*** javeriak_ has quit IRC17:38
*** degorenko is now known as _degorenko|afk17:40
*** crinkle_ is now known as crinkle17:40
*** chhavi has quit IRC17:41
*** bpokorny has joined #openstack-meeting-417:41
*** piet has joined #openstack-meeting-417:42
*** neelashah has quit IRC17:42
*** blahRus1 has joined #openstack-meeting-417:46
*** blahRus has quit IRC17:48
*** prithiv has quit IRC17:49
*** ihrachys has quit IRC17:52
*** piet has quit IRC17:53
*** emagana has quit IRC17:53
*** iyamahat has quit IRC17:58
*** SimonChung1 has quit IRC18:02
*** neelashah has joined #openstack-meeting-418:03
*** emagana has joined #openstack-meeting-418:08
*** uck has joined #openstack-meeting-418:08
*** amotoki has quit IRC18:12
*** emagana has quit IRC18:12
*** ninag has quit IRC18:22
*** ninag has joined #openstack-meeting-418:23
*** hvprash has joined #openstack-meeting-418:24
*** hvprash_ has joined #openstack-meeting-418:25
*** brucet has quit IRC18:26
*** brucet has joined #openstack-meeting-418:26
*** ninag has quit IRC18:28
*** emagana has joined #openstack-meeting-418:28
*** hvprash has quit IRC18:29
*** brucet has quit IRC18:32
*** emagana has quit IRC18:32
*** ninag has joined #openstack-meeting-418:44
*** avarner has quit IRC18:48
*** avarner has joined #openstack-meeting-418:48
*** DevonBoatwright has joined #openstack-meeting-418:52
*** DevonBoatwright has left #openstack-meeting-418:53
*** irenab has quit IRC18:53
*** emagana has joined #openstack-meeting-418:59
*** banix has quit IRC18:59
*** neelashah has quit IRC19:00
*** ninag has quit IRC19:00
*** ninag has joined #openstack-meeting-419:01
*** cartik has quit IRC19:01
*** piet has joined #openstack-meeting-419:01
*** fawadkhaliq has quit IRC19:02
*** emagana has quit IRC19:03
*** ninag has quit IRC19:05
*** neelashah has joined #openstack-meeting-419:05
*** hdaniel has joined #openstack-meeting-419:09
*** SimonChung has joined #openstack-meeting-419:09
*** emagana has joined #openstack-meeting-419:09
*** dshakhray has quit IRC19:09
*** emagana has quit IRC19:09
*** emagana has joined #openstack-meeting-419:09
*** spzala has joined #openstack-meeting-419:12
*** kebray has quit IRC19:14
*** piet has quit IRC19:19
*** ninag has joined #openstack-meeting-419:19
*** irenab has joined #openstack-meeting-419:19
*** ninag has quit IRC19:22
*** ninag has joined #openstack-meeting-419:22
*** kebray has joined #openstack-meeting-419:23
*** neelashah has quit IRC19:27
*** neelashah has joined #openstack-meeting-419:27
*** ninag has quit IRC19:27
*** salv-orlando has quit IRC19:30
*** markvoelker has joined #openstack-meeting-419:32
*** neelashah1 has joined #openstack-meeting-419:36
*** ninag has joined #openstack-meeting-419:36
*** neelashah has quit IRC19:36
*** banix has joined #openstack-meeting-419:36
*** markvoelker has quit IRC19:37
*** SimonChung has quit IRC19:46
*** uck has quit IRC19:49
*** padkrish has joined #openstack-meeting-419:56
*** padkrish has quit IRC19:57
*** sigmavirus24 is now known as sigmavirus24_awa19:58
*** bobh has joined #openstack-meeting-419:59
*** ninag has quit IRC20:04
*** jmckind has joined #openstack-meeting-420:05
*** ninag has joined #openstack-meeting-420:05
*** ninag has quit IRC20:10
*** bobh has quit IRC20:11
*** mbound has joined #openstack-meeting-420:12
*** dtardivel has quit IRC20:18
*** javeriak has quit IRC20:19
*** sigmavirus24_awa is now known as sigmavirus2420:25
*** dshakhray has joined #openstack-meeting-420:29
*** piet has joined #openstack-meeting-420:31
*** piet has quit IRC20:33
*** piet has joined #openstack-meeting-420:34
*** ninag has joined #openstack-meeting-420:40
*** salv-orlando has joined #openstack-meeting-420:42
*** piet has quit IRC20:47
*** piet has joined #openstack-meeting-420:48
*** uck has joined #openstack-meeting-420:49
*** uck has quit IRC20:54
*** mriedem has joined #openstack-meeting-421:00
mriedem#startmeeting stable21:00
openstackMeeting started Mon Feb 15 21:00:25 2016 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: stable)"21:00
openstackThe meeting name has been set to 'stable'21:00
*** irenab_ has joined #openstack-meeting-421:00
tonybmriedem: howdy21:00
* mriedem waits for the masses21:00
* tonyb is always here ;P21:00
*** irenab has quit IRC21:01
*** irenab_ is now known as irenab21:01
mriedemi know HPE has today off for a holiday so some people will be gone21:01
mriedemthere isn't a ton to go over21:01
mriedemanyway, let's just start and people can roll in, or not21:02
mriedem#link agenda https://wiki.openstack.org/wiki/Meetings/StableTeam#Agenda21:02
mriedem#topic status21:02
*** openstack changes topic to "status (Meeting topic: stable)"21:02
mriedem#link stable tracker https://etherpad.openstack.org/p/stable-tracker21:02
*** zeih has joined #openstack-meeting-421:02
mriedemfor the periodic stable jobs, i've mostly noticed the trove failures21:02
mrungeo/ sorry for being late21:02
mriedemwhich for kilo there is the change here https://review.openstack.org/#/c/276934/21:02
mriedemmrunge: o/21:03
tonybmriedem: Yeah and that's blocked by somethign else but I don't recall what.21:03
mriedem^ looks like it just needs some project-config love21:03
mriedemtonyb: you said in there trove services weren't running so no tests ran and it puked21:03
tonyb.... Oh yeah the gate config on kilo is wonky they asked for help figuring out why21:03
mriedemsounds like the sahara thing with devstack plugins21:03
mriedemi put a comment in there21:03
tonybmriedem: Yeah It just hasn't bubbled up yet21:03
mriedemthere was a new thing on my radar today21:04
mriedemstable/liberty https://bugs.launchpad.net/oslo.service/+bug/152959421:04
openstackLaunchpad bug 1529594 in oslo.service "[stable/liberty] gate-tempest-dsvm-neutron-src-oslo.service fails with "ContextualVersionConflict: (oslo.service 0.9.1.dev6 (/opt/stack/new/oslo.service), Requirement.parse('oslo.service>=0.12.0'), set(['oslo.messaging']))"" [High,Confirmed]21:04
mriedemoslo.service on stable/liberty is running one of those -src- jobs,21:04
mriedemthat blows up with a version conflict with oslo.messaging due to upper-constraints21:05
tonybWe need to think hard about the value of the -src- jobs in stable21:05
mriedemfor now i've just proposed that we exclude the job from stable/liberty for oslo.service since it's fundamentally broken https://review.openstack.org/#/c/280328/21:05
mriedemtonyb: yeah, at least stable/liberty21:05
mriedemi put alternatives in that change21:05
mriedemneither are great21:06
tonybmriedem: That's the second time we've seen liberty, -src- jobs and constrainst just fail to get along.21:06
mriedemwhat i'd like to do is just cap oslo.messaging in stable/liberty<2.6.021:06
mriedembut i feel like people will freak out if i propose that21:06
tonybI *think* we could modify the job to edit-constrainst but that might not work21:06
* tonyb will read the commit message21:07
mriedemwell, even if that does work, does it reflect reality?21:07
mriedemwe can do all sorts of things to make tests pass21:07
mriedembut the fact is oslo.service<0.12.0 won't work with oslo.messaging 3.0.0, which is what's in u-c on stable/liberty21:07
mriedemanyway, let's move on21:08
mriedemi think we're just going to keep whacking these moles21:08
tonybYeah probably21:08
mriedemthe other kilo thing was your fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/154298421:08
openstackLaunchpad bug 1542984 in Python Fixtures "fixtures 1.2.0 isn't compatible with testtools 2.0.0" [Undecided,New]21:08
mriedemtonyb: did you want to threaten lifeless on that again or should i this time? :)21:09
tonybmriedem: Yeah I'll try to get his attention today.21:09
*** piet has quit IRC21:09
mriedemok, cool, thanks21:09
mriedem#action tonyb to talk to lifeless about fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/154298421:09
tonybif I don't get traction I'll lean on you21:09
mriedemok21:09
mriedem#topic previous agenda items21:09
*** openstack changes topic to "previous agenda items (Meeting topic: stable)"21:09
mriedem#undo21:10
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x9775610>21:10
mriedem#topic previous action items21:10
*** openstack changes topic to "previous action items (Meeting topic: stable)"21:10
mriedemmrunge to follow up on server projects (e.g. horizon) being released to pypi from stable branches21:10
mriedemi can't remember what there was to follow up on there21:10
mrungeuhm, there was a mail from dhellmann on openstack-dev21:10
mrungehttp://lists.openstack.org/pipermail/openstack-dev/2016-February/086183.html21:10
mrungeit was about the announcement of server packages to pypi21:10
mriedemoh, so that was just a bug and doug fixed it21:11
mrungeexactly21:11
mriedemok, cool21:11
mriedemmoving on21:11
mriedemmriedem to nudge mistral stable CPL to update https://review.openstack.org/#/c/273223/21:11
mriedemthat's done, there was another change that needed reverting21:11
mriedemnow i'm +1 on the mistral 1.0.1 release request21:11
mriedemmriedem to follow up with mestery and/or ihar on releasing from stable more often if they are going to backport a lot of changes frequently21:11
mriedemalso done http://lists.openstack.org/pipermail/openstack-dev/2016-February/086158.html21:12
mriedemmestery is going to do more frequent stable neutron release requests21:12
mriedemmriedem to update the stable policy with what it means to be actively maintaining stable branches for a project21:12
mriedemi have that patch here: https://review.openstack.org/#/c/280372/21:12
mriedemso reviews appreciated21:12
mriedem^ is actually part of a series that cleans up some of the stable branch docs21:12
* dims_ peeks21:13
tonybmriedem: I'll look at them today21:13
mriedemthanks21:13
mrungein the past, we had issues with string changes in backports21:13
mriedemit's pretty simple21:13
*** sarob_ has joined #openstack-meeting-421:14
mrungei.e. string change == not allowed for backports21:14
mriedemmrunge: is that just horizon?21:14
mriedemb/c now the translation stuff happens on stable branches also21:14
mrungehmm, yes and no21:14
mriedemat least for stable/liberty21:14
mrungeexactly. it's not that simple any more21:14
tonybYeah if you change a transtalted string you loose all the translations :(21:14
mrungeclient packages and even server packages now have translations21:14
mriedemdoes horizon key off the translations or something? i think doug-fish has tried explaining it to me once.21:15
*** sarob_ has quit IRC21:15
*** _sarob has joined #openstack-meeting-421:15
tonybbut at least on liberty they can be re-translated21:15
mriedemtonyb: yeah21:15
mrungeI wonder if we should have something about translations in the guide21:15
mrungeas this is somehow unknown21:15
mriedemmrunge: if you think something is missing feel free to push up a change to add it in the review guidelines21:15
tonyb+121:16
mrungeack21:16
mriedemi know sometimes new translatable strings are backported, but that's less of an issue in my mind21:16
mriedemusually new exceptions or something21:16
mrungeI have an issue with "sometimes"21:16
mrungei.e that's not a clear rule21:16
tonybWe shoudl probably ask Daisy21:16
mriedemso you don't ever want them?21:16
mrungetwofold: yes for as many as possible21:17
mriedemit's definitely a different animal for horizon21:17
mriedemif your page is all chinese and then you have some english show up21:17
mrungeand no: as it makes backporting complicated: you can not guarantee a to have a translation backport21:17
mriedemin the server projects it might be a logging statement or something that doesn't get back to the end user21:17
mrungehttps://github.com/openstack/neutron/tree/master/neutron/locale21:18
mrungethat's translations for neutron21:18
mrungejust to illustrate, it's not only horizon21:18
mriedemyeah i know21:18
mrungeok.21:18
mriedembut my point is, if nova backports a new i18n string that is like a warning log in the service logs, i don't have a problem with that21:19
mriedemit's a bigger issue for horizon21:19
mrungeah, ok. that's different21:19
mrungeI get you21:19
mriedemnew rest api response exception messages, that's something we'd have to think about21:19
mrungelet's iterate over patches21:19
mriedemsure21:19
mriedemok, last action item from last week21:20
mriedemttx to propose corresponding governance review21:20
mriedemthat's here: https://review.openstack.org/#/c/277918/21:20
tonybbrb21:20
mriedemthere is already a fun issue bubbling up in that one, which is, if a project has stable branches that wouldn't pass the policy (backported features or something), but then wants to get the follows-policy tag, when do they get the tag? say stable/kilo is bad and stable/liberty+ is good21:21
mriedemdo they not get the tag until stable/kilo is gone?21:21
mriedemsince tags don't have any metadata on them, like a since:liberty meta21:21
mrungeheh21:21
mriedemanyway, flaper87 raised that point, so we're discussing in the change21:21
mriedemin practice i don't think it's probably going to be a huge issue once the tag is rolled out21:21
mriedemi have a feeling that projects which have messy stable branches are going to take awhile to get used to following policy anyway21:22
mriedem#topic release news21:22
*** openstack changes topic to "release news (Meeting topic: stable)"21:22
mriedemthis is just a reminder to stable CPLs to think about stable/liberty release requests around the time of m-321:22
mriedemper dhellmann's email http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html21:22
mriedem#info consider stable/liberty point releases around m-3 per http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html21:23
mriedemno stuck reviews so i'm skipping that21:23
mriedemi don't think we have any updates on tooling, so skipping that21:23
mriedem#topic open discussion21:24
*** openstack changes topic to "open discussion (Meeting topic: stable)"21:24
mriedemdoes anyone have anything?21:24
mrungenope21:24
mriedemand with tony gone, i think that's all21:24
tonybmriedem: just a general observation that not all the stable CPL's hang out in -stable21:24
mriedemtonyb: yeah, or by default PTLs21:24
tonybmriedem: Yeah. I don't know if it's a problem21:25
mriedem#action mriedem to send a reminder to -dev ML for stable CPLs/PTLs to hang out in #openstack-stable21:25
mriedemhow's that21:25
tonybthen other day I just jumped onto the appropriate project channel and asked for reviews21:25
tonybthat worked21:25
tonyb:)21:25
mriedemyeah that's usually what i do21:25
*** sridhar_ram has joined #openstack-meeting-421:25
mriedemi think it is an indicator of involvement though21:25
mrungesounds like a sane thing to do21:25
mrungeyes21:26
mriedemmaybe we should add that to my docs patch on what being active means21:26
mriedemi'll do that21:26
mriedemok, anything else?21:26
*** zeih has quit IRC21:26
tonybI know that becuase of timezones it's not complete coverage but as you say it's a good indication of investment21:26
tonybmriedem: not from me21:26
mriedemok, will end it. thanks tonyb/mrunge21:27
mriedem#endmeeting21:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:27
openstackMeeting ended Mon Feb 15 21:27:15 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-15-21.00.html21:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-15-21.00.txt21:27
openstackLog:            http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-15-21.00.log.html21:27
mrungethank you!21:27
*** piet has joined #openstack-meeting-421:29
*** dshakhray has quit IRC21:31
*** markvoelker has joined #openstack-meeting-421:33
*** cdelatte has quit IRC21:35
*** mriedem has left #openstack-meeting-421:35
*** SimonChung has joined #openstack-meeting-421:35
*** markvoelker has quit IRC21:38
*** ninag has quit IRC21:39
*** neelashah1 has quit IRC21:43
*** fnaval has joined #openstack-meeting-421:44
*** cdelatte has joined #openstack-meeting-421:50
*** deva_ has joined #openstack-meeting-421:54
*** thorst has quit IRC21:58
*** deva_ has quit IRC22:00
*** salv-orl_ has joined #openstack-meeting-422:03
*** padkrish has joined #openstack-meeting-422:03
*** thorst has joined #openstack-meeting-422:04
*** salv-orlando has quit IRC22:05
*** tkaczynski has quit IRC22:07
*** prithiv has joined #openstack-meeting-422:07
*** thorst has quit IRC22:09
*** banix has quit IRC22:10
*** piet has quit IRC22:14
*** thorst has joined #openstack-meeting-422:25
*** mbound has quit IRC22:26
*** blahRus1 has quit IRC22:26
*** vhoward has quit IRC22:27
*** shihanzhang has quit IRC22:28
*** piet has joined #openstack-meeting-422:28
*** shihanzhang has joined #openstack-meeting-422:29
*** thorst has quit IRC22:29
*** kebray has quit IRC22:30
*** padkrish has quit IRC22:30
*** ajmiller has joined #openstack-meeting-422:31
*** bharathm has quit IRC22:33
*** kebray has joined #openstack-meeting-422:34
*** padkrish has joined #openstack-meeting-422:35
*** armax has quit IRC22:36
*** bharathm has joined #openstack-meeting-422:36
*** piet has quit IRC22:37
*** piet has joined #openstack-meeting-422:38
*** SimonChung has quit IRC22:43
*** lbragstad_ has joined #openstack-meeting-422:56
*** SimonChung has joined #openstack-meeting-422:58
*** hippiepete has quit IRC23:01
*** avarner has quit IRC23:07
*** piet has quit IRC23:09
*** krtaylor has quit IRC23:11
*** piet has joined #openstack-meeting-423:11
*** jmckind has quit IRC23:12
*** yamamoto has quit IRC23:13
*** yamamoto has joined #openstack-meeting-423:13
*** ajmiller has quit IRC23:13
*** galstrom is now known as galstrom_zzz23:14
*** yamamoto has quit IRC23:14
*** sridhar_ram has quit IRC23:21
*** krtaylor has joined #openstack-meeting-423:23
*** sigmavirus24 is now known as sigmavirus24_awa23:25
*** markvoelker has joined #openstack-meeting-423:34
*** markvoelker has quit IRC23:38
*** Jeffrey4l has joined #openstack-meeting-423:39
*** dims_ has quit IRC23:41
*** banix has joined #openstack-meeting-423:45
*** yamamoto has joined #openstack-meeting-423:48
*** bpokorny has quit IRC23:48
*** reedip_away is now known as reedip23:50
*** spotz is now known as spotz_zzz23:50
*** hdaniel has quit IRC23:52
*** banix has quit IRC23:55
*** yamamoto has quit IRC23:55
*** dims has joined #openstack-meeting-423:57
*** padkrish has quit IRC23:58

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