Monday, 2016-12-05

*** bpokorny has joined #openstack-meeting-400:02
*** armax has quit IRC00:06
*** sdake has quit IRC00:08
*** baoli has quit IRC00:16
*** woodard has quit IRC00:17
*** woodard has joined #openstack-meeting-400:17
*** iyamahat has joined #openstack-meeting-400:27
*** Jeffrey4l has quit IRC00:29
*** Jeffrey4l has joined #openstack-meeting-400:30
*** galstrom is now known as galstrom_zzz00:32
*** iyamahat has quit IRC00:32
*** Julien-zte has joined #openstack-meeting-400:35
*** bpokorny has quit IRC00:35
*** bpokorny has joined #openstack-meeting-400:35
*** kylek3h is now known as kylek3h_away00:38
*** bpokorny has quit IRC00:40
*** limao has joined #openstack-meeting-400:50
*** thorst_ has joined #openstack-meeting-400:50
*** bpokorny has joined #openstack-meeting-400:51
*** JRobinson__ is now known as JRobinson__afk00:53
*** thorst_ has quit IRC00:58
*** Julien-zte has quit IRC01:01
*** Julien-zte has joined #openstack-meeting-401:01
*** julim has joined #openstack-meeting-401:01
*** hieulq has joined #openstack-meeting-401:02
*** JRobinson__afk is now known as JRobinson__01:19
*** bpokorny has quit IRC01:34
*** jovon has joined #openstack-meeting-401:41
*** baoli has joined #openstack-meeting-401:45
*** thorst_ has joined #openstack-meeting-401:45
*** ricolin has joined #openstack-meeting-401:46
*** thorst_ has quit IRC01:47
*** baoli has quit IRC01:50
*** julim has quit IRC01:56
*** zhihui has joined #openstack-meeting-401:56
*** julim has joined #openstack-meeting-401:56
*** julim has quit IRC02:01
*** hongbin has joined #openstack-meeting-402:10
*** zhihui has quit IRC02:10
*** gnuoy has quit IRC02:10
*** unicell1 has quit IRC02:12
*** yamahata has joined #openstack-meeting-402:17
*** unicell has joined #openstack-meeting-402:18
*** sdake has joined #openstack-meeting-402:37
*** sdake_ has joined #openstack-meeting-402:39
*** sdake has quit IRC02:41
*** tovin07 has joined #openstack-meeting-402:50
*** sdake_ has quit IRC02:51
*** thorst_ has joined #openstack-meeting-402:52
*** baoli has joined #openstack-meeting-402:55
*** thorst_ has quit IRC03:01
*** yamamoto_ has joined #openstack-meeting-403:02
*** baoli has quit IRC03:09
*** thorst_ has joined #openstack-meeting-403:11
*** thorst_ has quit IRC03:12
*** baoli has joined #openstack-meeting-403:13
*** sp_ has joined #openstack-meeting-403:15
*** limao has quit IRC03:16
*** limao has joined #openstack-meeting-403:17
*** limao has quit IRC03:21
*** baoli has quit IRC03:27
*** baoli has joined #openstack-meeting-403:27
*** bpokorny has joined #openstack-meeting-403:31
*** baoli has quit IRC03:32
*** jovon has quit IRC03:48
*** psachin has joined #openstack-meeting-403:52
*** thorst_ has joined #openstack-meeting-404:12
*** thorst_ has quit IRC04:21
*** ricolin has quit IRC04:26
*** vishnoianil has joined #openstack-meeting-404:28
*** bpokorny has quit IRC04:28
*** baoli has joined #openstack-meeting-404:28
*** bpokorny has joined #openstack-meeting-404:28
*** coolsvap has joined #openstack-meeting-404:30
*** julim has joined #openstack-meeting-404:32
*** bpokorny has quit IRC04:33
*** baoli has quit IRC04:33
*** julim_ has joined #openstack-meeting-404:34
*** julim has quit IRC04:36
*** limao has joined #openstack-meeting-404:48
*** yamamoto_ has quit IRC04:48
*** yamamoto_ has joined #openstack-meeting-404:50
*** sdake has joined #openstack-meeting-404:50
*** limao_ has joined #openstack-meeting-404:51
*** limao has quit IRC04:52
*** armax has joined #openstack-meeting-404:58
*** armax has quit IRC04:59
*** anilvenkata has joined #openstack-meeting-404:59
*** pbourke has quit IRC05:00
*** pbourke has joined #openstack-meeting-405:01
*** JRobinson__ has quit IRC05:07
*** JRobinson__ has joined #openstack-meeting-405:08
*** bpokorny has joined #openstack-meeting-405:11
*** thorst_ has joined #openstack-meeting-405:19
*** bpokorny has quit IRC05:21
*** bpokorny has joined #openstack-meeting-405:21
*** bpokorny has quit IRC05:26
*** sdake has quit IRC05:26
*** thorst_ has quit IRC05:26
*** prateek has joined #openstack-meeting-405:28
*** baoli has joined #openstack-meeting-405:29
*** trinaths has joined #openstack-meeting-405:29
*** janki has joined #openstack-meeting-405:34
*** baoli has quit IRC05:34
*** GB21 has joined #openstack-meeting-405:42
*** irenab has joined #openstack-meeting-405:50
*** Jeffrey4l has quit IRC05:51
*** Jeffrey4l has joined #openstack-meeting-405:51
*** mgagne has quit IRC05:53
*** mgagne has joined #openstack-meeting-405:55
*** mgagne is now known as Guest5173705:55
*** trinaths has quit IRC05:56
*** karts has joined #openstack-meeting-406:19
*** hongbin has quit IRC06:21
*** Jeffrey4l has quit IRC06:24
*** thorst_ has joined #openstack-meeting-406:25
*** tovin07_ has joined #openstack-meeting-406:25
*** trinaths has joined #openstack-meeting-406:29
*** baoli has joined #openstack-meeting-406:29
*** thorst_ has quit IRC06:31
*** yamamoto_ has quit IRC06:34
*** baoli has quit IRC06:34
*** Jeffrey4l has joined #openstack-meeting-406:36
*** yamamoto_ has joined #openstack-meeting-406:36
*** numans has joined #openstack-meeting-406:42
*** slaweq_ has quit IRC06:44
*** sgordon has quit IRC06:47
*** mfisch has quit IRC06:49
*** slaweq_ has joined #openstack-meeting-406:49
*** mrunge_ has joined #openstack-meeting-406:52
*** mfisch has joined #openstack-meeting-406:52
*** sgordon has joined #openstack-meeting-406:52
*** dhellmann_ has joined #openstack-meeting-406:53
*** mfisch has quit IRC06:53
*** mfisch has joined #openstack-meeting-406:53
*** mrunge has quit IRC06:53
*** dhellmann has quit IRC06:53
*** julim_ has quit IRC06:53
*** julim has joined #openstack-meeting-406:54
*** unicell has quit IRC06:54
*** unicell has joined #openstack-meeting-406:55
*** unicell has quit IRC06:55
*** unicell has joined #openstack-meeting-406:55
*** iberezovskiy|off has quit IRC06:56
*** dhellmann_ is now known as dhellmann06:56
*** iberezovskiy has joined #openstack-meeting-406:58
*** revon has quit IRC07:02
*** limao_ has quit IRC07:08
*** thorst_ has joined #openstack-meeting-407:30
*** baoli has joined #openstack-meeting-407:30
*** thorst_ has quit IRC07:36
*** baoli has quit IRC07:46
*** JRobinson__ has quit IRC07:47
*** limao has joined #openstack-meeting-407:50
*** d0ugal has joined #openstack-meeting-407:51
*** limao has quit IRC08:01
*** sshnaidm has joined #openstack-meeting-408:02
*** jichen has joined #openstack-meeting-408:04
*** nkrinner has joined #openstack-meeting-408:25
*** kylek3h__ has joined #openstack-meeting-408:31
*** thorst_ has joined #openstack-meeting-408:34
*** kylek3h_away has quit IRC08:34
*** yohoffman has quit IRC08:35
*** zz_ja has quit IRC08:35
*** zz_ja has joined #openstack-meeting-408:36
*** yohoffman has joined #openstack-meeting-408:38
*** dimak has joined #openstack-meeting-408:41
*** sshnaidm is now known as sshnaidm|mtgs08:41
*** thorst_ has quit IRC08:41
*** baoli has joined #openstack-meeting-408:43
*** baoli has quit IRC08:47
*** ralonsoh has joined #openstack-meeting-408:48
*** alexchadin has joined #openstack-meeting-408:55
*** xiaohhui has joined #openstack-meeting-408:56
*** limao has joined #openstack-meeting-408:57
*** ricolin has joined #openstack-meeting-408:59
*** oanson has joined #openstack-meeting-409:00
*** hujie has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Dec  5 09:00:22 2016 UTC and is due to finish in 60 minutes.  The chair is oanson. 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
dimakGood morning09:00
xiaohhuiHeel09:00
xiaohhuiHello09:00
oansonHi09:00
hujieHi09:00
oansonAgenda is here: https://wiki.openstack.org/wiki/Meetings/Dragonflow09:01
irenabhi09:01
*** lihi has joined #openstack-meeting-409:01
yuli_shello09:01
lihiHi09:01
oanson#info dimak xiaohhui hujie irenab yuli_s lihi is in meeting09:01
*** rajivk has joined #openstack-meeting-409:02
oansonAll right. Let's get this show on the road09:02
oanson#topic Ocata Roadmap09:02
*** openstack changes topic to "Ocata Roadmap (Meeting topic: Dragonflow)"09:02
*** ishafran has joined #openstack-meeting-409:02
oansonlihi, you want to update us on IPv6?09:02
*** Kevin_Zheng has joined #openstack-meeting-409:02
lihiThere is an issue with the fullstack tests and IPv609:03
lihiI'm working on that. Should upload a patch soon09:04
oansonGreat.09:04
lihiAfter that I'll be able to write the tests for the NS responser09:04
oansonAnything that makes fullstack more stable is very well accepted :)09:04
lihiAnd then I'll upload it too09:04
*** irenab_ has joined #openstack-meeting-409:05
oansonGreat. Thanks!09:05
oansondimak, any news on SFC?09:05
dimakI've uploaded some patches that don't do much yet09:05
dimakmainly code that connects sfc drivers with the ryu apps though nb api09:06
*** jingting has joined #openstack-meeting-409:06
*** irenab has quit IRC09:06
*** irenab_ is now known as irenab09:06
dimakI have some ideas to remove duplicate code around NB api and db store09:06
dimakand maybe make ryu app base slimmer09:06
oansonGreat.09:06
lihisounds good09:06
dimaksome of this is in https://review.openstack.org/#/q/status:open+project:openstack/dragonflow+branch:master+topic:bp/service-function-chaining09:07
hujie+109:07
oansondimak, that code is WF-1. Should we start sending comments? Or wait till it's more mature?09:07
dimakI'll move the refactoring code underneath all the sfc stuff09:08
dimakso it can be reviewed without the sfc noise09:08
dimakand get in without waiting for sfc09:08
oansonIf your changes are not directly related, you can just place them in unrelated patches09:08
*** asettle has joined #openstack-meeting-409:08
oansonIf you then need two changes as parents, you can use the Depends-On commit tag.09:08
oansonIf that helps09:08
dimakOh, I'll try that :)09:09
dimakthats about all09:09
oansonI noticed that when the patch chains get too long, it becomes a headache to maintain, especially for the developer09:09
dimakI'll update when I have more concrete09:09
oansonGreat. Thanks!09:09
dimakI prefer longer chains with concrete changes :)09:09
oansonUp to you09:10
oanson:)09:10
oansonChassis liveness09:10
oansonxiaohhui?09:10
xiaohhuiI haven't started yet09:10
xiaohhuiI plan to do it after virtual tunnel port09:10
oansonNo worries. I see you are doing a lot of other things in parallel :)09:10
*** Jeffrey4l has quit IRC09:11
oansonWasn't that merged?09:11
xiaohhuiAs they both changes lots of stuff of chassis09:11
xiaohhuiNot all the code09:11
oansonI see.09:12
xiaohhuiI put some other code in the review board09:12
oansonI see09:12
xiaohhuiI am on my mobile, so I can't put the link here09:13
*** bauwser is now known as bauzas09:13
oanson#link virtual tunnel port support https://review.openstack.org/#/q/project:openstack/dragonflow+branch:master+topic:bp/virtual-tunnel-port-support09:13
xiaohhuiBut that should be ok for the status09:13
xiaohhuiThanks oanson09:13
oansonnp :)09:13
xiaohhuiI mean that should be all for the status09:14
oansonrajivk, I see there are some comments on the service status reporting spec09:14
oansonAnything that needs to be discussed here?09:15
oanson(Also hujie, nick-ma_ )09:15
rajivkI would like more comments09:15
irenabrajivk: link tothe patch?09:15
rajivki have put different approaches for a few things, if someone can comment on them, it will be great.09:15
oanson#link service status reporting spec https://review.openstack.org/#/c/402395/09:16
oansonAll right. I'll review it by tomorrow09:16
hujieI'm do some refactor job and bug fix, and I plan to commit db consistent logic between neutron db and df db09:16
rajivkIf that is ok, i will put updated patch for it.09:16
xiaohhuiI will check it.09:16
*** qwebirc45930 has joined #openstack-meeting-409:16
*** danpawlik has joined #openstack-meeting-409:17
nick-ma_hi alll09:17
lihiI'll also check it09:17
oansonhujie, I'm looking forward to it :)09:17
hujie:)09:17
oansonI'm interested to know how you wrote it, since it will be useful for migration too09:17
oansonnick-ma_, hi09:17
hujieok, but the main logic is similar to the south:)09:18
oansonThat makes sense09:18
oansonI'm guessing it will sit on the Neutron service, or its own service?09:19
hujieyes09:19
hujiea separate service09:19
oansonSounds great09:19
hujie:)09:19
oansonTAPaaS - yuli_s any comments? Anything that needs to be discussed here?09:20
yuli_ssure09:20
yuli_splease take a look at the last version of spec09:20
yuli_shttps://review.openstack.org/#/c/396307/09:21
oanson#link TAP as a service spec https://review.openstack.org/#/c/396307/09:21
oansonI see a lot of work was done yesterday :)09:21
oansonI'll review it today too09:21
yuli_syes !09:21
yuli_sthanks,09:22
*** sp_ has quit IRC09:22
oansonI also saw that the position variable issue was resolved09:22
*** reedip has quit IRC09:22
oansonWhich is also great09:22
yuli_syes,09:22
yuli_sand we have a solution for cycles09:22
yuli_sof packets09:23
oansonCare to share?09:23
yuli_sas opposed to neutron09:23
yuli_syes, check the document09:23
oansonAll right. I'll stay in suspense until I do :)09:23
yuli_sok ;)09:24
oansonishafran, any news about anonymous sNAT?09:24
oansonI saw that the spec was updated earlier too09:24
ishafranI would like to get latest patch set #9 of spec approved09:24
oansonAnything that has to be discussed here?09:24
ishafrannothing except spec :)09:25
oansonAll right. I'll look at it as well :)09:25
oansondenghui isn't here to discuss LBaaS, so we'll skip it this week.09:26
oansonI think I reached a stable state in Dragonflow deployment with OSA09:26
nick-ma_great news.09:27
oanson#link Openstack-ansible dragonflow patch https://review.openstack.org/#/c/391524/09:27
oansonI am now waiting for reviews. If anyone wants to try it out and find all the hidden bugs I put in :)09:27
dimakI'll try to deploy it :)09:28
oansonAnything else for roadmap?09:28
oansondimak, go for it! Wear a hard-hat :)09:28
*** baoli has joined #openstack-meeting-409:28
oansonThey have a tox environment (tox -e dragonflow) that installs the bare minimum09:29
oansonincluding neutron and dragonflow09:29
oansonAnything else for roadmap?09:29
qwebirc45930Have you guys had a chance to review the new classifier spec09:30
qwebirc45930?09:30
irenabyes, I did09:30
hujieI have reviewed it :)09:30
hujieany problem?09:30
oanson#link Separation Classification app spec https://review.openstack.org/#/c/404622/09:31
*** lionelze has joined #openstack-meeting-409:31
oansonqwebirc45930?09:31
qwebirc45930So  how should we continue with it?09:32
oansonAll right. It looks like its pretty far along.09:32
oansonWe'll wait for a few more reviews.09:32
oansonIf there are no objections, we'll merge it later this week09:33
qwebirc45930Great09:33
nick-ma_i will review it later.09:33
oansonnick-ma_, thanks!09:33
*** qwebirc45930 is now known as itamaro09:33
oansonAnything else for roadmap?09:34
*** Julien-zte has quit IRC09:34
*** sp_ has joined #openstack-meeting-409:34
oanson#topic Bugs09:34
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"09:34
*** baoli has quit IRC09:34
oansonThere are bugs.09:35
hujiehttps://review.openstack.org/#/c/406751/09:35
oansonBut as I said a few weeks ago, I want to concentrate on features and code cleanup now. And crack down on bugs later (say 2-3 weeks from now)09:35
hujiedpdk config bug :)09:36
oansonhujie, fullstack fails in that patch. Connection to Neutron fails (at a quick glance)09:37
nick-ma_yes, i'm checking it.09:37
hujieok I see09:37
rajivkoanson, if you need my help for code cleaning, i am available.09:37
oansonrajivk, thanks.09:38
oansonI'll have to get back to you - there is a lot of work done by xiaohhui, dimak, and hujie, and I got a bit lost at who's doing what :)09:38
rajivkoanson, i will try my best to help you :)09:39
oansonThanks! Greatly appreciated!09:39
*** thorst_ has joined #openstack-meeting-409:39
oansonAnything else for bugs?09:39
rajivkhttps://review.openstack.org/#/c/320398/09:39
rajivkI have submitted patch for it. i am having problem for fullstack tests.09:40
*** alexchadin has quit IRC09:40
rajivkCan someone help me with them?09:40
*** alexchadin has joined #openstack-meeting-409:41
xiaohhuiI have a similar patch. Maybe you could use it09:41
xiaohhuiI am still on mobile09:41
rajivk:)09:41
oansonrajivk, I can look into it as well09:41
rajivkthanks09:41
oansonxiaohhui, do you remember the name of the patch, and I'll add the link?09:42
xiaohhuiDhcp options09:42
xiaohhuiI try to add some other dhcp options09:42
rajivkMay be we can list down, all the options and take them one by one.09:43
oanson#link Support default route from port extra dhcp options https://review.openstack.org/#/c/401964/109:43
xiaohhuiYes, this one09:43
oansonMaybe a list/map from option name to function that generates option data,09:43
oansonif the function returns none, skip that option09:43
oansonI am now working on a big refactor for dhcp app.09:43
oansonI'll add it there09:44
oanson(Or as a followup)09:44
oansonAnything else for bugs?09:44
oanson#topic Open Discussion09:45
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:45
*** thorst_ has quit IRC09:45
oanson@snapiri suggested we review the code in df_local_controller09:46
*** psachin has quit IRC09:46
oansonMany functions (mostly delete) receive object IDs only to fetch them from db_store09:46
oansonAnd many callers of these functions already have the object available.09:47
oansonsnapiri suggests duplicating the api - one for id, and one for object (since there is no real overloading in python)09:47
oansonThe ID api can call the object api, so there shoudn't be code duplication.09:47
oansonAny thoughts?09:47
dimaksounds reasonable09:48
dimakthere is also a lot of 'create or update' code09:48
dimakfetch original => check if none => check version09:48
dimakmaybe we can do something about it09:49
hujiethis patch is my first step to refactor the code: https://review.openstack.org/#/c/406114/09:49
hujieI'll use update instead of create/update method09:49
oansonSounds like the right direction.09:50
rajivkhujie: your patch is very big, can you please break it into smaller pieces, it will help in reviewing.09:50
oansonI would have preferred to keep them separated, but it really looks like the two methods are always very similar09:50
rajivki would prefer separated one's as well.09:51
hujieyes, it's very similar :)09:51
*** ricolin has quit IRC09:51
rajivkMay be we can create one more method, which has common code.09:51
*** gnuoy has joined #openstack-meeting-409:51
rajivkand both of the original method call's it. What do you think?09:52
oansonWe will have to review how each solution pans out, and select the best one.09:52
oansonIn general this sounds like a good idea.09:52
oansonWe should just make sure we don't end up with two identical functions calling the common code, just to keep the create/update separation09:52
hujieI have deleted the create method indeed :)09:52
oansonMaybe a fallback for create? on create call the create method, and if it doesn't exist, call the update method?09:53
dimakwe can but I'm not sure a standalone create method is justified here, update has to take care of create anyway09:53
hujieI think update is enough, while other resources have the update/delete method to cover all the scenario09:54
oansondimak wrote a _CRUDHelper class which holds stubs for create and update (for nb_api, but he says there should be a similar one for df_controller). Maybe something along these lines?09:54
oansonAll right. Then lets stick to update only. We can always add create methods later, on in specific cases09:54
dimak1 sec I'll send a link09:54
hujieok great09:54
dimakhttps://review.openstack.org/#/c/406599/1/dragonflow/db/api_nb.py09:55
oanson#link CRUDHelper https://review.openstack.org/#/c/406599/1/dragonflow/db/api_nb.py09:55
oansonAnything else on this?09:56
oansonThe floor is for the taking.09:56
oansonAll right. Great meeting. Great work!09:57
oansonI think its a good sign that there is so much being done that I can't keep up :)09:57
dimakThanks, good bye!09:57
nick-ma_thanks.09:57
irenabthanks09:57
rajivkthanks09:57
lihiThanks09:57
hujiethx bye09:57
xiaohhuiBye09:57
oanson#endmeeting09:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:57
openstackMeeting ended Mon Dec  5 09:57:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-12-05-09.00.html09:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-12-05-09.00.txt09:57
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-12-05-09.00.log.html09:57
*** hujie has quit IRC09:57
*** ishafran has quit IRC09:59
*** sp_ has quit IRC09:59
*** reedip has joined #openstack-meeting-410:00
*** sp_ has joined #openstack-meeting-410:01
gnuoyHi, there is a new checms meeting scheduled now10:02
*** rajivk has left #openstack-meeting-410:02
gnuoyHowever, an announcment hasn't been sent out yet10:02
tinwoodhello10:03
gnuoyIf you're here for that meeting give me a wave otherwise I'll postpone till after the announcment has been sent10:03
tinwoodo/10:04
gnuoytinwood, I think it's just you and I so lets postpone.10:05
tinwoodgnuoy, okay, sounds reasonable.10:05
gnuoyI was going to say for a fortnight but10:05
gnuoythats a holiday in lots of parts of the world10:05
*** sp_ has quit IRC10:06
tinwoodindeed.10:06
tinwoodHow about the new year.10:06
gnuoyYeah, I think Jan 9th for this slot is most likely10:06
tinwoodSounds good to me.10:06
gnuoykk10:07
*** sambetts|pto is now known as sambetts10:08
*** limao has quit IRC10:14
*** mrunge_ is now known as mrunge10:15
*** matrohon has joined #openstack-meeting-410:16
*** sp_ has joined #openstack-meeting-410:17
*** irenab has quit IRC10:25
*** yamamoto_ has quit IRC10:27
*** baoli has joined #openstack-meeting-410:31
*** psachin has joined #openstack-meeting-410:34
*** baoli has quit IRC10:35
*** yamamoto has joined #openstack-meeting-410:43
*** tovin07 has quit IRC10:44
*** tovin07_ has quit IRC10:48
*** irenab has joined #openstack-meeting-410:50
*** nkrinner has quit IRC10:52
*** thorst_ has joined #openstack-meeting-411:07
*** woodard has quit IRC11:08
*** reedip has quit IRC11:10
*** sp_ has quit IRC11:10
*** oanson has left #openstack-meeting-411:12
*** thorst_ has quit IRC11:12
*** GB21 has quit IRC11:15
*** GB21 has joined #openstack-meeting-411:17
*** julim has quit IRC11:20
*** nkrinner has joined #openstack-meeting-411:20
*** sp_ has joined #openstack-meeting-411:23
*** reedip has joined #openstack-meeting-411:23
*** portdirect_ has quit IRC11:26
*** sp_ has quit IRC11:28
*** reedip has quit IRC11:28
*** baoli has joined #openstack-meeting-411:31
*** nkrinner has quit IRC11:36
*** baoli has quit IRC11:36
*** nkrinner has joined #openstack-meeting-411:37
*** reedip has joined #openstack-meeting-411:41
*** sp_ has joined #openstack-meeting-411:42
*** Daviey has quit IRC11:43
*** Daviey has joined #openstack-meeting-411:43
*** nkrinner has quit IRC11:44
*** limao has joined #openstack-meeting-411:58
*** nkrinner has joined #openstack-meeting-411:58
*** limao has quit IRC12:03
*** GB21 has quit IRC12:07
*** xiaohhui has quit IRC12:08
*** thorst_ has joined #openstack-meeting-412:10
*** limao has joined #openstack-meeting-412:11
*** rtheis has joined #openstack-meeting-412:14
*** thorst_ has quit IRC12:16
*** trinaths has quit IRC12:20
*** limao has quit IRC12:21
*** limao has joined #openstack-meeting-412:21
*** julim has joined #openstack-meeting-412:26
*** slaweq_ has quit IRC12:31
*** baoli has joined #openstack-meeting-412:32
*** alexchadin has quit IRC12:36
*** alexchadin has joined #openstack-meeting-412:36
*** limao has quit IRC12:36
*** baoli has quit IRC12:37
*** oanson has joined #openstack-meeting-412:37
*** sdake has joined #openstack-meeting-412:41
*** bobh has joined #openstack-meeting-412:48
*** bobh has quit IRC12:48
*** bobh has joined #openstack-meeting-412:48
*** thorst_ has joined #openstack-meeting-412:50
*** limao has joined #openstack-meeting-412:51
*** prateek has quit IRC12:59
*** portdirect has joined #openstack-meeting-413:00
*** bobmel has joined #openstack-meeting-413:01
*** oanson has left #openstack-meeting-413:03
*** sp_ has quit IRC13:10
*** reedip has quit IRC13:11
*** limao has quit IRC13:12
*** limao has joined #openstack-meeting-413:12
*** irenab has quit IRC13:13
*** portdirect has quit IRC13:13
*** portdirect has joined #openstack-meeting-413:14
*** portdirect has quit IRC13:15
*** portdirect has joined #openstack-meeting-413:16
*** reedip has joined #openstack-meeting-413:24
*** yamamoto has quit IRC13:26
*** julim has quit IRC13:29
*** janki has quit IRC13:31
*** baoli has joined #openstack-meeting-413:33
*** limao_ has joined #openstack-meeting-413:34
*** irenab has joined #openstack-meeting-413:35
*** limao has quit IRC13:36
*** baoli has quit IRC13:38
*** dave-mccowan has joined #openstack-meeting-413:40
*** yamamoto has joined #openstack-meeting-413:44
*** uck has joined #openstack-meeting-413:50
*** Jeffrey4l has joined #openstack-meeting-413:50
*** limao_ has quit IRC13:54
*** limao has joined #openstack-meeting-413:55
*** mchiappero has joined #openstack-meeting-413:56
*** lmdaly has joined #openstack-meeting-413:56
*** mattmceuen has joined #openstack-meeting-414:00
*** cdelatte has joined #openstack-meeting-414:00
*** lamt has joined #openstack-meeting-414:01
*** cathrichardson_z has joined #openstack-meeting-414:01
*** ivc_ has joined #openstack-meeting-414:01
*** yedongcan has joined #openstack-meeting-414:02
apuimedo#startmeeting kuryr14:04
openstackMeeting started Mon Dec  5 14:04:11 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: kuryr)"14:04
openstackThe meeting name has been set to 'kuryr'14:04
apuimedoHello and welcome to another kuryr weekly IRC meeting14:04
apuimedowho's here today?14:04
ivc_o714:05
irenabhi14:05
lmdalyo/14:05
limaoo/14:05
mattmceueno/14:05
*** garyloug has joined #openstack-meeting-414:05
*** cathrich_ has joined #openstack-meeting-414:05
yedongcano/14:05
garylougo/14:05
mchiapperoo/14:05
*** pc_m has joined #openstack-meeting-414:05
janonymous\o/14:05
mchiappero:D14:05
apuimedowelcome to all of you :-)14:06
apuimedo#topic kuryr-lib14:06
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:06
*** cathrichardson_z has quit IRC14:06
*** alraddarla_ has joined #openstack-meeting-414:06
alraddarla_o/14:06
apuimedo#info last week we released kuryr-lib 0.2.0. This release marks the last of our direct development of new features in the openstack/kuryr repository. It was agreed that from now on new features go into kuryr-libnetwork and kuryr-kubernetes and then they move to openstack/kuryr14:07
apuimedoanybody has anything about kuryr-lib?14:08
mchiapperouhm, I don't have anything specific in mind but I guess there might be some changes/refactoring there14:08
mchiapperowell, one thing (yet has to be decided) is whether we want to add a mean to avoid the binding drivers to set the IP addresses14:09
*** hongbin has joined #openstack-meeting-414:09
apuimedomchiappero: yes. There is refactoring coming up14:09
hongbino/14:09
apuimedobut not before we finish container-in-vm for both kuryr-libnetwork and kuryr-kubernetes14:09
mchiapperoalthough I would really like to have some clear  well defined replies on libnetwork first14:09
mchiapperono ok, I see14:10
apuimedomchiappero: since you bring it up14:10
mchiapperoit seems to work anyway :)14:10
apuimedo#topic kuryr-libnetwork14:10
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:10
apuimedoWe merged mchiappero and lmdaly's fix so that now we create and delete the devices on the proper docker REST calls: https://review.openstack.org/#/c/394547/14:11
mchiapperothank you all! :)14:11
lmdaly+1 :)14:11
*** cathrich_ is now known as cathrichardson14:11
apuimedoltomasbo confirmed that with this (as was intended) we'll not have leftover container devices :-)14:12
apuimedoso now we have a bit of a funny but good situation14:12
mchiapperoI have something I would like to mention14:13
apuimedowe have https://review.openstack.org/#/c/402462/ and https://review.openstack.org/#/c/400365/14:13
apuimedoand they don't overlap on goals, but they may overlap partly on how they go about solving the needs they have14:13
apuimedomchiappero: go ahead14:14
mchiapperorelated to the previous patch,  we experienced some issues with an old version of Neutron (6.0.0) that had a bug exposed by that patch14:15
mchiapperohowever I came to know by I coleague of mine that neutronclient is going to be deprecated in favour of openstackclient14:15
apuimedothe mac address limitation14:15
apuimedo?14:15
apuimedoI thought that deprecation is only for the cli aspect of it14:16
*** limao has quit IRC14:16
apuimedoand that openstackclient will continue consuming neutronclient's code as a library14:16
mchiapperooh, ok, I didn't know, I wanted to check with you :)14:16
*** limao has joined #openstack-meeting-414:16
apuimedoirenab: limao: can you confirm?14:16
mchiapperoso, anyway, we will do more testing, but I guess the advice is to use a fairly recent version of Neutron14:17
irenabapuimedo: I am not sure, can check and update14:17
limaoSorry, I get disconnected at last min14:17
apuimedook14:17
limaocan you repeat it one time..14:17
apuimedolimao: sure14:17
apuimedolimao: it was about python-neutronclient. mchiappero said that he heard it is deprecated and I said that I thought only the cli part is deprecated and openstackclient will continue consuming it14:18
apuimedo(as a library)14:18
*** uck has quit IRC14:19
*** tovin07 has joined #openstack-meeting-414:19
hongbini think yes, openstackclient is the replacement of hte cli part, the python client part should continue to work14:19
apuimedohongbin: thanks!14:20
apuimedomchiappero: ;-)14:20
limaoapuimedo: yes, cli part will be openstackclient14:20
mchiapperogood, makes sense14:20
apuimedomchiappero: lmdaly: did you review ltomasbo's patch?14:21
mchiapperono, I'm sorry, I have little time lately14:21
lmdalyno, not the most recent update14:22
apuimedoI would appreciate if you could review it14:22
mchiapperoI will14:22
ltomasbome too :)14:22
apuimedoit seems it is ready to merge, and if you could point out incompatibilities14:22
apuimedobetween your approaches14:22
lmdalyyep will do!14:22
mchiapperoso, would that prevent our patch from merging?14:22
apuimedowe can discuss and reach consensus14:22
apuimedomchiappero: may be14:23
apuimedothat's why I want your review14:23
apuimedoto minimize conflict14:23
mchiapperook, I'll do, I would like to get all the comments collected and the issues sorted ASAP14:23
apuimedo#action mchiappero lmdaly ltomasbo to review https://review.openstack.org/#/c/400365/ and https://review.openstack.org/#/c/402462/14:23
apuimedomchiappero: agreed!14:23
mchiapperoso that both can be merged quickly14:23
apuimedoyup. I want to merge them latest on Wednesday14:24
apuimedobut I don't always get what I want14:24
apuimedo:-)14:24
apuimedoAnything else on kuryr-libnetwork?14:24
mchiapperocool :) we are a bit behind for the UT but will try to run fast14:24
apuimedomchiappero: remember to add people as reviewers https://review.openstack.org/#/c/406636/14:24
apuimedo:-)14:24
mchiapperook :)14:24
mchiapperoone last thing14:26
mchiapperoI was actually forgetting14:26
apuimedohttp://timhandotme.files.wordpress.com/2014/04/steve-jobs-one-last-thing-wwdc-2007.jpg14:26
apuimedoxD14:26
mchiapperothe code for IPVLAN and MACVLAN, unless something changes in the kernel drivers, is the same14:26
apuimedogo ahead14:26
*** coolsvap has quit IRC14:27
mchiapperohowever IPVLAN is not going to work at the moment, do we want to prevent it from loading, right?14:27
*** spzala has joined #openstack-meeting-414:27
mchiapperoI mean, the binding driver to be used by kuryr-libnetwork14:27
apuimedomchiappero: We can just log an error14:28
mchiapperowhat do you mean exactly?14:28
mchiapperoat runtime or start-up time or what?14:28
ltomasbowhy IPVLAN is not going to work? due to the ovs with same mac problem?14:29
apuimedowell, if people try to load the ipvlan driver, we just LOG error and raise exception14:29
mchiapperoltomasbo: yes14:29
mchiapperoltomasbo: well, ovs...? no14:29
ltomasbobut a neutron port is created, and it is included in allowed_pairs14:29
ltomasbocan we just take the MAC of the new created subport for the ipvlan?14:29
mchiapperoapuimedo: ok :)14:29
ltomasboor is there a kernel restriction to create the ipvlan device with a different mac than the main device is attached to?14:30
apuimedomchiappero: and please create a big TODO(mchiappero) that says when we can remove the error14:30
mchiapperoltomasbo: the second one :) let's continue on the kuryr channel14:30
ltomasbook14:30
apuimedoltomasbo: mchiappero said that there is that restriction, but that it could easily be fixed in kernel14:30
*** tonytan4ever has joined #openstack-meeting-414:31
ltomasbook, great to know! I was not aware of that14:31
apuimedo#topic fuxi14:31
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:31
mchiapperoI would have another topic, but not for this meeting, but I want to mention it before I forget14:31
mchiappero:D14:31
apuimedomchiappero: in the open discussion section ;-)14:31
mchiapperosure14:31
*** woodard has joined #openstack-meeting-414:31
apuimedo#info hongbin got a few patches merged and posted a devstack patch. I think it looks okay. It has a problem in fedora that was pointed out, but it should be fixed soon14:32
apuimedo#chair hongbin14:32
openstackCurrent chairs: apuimedo hongbin14:32
hongbinhi14:32
hongbinlast week, i tried to setup same basic fullstack test14:32
apuimedohongbin: please, update us :-)14:32
apuimedogood!14:33
hongbinfor example, create a volume with fuxi driver14:33
*** woodard has quit IRC14:33
hongbin#link https://review.openstack.org/#/c/403931/14:33
*** anilvenkata has quit IRC14:33
hongbin#link https://review.openstack.org/#/c/403941/14:33
hongbinThey are on merge conflict now, i will resolve them14:33
*** woodard has joined #openstack-meeting-414:33
hongbinAfter the fullstack tests are merged, the next step is to setup the CI14:33
hongbinfor the old reviews, apuimedo gave a good feedback on the devstack plugin patch14:34
hongbini will address his comment soon14:34
hongbinthen, you will have the devstack plugin to setup fuxi14:34
hongbinthe last thing is the review queue. Thanks all who performed reviews. We need more help on that :)14:35
hongbin#link https://review.openstack.org/#/q/project:openstack/fuxi14:35
hongbinapuimedo: that is all from me14:35
apuimedothanks a lot hongbin!14:35
*** bobh has quit IRC14:35
apuimedovery nice update!14:35
apuimedo#topic kuryr-kubernetes14:35
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:35
ivc_services/endpoints is WIP, will prolly push something this week14:36
apuimedo#info: Last week we made some devstack improvements (still some left to do when restacking)14:36
apuimedo#info ivc_ pushed the initial CNI driver support. https://review.openstack.org/404038 . It looks practically ready for merging14:37
*** limao has quit IRC14:37
apuimedoonce we have this, we have to enable the gates (I posted a devstack install patch that I have to fix)14:37
*** limao has joined #openstack-meeting-414:37
apuimedoand after those two pieces are there, just as hongbin is doing for fuxi, we need to start with the fullstack tests and put them as gates14:37
apuimedoivc_: you'll push them with polling I suppose14:38
ivc_yup14:38
ivc_for now14:38
apuimedovery well14:39
apuimedo#action ivc_ to push reworked versions of the services/endpoints patch14:39
apuimedoanything else about kuryr-kubernetes?14:40
ivc_apuimedo most likely it will have the same API logic as the current VIFDriver's activate_vif14:40
irenabwhen do we want to push devref?14:40
ivc_whenever you think it is ready :P14:40
ivc_i dont think we should wait for CNI14:40
ivc_so i'd say leave CNI part as-is14:41
apuimedoirenab: I propose to push it for the part we have merged14:41
apuimedothen we draft the CNI and services part14:41
irenabapuimedo: ivc_ agreed14:41
* apuimedo winks at writing "we draft"14:41
irenabapuimedo:  I will push a devref during this week14:41
apuimedogreat irenab!14:42
ivc_irenab, you want to keep my diagram for pipeline or will you redraw it with EArchitect?14:42
*** bobh has joined #openstack-meeting-414:42
apuimedoYour work with that gdoc is excellent, it helped me put in order my head (I made slides out of it)14:42
ivc_aye, awesome work, irenab :)14:42
apuimedoivc_: irenab: If you don't mind, I'll try replacing those diagrams with pngs and have the source in the repo in an open format14:43
irenabputing ivc_ ideas on paper (not code) was indeed a challenge14:43
apuimedoI was checking https://www.modelio.org/14:43
irenabapuimedo: sounds good, will check14:44
*** prateek has joined #openstack-meeting-414:44
apuimedoirenab: I don't mind doing it if you prefer to spend the time with the rest of the devref14:44
apuimedoanything else, anybody?14:44
irenabapuimedo: will be great, thanks14:45
apuimedo#topic Open Discussion14:46
*** openstack changes topic to "Open Discussion (Meeting topic: kuryr)"14:46
*** lamt has quit IRC14:46
apuimedomchiappero: your turn14:46
mchiapperoI noticed that the way kuryr-libnetwork there is no support for both IPv4 and IPv614:48
mchiappero*kuryr-libnetwork is14:48
mchiapperoI mean at the same time14:48
*** watanabe_isao has joined #openstack-meeting-414:49
mchiapperowhen you receive a request for address a port is created, I would assume libnetwork preforms two such calls for a V4 and V6 address, so two separate ports would get created14:49
mchiapperoI could not test as libnetwork doesn't seems to actually use IPv6 even when asked14:50
*** reedip_ has joined #openstack-meeting-414:50
mchiapperobut I guess this might (should) happen at some point14:50
apuimedoright14:50
mchiapperoso14:50
*** Jeffrey4l has quit IRC14:51
mchiapperothere aren't many solutions, basically two14:51
*** Jeffrey4l has joined #openstack-meeting-414:51
mchiapperoeither not reserving at RequestAddress, or rejoining the two ports into a single one as soon as we can correlate the two IP addresses as belonging to the same endpoint (at CreateEndpoint time)14:51
*** watanabe_isao has quit IRC14:52
*** bobh has quit IRC14:52
mchiapperobut it's something more long term, I guess14:52
apuimedoI'm more for the latter14:53
apuimedomchiappero: do we have a bug or blueprint for that?14:54
mchiapperoI don't know, I'm not sure if someone else managed instead to test both IPv4 and IPv6 together14:54
apuimedomchiappero: I don't think so14:55
mchiapperoyes, the latter is more safe14:55
apuimedoI think everybody that reported was either 6 or 414:55
mchiapperobut in theory it should take a fraction of seconds to move from RequestAddress to CreateEndpoint, so creating those two ports might not be a huge safety advantage14:56
mchiapperooh, ok, does anybody know why they prevent the use of both?14:56
*** git-harry has joined #openstack-meeting-414:56
apuimedoI don't :(14:57
mchiapperook.. that's all from me14:57
*** woodard has quit IRC14:57
apuimedothanks mchiappero!14:58
apuimedoplease, file a bug/bp!14:58
apuimedoSo we can look at it and have better discussion14:58
apuimedo:-)14:58
*** limao has quit IRC14:58
apuimedothank you all for joining the meeting!14:58
mchiapperoI'll do14:58
apuimedo#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:58
openstackMeeting ended Mon Dec  5 14:58:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-12-05-14.04.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-12-05-14.04.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-12-05-14.04.log.html14:58
*** yedongcan has left #openstack-meeting-414:58
*** pc_m has left #openstack-meeting-414:59
*** limao has joined #openstack-meeting-414:59
*** alexchadin has quit IRC15:00
sigmavirus#startmeeting craton15:00
openstackMeeting started Mon Dec  5 15:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: craton)"15:00
openstackThe meeting name has been set to 'craton'15:00
sigmavirus#chair jimbaker15:00
openstackCurrent chairs: jimbaker sigmavirus15:00
*** bobh has joined #openstack-meeting-415:00
sigmavirus#link https://etherpad.openstack.org/p/craton-meetings15:00
sigmavirus#topic Roll Call15:01
*** openstack changes topic to "Roll Call (Meeting topic: craton)"15:01
sigmaviruso/15:01
*** ivc_ has left #openstack-meeting-415:02
*** hongbin has quit IRC15:02
*** mattmceuen has left #openstack-meeting-415:02
suloo/15:03
*** cathrichardson has left #openstack-meeting-415:03
sigmavirusLooks like it's just the two of us sulo15:04
sulo:(15:04
* sigmavirus shrugs15:05
sigmavirus#topic Updates15:05
*** openstack changes topic to "Updates (Meeting topic: craton)"15:05
*** tojuvone has joined #openstack-meeting-415:05
sigmavirusAny updates on your end sulo ?15:05
sulonot much other than i've update thew wf blueprint15:05
sulohttps://blueprints.launchpad.net/craton/+spec/craton-workflow-engine15:05
*** Syed__ has joined #openstack-meeting-415:07
*** itamaro has quit IRC15:07
suloso i am working mosting on that15:08
sulomost of it i have it in some form in code15:08
sulobut watned to put that up for discussion15:08
*** lionelze has quit IRC15:09
*** yuli_s has quit IRC15:09
*** baoli has joined #openstack-meeting-415:09
jimbakero/15:09
jimbakersigmavirus, sulo, sorry, overslept here :)15:09
*** reedip_ has quit IRC15:09
sulojimbaker: np, we just started15:10
* sigmavirus is just back from vacation15:10
jimbakersulo, thanks for that blueprint15:10
sigmavirusI see tojuvone and toan are joining us today15:10
sigmavirusjimbaker: any concise updates for us today?15:10
jimbakersigmavirus, right, conciseness is something i could work on...15:11
jimbakeri have been working on blueprints about virtualized variables and how secrets are stored in craton15:11
jimbakervirtualized variables are fairly straightforward, especially because we have discussed them at length15:12
*** numans has quit IRC15:13
jimbakersecrets are potentially a rabbit hole that go as deep as we want it to go15:13
sigmavirusjimbaker: so secrets are back?15:13
Syed__o/15:13
*** reedip_ has joined #openstack-meeting-415:14
*** GB21 has joined #openstack-meeting-415:14
*** psachin has quit IRC15:14
jimbakersigmavirus, how else are we able to execute against target nodes? or against remote resources for virtualized variables?15:14
sigmavirusjimbaker: a simple yes or no is all I need :)15:15
jimbakersigmavirus, yes15:15
*** garyloug has left #openstack-meeting-415:15
sigmavirus(not trying to pick a fight)15:15
suloheh, secrets are b a c k !!15:15
sigmavirusor are they in the back? With the cookies? :P15:15
jimbakersigmavirus, i'm just trying to pick a scheme where we have secrets, but really it's deferred to another system15:16
sulosigmavirus: yes yes ;)15:16
sigmavirusokay15:16
sigmavirusjimbaker: what happened to gathering requirements and rbac?15:17
jimbakeranyway, it's a topic we will have to discuss in greater depth15:17
sigmavirusjimbaker: let's queue that for tomorrow's video meeting?15:17
jimbakersigmavirus, requirements were further gathered15:17
sigmavirusgood15:18
jimbakerso good discussion with rackspace private cloud about what they need15:18
sigmaviruswoot15:18
jimbakerwe will be working on taking that doc and publishing on a public etherpad this week15:18
*** julim has joined #openstack-meeting-415:19
jimbakersigmavirus, with respect to rbac, i think we need to gather more feedback on the blueprint i put out last week15:19
*** limao has quit IRC15:19
sigmavirusFair, I didn't have enough time to review it then. It's on my list for today15:19
* sigmavirus crosses fingers hoping to get to it15:20
Syed__i believe it would be better to discuss rbac in tomorrow's vidyo15:20
jimbakeranyway, vidyo meeting on all three tomorrow sounds good15:20
*** reedip has quit IRC15:20
sigmavirusSyed__: any uupdates?15:20
sigmavirusor just updates, either way15:20
*** limao has joined #openstack-meeting-415:20
Syed__yeah. been working on gathering information for Rbac15:20
Syed__i have one patch in the queue. Today will try uploading two more for networks tests and routes.py tests15:20
*** rbak has joined #openstack-meeting-415:21
sulook lets move on ?15:23
jimbaker+115:24
sigmavirussulo: move on to?15:24
sigmavirusPriority Reviews maybe?15:24
sigmavirus#topic Priority Reviews15:24
*** openstack changes topic to "Priority Reviews (Meeting topic: craton)"15:24
suloi dont have any reviews pending :)15:24
sulohowever, not sure if git-harry is in today .. but he has a lot of open review that15:25
jimbakerat this point, it's really git-harry15:25
git-harryI'm in but need to go in 2 minutes. Saw the -2, will rework (probably go back to my original patch)15:26
jimbakerwith the bulk of reviews. but i think the root has been -2 by me, so need to revisit15:26
suloyeah so i was goint to say they need review that i've -1'ed15:26
sulobut i thik those are teh ones that are in chain and have a -2 on endpoint15:26
sulojimbaker: yeah i think thats right15:26
jimbakergit-harry, so we agreed to keep /v1/hosts, /v1/regions, etc15:27
git-harryYeah, I saw that15:27
jimbakeri guess no dispute on /v1/regions... anyway15:27
jimbakerso keep flat, but actually make it work for querying more generally15:27
jimbakerwe could start by removing region_id as a required param15:28
git-harryYeah, it's fine.15:28
jimbakerwhich presumably should just work with the python-cratonclient as it is15:28
git-harryAnyway, gotta go15:29
tojuvonehieulq, yes here, have overlapping meeting. Need to go soon.15:29
*** numans has joined #openstack-meeting-415:29
jimbakergit-harry, np, thanks for looking into this15:30
jimbakersigmavirus, so am i'm correct on python-cratonclient?15:30
suloyeah it should work without change .. atleast the api .. as region_id is something that is passed15:31
suloso should work with  minimal change if any15:31
*** hongbin has joined #openstack-meeting-415:31
sigmavirusjimbaker: I'm not sure what you're talking about, I'd need a link to brush up on it and confirmd/eny15:31
jimbakeryeah, it's just a question of whether the client is specifically checking for this param or not15:32
*** reedip has joined #openstack-meeting-415:32
jimbakerbut agreed about minimal change (if any)15:32
jimbakergoing forward, it's certainly easy for the client - just needs to handle pagination as necessary15:33
jimbakerthat's it for priority reviews - i see that Syed__ just put in something into review a few minutes ago15:35
*** bobh has quit IRC15:36
Syed__There is one another for me15:36
Syed__For network endpoints15:36
Syed__The one for networks is actually dependent for me for routes and networks tests15:36
Syed__:)15:36
jimbakerSyed__, url ?15:37
jimbakerof the review15:37
jimbakeris this https://review.openstack.org/#/c/400977/ ?15:37
Syed__https://review.openstack.org/#/c/400977/15:37
Syed__Yeap15:37
Syed__Thats the one jim15:37
jimbakerok, i will test. especially since sulo hasn't actually tested it directly15:38
Syed__Sure15:38
Syed__Thank you15:38
jimbakerSyed__, were you able to add a functional test to this change?15:39
jimbaker(now that we have functional testing, we should be using it for future changes....)15:39
Syed__No this change doesnt needs one i believe15:39
Syed__I will add more functional tests for regions, cells etc this week15:39
Syed__Will raise bugs individually for those15:39
suloSyed__: you can leave them .. i have them already15:40
jimbakerSyed__, i', pretty sure if there's an endpoint involved, it will require one :)15:40
Syed__Ohh i see. I didnt knew that.15:40
sulowas waiting for endpoint change to go though15:40
*** jovon has joined #openstack-meeting-415:40
Syed__Cool sulo15:40
Syed__Thank you15:40
jimbakeranyway, usual transition15:40
*** limao has quit IRC15:41
jimbakerthe other consideration we will have is how to bring in the python client into the functional testing15:41
sigmavirusjimbaker: I don't think the client should be part of functional testing15:41
sigmavirusthe client and server should have their own individual functional tests15:41
*** limao has joined #openstack-meeting-415:41
sulojimbaker: you mean from teh client side ?15:41
sigmavirusthe client shouldn't be used in the server's functional tests15:41
sigmavirusif the server changes something that breaks the client then that change becomes dependent on the fix in the client, which is dependent on the change on the server and you have a loop that will never merge15:42
jimbakersigmavirus, yeah, sure, we might call this integration testing. but similar leverage of the functional test framework15:42
sigmavirusit's a terrible diea15:42
jimbakersigmavirus, oh i agree it's horribly complicated15:42
jimbakerbut having something that does this test is still going to be important15:43
sigmavirusjimbaker: right, what you want is for the client to have functional tests that run the server15:43
jimbakersigmavirus, i don't know where these tests are currently done in openstack projects. but hopefully the combination of standard client + service is tested on a regular basis, challenges and all15:44
sigmavirusI agree, and we'll set that up15:44
suloi am totes confused ... are we talking about putting client in server functional test or doing functional test for client ?15:44
sigmavirussulo: I understood the former, but I"m advocating solely for the latter15:44
jimbakersulo, i'm just saying, do test15:44
sulook15:44
jimbakerthe specifics i'm completely open to. it sounds like the client testing will drive, which is absolutely fine for me15:45
*** yamahata has quit IRC15:45
*** yamahata has joined #openstack-meeting-415:46
jimbakerwhich means the functional testing of the server code itself will purely look at its rest api, as is being done now15:46
jimbakerand speculating: the client will probably reuse the server functional test harness to do its own testing15:46
*** spotz_zzz is now known as spotz15:47
*** Sukhdev has joined #openstack-meeting-415:47
jimbakerif the server breaks its contract, the client tests will all start failing on a recheck. but at least we can fix the server, and get out of the pernicious loop that sigmavirus mentioned15:48
sigmavirusjimbaker: potentially15:48
sigmavirus(reuse the harness)15:48
*** haleyb_ has joined #openstack-meeting-415:48
jimbakersigmavirus, yeah, just throwing something out there15:48
jimbakeranything else we should discuss in this meeting?15:50
*** galstrom_zzz is now known as galstrom15:51
jimbakeri guess that's a *no*15:52
Syed__i am done15:52
Syed__nothing from my side15:52
Syed__thanks jim15:52
tojuvoneNothing that special15:52
jimbakerlet's move additional discussion to #craton15:52
Syed__+115:53
*** prateek has quit IRC15:53
sigmavirus#endmeeting15:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:53
openstackMeeting ended Mon Dec  5 15:53:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-12-05-15.00.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-12-05-15.00.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-12-05-15.00.log.html15:53
*** haleyb_ has quit IRC15:53
*** armax has joined #openstack-meeting-415:55
*** hshiina has joined #openstack-meeting-415:57
SukhdevFolks, time for Ironic-neutron meeting16:00
jroll\o16:00
Sukhdev#startmeeting ironic_neutron16:01
openstackMeeting started Mon Dec  5 16:01:09 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
Sukhdevsambetts: are you here?16:01
*** GB21 has quit IRC16:01
Sukhdev#topic: Agenda16:01
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:01
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_December_5.2C_201616:01
SukhdevThe agenda is pretty much same from last week16:02
*** limao has quit IRC16:02
*** jrist has joined #openstack-meeting-416:02
Sukhdev#topic: Announcements16:02
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:02
Sukhdevjroll : anything to announce?16:02
*** limao has joined #openstack-meeting-416:02
jrollnope!16:02
sambettso/16:02
sambettsNothing new from me16:03
Sukhdev#topic: Security Groups16:03
*** openstack changes topic to ": Security Groups (Meeting topic: ironic_neutron)"16:03
SukhdevI rebased the documentation patch - but, missed picking up updated names for variables16:04
*** doonhammer has joined #openstack-meeting-416:04
Sukhdevwill push another update later today16:04
Sukhdevthat should take care of the comments on the patch16:04
*** vsaienk0 has joined #openstack-meeting-416:05
Sukhdevsambetts : do we want to add anything else in the documentaiton patch?16:05
* sambetts still needs to re-review sorry 16:05
SukhdevNP16:06
SukhdevAnything else on this?16:06
*** ricolin has joined #openstack-meeting-416:07
* jroll does not16:07
Sukhdev#topic: Port Groups16:07
*** openstack changes topic to ": Port Groups (Meeting topic: ironic_neutron)"16:07
SukhdevIt seems pretty much in the same state -16:08
joannao/16:08
Sukhdevhttps://review.openstack.org/#/q/topic:bug/161875416:08
jrollyeah, getting close16:09
vsaienk0we can land ironiclient patches, if they are reviewed16:09
*** reedip_ has quit IRC16:09
Sukhdev+116:09
jrollawesome16:09
vsaienk0Please check if we are ok with the following testing approach - https://review.openstack.org/#/c/38174316:10
vsaienk0create nodes with portgroups and without portgroups in same environment and use nova flavors for scheduling16:10
*** GB21 has joined #openstack-meeting-416:10
*** sshnaidm|mtgs has quit IRC16:12
*** lihi has quit IRC16:12
Sukhdevvsaienk0 : nova flavors may or may not have anything to do with port groups - just an FYI16:12
Sukhdevbut, I think your approach is correct16:13
*** iyamahat has joined #openstack-meeting-416:13
vsaienk0Sukhdev it just for tests, to use multitenant environment for portgroup and non-portgroup tests16:14
Sukhdevvsaienk0 : Understood16:14
jrollya, it's probably fine, need to look in more detail though16:15
SukhdevAnything else on this?16:16
Sukhdev#topic: Interface attach APIs16:17
*** openstack changes topic to ": Interface attach APIs (Meeting topic: ironic_neutron)"16:17
Sukhdevsambetts pushed updates on Friday16:17
Sukhdevhttps://review.openstack.org/#/q/topic:+bug/158218816:17
sambettsyeah, these patches when super weird during that push16:17
vsaienk0the patches needs to be rebased, thay are in merge conflict, and the last version wasn't worked I got 500 from API16:17
sambettsI had some terrible merge conflcits and all the files got messed up16:18
*** nkrinner is now known as nkrinner_afk16:18
sambettsI have fixed it and I'm just resolving all the comments16:18
Sukhdevcool - thanks sambetts16:18
Sukhdevwill look for the updates16:19
*** yamamoto has quit IRC16:19
Sukhdevanything else on this?16:19
sambettsNothing right now from me16:20
Sukhdev#topic: VLAN aware servers16:20
*** openstack changes topic to ": VLAN aware servers (Meeting topic: ironic_neutron)"16:20
SukhdevI added few more comments on the spec16:21
SukhdevAnd noticed more comments this morning as well16:21
sambettsthere were a bunch of comments on the RFE over the weekend, I'm going to try to resolve them tomorrow16:21
Sukhdevbut, I think most of the juice is in place16:21
vsaienk0I've left a comments in the spec https://review.openstack.org/#/c/277853/10/specs/approved/VLAN-aware-baremetal-instances.rst@3516:21
vsaienk0I doubt that we need to change anything on ironic side to made it working16:22
*** bobh has joined #openstack-meeting-416:22
vsaienk0neutron allows to group ports to trunks https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms and https://review.openstack.org/#/c/361776/15/doc/networking-guide/source/config-trunking.rst16:23
sambettsmy spec takes all of this into account already16:23
*** limao has quit IRC16:23
vsaienk0Do we need to made any automatic decisions on Ironic side (ie create a trunk on the fly) when user requested instance with more ports that hardware server has, because user image may not support trunking at all16:24
Sukhdevvsaienk0 : I just saw your comment - I think it is covered16:24
*** limao has joined #openstack-meeting-416:24
*** hshiina has quit IRC16:24
Sukhdevvsaienk0 : what do you mean when you say user may not support trunking at all -16:26
Sukhdevdo you mean the TOR?16:26
vsaienk0no I mean the image that user trying to deploy16:26
*** lmdaly has left #openstack-meeting-416:26
jrollthe OS16:26
vsaienk0also I think that number of nic should be somehow mentioned in the flavor, so user always know hardware capabilities16:27
SukhdevThink of a use case when one runs a service on the BM sever -16:27
vsaienk0and if needed user may create a trunk in neutron manually and pass it to nova boot16:28
vsaienk0just wandered why we need to made this decision automatically on Ironic side is it right place?16:28
Sukhdevvsaienk0 : I think this info is needed by (at least) the ML2 drivers when vnic_type == baremetal16:30
sambettsso the reason for doing this may now have been solved by the attach/detach spec, but originally it was so that a user requesting 4 nics in nova could be given any baremetal server regardless of number physical ports16:30
vsaienk0Sukhed ML2 is neutron thing it should pick trunk info from port metadata16:30
Sukhdevnever mind my comment - as soon as I hit send, I realized that :-)16:31
vsaienk0there is an example how trunk port looks like http://paste.openstack.org/show/591426/16:31
joanna@sambetts - could you send me the link to this spec?16:31
vsaienk0it has trunk_details16:31
vdrokjoanna:  https://review.openstack.org/#/c/27785316:31
joannathanks!16:32
*** git-harry has left #openstack-meeting-416:32
vsaienk0sambetts: trying to pick any server is not right, we shouldn't convert user request and create trunks on the fly, we don't know if user image will work with it16:33
*** dimak has quit IRC16:33
*** slaweq_ has joined #openstack-meeting-416:33
*** janonymous has quit IRC16:34
vsaienk0user should know how many nics are available via flavor info, and based on that made decision to create trunks or not by his own16:34
*** alraddarla_ has left #openstack-meeting-416:34
*** alex_xu has quit IRC16:35
*** shaohe_feng has quit IRC16:35
Sukhdevvsaienk0 : If my memory serves me right, there are two use cases16:35
Sukhdev1) when the admin creates trunked port - this is what you are talking about16:35
Sukhdev2) when it is implicitly created on behalf of user16:36
SukhdevWe can debate if 2) is needed or not16:36
sambettsSukhdev: users, not just admins, can create a neutron trunk16:36
sambettsbasically the argument is whether --nic net-id should result in an implict creation16:37
Sukhdevsambetts : right - that is what I said in 1)16:37
Sukhdevin 2) it is implicitly created16:37
sambettsyeah16:37
vsaienk0Sukhdev: user may create a trunk port and use --nic port-id=<trunk-port-id>16:38
sambettsvsaienk0: that isn't broken by my spec16:38
*** lamt has joined #openstack-meeting-416:39
vsaienk0sambetts: I see, but what if user image doesn't support trunks16:39
vsaienk0are we going to handle that case somehow?16:39
sambettsright now we don't have any way for images to state what they support16:39
Sukhdevvsaienk0 : I think that is where flavor-id comes into play16:39
sambettsfor anything, bonding, trunks, cloud-init even16:40
*** julim has quit IRC16:40
Sukhdevvsaienk0 : So, when admin creates nova flavors for BM selection, I think that is where all these come into play16:41
vsaienk0so creating trunk on the fly will break cases when user image doensn't support trunks16:41
sambettsright now Ironic basically assumes the images support them all, and more or less assumes the images are provided not self created by users16:41
sambettsjroll: ^16:41
jrollyeah, it's hard/impossible to detect this16:42
vsaienk0sambetts: I can't say that user image supports vlan if we don't know it for sure16:42
*** reedip has quit IRC16:43
vsaienk0in my understanding if user do --nic net-id multiple times, it means that user want hardware server with number of hardware nics that were specified in request16:43
vsaienk0if user want trunk, he create a trunk and use --nic port-id <trunk>16:43
vsaienk0if want mixed env that --nic net-id ... --nic port-id <trunk>16:44
jrollthe problem is that in a cloudy world, you just connect networks16:44
sambettsIMO if you request --nic net-id multiple times it means I want a NIC connected to this network16:44
jrollyou shouldn't need to know the physical ccharacteristics of the cloud16:44
sambettssub-interfaces are NICs IMO16:44
vsaienk0sambetts: but if user image doesn't support vlans, converting --nic ... --nic and creating trunk will lead to active instance without network access16:45
jrollthe ultimate goal here is to make baremetal act cloudy, like a VM, imo16:45
sambettsvsaienk0: or no instance at all16:45
vsaienk0sambetts: we can't check if instance is accessible16:45
sambettsI mean, it won't even get scehduled16:46
sambettswhich isn't want we want16:46
*** tovin07 has left #openstack-meeting-416:46
Sukhdevsambetts : that is the way I thought it works - but, vsaienk0 does bring up an interesting angle16:47
*** limao has quit IRC16:47
Sukhdevvsaienk0 : in general, if there is no way to know what does instance image support - this is a bigger problem, no?16:47
sambetts+116:48
SukhdevI mean regardless of trunked i/f, it is an issue, no?16:48
vdrokis it going to be at least possible to say "I want this exact configuration, do not assume anything"?16:49
vsaienk0might be use vlan_support flag in image metadata with default = True16:49
*** haleyb_ has joined #openstack-meeting-416:49
Sukhdevvdrok : I thought that will play into the flavor creation process - so that a specific BM is selected or not selected16:50
*** irenab has quit IRC16:50
*** bpokorny has joined #openstack-meeting-416:51
* Sukhdev time check 9 min16:51
Sukhdevto summarize - there are really two orthogonal issues here16:51
vdrokSukhdev: well, with the planned switch to resource providers, the single resource class field might be encoding too much info in it, if we include enabling/disabling features there too16:51
vsaienk0I don't have anything to add, I think we can discuss it in the spec :)16:52
Sukhdev1) do we support implicit creation of trunk port or not16:52
Sukhdev2) Do we tie-in the image capabilities into the flavor creation - so that appropriate BMS are selected or not16:53
Sukhdevanybody sees anything else?16:54
*** haleyb_ has quit IRC16:54
*** unicell has quit IRC16:54
*** irenab has joined #openstack-meeting-416:54
sambettsalso do we include nic number in the flavor/resources to aid scehduling16:55
Sukhdevsambetts : perhaps you can mention these in the spec16:55
*** reedip has joined #openstack-meeting-416:56
*** unicell has joined #openstack-meeting-416:56
Sukhdevsambetts : right - perhaps a paragraph on the flavor creation guidelines :-)16:56
sambettsSukhdev: right now flavors don't include anything regarding networking, so its a larger issue16:57
*** Swami has joined #openstack-meeting-416:58
Sukhdevsambetts : we can keep networking out - but, use parameters such as image capabilities, Hw capabilities, etc - that should cover everything we discussed here16:58
sambettsI'll try to expand on these issues when I update the spec16:58
Sukhdevsambetts : thanks16:59
vsaienk0sambetts: thanks16:59
Sukhdevanything else - we are down to 1 min16:59
Sukhdevsambetts : BTW, if you need any help with this, feel free to ping me16:59
*** irenab_ has joined #openstack-meeting-417:00
*** uck has joined #openstack-meeting-417:00
sambettssure thanks :D and thanks for all the reviews :D17:00
SukhdevOK - folks, we are out of time17:00
vdrokmoving to meeting-317:00
vdrok:)17:00
Sukhdevthanks for attending - was a great discussion17:00
Sukhdevbyt17:00
Sukhdevbye17:00
vdrokthanks!17:00
Sukhdev#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Mon Dec  5 17:00:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-12-05-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-12-05-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-12-05-16.01.log.html17:00
*** tonytan4ever has quit IRC17:01
*** irenab has quit IRC17:01
*** irenab_ is now known as irenab17:01
*** reedip has quit IRC17:02
*** tonytan4ever has joined #openstack-meeting-417:02
*** vsaienk0 has left #openstack-meeting-417:03
*** uck has quit IRC17:05
*** mjturek has joined #openstack-meeting-417:05
*** uck has joined #openstack-meeting-417:06
*** d0ugal has quit IRC17:07
*** slaweq_ has quit IRC17:07
*** doonhammer has left #openstack-meeting-417:08
*** Hunner has joined #openstack-meeting-417:08
*** Hunner has quit IRC17:08
*** Hunner has joined #openstack-meeting-417:08
*** asettle has quit IRC17:09
*** ricolin has quit IRC17:10
*** iurygregory has joined #openstack-meeting-417:11
*** reedip has joined #openstack-meeting-417:15
*** portdirect is now known as portdirect_meeti17:16
*** matrohon has quit IRC17:19
*** mchiappero has left #openstack-meeting-417:19
*** yamamoto has joined #openstack-meeting-417:20
*** bobh has quit IRC17:23
*** woodard has joined #openstack-meeting-417:26
*** Guest51737 is now known as mgagne17:26
*** yamamoto has quit IRC17:26
*** portdirect_meeti is now known as portdirect17:26
*** mgagne has quit IRC17:27
*** mgagne has joined #openstack-meeting-417:27
*** baoli has quit IRC17:33
*** baoli has joined #openstack-meeting-417:34
*** bpokorny has quit IRC17:38
*** bpokorny has joined #openstack-meeting-417:39
*** GB21 has quit IRC17:42
*** bpokorny has quit IRC17:43
*** haleyb_ has joined #openstack-meeting-417:50
*** harlowja has joined #openstack-meeting-417:50
*** bpokorny has joined #openstack-meeting-417:50
*** Rockyg has joined #openstack-meeting-417:52
*** haleyb_ has quit IRC17:55
*** ralonsoh has quit IRC18:01
*** reedip has quit IRC18:08
*** piet has joined #openstack-meeting-418:14
*** vishnoianil has quit IRC18:17
*** bobh has joined #openstack-meeting-418:18
*** reedip has joined #openstack-meeting-418:21
*** jichen has quit IRC18:27
*** Sukhdev has quit IRC18:28
*** reedip has quit IRC18:30
*** doonhammer has joined #openstack-meeting-418:31
*** dharinic is now known as dharinic|lunch18:37
*** s3wong has joined #openstack-meeting-418:37
*** doonhammer has quit IRC18:41
*** reedip has joined #openstack-meeting-418:43
*** haleyb_ has joined #openstack-meeting-418:52
*** asettle has joined #openstack-meeting-418:53
*** d0ugal has joined #openstack-meeting-418:54
*** haleyb_ has quit IRC18:56
*** hemanth is now known as hemanth|lunch18:56
*** bpokorny_ has joined #openstack-meeting-418:58
*** bpokorny_ has quit IRC18:58
*** bpokorny_ has joined #openstack-meeting-418:59
*** emagana has joined #openstack-meeting-419:01
*** bpokorny has quit IRC19:01
*** sambetts is now known as sambetts|afk19:05
*** bpokorny_ has quit IRC19:08
*** bpokorny has joined #openstack-meeting-419:09
*** dharinic|lunch is now known as dharinic19:18
*** asettle__ has joined #openstack-meeting-419:18
*** baoli has quit IRC19:19
*** tonytan_brb has joined #openstack-meeting-419:19
*** baoli has joined #openstack-meeting-419:19
*** sayantani01__ has joined #openstack-meeting-419:20
*** uli-k__ has joined #openstack-meeting-419:20
*** NachoDuck_ has joined #openstack-meeting-419:20
*** hemanth|lunch is now known as hemanth19:21
*** madgin has joined #openstack-meeting-419:22
*** vishnoianil has joined #openstack-meeting-419:22
*** ntr0py_ has joined #openstack-meeting-419:23
*** admcleod_ has joined #openstack-meeting-419:23
*** odyssey4me_ has joined #openstack-meeting-419:26
*** madgin has left #openstack-meeting-419:26
*** mfranc213_ has joined #openstack-meeting-419:26
*** SergeyLukjanov2 has joined #openstack-meeting-419:26
*** bapalm_ has joined #openstack-meeting-419:26
*** mrunge_ has joined #openstack-meeting-419:27
*** MikeG451_ has joined #openstack-meeting-419:27
*** asettle has quit IRC19:28
*** tonytan4ever has quit IRC19:28
*** mrunge has quit IRC19:28
*** karts has quit IRC19:28
*** noama has quit IRC19:28
*** bapalm has quit IRC19:28
*** sayantani01_ has quit IRC19:28
*** uli-k has quit IRC19:28
*** NachoDuck has quit IRC19:28
*** SergeyLukjanov has quit IRC19:28
*** mjturek has quit IRC19:28
*** mfranc213 has quit IRC19:28
*** admcleod has quit IRC19:28
*** ntr0py has quit IRC19:28
*** odyssey4me has quit IRC19:28
*** MikeG451 has quit IRC19:28
*** mrhillsman has quit IRC19:28
*** jroll has quit IRC19:28
*** SergeyLukjanov2 is now known as SergeyLukjanov19:28
*** asettle__ is now known as asettle19:28
*** sayantani01__ is now known as sayantani01_19:28
*** uli-k__ is now known as uli-k19:29
*** sdake_ has joined #openstack-meeting-419:31
*** NachoDuck_ is now known as NachoDuck19:31
*** sdake has quit IRC19:31
*** noama has joined #openstack-meeting-419:35
*** karts has joined #openstack-meeting-419:35
*** jroll has joined #openstack-meeting-419:36
*** mjturek has joined #openstack-meeting-419:36
*** codebauss has joined #openstack-meeting-419:38
*** codebauss is now known as mrhillsman19:38
*** bobh has quit IRC19:50
*** portdirect has quit IRC19:51
*** woodster_ has joined #openstack-meeting-419:51
*** portdirect has joined #openstack-meeting-419:51
*** sdake has joined #openstack-meeting-419:53
*** portdirect has quit IRC19:55
*** sdake_ has quit IRC19:56
*** bpokorny has quit IRC19:59
*** bpokorny has joined #openstack-meeting-420:00
*** bpokorny has quit IRC20:04
*** doonhammer has joined #openstack-meeting-420:04
*** uck has quit IRC20:05
*** portdirect has joined #openstack-meeting-420:10
*** portdirect is now known as portdirect__20:10
*** tonytan_brb has quit IRC20:16
*** jovon has quit IRC20:18
*** tonytan4ever has joined #openstack-meeting-420:23
*** d0ugal has quit IRC20:32
*** vishnoianil has quit IRC20:37
*** asettle has quit IRC20:41
*** haleyb_ has joined #openstack-meeting-420:53
*** numans has quit IRC20:53
*** haleyb_ has quit IRC20:58
tonyb#startmeeting stable21:02
openstackMeeting started Mon Dec  5 21:02:46 2016 UTC and is due to finish in 60 minutes.  The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: stable)"21:02
openstackThe meeting name has been set to 'stable'21:02
tonyb#topic rollcall21:02
*** openstack changes topic to "rollcall (Meeting topic: stable)"21:02
tonyb... Thjis time in the correct channel21:03
tonybI seem to have problems with that lately21:03
RockygI'm here, too21:03
*** lamt has quit IRC21:03
tonybRockyg: :)21:03
tonybRockyg: multitasking like a boss!21:03
RockygHey, it's in my job description...21:04
tonybRockyg: My plan was to drop into the product WG meetign at the end and chat to Carol but she replied overnight21:04
Rockygok.  what's the status on liberty eol?21:05
tonyb#link https://wiki.openstack.org/wiki/Meetings/StableTeam#Agenda21:05
Rockygoops.  jumping the gun21:05
*** uck has joined #openstack-meeting-421:05
tonybRockyg: Nah I was just going to say if there is anything there we can skip to it ...21:05
tonybRockyg: So last cycle (kilo) I wrote a bunch of tools to help with EOLing $branch21:06
tonybRockyg: for $good_reasons fungi suggested I do them different so I'm writeing and testing the different approach this time21:06
*** bpokorny has joined #openstack-meeting-421:06
Rockygoh, good stuff.21:06
tonybRockyg: so I'm going to do nova today, perhaps cinder if that works then I'll roll out the rest during this week21:07
Rockygah.  excellent21:07
tonybRockyg: I do have a few teams to reach out to to get an explicit ACK befoer I EOL them21:07
fungioh, right, api vs git push21:07
*** cdelatte has quit IRC21:07
tonybRockyg: that's one of the problem with openstack-dev is it's lossy.  You can't assume silence is agreement :(21:08
tonybfungi: Yeah :)21:08
tonybfungi: Shoudl I be able to create and delet branches in the snadbox repo?21:08
tonybfungi: from a gerrit POV is being a release manager enough to do this or do I need to hand over to an admin?21:09
Rockygreally lossy to my company mail server21:09
tonybfungi: will regret de-lurking ;P21:09
tonybRockyg: :)21:09
fungitonyb: we can set you up with access if it's not working for you21:09
fungijust let me know21:10
fungionce you get a chance to try it out21:10
tonybfungi: Thanks.  I'll test it after the meeting and if it's not working can I call on you to do that thing21:10
tonybfungi: :)21:10
*** uck has quit IRC21:10
fungiyou bet21:10
tonyb\o/ #winning21:10
tonybRockyg: did you have anything else on liberty or shouls I let you get back to the product_WG?21:13
RockygNope.  go ahead and end this and join me in pwg21:14
tonyb:)21:14
*** spzala has quit IRC21:14
tonybThanks everyone21:14
tonyb#endmeeting21:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:15
openstackMeeting ended Mon Dec  5 21:14:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-12-05-21.02.html21:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-12-05-21.02.txt21:15
openstackLog:            http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-12-05-21.02.log.html21:15
*** emagana has quit IRC21:19
*** sdake has quit IRC21:22
*** Sukhdev has joined #openstack-meeting-421:23
*** doonhammer has quit IRC21:25
*** Marcellin__ has joined #openstack-meeting-421:25
*** tonytan4ever has quit IRC21:27
*** tonytan4ever has joined #openstack-meeting-421:27
*** sdake has joined #openstack-meeting-421:29
*** Jeffrey4l has quit IRC21:35
*** Jeffrey4l has joined #openstack-meeting-421:36
*** emagana has joined #openstack-meeting-421:36
*** tonytan4ever has quit IRC21:40
*** bpokorny has quit IRC21:42
*** bpokorny has joined #openstack-meeting-421:42
*** bpokorny_ has joined #openstack-meeting-421:46
*** bpokorny has quit IRC21:46
*** thorst_ has quit IRC21:47
*** lamt has joined #openstack-meeting-421:49
*** bobh has joined #openstack-meeting-421:52
*** baoli has quit IRC21:53
*** rtheis has quit IRC21:53
*** haleyb_ has joined #openstack-meeting-421:54
*** sdake_ has joined #openstack-meeting-421:57
*** haleyb_ has quit IRC21:59
*** sdake has quit IRC22:01
*** uck has joined #openstack-meeting-422:05
*** thorst has joined #openstack-meeting-422:07
*** thorst has quit IRC22:11
*** portdirect__ has quit IRC22:13
*** aderyugin has quit IRC22:15
*** bobh has quit IRC22:16
*** vishnoianil has joined #openstack-meeting-422:19
*** bobh has joined #openstack-meeting-422:34
*** doonhammer has joined #openstack-meeting-422:36
*** emagana has quit IRC22:47
*** Swami_ has joined #openstack-meeting-422:53
*** numans has joined #openstack-meeting-422:54
*** Swami_ has quit IRC22:55
*** Swami_ has joined #openstack-meeting-422:55
*** haleyb_ has joined #openstack-meeting-422:56
*** Swami has quit IRC22:56
*** piet has quit IRC23:00
*** haleyb_ has quit IRC23:00
*** Swami_ has quit IRC23:01
*** spotz is now known as spotz_zzz23:06
*** JRobinson__ has joined #openstack-meeting-423:07
*** spzala has joined #openstack-meeting-423:15
*** bpokorny_ has quit IRC23:18
*** bpokorny has joined #openstack-meeting-423:18
*** spzala has quit IRC23:20
*** thorst has joined #openstack-meeting-423:20
*** thorst has quit IRC23:22
*** thorst has joined #openstack-meeting-423:22
*** bpokorny has quit IRC23:23
*** bpokorny has joined #openstack-meeting-423:27
*** thorst has quit IRC23:29
*** Sukhdev has quit IRC23:31
*** Swami has joined #openstack-meeting-423:34
*** galstrom is now known as galstrom_zzz23:35
*** lamt has quit IRC23:44
*** spzala has joined #openstack-meeting-423:47
*** rbak has quit IRC23:56
*** haleyb_ has joined #openstack-meeting-423:56

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