Monday, 2016-02-29

*** sdake has joined #openstack-meeting-400:00
*** unicell has joined #openstack-meeting-400:05
*** thorst has joined #openstack-meeting-400:08
*** unicell has quit IRC00:10
*** unicell has joined #openstack-meeting-400:19
*** xingchao has joined #openstack-meeting-400:24
*** thorst has quit IRC00:27
*** xingchao has quit IRC00:29
*** beekneemech has quit IRC00:29
*** bnemec has joined #openstack-meeting-400:31
*** zeih has joined #openstack-meeting-400:38
*** markvoelker has joined #openstack-meeting-400:43
*** zeih has quit IRC00:43
*** sdake has quit IRC00:45
*** markvoelker has quit IRC00:47
*** sdake has joined #openstack-meeting-400:50
*** tfukushima has joined #openstack-meeting-400:56
*** unicell has quit IRC00:59
*** zeih has joined #openstack-meeting-401:00
*** prashantD has quit IRC01:00
*** Jeffrey4l has joined #openstack-meeting-401:01
*** zeih has quit IRC01:05
*** sdake has quit IRC01:06
*** sdake has joined #openstack-meeting-401:08
*** bobh has joined #openstack-meeting-401:12
*** salv-orlando has joined #openstack-meeting-401:12
*** bobh has quit IRC01:17
*** salv-orlando has quit IRC01:20
*** xingchao has joined #openstack-meeting-401:25
*** xingchao has quit IRC01:30
*** baohua has joined #openstack-meeting-401:34
*** tfukushima has quit IRC01:41
*** baohua has quit IRC01:42
*** baohua has joined #openstack-meeting-401:42
*** sdake has quit IRC01:43
*** iceyao has joined #openstack-meeting-401:43
*** markvoelker has joined #openstack-meeting-401:44
*** bobh has joined #openstack-meeting-401:44
*** tfukushima has joined #openstack-meeting-401:48
*** markvoelker has quit IRC01:48
*** yamamoto_ has joined #openstack-meeting-401:50
*** baohua has quit IRC01:55
*** yamamoto_ has quit IRC01:55
*** baohua has joined #openstack-meeting-401:56
*** Sukhdev has joined #openstack-meeting-401:56
*** iceyao has quit IRC01:58
*** zeih has joined #openstack-meeting-402:01
*** baohua_ has joined #openstack-meeting-402:03
*** Kevin_Zheng has joined #openstack-meeting-402:04
*** zeih has quit IRC02:06
*** baohua has quit IRC02:06
*** yamamoto_ has joined #openstack-meeting-402:08
*** yamamoto_ has quit IRC02:09
*** iceyao has joined #openstack-meeting-402:12
*** Sukhdev has quit IRC02:13
*** Sukhdev has joined #openstack-meeting-402:13
*** xingchao has joined #openstack-meeting-402:14
*** iceyao has quit IRC02:19
*** iceyao has joined #openstack-meeting-402:24
*** ajmiller has quit IRC02:25
*** thorst has joined #openstack-meeting-402:28
*** zehicle has quit IRC02:31
*** Sukhdev has quit IRC02:31
*** sdake has joined #openstack-meeting-402:31
*** yamamoto has joined #openstack-meeting-402:33
*** xingchao has quit IRC02:34
*** zehicle has joined #openstack-meeting-402:36
*** thorst has quit IRC02:36
*** salv-orlando has joined #openstack-meeting-402:37
*** xingchao has joined #openstack-meeting-402:39
*** yamamoto has quit IRC02:40
*** markvoelker has joined #openstack-meeting-402:44
*** pbourke_ has joined #openstack-meeting-402:46
*** pbourke has quit IRC02:47
*** jokke_ has quit IRC02:47
*** jokke_ has joined #openstack-meeting-402:47
*** ianychoi has quit IRC02:49
*** markvoelker has quit IRC02:49
*** ianychoi has joined #openstack-meeting-402:49
*** Sukhdev has joined #openstack-meeting-402:52
*** salv-orlando has quit IRC02:53
*** bobh has quit IRC03:05
*** julim has quit IRC03:07
*** bobh has joined #openstack-meeting-403:07
*** sdake has quit IRC03:19
*** baoli has joined #openstack-meeting-403:21
*** neelashah has joined #openstack-meeting-403:22
*** yamamoto_ has joined #openstack-meeting-403:23
*** baohua_ has quit IRC03:23
*** tfukushima has quit IRC03:23
*** baohua has joined #openstack-meeting-403:24
*** prashantD has joined #openstack-meeting-403:26
*** prashantD has quit IRC03:31
*** prashantD has joined #openstack-meeting-403:33
*** tfukushima has joined #openstack-meeting-403:35
*** thorst has joined #openstack-meeting-403:36
*** thorst has quit IRC03:41
*** dave-mccowan has quit IRC03:42
*** xingchao has quit IRC03:44
*** sdake has joined #openstack-meeting-403:47
*** xingchao has joined #openstack-meeting-403:47
*** baoli has quit IRC03:49
*** bobh has quit IRC03:50
*** neelashah has quit IRC03:51
*** salv-orlando has joined #openstack-meeting-403:57
*** zeih has joined #openstack-meeting-404:03
*** itisha has joined #openstack-meeting-404:03
*** salv-orlando has quit IRC04:03
*** Sukhdev has quit IRC04:04
*** zeih has quit IRC04:07
*** david-lyle has joined #openstack-meeting-404:13
*** xingchao has quit IRC04:24
*** xingchao has joined #openstack-meeting-404:27
*** salv-orlando has joined #openstack-meeting-404:32
*** david-lyle has quit IRC04:36
*** salv-orlando has quit IRC04:38
*** iceyao has quit IRC04:45
*** markvoelker has joined #openstack-meeting-404:45
*** tfukushima has quit IRC04:48
*** markvoelker has quit IRC04:50
*** xingchao has quit IRC04:50
*** david-lyle has joined #openstack-meeting-404:50
*** bobh has joined #openstack-meeting-404:51
*** thorst has joined #openstack-meeting-404:54
*** bobh has quit IRC04:56
*** david-lyle has quit IRC04:56
*** numans has joined #openstack-meeting-404:59
*** thorst has quit IRC05:03
*** prashantD has quit IRC05:06
*** javeriak has joined #openstack-meeting-405:06
*** javeriak_ has joined #openstack-meeting-405:12
*** javeriak has quit IRC05:12
*** tfukushima has joined #openstack-meeting-405:22
*** salv-orlando has joined #openstack-meeting-405:36
*** xingchao has joined #openstack-meeting-405:40
*** sridhar_ram has joined #openstack-meeting-405:42
*** sridhar_ram has quit IRC05:42
*** watanabe_isao has joined #openstack-meeting-405:42
*** salv-orlando has quit IRC05:47
*** bobh has joined #openstack-meeting-405:52
*** fawadkhaliq has joined #openstack-meeting-405:54
*** amotoki has joined #openstack-meeting-405:56
*** gongysh has joined #openstack-meeting-405:57
*** bobh has quit IRC05:57
*** javeriak_ has quit IRC05:58
*** thorst has joined #openstack-meeting-406:00
*** baoli has joined #openstack-meeting-406:01
*** baoli has quit IRC06:05
*** thorst has quit IRC06:07
*** Sukhdev has joined #openstack-meeting-406:13
*** zhurong has joined #openstack-meeting-406:15
*** javeriak has joined #openstack-meeting-406:15
*** hdaniel has joined #openstack-meeting-406:25
*** zhurong has quit IRC06:29
*** zhurong has joined #openstack-meeting-406:30
*** nikhil has quit IRC06:32
*** iceyao has joined #openstack-meeting-406:37
*** iceyao has quit IRC06:41
*** salv-orlando has joined #openstack-meeting-406:42
*** zhurong has quit IRC06:43
*** sdake has quit IRC06:43
*** outofmemory is now known as reedip_06:44
*** markvoelker has joined #openstack-meeting-406:46
*** markvoelker has quit IRC06:50
*** bobh has joined #openstack-meeting-406:53
*** nkrinner has joined #openstack-meeting-406:57
*** bobh has quit IRC06:57
*** sdake has joined #openstack-meeting-406:59
*** mrunge_ is now known as mrunge07:01
*** thorst has joined #openstack-meeting-407:05
*** fjvicens has joined #openstack-meeting-407:07
*** thorst has quit IRC07:12
*** paul-carlton2 has joined #openstack-meeting-407:12
*** fnaval has joined #openstack-meeting-407:12
*** fjvicens has quit IRC07:14
*** fawadk has joined #openstack-meeting-407:15
*** fawadkhaliq has quit IRC07:15
*** fawadkhaliq has joined #openstack-meeting-407:15
*** sdake has quit IRC07:17
*** amotoki has quit IRC07:19
*** fawadk has quit IRC07:20
*** hdaniel has quit IRC07:23
*** belmoreira has joined #openstack-meeting-407:25
*** tfukushima has quit IRC07:28
*** tfukushima has joined #openstack-meeting-407:29
*** amotoki has joined #openstack-meeting-407:31
*** nikhil has joined #openstack-meeting-407:32
*** paul-carlton2 has quit IRC07:32
*** paul-carlton2 has joined #openstack-meeting-407:35
*** amotoki has quit IRC07:35
*** gongysh has quit IRC07:39
*** pcaruana has joined #openstack-meeting-407:43
*** fawadkhaliq has quit IRC07:43
*** evgenyf has joined #openstack-meeting-407:46
*** iceyao has joined #openstack-meeting-407:46
*** amotoki has joined #openstack-meeting-407:49
*** amotoki has quit IRC07:49
*** fnaval has quit IRC07:50
*** gongysh has joined #openstack-meeting-407:55
*** fnaval has joined #openstack-meeting-407:59
*** pasquier-s_ has quit IRC08:03
*** mattymo has quit IRC08:03
*** fnaval has quit IRC08:04
*** pasquier-s has joined #openstack-meeting-408:05
*** mattymo has joined #openstack-meeting-408:05
*** ihrachys has joined #openstack-meeting-408:06
*** fnaval has joined #openstack-meeting-408:07
*** fjvicens has joined #openstack-meeting-408:08
*** thorst has joined #openstack-meeting-408:11
*** fnaval has quit IRC08:11
*** zeih_ has joined #openstack-meeting-408:11
*** zeih_ has quit IRC08:12
*** zeih_ has joined #openstack-meeting-408:12
*** paul-carlton2 has quit IRC08:13
*** javeriak has quit IRC08:13
*** zhurong has joined #openstack-meeting-408:16
*** thorst has quit IRC08:17
*** jed56 has joined #openstack-meeting-408:20
*** acabot has joined #openstack-meeting-408:22
*** matrohon has joined #openstack-meeting-408:25
*** paul-carlton2 has joined #openstack-meeting-408:26
*** fawadkhaliq has joined #openstack-meeting-408:27
*** hdaniel has joined #openstack-meeting-408:28
*** gongysh has quit IRC08:29
*** amotoki has joined #openstack-meeting-408:35
*** amotoki has quit IRC08:36
*** fawadkhaliq has quit IRC08:38
*** amotoki has joined #openstack-meeting-408:45
*** d0ugal_ has quit IRC08:46
*** d0ugal has joined #openstack-meeting-408:46
*** markvoelker has joined #openstack-meeting-408:47
*** watanabe_isao has quit IRC08:49
*** bobh has joined #openstack-meeting-408:50
*** markvoelker has quit IRC08:51
*** gampel has joined #openstack-meeting-408:55
*** bobh has quit IRC08:55
*** yuli_s_ has joined #openstack-meeting-408:56
yuli_s_hello08:57
*** paul-carlton2 has quit IRC08:57
*** DuanKebo has joined #openstack-meeting-408:58
*** mfedosin has joined #openstack-meeting-408:58
*** gsagie has joined #openstack-meeting-408:58
*** javeriak has joined #openstack-meeting-408:59
*** Shlomo_N has joined #openstack-meeting-408:59
nick-mahello08:59
gsagie#startmeeting dragonflow09:00
openstackMeeting started Mon Feb 29 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 to all the dragons :) and the flows..09:00
gampelHi09:00
gsagielet this show begin!09:00
gsagiewho is here for dragonflow meeting?09:00
matrohonhi09:00
Shlomo_Nhi09:00
nick-mahi09:00
matrohonhi09:00
gsagiematrohon: welcome :) first time i see you09:00
matrohongsagie, thanks :)09:01
gampelwelcome09:01
yuli_s_Hello09:01
*** oanson has joined #openstack-meeting-409:01
matrohonI hope there will be room for open discussion today!09:01
gsagie#info gampel, matrohon, nick-ma, oanson, Shlomo_N, yuli_s, gsagie, DuanKebo in meeting09:02
DuanKeboHi09:02
gsagiematrohon: sure, we have a tight schedule but we are here for the open discussion so we will make some time09:02
gsagie#topic design summit09:02
*** openstack changes topic to "design summit (Meeting topic: dragonflow)"09:02
nick-mawe also can move to dragonflow room for discussion.09:02
gsagieso, Dragonflow was approved as big-tent project09:03
matrohongsagie, nick-ma fine!09:03
Shlomo_NCongrats...!09:03
gsagieand this means we need to request for rooms for design summit sessions, we have few topics and gampel09:03
gsagieneed to send an email to request how many rooms09:03
gampelwe need to decide  how many work session  we want in the summit09:03
gsagiehow many sessions09:03
gsagiegampel: i think we also want 1-2 fishbowl to hopefully have a broder community discussion regarding general roadmap and users requests/questions09:04
*** javeriak has quit IRC09:04
gampelI think that we need at least 4  1 hour sessions09:04
gsagieso i was thinking something in the area of 1 fishbowl session and 5 1 hour sessions09:04
gsagieyeah09:04
gampelyes sound good09:04
gsagiegampel: ok, lets also start etherpad to prioritze the points we want to discuss09:05
gsagieso anyone can add09:05
gsagieand publish to mailing list maybe09:05
gampelroad map for N  is one09:05
nick-mawe can list our session schedule on etherpad for priority.09:05
nick-mayes09:05
gsagie#action gampel return design session numbers we need (1 fishbowl, 5x1 hour)09:05
gsagie#action gampel start etherpad for design summit topics09:05
gsagieyeah lets continue on that etherpad, we still have time09:06
gampelI will create the etherpad and sent it to the mailing list09:06
gsagieok great!09:06
gsagiethanks09:06
nick-mathakns09:06
gsagie#topic testing09:06
*** openstack changes topic to "testing (Meeting topic: dragonflow)"09:06
*** dshakhray has joined #openstack-meeting-409:06
gsagieOk, Shlomo_N, yuli_s, please update us on this front09:06
Shlomo_Nok09:06
gsagieWe are starting to create scale and API tests09:06
*** javeriak has joined #openstack-meeting-409:07
Shlomo_NFirst, the data plane performance testing spec was merged into the DragonFlow git repository, you can find it here:09:07
Shlomo_Nhttps://github.com/openstack/dragonflow/blob/master/doc/source/specs/performance_testing.rst09:07
gsagie#link https://github.com/openstack/dragonflow/blob/master/doc/source/specs/performance_testing.rst09:07
Shlomo_N10x gsagie09:07
Shlomo_NI have finished the data plane performance testing for DVR and09:07
Shlomo_NDragonFlow in multi-node environment09:07
gsagieShlomo: good job, lets wait with publishing the results09:08
gsagieuntil we have full picture of Dragonflow with security groups09:08
Shlomo_Nsure09:08
gsagiebut after that we can start pushing things to openstack-performance-docs09:08
gsagieok thanks09:08
*** acabot has quit IRC09:08
*** mbound has joined #openstack-meeting-409:08
gsagieWe need to see how we can automate this09:08
gsagieso we can start applying this per patch09:08
gsagieyuli_s also published API/control plane testing spec09:09
Shlomo_NI am starting to work on the automation part09:09
gsagie#link https://review.openstack.org/#/c/282873/09:09
gsagieso please everyone review and share comments/ideas09:09
*** acabot has joined #openstack-meeting-409:09
gsagiewe also would like to work on this with the community yuli_s and define shared standards09:09
DuanKeboCan we also test the perf of neutron refrence design.09:09
gsagieDuanKebo: thats what we do09:10
*** _degorenko|afk is now known as degorenko09:10
DuanKeboand compare dragonflow's to it .09:10
gsagieDuanKebo: Shlomo_N did a comparsion and will send results09:10
yuli_s_the doc covvers more single box tests09:10
DuanKeboGreat!09:10
gsagiewe need to go over them and verify09:10
gampelGood job Yuli , are you going to do it with rally ?09:10
yuli_s_so, it will be extended as we go09:10
*** amotoki has quit IRC09:10
gsagieyeah as me and yuli_s talked about the goal is to reach rally09:10
yuli_s_and work with bigger test lab09:10
gsagiefor automation, but get initial numbers first as well so we will have an idea what to expect09:11
gampelIt will be important to simulate DB client's as well to test09:11
gampelDC scale 1000+ compute node09:12
gsagiegampel: yes good point, after API we will want to test the DB backend as well09:12
gsagiei think its mentioned in the document09:12
*** amotoki has joined #openstack-meeting-409:13
gsagieyuli_s: i say lets first get initial numbers and then start investigating Rally for this, i can help you with that09:13
*** vikram_ has joined #openstack-meeting-409:13
*** Sukhdev has quit IRC09:13
gsagiehi vikram! :)09:13
yuli_s_gsagie: sure !09:13
gsagieok lets move to the next topic09:13
vikram_hi gal ;)09:13
gsagie#topic DB consistency09:13
*** raofei has joined #openstack-meeting-409:13
*** openstack changes topic to "DB consistency (Meeting topic: dragonflow)"09:13
gsagienick-ma: :)09:13
gampelwelcome @ vikram_09:13
nick-mathe current code is in the review.09:13
gsagiehi raofei welcome09:13
raofeihi09:13
vikram_gampel; thanks09:13
gsagie#info raofei, vikram are in meeting as well09:13
gsagienick-ma: good job, i did saw we had some exceptions in neutron server, will re check09:14
nick-mai'm also working on the testing. there are some errors on updating subnet in fullstack.09:14
gsagieyeah i saw some tests are sometimes failing09:14
nick-mai updated the code.09:14
nick-mayes. but for manual testing and rally, it works.09:14
nick-maso i need to figure out why.09:14
yuli_s_the DB consistency architecture is great, I think we might have some rejections from neutron team that we want to add a new table09:15
gsagie#link DB consistency review https://review.openstack.org/#/c/282290/09:15
*** qwebirc77623 has joined #openstack-meeting-409:15
*** thorst has joined #openstack-meeting-409:15
yuli_s_to sync data in neutron db09:15
gsagienick-ma: okie great09:15
gsagieyuli_s: thats not a problem09:15
gampelit is an additional table only accessed from our plugin i do not see a problem09:15
yuli_s_gsagie: i hope too09:15
gsagienick-ma: okie let us know if you need any help with investigating these tests, i saw some fails that relate to floating ip as well09:16
nick-mayes. there's no problem for adding a new table for a plugin.09:16
gsagieanything else for DB consistency?09:16
gsagie#topic pub-sub09:17
*** openstack changes topic to "pub-sub (Meeting topic: dragonflow)"09:17
gsagieokie..09:17
nick-mathere's some discussion on getting rid of neutron db and just use nosql for persistent storage. i'll write my thoughts on it. we can discuss it later.09:17
gsagienick-ma: okie, we had same thoughts but this require much more work and needs to be synced with the Neutron community09:17
gsagieso its defiantly not for this release09:18
gampelyes this is a big change  and the biggest problem there is that the DB is only eventually  consistent09:18
yuli_s_for me it is not clear why we need to use ZerroMQ together with redis09:18
nick-mayes, you are right.09:18
gsagiegampel: the pub-sub stage is yours, please publish us some status :)09:18
DuanKeboredis pub/sub driver is under test now.09:18
gampelYes pub-sub status09:18
DuanKebo@ruli_s Yes09:18
gampelwe have the ZMQ merged09:19
DuanKeboWe are try not to use zerroMQ in redis driver09:19
gampeland@ omer is  working  on separating the publisher into a different service09:19
gsagieDuanKebo: gampel found some interesting posts describing that ZeroMQ performance is much better then Redis09:19
gsagiewe do need to verify all of it09:19
gampelCurently we only support Neutron server Publishers09:19
gsagieso it might prove more efficent to us redis as DB backend and ZeroMQ as the pub/sub09:20
yuli_s_gsagie: in the control performance doc we are covering this09:20
DuanKeboYes, we will investigate it.09:20
gampelwe do not support for this release  controller to controller09:20
gampelthe chasiss are handled from the neutron server side09:20
gampelZMQ and REdis do not work together  they are two drivers09:21
gsagieDuanKebo, gampel: any open points regarding Redis pub/sub?09:21
gampelwe can use any DB with any Pub sub driver09:21
gsagieany problems we need to discuss?09:21
oansonIn case we'll want DFcontroller-DFcontroller, we can use the database + a table monitor on the controller.09:21
DuanKeboCurrently, we are using redis for db and pub/sub09:21
gampelFrom the discussion today we understand  that redis does not need to bind a local socket for the publisher09:21
DuanKeboBut open to other opinions09:22
gampeland can run publisher per Neutron server process09:22
DuanKeboopent to other options.09:22
*** thorst has quit IRC09:22
gsagieokie, then the implementation doesnt need to use the pub/sub service09:22
DuanKeboYes, it support multiply neutron servers on one host.09:22
oansonDuanKebo, by separating the pub/sub and DB drivers, we allow flexibility. In configuration, we can select to do both with redis, or DB with redis and pub/sub with ZMQ.09:23
gampelwhat I suggest is that we test performance of the different Pub?sub and then we could compare them all09:23
gsagieDuanKebo, gampel: okie then, lets continue with Redis implementation and compare results to Redis + ZeroMQ or only Redis09:23
yuli_s_yes, we can start the actual control plane test from here09:23
gsagieDuanKebo: is there any time frame for Redis to be completed?09:23
gampelFor M Cycle i propose to focus only on Neutron server publishers09:23
gsagieare we close?09:23
*** amotoki has quit IRC09:24
DuanKeboWe are doing the test.09:24
*** patrickeast has quit IRC09:24
DuanKeboI think  it can be finished this week09:24
gsagiethe test or the code?09:24
DuanKebothe test09:24
nick-mawe need to build gate check for each db backend.09:25
gampelyes this is a good idea09:25
*** patrickeast has joined #openstack-meeting-409:25
*** baohua has quit IRC09:25
gsagieDuanKebo: okie, so please update us with the results09:25
gsagiewhen you have them09:25
*** paul-carlton2 has joined #openstack-meeting-409:25
DuanKeboOK, np09:25
gampelI will add it to the list and register a bug09:25
oansonGate-tests for each possible configuration is very expensive performance-wise, and may take a lot of time. I think this should be considered.09:26
gsagieBut if the effort of completing Redis is minimal, i think we should do it with the pub/sub as well09:26
yuli_s_DuanKebo: check this out https://github.com/openstack/performance-docs/blob/master/doc/source/test_plans/mq/plan.rst09:26
*** zeih_ has quit IRC09:26
gsagielets talk about gate tests after..09:26
nick-mayes, very expensive. :-)09:27
gsagieokie09:27
gsagie#action DuanKebo publish results of pub/sub testing09:27
gampelI think in this teste there are not using pub/sub sockets09:28
gsagie#action DuanKebo try to asses the time it takes to finish Redis for both pub/sub and DB09:28
gsagiegampel:  we need to test this end to end, if the effort of adding this now is small i think we need to test this end to end09:28
gampel@DuanKebo the test are mainly for The MSQ part and not for the Pub/Sub09:29
gsagieThere are some advantage to selective proactive distribution with redis09:29
gsagiewe need to explore09:29
gsagieso lets see if we can complete the work and then do the testing09:29
gsagieDuanKebo: what do you think?09:30
gampelYes i think that the controller path testing will be the key for the selection09:30
yuli_s_DuanKebo I will be happy to help with the test09:30
gsagieokie, lets continue talking about this after09:31
gsagie#topic security groups and port security09:31
*** openstack changes topic to "security groups and port security (Meeting topic: dragonflow)"09:31
*** acabot_ has joined #openstack-meeting-409:31
gsagiedingbo here?09:31
gsagieraofei: can you update on this?09:31
gampelwe will add th reliability latter but I agree we should start testing as soon as possible09:31
*** zeih_ has joined #openstack-meeting-409:31
raofeisecurity group is done by Yuanwei now09:31
raofeiThe code is almostly completed, now it's testing09:32
gsagieokie, you know when he will upload it up stream?09:32
gsagieso we can all review09:32
gampelmaybe ask him to upload with WIP09:33
gampelso we could speed the review cycle09:33
raofeiYes, I think so. @duankebo, when does yuanwei can commit the latest code?09:33
gsagiei think he is disconnected09:34
DuanKeboonline again09:34
gsagieahh ok09:34
gsagiewelcome back :)09:34
*** zhurong has quit IRC09:34
DuanKeboI will confirm it with yuanwei09:34
*** amotoki has joined #openstack-meeting-409:34
DuanKeboI think it may be this week09:34
gsagieDuanKebo: please do because we are approaching end of release09:34
gsagiedoing the testing without security groups is pointless09:35
gsagie#action DuanKebo check security groups status and upload for review to upstream09:35
gsagie#topic distributed DNAT09:35
*** openstack changes topic to "distributed DNAT (Meeting topic: dragonflow)"09:35
DuanKeboyes. as i know most of the code have been finished.09:35
gsagieraofei: ...:)09:35
raofeiit's coding phase.09:36
gsagieonly the application is missing right?09:36
raofeiI think the coding and testing will be completed  this week.09:36
raofeiyes.09:36
gsagieraofei: ok good job09:36
gampelgreat :)09:36
raofeiof course, the plugin also need to do some change.09:36
gsagie#action raofei upload distributed dnat upstream for review09:37
DuanKebo@raofei Hujie is doing the integration09:37
gsagie#topic selective proactive09:37
*** openstack changes topic to "selective proactive (Meeting topic: dragonflow)"09:37
gsagieDuanKebo: i saw the code, i need to see about my comments from last patch but over all it looks good09:37
gsagieneed to make sure the OVSDB monitor patch updates the correct queue and it seems we have this covered and we only then need the support of the DB/pub sub09:38
DuanKeboYes i have saw the comments.09:38
DuanKeboand will upload a patch today.09:38
DuanKeboit is under testing aslo.09:38
gsagieoanson: you have a bug on you to move the local cache to be tenant aware, will you find time to work on this?09:38
oansonSure09:38
gsagieDuanKebo: ok great job, looks good to me09:38
gsagie#action oanson continue gsagie patch for Tenant aware cache09:39
gsagiewe can then create better searched per tenant in cache09:39
gsagieDuanKebo: any open issue regarding that?09:39
gsagie#link tenant cache https://review.openstack.org/#/c/277176/09:39
DuanKebo@gsagie I need nb-api to support query by topic09:39
gampelYou mean adding additional indexes  ?09:39
gsagiegampel: no, we talked about that to make the cache structure by tenants09:40
DuanKeboSome apis miss this para. But we can discuss this after the IRC09:40
gsagieso you have a list/dict of tenants and so on09:40
gampelI see we just need to make sure we do not slow the other query s09:40
gsagieDuanKebo: ok, look at this patch: https://review.openstack.org/#/c/284178/09:40
gsagieit has eveyrthing you need i think09:40
gsagiewe need to merge it soon09:40
DuanKeboOK09:41
gsagiegampel: maybe you can review and merge09:41
gampelOK09:41
gampeli will09:41
gsagiegampel: its not going to slow things only make them faster09:41
gsagieboth for L3 apps and for DB/controller09:41
gsagieespecially when using L3 reactive09:42
*** xingchao has quit IRC09:42
gsagiei do have some work to also fix some things in the L3 proactive app09:42
gsagie#action gsagie decrease flow number in L3 proactive app, one flow per router interface09:42
gsagiefor controller reliability, we need to review this code09:43
gsagie#topic controller reliability09:43
*** openstack changes topic to "controller reliability (Meeting topic: dragonflow)"09:43
gsagieDuanKebo: is there any open issue for that?09:43
DuanKebono09:43
DuanKeboThis work is delayed.09:43
gsagieokie great, gampel, Li-Ma please review this patch when you have time (and everyone else of course)09:44
DuanKeboHeshan(The guy in charge of this) has been assigned another work09:44
gsagieDuanKebo: ok :(09:44
gampelI will review it today09:44
gampelso we need some one to pick this work09:45
*** xingchao has joined #openstack-meeting-409:45
gsagieDuanKebo: its probably not the most urgent job, but do you want someone else continue this work?09:45
nick-maokie09:45
gsagiei can work on it09:45
DuanKeboNo, Heshan will come back soon09:45
gsagieor you have anyone else?09:45
gsagieok09:45
DuanKeboHe can continue this work.09:45
gsagie#info Heshan come back :) we need you!09:46
gsagie#topic open discussion09:46
*** openstack changes topic to "open discussion (Meeting topic: dragonflow)"09:46
gsagiematrohon: stage is yours :)09:46
matrohongsagie, thanks09:46
gsagiethen we can talk about CI jobs09:46
matrohonas nick-ma said earlier, we are considering getting rid of neutron db, and rely on a nosql db instead09:47
nick-mahaven't decided yet. there are lots of tradeoffs and discussion on it.09:47
matrohonthis kind of work take place in the following context :09:47
matrohon#link https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/734209:47
gsagiematrohon: you work with nick-ma?09:47
gampelDid you evaluate  how much work it is ?09:48
matrohongsagie, no, I'm working on distributed cloud09:48
matrohonsome experiments have already been done by replacing the neutron db backend with redis09:48
gsagiematrohon: such a model can really help us, so its an interesting thing that we actually also considered09:49
nick-mai will go to that topic and we can discuss it during the summit.09:49
matrohonnick-ma, +109:49
gampelwe consider it as well main issues are the eventually consistency of teh D DB and the work load09:49
*** iceyao has quit IRC09:49
gsagiewe would all like to participate, i think gampel and I would also love to be there09:49
matrohonthere are chances that a dedicated WG gets created in Openstack09:49
nick-maneutron xxx-list may mislead end-users when db backend is not ACID, due to eventual consistency.09:50
matrohongampel, yep, I'm not a nosql expert, but I understand that it's a challenging topic09:50
nick-mayes.09:50
gampeland the query speed09:51
gampelfor read09:51
gsagiematrohon: its nice to know about this effort, how can we help?09:51
matrohonit seems your group already gave it a lot of thoughs, it would be awesome to share them in the WG09:51
nick-mafor that dedicated WG? I'm interested in it.09:51
*** sdake has joined #openstack-meeting-409:51
gsagiematrohon: ok would love that, how do we do it?09:51
gampelyes this is a great effort  that we would like to join09:51
matrohongsagie, we'll probably set up a dedicated meeting during the next summit, I'll let you know09:52
gsagiematrohon: ok that will be great, thanks for sharing and hope to meet you in the summit09:52
nick-maawesome.09:52
gsagiewe might also use one Dragonflow design session to discuss about it, as we explored this area quiet alot09:53
gampelYes lets us know and if there is active talk about it can you please send us a link09:53
matrohondo you already have some materials about changes to be made in upstream project to achieve the distributed goal09:53
matrohon?09:53
*** evgenyf has quit IRC09:53
gsagie#link https://www.openstack.org/summit/austin-2016/vote-for-speakers/presentation/734209:53
gampelyes this is a good idea DB consistency and DB alternative09:53
gsagiematrohon: nothing written09:54
*** ihrachys has quit IRC09:54
gsagiematrohon: but we know others that might be interested with this as well09:54
nick-mayou can review the spec of db consistency. we discussed a lot during review.09:54
nick-mamatrohon: .09:54
matrohongsagie, great!09:54
matrohonnick-ma, I'll do thanks09:54
gsagieokie, so lets continue talk about this and feel free to drop to our channel #openstack-dragonflow if you have any more questions09:55
matrohongsagie, ok09:55
gsagieand if you guys start meeting before the summit, would love to join09:55
gsagiefor the CI, i think we need to decide on our default setup first09:55
gsagieas i mentioned to nick-ma in one of the reviews, i think he will also want to run CI for zookeeper09:56
gampelFor the Ci I feel it is very impotent to test the main used DB drivers09:56
*** iceyao has joined #openstack-meeting-409:56
gsagiegampel: i agree, so maybe after Redis is implemented we can add this as well09:56
gampelin the CI so it seem that zookeeper, Redis, etcd09:56
gsagieyep09:57
gampeldo we have a limit on the number of CI ?09:57
gampeljobs09:57
gsagieat least for the fullstack tests, dont know if we need to do it for tempest09:57
gsagiegampel: i am not aware of such restriction, but i dont think it will be a problem to add 2 more jobs09:57
nick-maif we set up all of them, it will take long time on verification.09:57
gampelyes i agree for the fullstack09:57
gsagienick-ma: i think its done in parallel so not sure about that09:58
oansonDo we want such a job only for zookeeper, redis, etcd?09:58
nick-maok09:58
oansonOr any other db driver we add?09:58
nick-mafullstack only? or adding tempest api testing?09:58
gampeli think it is enough  for now09:58
gsagieoanson: lets decide that as we go, right now i dont see a reason to add anythign else09:58
*** shaohe_feng has joined #openstack-meeting-409:58
gampelRamCloud is not used yet09:58
gsagienick-ma: what do you suggest?09:58
oansonAll right09:58
gsagiei think fullstack is enough as it grows it verify the important things09:59
*** salv-orl_ has joined #openstack-meeting-409:59
gsagietempest is more about the controller logic and less about the DB it self09:59
nick-mapriority? before or after summit?09:59
gsagiemaybe add some more DB specific tests to the fullstack09:59
*** ihrachys has joined #openstack-meeting-409:59
gampelyes I agree only fullstack and maybe rally latter09:59
*** thorst has joined #openstack-meeting-409:59
gsagienick-ma: zookeeper depends on you :)10:00
gsagiei can add the one for Redis10:00
yuli_s_gsagie: meta service without q-dhcp10:00
yuli_s_:)10:00
gsagieyuli_s: yeah, we need to work on this as well :)10:00
nick-maok10:00
gampelthis is a feature we do not support yet10:00
gsagielets take this offline as our time is done10:00
gsagiethanks everyone for attending!10:00
gampelthanks10:00
gsagieand see you next week10:01
gsagie#endmeeting10:01
nick-mathanks see you.10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:01
openstackMeeting ended Mon Feb 29 10:01:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-02-29-09.00.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-02-29-09.00.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-02-29-09.00.log.html10:01
DuanKeboBye10:01
raofeibye!10:01
yuli_s_bye10:01
*** salv-orlando has quit IRC10:02
*** Shlomo_N has left #openstack-meeting-410:02
*** oanson has left #openstack-meeting-410:03
*** thorst has quit IRC10:06
*** sdake has quit IRC10:06
*** wznoinsk__ is now known as wznoinsk10:07
*** DuanKebo has quit IRC10:09
*** prithiv has joined #openstack-meeting-410:13
*** tfukushima has quit IRC10:28
*** iceyao has quit IRC10:30
*** acabot_ has quit IRC10:32
*** iceyao has joined #openstack-meeting-410:36
*** salv-orlando has joined #openstack-meeting-410:42
*** salv-orlando has quit IRC10:43
*** salv-orl_ has quit IRC10:43
*** sdake has joined #openstack-meeting-410:43
*** salv-orlando has joined #openstack-meeting-410:43
*** markvoelker has joined #openstack-meeting-410:47
*** bobh has joined #openstack-meeting-410:52
*** markvoelker has quit IRC10:52
*** yamamoto_ has quit IRC10:53
*** sdake has quit IRC10:53
*** bobh has quit IRC10:56
*** flaper87 has quit IRC10:56
*** flaper87 has joined #openstack-meeting-410:56
*** amotoki has quit IRC11:00
*** amotoki has joined #openstack-meeting-411:03
*** acabot_ has joined #openstack-meeting-411:04
*** gsagie has left #openstack-meeting-411:04
*** thorst has joined #openstack-meeting-411:06
*** sdake has joined #openstack-meeting-411:06
*** iceyao has quit IRC11:10
*** JieLi has joined #openstack-meeting-411:10
*** thorst has quit IRC11:11
*** amotoki has quit IRC11:11
*** iceyao has joined #openstack-meeting-411:12
*** acabot_ has quit IRC11:14
*** sdake has quit IRC11:16
*** JieLi has quit IRC11:24
*** dims has joined #openstack-meeting-411:29
*** yamamoto has joined #openstack-meeting-411:31
*** mfedosin has quit IRC11:31
*** dims has quit IRC11:32
*** dims has joined #openstack-meeting-411:32
*** yamamoto_ has joined #openstack-meeting-411:33
*** yamamoto has quit IRC11:36
*** iceyao has quit IRC11:39
*** dingboopt has joined #openstack-meeting-411:42
*** mfedosin has joined #openstack-meeting-411:44
*** javeriak has quit IRC11:53
*** gampel has quit IRC11:55
*** dave-mccowan has joined #openstack-meeting-411:55
*** marcusvrn_ has joined #openstack-meeting-411:55
*** xingchao has quit IRC11:56
*** mfedosin has quit IRC11:58
*** shh_away has joined #openstack-meeting-411:58
*** spotz_zzz is now known as spotz12:03
*** zeih_ has quit IRC12:03
-openstackstatus- NOTICE: Infra currently has a long backlog. Please be patient and where possible avoid rechecks while it catches up.12:06
*** prithiv has quit IRC12:08
*** bobh has joined #openstack-meeting-412:14
*** fangzhen has joined #openstack-meeting-412:16
*** mfedosin has joined #openstack-meeting-412:16
*** fangzhen has quit IRC12:17
*** zeih has joined #openstack-meeting-412:18
*** bobh has quit IRC12:19
*** baoli has joined #openstack-meeting-412:22
*** baoli has quit IRC12:22
*** zeih has quit IRC12:28
*** amotoki has joined #openstack-meeting-412:30
*** zeih has joined #openstack-meeting-412:30
*** thorst has joined #openstack-meeting-412:32
*** bobh has joined #openstack-meeting-412:36
*** acabot_ has joined #openstack-meeting-412:42
*** amotoki has quit IRC12:45
*** markvoelker has joined #openstack-meeting-412:48
*** markvoelker has quit IRC12:53
*** pcaruana has quit IRC12:53
*** mbound has quit IRC12:54
*** baoli has joined #openstack-meeting-412:55
*** julim has joined #openstack-meeting-412:56
*** mbound has joined #openstack-meeting-412:59
*** spotz is now known as spotz_zzz13:00
*** amotoki has joined #openstack-meeting-413:02
*** zeih has quit IRC13:02
*** woodard has joined #openstack-meeting-413:06
*** dtardivel has joined #openstack-meeting-413:07
*** woodard has joined #openstack-meeting-413:07
*** pcaruana has joined #openstack-meeting-413:08
*** prithiv has joined #openstack-meeting-413:10
*** qwebirc77623 has quit IRC13:13
*** yuli_s_ has quit IRC13:13
*** klamath has joined #openstack-meeting-413:18
*** iceyao has joined #openstack-meeting-413:29
*** acabot_ has quit IRC13:37
*** amotoki has quit IRC13:39
*** acabot_ has joined #openstack-meeting-413:39
*** acabot__ has joined #openstack-meeting-413:41
*** fawadkhaliq has joined #openstack-meeting-413:43
*** acabot_ has quit IRC13:44
*** markvoelker has joined #openstack-meeting-413:47
*** baoli has quit IRC13:47
*** ninag has joined #openstack-meeting-413:47
*** baoli has joined #openstack-meeting-413:48
*** amotoki has joined #openstack-meeting-413:53
*** baohua has joined #openstack-meeting-413:54
*** baohua has quit IRC13:57
*** baohua has joined #openstack-meeting-413:57
*** neelashah has joined #openstack-meeting-413:58
*** mbound has quit IRC14:00
*** haleyb has joined #openstack-meeting-414:06
*** cemmason has joined #openstack-meeting-414:08
*** mbound has joined #openstack-meeting-414:09
*** bobh has quit IRC14:14
*** yifei has quit IRC14:15
*** yifei has joined #openstack-meeting-414:15
*** zeih has joined #openstack-meeting-414:16
*** ajmiller has joined #openstack-meeting-414:18
*** cemmason has quit IRC14:19
*** cdelatte has joined #openstack-meeting-414:21
*** ajmiller has quit IRC14:25
*** andymaier has joined #openstack-meeting-414:26
*** KLevenstein has joined #openstack-meeting-414:27
*** banix has joined #openstack-meeting-414:31
*** sdake has joined #openstack-meeting-414:35
*** pcaruana has quit IRC14:38
*** rbak__ has quit IRC14:39
*** xingchao has joined #openstack-meeting-414:39
*** sigmavirus24_awa is now known as sigmavirus2414:42
*** vhoward has joined #openstack-meeting-414:47
*** bobh has joined #openstack-meeting-414:47
*** jmckind has joined #openstack-meeting-414:48
*** baohua has quit IRC14:48
*** bobh has quit IRC14:49
*** bobh has joined #openstack-meeting-414:49
*** acabot__ has quit IRC14:52
*** pcaruana has joined #openstack-meeting-414:52
*** apuimedo has joined #openstack-meeting-414:53
*** rbak has joined #openstack-meeting-414:55
*** yamahata_ has quit IRC14:55
*** blahRus has joined #openstack-meeting-414:57
*** sdake has quit IRC14:58
*** xingchao has quit IRC15:00
apuimedo#startmeeting kuryr15:01
openstackMeeting started Mon Feb 29 15:01:07 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: kuryr)"15:01
openstackThe meeting name has been set to 'kuryr'15:01
banixhi15:01
*** gsagie has joined #openstack-meeting-415:01
apuimedoHello everybody and welcome to another kuryr weekly meeting15:01
gsagieHello!15:01
fawadkhaliqhi15:01
apuimedoapart from banix, who's here?15:01
salv-orlandome15:01
apuimedoirenab: fkautz: are you there?15:02
irenabhey15:02
apuimedo#info banix, gsagie, fawadkhaliq, salv-orlando, irenab and apuimedo in the meeting15:02
apuimedoThank you all for joining15:02
apuimedolet's get the party started15:03
*** dane_leblanc has joined #openstack-meeting-415:03
apuimedowho brings the red plastic cups?15:03
apuimedo#topic design summit logistics15:03
*** openstack changes topic to "design summit logistics (Meeting topic: kuryr)"15:03
apuimedo#link https://etherpad.openstack.org/p/kuryr-design-summit15:03
apuimedoIn this etherpad you can see the topics that were discussed via email and a tentative list of requirements for Gal to send15:04
gsagiefrom that list, i think we want to request 1-2 fishbowl sessions and around 5-6 work sessions15:04
apuimedo(thanks Gal for compiling it)15:04
gsagieand hope to get it15:04
irenabgsagie: it should be Tu-Thu?15:05
gsagieI am also checking how we can get a spot (if possible) in the operators summit day thanks to Salvatore suggestion15:05
apuimedoMost of you already commented about the topics and so on, but before gsagie sends it, iare there further comments?15:05
gsagieso we can learn about mixed openstack containers production/dev deployments15:05
apuimedogsagie: salv-orlando: ops presence would be great15:05
apuimedowe could do with more end-user feedback15:05
gsagieirenab: sec checking15:06
gsagieirenab: tue-friday15:06
gsagiewe will request friday free talks half day as well15:06
apuimedogsagie: how long are fishbowl and work session slots?15:06
gsagie40 minutes15:06
* apuimedo can't remember15:06
gsagie+ 10 minutes break15:06
salv-orlandoapuimedo, gsagie sure it would be great to know how many are using kuryr and in which way15:06
apuimedo#info fishbowl and work session slots are 40 minute15:07
*** xingchao has joined #openstack-meeting-415:07
apuimedosalv-orlando: if the answer is more than 0 I'll be surprised, since we did not release yet :P15:07
apuimedobut who knows these days, people like to live at the bleeding edge15:07
irenabgsagie: apuimedo : I think it worth to send an email to the opestack-ops mailing list15:07
apuimedoirenab: good point15:07
irenabto track attesion prior to the summit15:08
salv-orlandoapuimedo: indeed. whuch probably begs one question on how to put together a meaningful ops session15:08
apuimedogsagie: do you take that one?15:08
gsagieapuimedo: yep15:08
apuimedosalv-orlando: I was thinking of showing something similar to what I showed on Fosdem15:08
gsagiewould love to learn about the use cases people are facing without Kuryr as well, just understand what the common ways to deploy and connect between the two environments , maybe we can get some priorities depending on problems15:08
apuimedobut in this case, swarm bare metal alongside OSt and communication between conts and VMs15:08
apuimedo#action gsagie to prepare a proposal/email to the ops list detailing what we'd like to show and try to get some feedback15:09
irenabapuimedo: and nested case too15:09
fawadkhaliqgsagie: +115:09
gsagieso the numbers of 1-2 fishbowl + 5-6 work sessions sounds ok?15:10
gsagieand Friday15:10
apuimedook, to close this agenda point, I'd like it if we could maybe agree that each session should probably only get one topic and we should try to decide which should be fish bowl and which work sessions15:10
*** sivaramakrishna has joined #openstack-meeting-415:10
apuimedo(can be done offline in the etherpad by voting with your name next to the point)15:10
irenabapuimedo: probably after the slots are confirmed?15:11
apuimedolike for example:15:11
apuimedoDocumentation: fishbowl (toni) worksession()15:11
apuimedoirenab: well, I want to see what kind of discussion people feel we should have on each item15:11
irenabthe main difference is?15:12
irenabtalking versus coding?15:12
apuimedoI feel like in working sessions it is a bit less directed15:12
apuimedothe agenda15:12
gsagieapuimedo: i think we can get some good progress on small groups of work sessions (i dont expect too much people anyway)15:13
apuimedoAgreed15:13
gsagieand we need to return an answer this week15:13
gsagieregarding our request15:13
irenabgsagie: so maybe its more about big/smaller rooms?15:13
apuimedofor fishbowl I was thinking about early planning things like mesos and horizon integration15:14
gsagiei think 5-6 sessions and Friday is more then enough (and probably we will not get more)15:14
apuimedogsagie: sounds good15:14
apuimedomoving on15:14
gsagieirenab: yeah, i dont think we really need the big rooms, maybe just 1-2 session for road map and requierments discussion which we might want more people15:14
apuimedo#action gsagie to send the rooms request. Last chance today for people to add stuff to the etherpad :-)15:15
gsagieokie great15:15
apuimedo#topic Kubernetes integration15:15
*** openstack changes topic to "Kubernetes integration (Meeting topic: kuryr)"15:15
irenabapuimedo: let me update here15:15
apuimedoI was gonna ask you anyway15:15
apuimedo#link https://review.openstack.org/#/c/281132/15:16
*** ajmiller has joined #openstack-meeting-415:16
irenabI pushed the initial spec, early draft and will send update with more details and adress the comments15:16
apuimedoirenab: Do you think it could benefit from the diagram I made yesterday for the prototyping we are doing?15:16
irenabWe had chatwith gsagie yesterday and sent email to the k8s-sig-network regarding the concerns we had15:17
apuimedocause if it does, you can freely copy it over :-)15:17
irenabapuimedo: Lets sync offline and the answer is probably yes, but I want to flash it out a bit more15:17
apuimedo*flesh :P15:18
apuimedoalright15:18
irenabinitial intent is to focus on requirements and discuss the translation from k8s to neutron models15:18
irenabapuimedo:  sorry, typing to fast15:18
*** fnaval has joined #openstack-meeting-415:18
gsagieapuimedo, irenab: i looked at the diagram and think it makes sense, at least it solves most of the problems i could think of that we talked with irenab15:18
apuimedoit just has a very special meaning to flash things out :D15:18
gsagiewould be great to get it in Kuryr repo as well15:18
apuimedoirenab: ok. My intention is to then send two specs15:18
gsagieand start discussion15:18
*** mestery has quit IRC15:19
apuimedo(not necessarily myself)15:19
gsagieheh :)15:19
apuimedoone for the CNI driver15:19
apuimedoone for the API watcher15:19
*** mestery has joined #openstack-meeting-415:19
apuimedothat will answer the requirements of the spec you sent irenab15:19
irenabapuimedo: gsagie : I think it makes to capture all piece at high level in the spec and add devref for the details15:19
gsagiebtw, sorry for raising this now, but Kuryr is going to be mentioned in ONS (by Eshed Gal Or) in this talk: http://ons2016.sched.org/event/67nA/container-based-dynamic-service-chain-using-distributed-sdn-pipeline-injection-openstack-dragonflow-kuryr-eshed-gal-or-huawei?iframe=yes&w=&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no15:20
gsagieif anyone is going..15:20
salv-orlandogsagie: I did not know ons was still a thing ;)15:20
apuimedogsagie: this is on the community updates agenda point ;-)15:20
apuimedoI'll bring it up later and we add it as a link ;-)15:20
gsagiesalv-orlando: heh same..15:20
apuimedoirenab: I'm not sure I got it completely15:21
apuimedoah, ok, now I got it15:21
*** izaakk has joined #openstack-meeting-415:21
apuimedoyou mean that those two sections should be devref instead of spec15:21
irenabapuimedo: yes15:21
apuimedoI'm more than fine with it. Good idea :-)15:21
apuimedo#action apuimedo to send API watcher as devref15:21
apuimedo#action devvesa to send CNI driver as devref15:22
apuimedo#action all to review the current spec15:22
apuimedoanything more about k8s before we move on to nested?15:22
salv-orlandoapuimedo: I think that is all atm15:22
gsagienot from me, but they are obviously also related :)15:22
apuimedocool!15:22
apuimedo#topic VM-nested containers15:23
*** openstack changes topic to "VM-nested containers (Meeting topic: kuryr)"15:23
irenabI think banix and the team also play with k8s15:23
apuimedoindeed. I was hoping mpreitzer would also be in the meeting15:23
gsagieyeah, actually would love to get banix and IBM team thoughts about the Kubernetes integration15:23
apuimedobut we can continue engaging in the spec, I think he made a few comments15:23
gsagieand how they see it, but i guess we can also iterate on the review15:23
banixi believe mike has a prototype running15:23
irenabusing libnetwork?15:24
apuimedofawadkhaliq: the floor is yours (thanks for addressing all the comments, I'll try to review it today)15:24
fawadkhaliqapuimedo: thanks15:24
banixwe will comment on the review15:24
apuimedoirenab: yup, using libnetwork15:24
irenabbanix: thanks15:24
apuimedo#link https://review.openstack.org/#/c/269039/9/doc/source/specs/mitaka/nested_containers.rst15:24
banixirenab: yes.15:24
fawadkhaliqso the spec is updated after all the comments. thanks for the review everyone15:24
fawadkhaliqwe got reviews from Magnum team as well15:24
* apuimedo has been bad lately with getting to it15:24
fawadkhaliqNow action item for all of you to review the current version so we can close on it soon15:25
fawadkhaliq:-)15:25
apuimedoyes, it was great to see hongbin and adrian joining in15:25
apuimedo#action apuimedo and all to review the spec!15:25
gsagiefawadkhaliq: great will do it today/tommorow but i also want to wait so we get approval from the Magnum guys before we merge it15:25
gsagiemaybe ping Adrian/Daneyon to review it15:25
fawadkhaliqnext steps would be to start hashing out details about the Kuryr Agent.15:25
apuimedofawadkhaliq: gsagie: maybe we can...15:25
fawadkhaliq#link https://blueprints.launchpad.net/kuryr/+spec/kuryr-agent15:26
apuimedoyup, nagging them a bit :-)15:26
irenabfawadkhaliq: can the implementation start based on the VLAN aware VM support progress?15:26
fawadkhaliqgsagie: agree and makes sense15:26
*** xingchao has quit IRC15:26
apuimedofawadkhaliq: are you going to use vlan aware VM or the binding profile for starting out?15:26
*** Hui has joined #openstack-meeting-415:26
fawadkhaliqirenab: I will have to evaluate the current status of VLAN aware VMs and will comment on this15:26
*** iceyao has quit IRC15:26
*** irenab has quit IRC15:26
fawadkhaliqI am hoping VLAN aware VMs15:26
*** iyamahat has joined #openstack-meeting-415:26
apuimedovery well15:27
fawadkhaliqif not, then binding profile could be for the used until, I will check and comment15:27
apuimedofawadkhaliq: apart from reviews, is there any tasks you'd like to create or get help with?15:27
banixdo we know the status of vlan-aware vm work?15:28
*** MarkAtwood has joined #openstack-meeting-415:28
*** irenab has joined #openstack-meeting-415:28
fawadkhaliqapuimedo: I think at this point, I will involve you, gsagie, irenab in the agent discussion15:28
banixbeyond the spec that is15:28
*** irenab has quit IRC15:28
apuimedovery well fawadkhaliq. You got that ;-)15:28
fawadkhaliqapuimedo: nothing else so far. will let you know, thanks15:28
*** spotz_zzz is now known as spotz15:28
fawadkhaliqthats all on the nested containers today15:29
gsagiebanix: i am not aware of progress, but maybe i missed it15:29
apuimedobanix: I got the sensation from russellb's comment that "in the meantime we could use the binding profile"15:29
fawadkhaliqbanix: I will send an update on the current progress15:29
apuimedothat it probably will be some time until it is functional in devstack15:29
* russellb looks up15:29
fawadkhaliqapuimedo:  please assign an action item to me for that15:29
apuimedo#action fawadkhaliq report on vlan aware VMs progress to the ML15:29
russellbvlan-aware-vms is in progress.  the OVN plugin has an OVN specific binding profile that can be used now, yes15:29
russellbthere are initial vlan-aware-vms API patches up for review now15:30
russellbmarked WIP last i checked though15:30
fawadkhaliqrussellb: thanks, will check out the binding profile mechanism15:30
russellbso might be early Newton cycle work15:30
*** irenab has joined #openstack-meeting-415:30
apuimedorussellb: thanks a lot for checking in!15:30
russellbthe OVN binding profile mechanism is here: http://docs.openstack.org/developer/networking-ovn/containers.html15:30
gsagiefawadkhaliq: can help you with that if you need15:31
apuimedorussellb: who is working on the implementation now?15:31
russellbvlan-aware-vms patches: https://review.openstack.org/279253 https://review.openstack.org/279251 https://review.openstack.org/281723 https://review.openstack.org/28340715:31
fawadkhaliq#link OVN binding profile mechanism http://docs.openstack.org/developer/networking-ovn/containers.html15:31
russellbalso related to vlan-aware-vms work https://review.openstack.org/27395415:31
apuimedo#link https://review.openstack.org/27395415:31
apuimedolink https://review.openstack.org/27925315:32
apuimedo#link https://review.openstack.org/27925315:32
apuimedoand so on :P15:32
apuimedothanks russellb15:32
russellbnp15:32
*** xingchao has joined #openstack-meeting-415:32
apuimedomoving on to the next topic15:32
apuimedobanix, your time has come15:32
apuimedo#topic Existing network reuse15:32
*** openstack changes topic to "Existing network reuse (Meeting topic: kuryr)"15:32
banixso I tried a couple of approaches15:33
banixOne that keeps using Neutron network name to store the Kuryr network ID15:33
irenabapuimedo: can you please post the link to the agenda?15:33
apuimedoirenab: yes15:33
apuimedohttps://wiki.openstack.org/wiki/Meetings/Kuryr#Meeting_February_29.2C_201615:34
banixwhich requires updating the neutron network name in the cases where we use existing networks15:34
*** xingchao has quit IRC15:34
apuimedobanix: did you try the new description field?15:34
banixIn my opinion this is reasonable as a stop-gap measure until we have tags in Neutron15:34
banixapuimedo: i thought hat is not there yet but if there will try15:35
gsagiebanix: there is the patch about adding descriptions to neutron objects, which can be used in the meantime as well15:35
gsagieits not merged yet15:35
banixyeah thats what i saw last15:35
gsagiebut it has the chance to be faster then the tags15:35
banixI also played with using a kv store15:35
apuimedobanix: I agree, as long as we change to descriptions/tags in the near future, I'm happy to take it15:35
*** raddaoui has joined #openstack-meeting-415:35
gsagiebanix: probably will be good to also update https://review.openstack.org/#/c/254005/15:35
gsagiethats the spec Taku started15:35
banixwhich works but opens up a whole new set of things to consider15:35
apuimedobanix: if possible, I'd avoid that15:36
banixgsagie: yes i promised to update it but haven’t done so; will do today15:36
*** alexchadin has joined #openstack-meeting-415:36
banixapuimedo: i agree15:36
apuimedobanix: which approach did you go for?15:36
irenabbanix: about the kv store usage, what are your findings?15:36
*** hdaniel has quit IRC15:36
apuimedoschedule a task after returning control to docker that goes and updates kv?15:36
*** hdaniel_ has joined #openstack-meeting-415:36
banixUsing consul as kvstore is rather trivial15:36
banixI suspect other choises wont be much more difficult either15:37
apuimedo(I had thought of doing that for updating neutron name once we have tags descriptions to give nice neutron names to the kuryr created nets15:37
*** alexchadin has left #openstack-meeting-415:37
apuimedo)15:37
irenabbanix: but this adds another dependency15:37
banixi keep the kuryr is and neutron id as a kv  pair in the store15:37
banixirenab: agree15:37
banixand if we want to do it properly need to support various kvstores etc15:38
apuimedobanix: or use something like libkv15:38
apuimedobut that is just Go15:38
apuimedo:/15:38
salv-orlandobanix, irenab: but it seems this is just a stopgap measure until neutron has tugs15:38
irenaband it break the initial goal of being stateless15:38
banixso considering tags are going to be there i thin it is not worth going the kv store path15:38
gsagiebanix: agreed on my part15:39
irenabbanix: +115:39
salv-orlandoso why worry too much. at the end of the day kuryr is still in an experimental phase. I think it's ok to use consul and then throw it away once neutron tags are available15:39
apuimedoI call for a vote15:39
apuimedoon which stopgap measure to go for15:39
salv-orlandounless, of course, there is reasonable certainity that neutron will have tag support in mitaka15:40
*** iyamahat has quit IRC15:40
irenabgsagie: can you update on this?15:40
apuimedothose in favor of "name changing" say name, those in favor of kv say "kv"15:40
banixi believe neutron wont have tags in Mitaka15:40
apuimedobanix: I agree15:40
salv-orlandobanix: I believe that too15:40
irenaband description?15:40
apuimedoI believe there will be description, but I'm an outsider :P15:40
salv-orlandoI am for kv. I don't like mangiling with strings15:40
banixirenab: no description; just flip a coin :)15:40
banixname15:40
gsagieirenab: someone else took the implementation of the spec15:40
gsagiethe spec itself is merged15:41
gsagieI can ask him for the status and update next meeting15:41
*** sivaramakrishna has quit IRC15:41
irenabI am agains the name but see additional burden of kv store15:41
*** sivaramakrishna has joined #openstack-meeting-415:42
apuimedoirenab: I count that as kv15:42
irenabgsagie: yes, please15:42
apuimedogsagie: what's your take?15:42
apuimedofawadkhaliq: you too15:42
irenabapuimedo: not, I prefer avoid the vote :-)15:42
apuimedoirenab: too late :P15:42
gsagieapuimedo: i think we need to talk with the person that is going to use it15:43
fawadkhaliqapuimedo: kv is lessy hacky15:43
gsagieif the name change is fine15:43
irenabI count on banix to make the best choice15:43
fawadkhaliqirenab: +115:43
gsagielets keep it simple until we have tags or description15:43
banixirenab:  thought you had better judgement :)15:43
gsagiei feel that the description could be merged soon15:43
apuimedook15:43
apuimedoname*15:44
banixlet me checkout the description patch and see where we can go from there15:44
irenabI do not want kuryr to modify something that user defines, but as a temporary solution probably ok15:44
apuimedo#action: banix to work on using name to have it working like right now15:44
apuimedo#action: banix to continue investigation of replacing it with description/tags/kv for release time15:45
gsagiei dont mind either solution banix picks :) they are the main first user of this anyway15:45
apuimedois that right?15:45
apuimedoI mean, the action points?15:45
banixsounds good15:45
irenabbanix: I beleive in you :-)15:45
gsagiesounds good to me15:45
gsagiewe all do :)15:45
apuimedobanix: anything you could use some help with?15:45
*** sivaramakrishna has quit IRC15:46
*** Sukhdev has joined #openstack-meeting-415:46
banixno, I am good15:46
apuimedovery well :-)15:46
apuimedo#topic Packaging15:46
*** openstack changes topic to "Packaging (Meeting topic: kuryr)"15:46
apuimedoI was not able to move it last week unfortunately15:46
apuimedobut I believe this week I'll be able to get the rdo one ready15:46
apuimedo#link https://github.com/celebdor/rdo-kuryr15:47
*** numans has quit IRC15:47
apuimedoobviously it is not in the kuryr repo15:47
*** sivaramakrishna has joined #openstack-meeting-415:47
apuimedoit should end up living on https://github.com/openstack-packages/kuryr15:47
apuimedo#link https://github.com/openstack-packages/kuryr15:47
gsagiecool15:47
apuimedoNote that the packaging is a bit ambitious and it uses the CAP_NET_ADMIN hack not to run as root15:48
*** SimonChung1 has quit IRC15:48
apuimedoso probably I'll have to patch the binding scripts not to drop the privilege15:48
apuimedoany questions about the packaging?15:48
*** sivaramakrishna has quit IRC15:49
apuimedo(besides, when will you finish, darn it?!15:49
apuimedo)15:49
gsagieany progress on the Kolla+OVS ?15:49
gsagiedont know if its related15:49
banixI saw the blueprint for Kola integration was pushed out of Mitaka, Hui Do you have any updates?15:49
HuiHI15:49
apuimedoI have some work on containerization15:49
*** sivaramakrishna has joined #openstack-meeting-415:49
apuimedo#link https://review.openstack.org/#/c/279320/15:49
HuiIf kuryr requires consul, we need add consul to kolla first.15:50
*** armax has joined #openstack-meeting-415:50
apuimedoHui: are you starting from there or is there somewhere else we could look at?15:50
HuiI have some old patch in kolla, but has not merged15:50
apuimedoHui: so far we don't need consul :P15:50
Huiok, i see15:50
apuimedoHui: can we get a link for that?15:50
apuimedoHui: does kolla have etcd?15:50
banixapuimedo: we need a kv store for docker irtself15:50
Huino etcd in kolla15:50
apuimedowe need either consul, etcd or zk15:50
apuimedoHui: banix: which do you think is easier to add?15:51
HuiI prefer consul as we have some existing work on it15:51
apuimedoconsul clusters easier15:51
irenabguys, any spec/doc/launchpad on this task?15:51
apuimedoHui: ok, go for it!15:51
Huibut etcd should also be straitforward15:51
Huisure, let me add that to the kolla bp15:51
*** julim has quit IRC15:51
irenablink can be helpful15:51
Huihttps://blueprints.launchpad.net/kolla/+spec/kuryr-docker-plugin15:52
apuimedo#link https://blueprints.launchpad.net/kolla/+spec/kuryr-docker-plugin15:52
irenabHui: thanks15:52
Huimy pleasure15:52
apuimedo#topic Rally and fullstack integration15:52
*** openstack changes topic to "Rally and fullstack integration (Meeting topic: kuryr)"15:53
*** yifei has quit IRC15:53
apuimedogsagie: are you taking this point? (got only 4 minutes)15:53
*** julim has joined #openstack-meeting-415:53
gsagieBaohua is working on this15:53
gsagiehttps://review.openstack.org/#/c/265105/15:53
*** yifei has joined #openstack-meeting-415:53
apuimedo#link https://review.openstack.org/#/c/265105/15:53
gsagiekeeps failing for testing containers15:53
gsagiewill need to check it15:53
apuimedo#action apuimedo review https://review.openstack.org/#/c/265105/15:53
gsagiedont know if the problems are related to the python client15:54
apuimedo#action gsagie to check the patch to try to dig out the issues15:54
gsagieor to the use15:54
gsagiek15:54
apuimedoany other thing about rally?15:54
gsagienot at this point15:54
gsagieonce we get this working we can add more rally tests15:54
apuimedo#info: as we start implementing specs (like re-using neutron nets) please, add integration tests15:55
apuimedoright!15:55
apuimedo#topic community and other topics15:55
*** openstack changes topic to "community and other topics (Meeting topic: kuryr)"15:55
*** javeriak has joined #openstack-meeting-415:55
gsagiehttp://ons2016.sched.org/event/67nA/container-based-dynamic-service-chain-using-distributed-sdn-pipeline-injection-openstack-dragonflow-kuryr-eshed-gal-or-huawei?iframe=yes&w=&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no15:55
apuimedo#link http://ons2016.sched.org/event/67nA/container-based-dynamic-service-chain-using-distributed-sdn-pipeline-injection-openstack-dragonflow-kuryr-eshed-gal-or-huawei?iframe=yes&w=&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no15:55
gsagiefor the people going to the bay area :)15:56
gsagiefor ONS15:56
*** yifei has quit IRC15:56
apuimedothere is going to be a kuryr talk in the bay area :-)15:56
apuimedowe have to cover the globe all the way down to Milwaukee15:56
apuimedo:-)15:56
*** zeih has quit IRC15:56
*** yifei has joined #openstack-meeting-415:56
apuimedoanybody else has other news or questions?15:57
*** angdraug has joined #openstack-meeting-415:57
irenabapuimedo:  I think maybe for next meetings there should be some bug overview at agenda15:57
*** zeih has joined #openstack-meeting-415:57
banixirenab: excellent point!15:57
*** alexchadin has joined #openstack-meeting-415:58
irenabpeople can add links and ask for review15:58
apuimedo#action gsagie apuimedo to add to the next meeting agenda bug scrubbing15:58
apuimedomost likely gsagie since I always forget about writing the agenda down :P15:58
apuimedonice idea!15:59
banixwe need to review bgs on launchpad, assign level, etc15:59
apuimedoyes15:59
banixi did some a couple of weeks ago15:59
apuimedomaybe we could rotate it among the cores every week15:59
apuimedothe bug scrubbing15:59
*** bgmccollum has left #openstack-meeting-415:59
banixyup15:59
fawadkhaliqapuimedo gsagie let me know if you guys need help with that. Will be happy to help.16:00
*** salv-orl_ has joined #openstack-meeting-416:00
irenab+116:00
banixSukhdev: must be behind the door :) out of time16:00
apuimedofawadkhaliq: oh yes, sorry. I didn't mean to close it down to the cores16:00
fawadkhaliqbanix: lol16:00
Sukhdevbanix : I am here - waiting :-)16:00
apuimedohere we're all in the same standing :-)16:00
apuimedo#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Mon Feb 29 16:01:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
salv-orl_adieuuu16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-02-29-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-02-29-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-02-29-15.01.log.html16:01
apuimedoThanks all for joining!16:01
fawadkhaliqbyee16:01
irenabbye16:01
banixbye16:01
*** alexchadin has quit IRC16:01
SukhdevFolks time for Ironic-neutron meeting16:01
Sukhdev#startmeeting ironic_neutron16:01
openstackMeeting started Mon Feb 29 16:01:51 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
davidlenwello/16:02
sambettso/16:02
Sukhdev#topic: Agenda16:02
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:02
*** Hui has quit IRC16:02
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_February_29.2C_201616:02
SukhdevWelcome to ironic-neutron meeting16:02
SukhdevFeel free to add to the agenda16:02
Sukhdev#topic: Announcements16:03
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:03
*** salv-orlando has quit IRC16:03
SukhdevHappy 29th Feb16:03
*** alexchadin has joined #openstack-meeting-416:03
SukhdevAnybody has any announcement?16:03
*** nkrinner has quit IRC16:03
Sukhdevjroll : are you here?16:04
jrollmorning :)16:04
*** alexchadin has quit IRC16:04
Sukhdevdevananda : are you here ?16:04
Sukhdev#topic: Patches Updates16:05
*** openstack changes topic to ": Patches Updates (Meeting topic: ironic_neutron)"16:05
devanandaSukhdev: o/16:05
Sukhdev#link: https://etherpad.openstack.org/p/ironic-neutron-mid-cycle16:05
Sukhdevdevananda, jroll: want to share any update on the patch refactoring?16:06
jrollSukhdev: it's well underway, not quite finished yet unfortunately16:06
Sukhdevjroll: cool - we have some time still16:07
Sukhdevlet me know when ready  - I will give it a spin16:07
SukhdevI am in the middle of setting up my automated test setup16:07
jrollcool16:08
jrollshould be this week16:08
SukhdevBTW, I tested latest versions of patches as of last Tuesday - all looks good so far16:08
Sukhdevcouple of patches have some minor comments  - I paced +1's on others16:08
SukhdevEverybody please keep the etherpad updated with all the issues, patch updates, etc...16:09
Sukhdevthis gives us one stop to check everything16:10
jrollgood point16:10
* jroll updates16:10
sivaramakrishnaSukhdev: which mech driver did you use.. did you use generic plugin?16:10
Sukhdevsivaramakrishna : I use Arista ML2 driver, along with all the patches listed on etherpad16:11
sivaramakrishnawhich etherpad.. the mid cycle one?16:11
Sukhdevsivaramakrishna : https://etherpad.openstack.org/p/ironic-neutron-mid-cycle16:11
sivaramakrishnaoh,ok.. is your code anywhere upstream?16:11
sivaramakrishnaI was using the generic plugin16:12
Sukhdevsivaramakrishna : yes it is on netwroking-arista repo16:12
Sukhdevnetworking-arista16:12
*** hdaniel_ has quit IRC16:12
*** zeih has quit IRC16:13
Sukhdevanything else on the patches?16:13
*** sivaramakrishna has quit IRC16:13
Sukhdevdevananda : how's your testing/setup coming along?16:13
*** sivaramakrishna has joined #openstack-meeting-416:14
sivaramakrishnagot disconnected..16:14
Sukhdev#topic: Vlan aware BMs16:15
*** openstack changes topic to ": Vlan aware BMs (Meeting topic: ironic_neutron)"16:15
Sukhdevlink: https://review.openstack.org/#/c/277853/216:15
devanandaSukhdev: I've been busy working on the infrastructure setup for that testing, but it's not up yet16:15
Sukhdevdevananda : were you able to get the right switches, etc..16:15
Sukhdevdevananda : ping me off-line, if you still need any help16:16
devanandaSukhdev: will do16:16
Sukhdevsambetts : I added this topic to the agenda -16:16
devanandawe found some switches with HW VTEP support, but unclear yet about which ML2 plugin we'll need to use with them16:16
*** fawadkhaliq has quit IRC16:17
*** pcaruana has quit IRC16:17
Sukhdevdevananda : mestery is working with you, right? I gave him some pointers as to how to test with OVN16:18
devanandayep16:18
*** banix has quit IRC16:19
SukhdevI have not tested ironic integration with OVN, but, used L2GW with OVSDB setup -16:19
Sukhdevit should be similar - with some work, you should be able to test this interface -16:19
Sukhdevwhen you are ready, ping me if you need any help16:20
*** neelashah has quit IRC16:20
Sukhdevgetting back to the topic (sorry) -16:21
*** gsagie has left #openstack-meeting-416:21
Sukhdevsambetts: wanted to chat about your patch16:21
mesterySukhdev: I have your email, once we get to that point, I'm going to try it16:21
sambettsSukhdev: sure :)16:21
Sukhdevmestery : cool - you know where to find me :-)16:21
Sukhdevsambetts : I left some comments on your patch16:22
mesteryI do Sukhdev ;)16:22
Sukhdevsambetts : one thing is not clear  - i.e. the plumbing of sub-ports on neutron side -16:22
sambettsSukhdev: yes, so the spec right now doesn't intergrate with the VLAN aware VMs work / trunk port work going on in neutron16:23
Sukhdevsambetts : do you have any thought as to how that integration will work?16:24
*** belmoreira has quit IRC16:24
*** banix has joined #openstack-meeting-416:24
*** sigmavirus24 is now known as sigmavirus24_awa16:25
sambettsSukhdev: I've had some thoughts, and the way I think it'll most likely work is a user requests normal nic interfaces on nova boot using the --nic parameter, and then Ironic creates the trunk port16:25
sambettsand then links the nova created ports to the trunk port16:25
*** prashantD has joined #openstack-meeting-416:25
*** sigmavirus24_awa is now known as sigmavirus2416:25
sambettsbut we've implemented this functionality downstream without the trunk support in neutron by making our BM ml2 driver do something slightly different16:26
sambettsthe switch port is always a trunk port, and then on the first port update it binds native and the allowed vlan, then on second or more port updates with the same switch port in the local link it will only update the allowed list16:27
Sukhdevnova will create one port based upon the parameters to boot command - who will orchestrate the create of the subsequent ports?16:28
sambettsSukhdev: with my changes you send multiple --nics to nova16:29
Sukhdevoh - I see - does nova allow that - or you have hacked it in your implementation?16:29
sambettsnova boot --nic net-id=net1 --nic net-id=net2216:29
jrollnova allows it16:29
sambettsbuilt into nvoa16:30
sambettsnova16:30
Sukhdevah cool - then it is easy -16:30
Sukhdevso, nova will issue the create_port() or ironic?16:31
sambettsnova16:32
*** apuimedo has quit IRC16:32
sambettsthen Ironic just uses the ports that nova creates16:32
SukhdevI guess then is fairly straightforward -16:32
sambettsyeah, I've got it working downstream with ~200 lines of code in Ironic and Nova on top of the existing Ironic Neutron intergration16:33
Sukhdevso, at the time of time network flip, ironic conductor will issue multiple port-updates, right?16:33
sambettsSukhdev: yup16:33
*** neelashah has joined #openstack-meeting-416:33
sambettsSukhdev: https://review.openstack.org/#/c/282431/16:34
Sukhdevsambetts : cool - got it....16:34
*** xingchao has joined #openstack-meeting-416:34
Sukhdevyuriy is not here -16:35
SukhdevI thought we could discuss about the tempest testing that he has been working on16:36
Sukhdevanybody tested the his patch?16:36
sambettsSukhdev: not yet, still working on setting up my test bed16:36
Sukhdevsambetts : cool - thanks16:37
*** alexchadin has joined #openstack-meeting-416:37
*** dingboopt has quit IRC16:37
Sukhdevsambetts : which ML2 driver are you using for your testing?16:38
sambettsSukhdev: cisco nexus16:38
sambettsSukhdev: although it still needs work16:39
Sukhdevso, you are using the driver for both VMs and BMs, right?16:39
sambettsSukhdev: yup, we've extending the driver to accept the BM type16:40
*** xingchao has quit IRC16:40
sambettsextended*16:40
Sukhdevmakes sense - same here....it makes much easier for the customers/operators16:40
sambettsYup :D16:40
Sukhdev#topic: Open Discussion16:41
*** openstack changes topic to ": Open Discussion (Meeting topic: ironic_neutron)"16:41
SukhdevAny body wants to discuss anything?16:42
Sukhdevas I am done with the main agenda16:42
sivaramakrishnaa question..16:42
sivaramakrishnawhen you use 2 nics16:42
sambettsI've got a patch into Glean to help support multiple in-band vlans configured via config drive https://review.openstack.org/#/c/283726/16:43
sivaramakrishnahow are setting up any routes so that the tenant dhcp request gets answered?16:43
*** prithiv has quit IRC16:43
*** thorst is now known as thorst_afk16:44
sivaramakrishnadid anyone test using 2 nics?16:44
*** klindgren has quit IRC16:44
SukhdevI have tested with single nic only16:44
Sukhdevsivaramakrishna: you want to connect two nics to the same network?16:45
sivaramakrishnanope16:45
sambettssivaramakrishna: I've used multiple nics on different neutron networks, and it just works16:45
sivaramakrishnaokay great.. and you were able to ssh into it right?16:45
Sukhdevtwo different networks is always supported (even for VMS)16:46
sivaramakrishnaalso in my devstack sometimes the metadata api doesn't come up at all16:46
sivaramakrishnaand the cloudinit goes for a toss16:46
sivaramakrishnaoh cool..16:46
sivaramakrishnais there any way we can ssh to instance without cloudinit?16:47
sambettssivaramakrishna: it is possible to create an ubuntu image through DIB with a default user installed on the image so you can ssh using username and password instead of relying on ssh key16:48
sivaramakrishnathat would be nice.. do you have any such image16:48
sivaramakrishnaor a link on how to create it?16:48
sambettssivaramakrishna: https://github.com/openstack/diskimage-builder/tree/master/elements/devuser16:49
sambettssivaramakrishna: you need to include this element when you do disk image create16:49
*** paul-carlton2 has quit IRC16:50
sambettssivaramakrishna: and you need to set the Env variables listed in the README there to customise the password and sudo access etc16:50
sivaramakrishnawhich element?16:50
sambettsthe one I linked to, devuser16:50
sivaramakrishnaah ok..16:51
sivaramakrishnaand I can set the env vars and I should be able to create the image?16:51
sambettsso it would be like, disk-image-create ubuntu baremetal dhcp-all-interfaces devuser16:51
sambettsyup16:51
sivaramakrishnagreat.. thanks!16:51
sivaramakrishnalet me know if you already have any such image.16:52
*** raddaoui has quit IRC16:52
sivaramakrishnaI'll try to create one though.. I haven't tried this yet16:52
sivaramakrishnawhat I did was tried to mount a qcow216:53
sivaramakrishnaand changed the password16:53
sivaramakrishnaand then tried deploying it16:53
sivaramakrishnait didn't work..16:53
*** raddaoui has joined #openstack-meeting-416:53
sambettssivaramakrishna: I've used that method several times recently to debug config drive work16:53
sambettssivaramakrishna: it works well :)16:54
sivaramakrishnaokay.. thanks a bunch!!16:54
*** prithiv has joined #openstack-meeting-416:54
sivaramakrishnawill try that..16:54
sivaramakrishna:)16:54
*** yamamoto_ has quit IRC16:54
Sukhdevtime check - 6 min16:54
SukhdevAnything else?16:55
* jroll is good16:55
*** yamamoto has joined #openstack-meeting-416:55
* Sukhdev waiting16:55
Sukhdevgoing once16:55
Sukhdevgoing twice16:56
Sukhdevand.....16:56
Sukhdevand...16:56
Sukhdevgone!!!16:56
Sukhdevthanks folks16:56
sambettsThanks everyone :D16:56
Sukhdevit was a good meeting16:56
sivaramakrishnathanks a lot everyone!!16:56
Sukhdevby16:56
Sukhdevbye16:56
jrollthanks all16:56
sivaramakrishnabye! :-)16:56
Sukhdev#endmeeting16:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:56
openstackMeeting ended Mon Feb 29 16:56:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-02-29-16.01.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-02-29-16.01.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-02-29-16.01.log.html16:56
*** matrohon has quit IRC16:57
*** sivaramakrishna has left #openstack-meeting-416:57
*** alexchadin has quit IRC17:00
SukhdevFolks, time for L2GW meeting17:01
*** neelashah has quit IRC17:02
*** Jeffrey4l has quit IRC17:03
SukhdevAnybody here for L2GW meeting?17:03
*** yamahata has joined #openstack-meeting-417:04
SukhdevLooks like no body here - so, I am going to cancel the L2GW meeting this week17:05
*** neelashah has joined #openstack-meeting-417:05
*** sdake has joined #openstack-meeting-417:06
*** yamamoto has quit IRC17:10
*** dslevin has joined #openstack-meeting-417:11
*** dslevin has quit IRC17:11
*** dslevin has joined #openstack-meeting-417:11
*** dslevin has quit IRC17:12
*** amotoki has quit IRC17:13
*** dslevin has joined #openstack-meeting-417:13
*** paul-carlton2 has joined #openstack-meeting-417:13
*** jmckind has quit IRC17:14
*** bobh has quit IRC17:14
*** sridhar_ram has joined #openstack-meeting-417:14
*** prithiv has quit IRC17:16
*** cemmason has joined #openstack-meeting-417:18
*** evgenyf has joined #openstack-meeting-417:21
*** sdake has quit IRC17:22
*** sdake has joined #openstack-meeting-417:23
*** blakec has joined #openstack-meeting-417:23
*** sigmavirus24 is now known as sigmavirus24_awa17:26
*** blakec has left #openstack-meeting-417:27
*** uck has joined #openstack-meeting-417:28
*** lakshmiS has joined #openstack-meeting-417:29
*** david-lyle has joined #openstack-meeting-417:30
*** degorenko is now known as _degorenko|afk17:33
*** xingchao has joined #openstack-meeting-417:36
*** fawadkhaliq has joined #openstack-meeting-417:36
*** SimonChung has joined #openstack-meeting-417:38
*** xingchao has quit IRC17:41
*** fjvicens has quit IRC17:42
*** mbound has quit IRC17:44
*** ihrachys has quit IRC17:45
*** rbradfor_ is now known as rbradfor17:49
*** ajmiller has quit IRC17:50
*** bobh has joined #openstack-meeting-417:51
*** ajmiller has joined #openstack-meeting-417:52
*** sdake has quit IRC17:54
*** david-lyle has quit IRC17:55
*** david-lyle_ has joined #openstack-meeting-417:55
*** sdake has joined #openstack-meeting-417:57
*** krtaylor has quit IRC17:59
*** Guest67703 is now known as me_18:01
*** me_ is now known as med_18:01
*** med_ has quit IRC18:01
*** med_ has joined #openstack-meeting-418:01
*** baoli has quit IRC18:01
*** baoli has joined #openstack-meeting-418:03
*** baoli has quit IRC18:03
*** sridhar_ram1 has joined #openstack-meeting-418:05
*** dane_leblanc has quit IRC18:06
*** sridhar_ram has quit IRC18:07
*** bobh has quit IRC18:08
*** sarob has joined #openstack-meeting-418:09
*** matrohon has joined #openstack-meeting-418:10
*** baoli has joined #openstack-meeting-418:10
*** krtaylor has joined #openstack-meeting-418:11
*** Swami has joined #openstack-meeting-418:14
*** raddaoui has quit IRC18:15
*** yamamoto has joined #openstack-meeting-418:16
*** lakshmiS_ has joined #openstack-meeting-418:19
*** baoli_ has joined #openstack-meeting-418:19
*** lakshmiS has quit IRC18:21
*** yamamoto has quit IRC18:21
*** baoli has quit IRC18:22
*** thorst_afk is now known as thorst18:23
*** Guest63721 is now known as mfisch18:24
*** mfisch is now known as Guest200418:25
*** krtaylor has quit IRC18:27
*** Guest2004 is now known as mfisch18:28
*** mfisch has quit IRC18:28
*** mfisch has joined #openstack-meeting-418:28
*** bpokorny has joined #openstack-meeting-418:28
*** baoli_ has quit IRC18:29
*** baoli has joined #openstack-meeting-418:31
*** thorst is now known as thorst_afk18:31
*** sridhar_ram1 is now known as sridhar_ram18:34
*** paul-carlton2 has quit IRC18:36
*** xingchao has joined #openstack-meeting-418:37
*** cloudtrainme has joined #openstack-meeting-418:37
*** emagana has joined #openstack-meeting-418:38
*** krtaylor has joined #openstack-meeting-418:39
*** baoli has quit IRC18:42
*** evgenyf has quit IRC18:42
*** sdake has quit IRC18:43
*** xingchao has quit IRC18:43
*** baoli has joined #openstack-meeting-418:44
*** angdraug has quit IRC18:45
*** Sukhdev has quit IRC18:45
*** baoli has quit IRC18:52
*** thorst_afk is now known as thorst18:52
*** sigmavirus24_awa is now known as sigmavirus2418:53
*** spzala has joined #openstack-meeting-418:53
*** baoli has joined #openstack-meeting-418:54
*** baoli has quit IRC18:55
*** neelashah has quit IRC18:55
*** lakshmiS_ has quit IRC18:57
*** izaakk has quit IRC18:57
*** baoli has joined #openstack-meeting-418:58
*** fnaval_ has joined #openstack-meeting-418:58
*** andymaier has quit IRC18:59
*** jmckind has joined #openstack-meeting-418:59
*** delattec has joined #openstack-meeting-419:00
*** delattec has quit IRC19:00
*** rockyg has joined #openstack-meeting-419:01
*** fnaval has quit IRC19:01
*** neelashah has joined #openstack-meeting-419:02
*** cdelatte has quit IRC19:03
*** fnaval_ has quit IRC19:03
*** fnaval has joined #openstack-meeting-419:04
*** julim has quit IRC19:07
*** myatsenko has quit IRC19:07
*** neelashah has quit IRC19:09
*** julim has joined #openstack-meeting-419:10
*** neelashah has joined #openstack-meeting-419:10
*** dims_ has joined #openstack-meeting-419:11
*** dims has quit IRC19:11
*** angdraug has joined #openstack-meeting-419:13
*** raddaoui has joined #openstack-meeting-419:15
*** harshs has joined #openstack-meeting-419:16
*** baoli has quit IRC19:18
*** baoli has joined #openstack-meeting-419:18
*** ihrachys has joined #openstack-meeting-419:20
*** cdelatte has joined #openstack-meeting-419:22
*** baoli has quit IRC19:23
*** baoli has joined #openstack-meeting-419:23
*** baoli has quit IRC19:26
*** hdaniel_ has joined #openstack-meeting-419:27
*** javeriak_ has joined #openstack-meeting-419:28
*** javeriak_ has quit IRC19:28
*** raddaoui has quit IRC19:30
*** javeriak has quit IRC19:32
*** IlyaG has joined #openstack-meeting-419:34
*** IlyaG has quit IRC19:34
*** raddaoui has joined #openstack-meeting-419:34
*** sambetts is now known as sambetts|afk19:36
*** baoli has joined #openstack-meeting-419:39
*** hdaniel_ is now known as hdaniel19:43
*** banix has quit IRC19:43
*** ihrachys has quit IRC19:44
*** evgenyf has joined #openstack-meeting-419:44
*** MarkAtwood1 has joined #openstack-meeting-419:50
*** reedip has quit IRC19:51
*** MarkAtwood1 has quit IRC19:51
*** MarkAtwood has quit IRC19:51
*** banix has joined #openstack-meeting-419:57
*** dims_ has quit IRC19:58
*** armax has quit IRC19:59
*** spzala has quit IRC19:59
*** baoli has quit IRC20:02
*** neelashah has quit IRC20:02
*** cemmason1 has joined #openstack-meeting-420:03
*** cemmason has quit IRC20:04
*** sdake has joined #openstack-meeting-420:04
*** neelashah has joined #openstack-meeting-420:07
*** dtardivel has quit IRC20:08
*** mbound has joined #openstack-meeting-420:11
*** angdraug has quit IRC20:11
*** dims has joined #openstack-meeting-420:12
*** s3wong has joined #openstack-meeting-420:12
*** david-lyle_ is now known as david-lyle20:12
*** banix has quit IRC20:16
*** yamahata has quit IRC20:18
*** sdake has quit IRC20:22
*** fawadkhaliq has quit IRC20:22
*** sshnaidm has quit IRC20:22
*** banix has joined #openstack-meeting-420:27
*** dims has quit IRC20:29
*** sshnaidm has joined #openstack-meeting-420:32
*** raddaoui has quit IRC20:34
*** cemmason1 has quit IRC20:35
*** cemmason has joined #openstack-meeting-420:35
*** salv-orlando has joined #openstack-meeting-420:36
*** mfedosin has quit IRC20:37
*** salv-orl_ has quit IRC20:39
*** cemmason has quit IRC20:40
*** Sukhdev has joined #openstack-meeting-420:40
*** neelashah1 has joined #openstack-meeting-420:40
*** cemmason has joined #openstack-meeting-420:40
*** neelashah has quit IRC20:43
*** fnaval has quit IRC20:43
*** fnaval has joined #openstack-meeting-420:44
*** baoli has joined #openstack-meeting-420:47
*** cemmason has quit IRC20:47
*** cemmason has joined #openstack-meeting-420:47
*** baoli has quit IRC20:48
*** baoli has joined #openstack-meeting-420:48
*** itisha has quit IRC20:49
*** neelashah has joined #openstack-meeting-420:52
*** neelashah1 has quit IRC20:52
*** britthou_ has quit IRC20:54
*** IlyaG has joined #openstack-meeting-420:54
*** Sukhdev has quit IRC20:55
*** IlyaG has quit IRC20:57
*** harshs has quit IRC20:57
*** angdraug has joined #openstack-meeting-420:59
*** mriedem has joined #openstack-meeting-420:59
mriedem#startmeeting stable21:00
openstackMeeting started Mon Feb 29 21:00:22 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
mriedem#link agenda https://wiki.openstack.org/wiki/Meetings/StableTeam21:00
mriedemwho's all around?21:00
*** harshs has joined #openstack-meeting-421:01
*** neelashah1 has joined #openstack-meeting-421:01
mriedemmtreinish: tonyb: ttx: mrunge: ping21:01
tonybo/21:01
mriedemflaper87: jokke_: ping21:01
tonybGah I was in meeting-3 bad IRC client!21:01
mriedemmoves week to week21:01
mriedemwhich is confusing21:01
mriedemlet's get started21:02
mriedem#topic status21:02
flaper87o/21:02
*** openstack changes topic to "status (Meeting topic: stable)"21:02
mriedemi've been watching the periodic-stable ML21:02
*** prithiv has joined #openstack-meeting-421:02
mriedemfixed some issues in glance last week21:02
mriedemironic and some other projects had fallout from an oslo.config release too21:02
mriedemironic is fixed21:02
jokke_mriedem: pong21:03
mriedemmurano and ceilometer also had issues21:03
* mtreinish is about to step away for a very late lunch21:03
*** neelashah has quit IRC21:03
mriedemthe trakcing bug was https://bugs.launchpad.net/oslo.config/+bug/154761221:03
openstackLaunchpad bug 1547612 in Ceilometer "AttributeError: 'NoneType' object has no attribute '_config_dirs'" [Medium,Triaged]21:03
mriedemlooks like murano and ceilometer are on there now21:03
*** breton has joined #openstack-meeting-421:03
mriedem#link stable issues tracker https://etherpad.openstack.org/p/stable-tracker21:04
tonybmriedem: Thanks.  I've been keeping the failure logs for looking at but ....21:04
mriedemsahara pep8 fixes are finally in21:04
mriedemksm g-r sync for kilo is also in21:04
tonyb\o/21:04
tonybthat was much harder than it shoudl have ben21:05
mriedemthat took some manual updating by bknudson, looks like the g-r sync bot isn't applying changes to *requirements-py3.txt on stable21:05
tonybmriedem: can we fix that?21:05
*** lakshmiS has joined #openstack-meeting-421:05
mriedemi'm assuming b/c i thought the -py3 files were removed in master21:05
mriedemtonyb: probably?21:05
mriedemi never reported a bug21:05
mriedemthis was the ksm review: https://review.openstack.org/#/c/277022/21:05
*** uck has quit IRC21:06
tonybmriedem: Thanks21:06
tonybbrb21:06
mriedemanyway, it's probably worth digging through git log on the requirements repo to see if the py3 thing was intentionally dropped21:06
mriedembut it's lower priority21:06
tonyb.21:06
mriedemlifeless might also know off the top of his head21:07
tonybmriedem: yeah21:07
mriedem#topic action items from previous meeting21:07
*** openstack changes topic to "action items from previous meeting (Meeting topic: stable)"21:07
mriedemtonyb to talk to lifeless about fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/154298421:07
openstackLaunchpad bug 1542984 in Python Fixtures "fixtures 1.2.0 isn't compatible with testtools 2.0.0" [Undecided,New]21:07
mriedemi didn't see any updates in the bug21:07
mriedemlast i looked the neutron kilo patch was still failing in weird ways21:07
mriedemeven though ihar capped testtools in stable/kilo g-r21:07
mriedem2.0.0 was getting used21:08
*** salv-orlando has quit IRC21:08
tonybmriedem: Yeah and an unpatched job passes, so there is somethign moer to it that I haven't been able to find.21:08
tonybI'ev asked lifless to either do ther release or close the bug21:08
*** salv-orlando has joined #openstack-meeting-421:09
mriedemoh i see https://review.openstack.org/#/c/282146/21:09
tonybI feel like we can't progress alternate approaches until we have that decision made21:09
tonybYeah and I have a WiP patch for oslo.concurency to do the capping there too21:09
bknudsonI hope stable/kilo goes away soon.21:09
*** baoli_ has joined #openstack-meeting-421:10
mriedemi can ping lifeless on the bug again21:10
*** minwang2 has joined #openstack-meeting-421:10
tonybmriedem: https://review.openstack.org/#/c/282123/ is the one that passes the -api tests without any kind of cap21:10
mriedem#action mriedem to ping lifeless about fixtures bug https://bugs.launchpad.net/python-fixtures/+bug/1542984 21:10
openstackLaunchpad bug 1542984 in Python Fixtures "fixtures 1.2.0 isn't compatible with testtools 2.0.0" [Undecided,New]21:10
*** neelashah has joined #openstack-meeting-421:10
tonybmriedem: which just doesn't make sense to me21:10
tonybmriedem: that'd be cool21:10
tonybmriedem: I just did it in #openstack-infra21:10
*** baoli_ has quit IRC21:10
mriedemok, i was trying to unwind some of the neutron job setup b/c there could be something weird in there21:11
mriedemi know you patched devstack on kilo to workaround it21:11
rockygo/21:11
tonybmriedem: right that works for devstack21:11
mriedemi'm guessing maybe something like that is needed in neutron stable/kilo functional script or something21:11
tonybbut the -api and neitron-neutron jobs run up a new tox env ontop of the dsvm and then get the wrong testtools21:12
tonybmriedem: Yeah I looked at that approch rather than https://review.openstack.org/#/c/282146/21:12
tonybbut I couldn't find anytthing that worked well21:13
*** baoli_ has joined #openstack-meeting-421:13
tonybotehr than a just addeding "pip install -U testtools<=2.0.0" in the post-gate-hoo21:13
tonybk21:13
mriedemhmm, that failed the LB test21:13
*** neelashah1 has quit IRC21:13
mriedemwhich i think there is another kilo patch backport for nova related to that21:13
rockygbknudson, stable/kilo dies in June???21:14
*** baoli has quit IRC21:14
mriedemtonyb: anyway, we should probably try to capture some of this in the stable-tracker etherpad,21:14
mriedemsince it's pretty sparse on the latest changes / attempts21:14
tonybmriedem: Yeah I've done a terrible job of that.21:14
mriedemrockyg: re: kilo, the releases docs say (EOL: 2016-05-02)21:15
mriedemhttp://releases.openstack.org/21:15
mriedemthere was another action item from last week21:15
mriedembknudson to propose dropping upper-constraints from stable/kilo to see if the reqs job will work without it21:15
rockygmriedem, even better.  In some ways.21:15
mriedemthat was already sorted out, and we've already talked about it (the py3 thing)21:15
bknudsonmriedem: I did that21:15
mriedemyup21:16
*** bpokorny has quit IRC21:16
mriedem#topic release news21:16
*** openstack changes topic to "release news (Meeting topic: stable)"21:16
mriedemjust a reminder to be reviewing stable/liberty things and consider a release sometime soonish to line up with m-321:16
bknudsonsupposedly there will be no more features in oslo libs21:16
mriedem#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/086362.html21:16
bknudsonso we'll have stable branches sometime.21:16
mriedembknudson: ?21:16
bknudsonthe final releases of non-client libs is past21:17
mriedemi'm assuming that's the bknudson dry humor?21:17
mriedemah21:17
bknudsony, just for mitaka, not all time21:17
mriedemwell, oslo.config managed to break stable/liberty last week for 3 projects21:17
mriedembut sure21:17
rockygoslo libs are frozen except for critical bugfixes21:18
bknudsonso if we're still going to do stable releases for libs there will be stable branch21:18
mriedembknudson: yeah21:18
tonybmriedem: right but that's linked to the u-c mistakes we made on liberty that hopefully we won't do again on mitaka21:18
mriedemtonyb: sort of...21:19
*** cloudtrainme has quit IRC21:19
mriedem#topic stuck reviews21:19
*** openstack changes topic to "stuck reviews (Meeting topic: stable)"21:19
mriedemthere was nothing on the agenda, did anyone have something for this?21:19
tonybmriedem: there are a couple of nova ones but we can talk about that later if you prefer.  Possibly best at a nova meeting21:20
mriedemthere was a largeish nova backport for an rbd thing21:20
mriedembut that merged21:20
*** lakshmiS_ has joined #openstack-meeting-421:20
mriedemhttps://review.openstack.org/#/c/228505/21:20
mriedemtonyb: yeah21:20
mriedem#topic tooling21:20
*** openstack changes topic to "tooling (Meeting topic: stable)"21:20
mriedemthere isn't any news here21:20
mriedemi haven't had a chance to work on this21:21
*** cbouch has joined #openstack-meeting-421:21
*** cloudtrainme has joined #openstack-meeting-421:21
mriedemwell, specifically, "script to check for backport-potential bugs which are fixed on trunk but backports are not yet proposed"21:21
tonybmriedem: Ooooo I have one of those21:21
mriedemrockyg: if you have devs that are looking for things to hack on, ^ would be one21:21
tonybI wrote it last week21:21
mriedemtonyb: for that one?21:21
tonybit need to be cleaned up21:21
mriedemok, cool21:22
mriedemi'm not sure what repo these go in, maybe release-tools21:22
tonybmriedem: It looks at all the fixed* bugs in LP with a librty-backport-potential tag21:22
tonyband then checks to see if there is an review for that on liberty21:22
tonybmriedem: that's kinda what you wanted right?21:22
mriedemyeah21:22
mriedembasically21:22
*** apuimedo has joined #openstack-meeting-421:22
rockygOK.  I supposedly have one.  I'll see if I can light a fire, mriedem I likely will need to intro him to you guys then you can guide him.21:22
mriedemrockyg: sounds like tonyb already has what i was looking for21:23
*** dims has joined #openstack-meeting-421:23
*** lakshmiS has quit IRC21:23
mriedemtonyb: i'm not very familiar with the launchpad API but it would be cool if we could also scrape those with a specific release propsed, if the tag isn't there21:23
rockygYeah.  Just caught up.  In two meetings :P21:23
tonybmriedem: I ran it on nova tl;dr 3 bugs match that criteria which is somethign I wanted to discuss in open-discussion....21:23
mriedembut it's a good start21:23
rockygstill need to intro him to you guys to get him active.21:23
*** vishwanathj has joined #openstack-meeting-421:24
tonybmriedem: Hmm okay I'll look at adding that.21:24
tonybrockyg: Yeah the more people on #openstack-stable the better :)21:24
mriedemtonyb: would be a good start to just get what you have cleaned up i guess and up for review in release-tools21:24
mriedemi generally add the release to the bug and tag with liberty-backport-potential21:24
mriedemin some projects i can only nominate the bug for a release though, so the tag is always good21:25
tonybmriedem: Yeah I'll do it (adda review) this week21:25
*** hdaniel has quit IRC21:25
mriedem#action tonyb to push up his initial script for scraping backport potential bugs21:25
mriedem#topic open discussion21:25
*** uck has joined #openstack-meeting-421:25
*** openstack changes topic to "open discussion (Meeting topic: stable)"21:25
mriedemi had one thing21:25
mriedem(mriedem): Do we want/need a summit session? I figure there will at least be some overlap with the release and QA teams on how long to keep stable/liberty.21:25
mriedemnow that i look at the releases docs though, liberty is marked as Current stable release, security-supported (EOL: 2016-11-17)21:26
rockygI'd love a summit session.  Get more people aware, up to date, etc.21:26
mriedemwhich is just ~6 months after kilo eol21:26
bknudsonhow many times can we have the same discussion at the sumit?21:26
mriedemrockyg: well, there are at least 2 talk proposals related to stable branch maint21:26
tonybbknudson: the landscape is changing so I think it's a good idea21:26
bknudsonmaybe operators that love using past-eol branches will step up21:27
tonybmriedem: I'd be in favor of it but it'll be hard to get the right people in the room (read PTL/CPLs)21:27
rockygNew project.  If we get people, we could make new policies....like extending liberty if there are hands to make it happen.  and mriedem, Oh.  Okay.21:27
mriedemwell, so far no one new has really stepped up to help out with stable21:27
mriedemtonyb: yeah, i need to chat with dhellmann21:27
tonybmriedem: really (2 talks?) /me will be interested in them21:27
rockygThe one guy I've got is supposed to help with keeping stable more current/working longer21:28
mriedemtonyb: well, they are sort of similar21:28
tonybmriedem: I think sneek it into release/cross-project but I think there shoudl be 45mins to focus on it ...21:28
rockyg++21:28
mriedemyeah, i do see value in re-assessing the support timeline on stable/liberty21:28
mriedem#action mriedem to talk to dhellmann about cross-project discussion for stable/liberty timeline21:29
*** bpokorny has joined #openstack-meeting-421:29
*** lakshmiS_ has quit IRC21:29
*** lakshmiS has joined #openstack-meeting-421:29
mriedemok, tonyb you had something for open discussion?21:29
tonybmriedem: yeah21:29
rockygI also brought up the topic in prod-wg.  Got them up to speed on what ops want/need and how to help.21:29
dhellmannmriedem : seems reasonable as a cross-project session topic, when the tc starts putting that list together21:29
tonybSo we all knwo the bug-smash is comming up21:29
*** yamahata has joined #openstack-meeting-421:29
tonybmy focus is going to be on addressing stuff that's appropriate for stabel but isn't backported21:30
tonybI have 3 bugs for nova.21:30
tonybI wanted to check a coupel of things21:30
tonyb1) is that actually helpful?21:30
*** lakshmiS_ has joined #openstack-meeting-421:30
* mriedem waits for #221:31
mriedemwhen is the great bug smash happening again?21:31
tonyb2) assuming yes do others want to drop me a list of appropriate bugs to look at21:31
mriedemwell for stable it's just a matter of backporting the fixes and reviewing them, right?21:31
*** neelashah has quit IRC21:32
tonybthe bug-smash is a bit of a crap-shoot so I can't make promises but I was hopign to get some attention on stable/liberty befoer we go into phase II support21:32
mriedemin general i think it would be helpful to have a concerted effort to review backports for a given project/release and flush them through21:32
tonybmriedem: 7-9March21:32
mriedemlike this week for stable/liberty21:32
mriedemok, so next week21:33
tonybmriedem: yeah.21:33
*** sgordon has joined #openstack-meeting-421:33
*** cdelatte has quit IRC21:33
mriedemi sort of view this as the stable branch liaisons for each project should be driving this kind of thing21:33
tonybI was thinkign that master will be pretty much closed to anything that isn't a release blocker but stable would be a little more open21:33
rockygI think you can distribute bugs to get fixed to some of the etherpads that look like matches.  Like china is nova and neutron21:34
tonybmriedem: I was hopign that a few of them would read this :)21:34
rockygThen, just be ready to review quickly.21:34
*** lakshmiS has quit IRC21:34
tonybrockyg: yeah that's pretty much the point21:34
mriedemtonyb: so as a run up to next week, are you thinking about running your script on a bunch of projects and posting the results in an etherpad or something?21:35
rockygMaster will be closed for Mitaka, but open for new bugfixes. Might be good to review all fixed bugs that happen during smash and add Backport potential to the ones that should.  Review nightly?21:35
tonybmriedem: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka-Bugs21:36
tonybthat has the nova/liberty stuff21:36
tonybmriedem: I can do it for cinder/neutron as well21:36
mriedemand keystone, and glance...21:37
tonybmriedem: the "challenge" (that you pointed out before) si that we don't fir sure have cores in thos projects on board (yet)21:37
tonybbut at least for nova we have me, mikal and (hopefully you)21:37
bknudsonthere's no bugs in keystone21:37
tonybmriedem: Sure21:37
*** neelashah has joined #openstack-meeting-421:37
bknudsonwe need people to do reviews not post more patches21:37
tonybbknudson: I'll just run my script .....21:37
jokke_tonyb: I'm glance and I will be working again from tomorrow onwards so I will be way more available21:38
tonybbknudson: I hear that.21:38
mriedemi can see value in at least putting bugs in the etherpad for people to do the backports,21:38
rockygThe China folks have recruited heavily for cores for the areas they are targetting21:38
tonybjokke_: is that something (liberty backports) you're interested in?21:39
jokke_I had unexpected month of holidays that bit broke the plans for the start of this year :P21:39
mriedembut there is maybe a separate push for the stable team / CPLs to actually review them21:39
jokke_tonyb: as stable liaison for glance, yes backports are definitely in my interest21:39
tonybjokke_: okay.21:39
tonybjokke_: Thanks.21:39
jokke_tonyb: no no, thank you! ;)21:39
rockygmriedem, ++ for the backports in the etherpads.  Especially if the bug is already on the ehterpad and it gets fixed.21:40
tonybFrankly I'm tryign to turn the bug-smash into somethign *helpful*.  I really don't want to distract21:40
*** dims has quit IRC21:40
tonybbknudson: this keystone bug is tagg with librty-potential but no patch has been proposed: https://bugs.launchpad.net/keystone/+bug/152525021:41
openstackLaunchpad bug 1525250 in OpenStack Identity (keystone) "Failure when federated user name contains non ascii characters" [High,Fix released] - Assigned to Steve Martinelli (stevemar)21:41
*** xingchao has joined #openstack-meeting-421:41
mriedemtonyb: i think that's fine21:41
tonybbknudson: so for keystone it's the only one21:41
*** lakshmiS_ has quit IRC21:41
mriedemhonestly we probably don't have the tag on a lot of bugs,21:42
mriedembugs that are reported in kilo or liberty, but fixed in mitaka21:42
tonybmriedem: Yeah that was my feeling.21:42
*** reedip has joined #openstack-meeting-421:42
*** lakshmiS has joined #openstack-meeting-421:42
mriedembut someone could report it in the liberty timeframe and be using juno21:42
mriedemidk21:42
*** cdelatte has joined #openstack-meeting-421:42
tonybmriedem: Hmm I wonder how I could find those ....21:42
mriedemi think that's pretty hard given ^ scenario21:42
mriedemwe see that a lot in nova bugs21:42
tonybmriedem: yeah.21:42
mriedemcould be reported in december of 2015 but they are using juno or kilo21:43
rockygmriedem, yeah.  Maybe put a note in bold above the list of bugs on each etherpad to check whether the bug getting fixed should be backported?  A reminder when they change the status on the etherpad.21:43
tonybmriedem: Yeah I could look for *juno* or *kilo* in comment0 but I think that'd be messy21:44
mriedemtonyb: i don't really think it's worth it21:44
*** dims has joined #openstack-meeting-421:44
tonybmriedem: okay.21:44
*** kebray has joined #openstack-meeting-421:44
mriedemi think teams just have to be on top of tagging things if they seem valid for backporting, like what ihar has been doing in neutron21:44
tonybmriedem: now that I have the ground work playign isn't too hard21:45
tonyb+1 neutron is doign great there.  did they start doign frequent releases?21:45
mriedemmore frequent yes21:45
rockygwhich is also great21:45
*** xingchao has quit IRC21:46
mriedemassuming they aren't backporting regressions or bugs, but that's hard to know :)21:46
rockygUh, yeah ;-)21:46
tonybmriedem: :)21:46
mriedemanyway, i don't really have anything else for this topic21:47
rockygI've got a topic....21:47
mriedemok21:47
rockygProd_wg is working on a "user_story" for longer lasting stable releases.  In fact, I'm writing a good bit about it.  I'll cc you guys when I get the next draft.  It's RST in gerrit21:48
*** baoli_ has quit IRC21:48
mriedemok21:48
rockygI'm trying to dovetail some needs/desires on the user community side with reality.  And get more people dedicated (at least part time) to this team.21:49
tonybrockyg: cool.21:49
mriedemi'm assuming user in this case is more operator/deployer than actual cloud user21:49
rockygSo, this is an FYI at the moment, but if you see yourself cc'ed on a review, please review?21:50
bknudsonit's also infra that has concerns about supporting stable longer21:50
mriedembknudson: yeah, and QA21:50
rockygYeah.  The HW needed to support it21:50
*** fawadkhaliq has joined #openstack-meeting-421:50
mriedemthat's why it's generally 4 teams when talking about timelines21:50
mriedemstable, release, QA and infra21:50
mriedemb/c tempest changes are tested on all branches too21:50
rockygAin't that fun;-)21:50
rockygYeah.  And the tempest changes propagating to stable is an interesting thing.21:51
mriedemwell, tempest is branchless21:52
rockygAlthough tempest does get a tag at about the time of each release21:52
mriedemso it has to make sure that tempest master works with stable service APIs21:52
mriedemand you can't drop things or add things to tempest that would fail on stable21:52
*** cdelatte has quit IRC21:52
rockygYeah, but the branchless doesn't work so well for DefCore/Refstack21:53
*** cdelatte has joined #openstack-meeting-421:53
mriedemwhy?21:53
*** armax has joined #openstack-meeting-421:53
rockygBecause tests change that are not backward compatible.21:53
mriedemfor like an icehouse cloud?21:53
rockygLike all "extra options" were turned off for Kilo, but Juno still can use them.  So Juno tests fail.21:53
rockygThat's nova stuff.21:54
*** cdelatte has quit IRC21:54
mriedemi guess i'd need specific examples/details21:54
mriedemwhich we don't have time to get into here21:54
mriedemis this in the review or in the ML?21:54
rockygBut, other tests had bugs, so you have to pick and choose git IDs to find the "just right" version where bugs are fixed but tests still work.21:55
rockygIt's in the DefCore mailing list.21:55
rockygAnd in the DefCore meeting minutes.21:55
mriedemok, neither of which are things i've been privy too yet21:56
mriedemso a link to the ML would be helpful21:56
rockygI can get you the thread.  Just not before the end of the meeting;-)21:56
rockygIs there an IRC channel for this group?21:56
rockygI can post it there.21:56
tonyb#opensatck-stable21:56
jokke_rockyg: #openstack-stable21:56
rockygThanks.  I'll add it to my "favorites.21:56
tonybrockyg: only without typos :)21:56
mriedemok, with that, let's wrap this up21:57
mriedemanything else for 3 minutes left21:57
mriedem?21:57
tonybmriedem: not from me21:57
mriedemok, i'm assuming you're speaking for everyone too21:57
jokke_:)21:57
mriedemthanks everyone21:57
jokke_thanks all21:57
mriedem#endmeeting21:57
rockygI've talked enough!21:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:57
openstackMeeting ended Mon Feb 29 21:57:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-29-21.00.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-29-21.00.txt21:57
rockygThanks!21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-29-21.00.log.html21:57
*** mriedem has left #openstack-meeting-421:57
tonybThanks mriedem21:57
*** mbound has quit IRC21:59
*** salv-orl_ has joined #openstack-meeting-421:59
*** salv-orlando has quit IRC22:02
*** sdake has joined #openstack-meeting-422:05
*** banix has quit IRC22:08
*** sarob has quit IRC22:08
*** neelashah1 has joined #openstack-meeting-422:09
*** dims has quit IRC22:09
*** prithiv has quit IRC22:09
*** baoli has joined #openstack-meeting-422:10
*** neelashah has quit IRC22:11
*** reedip has quit IRC22:11
*** woodard has quit IRC22:12
*** neelashah has joined #openstack-meeting-422:13
*** sdake has quit IRC22:14
*** prithiv has joined #openstack-meeting-422:15
*** neelashah1 has quit IRC22:16
*** britthouser has joined #openstack-meeting-422:17
*** sdake has joined #openstack-meeting-422:18
*** yamahata has quit IRC22:18
*** yamahata has joined #openstack-meeting-422:19
*** armax has quit IRC22:19
*** cloudtrainme has quit IRC22:20
*** jmckind has quit IRC22:22
*** vhoward has quit IRC22:23
*** cemmason has quit IRC22:23
*** cemmason1 has joined #openstack-meeting-422:23
*** neelashah1 has joined #openstack-meeting-422:24
*** neelashah has quit IRC22:24
*** sarob has joined #openstack-meeting-422:25
*** armax has joined #openstack-meeting-422:26
*** cemmason has joined #openstack-meeting-422:27
*** cemmason1 has quit IRC22:27
*** qwebirc71842 has joined #openstack-meeting-422:29
qwebirc71842I upgraded barbican to c0c1833d3c18dcee1d44a2c88670b6668f7a68ab.  "Merge "Remove padding from legacy stored secrets". But I still cannot  access my old secrets from before the upgrade. Any ideseas?22:32
*** neelashah1 has quit IRC22:35
*** thorst has quit IRC22:35
*** neelashah has joined #openstack-meeting-422:36
*** julim has quit IRC22:39
*** baoli has quit IRC22:41
*** thorst has joined #openstack-meeting-422:42
*** rockyg has quit IRC22:42
*** neelashah has quit IRC22:43
*** rockyg has joined #openstack-meeting-422:45
*** cbouch has quit IRC22:45
*** thorst has quit IRC22:46
*** sdake has quit IRC22:46
*** ninag has quit IRC22:47
*** reedip has joined #openstack-meeting-422:50
*** baoli has joined #openstack-meeting-422:57
*** KLevenstein has quit IRC22:59
*** azbiswas has joined #openstack-meeting-423:00
*** thorst has joined #openstack-meeting-423:00
*** sdake has joined #openstack-meeting-423:03
*** baoli has quit IRC23:04
*** cloudtrainme has joined #openstack-meeting-423:05
*** thorst has quit IRC23:05
*** klamath has quit IRC23:07
*** yamamoto_ has joined #openstack-meeting-423:11
*** sarob has quit IRC23:11
*** sarob has joined #openstack-meeting-423:11
*** yamahata has quit IRC23:12
*** sbadia has quit IRC23:13
*** cemmason has quit IRC23:14
*** sbadia has joined #openstack-meeting-423:14
*** dims has joined #openstack-meeting-423:14
*** Sukhdev has joined #openstack-meeting-423:15
*** salv-orl_ has quit IRC23:15
*** yamamoto_ has quit IRC23:16
*** prithiv1 has joined #openstack-meeting-423:17
*** ninag has joined #openstack-meeting-423:18
*** qwebirc71842 has left #openstack-meeting-423:19
*** prithiv has quit IRC23:19
*** salv-orlando has joined #openstack-meeting-423:19
*** ninag has quit IRC23:22
*** spotz is now known as spotz_zzz23:24
*** dshakhray has quit IRC23:31
*** sridhar_ram has quit IRC23:33
*** baoli has joined #openstack-meeting-423:35
*** andymaier has joined #openstack-meeting-423:37
*** banix has joined #openstack-meeting-423:42
*** yamamoto_ has joined #openstack-meeting-423:42
*** matrohon has quit IRC23:50
*** rockyg has quit IRC23:52
*** jmckind has joined #openstack-meeting-423:52
*** fnaval has quit IRC23:52
*** Swami has quit IRC23:55
*** thorst has joined #openstack-meeting-423:56
*** baoli has quit IRC23:57
*** thorst_ has joined #openstack-meeting-423:58

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