Monday, 2016-01-04

*** salv-orl_ has joined #openstack-meeting-400:06
*** salv-orlando has quit IRC00:09
*** markvoelker has joined #openstack-meeting-400:12
*** galstrom is now known as galstrom_zzz00:27
*** zeih has joined #openstack-meeting-400:30
*** zeih has quit IRC00:34
*** May-meimei has joined #openstack-meeting-401:05
*** salv-orl_ has quit IRC01:11
*** salv-orlando has joined #openstack-meeting-401:12
*** bobh has joined #openstack-meeting-401:14
*** bobh has quit IRC01:23
*** bobh has joined #openstack-meeting-401:26
*** galstrom_zzz is now known as galstrom01:27
*** armax has quit IRC01:29
*** baohua has joined #openstack-meeting-401:30
*** zeih has joined #openstack-meeting-401:31
*** bobh has quit IRC01:32
*** zeih has quit IRC01:35
*** Sukhdev has joined #openstack-meeting-401:59
*** baoli has joined #openstack-meeting-402:09
*** baoli has quit IRC02:10
*** baoli has joined #openstack-meeting-402:16
*** bobh has joined #openstack-meeting-402:17
*** galstrom is now known as galstrom_zzz02:26
*** baoli has quit IRC02:29
*** zeih has joined #openstack-meeting-402:32
*** yasui_ has quit IRC02:35
*** zeih has quit IRC02:36
*** baoli has joined #openstack-meeting-402:37
*** baoli has quit IRC02:43
*** sdake has joined #openstack-meeting-402:47
*** sdake_ has joined #openstack-meeting-402:49
*** sdake has quit IRC02:52
*** baoli has joined #openstack-meeting-402:56
*** krtaylor has joined #openstack-meeting-402:56
*** sdake_ is now known as sdake03:00
*** woodard has joined #openstack-meeting-403:06
*** baoli has quit IRC03:06
*** yamahata has quit IRC03:16
*** iyamahat has joined #openstack-meeting-403:18
*** Sukhdev has quit IRC03:26
*** zeih has joined #openstack-meeting-403:32
*** coolsvap|away is now known as coolsvap03:33
*** Sukhdev has joined #openstack-meeting-403:34
*** zeih has quit IRC03:37
*** beekneemech has quit IRC03:37
*** bnemec has joined #openstack-meeting-403:39
*** Jeffrey4l_ has joined #openstack-meeting-403:41
*** iyamahat has quit IRC03:42
*** woodard has joined #openstack-meeting-403:43
*** Sukhdev_ has joined #openstack-meeting-403:47
*** Sukhdev has quit IRC03:49
*** iyamahat has joined #openstack-meeting-404:02
*** woodard has quit IRC04:06
*** sdake has quit IRC04:14
*** galstrom_zzz is now known as galstrom04:29
*** zeih has joined #openstack-meeting-404:33
*** zeih has quit IRC04:37
*** Sukhdev_ has quit IRC04:43
*** Sukhdev has joined #openstack-meeting-404:44
*** bobh has quit IRC04:48
*** galstrom is now known as galstrom_zzz04:51
*** armax has joined #openstack-meeting-404:53
*** salv-orl_ has joined #openstack-meeting-405:07
*** salv-orlando has quit IRC05:07
*** baoli has joined #openstack-meeting-405:18
*** baoli has quit IRC05:23
*** baigk has quit IRC05:25
*** baigk has joined #openstack-meeting-405:25
*** bobh has joined #openstack-meeting-405:30
*** zeih has joined #openstack-meeting-405:35
*** Jeffrey4l_ has quit IRC05:37
*** iyamahat has quit IRC05:38
*** k-yasui has joined #openstack-meeting-405:39
*** zeih has quit IRC05:39
*** markvoelker has quit IRC05:39
*** dingboopt has joined #openstack-meeting-405:43
*** prashantD has quit IRC05:48
*** Jeffrey4l_ has joined #openstack-meeting-405:50
*** javeriak has joined #openstack-meeting-405:51
*** javeriak has quit IRC05:54
*** javeriak has joined #openstack-meeting-405:54
*** javeriak has quit IRC06:00
*** javeriak has joined #openstack-meeting-406:00
*** Sukhdev_ has joined #openstack-meeting-406:04
*** salv-orlando has joined #openstack-meeting-406:06
*** Sukhdev has quit IRC06:07
*** salv-orl_ has quit IRC06:09
*** grakiss has joined #openstack-meeting-406:14
*** bobh has quit IRC06:17
*** bobh has joined #openstack-meeting-406:21
*** FallenPegasus has joined #openstack-meeting-406:33
*** diga has joined #openstack-meeting-406:34
*** markvoelker has joined #openstack-meeting-406:40
*** irenab has quit IRC06:42
*** bobh has quit IRC06:43
*** lazy_prince has joined #openstack-meeting-406:43
*** markvoelker has quit IRC06:45
*** armax has quit IRC06:52
*** Sukhdev_ has quit IRC06:52
*** paul-carlton2 has joined #openstack-meeting-406:57
*** paul-carlton2 has quit IRC07:07
*** paul-carlton2 has joined #openstack-meeting-407:08
*** Jeffrey4l_ has quit IRC07:11
*** irenab has joined #openstack-meeting-407:13
*** numans has joined #openstack-meeting-407:20
*** Jeffrey4l_ has joined #openstack-meeting-407:29
*** belmoreira has joined #openstack-meeting-407:29
*** salv-orlando has quit IRC07:34
*** salv-orlando has joined #openstack-meeting-407:35
*** amotoki has joined #openstack-meeting-407:38
*** salv-orlando has quit IRC07:42
*** salv-orlando has joined #openstack-meeting-407:42
*** kevinbenton has quit IRC07:49
*** nkrinner has joined #openstack-meeting-407:51
*** kevinbenton has joined #openstack-meeting-407:54
*** Jeffrey4l_ has quit IRC07:59
*** javeriak has quit IRC07:59
*** vtech has joined #openstack-meeting-408:05
*** kevinbenton has quit IRC08:08
*** wojdev has joined #openstack-meeting-408:10
*** javeriak has joined #openstack-meeting-408:11
*** Jeffrey4l_ has joined #openstack-meeting-408:12
*** zeih has joined #openstack-meeting-408:18
*** matrohon has joined #openstack-meeting-408:28
*** zeih has quit IRC08:28
*** jed56 has joined #openstack-meeting-408:32
*** Jeffrey4l__ has joined #openstack-meeting-408:32
*** Jeffrey4l_ has quit IRC08:33
*** salv-orlando has quit IRC08:34
*** salv-orlando has joined #openstack-meeting-408:35
*** grakiss has quit IRC08:35
*** leo_ has joined #openstack-meeting-408:35
*** leo_ is now known as leo_wang08:36
*** markvoelker has joined #openstack-meeting-408:41
*** markvoelker has quit IRC08:45
*** May-meimei has quit IRC08:53
*** gsagie has joined #openstack-meeting-408:54
gsagieHello all, anyone here for dragonflow meeting? :)08:54
*** gampel1 has joined #openstack-meeting-408:55
*** kun_huang has joined #openstack-meeting-408:56
digagsagie: Hi08:56
*** gampel1 has quit IRC08:56
gsagiehi diga08:56
*** gampel has joined #openstack-meeting-408:57
gsagiegood to see you here08:57
gsagiehi kun_huang, gampel08:57
digagsagie: NP08:57
gampelhi everyone08:57
*** ianychoi has joined #openstack-meeting-408:57
kun_huango/08:57
gsagie#startmeeting dragonflow08:58
openstackMeeting started Mon Jan  4 08:58:08 2016 UTC and is due to finish in 60 minutes.  The chair is gsagie. Information about MeetBot at http://wiki.debian.org/MeetBot.08:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:58
*** openstack changes topic to " (Meeting topic: dragonflow)"08:58
openstackThe meeting name has been set to 'dragonflow'08:58
gsagie#info gampel, kun_huang, diga, yuli_s, gsagie in meeting08:58
gsagie#info Shlomo will not attend this meeting08:58
gsagieok, lets start with the first topic08:59
*** yuli_s has joined #openstack-meeting-408:59
gsagie#topic security groups08:59
*** openstack changes topic to "security groups (Meeting topic: dragonflow)"08:59
yuli_shello !08:59
*** abaron has joined #openstack-meeting-408:59
gsagiehi yuli_s!08:59
*** javeriak has quit IRC08:59
gsagie#info abaron and yuli_s in meeting :)08:59
gsagie#link security groups design https://review.openstack.org/#/c/261903/09:00
gsagiedingoboopt: ping09:00
dingbooptpong09:00
gsagiedingboopt: would you please share your progress on security groups09:00
dingbooptI have reviewed the bp, and write some code about configuring DF09:01
gsagie#link https://review.openstack.org/#/c/262634/09:01
dingbooptsecurity group  in DF DB09:01
gsagieyeah we will start reviewing this patch09:02
gsagieyou need to fix some pep8 errors but looks good otherwise09:02
dingbooptyes, I will fix it as soon as possible09:02
gsagieAnyone has any comments/ideas about the security group impl design? because the next step would be to start implementing it09:02
*** raofei has joined #openstack-meeting-409:02
gampellooks good to me09:02
gsagiehi raofei!09:02
raofeihi gsagie09:03
gsagieok, dingboopt i think the next step will be to read the security groups configuration in the controller and adds some logic that implements the configuration to flows09:03
dingbooptok09:04
gsagiedo you have any questions regarding that step?09:04
dingbooptcurrently no09:04
gampelgsagie: we all set on the second option ?09:04
gsagie#action dingboopt finish and merge security groups configuration from plugin09:04
gsagie#action dingboopt start reading sg configuration from the controller and sending to sg application09:04
gsagiegampel: i am, would like to hear other opinions09:05
gsagiebut i think we can adjust the code between the two solutions very quickly anyway09:05
gsagieplease everyone review the spec and see everything is ok09:06
gsagieanything else on this topic?09:06
*** May-meimei has joined #openstack-meeting-409:06
raofeiexcept sg, do we need start other features concurrently09:06
gsagieraofei: we have some tasks yeah, are you available to take anything right now?09:07
raofeiOK, review will be done ASAP.09:07
gsagiei will just get to it in next topic (blueprints)09:07
gampeldistributed DNAT  is up for taking09:07
gsagielets move to this topic09:07
gsagie#topic blueprints09:07
*** openstack changes topic to "blueprints (Meeting topic: dragonflow)"09:07
*** sdake has joined #openstack-meeting-409:08
gsagieraofei: there is a distributed DNAT spec, would you like to start working on that?09:08
gampellink: https://github.com/openstack/dragonflow/blob/master/doc/source/specs/distributed_dnat.rst09:08
gsagie#link http://docs.openstack.org/developer/dragonflow/specs/distributed_dnat.html09:08
gsagiethanks gampel :)09:08
gsagieraofei: ?09:08
gsagieYou can start the first part, of just translating the configuration from the neutron plugin to DF DB09:09
gsagiethis will be a good rampup task09:09
raofeiI'd like to do. but i'm not sure whether I can start it right now. I think I may lauch this task if the networking-sfc testing is done in this week09:09
gsagieok, so lets talk later this week, i will optionally put this on you09:10
raofeiok. I will try to start it.09:10
gsagie#action raofei optionally start looking at distributed dnat task09:10
gsagiethanks raofei! greatly appreciated09:10
raofeimy pleasure.09:11
gsagieok, i have written a spec about MAC spoofing protection, its complimenting feature for security groups09:11
gsagie#link https://review.openstack.org/#/c/263019/09:11
gsagieplease all help to review the spec09:11
gsagiei also havent gotten to it yet but i am suppose to write a spec about publish-subscribe abstraction, as nick-ma asked for it09:12
raofeiOK, it's quite similary with security group.09:13
gsagiegampel: maybe you can update us regarding that?09:13
*** holser_ has left #openstack-meeting-409:13
gampelyes we are trying to integrate nanomsg as the pub syb09:13
gsagieraofei: its implicitly implemented09:13
gampelit will allow use of the DB pub/sub or use the DF implementations09:14
gsagie#action gsagie write publish-subscriber abstraction spec09:14
gampelthis will allow us to add this support to DB like Ram Cloud that do not support pub/sub09:14
gampeland will allow us to implement the Selective proactive in a very simple way09:15
gsagiethanks gampel09:15
gsagiei am also working on writing two more specs, one is for L2 ARP supression, currently we add ARP responders only for router ports there was a request to also add them for all ports09:16
gsagiegoing to be pretty straight forward09:16
raofeidoes dhcp spoofing will be done also under port security feature?09:16
gsagieraofei: currently all DHCP traffic for DHCP enabled networks is being directed to Dragonflow DHCP application, so we believe its safe for that case09:17
raofeiwill dhcp spoofing  be done also under sg or ip/mac spoofing?09:17
gsagieraofei: do you have another use case when there is a problem? the only case i see is for networks with DHCP disabled and the user brings their own DHCP VM09:18
gampelraofei: the only way a DHCP traffic from a VM will go out is in DHCP disable networks09:19
raofeiYes, i think dhcp spoofing is done indirectly due to the DHCP application mechnisam.09:19
gsagieraofei: yeah, but let me know if you think about a problematic scenario, it should be done as part of the MAC spoofing spec09:20
gampelYes when DHCP is disable we allow the user to implement it in a VM but we can add a configuration to allow or disallow this09:20
gsagiethere are other blue prints that i am going to add specs too, will update in next meeting09:20
gsagieworking on a mechanism to sync DB's between Neutron and DF09:21
gsagie#link https://review.openstack.org/#/c/263035/09:21
gsagiethat will help solve inconsistent states09:21
gampelthis is a period task ?09:22
gsagiehavent decided yet, we can have different configurations, lets discuss it over the spec once i write it09:22
gampelI think that we should look in the patch from Li MA as well the role back patch09:23
gsagiefor example, one that is actually doing periodic sync, one that is only alerting of inconsistent and so on..09:23
gsagieyeah09:23
gsagie#link https://review.openstack.org/#/c/262423/09:23
gsagiegampel: this can also be used for cases like with RAMcloud after a restart..09:24
gampel gsagie: good idea09:24
gsagiegampel: i also would like to start writing a plan for how to integrate selective proactive in steps, for example first step sync all but only send related information to applications09:25
gsagieand so on09:25
gsagie#action gsagie start writing a plan for selective proactive integration09:25
gampelwe should  think about it and make sure we have a plan for the DB inconsistent09:25
gsagieok09:26
gsagieCan i put this on you for now?09:26
gampelyes09:26
gampelsure09:26
gsagie#action gampel have a plan for DB inconsistent problems between DF and Neutron09:26
gsagieok, anyone has anything else regarding blueprints?09:26
gampelI think that we should move all the DB drivers in the new service09:27
gsagiegampel: DB topic is after..09:27
gsagie#topic testing09:27
*** openstack changes topic to "testing (Meeting topic: dragonflow)"09:27
gsagieyuli_s: ping09:27
gsagieyuli_s: would you please share with us your progress regarding fullstack tests ?09:28
yuli_sYes09:29
yuli_sSure09:29
yuli_sI found a solution for sequential tests09:29
yuli_sto fix the raise conditions I have while running tests09:30
gsagieyou added port creation/deletion tests as i saw09:30
gsagieok, good job09:30
*** javeriak has joined #openstack-meeting-409:30
gsagie#link https://review.openstack.org/#/c/263042/  yuli_s fullstack patch09:30
yuli_si am going to comment out new tests for now and revert them later as you sugested privately09:31
gsagiefor next meeting you moving to flow tests and update right?09:31
gsagieokie09:31
yuli_sYes,09:31
gsagie#action yuli_s work on update fullstack tests09:31
gsagie#action yuli_s work on OVS flows related tests09:31
gsagiebasically yuli is adding fullstack tests that will check that we configure the correct OVS flows for various different scenarios09:32
gsagiei would also like to refactor the base test class, so we can have few files for different tests and not everything in the same class, so the base one will have the clients (neutron, DF DB) and then every test class will inherit from uit09:32
gsagie#action gsagie refactor fullstack test class09:33
gsagiefor the unit tests, we have encounter a small problem as OVS python binding dont yet have python3 support so our unit tests keeps failing in the gate09:33
gsagiei have added patch to solve it in the meantime09:33
gsagie#link https://review.openstack.org/#/c/262981/   remove python3 gate tests09:34
gsagiei know that russellb is working on making OVS package work with Python3, so we should have solution quickly and i will start adding unit tests examples09:34
gsagiediga: are you interested to work on that as well?09:34
gsagiekun_huang: ping09:35
gsagiediga: ping09:35
gsagie#action gsagie add unit tests examples once python3 job is fixed09:36
kun_huanggsagie: not yet, I'm trying to supply HWs ASAP09:36
kun_huangbtw nick-ma has a fever these days, he is in hospital now...09:36
gsagiekun_huang: ok, we are also working here to create performance tests enviorments so we can debug L3 east-west performance and data path performance09:36
digagsagie: hi09:37
gsagiekun_huang: ohh sorry to hear that :( please send him our regards and hope he feels better soon09:37
digayes09:37
gampelkun_huang: I am sorry to hear , yes please send mine as well09:37
kun_huangno problem09:37
gsagie#info warm regards to nick-ma and hope he feels better soon :)09:37
gsagiekun_huang: thanks, Shlomo from our team is going to start working on the setup from our end, i will connect the two of you so you could share information09:38
gsagiei have found Rally are doing some work in order to support benchmarking same as VMTP/Shaker projects.09:38
gsagie#link https://review.openstack.org/#/q/status:open+project:openstack/rally+branch:master+topic:bp/vm-workloads-framework09:39
gsagie#link https://review.openstack.org/#/c/254851/609:39
gsagiemaybe will be good to look at them09:39
gsagieas well09:39
gsagiefor automating the tests09:39
kun_huangI know that work09:39
gsagiecool :)09:39
kun_huanganyway, let's build the setup first09:39
gsagie#info kun_huang waiting for HW for scale testing09:40
gsagiekun_huang: we also could use any help you can provide with performance testing that is not related to scale, like L3 in 1-2 compute nodes, do you have any experience with Shaker/VMTP or any other automated tests written that you can share?09:40
kun_huangI have built VMTP inside FusionNetwork09:41
kun_huangas daily test in our CI09:41
gsagiekun_huang: cool, thats is very use full, i will tell Shlomo to sync with you regarding that, i think we need something like that for Dragonflow as well09:42
gsagie#action gsagie, Shlomo sync with kun_huang regarding daily VMTP CI tests for Dragonflow09:42
gsagieanything else for testing? gampel?09:42
gampelno09:43
gsagieok09:43
gsagie#topic DB09:43
*** openstack changes topic to "DB (Meeting topic: dragonflow)"09:43
gsagieWe are planning to merge RethinkDB, gampel will work on fixing any final things that needs to be addressed09:44
gsagiegampel: right?09:44
gampelwill do yes09:44
*** bobh has joined #openstack-meeting-409:45
gampelI think that we should move  all the DBs drivers into a service configuration09:45
gsagieok, thanks, sorry for the rush but we running out of time :)09:45
gampellike we did for etcd09:45
*** diga_ has joined #openstack-meeting-409:45
gsagie#action move all DBs installtions into services similar to what we did with etcd09:45
gsagie#action gampel merge and fix final things with RethinkDB09:45
gsagienick-ma is not here, but he is working on ZooKeeper integration, he will update us next meeting09:46
*** zeih has joined #openstack-meeting-409:46
gsagie#info nick-ma update next meeting regarding zookeeper integration09:46
*** diga has quit IRC09:46
gsagieWe should review the patch for cluster configuration09:46
gsagie#link https://review.openstack.org/#/c/261731/09:46
gampelgsagie: Ok will do09:46
gsagiegampel: you did :) i have too09:47
gsagiejust noticed09:47
gsagiediga, can i assign a task for you to start looking at unit tests?09:47
gsagieyou told me you want to take it09:47
diga_yes09:47
gampelwait i will rebase it today today09:47
gsagie#action diga start working on unit tests for the controller09:47
gsagiediga_ : i started to create the needed things for it, look at this patch:09:48
diga_gsagie: okay09:48
gsagie#link https://review.openstack.org/#/c/262796/09:48
gsagiestill need to wait for the infrastructure to remove python3 jobs, hopefully today or tommorow09:48
gsagiefrom the gate09:48
gsagie#topic bugs09:48
*** openstack changes topic to "bugs (Meeting topic: dragonflow)"09:48
*** pbourke has joined #openstack-meeting-409:48
gsagiei forgot also, i havent looked yet but needs to look at tempest failing tests, maybe i will start converting them to bugs09:49
gsagie#action gsagie look at failing tempest tests and convert them to bugs09:49
gsagiewe should probably give more time for talking about bugs next meeting and going over all the open bugs09:49
gsagieanyone has any notable bugs?09:49
gsagiekexiaodong: ping09:50
*** bobh has quit IRC09:50
gsagieok09:51
gsagie#topic open discussion09:51
*** openstack changes topic to "open discussion (Meeting topic: dragonflow)"09:51
gsagieHappy new year everyone :)09:51
gampel Happy new year09:51
gsagieand thanks for attending the meeting and all your help09:51
yuli_sHappy new Yes09:51
gsagieif anyone has anything else please let us know09:51
yuli_shm09:51
gsagiegampel: next week we going to have the meeting?09:51
diga_Happy New Year to you all09:51
kun_huanggsagie, gampel what's your schedule of coming China?09:52
yuli_si think we need to think again about running tests sequentially09:52
gampelnot sure i think that we should postponed  the next meeting09:52
yuli_si just commited a fix to the bug09:52
gsagieyuli_s : ok, lets continue to talk about it in #openstack-dragonflow, but i agree its something we need to consider09:52
yuli_sok, great09:52
gsagiekun_huang: we come next week09:52
gsagiekun_huang: you located in hangzhou?09:53
kun_huangyep09:53
gampelkun_huang: see you next week09:53
gsagieok cool, we will meet then face to face :)09:53
kun_huangwhat's your arrived date on hangzhou?09:53
kun_huangI could make a meetup for us09:53
gsagie#info next week meeting is canceled, we will continue week after09:53
*** Prithiv has joined #openstack-meeting-409:53
kun_huangthere are some other openstack guys09:53
gampelon the 10th09:53
gsagiekun_huang: 12/109:53
gampel11th sorry09:54
gsagieohh yeah sorry 11th09:54
kun_huangarrive at 11th?09:54
gsagieok everyone thanks for attending the meeting! and see you in two weeks (next week meeting is canceled)09:54
gsagie#endmeeting09:54
gampelsue it will be great to do a meet up09:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:54
openstackMeeting ended Mon Jan  4 09:54:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-01-04-08.58.html09:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-01-04-08.58.txt09:54
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-01-04-08.58.log.html09:54
gsagiekun_huang: yeah on the 11th, will be great to meet :)09:55
*** kun_huang has left #openstack-meeting-409:55
*** Jeffrey4l__ has quit IRC09:58
*** lkoranda has quit IRC09:59
*** FallenPegasus has quit IRC10:02
*** coolsvap is now known as coolsvap|away10:04
*** Jeffrey4l__ has joined #openstack-meeting-410:11
*** zeih has quit IRC10:12
*** acabot has joined #openstack-meeting-410:13
*** zeih has joined #openstack-meeting-410:17
*** wojdev has quit IRC10:38
*** markvoelker has joined #openstack-meeting-410:42
*** markvoelker has quit IRC10:46
*** f13o has joined #openstack-meeting-410:55
*** wojdev has joined #openstack-meeting-410:57
*** zeih has quit IRC11:03
*** wojdev has quit IRC11:13
*** zeih has joined #openstack-meeting-411:15
*** vtech has quit IRC11:17
*** zeih has quit IRC11:24
*** abaron has quit IRC11:30
*** dims has joined #openstack-meeting-411:40
*** dims has quit IRC11:40
*** dims has joined #openstack-meeting-411:41
*** Jeffrey4l__ has quit IRC11:43
*** gsagie has left #openstack-meeting-411:46
*** javeriak has quit IRC11:56
*** baohua has quit IRC11:58
*** FallenPegasus has joined #openstack-meeting-412:02
*** salv-orl_ has joined #openstack-meeting-412:06
*** salv-orl_ has quit IRC12:07
*** salv-orl_ has joined #openstack-meeting-412:07
*** FallenPegasus has quit IRC12:08
*** salv-orlando has quit IRC12:09
*** markvoelker has joined #openstack-meeting-412:12
*** markvoelker has quit IRC12:17
*** zeih has joined #openstack-meeting-412:20
*** vtech has joined #openstack-meeting-412:22
*** wojdev has joined #openstack-meeting-412:28
*** sdake has quit IRC12:39
*** sdake has joined #openstack-meeting-412:40
*** diga_ has quit IRC12:46
*** bobh has joined #openstack-meeting-412:47
*** javeriak has joined #openstack-meeting-412:48
*** bobh has quit IRC12:52
*** sdake_ has joined #openstack-meeting-412:53
*** markvoelker has joined #openstack-meeting-412:55
*** sdake has quit IRC12:57
*** bobh has joined #openstack-meeting-413:02
*** baoli has joined #openstack-meeting-413:05
*** hippiepete has quit IRC13:08
*** klamath has joined #openstack-meeting-413:09
*** klamath_ has joined #openstack-meeting-413:10
*** salv-orl_ has quit IRC13:13
*** klamath has quit IRC13:14
*** salv-orlando has joined #openstack-meeting-413:14
*** Jeffrey4l__ has joined #openstack-meeting-413:24
*** hippiepete has joined #openstack-meeting-413:26
*** bobh has quit IRC13:33
*** baoli_ has joined #openstack-meeting-413:36
*** baoli has quit IRC13:38
*** dslevin_ has joined #openstack-meeting-413:41
*** dingboopt has quit IRC13:41
*** dingboopt has joined #openstack-meeting-413:43
*** javeriak has quit IRC13:45
*** dslevin_ has quit IRC13:50
*** dslevin_ has joined #openstack-meeting-413:51
*** dslevin_ has quit IRC13:51
*** FallenPegasus has joined #openstack-meeting-413:51
*** dslevin_ has joined #openstack-meeting-413:52
*** baohua has joined #openstack-meeting-413:52
*** FallenPegasus has quit IRC13:56
*** irenab has quit IRC13:57
*** fawadkhaliq has joined #openstack-meeting-413:59
*** javeriak has joined #openstack-meeting-414:00
*** baohua has quit IRC14:01
*** baohua has joined #openstack-meeting-414:03
*** javeriak has quit IRC14:03
*** javeriak has joined #openstack-meeting-414:03
*** javeriak has quit IRC14:06
*** sdake has joined #openstack-meeting-414:11
*** sdake_ has quit IRC14:12
*** woodard has joined #openstack-meeting-414:13
*** dolphm has left #openstack-meeting-414:14
*** vhoward has joined #openstack-meeting-414:16
*** jmckind has joined #openstack-meeting-414:19
*** gsagie has joined #openstack-meeting-414:19
*** julim has joined #openstack-meeting-414:23
*** bobh has joined #openstack-meeting-414:28
*** numans has quit IRC14:29
*** jpeeler has joined #openstack-meeting-414:29
*** jpeeler has quit IRC14:29
*** jpeeler has joined #openstack-meeting-414:29
*** rbak has quit IRC14:35
*** zeih has quit IRC14:39
*** jlvacation is now known as jlvillal14:40
*** zeih has joined #openstack-meeting-414:43
*** irenab has joined #openstack-meeting-414:44
*** vikasc has joined #openstack-meeting-414:46
*** zeih has quit IRC14:47
*** baohua has quit IRC14:49
gsagieHello everyone coming for Kuryr meeting :)14:51
gsagieirenab: apuimedo is still on vacation?14:51
irenabI am not sure, but probably yes14:51
irenabgsagie: I will be able to attend only for first 30 mins14:52
gsagieirenab: np, i have a feeling we will finish in 30 :)14:52
irenabgsagie: if possible, lets start with kubernetes discussion14:52
gsagieTaku is on vacation as well right?14:52
gsagieyeah, its #1 on the agenda14:52
irenabgsagie: yes14:52
gsagielets wait 5 more minutes for the official time14:52
fawadkhaliqyup yup!14:53
vikasco/14:53
*** banix has joined #openstack-meeting-414:54
*** sdake_ has joined #openstack-meeting-414:55
gsagiehi banix, vikasc, fawadkhaliq, irenab!14:56
irenabhi14:56
fawadkhaliqhi everyone!14:57
fawadkhaliqhappy new year!14:57
vikascvikasc, Hi Gal!!!14:57
vikascHappy New Year everyone :)14:57
*** rbak has joined #openstack-meeting-414:57
*** belmoreira has quit IRC14:58
*** sdake has quit IRC14:58
*** sdake has joined #openstack-meeting-415:00
gsagieok, lets start the meeting15:00
gsagie#startmeeting kuryr15:00
openstackMeeting started Mon Jan  4 15:00:28 2016 UTC and is due to finish in 60 minutes.  The chair is gsagie. 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#info irenab, vikasc, fawadkhaliq, banix, gsagie in meeting15:00
*** galstrom_zzz is now known as galstrom15:01
gsagie#info apuimedo, tfukushima are on vacations15:01
gsagie#topic kubernetes integration15:01
*** openstack changes topic to "kubernetes integration (Meeting topic: kuryr)"15:01
*** sigmavirus24_awa is now known as sigmavirus2415:01
gsagie#link https://etherpad.openstack.org/p/kuryr_k8s15:01
gsagieirenab: want to update on this?15:01
*** devvesa has joined #openstack-meeting-415:01
irenabI will try to sum-up what we have15:01
*** rbak has quit IRC15:02
gsagiebanix: i believe you have more experience on this issue as well, we should use your experience on this subject :)15:02
gsagiehi devvesa! welcome15:02
devvesagsagie: o/15:02
gsagie#info devvesa in meeting as well :)15:02
irenabOne of the missions for the Mitaka release is to provide kuryr - Kubernetes integration15:02
irenabWe started to put ideas on the etherpad  ^^15:03
*** sdake_ has quit IRC15:03
irenabWe should decide on the approach to take here if its another disctinct integration via network plugin or CNI driver15:04
devvesa#link https://etherpad.openstack.org/p/kuryr_k8s15:04
gsagieOne of the ideas irenab brought up and i wrote it there, is that we need to think about ways to expose the extra features Neutron provide to the users, so they could use for example Kubernetes anootation to configure security groups and so on..15:04
irenabgsagie: I think before extra features, we need to define the integration model15:04
irenabLooks like libnetwork reuse is not applicable at this phase15:05
gsagieirenab: agreed, i believe the only option right now is Kubernetes network plugin15:05
gsagieirenab: yes, until Kubernetes will support it15:05
gsagiebanix: any ideas on this subject?15:06
gsagieor anyone else of course :)15:06
irenabthere is a network plugin that is actually CNI Driver that invokes CNI plugins, I am in favor to explore this option15:06
*** haleyb has joined #openstack-meeting-415:06
banixsorry was away15:06
gsagienp15:06
banixyes have been following up our options with k8s15:07
banixit seems they have a different network model in mind that may want to build on15:07
banixI will know more by next week and can report back with a better understanding15:07
*** rbak has joined #openstack-meeting-415:07
irenabSo we need 1. Integration approach.  2. Data Model mapping from k8s to neutron 3. Extra features (mainly security)15:07
irenabbanix: can you please elaborate?15:08
irenabon they have different approach in mind15:08
banixyes, the integration through a plugin is the available option right now15:09
banixthere are discussions about how to map/integrate  CNI and CNM15:09
banixformer from k8 and later from libnetwork15:09
*** zeih has joined #openstack-meeting-415:10
banixi haven’t followed the latest discussions in the last two weeks15:10
irenabbanix:discussions on kubernetes-sig-network ?15:10
banixyes15:10
gsagieirenab, banix: any chance we can put this task on any of you two to write a short spec for this? or is taku also working on that?15:11
irenabgsagie:  I will start this asap15:11
banixgsagie: yes sure; will talk to irenab15:11
gsagie#action irenab, banix start writing a spec for kubernetes integration in terms of 1. Integration approach.  2. Data Model mapping from k8s to neutron 3. Extra features (mainly security)15:11
irenabbanix: great! Will be happy to collaborate on this15:11
gsagieirenab, banix: thanks!15:12
gsagiewe all should read more and be ready to discuss more concrete details next week15:12
vikasc+1 gsagie15:12
gsagiei would like us to also try to talk with deployers and understand missing use cases for networking features when deploying with Kubernetes15:12
gsagiei have some team i can check internally15:12
irenabgsagie: I beleive it both deployers and cluster admins15:13
gsagie#action gsagie understand use cases for deploying Kubernetes and update the etherpad15:13
gsagieirenab: yep15:13
irenabif you can collect data from both, will be great15:13
gsagieirenab: yeah i have some people that i can talk with, but would appreciate any more feedback15:13
irenabI can provide useful link of use cases shared in the kubernetes-sig-networking team15:14
gsagieirenab: that would be great!15:14
gsagie#action irenab provide useful link of use cases shared in the kubernetes-sig-networking team15:14
irenabhttps://docs.google.com/document/d/1ZCz_MZILzKCbFwF9gjU1YNA1YbNaw0NDsESh1P6Vcnc/edit15:14
*** zeih has quit IRC15:14
gsagie#link https://docs.google.com/document/d/1ZCz_MZILzKCbFwF9gjU1YNA1YbNaw0NDsESh1P6Vcnc/edit15:14
gsagieso anything else for Kubernetes ? i think Taku will also join you and banix as he also investigated these areas15:15
gsagieand we should be smarter next meeting hopefully15:15
*** asif has joined #openstack-meeting-415:15
*** shakamunyi has quit IRC15:15
*** barra204 has quit IRC15:15
banixsounds good15:15
irenabgsagie: banix : I think we should have initial spec up to next meeting15:15
gsagie#topic vif binding15:16
*** openstack changes topic to "vif binding (Meeting topic: kuryr)"15:16
gsagiebanix, i see you have an action item for linux bridge binding15:16
banixgsagie: I will get to it. Have been off the grid for last two weeks15:17
gsagiei dont think its any urgent task, but was wondering if you have any update15:17
gsagiebanix: np, understandable :)15:17
banixone thing that worries me is the cost in terms of latency15:17
gsagiewhat do you mean cost?15:17
banixusing an executable; I think eventually, sooner rather than later we need to load modules for drivers, etc15:17
banixgsagie: i mean specially for ovs with sec groups, there are many commands to be executed15:18
gsagiebanix: i agree, executable doesnt scale and there are already examples for that with security groups iptables CLI ;)15:18
banixwith sudo, etc15:18
gsagieheh yeah15:18
banixso i have that in my list of todos15:19
gsagie#action banix to investigate linux bridge binding and alternatives to using an executable scripts for binding15:19
gsagiebanix: ok sounds good15:19
*** spotz has joined #openstack-meeting-415:19
*** markvan has quit IRC15:20
gsagiebanix: the OVS unbind part was merged while in holiday, seems ok to me but i would verify when you have time that everything works for you too15:20
banixyes noticed that. will do.15:20
gsagieok, thanks15:20
gsagie#topic IPAM15:20
*** openstack changes topic to "IPAM (Meeting topic: kuryr)"15:20
gsagievikasc: any update for this?15:21
vikaschttps://review.openstack.org/#/c/256211/15:21
vikasci addressed banix comments on this patch15:21
gsagie#link https://review.openstack.org/#/c/256211/15:21
gsagieokie, will review it probably tommorow15:21
gsagievikasc: there is also updating the devref with the implementation details15:22
vikascthanks.. i am spending time understanding kubernetes networking model15:22
*** markvan has joined #openstack-meeting-415:22
vikascyes15:22
vikasclast week i was on vacation15:22
gsagiejust to document things better, i will add fullstack tests for it, unless you want to do it as well15:22
gsagienp15:22
*** sdake_ has joined #openstack-meeting-415:22
gsagiewas quite 2 weeks with out all of you here :)15:22
gsagie#action vikasc update devref for IPAM15:23
gsagie#action gsagie add fullstack tests for IPAM15:23
vikascsounds good15:23
gsagie#topic packaging15:23
*** openstack changes topic to "packaging (Meeting topic: kuryr)"15:23
*** ajmiller has joined #openstack-meeting-415:23
gsagiedevvesa: any update on that?15:23
devvesaNo. I didn't get any feedback15:24
devvesaI'll try to push this week15:24
gsagiedevvesa: is there anything i can help with?15:24
devvesaand test it better15:24
gsagieokie, sounds good15:24
devvesaNot now. If I have any question about the service/configuration for packaging, I'll ask in the mailing list or IRC15:24
devvesa:)15:25
gsagieokie great15:25
gsagieihar from neutron might be able to help with that15:25
*** sdake has quit IRC15:25
gsagie#action devvesa continue with packaging task and testing15:25
gsagie#topic capabilities15:26
*** openstack changes topic to "capabilities (Meeting topic: kuryr)"15:26
*** piet has joined #openstack-meeting-415:26
gsagieToni is not here, so i guess no update on that,15:26
gsagie#action gsagie check capabilities progress with apuimedo15:26
gsagie#topic docker swarm15:26
*** openstack changes topic to "docker swarm (Meeting topic: kuryr)"15:26
gsagiebanix: i see from 2 meetings ago that you conducted a demo with Kuryr and Docker Swarm anything available?15:27
*** blahRus has joined #openstack-meeting-415:27
gsagiewill be cool to post it to the mailing list15:27
banixgsagie: will do; don’t have a recorded demo but will do it15:28
banixgsagie: to be more accurate i have recorded a simple demo but will try to make a cleaner and better one in a day or two and post15:28
gsagiecool, that will be awesome, let me know when you do15:28
gsagiewe should link to it for people to see :)15:29
banixyes will do15:29
gsagie#action banix publish a recorded demo of docker swarm with Kuryr15:29
gsagiethanks!15:29
banixnp15:29
gsagie#topic testing15:29
*** openstack changes topic to "testing (Meeting topic: kuryr)"15:29
*** shakamunyi has joined #openstack-meeting-415:29
gsagieok, so regarding testing i would like to ask your premission to merge https://review.openstack.org/#/c/259744/   , apuimedo has -1 on it but he is on long time off15:30
gsagieand already approved to merge it in temporary15:30
gsagieits blocking the fullstack tests progress15:30
gsagieI already have a bug assigned to solve this issue and an idea how to do it but want it to happen in parallel15:30
banixgsagie: go for it15:31
gsagiebanix: great15:31
gsagie#action gsagie continue on fullstack tests and solve the neutron credential problem in the gate15:31
gsagiebanix: Baohua is from your team?15:32
banixgsagie: yes15:32
gsagiei guess he was on vacation as well since i havent seen him and i think you said he wants to join the testing efforts15:32
gsagielast meeting i directed him to my patches15:32
gsagiei will try to sync with him tommorow15:33
banixgsagie: yes, i will follow up with him too15:33
gsagie#action gsagie sync with Baohua regarding testing15:33
gsagie#action gsagie add Rally docker plugin15:33
gsagieAnother thing i wanted to ask you guys, i want to start adding Docker plugin for Rally, do we want to do this as part of Kuryr, or add this directly to Rally?15:34
gsagieand only use it from Kuryr15:34
fawadkhaliqgsagie: adding in Kuryr should be okay and can be managed well.15:34
gsagiewanted to ask everyone before sending the question to the list, the rally team said we can go either way where they prefer to have it in the rally repository15:34
gsagiefawadkhaliq: yeah i agree15:35
banixdon’t know I am afraid15:35
gsagiei think i will also email to the list, so we do this process in the open and get more opinions15:35
fawadkhaliqunless there is an added benefit of keeping in the Rally repo, which I can't think of right now.15:36
fawadkhaliqcool. makes sense15:36
gsagiefawadkhaliq: the only benefit is that we will have the rally team review it more closely15:36
gsagieatleast thats what i can think of15:36
fawadkhaliqreviews are significant :-)15:36
fawadkhaliqwe can consider it.15:37
gsagieokie, will send to the list and we take it from there :)15:37
fawadkhaliqsounds great!15:37
gsagiei still havent got to the magnum integration for nested containers15:37
gsagie#action gsaguie magnum integration and nested containers design15:37
gsagie#action gsagie magnum integration and nested containers design15:37
fawadkhaliqon nested containers15:37
*** sdake has joined #openstack-meeting-415:38
fawadkhaliqToni gave me an action item 2 weeks ago and we were heading into the holidays15:38
fawadkhaliqI will take a stab at writing a spec and we can iterate over it.15:38
*** jmckind has quit IRC15:38
gsagiewhich one?15:38
gsagieokie great! thanks for that15:38
*** sdake_ has quit IRC15:39
gsagie#action fawadkhaliq propose a spec for magnum integration and nested containers15:39
fawadkhaliqI will reach out for discussions :-)15:39
gsagiefawadkhaliq: important to think how we expose all the possible models to the user , for example OVS in the VM, IPVLAN usage with eBPF like you guys did and so on15:39
fawadkhaliqabsolutely15:40
gsagieand another point that came up, is how to model the Kuryr service and where, there were questions about how it can reach Neutron API from inside the VM15:40
gsagieand points like these.. just bringing them up :)15:40
*** bobh has quit IRC15:40
*** FallenPegasus has joined #openstack-meeting-415:40
gsagieok, feel free to discuss about that if you have any questions15:41
fawadkhaliqyup, thanks! will cater for them and definitely, will discuss over #kuryr15:41
gsagieokie15:41
gsagie#topic open discussion15:41
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"15:41
gsagieThanks everyone for joining the first meeting of the new year :)15:41
gsagieand welcome back everyone that had a good vacation, hope you had fun and managed to get some rest :)15:42
gsagieand good to see you all again!15:42
banixthank you!15:42
fawadkhaliqthanks and likewise!15:42
gsagieokie, good day everyone! bye15:43
gsagie#endmeeting15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:43
openstackMeeting ended Mon Jan  4 15:43:12 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-01-04-15.00.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-01-04-15.00.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-01-04-15.00.log.html15:43
*** jmckind has joined #openstack-meeting-415:43
*** Sukhdev has joined #openstack-meeting-415:44
*** FallenPegasus has quit IRC15:45
*** mtreinish has quit IRC15:46
*** vdrok has joined #openstack-meeting-415:47
*** mtreinish has joined #openstack-meeting-415:48
*** blahRus1 has joined #openstack-meeting-415:49
*** blahRus has quit IRC15:50
*** javeriak has joined #openstack-meeting-415:55
SukhdevHi folks time for Ironic-neutron meeting16:00
Sukhdev#startmeeting ironic_neutron16:01
openstackMeeting started Mon Jan  4 16:01:21 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:01
openstackThe meeting name has been set to 'ironic_neutron'16:01
*** mitchjameson has joined #openstack-meeting-416:01
SukhdevGood morning folks -16:01
Sukhdevwho is here to attend the ironic-neutron meeting?16:01
Sukhdevjroll : are you here?16:02
jroll\o16:02
*** vsaienko has joined #openstack-meeting-416:02
Sukhdevlazy_prince, vsaienko ?16:02
*** javeriak_ has joined #openstack-meeting-416:02
vsaienkohello to all16:02
Sukhdev#topic: Agenda16:02
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:02
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_January_4.2C_201616:03
Sukhdev#topic: Announcements16:03
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:03
SukhdevHappy New Year to everybody16:03
Sukhdevhope everybody had a relaxing holidays!!16:03
vdroko/ happy new year!16:04
*** javeriak has quit IRC16:04
SukhdevI was trying to catch up on the action I missed in last two weeks -16:04
lazy_prince0/16:05
Sukhdevlazy_prince : hi16:05
Sukhdev#topic: Patches under review16:05
*** openstack changes topic to ": Patches under review (Meeting topic: ironic_neutron)"16:05
vsaienkolazy_prince: hi16:05
Sukhdev#link: https://etherpad.openstack.org/p/ironic-neutron-mid-cycle16:05
* jroll wonders if devananda is around16:06
SukhdevI noticed there were bunch of updates to the patches - which is excellent16:06
*** devananda has quit IRC16:07
lazy_princeyup.. Thanks to vsaienko16:07
Sukhdevand lots of review comments as well16:07
Sukhdevyes noticed that vsaienko has been busy :-)16:07
Sukhdevvsaienko : are we ready to ship :-)16:08
vsaienkoyep16:08
Sukhdevvsaienko : perhaps you can give us an update and bring everybody to speed16:08
lazy_princethat would be helpful assuming I missed couple of meetings..16:08
vsaienkoI've rebased  patches and resolved comments16:09
lazy_princeis there anything left for me to work on.. :)16:09
vsaienkoI test all of them together, guide is on review also https://review.openstack.org/#/c/258596/7/doc/source/dev/ironic-neutron-integration.rst16:09
jrolldeva also mentioned he was able to test, mostly successfully16:10
vsaienkoI would be perfect if any body else also test them and provide feedback16:10
jrollhe found it wasn't isolating between two tenants, but it looks like the devstack stuff isn't intended to do so?16:10
vsaienkojroll: it should16:11
lazy_princeif tags are applied properly, they should be isolated..16:12
jrollvsaienko: maybe it was because the default is a provider network16:12
vsaienkofrom Newtron side each network in the tenant has unique VLAN16:12
jrollI'd have to look back at irc logs16:12
Sukhdevjroll : based upon the devstack patches, it should have16:12
*** gomarivera has joined #openstack-meeting-416:12
vsaienkoah, yes, I've missed part that configured network_provider in Ironic16:12
vsaienkobut already fixed it in last patchset, thanks vdrok!16:13
jrollhrm, he said it isolated control plane okay16:13
jrollanyway, not much use dwelling on that now16:13
Sukhdevvsaienko : the list of patches on https://etherpad.openstack.org/p/ironic-neutron-mid-cycle is up-to-date, right?16:14
vsaienkosukhdev: looks like yes16:15
*** devananda has joined #openstack-meeting-416:15
Sukhdevvsaienko : before I went on PTO, there was an issue with the devstack patches, which needed to be pushed again - wonder if those are listed correctly16:15
SukhdevI have not had time to verify recently16:15
devanandao/16:16
jrollthey look right, Sukhdev16:16
vsaienkohello devananda16:16
jrollhai devananda :)16:16
devanandaSukhdev, jroll: I tested the devstack support for that patch chain last week and confirmed it works16:16
devanandanodes are moved between the provisioning provider network and the tenant network, etc, as expected16:16
jroll\o/16:16
Sukhdevdevananda : Wow!! cool - thanks16:16
devanandahowever I had difficulty creating >1 tenant network and separating traffic from tenant A and tenant B16:16
devanandaI suspect I was doing something wrong with regards to creating the neutron networks16:17
Sukhdevdevananda : oh I see -16:17
devanandaI started reviewing the patch chain over the weekend, but haven't gotten too far. at this point, it will be mostly nitpicks -- little things in the db code that I would like to see improved, etc16:17
*** gampel has quit IRC16:18
Sukhdevdevananda : I wonder how you were creating neutron networks?16:18
devanandaas tenant A: neutron net-create; neutron subnet-create; nova boot ... --nic net=aaaa;16:19
devanandaso neutron assigned an IP from that range to the instance, but there wasn't actually an OVS network on the host that matched / routed to it16:19
Sukhdevdevananda : as an admin, when you create a network, you can specify which tenant it is for, etc..16:19
devanandaSukhdev: does the admin need to create a network for each tenant (eg, when creating the tenant) ?16:19
vsaienkodevananda: but there wasn't actually an OVS network on the host that matched / routed to it what do you mean/16:20
*** AlanClark has joined #openstack-meeting-416:20
devanandavsaienko: yes16:20
Sukhdevdevananda : I believe so..16:21
devanandafirst off, I created two tenants, did not define any networks for them, and just booted two servers. Neutron assigned a private IP to each one -- on the same subnet16:22
devanandaand I was able to route traffic between them16:22
devanandaso while provisioning network was not visible to tenants, they were visible to each other16:22
devanandathen, as each tenant (not the admin), I issued "neutron net-create ...; neutron subnet-create ...;" commands with non-overlapping IP ranges16:23
devanandaand booted a server on that network16:23
devanandaneutron assigned an IP from the new subnet range, but it was inaccessible.16:24
vsaienkodevananda: did you checked that VLAN ID has been changed in OVS with ovs-vsctl show?16:24
devanandavsaienko: I did not see any new networks on the host16:24
Sukhdevdevananda : your sequence of steps seems right16:25
*** ajafo has quit IRC16:26
vsaienkodevananda: that is trange, since once you create new neutron network, neutron should create new IP namespace for it16:26
Sukhdevonly difference is that I would create a networks from admin context and specify the tenant for these networks and then create subnets from the tenant's context16:26
vsaienko*strange16:26
Sukhdevbut, your sequence should work as well16:27
devanandaSukhdev: if this were hardware switches instead of OVS, in a real deployment, would the non-admin tenant be able to create a neutron network?16:27
Sukhdevdevananda : yes16:27
vsaienkodevananda: it should16:27
devanandahmm ...16:28
vsaienkoneutron should call create_network() from ML2 driver and it will do all the rest16:28
vsaienkoI mean ML2 should create missing VLANs on the switches16:28
Sukhdevdevananda : I think you are doing everything correct16:28
devanandaI see16:29
*** vikasc has quit IRC16:29
devanandathat's good - but then I don't know why it didn't work locally16:29
Sukhdevdevananda : we need to triage a bit to dig deep - as vsaienko pointed, we need to check if correct vlan ID are being used16:29
devanandaI don't know if I'll have time to rebuild that env today, but I'll try to help as much as I can16:30
*** vikasc has joined #openstack-meeting-416:30
Sukhdevdevananda : are you using HW switches or OVS ?16:30
devanandaOVS16:30
devanandaI don't have that kind of fancy hardware at home ;)16:30
Sukhdevdevananda : in that case, I think OVS plumbing may be missing something -16:31
Sukhdevovs-vsctl show output will be helpful16:31
vsaienkodevananda: if you still have environment, I'm ready to debug issues with you16:31
*** ajafo has joined #openstack-meeting-416:32
devanandavsaienko: I do not16:32
SukhdevI will set up the test setup this week and play with it as well - and will ping you guys with the feedback16:33
Sukhdevvsaienko : did you test the same way as devananda is trying to do?16:33
vsaienkoyes16:33
Sukhdevhmmm...16:33
SukhdevOK - lets try to reproduce it then....I will get on it this week as well16:34
devanandaSukhdev: what I want to get as output of this test is confirmation of isolation between tenants16:34
vsaienkoI will triple check all16:34
Sukhdevdevananda : understood - and, actually, that leads me to the next topic on agenda16:35
SukhdevIs Yuri here?16:35
vsaienkosukhdev: he is on PTO this week16:36
Sukhdevhe was writing a tempest scenario test to test exactly the same thing16:36
devananda\o/16:36
vsaienkohttps://review.openstack.org/#/c/258934/16:36
Sukhdevdevananda : see here - https://bugs.launchpad.net/tempest/+bug/152023016:36
openstackLaunchpad bug 1520230 in tempest "Test Case: Create a test scenario to verify that Ironic supports multitenancy" [Undecided,In progress] - Assigned to Yuriy Yekovenko (yyekovenko)16:36
Sukhdevvsaienko : do you know if he was able to test this patch?16:37
devanandajroll: aren't we moving tempest scenario tests into ironic's tree soon?16:38
Sukhdev#link: https://review.openstack.org/#/c/258934/16:38
vsaienkoas far I know he is still working on that patch16:38
jrolldevananda: that's a goal, yes16:38
devanandayea, found it16:39
devanandavsaienko: he may want to rebase on top of https://review.openstack.org/#/c/253982/ or something16:39
*** vikasc has quit IRC16:40
vsaienkodevananda, I will ping him about it16:40
*** lkoranda has joined #openstack-meeting-416:40
jrolldevananda: I'm curious what other work is needed there, but probably a good idea16:41
SukhdevLooks like this test will be very helpful in testing this scenario16:41
devanandajroll: I think we were bike shedding on the folder name16:41
jrolldevananda: oh good16:41
jrolldevananda: I meant in project-config and such though :)16:41
*** FallenPegasus has joined #openstack-meeting-416:41
devanandayep. https://review.openstack.org/#/c/246161/716:41
devanandajroll: oh. that I'm not sure about16:42
jrolldevananda: yeah, it's fine though16:42
devanandai'm not saying we shouldn't land the multitenancy testing in tempest - just making sure folks are aware of the move to tempest-lib16:43
*** oferby has joined #openstack-meeting-416:43
*** devvesa has left #openstack-meeting-416:45
*** bobh has joined #openstack-meeting-416:45
SukhdevI am hoping Yuriy is aware of this tempest-lib stuff16:45
Sukhdevit has been a long time since I touched tempest stuff - I am not up-to-date in that regard :-):-016:46
*** FallenPegasus has quit IRC16:46
SukhdevFor now, as long as we can test multi-tenancy manually, we should be good16:46
SukhdevAnything else to discuss on this topic?16:47
Sukhdev#topic: Integration Status16:47
*** openstack changes topic to ": Integration Status (Meeting topic: ironic_neutron)"16:47
SukhdevWe have mostly covered the integration status already, but, I wanted to specifically talk about item 7 on https://etherpad.openstack.org/p/ironic-neutron-mid-cycle16:48
SukhdevThis is based upon two week old information - perhaps this has been addressed while I was gone16:49
*** sridhar_ram has joined #openstack-meeting-416:49
Sukhdevany update on this?16:49
jrollthat patch still needs a major update16:49
jrollit's on my todo list, apologies for not getting to it16:49
Sukhdevjroll: this will impact the portgroups, which no body is testing as of now16:50
lazy_princei am sorry.. which item 7.. under issues o rpatches..?16:50
Sukhdevlazy_prince : yes16:50
*** barra204 has joined #openstack-meeting-416:51
jrollSukhdev: yes I know16:51
Sukhdevlazy_prince : issues16:51
lazy_princeaha.. okay..16:51
*** prashantD has joined #openstack-meeting-416:51
*** asif has left #openstack-meeting-416:51
*** shakamunyi has quit IRC16:51
vsaienkofolks, at the moment we don't test portgroups at all, OVS allows to create portchannels with LACP I think we should try to cover portgroups with OVS also16:51
SukhdevOK - I was just making sure that I am up-to-date on this status16:51
*** lkoranda_ has joined #openstack-meeting-416:52
lazy_princevsaienko: ironic code is not upto date with portgroups yet.. we will have to wait for that...16:52
*** woodard has quit IRC16:52
*** lkoranda has quit IRC16:53
SukhdevThe question for the team is - should we consider merging the patches for M2 (mid Jan)?16:53
Sukhdevand do the portgroups after that for M3?16:54
lazy_princewhere are we with nova patches...?16:54
jrollwe should merge all the things as soon as they're ready :P16:54
jrolllazy_prince: 2 patches, one has a +2, the other is the portgroups thing that needs a major update16:54
lazy_princebefore we merge, we need to be ready from nova side too..16:54
*** lkoranda_ is now known as lkoranda16:54
lazy_princecool..16:55
Sukhdevupdate on etherpad is two weeks old - but, one of the patches was merged back then16:55
vsaienkoI'm asking to review devstack related patches so we have consensus on global variables names and can proceed with https://review.openstack.org/#/c/252814/16:55
*** piet has quit IRC16:56
jrollvsaienko: will do16:56
vsaienkojroll: thanks~16:56
*** Asif has joined #openstack-meeting-416:56
* Sukhdev time check - 4 min left16:56
Sukhdevlazy_prince : have you had a chance to test the devstack patches?16:57
devanandaSukhdev: I only saw one devstack patch when I was testing last week?16:57
lazy_princehmm... was busy all this time but free from now on.. I will test and update...16:58
Sukhdevdevananda : I try to keep the list of all patches on - https://etherpad.openstack.org/p/ironic-neutron-mid-cycle16:58
Sukhdevhence, I was asking earlier in the meeting to make sure the team updates this etherpad -16:58
Sukhdevthis keeps things simple to track16:59
devanandaah, thx16:59
*** woodard has joined #openstack-meeting-416:59
jrolldevananda: there's a bunch in the chain16:59
SukhdevLets all try to review devstack patches this week17:00
SukhdevWe are out of time - folks17:00
Sukhdevthanks for attending - this was great discusion17:00
krotschecko/17:00
Sukhdevbye17:00
Sukhdev#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Mon Jan  4 17:00:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-01-04-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-01-04-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-01-04-16.01.log.html17:00
*** nihilifer has quit IRC17:00
SukhdevNow is the time for L2 GW meeting17:01
Sukhdevanybody here for L2GW meeting?17:01
*** mitchjameson has quit IRC17:01
oferbyI'm here17:01
Sukhdev#startmeeting networking_l2gw17:02
openstackMeeting started Mon Jan  4 17:02:10 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: networking_l2gw)"17:02
openstackThe meeting name has been set to 'networking_l2gw'17:02
Sukhdev#topic: Agenda17:02
*** openstack changes topic to ": Agenda (Meeting topic: networking_l2gw)"17:02
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/L2Gateway#Meeting_January_4.2C_201617:02
SukhdevHi oferby17:02
oferbyhi17:03
*** vtech has quit IRC17:03
*** ChuckC has joined #openstack-meeting-417:03
SukhdevI guess it is you and me today17:03
oferbyas it was last time ....17:03
Sukhdev#topic: Announcements17:03
*** openstack changes topic to ": Announcements (Meeting topic: networking_l2gw)"17:03
SukhdevHappy new yeat17:03
Sukhdevyear17:04
ChuckCo/17:04
oferbyHNY to you too17:04
*** nihilifer has joined #openstack-meeting-417:04
Sukhdev#topic: Patches under review17:05
*** openstack changes topic to ": Patches under review (Meeting topic: networking_l2gw)"17:05
Sukhdev#link: https://review.openstack.org/#/q/status:open+project:openstack/networking-l2gw,n,z17:05
SukhdevI was gone for two and half weeks17:05
SukhdevI approved some of the patches last night and noticed that jenkins was not happy17:05
*** piet has joined #openstack-meeting-417:06
oferbyabout what? did not see..17:06
*** matrohon has quit IRC17:06
*** haleyb has quit IRC17:06
Sukhdevoferby : check out that link that I posted17:06
*** sambetts has joined #openstack-meeting-417:07
*** armax has joined #openstack-meeting-417:07
Sukhdevoferby : I gave +2 to several patches and none of them merged17:07
oferbyi see now thew mcast remote17:07
Sukhdevoferby : ?17:09
*** sambetts has left #openstack-meeting-417:10
oferbydidn't get you question .... I see the patch that have a problem in jenkins .17:11
*** cbouch has joined #openstack-meeting-417:11
oferbyis anyone working on it? I was working off-line on the inter-cloud connection.17:12
Sukhdevsorry - was looking through the logs to see if I can spot something17:12
Sukhdevoferby : I was gone on PTO for 2.5 weeks and it seems no body has been looking at these17:13
SukhdevLooks like this will prevent for merging anything17:14
SukhdevI will try to look into this later this week17:14
Sukhdevoferby : if you happen to have few cycles, please have a look as well17:15
oferbyI have some tasks that I have to finish and I can than help.17:15
SukhdevI will ping the india team as well17:15
oferbyok17:15
Sukhdevoferby : sounds good17:15
Sukhdevoferby : how is your inter-cloud project coming along?17:15
*** Asif has quit IRC17:16
oferbyas you guys were off-line, I started to work in my own branch17:16
oferbyall working well. I plan to merge as soon as I will finish it17:16
oferbymeanwhile, I worked with the OVS team17:17
*** f13o has quit IRC17:17
oferbyto add the passive mode. I send out the patch and it is being reviewed17:17
oferbythe schema extension too.17:17
*** nihilifer has quit IRC17:17
*** nihilifer has joined #openstack-meeting-417:18
*** Swami has joined #openstack-meeting-417:18
SukhdevI saw that patch two weeks ago - any progress on it?17:18
Sukhdevdoes it look like it will merge soon?17:18
oferbysure, but I have to finish it in 2 weeks. internal milestone.... I will merge it as soon as I pass the milestone. ok?17:19
Sukhdevmakes sense17:20
oferbyI also met with people from Midokura17:20
SukhdevIn the mean time, I will work on identifying the issue with the gate17:20
oferbythey are also interested in this17:20
Sukhdevhow did that meeting go?17:20
oferbyvery well. had 2 meeting with them.17:20
Sukhdevgood17:21
oferbythey are interested with the new API (inter-cloud extension) as they have their own implementation.17:21
Sukhdevwhen will you post your patch for review?17:21
oferbyirena from Midokura added a bug on this and I will write with her blue print, ok?17:22
Sukhdevdo you have a link to the bug?17:22
oferbysec17:22
*** sdake_ has joined #openstack-meeting-417:23
*** wojdev has quit IRC17:23
SukhdevChuckC : hi17:24
oferbyhttps://bugs.launchpad.net/networking-l2gw/+bug/152986317:25
openstackLaunchpad bug 1529863 in networking-l2gw "[RFE] extend l2gw api to support multi-site connectivity" [Undecided,New]17:25
ChuckCSukhdev:happy new year17:25
*** sdake has quit IRC17:25
Sukhdev#link: https://bugs.launchpad.net/networking-l2gw/+bug/152986317:25
SukhdevChuckC : Thanks - same to you17:25
*** haleyb has joined #openstack-meeting-417:25
Sukhdevsaw you were lurking here - wondered if you were interested in L2 GW as well17:25
ChuckCWe are planning to use it, so I'm trying to see where things are.17:26
*** bharathm has joined #openstack-meeting-417:26
Sukhdevoferby : thanks for the link17:26
SukhdevChuckC : what is your use case?17:26
*** f13o has joined #openstack-meeting-417:27
*** piet has quit IRC17:27
*** piet has joined #openstack-meeting-417:27
Sukhdevoferby : If I remember correctly from our discussion during Tokyo summit, Midokura wants to use it for L3, right?17:28
oferbyyes17:28
Sukhdevso, they will build it upon your work -17:28
ChuckCI think the basic use case already in place is a good start.  We're integrating with Helion.17:28
oferbythey have their own implementaion17:29
oferbythey use the API17:29
SukhdevChuckC : It already is integrated with Helion, right? the HP team made it work17:30
Sukhdevoferby : correct -17:30
SukhdevChuckC : are you part of HP team>17:30
ChuckCSukhdev: yes, one of them.  The other team is HP networking.  Probably others....17:31
Sukhdevoferby : are you planning on pushing your patch(es)?17:31
oferbyI will finish all in 2 weeks. would you like me to push it when it is in progress or at the end?17:32
*** vtech has joined #openstack-meeting-417:32
ChuckCHP has enough openstack offerings that I'm a bit confused what's been done where ;)17:32
Sukhdevoferby : Yes, please17:32
*** cbouch has quit IRC17:32
oferby:-) yes push or yes wait ....17:33
Sukhdevoferby : sorry - I meant yes, push it when you are ready17:33
SukhdevChuckC : that is the blessing and curse for working for large company :-):-)17:33
ChuckCindeed17:34
SukhdevI used to work for Cisco many years ago - and I felt like that some times :-)17:34
SukhdevChuckC : most of the HP india team was working on L2 GW project - with armax leading from Palo Alto team17:35
ChuckCYes, I believe that was HP networking.  I'm kind of surprised that only you and oferby seem to be attending these meetings.17:36
Sukhdevoferby : so, I will look into the gate issues - hopefully, it will be cleaned up before you are ready to push your patches17:36
oferbygreate.17:36
Sukhdevoferby : feel free to jump in, if you have any cycles -17:37
oferbyI will.17:37
SukhdevAnything else we need to cover here?17:37
oferbynot from here.17:37
ChuckCwhere do you track your work for mitaka?17:37
ChuckCyou don't do launchpad, right?17:38
SukhdevChuckC:  we have launchpad17:38
ChuckCblueprints?  or just bug list?17:38
Sukhdevhowever, there is no specific charter for mitaka - other than what oferby is working on17:38
SukhdevChuckC : we track everything via bugs17:39
ChuckCok, that's what it looked like17:39
ChuckCthanks17:39
SukhdevChuckC: it keeps things simple :-)17:39
SukhdevChuckC : anything you would like to discuss?17:39
ChuckCsure17:39
ChuckCnot in particular.  I need to get devstack working, but haven't been able to give it too much time yet17:40
SukhdevChuckC : give it a shot....actually, I intend to run it as well later this week or early next week17:41
*** cbouch has joined #openstack-meeting-417:41
SukhdevChuckC : feel free to ping me if you see any issue17:41
ChuckCSukhdev: thanks, will do17:41
SukhdevI guess we are done for today.17:41
Sukhdevwill see you guys in two weeks17:41
SukhdevThanks for attending17:42
ChuckCadios17:42
Sukhdevbye17:42
oferbyyep. bye.17:42
Sukhdev#endmeeting17:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:42
openstackMeeting ended Mon Jan  4 17:42:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_l2gw/2016/networking_l2gw.2016-01-04-17.02.html17:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_l2gw/2016/networking_l2gw.2016-01-04-17.02.txt17:42
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_l2gw/2016/networking_l2gw.2016-01-04-17.02.log.html17:42
*** oferby has quit IRC17:43
*** kevinbenton has joined #openstack-meeting-417:49
*** ajmiller has quit IRC17:55
*** sdake_ is now known as sdake17:56
*** ajmiller has joined #openstack-meeting-418:00
*** kevinbenton has quit IRC18:03
*** SimonChung has joined #openstack-meeting-418:03
*** FallenPegasus has joined #openstack-meeting-418:05
*** salv-orl_ has joined #openstack-meeting-418:06
*** salv-orl_ has quit IRC18:06
*** salv-orl_ has joined #openstack-meeting-418:07
*** vhoward has quit IRC18:08
*** salv-orlando has quit IRC18:08
*** kevinbenton has joined #openstack-meeting-418:09
*** iyamahat has joined #openstack-meeting-418:09
*** angdraug has joined #openstack-meeting-418:10
*** armax has quit IRC18:11
*** iyamahat has quit IRC18:15
*** FallenPegasus has quit IRC18:19
*** FallenPegasus has joined #openstack-meeting-418:20
*** bharathm has quit IRC18:26
*** baoli_ has quit IRC18:27
*** Sukhdev has quit IRC18:28
*** lazy_prince has quit IRC18:30
*** julim_ has joined #openstack-meeting-418:30
*** baoli has joined #openstack-meeting-418:31
*** jwagner is now known as jwagner[away]18:31
*** julim has quit IRC18:32
*** sridhar_ram has quit IRC18:34
*** iyamahat has joined #openstack-meeting-418:34
*** paul-carlton2 has quit IRC18:36
*** vtech has quit IRC18:39
*** s3wong has joined #openstack-meeting-418:40
*** vtech has joined #openstack-meeting-418:41
*** yamahata has joined #openstack-meeting-418:42
*** bpokorny has joined #openstack-meeting-418:43
*** piet has quit IRC18:43
*** piet has joined #openstack-meeting-418:47
*** isq has quit IRC18:50
*** isq has joined #openstack-meeting-418:51
*** bharathm has joined #openstack-meeting-418:51
*** angdraug has quit IRC18:55
*** bnemec has quit IRC18:58
*** AlanClark has quit IRC19:03
*** piet has quit IRC19:03
*** baoli has quit IRC19:06
*** dslevin has quit IRC19:06
*** baoli has joined #openstack-meeting-419:06
*** baoli has quit IRC19:07
*** sdake has quit IRC19:08
*** sc68cal has quit IRC19:11
*** bharathm has quit IRC19:11
*** FallenPegasus is now known as MarkAtwood19:11
*** baoli has joined #openstack-meeting-419:11
*** dslevin has joined #openstack-meeting-419:12
*** bharathm has joined #openstack-meeting-419:12
*** sc68cal has joined #openstack-meeting-419:14
*** uck has joined #openstack-meeting-419:18
*** bnemec has joined #openstack-meeting-419:20
*** openstackstatus has quit IRC19:20
*** sdake has joined #openstack-meeting-419:21
*** sridhar_ram has joined #openstack-meeting-419:22
*** openstackstatus has joined #openstack-meeting-419:22
*** ChanServ sets mode: +v openstackstatus19:22
*** jwagner[away] is now known as jwagner19:22
*** bharathm has quit IRC19:28
*** bharathm has joined #openstack-meeting-419:32
*** yhvh has quit IRC19:35
*** Kiall has quit IRC19:36
*** Kiall has joined #openstack-meeting-419:36
*** jmckind_ has joined #openstack-meeting-419:40
*** fawadkhaliq has quit IRC19:41
*** fawadkhaliq has joined #openstack-meeting-419:42
*** jmckind has quit IRC19:43
*** dims_ has joined #openstack-meeting-419:46
*** bharathm has quit IRC19:46
*** dims has quit IRC19:47
*** vtech has quit IRC19:49
*** bharathm has joined #openstack-meeting-419:50
*** Prithiv has quit IRC19:54
*** baoli has quit IRC19:56
*** bharathm has quit IRC20:00
*** kebray has joined #openstack-meeting-420:03
*** daneyon has joined #openstack-meeting-420:04
*** cdelatte has joined #openstack-meeting-420:05
*** bharathm has joined #openstack-meeting-420:05
*** bharathm has quit IRC20:21
*** wojdev has joined #openstack-meeting-420:22
*** Sukhdev has joined #openstack-meeting-420:23
*** bharathm has joined #openstack-meeting-420:24
*** uck has quit IRC20:25
*** krtaylor has quit IRC20:26
*** bharathm has quit IRC20:31
*** bharathm has joined #openstack-meeting-420:34
*** mrunge has joined #openstack-meeting-420:36
*** piet has joined #openstack-meeting-420:40
*** bharathm has quit IRC20:40
*** ihrachys has joined #openstack-meeting-420:42
*** bharathm has joined #openstack-meeting-420:42
*** Sukhdev has quit IRC20:43
*** baoli has joined #openstack-meeting-420:51
*** ihrachys_ has joined #openstack-meeting-420:51
*** ihrachys has quit IRC20:52
*** sarob_ has joined #openstack-meeting-420:55
*** ihrachys_ is now known as ihrachys20:56
*** mriedem has joined #openstack-meeting-420:59
ihrachyso/ to all stable folks around21:00
mriedem#startmeeting stable21:00
openstackMeeting started Mon Jan  4 21:00:29 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
mrungeo/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
mriedemhi, who's around?21:00
ihrachyso/21:00
mrungeo/21:01
*** qwebirc20845 has joined #openstack-meeting-421:01
mriedemok, will give it another minute or so, maybe i can lure mtreinish in21:01
mriedemtonyb: are you around?21:01
tonybmriedem: yup21:01
tonybsorry should have waved21:02
mtreinishmriedem: oh is something going on?21:02
mriedembig big things are going on21:02
mtreinishheh21:02
mriedemlet's just roll through this, there isn't much planned today since it's the first day back for a lot of people21:02
mtreinishI guess I did say this time worked for me21:02
mriedemthe agenda is here https://wiki.openstack.org/wiki/Meetings/StableTeam#Agenda21:02
mriedem#link https://wiki.openstack.org/wiki/Meetings/StableTeam#Agenda21:02
mriedempretty sparse, i think ttx said he had some items for next week21:03
mriedem#topic status21:03
*** openstack changes topic to "status (Meeting topic: stable)"21:03
mriedemso i put a logstash query in the agenda http://goo.gl/5qiw2U21:03
mriedemthat shows periodic-stable failures in the last 7 days21:03
ihrachyswell I guess that's mostly lbaas for a known reason21:04
mriedemi've been out but just quickly looking over these this afternoon they are mostly neutron-lbaas and ceilomteer, which are known issues in https://etherpad.openstack.org/p/stable-tracker21:04
mriedemyeah21:04
mtreinishmriedem: there is also: http://status.openstack.org/openstack-health/#/g/build_queue/periodic-stable21:04
mriedemkilo was also busted, but mkoderer fixed that21:04
mriedemmtreinish: ooo pretty21:04
mriedem#link http://goo.gl/5qiw2U21:04
tonybmriedem: is that the testrepositoiry issue?21:04
mriedem#link http://status.openstack.org/openstack-health/#/g/build_queue/periodic-stable21:04
mtreinishbut that doesnt show the devstack failures21:04
mriedemtonyb: yeah, pbr and tox21:04
mtreinishtonyb: yeah, its actually a pbr thing21:04
tonybmriedem: cool.21:05
mriedemhttps://review.openstack.org/#/c/262470/ fixed kilo21:05
tonybmriedem: cool.21:05
*** ihrachys_ has joined #openstack-meeting-421:05
mriedemihrachys: on the neutron-lbaas thing, did you have any updates on that? it was bit rotting in project-config from what i remember21:05
mriedemhttps://review.openstack.org/#/c/245525/21:06
ihrachys_mriedem: yeah. I tried several isolated patchsets, but seems like infra wants a full blown rework21:06
ihrachys_mriedem: introducing new macros just for periodic jobs21:06
*** matrohon has joined #openstack-meeting-421:06
mriedemthe alternative is hard-coding it in the in-tree setup file right?21:06
ihrachys_which was not in line with my scarce time :-|21:06
mriedemsure, but21:06
*** javeriak_ has quit IRC21:06
mriedemyou wouldn't have to work on it21:07
mriedemit's not great since it's a thing that has to be done every release21:07
ihrachys_mriedem: probably yeah, we could go with hardcoded way. Not that I like it much, and not that I get infra concerns enough.21:07
ihrachys_mriedem: I haven't seen many volunteers to do it instead of me from infra side :)21:07
mriedemi doubt anyone besides me knows about that infra patch21:08
ihrachys_mriedem: you mean from infra folks?21:08
mriedemwell, anyone21:08
mriedemare there neutron-lbaas mini PTLs that should be involved with this kind of thing?21:08
*** ihrachys has quit IRC21:08
ihrachys_mriedem: people were reviewing it, telling me I do it wrong, and that we need macros. not that we did not have discussion around it.21:08
* mriedem is unclear on the complicated beurocracy that is the neutron stadium21:09
tonybihrachys_: I'll have a look at it.21:09
tonyb(where "it" == the new macros21:09
mriedem#action tonyb to take a crack at the infra side of https://bugs.launchpad.net/neutron/+bug/152324121:09
openstackLaunchpad bug 1523241 in neutron "neutron-lbaas failing in stable/liberty due to "ImportError: No module named embrane.common"" [Medium,In progress] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)21:09
ihrachys_mriedem: there are lbaas cores, not sure they would be of help here though. this tox_install.sh thing is hardly understood by enough folks in neutron team.21:09
ihrachys_tonyb: thanks21:09
mriedemok, cool, thanks. if that doesn't get anywhere i'd say we hack the branch in the scripts for now if no one has time to work on this21:09
mriedemihrachys_: yeah21:10
ihrachys_sounds like a plan21:10
mtreinishihrachys_: ugh, that script...21:10
ihrachys_mtreinish: it's now all over neutron subprojects :D21:10
mriedemfunny how that works21:11
mriedemanything else on this or should we move on?21:11
mtreinishsigh, this is why I keep saying this is why you need a stable interface and work from releases21:11
mtreinishbut whatever21:11
*** sarob_ has quit IRC21:11
ihrachys_side note: problem with periodic jobs is they don't indicate that a patch will actually merge in gate.21:11
ihrachys_mtreinish: we work on neutron-lib, it's ongoing.21:11
mriedemihrachys_: can you expand a bit on the periodic job thing?21:12
*** matrohon has quit IRC21:12
mriedemthey don't actually run on a patch21:12
ihrachys_mriedem: well, the problem is that it covers unit tests, docs, prolly that's all? none of those devstack jobs that we run in real gate.21:12
mriedemyeah21:12
*** baoli has quit IRC21:13
mtreinishihrachys_: that's not true, there are periodic stable jobs for tempest jobs21:13
mriedemmtreinish: did anyone ever propose running a dsvm tempest job in the periodic-stable queue?21:13
ihrachys_and those jobs start to fail no less often than unit tests. so it's kinda not complete solution.21:13
mriedemoh right,21:13
mriedemstable tempest kilo was failing on that devstack thing21:13
*** baoli has joined #openstack-meeting-421:13
mtreinishright21:13
ihrachys_mtreinish: really? ok. probably not of those from gate anyhow21:13
mtreinishihrachys_: jsut look at the link to the health dashboard21:13
mtreinishthose are the periodic stable tempest jobs we run21:14
mriedemihrachys_: e.g. http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-full-kilo/8de4dcd/console.html21:14
*** baoli has quit IRC21:14
mtreinishit's not exhaustive, but its the common ones21:14
ihrachys_ack21:14
mriedemwhich hits that devstack pbr failure http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-full-kilo/8de4dcd/logs/devstacklog.txt.gz#_2016-01-04_06_11_29_93821:14
*** ihrachys_ is now known as ihrachys21:14
mtreinishfull, postgres full, and neutron full for each branch iirc21:14
mriedemso yeah, i guess i forget about that one21:14
*** baoli has joined #openstack-meeting-421:14
mriedemi'm surprsised we even run that many21:14
*** matrohon has joined #openstack-meeting-421:15
mriedemlet's move on21:15
mriedemthe other stable/liberty failure i was seeing was ceilometer, which was tracked at one point with https://bugs.launchpad.net/ceilometer/+bug/152653021:15
openstackLaunchpad bug 1526530 in Ceilometer "stable/liberty integration tests failing" [Critical,In progress] - Assigned to gordon chung (chungg)21:15
mriedemgordc had some things proposed but abandoned them, i need to follow up21:15
mtreinishmriedem: we added them back in the day because I complained I was the only one looking at the failures, this was supposed to raise awareness of stable branch issues in the gate....21:15
mriedem#action mriedem to follow up with gordc on https://bugs.launchpad.net/ceilometer/+bug/152653021:16
*** bharathm has quit IRC21:16
mriedemwere there other stable branch issues we haven't covered?21:16
mtreinish(those were the only 3 configs back when we added them)21:16
ihrachyspbr thing? do we have a plan for that?21:16
mriedemihrachys: the kilo thing was fixed this morning21:16
ihrachysmriedem: hm? what was the fix?21:17
mriedemhttps://review.openstack.org/#/c/262470/21:17
mriedemso i think by and large stable right now is okish21:17
mriedemgordc has a patch up for the ceilometer issue https://review.openstack.org/#/c/258642/21:18
mrungeI'm a bit astonished, that issue hit so different projects but not all branches...21:18
ihrachysnice. thanks for the link.21:18
mriedemmrunge: i think stable/liberty was already fixed21:18
mriedemmrunge: the tox thing hit a bunch of projects21:18
mriedembut dims and others were fixing before the vacation21:18
mrungeheh, horizon was hit by the issue beginning with Dec 26th21:19
*** baoli has quit IRC21:19
tonybmrunge: yeah really bad timing ;P21:19
mriedemok, moving on from status21:20
mriedem#topic release-plans21:20
*** openstack changes topic to "release-plans (Meeting topic: stable)"21:20
*** jmckind_ has quit IRC21:20
mriedemthe only thing i have on the agenda is nova doing a stable/liberty 12.0.1 release21:20
mriedemwhich i brought up in the ML awhile back http://lists.openstack.org/pipermail/openstack-dev/2015-December/081872.html21:21
mriedemthese are the open reviews21:21
mriedem#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/liberty21:21
mriedemi haven't gone through all of those yet, but i want to get at least a couple in, like https://review.openstack.org/#/c/253224/21:21
mriedemit's basically a point release to get some key bug fixes out21:21
mriedemanyway, i plan on getting into more of those this week and then i'll be pinging nova stable cores to look21:22
mriedemis anyone else aware of any projects that are looking at doing a stable branch release?21:22
tonybmriedem: FWIW I'll look through again and see if there is anything *I* think shoudl be in 12.0.1 (apart from the reno review)21:23
mriedemtonyb: thanks21:23
mriedemi didn't want to start pinging people today on reviews21:23
mtreinishI dont know of any21:23
mriedemthere have been a couple of projects that have done a stable/liberty release already21:23
* ihrachys wonders why we don't automate minor releases, and make them frequent. we were thinking of getting there for neutron for L.21:23
mriedemihrachys: well, there was that long thread in the ML on that21:23
mriedemlike, every commit being a release21:24
*** kebray has quit IRC21:24
mriedemit's really up to the project teams now as to how frequent they want to release21:24
dims_mriedem : mordred had this review https://review.openstack.org/#/c/247677/ about documenting EOL and proposed release dates in openstack/releases repo. do we want to do that?21:24
mriedemdims_: huh, hadn't seen it, i'll have to look21:25
mriedem#action mriedem to look at https://review.openstack.org/#/c/247677/21:25
*** Swami_ has joined #openstack-meeting-421:25
tonybit's merged21:25
*** bharathm has joined #openstack-meeting-421:25
*** Swami has quit IRC21:25
mriedemyeah21:25
mriedemit's also confusing21:25
dims_tonyb : i know, continue to use that place to document future releases21:25
mriedemthe commit message talks about when they will EOL but doesn't specify that21:26
mtreinishmriedem: it does in the index21:26
tonybmriedem: yeah I just saw that21:26
mriedemmtreinish: oh yeah21:26
*** julim_ has quit IRC21:26
*** uck has joined #openstack-meeting-421:26
mtreinishwe probably need to mark juno as EOL though21:27
mtreinishinstead of security supported (EOL 2015-12-03)21:27
mriedemi guess that's implied21:27
tonybdims_: ok.21:27
mtreinishheh, I was just going off the other branches where it says EOL21:27
mriedemok, i guess if there are things to address there let's take it to -stable after the meeting21:28
mriedem#topic open discussion21:28
*** openstack changes topic to "open discussion (Meeting topic: stable)"21:28
mriedemthere are 2 items on the agenda21:28
mriedem1. i want to get a review dashboard link in the #openstack-stable channel topic21:29
tonybFWIW it's now markjed as EOL21:29
mtreinishtonyb: ah, ok21:29
tonybmtreinish: send me the link I'll work with @infra to get it in there.21:29
mriedemsdague had an email to the ML on dashboards for new gerrit, i was thinking it'd be good to have something like that in the -stable channel topic21:29
mriedemtonyb: was that meant for me?21:29
anteayanice idea21:29
tonybmriedem: yeah, bad tab-complete21:30
mtreinishtonyb: ??21:30
ihrachysmriedem: what will the board contain? all backports?21:30
mriedemihrachys: just open reviews in stable/branches, pretty simple to start21:30
mriedembut sdague's had things broken down by what was passing jenkins, what has a +2, etc21:30
*** uck has quit IRC21:30
mriedemmakes prioritizing easier21:31
tonybYeah we can modify the dashboard as we go21:31
ihrachysmriedem: I am agnostic, but if you want to use it as a data point, personally I care little for backports outside neutron subprojects (because the latter are already more than enough for my taste)21:31
mriedemso i was going to take a stab at that when i got a chance, but if others are interested feel free to propose some ideas and we can check them out21:31
mriedemihrachys: same for me and nova,21:32
mriedemihrachys: i just like to see what it looks like at first and we can iterate on it21:32
mriedemswift has a nice dashboard in their channel topic and i'd like nova to do similar21:32
ihrachysmriedem: for neutron stable stuff, I use this: https://github.com/openstack/gerrit-dash-creator/blob/master/dashboards/neutron-subprojects-stable.dash21:32
tonybI tend to focus on nova and whatever I see the get the requirements updates passing21:32
mriedem#link neutron stable review dashboard example https://github.com/openstack/gerrit-dash-creator/blob/master/dashboards/neutron-subprojects-stable.dash21:33
mriedemanyway, it's a thing, if people have input or want to propose something to infra, we can review there21:33
mriedemthe last item in open discussion,21:34
mriedem2. https://etherpad.openstack.org/p/stable-tracker has completed sections for icehouse and juno, which are now EOL21:34
mtreinishjust drop them21:34
mriedemit's getting messy in there, and since i spent part of my vacation cleaning up and organizing my office, i'm in the mode21:34
mriedemyeah, so was just wondering if anyone had reason not to drop those21:35
ihrachyskill the witch21:35
mriedemok, will do21:35
tonybmriedem: nuke 'em21:35
mriedemthat's it for agenda items, did anyone else have anything?21:35
mriedem#action mriedem to drop icehouse and juno sections from https://etherpad.openstack.org/p/stable-tracker21:35
mriedemok, not hearing anything else, so we can end early.21:36
mriedemlike i said, ttx said he had some items for next week21:36
ihrachysone thing we should discuss is pushing forward constraints to more projects. next time.21:36
mriedemso i await in eager anticipation21:36
mriedemihrachys: yeah, good point.21:36
*** woodard has quit IRC21:36
mriedemthose jobs are passing but non-voting in nova stable/liberty right now21:36
ihrachyswe did it for neutron, and will backport remaining stuff to L21:36
mriedemwe should circle back with lifeless on the plan there21:36
mriedem#action figure out what's going on with the -constraints jobs in stable/liberty and if/when they become voting21:37
mriedemi'll follow up with lifeless and bring back what we talked about to this meeting next week21:37
ihrachysI think L for neutron repo should be done, and we look into *aas and remaining gaps. hopefully more projects will get to it in L, so that we can reasonably consider extending life for the branch. but I suspect it will be Mitaka21:37
mriedemi'm hoping the guys working on that are tracking that work somewhere21:38
ihrachyslet's hear from them for now.21:38
mriedemok, anything else?21:39
mriedemtaking that as a no, so we can end early21:39
mriedemthanks everyone21:39
mriedem#endmeeting21:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:39
openstackMeeting ended Mon Jan  4 21:39:24 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-01-04-21.00.html21:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-01-04-21.00.txt21:39
openstackLog:            http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-01-04-21.00.log.html21:39
ihrachysthanks. not a bad one for the first time. gn to all.21:39
mriedemttyl21:39
*** mriedem has left #openstack-meeting-421:39
*** baoli has joined #openstack-meeting-421:40
mrungegood night21:42
mrungeand thank you21:42
*** ihrachys has quit IRC21:44
*** matrohon has quit IRC21:49
*** matrohon has joined #openstack-meeting-421:51
*** galstrom is now known as galstrom_zzz21:59
*** sdake has quit IRC22:00
*** sdake has joined #openstack-meeting-422:00
*** cbouch has quit IRC22:02
*** galstrom_zzz is now known as galstrom22:02
*** gomarivera has quit IRC22:05
*** bharathm has quit IRC22:05
*** bharathm has joined #openstack-meeting-422:10
*** salv-orl_ has quit IRC22:15
*** qwebirc20845 has quit IRC22:16
*** matrohon has quit IRC22:23
*** bobh has quit IRC22:28
*** angdraug has joined #openstack-meeting-422:30
*** galstrom is now known as galstrom_zzz22:39
*** darrenc is now known as darrenc_afk22:39
*** kebray has joined #openstack-meeting-422:45
*** Sukhdev has joined #openstack-meeting-422:49
*** bharathm has quit IRC22:52
*** padkrish has joined #openstack-meeting-422:54
*** darrenc_afk is now known as darrenc22:54
*** kebray has quit IRC22:55
*** hippiepete has quit IRC22:59
*** bharathm has joined #openstack-meeting-423:01
*** klamath_ has quit IRC23:03
*** blahRus1 has quit IRC23:04
*** yuli_s has quit IRC23:13
*** gsagie has quit IRC23:14
*** baoli has quit IRC23:14
*** lifeless has joined #openstack-meeting-423:15
*** padkrish has quit IRC23:15
*** lifeless has left #openstack-meeting-423:19
*** piet has quit IRC23:19
*** piet has joined #openstack-meeting-423:20
*** padkrish has joined #openstack-meeting-423:21
*** banix has quit IRC23:22
*** gsagie has joined #openstack-meeting-423:28
*** baoli has joined #openstack-meeting-423:28
*** uck has joined #openstack-meeting-423:28
*** angdraug has quit IRC23:29
*** baoli has quit IRC23:30
*** spotz is now known as spotz_zzz23:31
*** baoli has joined #openstack-meeting-423:31
*** haleyb has quit IRC23:32
*** uck has quit IRC23:34
*** avarner has joined #openstack-meeting-423:36
*** ChuckC has quit IRC23:36
*** baoli has quit IRC23:37
*** bharathm has quit IRC23:40
*** sigmavirus24 is now known as sigmavirus24_awa23:46
*** uck has joined #openstack-meeting-423:47
*** bharathm has joined #openstack-meeting-423:49
*** stanchan has joined #openstack-meeting-423:54

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