Monday, 2016-12-19

*** yamamoto has joined #openstack-meeting-400:00
*** yamamoto has quit IRC00:01
*** yamamoto has joined #openstack-meeting-400:05
*** yfauser has joined #openstack-meeting-400:05
*** thorst has quit IRC00:06
*** baoli has quit IRC00:09
*** yfauser has quit IRC00:10
*** yamamoto has quit IRC00:11
*** yamamoto has joined #openstack-meeting-400:12
*** galstrom is now known as galstrom_zzz00:20
*** limao has joined #openstack-meeting-400:44
*** brucet has joined #openstack-meeting-400:47
*** brucet has quit IRC00:47
*** JRobinson has quit IRC01:00
*** baoli has joined #openstack-meeting-401:00
*** thorst has joined #openstack-meeting-401:03
*** baoli has quit IRC01:05
*** Julien-zte has joined #openstack-meeting-401:06
*** yfauser has joined #openstack-meeting-401:07
*** baoli has joined #openstack-meeting-401:07
*** thorst has quit IRC01:11
*** yfauser has quit IRC01:13
*** tovin07 has joined #openstack-meeting-401:32
*** klamath has joined #openstack-meeting-401:34
*** klamath has quit IRC01:35
*** klamath has joined #openstack-meeting-401:36
*** klamath has quit IRC01:40
*** yifei has joined #openstack-meeting-401:50
*** Julien-zte has quit IRC01:54
*** thorst has joined #openstack-meeting-401:57
*** thorst has quit IRC01:58
*** gongysh has joined #openstack-meeting-402:07
*** yfauser has joined #openstack-meeting-402:09
*** yfauser has quit IRC02:14
*** asettle has joined #openstack-meeting-402:22
*** asettle has quit IRC02:26
*** yfauser has joined #openstack-meeting-402:33
*** yfauser has quit IRC02:38
*** Julien-zte has joined #openstack-meeting-402:44
*** baoli has quit IRC02:55
*** baoli has joined #openstack-meeting-402:57
*** amotoki has joined #openstack-meeting-402:57
*** amotoki has quit IRC02:59
*** amotoki has joined #openstack-meeting-402:59
*** thorst has joined #openstack-meeting-403:03
*** Jeffrey4l has quit IRC03:05
*** Jeffrey4l has joined #openstack-meeting-403:05
*** ediardo has quit IRC03:09
*** ediardo has joined #openstack-meeting-403:11
*** noama has quit IRC03:12
*** thorst has quit IRC03:12
*** noama has joined #openstack-meeting-403:12
*** lrensing has quit IRC03:13
*** irenab_ has joined #openstack-meeting-403:15
*** irenab has quit IRC03:17
*** irenab_ is now known as irenab03:17
*** ChrisPriceAB has quit IRC03:19
*** ChrisPriceAB has joined #openstack-meeting-403:19
*** tkaczynski_ has joined #openstack-meeting-403:22
*** tkaczynski has quit IRC03:22
*** tkaczynski_ is now known as tkaczynski03:22
*** trozet_ has quit IRC03:22
*** trozet_ has joined #openstack-meeting-403:23
*** alanmeadows has quit IRC03:25
*** alanmeadows has joined #openstack-meeting-403:26
*** baoli has quit IRC03:30
*** baoli has joined #openstack-meeting-403:30
*** HenryG has quit IRC03:30
*** baoli has quit IRC03:30
*** HenryG has joined #openstack-meeting-403:33
*** tovin07_ has joined #openstack-meeting-403:48
*** psachin has joined #openstack-meeting-403:53
*** sdake has joined #openstack-meeting-403:56
*** coolsvap has joined #openstack-meeting-403:59
*** thorst has joined #openstack-meeting-404:09
*** marst has quit IRC04:11
*** thorst has quit IRC04:18
*** limao has quit IRC04:28
*** sdake has quit IRC04:28
*** baoli has joined #openstack-meeting-404:32
*** yfauser has joined #openstack-meeting-404:36
*** yfauser has quit IRC04:40
*** prateek has joined #openstack-meeting-404:49
*** limao has joined #openstack-meeting-404:51
*** Jeffrey4l has quit IRC04:53
*** baoli has quit IRC04:53
*** hongbin has joined #openstack-meeting-404:53
*** yfauser has joined #openstack-meeting-404:56
*** yfauser has quit IRC05:00
*** hongbin has quit IRC05:11
*** thorst has joined #openstack-meeting-405:15
*** unicell1 has joined #openstack-meeting-405:16
*** unicell has quit IRC05:16
*** thorst has quit IRC05:22
*** janki has joined #openstack-meeting-405:28
*** amotoki has quit IRC05:32
*** yamamoto has quit IRC05:37
*** janki has quit IRC05:40
*** janki has joined #openstack-meeting-405:40
*** jchhatbar has joined #openstack-meeting-405:45
*** janki has quit IRC05:48
*** yfauser has joined #openstack-meeting-405:51
*** jchhatbar is now known as janki05:53
*** yfauser has quit IRC05:55
*** amotoki has joined #openstack-meeting-405:55
*** amotoki has quit IRC05:58
*** amotoki has joined #openstack-meeting-406:18
*** thorst has joined #openstack-meeting-406:19
*** asettle has joined #openstack-meeting-406:23
*** yfauser has joined #openstack-meeting-406:25
*** asettle has quit IRC06:27
*** thorst has quit IRC06:28
*** xiaohhui has joined #openstack-meeting-406:37
*** yamamoto has joined #openstack-meeting-406:38
*** yamamoto has quit IRC06:38
*** yamamoto has joined #openstack-meeting-406:38
*** anilvenkata has joined #openstack-meeting-406:47
*** mohankumar has joined #openstack-meeting-407:10
*** amotoki has quit IRC07:10
*** JRobinson__ has quit IRC07:21
*** baoli has joined #openstack-meeting-407:21
*** thorst has joined #openstack-meeting-407:25
*** portdirect has quit IRC07:26
*** baoli has quit IRC07:26
*** amotoki has joined #openstack-meeting-407:32
*** thorst has quit IRC07:33
*** pcaruana has joined #openstack-meeting-407:33
*** alexchadin has joined #openstack-meeting-407:51
*** amotoki has quit IRC08:06
*** gongysh has quit IRC08:10
*** yamamoto has quit IRC08:13
*** baoli has joined #openstack-meeting-408:22
*** amotoki has joined #openstack-meeting-408:25
*** thorst has joined #openstack-meeting-408:29
*** ntpttr__ has joined #openstack-meeting-408:30
*** ntpttr__ has quit IRC08:35
*** thorst has quit IRC08:38
*** amotoki has quit IRC08:40
*** mrunge has quit IRC08:41
*** dtardivel has joined #openstack-meeting-408:42
*** baoli has quit IRC08:45
*** yuval has joined #openstack-meeting-408:46
*** mrunge has joined #openstack-meeting-408:46
*** noama has quit IRC08:48
*** sshnaidm|afk is now known as sshnaidm08:52
*** Wangjian has joined #openstack-meeting-408:53
*** lihi has joined #openstack-meeting-408:53
*** oanson has joined #openstack-meeting-409:00
*** hujie has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Dec 19 09:00:12 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
oansonHello.09:00
lihiHi09:00
hujieHello09:00
oansonWelcome to this weeks Dragonflow Weekly!09:00
yuvalHey09:00
oansonWe'll wait a second for others to join.09:00
yuval¯\_(ツ)_/¯09:00
*** dimak has joined #openstack-meeting-409:01
dimakGood morning09:01
oansonyuval, a giant in the playground, no doubt!09:01
evrardjpo/09:01
hujieplay basketball??09:01
oansonI thought more along the lines of order of the stick, but that works too09:02
oansonevrardjp, hi!09:02
yuli_shello09:02
oansonAll right. Let's start.09:02
oanson#topic Ocata Roadmap09:02
*** openstack changes topic to "Ocata Roadmap (Meeting topic: Dragonflow)"09:02
irenabhi09:02
*** rajivk has joined #openstack-meeting-409:02
oansonirenab, rajivk, hi.09:02
rajivkhi09:03
oanson#info lihi hujie yuli_s yuval dimak evrardjp irenab rajivk in meeting09:03
oansonIPv6 - lihi uploaded an initial advertiser implementation.09:03
* xiaohhui waves his hand09:03
oanson#info xiaohhui also in meeting09:03
oansonlihi, is it ready for review? Do you want some comments on it? Or do you want more time to stabilise it?09:04
*** yamahata has quit IRC09:04
lihiI still need to stabilize the tests. They fail differently in different envs. However, comments would be nice :)09:05
oansonGreat09:06
oanson#link Add IPv6 ND Neighbor Advertiser application https://review.openstack.org/#/c/412208/09:06
oansonSFC - dimak, I guess most of your patches will wait the NB refactor?09:06
dimakYes09:06
oansonAnything you'd like to discuss?09:06
dimakDon't have much to show for now09:06
dimakMostly NB refactor, but thats for later :)09:07
oansonYes. Next time don't try to rewrite the project in ten patches, and we'll be good :)09:07
oansonChassis health/service health reporting09:07
oansonrajivk 's spec is here: https://review.openstack.org/#/c/402395/09:07
oanson#link Spec to support service status reporting https://review.openstack.org/#/c/402395/09:08
oansonI see it has a few comments, but if I recall it is fairly close to being ready09:08
rajivkSorry, no status update.09:08
oansonAnything that has to be discussed?09:08
rajivkyes09:08
rajivkHow should i handle service disable and enable?09:09
rajivkIs it ok, if i put service status down?09:09
rajivkor i need to remove corresponding app from the pipeline?09:09
*** portdirect has joined #openstack-meeting-409:10
oansonrajivk, putting service status down is enough09:10
oansonThis feature is just monitoring and reporting. Acting upon this information can be dealt with later09:10
rajivkok09:10
rajivkI will update the patch soon :)09:10
rajivkthat's all from my side.09:11
irenaboanson: question about the last poit09:11
oansonSince there are some open questions on how to handle actions: Each application to its own, or a centralised way? How to do this in a distributed manner (e.g. taking over control of other nodes), etc.09:11
oansonirenab, shoot09:11
irenabwhat is the way to manage services, it is only conf file for now?09:11
irenabI mean enable/disable09:12
rajivksorry, can you please elaborate more?09:12
irenabrajivk: you asked about taking action. My question is how this can be done, is there some API to do it?09:13
rajivkI will add a command in df-db09:14
*** yamamoto has joined #openstack-meeting-409:14
rajivkwhich can enable or disable a service.09:14
irenabrajivk: got it, thanks. so it for the follow-up after monitoring and reporting is done09:14
rajivkyes09:15
rajivkLater on we can extend to perform some operations based on the status of the service.09:15
rajivkas oanson pointed out earlier.09:15
oansonSounds good to me. I hope that will probably be made easier with the NB refactor09:15
*** gsagie has joined #openstack-meeting-409:15
irenabrajivk: thanks for clarification09:15
oansonAnything else for chassis/service health?09:16
rajivkno09:16
oansonGreat! TAPaaS09:16
*** ishafran has joined #openstack-meeting-409:16
oansonyuli_s, any updates?09:17
yuli_ssure09:17
yuli_stap as a service09:17
yuli_shttps://review.openstack.org/#/c/25621009:17
oansonI see on the patch that the tunnel ID issue requires discussion09:17
yuli_sops,09:18
yuli_sthis one09:18
yuli_shttps://review.openstack.org/#/c/396307/09:18
xiaohhuiyeah, the neutron ml2 doesn't expose api to allocate segment_id, so how could the tapaas get segment_id from neutron?09:18
yuli_sHong Hui Xiao advised to use one segment_id for all tapped packets09:19
yuli_sand I wanted to bring this to discussion09:19
oansonIf there are two TapService ports on a remote compute node, how will that compute node know which tapped packets go where?09:19
irenabyuli_s: Can this be reserved range of seg-ids for taas?09:20
xiaohhuiNo, I suggest to use a specific tunnel port whose local_ip is something special for the tapaas09:20
yuli_sirenab, yes, by marking original packet src09:20
oansonxiaohhui, and then recognise it's TAPaaS by tunnel source IP?09:20
*** qwebirc2641 has joined #openstack-meeting-409:20
xiaohhuiyes, so that we don't need to depend on neutron to allocate segment_id09:21
yuli_sfrom security point of view, it is better to have at least one segment for each customer09:21
*** qwebirc2641 is now known as itamaro09:21
xiaohhuiyou can have one segment for one customer,09:21
oansonyuli_s, true. But that might not be possible09:21
yuli_sto minimize the chance the packet interfrerance in case of the bug09:21
xiaohhuijust the src of the tunnel is special09:21
yuli_syes,09:22
yuli_sfor me this can be done09:22
oansonIf we don't have a way to get segment IDs, that won't work. And a bug may cause the same issue with different segment IDs too.09:22
xiaohhuiI just can't think about an easy way to get segment_id from neutron.09:22
yuli_sit complicates the system a bit09:22
yuli_swe can assign a segment id on each new tenant09:23
*** asettle has joined #openstack-meeting-409:23
yuli_sin a kind of global way09:23
oansonxiaohhui, we can try asking them to expose an API for it.09:23
oanson Until then, I think the segmentation be src IP would work.09:23
oansonyuli_s, how would you assign the segment id?09:23
oansonIt must be unique from anything Neutron will assign09:24
yuli_scurrently we have no table for tenants09:24
oansonyuli_s, I don't see how a table for tenants would help09:24
xiaohhuiwait, neutron now has api for segments, which might be something we want.09:25
oansonxiaohhui, can you post a link?09:25
yuli_swe have the allocate_tenant_segment() call09:25
xiaohhuione sec09:26
yuli_sin neutron/plugins/ml2/drivers/type_tunnel.py09:26
irenabdo we need neutron to assign seg_id for taas? Maybe taas service plugin/driver can manage it09:26
yuli_syes, that is what suggested by, or one for each tenant09:27
oansonirenab, you mean the TaaS northbound?09:28
*** asettle has quit IRC09:28
irenabyes09:28
xiaohhuihttps://review.openstack.org/#/c/317358/09:28
*** yamamoto has quit IRC09:28
xiaohhuiI added it in newton for routed network09:28
oansonxiaohhui, very cool! :)09:28
*** hieulq has joined #openstack-meeting-409:29
oansonyuli_s, what does the TaaS northbound say about segment IDs?09:29
xiaohhuiIf we are going to use segment_id from neutron, then we can use the segment api09:29
oansonI think that would be better than piggy-backing it on the src IP.09:29
oansonIf we can put it in the TaaS northbound, that would be best.09:30
oansonyuli_s, what do you think?09:30
yuli_sI need to study this.09:30
yuli_simho this can be done09:31
*** gongysh has joined #openstack-meeting-409:31
oansonyuli_s, that's great.09:31
oansonPlease also consult yamamoto if it's possible to add it to the TaaS northbound09:31
yuli_sok09:31
oansonOtherwise, we will have to do it in our northbound driver09:31
*** mohankumar has quit IRC09:32
oansonWhichever solutions you think is best.09:32
*** asettle has joined #openstack-meeting-409:32
oansonPlease also update the spec09:32
yuli_sok09:33
oansonAnonymous sNAT09:33
oansonishafran, any updates?09:34
ishafranI put latest spec: https://review.openstack.org/#/c/397992/1209:34
ishafranI would like to get functional comments/rejects if any09:34
oansonI see in that spec that you still have per-tenant hidden networks in br-int09:34
ishafranThere are 3 possible solutions threre , and I am going to stick to first one09:34
oansonI thought this requirement was removed due to the information in the metadata fields (reg6 and metadata)09:34
*** thorst has joined #openstack-meeting-409:35
ishafranI need cross-tenant network if double NAT is used09:35
oansonMy understanding was to do first [1], and then [3]09:35
ishafranI am OK with it09:36
*** Julien-zte has quit IRC09:36
oansonGreat.09:36
oansonPlease update the spec and diagram, and I think we can start pushing this along :)09:36
ishafranOK09:36
oansonAnything open in Distributed sNAT?09:37
ishafranI will use local file to store tenant info at least at first phase09:37
oansonSounds good09:37
ishafranfine09:38
oansonIn the second phase (With external IP per (Compute node, tenant) pair) you will need an IP distribution mechanism09:38
oansonTo distribute one IP pool across multiple compute nodes09:38
oansonBut as we said, that's the second phase. It can wait09:38
ishafranno sure but of course database is better09:38
oansonIf it's local and constant, config file is a good solution09:39
oanson(constant in the lifetime of the controller, that is)09:39
ishafranagree09:39
oansonGreat!09:39
oansonNorthBound API refactor09:40
oanson#link North Bound Code Refactor https://review.openstack.org/#/c/410298/09:40
oansonI don't know if you had a chance to go over the spec09:40
dimakI read it and looks good, have some comments09:40
oansonThe version I put up last night (IST) was a bit buggy, and I only updated it a few hours ago09:41
oansondimak, shoot09:41
dimakI saw that you defined events per model09:41
dimakwhich I think is a great idea09:42
dimakThey serve to replace https://github.com/openstack/dragonflow/blob/master/dragonflow/db/api_nb.py#L199 ?09:42
*** yfauser has quit IRC09:42
dimakWith some code in local controller that registers its functions to specific events?09:42
oansonYes09:42
*** thorst has quit IRC09:42
*** yfauser has joined #openstack-meeting-409:42
oansonThere is plan for a southbound refactor as well.09:42
dimakOk09:43
oansonIt will allow applications to register to these 'dynamic' events09:43
dimakAnother thing with crud example09:43
oansonHopefully, we will also have other cool stuff, like an application manager that registers and organises applications09:43
dimakWe're using **kwargs construct objects inside the crud helper09:44
dimaksame with update09:44
dimakwhy not have @classmethod from_dict() or something?09:44
dimakon the model09:44
oansonYes. Currently we support 'partial' updates, meaning we can only pass the columns we update09:44
dimakand update() for instances09:44
dimakThis reduces the case for which we need to define a custom crud helper09:45
oansondimak, the new structure will allow it, so there's no problem adding it09:45
dimakand the crud helper will operate on objects directly rather than dictionaries09:45
oansondimak, I think being able to update a single column is a good thing09:46
oansone.g. the Neutron API lets you update a single column if you provide the ID of the object09:46
oanson(I think it's a REST thing, but I don't remember the details enough to commit)09:47
dimakYes, I wasn't talking about partial vs full updates though :)09:47
*** yfauser has quit IRC09:47
oansonIn any case, with a from_dict/to_dict method, we can call: nbapi.get_resource(<resource>).update(**<instance>.to_dict())09:48
oansondimak, if I need to pass an object rather than column=value fields (or in addition), we're going to have strange overloading magic to support both methods09:48
dimakCRUD can handle the instance rather than the dict09:48
oansonwe*09:48
oansonbut then I need to know if the instance is partial or complete09:49
dimakummm09:49
oansonfor a syntactic improvement that can be done with '**'09:49
oansonActually, with '**'..to_dict(), but that still is not much09:49
dimakWe still have to retrieve the full object for an update..09:49
dimakWell I'm not sure it can be done in a nice way, I'll think about it09:50
*** gsagie has left #openstack-meeting-409:50
oansonThe retrieval is done very close to the database layer. The API layer doesn't see or know about it09:50
dimakAnyway, I wrote both points as comments, I'll post once I'll finish going over the spec09:50
oansonIf some day we will be able to take advantage of that, I think that would be great09:50
oansonSure09:50
oansonAny other comments on the NB refactor spec?09:51
dimakOver all, it seems like a huge step in the right direction09:51
oansonI hope so :)09:52
oansonhujie, would you like to take it?09:52
oansonSince you started doing something similar?09:52
hujieI'll take part in :)09:52
oansonI broke it down into byte sized actions. So we can split the work09:53
hujiegreat!09:53
*** zenoway has joined #openstack-meeting-409:53
oansonRegistration was already started and merged by xiaohhui09:53
*** Adri2000 has quit IRC09:54
oansonThe Base CRUD helper was written by dimak in another patch - dimak, would you mind isolating it and uploading it for review?09:54
dimaksure09:54
oansonThe next two steps are Db Store implementation, and model constructor.09:54
dimakI'll see revise it according to the ideas in the spec09:54
oansonGreat! Thanks!09:54
oansonOnce these two are done, models can be moved 1 by 1 (rather than all of them at once)09:55
oansonSo hujie, do you want to take the Db Store implementation? Or the model construction?09:56
hujieok, maybe I need time to think about it09:56
*** sshnaidm has quit IRC09:56
oansonSure. Let me know, and I'll take the other one09:56
*** amotoki has joined #openstack-meeting-409:56
hujiesure09:57
oansonThanks!09:57
hujie:)09:57
oansonAnything else for Nb API refactor?09:57
oanson#topic Open Discussion09:57
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:57
oansonWe have three minutes. Anything anyone would like to raise?09:57
oansonAll right. Thanks everyone for the great work!09:58
oansonEnjoy your dinner/lunch/breakfast/tea09:58
dimakGbye!09:59
oanson#endmeeting09:59
lihiBye09:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:59
openstackMeeting ended Mon Dec 19 09:59:14 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-12-19-09.00.html09:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-12-19-09.00.txt09:59
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-12-19-09.00.log.html09:59
*** yuval has left #openstack-meeting-409:59
*** yifei has quit IRC10:03
*** Adri2000 has joined #openstack-meeting-410:06
*** amotoki has quit IRC10:06
*** tovin07_ has quit IRC10:07
*** gongysh has quit IRC10:07
*** amotoki has joined #openstack-meeting-410:09
*** yfauser has joined #openstack-meeting-410:14
*** yfauser has quit IRC10:18
*** hujie has left #openstack-meeting-410:20
*** amotoki has quit IRC10:23
*** Jeffrey4l has joined #openstack-meeting-410:24
*** alexchad_ has joined #openstack-meeting-410:25
*** alexchadin has quit IRC10:27
*** limao has quit IRC10:33
*** greeny___ has joined #openstack-meeting-410:33
*** limao has joined #openstack-meeting-410:34
*** limao has quit IRC10:38
*** amotoki has joined #openstack-meeting-410:38
*** thorst has joined #openstack-meeting-410:40
*** apuimedo has quit IRC10:41
*** sshnaidm has joined #openstack-meeting-410:41
*** yfauser has joined #openstack-meeting-410:43
*** amotoki has quit IRC10:45
*** thorst has quit IRC10:48
*** yfauser has quit IRC10:48
*** greeny___ has quit IRC10:53
*** alexchad_ has quit IRC11:00
*** sshnaidm has quit IRC11:00
*** asettle has quit IRC11:05
*** sshnaidm has joined #openstack-meeting-411:06
*** asettle has joined #openstack-meeting-411:09
*** yamamoto has joined #openstack-meeting-411:11
*** mohankumar has joined #openstack-meeting-411:13
*** asettle has quit IRC11:17
*** yamamoto has quit IRC11:22
*** yfauser has joined #openstack-meeting-411:22
*** dave-mccowan has joined #openstack-meeting-411:26
*** yifei has joined #openstack-meeting-411:28
*** draynium has joined #openstack-meeting-411:29
*** yifei has quit IRC11:33
*** portdirect is now known as portdirect_away11:34
*** Wangjian has quit IRC11:34
*** itamaro has quit IRC11:37
*** mohankumar has quit IRC11:37
*** janki has quit IRC11:38
*** baoli has joined #openstack-meeting-411:44
*** thorst has joined #openstack-meeting-411:45
*** dave-mcc_ has joined #openstack-meeting-411:45
*** sshnaidm is now known as sshnaidm|lnch11:47
*** baoli has quit IRC11:48
*** dave-mccowan has quit IRC11:48
*** alexchadin has joined #openstack-meeting-411:52
*** thorst has quit IRC11:52
*** yifei has joined #openstack-meeting-411:52
*** yifei has quit IRC11:57
*** yamamoto has joined #openstack-meeting-412:02
*** yamamoto has quit IRC12:02
*** yamamoto has joined #openstack-meeting-412:09
*** Jeffrey4l has quit IRC12:10
*** thorst has joined #openstack-meeting-412:15
*** dave-mcc_ has quit IRC12:18
*** sdake has joined #openstack-meeting-412:18
*** sdake_ has joined #openstack-meeting-412:22
*** sdake has quit IRC12:23
*** prateek has quit IRC12:24
*** rtheis has joined #openstack-meeting-412:25
*** sshnaidm|lnch is now known as sshnaidm12:25
*** mohankumar has joined #openstack-meeting-412:26
*** portdirect_away is now known as portdirect12:29
*** sdake has joined #openstack-meeting-412:29
*** iurygregory has joined #openstack-meeting-412:29
*** sdake_ has quit IRC12:32
*** alexchadin has quit IRC12:34
*** iberezovskiy|off is now known as iberezovskiy12:35
*** alexchadin has joined #openstack-meeting-412:35
*** portdirect is now known as portdirect_away12:43
*** Jeffrey4l has joined #openstack-meeting-412:43
*** yamamoto has quit IRC12:44
*** baoli has joined #openstack-meeting-412:44
*** yamamoto has joined #openstack-meeting-412:49
*** baoli has quit IRC12:49
*** alexchadin has quit IRC12:59
*** gibi has quit IRC12:59
*** alexchadin has joined #openstack-meeting-412:59
*** yifei has joined #openstack-meeting-413:00
*** bjolo has left #openstack-meeting-413:05
*** portdirect_away is now known as portdirect13:09
*** tuan_luong has joined #openstack-meeting-413:09
*** lamt has quit IRC13:12
*** alexchadin has quit IRC13:13
*** mohankumar has quit IRC13:14
*** limao has joined #openstack-meeting-413:14
*** yamamoto has quit IRC13:15
*** lihi has quit IRC13:16
*** asettle has joined #openstack-meeting-413:22
*** ishafran has quit IRC13:26
*** watanabe_isao has joined #openstack-meeting-413:27
*** prateek has joined #openstack-meeting-413:31
*** limao has quit IRC13:34
*** dtardivel has quit IRC13:34
*** limao has joined #openstack-meeting-413:35
*** zaneb has quit IRC13:36
*** noama has joined #openstack-meeting-413:37
*** portdirect has quit IRC13:38
*** alraddarla_ has joined #openstack-meeting-413:39
*** zaneb has joined #openstack-meeting-413:39
*** noama has left #openstack-meeting-413:39
*** mattmceuen_away has joined #openstack-meeting-413:44
*** yamamoto has joined #openstack-meeting-413:44
*** baoli has joined #openstack-meeting-413:45
*** tuan_luong has quit IRC13:49
*** woodard has joined #openstack-meeting-413:50
*** mattmceuen_away is now known as mattmceuen13:50
*** woodard has quit IRC13:50
*** woodard has joined #openstack-meeting-413:50
*** baoli has quit IRC13:50
*** uck has joined #openstack-meeting-413:51
*** limao_ has joined #openstack-meeting-413:52
*** diga has joined #openstack-meeting-413:55
*** limao has quit IRC13:56
*** yedongcan has joined #openstack-meeting-413:56
*** ivc_ has joined #openstack-meeting-413:56
*** vikasc has joined #openstack-meeting-413:58
*** Julien-zte has joined #openstack-meeting-413:59
*** mchiappero has joined #openstack-meeting-413:59
*** lmdaly has joined #openstack-meeting-414:00
*** pc_m has joined #openstack-meeting-414:01
*** irenab has left #openstack-meeting-414:02
*** irenab has joined #openstack-meeting-414:02
*** garyloug has joined #openstack-meeting-414:03
*** apuimedo has joined #openstack-meeting-414:03
apuimedo#startmeeting kuryr14:03
openstackMeeting started Mon Dec 19 14:03:48 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: kuryr)"14:03
openstackThe meeting name has been set to 'kuryr'14:03
apuimedoHello everybody and welcome to another weekly IRC meeting!14:03
apuimedoWho's here?14:04
ivc_\o/14:04
janonymouso/14:04
alraddarla_o/14:04
mattmceueno/14:04
irenabhi14:04
yedongcano/14:04
limao_o/14:04
digao/14:04
mchiapperoo/14:04
garylougo/14:04
vikasco/14:04
apuimedoThat's a nice attendance :-)14:04
apuimedo#topic kuryr-libnetwork14:05
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:05
*** hongbin has joined #openstack-meeting-414:05
hongbino/14:05
apuimedoAlright then, let's get started14:05
apuimedoWe got some nice fixes last week14:06
apuimedoI want to draw attention to one in particular from yedongcan14:07
apuimedohttps://review.openstack.org/40459114:07
apuimedo#link https://review.openstack.org/40459114:07
apuimedothanks for the patch yedongcan!14:07
yedongcanapuimedo: you're welcome14:08
apuimedoheh, I actually wanted to talk about https://review.openstack.org/#/c/401874/514:08
apuimedosorry about that14:08
apuimedoI copied the wrong link14:08
apuimedo:-)14:09
apuimedo#link https://review.openstack.org/#/c/401874/514:09
apuimedothis was merged the previous week14:09
apuimedoand it solved an ipam address release issue14:09
*** yifei has quit IRC14:09
*** bobh has joined #openstack-meeting-414:09
apuimedomchiappero brought up that this solution poses some difficulty for the ongoing nested work14:10
apuimedo#link https://review.openstack.org/#/c/400365/14:10
apuimedothat would otherwise be pretty ready for merging14:10
apuimedomchiappero: could you please describe the issue14:10
mchiapperoI'm not sure about where the problem is actually originated, but that code ends up returning no subnets for nested containers14:11
*** lamt has joined #openstack-meeting-414:11
mchiapperothat means that neutron ports don't get deleted anymore with nested containers14:12
mchiapperoI'm wondering whether having a subnetpool_id in the subnet is now a requirement14:12
apuimedomchiappero: you mean that after this change, when a port was being used for nested, it can't be deleted, right?14:12
mchiapperoor whether there is another way to refactor that code in order to handle nested containers as well14:13
mchiapperoapuimedo: exactly14:13
mchiapperoit doesn't get deleted by kuryr anymore, of course you can delete it manually14:13
*** limao has joined #openstack-meeting-414:13
yedongcanapuidemo: got it, i had disscuss it with ltomasho, and limao file a bug for this: https://bugs.launchpad.net/kuryr-libnetwork/+bug/165101514:13
openstackLaunchpad bug 1651015 in kuryr-libnetwork "kuryr-libnetwork did not clearn neutron port when use existed neutron network" [Undecided,New]14:13
apuimedo#link https://bugs.launchpad.net/kuryr-libnetwork/+bug/165101514:14
*** cleong has joined #openstack-meeting-414:14
mchiapperowhat would be the best approach in your opinion?14:14
apuimedoyedongcan: I just 'confirmed' the bug14:15
*** limao_ has quit IRC14:16
apuimedoyedongcan: did you have something in mind to address the bug already?14:17
mchiapperomaybe we can continue offline, but it would be nice to get this sorted14:17
irenabmchiappero: lets try to draft proposal at the bug description board14:18
mchiapperoI guess we have a number of other topic, let's continue on the kuryr channel :)14:18
apuimedomchiappero: we can devote a few more minues14:18
apuimedo:-)14:18
yedongcanI will sort some consideration in the LP, I think this need further discussion.14:19
*** baoli has joined #openstack-meeting-414:19
apuimedoyedongcan: mchiappero: irenab: Agreed14:19
mchiapperoirenab: I don't have a proposal yet, lately I have little time so I could not check the new code, but I'll trye14:19
limaoYes, we can discuss it in channel later14:19
yedongcanit's related neutron existing resource, overlapping cidrs and others.14:20
mchiappero*try14:20
*** uck has quit IRC14:20
apuimedofor now. Maybe we can put the workaround that the network for the VM be created first with Kuryr by running a container14:20
apuimedoand linking the bug in mchiappero's patch14:20
apuimedothis would be enough to allow us to merge mchiappero's patch IMHO, since it is not introducing a problem, just experiencing it harder14:20
*** sdake_ has joined #openstack-meeting-414:20
apuimedosince the normal flow to try nested is to create Nova instances on end user created neutron nets14:21
apuimedodo you all agree with that?14:21
irenabapuimedo: sounds reasonable14:21
mchiapperook by me14:22
yedongcanAgree.14:22
apuimedomchiappero: I'll push an update of your patch with a link to the bug14:22
apuimedothen I'll +214:22
mchiapperothank you14:22
apuimedoand ping irenab and vikasc for review14:22
apuimedo#topic kuryr-kubernetes14:22
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:22
apuimedo#info ivc_ made a very nice demo of the services patch https://asciinema.org/a/51qn06lgz78gcbzascpl2du4w14:23
apuimedoThanks a lot for that ivc_14:23
ivc_aye14:23
mchiapperoregarding the patch, the unit tests should be ok now, maybe some mock instances could be reused, anyone willing to have a look and improve is very welcome14:23
janonymous+114:23
*** sdake has quit IRC14:23
apuimedoas a reminder, this patch is not meant to be merged right now14:24
apuimedorather, it should be split into smaller patches14:24
apuimedoso with master code you can't replicate the demo just yet14:24
ivc_apuimedo in that thread http://lists.openstack.org/pipermail/openstack-dev/2016-December/109163.html14:24
apuimedo#info irenab posted a WIP patch for adding OVS native support https://review.openstack.org/#/c/412215/14:25
*** baoli has quit IRC14:25
ivc_Alexander Stafeyev has a good point that we dont have a very informative user-facing docs14:25
apuimedoup until now we only have ovs hybrid14:25
irenabit is missing unit tests, but please review/try it is you have time14:25
apuimedo#info irenab reports ovs native ~ 2x pod creation burst speed performance improvement when using ovs-native binding with Dragonflow14:26
ivc_irenab i've skimmed over that patch and it does look good, but i've not tested it yet14:26
irenabivc_: docs in general or on k8s?14:26
apuimedoirenab: May I suggest that you put a local.conf.df and a local.conf.ovsnative in devstack plugin dir?14:26
irenabapuimedo: good idea, will add it14:27
apuimedoIt makes things easier for reviewers and people wanting to try it out14:27
apuimedothanks irenab14:27
irenabapuimedo: will post as separate patch14:27
apuimedo#action irenab to add local.conf.df and local.conf.ovsnative to the ovs native WIP patch14:27
ivc_irenab i'm mostly speaking about kuryr-k8s now, i've not checked kuryr-libnetwork docs situation14:27
apuimedodarn14:27
apuimedoput the action too soon14:27
apuimedo:P14:27
apuimedomchiappero: tests can be improved afterwards14:27
apuimedobut let's put it in the list of low hanging fruit for new contributors14:28
ivc_irenab apuimedo also our README.md for kuryr-k8s has some stubs/leftovers from template14:28
irenabivc_: lets add doc item to the critical tasks for the first k8s-kuryr relelase14:28
ivc_^ +114:28
apuimedoagreed14:28
apuimedo#action put README.md and doc fixes for kuryr-kubernetes 1.0.0 milestone14:29
apuimedoI'll be posting a Dockerfile for the controller14:29
*** baoli has joined #openstack-meeting-414:29
ivc_apuimedo we also still have some races with docker containers in devstack14:30
apuimedoso we can have automatically built Docker containers of the controller14:30
apuimedoI'm still considering whether making one for kubelet that inherits from hyperkube14:30
irenabivc_: maybe worth to add the demo dockerfile to the repo if someone wants to easily reproduce the demo you did14:30
apuimedoivc_: which?14:30
ivc_apuimedo k8s-controller-manager starts before etcd is fully up and running and crashes14:31
apuimedoirenab: agreed. I propose to make it into contrib14:31
ivc_apuimedo we need some more 'wait_for' there14:31
apuimedoivc_: thanks14:31
apuimedoI thought I had it. Anyways, I have code for that14:31
apuimedoI'll fix it14:31
apuimedo#action apuimedo to add the wait for dependencies in devstack container start14:32
ivc_apuimedo it's not specific, its just that it is racy by its nature of being async with 'run_container'14:32
apuimedoivc_: sure, in the midonet PoC I had it already solved, so it won't be a big deal to move over what I did there14:32
apuimedo#info vikasc posted a patch for bringing nested vlan vifs to kuryr-kubernets14:33
apuimedo#link https://review.openstack.org/#/c/410578/14:33
apuimedovikasc: looking forward to the new patch set addressing the posted comments :-)14:34
vikasci still need to test changes locally14:34
vikasc:)14:34
*** watanabe_isao has quit IRC14:34
vikascsoon will be updating14:34
apuimedovikasc: no worries. I know you are busy with deployments14:34
apuimedoirenab: vikasc: https://review.openstack.org/#/c/409797/14:35
apuimedolet's have the doc issue solved before it materializes14:35
ivc_vikasc maybe we can have some doc 'how to run kuryr-k8s with nested mode' along with those patch?14:35
apuimedoivc_: agreed14:36
vikascivc_, sure , good idea14:36
apuimedovikasc: please, make it part of the patch, and if it needs some local.conf changes, please, put a sample in devstack/14:36
apuimedoand this goes in general for everybody14:36
vikascapuimedo, ack14:36
apuimedoIt's important to help people reproduce14:36
apuimedo:-)14:36
irenab+114:37
ivc_+114:37
mchiappero+114:37
apuimedoanything else about kuryr-kubernetes?14:37
*** psachin has quit IRC14:37
ivc_apuimedo pete from port-direct suggested that we could have some integration with kolla14:38
apuimedojust as a reminder, some of the more burning items are the /run files for deletion and the fullstack tests14:38
apuimedoivc_: I agree14:38
apuimedoI think this is a very interesting field to explore14:38
apuimedoportdirect did already a similar experiment before14:38
apuimedowith his 'harbor'14:38
ivc_aye14:38
apuimedodo we have anybody here directly interested in deploying openstack over kuryr-kubernetes/kubernetes ?14:39
irenabapuimedo: not sure what it means. Can you please elaborate?14:39
mchiapperome14:39
janonymousi wanna give a try14:39
apuimedosure14:39
apuimedowhat it means is14:39
apuimedoyou deploy keystone and Neutron with K8s hostmode networking14:39
apuimedothen, you deploy kuryr-kubernetes too in hostmode14:40
apuimedopointing to the aforementioned services14:40
apuimedofrom then on, the rest of OSt services, get deployed with kuryr/neutron providing the networking14:40
apuimedoand potentially having a driver for having each service in a different subnet14:40
apuimedo(by namespace)14:41
apuimedodepending on the deployer architecture and needs14:41
apuimedothat's why I'm asking for people directly interested14:41
irenabapuimedo: thanks14:41
*** bobh has quit IRC14:41
ivc_apuimedo it's essentially a trippleO, right?14:41
apuimedobecause it'd be nice to have some requirements for the first plugin (set of resource drivers)14:41
apuimedoivc_: quite similar to what it does14:42
apuimedoI believe in harbor case, for example, there was no second level neutron14:42
apuimedothere's a lot of possibilities as to which deployment models you can serve14:42
ivc_apuimedo we need to take ironic case into account too14:43
apuimedoivc_: Indeed14:43
janonymouswith keystone i had a question, is there a need to register kuryr endpoints in keystone also?14:43
apuimedojanonymous: it is not necessary14:43
ivc_janonymous for kuryr-k8s there are no endpoings14:43
apuimedobut it is nice to do14:43
janonymousahh..okay14:43
apuimedoivc_: IIRC in devstack I registered it somewaht14:43
apuimedo*somehow14:43
*** singlethink has joined #openstack-meeting-414:44
apuimedoI don't remember if it is in the master version though14:44
janonymousonly username was registerred14:44
janonymousokay14:44
apuimedoivc_: it will probably end up having an endpoint for reporting14:44
ivc_apuimedo janonymous maybe we'd need to look at k8s integration with OSt keystone14:44
apuimedoand watchdog14:44
apuimedobut that's not the sort of stuff that keystone is interested on14:44
apuimedo:-)14:44
apuimedoivc_: agreed14:45
janonymousyeah,14:45
ivc_i mean k8s already has it, we just need to leverage it14:45
*** TxGirlGeek has joined #openstack-meeting-414:45
apuimedoivc_: I think it is an ongoing thing, the k8s keystone support14:45
irenabapuimedo: so the answer that we probably need to register kuryr as a service?14:46
*** prateek has quit IRC14:46
apuimedoalright then. As I said, please, let's use ivc_'s started thread on the ML that portdirect answered to to move this forward14:46
apuimedoirenab: 'need' is a strong word14:46
apuimedoI think we should in general register the service14:47
apuimedobut we do not have it as a hard requirement14:47
apuimedonor are we likely to leverage it in this cycle14:47
ivc_apuimedo we might eventually get to the point where kuryr-k8s has some restapi14:47
apuimedoivc_: I was hinting at that14:48
ivc_apuimedo but imo thats not gonna happen before 1.0.0 release14:48
irenabapuimedo: for libnetwork it is not needed, correct?14:48
apuimedofor reports, watchdogs, (even for split daemon duty made by the controller)14:48
apuimedoirenab: for libnetwork you can have a service without endpoints too14:48
apuimedobut with our model, putting endpoints wouldn't work14:48
apuimedook, let's move on14:49
apuimedo#topic fuxi14:49
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:49
*** trozet_ is now known as trozet14:49
hongbinhi14:49
apuimedohongbin: thanks for reaching out to cinder go14:49
apuimedo#chair hongbin14:49
openstackCurrent chairs: apuimedo hongbin14:49
hongbinapuimedo: my pleasure14:49
apuimedoyou have the floor14:49
hongbinapuimedo mentioned that i just sent a ML to jhon grifft for hte ciinder docker driver14:50
hongbinwe agreed to consolidate the effort into one (sort-of)14:50
hongbini think this is a good news, i will reach out to him about that14:50
hongbinnext one is14:51
apuimedoit definitely is good news14:51
hongbinThe fuxi is switching to keystone v314:51
apuimedohongbin: please, use 'info'14:51
apuimedohongbin: do you think you can reuse some of the openstack/kuryr library code for the keystone v3 support?14:51
*** prateek has joined #openstack-meeting-414:51
hongbinapuimedo: not sure exactly, need to look into that14:52
hongbin#info The fuxi is switching to keystone v314:52
apuimedohongbin: please do14:52
hongbinapuimedo: here is the patch i proposed14:52
apuimedoif we can reuse code, all the better14:52
hongbin#link https://review.openstack.org/#/c/410403/14:52
hongbin#link https://review.openstack.org/#/c/409982/14:52
hongbin#action hongbin look into how to resue keystone v3 code in kuryr lib14:52
hongbinapuimedo: however, we need to merge the v3 patches above to pass the gate14:53
apuimedohongbin: understood14:53
apuimedoI'll take it into account for the reviews14:53
hongbinThe non-voting fullstack pipeline is complainting14:53
hongbinapuimedo: thx14:53
hongbinHere is a few fullstack tests patch:14:54
hongbin#link https://review.openstack.org/#/c/403931/14:54
hongbin#link https://review.openstack.org/#/c/403941/14:54
hongbinIn addition, we need to get hte lastest requirement14:54
hongbin#link https://review.openstack.org/#/c/373745/14:54
hongbinneed to merge the patch above as well14:54
apuimedogood14:55
hongbinthose are important items last week, there are a few fixes as well14:55
hongbin#link https://review.openstack.org/#/c/408845/14:55
hongbin#link https://review.openstack.org/#/c/409968/14:55
hongbinthe last thing is i submitted a patch to docker upstream to list fuxi in their docs14:55
hongbin#link https://github.com/docker/docker/pull/2946814:55
hongbinapuimedo: that is all from my side14:55
apuimedothanks hongbin14:56
apuimedo#topic general14:56
*** openstack changes topic to "general (Meeting topic: kuryr)"14:56
apuimedoAny other topic, issue, comment from anybody?14:56
alraddarla_https://review.openstack.org/#/c/405203/  could use one more +2 :)14:56
apuimedoalraddarla_: thanks!14:56
apuimedoIt went under my radar14:56
apuimedowill get to it today14:56
apuimedoanything else?14:56
alraddarla_apuimedo, thanks!14:56
* apuimedo is having mox/mock dreams14:57
apuimedoif I have one more dream of mox appearing like a mushroom amidst a clean forest of mock, I'll take holidays14:57
*** Julien-zte has quit IRC14:58
janonymoushahaha, bye bye mox just 1 more patch for cleanup14:58
alraddarla_hahaha14:58
*** Julien-zte has joined #openstack-meeting-414:58
apuimedoyay!14:58
apuimedoTHank you all for joining!14:58
apuimedo#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Mon Dec 19 14:59:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-12-19-14.03.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-12-19-14.03.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-12-19-14.03.log.html14:59
*** pc_m has left #openstack-meeting-415:02
*** lmdaly has left #openstack-meeting-415:03
*** yedongcan has left #openstack-meeting-415:03
*** Julien-zte has quit IRC15:04
*** limao has quit IRC15:04
*** Julien-zte has joined #openstack-meeting-415:05
*** Julien-zte has joined #openstack-meeting-415:06
*** Julien-zte has quit IRC15:06
*** bobh has joined #openstack-meeting-415:06
*** limao has joined #openstack-meeting-415:06
*** hongbin has quit IRC15:06
*** Julien-zte has joined #openstack-meeting-415:07
*** bobh has quit IRC15:07
*** Julien-zte has quit IRC15:07
*** Julien-zte has joined #openstack-meeting-415:07
*** bobh has joined #openstack-meeting-415:07
*** Julien-zte has quit IRC15:07
*** Julien-zte has joined #openstack-meeting-415:08
*** Julien-zte has quit IRC15:08
*** Julien-zte has joined #openstack-meeting-415:09
*** Julien-zte has quit IRC15:09
*** tovin07_ has joined #openstack-meeting-415:10
*** alraddarla_ has left #openstack-meeting-415:11
*** ivc_ has left #openstack-meeting-415:11
*** bobh has quit IRC15:12
*** limao_ has joined #openstack-meeting-415:22
*** reedip_ has joined #openstack-meeting-415:23
*** limao has quit IRC15:25
*** marst has joined #openstack-meeting-415:34
*** mattmceuen is now known as mattmceuen_away15:36
*** yamamoto has quit IRC15:38
*** aarefiev is now known as aarefiev_afk15:41
*** Syed__ has joined #openstack-meeting-415:42
*** limao has joined #openstack-meeting-415:43
*** baoli has quit IRC15:44
*** prateek has quit IRC15:44
*** baoli has joined #openstack-meeting-415:45
*** limao_ has quit IRC15:45
*** lrensing has joined #openstack-meeting-415:47
*** dtardivel has joined #openstack-meeting-415:49
*** priya__ has joined #openstack-meeting-415:51
*** Sukhdev has joined #openstack-meeting-415:52
*** Sukhdev has quit IRC15:53
*** yamahata has joined #openstack-meeting-415:54
*** lrensing has quit IRC15:54
*** iyamahat has joined #openstack-meeting-415:55
*** lrensing has joined #openstack-meeting-415:56
*** yamahata has quit IRC15:56
*** yamahata has joined #openstack-meeting-415:57
*** Sukhdev has joined #openstack-meeting-415:57
jrollSukhdev: morning16:02
Sukhdevjroll: good morning16:02
joannaevening everyone16:02
*** nishpatwa007 has quit IRC16:03
Sukhdevjroll: having computer issue. Give me a second16:03
* jroll continues staring at the screen16:03
*** yohoffman has quit IRC16:03
*** Sukhdev_ has joined #openstack-meeting-416:03
*** limao_ has joined #openstack-meeting-416:04
TheJuliajroll: Coffee perhaps?16:05
Sukhdev_folks - sorry had to restart the computer at the last second16:05
*** nishpatwa007 has joined #openstack-meeting-416:05
*** dimak has quit IRC16:05
* jroll has had 3 cups already, will wait til after lunch for more :P16:05
Sukhdev_jroll : :_16:06
Sukhdev_:)16:06
*** limao has quit IRC16:06
Sukhdev_#startmeeting ironic_neutron16:06
openstackMeeting started Mon Dec 19 16:06:26 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev_. Information about MeetBot at http://wiki.debian.org/MeetBot.16:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:06
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:06
openstackThe meeting name has been set to 'ironic_neutron'16:06
*** yohoffman has joined #openstack-meeting-416:06
Sukhdev_Good morning everybody16:06
Sukhdev_Sorry for late start because of technical difficulties16:06
Sukhdev_#topic: Agenda16:07
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:07
Sukhdev_#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_December_19.2C_201616:07
* jroll notes sam is out today16:07
*** tovin07_ has quit IRC16:07
Sukhdev_hmm... probably in holiday spirit already :-)16:07
Sukhdev_#topic: Announcements16:08
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:08
*** diga has quit IRC16:08
joannao/16:08
Sukhdev_talking about the holidays - we are heading into holidays16:08
Sukhdev_Next week is Christmas week and following is new year day/eve16:08
Sukhdev_Hence, we will skip meetings for next two weeks16:09
Sukhdev_Next meeting on 9th Jan16:09
Sukhdev_Please take a note of this - hope everybody is OK with that16:09
* jroll won't be here anyway16:10
*** hongbin has joined #openstack-meeting-416:10
* Sukhdev_ will not be here either16:10
Sukhdev_with sambetts out, we may zoom through the agenda real quick16:11
jrollyep16:11
Sukhdev_Another announcement is that Security Group feature is now complete16:11
jroll\o/16:11
Sukhdev_unless somebody feels we need something more for this16:12
jrollnah I think we're good to go16:12
jrollCI testing would be cool, eventually16:12
Sukhdev_I tested it manually and seems to work just fine16:12
jrollmanually doesn't help keep it from breaking later :)16:13
*** mhayden has quit IRC16:13
Sukhdev_jroll : If somebody can give me pointers to the CI part (not familiar) I can take a crack at it16:13
jrollSukhdev_: I'm not sure right this second how we would want to do it16:14
*** pcaruana has quit IRC16:15
Sukhdev_jroll : we can discuss it in the next meeting - when everybody is here and the year will be new :-)16:15
*** spotz_zzz has quit IRC16:15
jrollyep16:15
Sukhdev_Moving right along -16:15
Sukhdev_#topic: Port Groups16:15
*** openstack changes topic to ": Port Groups (Meeting topic: ironic_neutron)"16:15
Sukhdev_This looks like there - I see two patches in merge conflict16:16
Sukhdev_#link: https://review.openstack.org/#/q/topic:bug/161875416:16
vdrokon the ironic side everything is ready I think16:16
*** spotz_zzz has joined #openstack-meeting-416:16
vdrokthere is a patch for osc support left https://review.openstack.org/36213016:17
jrollnice!16:17
Sukhdev_very good16:17
vdrokand I'll try to add a mode/properties fields to client too today/tomorrow, that should be easy16:17
vdrokthen we're ready to do the nova side16:17
Sukhdev_thank vdrok16:18
Sukhdev_thanks16:18
vdrokjroll: do we also need a release of client so that nova sees the changes? or it installs client from master?16:19
jrollvdrok: yes, we will16:19
jrollwhich is easy :)16:19
vdrokyup, ok16:19
jrollthough releases aren't happening next week (this week is fine)16:19
vdrokok, then I'll prioritize finishing client :)16:19
jrollcool, thanks!16:20
jrollyou can do weird depends-on stuff to test the nova bits, though16:20
jrollwe also said nova should wait for the attach/detach stuff, because it simplifies it so much16:20
vdrokwith install_libs_from_git things>16:20
vdrok?16:20
jrollyep16:20
*** mattmceuen_away is now known as mattmceuen16:21
jrollsomething like LIBS_FROM_GIT+=',ironic-lib' and IRONIC_LIB_BRANCH=master or so16:21
jrolldon't remember the exact details16:21
vdrokyeah, I've done that once I think16:22
jrollcool16:22
* jroll thinks we're done with this section16:22
Sukhdev_good - thanks16:23
Sukhdev_#topic: Interface attach API16:23
*** openstack changes topic to ": Interface attach API (Meeting topic: ironic_neutron)"16:23
vdrokvsaienko has pushed some updates. basically that's mostly ok16:24
Sukhdev_I see updated patches this morning - so looks like sambetts is working on these16:24
vdroksome small things left16:24
Sukhdev_#link: https://review.openstack.org/#/q/topic:+bug/158218816:24
*** zenoway has quit IRC16:24
jrollvsaienko is working on it while sam is out16:24
*** limao has joined #openstack-meeting-416:25
Sukhdev_oh - did not see who pushed the patch :-)16:25
jrollbut yeah, they're making progress16:25
Sukhdev_this is progressing well16:25
Sukhdev_neither of them is here to discuss anything here16:26
*** iberezovskiy is now known as iberezovskiy|off16:26
Sukhdev_#topic: VLAN Aware Servers16:27
*** openstack changes topic to ": VLAN Aware Servers (Meeting topic: ironic_neutron)"16:27
jrollnothing since dec 7, but it's blocked on the rest anyway16:27
Sukhdev_we can review the spec though - I did last week - looks good16:27
Sukhdev_I added few comments - but, this is generally good to go16:28
Sukhdev_there were some additional comments which needs to be addressed - based upon the discussion here in the previous meeting16:28
Sukhdev_We can pick it up when everybody is back16:29
*** limao_ has quit IRC16:29
Sukhdev_I have nothing else on the agenda16:29
Sukhdev_#topic: Open Discussion16:29
*** openstack changes topic to ": Open Discussion (Meeting topic: ironic_neutron)"16:29
Sukhdev_anything to cover?16:30
jrollso I have a thing here16:30
jrollthis meeting has basically become a status report16:30
jroll(which is great!)16:30
jrollI'm wondering if we can just roll it into the general ironic meeting16:30
jrollreport in the subteam status reports, put a topic on the agenda if it needs discussion16:30
jrollany thoughts on that?16:31
Sukhdev_you are correct - with most of the things in place, that is not a bad idea16:31
jrollwe can always have ad-hoc meetings on things to dig deeper if needed, too16:32
Sukhdev_+116:32
jrollanyone else have opinions?16:32
jrollotherwise Sukhdev_ can email the mailing list about it and I'm happy to do the patch to the irc meetings repo16:33
jroll(I can do the email, too, if that makes Sukhdev_'s life easier)16:33
Sukhdev_jroll : I can send out the email - no worries16:34
Sukhdev_I can push the patch as well16:34
jrolleven better!16:34
jrollI'll update the main ironic meeting wiki16:34
Sukhdev_The question is - should we have the last meeting on Jan 9 or kill it?16:34
jrollI'm fine either way16:34
jrollprefer the latter but don't have strong objections to one more16:35
Sukhdev_Lets just kill it16:36
jrollsounds good to me16:36
Sukhdev_I have some free cycles later this week and next - I will send the email and push the patch16:36
jrollawesome, thanks Sukhdev_ :)16:37
Sukhdev_Anything else?16:37
Sukhdev_Anybody ?16:37
* jroll has nothing16:37
Sukhdev_looks like we are done16:37
Sukhdev_Thanks everybody16:37
Sukhdev_#endmeeting16:37
jrollty!16:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:37
openstackMeeting ended Mon Dec 19 16:37:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-12-19-16.06.html16:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-12-19-16.06.txt16:38
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-12-19-16.06.log.html16:38
*** Sukhdev_ has quit IRC16:39
*** yamamoto has joined #openstack-meeting-416:39
*** mhayden has joined #openstack-meeting-416:41
*** cinerama has joined #openstack-meeting-416:43
*** cinerama has quit IRC16:44
*** cinerama has joined #openstack-meeting-416:44
*** limao has quit IRC16:48
*** yamamoto has quit IRC16:49
*** limao has joined #openstack-meeting-416:50
*** sshnaidm is now known as sshnaidm|afk16:52
*** klamath has joined #openstack-meeting-416:54
*** limao has quit IRC17:02
*** mattmceuen is now known as mattmceuen_away17:08
*** sdake_ is now known as sdake17:15
*** cleong has quit IRC17:15
*** cleong has joined #openstack-meeting-417:15
*** bobmel_ has quit IRC17:16
*** Zer0Byte__ has joined #openstack-meeting-417:17
*** reedip_ has quit IRC17:21
*** corey_ has joined #openstack-meeting-417:23
*** cleong has quit IRC17:23
*** corey_ is now known as Guest162217:24
*** bobmel has joined #openstack-meeting-417:25
*** SergeyLukjanov__ has quit IRC17:34
*** SergeyLukjanov has joined #openstack-meeting-417:35
*** bobmel_ has joined #openstack-meeting-417:37
*** bobmel has quit IRC17:38
*** sshnaidm|afk has joined #openstack-meeting-417:40
*** bobmel has joined #openstack-meeting-417:45
*** bobmel_ has quit IRC17:46
*** Swami has joined #openstack-meeting-417:52
*** garyloug has quit IRC17:55
*** bobmel_ has joined #openstack-meeting-417:57
*** bobmel has quit IRC17:59
*** iyamahat has quit IRC18:00
*** unicell1 has quit IRC18:00
*** priya__ has quit IRC18:00
*** yamahata has quit IRC18:01
*** klamath has quit IRC18:04
*** pbourke has quit IRC18:06
*** Jeffrey4l has quit IRC18:07
*** iyamahat has joined #openstack-meeting-418:22
*** armax has joined #openstack-meeting-418:25
*** unicell has joined #openstack-meeting-418:34
*** vishnoianil has quit IRC18:35
*** matrohon has joined #openstack-meeting-418:36
*** yamahata has joined #openstack-meeting-418:40
*** baoli has quit IRC18:59
*** baoli has joined #openstack-meeting-419:00
*** emagana has joined #openstack-meeting-419:00
*** s3wong has joined #openstack-meeting-419:01
*** anilvenkata has quit IRC19:06
*** kylek3h is now known as kylek3h_19:08
*** britthouser has quit IRC19:13
*** britthouser has joined #openstack-meeting-419:13
*** david-lyle_ has joined #openstack-meeting-419:13
*** Sukhdev has quit IRC19:13
*** jamespag` has joined #openstack-meeting-419:13
*** jamespag` has quit IRC19:13
*** jamespag` has joined #openstack-meeting-419:13
*** david-lyle has quit IRC19:13
*** jamespage has quit IRC19:13
*** openstack has joined #openstack-meeting-419:16
*** ChanServ sets mode: +o openstack19:16
*** matrohon has quit IRC19:20
*** armax has quit IRC19:21
*** vishnoianil has joined #openstack-meeting-419:26
*** sshnaidm|afk is now known as sshnaidm19:29
*** armax has joined #openstack-meeting-419:31
*** baoli has quit IRC19:32
*** baoli has joined #openstack-meeting-419:32
*** portdirect has joined #openstack-meeting-419:50
*** bobmel has joined #openstack-meeting-420:02
*** bobmel_ has quit IRC20:02
*** breton_ is now known as breton20:04
*** TxGirlGeek has quit IRC20:08
*** TxGirlGeek has joined #openstack-meeting-420:10
*** dtardivel has quit IRC20:14
*** palendae has left #openstack-meeting-420:24
*** Sukhdev has quit IRC20:33
*** sshnaidm is now known as sshnaidm|afk20:33
*** TxGirlGeek has quit IRC20:38
*** reedip_ has joined #openstack-meeting-420:39
*** TxGirlGeek has joined #openstack-meeting-420:39
*** iurygregory has quit IRC20:42
*** yfauser has quit IRC20:44
*** yfauser has joined #openstack-meeting-420:45
*** baoli has quit IRC20:48
*** yfauser has quit IRC20:49
*** rockyg has joined #openstack-meeting-421:02
*** yfauser has joined #openstack-meeting-421:03
*** galstrom_zzz is now known as galstrom21:04
*** baoli has joined #openstack-meeting-421:04
*** yfauser has quit IRC21:08
*** rtheis has quit IRC21:13
*** Guest1622 has quit IRC21:18
*** emagana has quit IRC21:21
*** klamath has joined #openstack-meeting-421:22
*** emagana has joined #openstack-meeting-421:24
*** l4yerffeJ_ has joined #openstack-meeting-421:33
*** l4yerffeJ has quit IRC21:35
*** galstrom is now known as galstrom_zzz21:35
*** thorst has quit IRC21:46
*** thorst has joined #openstack-meeting-421:46
*** galstrom_zzz is now known as galstrom21:48
*** TxGirlGeek has quit IRC21:51
*** TxGirlGeek has joined #openstack-meeting-421:51
*** thorst has quit IRC21:55
*** bobh has joined #openstack-meeting-421:56
*** TxGirlGeek has quit IRC21:56
*** bobh has quit IRC21:58
*** dave-mccowan has joined #openstack-meeting-422:02
*** yfauser has joined #openstack-meeting-422:04
*** TxGirlGeek has joined #openstack-meeting-422:05
*** dave-mccowan has quit IRC22:07
*** yfauser has quit IRC22:09
*** Sukhdev has joined #openstack-meeting-422:10
*** dave-mccowan has joined #openstack-meeting-422:10
*** klamath has quit IRC22:13
*** TxGirlGeek has quit IRC22:13
*** lrensing has quit IRC22:28
*** baoli has quit IRC22:29
*** galstrom is now known as galstrom_zzz22:46
*** thorst has joined #openstack-meeting-422:52
*** reedip_ has quit IRC22:55
*** Swami has quit IRC22:56
*** baoli has joined #openstack-meeting-422:56
*** TxGirlGeek has joined #openstack-meeting-422:57
*** thorst has quit IRC23:00
*** baoli has quit IRC23:01
*** sdake has quit IRC23:02
*** hippiepete has quit IRC23:03
*** rockyg has quit IRC23:05
*** yfauser has joined #openstack-meeting-423:06
*** yfauser has quit IRC23:11
*** singlethink has quit IRC23:25
*** neiljerram has quit IRC23:27
*** neiljerram has joined #openstack-meeting-423:27
*** TxGirlGeek has quit IRC23:29
*** lamt has quit IRC23:32
*** Sukhdev has quit IRC23:34
*** JRobinson__ has joined #openstack-meeting-423:37
*** vishnoianil has quit IRC23:38
*** dave-mccowan has quit IRC23:50
*** thorst has joined #openstack-meeting-423:57
*** Sukhdev has joined #openstack-meeting-423:59

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