Monday, 2016-11-07

*** yifei has quit IRC00:00
*** yifei has joined #openstack-meeting-400:03
*** thorst_ has joined #openstack-meeting-400:38
*** yamahata has joined #openstack-meeting-400:40
*** bobmel has quit IRC00:42
*** thorst_ has quit IRC00:43
*** tovin07 has joined #openstack-meeting-401:00
*** limao has joined #openstack-meeting-401:01
*** limao has quit IRC01:02
*** limao has joined #openstack-meeting-401:02
*** bobh has joined #openstack-meeting-401:25
*** amotoki has joined #openstack-meeting-401:25
*** zhurong has joined #openstack-meeting-401:26
*** bobh has quit IRC01:30
*** zhurong has quit IRC01:34
*** zhurong has joined #openstack-meeting-401:34
*** amotoki has quit IRC01:34
*** amotoki has joined #openstack-meeting-401:35
*** amotoki has quit IRC01:47
*** amotoki has joined #openstack-meeting-401:51
*** amotoki has quit IRC01:53
*** amotoki has joined #openstack-meeting-401:55
*** bobh has joined #openstack-meeting-402:01
*** amotoki has quit IRC02:03
*** bobh has quit IRC02:05
*** sdake has quit IRC02:08
*** tovin07 is now known as tovin07_02:08
*** tovin07 has joined #openstack-meeting-402:09
*** tovin07_ has quit IRC02:10
*** tovin07 has quit IRC02:10
*** tovin07 has joined #openstack-meeting-402:11
*** tovin07_ has joined #openstack-meeting-402:11
*** sdake has joined #openstack-meeting-402:12
*** thorst_ has joined #openstack-meeting-402:12
*** gongysh has joined #openstack-meeting-402:12
*** tovin07__ has joined #openstack-meeting-402:12
*** tovin07__ has quit IRC02:13
*** tovin07_ has quit IRC02:13
*** tovin07_ has joined #openstack-meeting-402:13
*** tovin07__ has joined #openstack-meeting-402:13
*** tovin07__ has quit IRC02:13
*** tovin07_ has quit IRC02:13
*** tovin07_ has joined #openstack-meeting-402:14
*** tovin07_ has quit IRC02:15
*** tovin07_ has joined #openstack-meeting-402:16
*** tovin07 has quit IRC02:16
*** tovin07_ is now known as tovin0702:16
*** thorst_ has quit IRC02:17
*** tovin07 is now known as tovin07_02:17
*** thorst_ has joined #openstack-meeting-402:17
*** tovin07_ is now known as tovin0702:18
*** tovin07 has quit IRC02:18
*** tovin07 has joined #openstack-meeting-402:18
*** tovin07_ has joined #openstack-meeting-402:19
*** amotoki has joined #openstack-meeting-402:23
*** baoli has quit IRC02:25
*** baoli has joined #openstack-meeting-402:26
*** thorst_ has quit IRC02:28
*** baoli has quit IRC02:28
*** baoli has joined #openstack-meeting-402:28
*** thorst_ has joined #openstack-meeting-402:28
*** armax has quit IRC02:33
*** baoli has quit IRC02:37
*** thorst_ has quit IRC02:37
*** bobh has joined #openstack-meeting-402:38
*** baoli has joined #openstack-meeting-402:39
*** tonytan4ever has quit IRC02:39
*** armax has joined #openstack-meeting-402:49
*** bobmel has joined #openstack-meeting-402:54
*** armax has quit IRC02:55
*** bobmel has quit IRC02:58
*** baoli has quit IRC03:01
*** bobh has quit IRC03:03
*** bobh has joined #openstack-meeting-403:05
*** bobh has quit IRC03:06
*** dave-mccowan has quit IRC03:09
*** julim_ has joined #openstack-meeting-403:26
*** thorst_ has joined #openstack-meeting-403:26
*** julim has quit IRC03:28
*** thorst_ has quit IRC03:28
*** thorst_ has joined #openstack-meeting-403:28
*** amotoki has quit IRC03:30
*** gongysh has quit IRC03:36
*** thorst_ has quit IRC03:37
*** amotoki has joined #openstack-meeting-403:40
*** links has joined #openstack-meeting-403:55
*** coolsvap has joined #openstack-meeting-404:10
*** sdake has quit IRC04:21
*** baoli has joined #openstack-meeting-404:25
*** baoli has quit IRC04:30
*** thorst_ has joined #openstack-meeting-404:35
*** thorst_ has quit IRC04:42
*** prateek has joined #openstack-meeting-404:54
*** prateek has quit IRC04:54
*** GB21 has joined #openstack-meeting-405:03
*** limao has quit IRC05:13
*** limao has joined #openstack-meeting-405:13
*** Jeffrey4l has joined #openstack-meeting-405:21
*** GB21 has quit IRC05:25
*** GB21 has joined #openstack-meeting-405:37
*** thorst_ has joined #openstack-meeting-405:40
*** janki has joined #openstack-meeting-405:43
*** anilvenkata has joined #openstack-meeting-405:44
*** thorst_ has quit IRC05:47
*** trinaths has joined #openstack-meeting-405:48
*** armax has joined #openstack-meeting-405:53
*** bobmel has joined #openstack-meeting-405:54
*** mohankumar has joined #openstack-meeting-405:57
*** armax has quit IRC05:58
*** bobmel has quit IRC05:58
*** numans has joined #openstack-meeting-406:01
*** xuao has joined #openstack-meeting-406:02
*** amotoki has quit IRC06:03
*** xuao has quit IRC06:06
*** yfauser has joined #openstack-meeting-406:09
*** eyalb has joined #openstack-meeting-406:16
*** yfauser has quit IRC06:32
*** thorst_ has joined #openstack-meeting-406:46
*** thorst_ has quit IRC06:53
*** amotoki has joined #openstack-meeting-406:53
*** armax has joined #openstack-meeting-406:55
*** irenab has joined #openstack-meeting-406:56
*** trinaths has left #openstack-meeting-406:57
*** armax has quit IRC07:00
*** berendt has joined #openstack-meeting-407:00
*** berendt has quit IRC07:00
*** berendt has joined #openstack-meeting-407:01
*** amotoki has quit IRC07:08
*** gongysh has joined #openstack-meeting-407:12
*** pcaruana has joined #openstack-meeting-407:17
*** Jeffrey4l has quit IRC07:18
*** limao has quit IRC07:19
*** amotoki has joined #openstack-meeting-407:21
*** amotoki has quit IRC07:22
*** amotoki has joined #openstack-meeting-407:22
*** limao has joined #openstack-meeting-407:25
*** mohankumar has quit IRC07:43
*** GB21 has quit IRC07:45
*** belmoreira has joined #openstack-meeting-407:46
*** thorst_ has joined #openstack-meeting-407:50
*** ad_rien_ has joined #openstack-meeting-407:55
*** armax has joined #openstack-meeting-407:56
*** thorst_ has quit IRC07:57
*** armax has quit IRC08:00
*** Julien-zte has joined #openstack-meeting-408:00
*** Julien-zte has quit IRC08:01
*** Julien-zte has joined #openstack-meeting-408:01
*** ad_rien_ has quit IRC08:09
*** dtardivel has joined #openstack-meeting-408:12
*** Jeffrey4l has joined #openstack-meeting-408:17
*** baoli has joined #openstack-meeting-408:18
*** bobmel has joined #openstack-meeting-408:21
*** matrohon has joined #openstack-meeting-408:22
*** baoli has quit IRC08:23
*** bobmel has quit IRC08:25
*** ddellav has quit IRC08:28
*** shaohe_feng has quit IRC08:29
*** ddellav has joined #openstack-meeting-408:29
*** shaohe_feng has joined #openstack-meeting-408:30
*** alex_xu has quit IRC08:30
*** mohankumar has joined #openstack-meeting-408:32
*** betherly has joined #openstack-meeting-408:34
*** myatsenko has joined #openstack-meeting-408:36
*** alex_xu has joined #openstack-meeting-408:37
*** rajivk has joined #openstack-meeting-408:46
*** ddellav has quit IRC08:48
*** mohankumar has quit IRC08:49
*** ddellav has joined #openstack-meeting-408:49
*** GB21 has joined #openstack-meeting-408:53
*** thorst_ has joined #openstack-meeting-408:55
*** jingting has left #openstack-meeting-408:56
*** xiaohhui has joined #openstack-meeting-408:56
*** armax has joined #openstack-meeting-408:57
*** zenoway has joined #openstack-meeting-408:59
*** lihi has joined #openstack-meeting-408:59
*** oanson has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Nov  7 09:00:44 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. Who's here for the meeting?09:00
lihiHi09:00
xiaohhuihello,09:01
rajivkHi09:01
*** dimak has joined #openstack-meeting-409:01
oansonLet's wait another minute, maybe nick-ma and yuli will also join.09:01
dimakHello09:01
nick-ma_hi all09:01
*** armax has quit IRC09:02
*** thorst_ has quit IRC09:02
*** yuli_s has joined #openstack-meeting-409:02
yuli_shello09:02
oansonAll right. We can begin09:02
oanson#topic Ocata Roadmap09:02
*** openstack changes topic to "Ocata Roadmap (Meeting topic: Dragonflow)"09:02
oansonLet's start with a very quick status update.09:03
oansonOpenstack-ansible deployment is coming along nicely. You can see it here: https://review.openstack.org/#/c/391524/09:03
oansonGreat thanks to the openstack-ansible guys who practically wrote all of it (I only stitched it together)09:04
*** yuval has joined #openstack-meeting-409:04
xiaohhuiGood to know that09:04
yuvalhey09:04
oansonAbout the other items I suggest to wait for next week.09:04
*** Julien-zte has quit IRC09:04
oansonI would be happy if anyone working on new features would upload a spec in time for next week's meeting, so that it could be discussed.09:05
oansonAccording to the relase timetable, we are supposed to have specs up by the end of next week.09:05
oanson(I hope we can make it (: )09:05
oansonrelease*09:05
dimakI will have SFC spec up for review today09:05
oansonGreat. Thanks!09:05
*** ntr0py has joined #openstack-meeting-409:06
nick-ma_about the release, dragonflow releases independently. do we need to release a version for N cycle?09:06
oansonnick-ma_, I thought I have. I released version 2.0.0.09:07
nick-ma_oho, got it.09:07
oansonIf it didn't register as N cycle release, I'll have to go back and fix it09:07
oansonAdditionally, I plan to move us to the Openstack release cycle09:07
*** jingting has joined #openstack-meeting-409:07
nick-ma_i see the tags, but not branch.09:07
oansonI want to see how this and next week go, before I finalise it09:07
*** oshidoshi has joined #openstack-meeting-409:07
oansonnick-ma_, then I'll look into it09:08
oanson#action oanson Branch out N cycle version from tag 2.0.009:08
oansonNext on the roadmap talk is the a couple of blueprints: Controller HA, Services' status, and monitoring and notification09:08
nick-ma_it is a big change and we will have a fixed cycle.09:08
oansonYes09:08
nick-ma_if we follow the openstack.09:08
oansonI think the project is mature enough to manage09:09
oansonUnless there are objections09:09
oansonIn fact, if there are objections, now would be a good time to bring them up and discuss. If this may be a bad idea, I would like to know :)09:10
nick-ma_there is a bp about chassis status report. what about service status? health check? maybe we need to make them together to prevent from duplicate work?09:10
*** hujie has joined #openstack-meeting-409:11
oansonYes. That's a good idea.09:11
xiaohhuiThe chassis status report spec is here https://review.openstack.org/#/c/385719/09:12
nick-ma_yes.09:12
oanson#link Chassis status report spec patch https://review.openstack.org/#/c/38571909:12
rajivkoanson: notification and monitoring, i would like to know more.09:12
oansonrajivk, actually I was hoping you'd share your ideas :)09:12
rajivkokay, i just wanted to say that notification is not in the scope of dragonflow09:13
oansonIn general, Dragonflow should monitor its artifacts, e.g. service health, statistics, etc., and pass that information on (e.g. to ceilometer).09:13
rajivkhowever monitoring can be used for internal scheduling etc.09:13
oansonrajivk, yes. My understanding is that notification is handled in project aodh,09:13
oansonwhich takes its info from ceilometer09:14
oansonBut I assume we have to provide ceilometer with the relevant data09:14
rajivkokay, i think, i misunderstood by notification09:14
rajivki thought notification means notifying user or admin as per our earlier discussion09:14
oansonrajivk, yes. I thought so too...09:14
nick-ma_notify metrics of virtual network.09:15
rajivknotification to other components like ceilometer, congress etc should be there09:15
*** ralonsoh has joined #openstack-meeting-409:15
*** ruriryan has joined #openstack-meeting-409:15
rajivkI agree on notification for openstack component09:15
oansonMaybe we should start over :)09:16
rajivkHelp from other component team might be required, in some scenario's.09:16
rajivkyes09:16
oansonMy understanding is the ceilometer exists to receive monitor information from components. In dragonflow's case: services' health, statistics, etc.09:16
oansonAodh exists to raise alarms, which could be used to take actions, or notify other components or users and admins09:17
nick-ma_neutron will send basic notifications in its api worker.09:17
oansonSo far, am I correct?09:17
oansonnick-ma_, to whom?09:17
nick-ma_ceilometer09:17
rajivkokay, may be we can think, about integration with congress as well.09:18
nick-ma_like starting to create router, create router success/failure.09:18
oansonrajivk, sure.09:18
rajivkMay be congress allow to provide some policy for neutron09:19
rajivkwe will have to provide some mechanism to do the same in Dragonflow.09:19
oansonCongress probably pushes policy using the Neutron API.09:20
oansonSo that should natively reach Dragonflow09:20
oanson(Unless I am wrong)09:20
rajivkSorry, no idea about internal working of congress :(09:20
nick-ma_i have no idea about how the congress works.09:20
nick-ma_me too~09:20
oansonFrom a quick look at their documentation, there is a Neutron Policy Engine. But I don't know how it works internally wither09:21
oansonrajivk, could you do the research?09:21
rajivkI know some who can help me09:21
rajivkfrom congress community09:21
oansonThat would be great!09:21
oansonI suggest you also work with xiaohhui about the service monitor ideas you mentioned the other day. See if you can collaborate on the work he is doing on the chassis status.09:22
rajivkok, i will work with him.09:23
xiaohhui:)09:23
oansonWould you like to talk about controller HA?09:23
rajivkyes09:23
oansonThe floor is yours! :)09:24
rajivkCurrently, if local controller goes down on a compute node than no flows will be added and removed09:24
rajivkAs per discussion with oanson, we can take two approaches to avoid this problem09:25
rajivk1) Add a watch dog, that keeps on monitoring local controller and if it goes down than it tries to restart it.09:25
rajivkIt try a few times(configurable), if it fails everytime then some other node's controller can be notified and from that point ownward09:26
rajivkremote controller takes care of it's own flows as well as failed node's flows.09:26
hujiewhat about deploy two df controllers, master and slave?09:27
rajivkYou mean on the same node.09:27
nick-ma_that doesn't make sense to deploy two same process on the same node.09:27
rajivkhujie, usually if a service fails on one machine then there must be some external factor, which affected it from continuing09:28
rajivktherefore slave will most probably fail09:28
oansonThis is also why the watchdog solution may not be enough09:28
nick-ma_in production, we use watchdog.09:28
hujieindeed we may not consider the HA in full-distributed SDN solution, if the df goes down, the server is also down, but if you consider df goes down and the server works well you can consider deploy two role df controllers09:29
*** karthiks has joined #openstack-meeting-409:29
yuvalSorry to pop in, but if the controller is deployed using kubernetes (kolla-kubernetes?) with health check, why is there a need for a watchdog?09:29
oansonyuval, the watchdog is there to verify the process is still running and behaving correctly. If k8s' health check does that, then that is a watchdog implementation.09:30
rajivkyuval, you are right. In that it might not be required.09:31
oansonBut not all deployments use k8s09:31
oansonw.g. OSA use lxc09:31
oansone.g.*09:31
yuvalsounds like watchdog is a deployment issue not specific to dragonflow09:31
*** markvoelker has quit IRC09:32
rajivkwatchdog is solve the issue of a short misbehaviour of service.09:32
oansonPossibly. We need to know what solutions exist before writing our own09:32
oansonBut the point is what to do if the process fails, and the watchdog can't bring it back up.09:32
rajivkIn that case, we can notify other node's controller to take over and do all the tasks remotely it possible.(Not sure about, whether possible or not)09:33
oansonIn theory, currently, is should be possible, since both ovsdb and the OVS ofproto interface can be connected over the net.09:34
*** zhurong_ has joined #openstack-meeting-409:34
rajivkokay, is there any major challenges to implement it?09:34
rajivkcan you see anything, that can stop us from doing it?(i am new to Dragonflow therefore does not know internal details)09:35
*** zhurong has quit IRC09:35
xiaohhuiHow would other node's controller get the vm of current node? Besides vm, I think other resources don't need to migrate09:35
oansonI suspect the whole thing is a challenge :). But I don't see a technological problem.09:36
yuli_smay be we will consider one df controller to implement all rules on all cns ?09:36
yuli_scomputer nodes09:36
oansonyuli_s, that goes against the dragonflow design. We want to be fully distributed, not migrate back to a central control unit09:36
yuli_swith a failover in this case09:36
oansonthis is only for failover, in case local solutions (e.g. watchdog) fail09:36
*** neiljerram has joined #openstack-meeting-409:36
hujieyuli_s: we are full distributed SDN solution:)09:37
oansonxiaohhui, I think all the necessary information is stored in the OVSDB. If it is still running, the event should be received09:37
oansonWe don't even need to know about the vm. Just how to connect the southbound (OVS/OVSDB) port to the northbound (Neutron DB) port09:38
oansonAnd as far as I know, that information is stored in OVSDB.09:38
yuli_si remember seeing a patch to update the chases table periodically. it can be used for this09:38
yuli_s(to detect failed controller)09:39
hujieif other df to manage remote ovs, it is in-band flow, the OM and data plane is shared,09:39
oansonWe can also try adding a plug-vif driver to nova, which would help when we want to extend beyond vms and beyond ovs. But I don't think we'll make it for Ocata.09:39
nick-ma_when the remote controller takes over the work, it also needs to update its local cache for all the remote topology09:39
oansonAnd tell apart items that belong to the local compute node, and to the HAed compute node09:40
rajivknick-ma_: can you elaborate09:40
nick-ma_rajivk: i can help discuss and review. :-)09:42
rajivkI think, it is good feature.09:42
hujieif df could manage remote ovs, it seems dragonflow is a high distributed ODL\floodlight\onos\ryu..., not full distributed09:42
*** admcleod_ has joined #openstack-meeting-409:42
rajivknick-ma_: i would a lot of help and discussion. Thanks.09:43
xiaohhuiI agree with hujie09:43
oansonrajivk, the local DF controller holds an in-memory cache of the database objects. We try to have it as small as possible. In case of HA, we need to read the information of the other compute node into the cache09:43
oansonhujie, xiaohhui, this feature is for fallback only. There should be a dragonflow local controller on every node.09:43
*** admcleod has quit IRC09:43
rajivkwhat about supporting distributed cache as well like memcache?09:43
nick-ma_yes, HA is an exception for centralization. we can run HA for all the compute nodes, but that doesn't make sense to deploy in production.09:43
oansonBut it is possible it will crash, and it might be possible that the watchdog won't be able to raise it again.09:43
*** betherly has quit IRC09:44
nick-ma_we do have a distributed data store.09:44
oansonThe local cache is just to speed up reads from that data store.09:44
nick-ma_if we need distributed cache, we just remove the local cache layer. that's all.09:44
nick-ma_every read will go to db layer.09:45
rajivkhmm, i got it.09:45
oansonrajivk, additionally, the data store layer is fully pluggable. If we want to use specifically memcache, a driver can be written09:46
rajivki just said it for caching remote machine's info.09:46
rajivkBut i think, i did not understand that much about Dragonflow. May be i will discuss about it later on.09:47
oansonNo worries. I was just showing off our pluggability :)09:47
oansonrajivk, sure.09:47
oansonI am always available (if not in IRC, then by mail)09:47
rajivkoanson, okay thanks.09:48
oansonI would ask that you let me know what you want to implement, and that you upload a spec so that we'll have it organised.09:48
oansonBut that can be done later09:48
rajivkokay, i will discuss and let you know on IRC.09:49
oansonGreat. Thanks!09:49
oansonAnything else for roadmap?09:49
rajivkI have created a bp09:50
rajivkit is not a feature but now other components are also centerlizing configurations09:50
rajivkthat's it from my side.09:50
yuli_soanson, u wnat to talk about ml2 and dumping plugin ?09:51
yuli_soanson, you want to talk about ml2 and dumping plugin.py ?09:51
*** tovin07 has quit IRC09:51
oansonrajivk, I brushed over the spec. Seems like a good idea. I think nick-ma_ started working on something like.09:51
oansonUsing oslo config generation09:52
oansonyuli_s, not sure what you mean. Could you please explain?09:52
nick-ma_yes, that was done. centralized configuration is also welcomed. please share the spec link here. i can catch up.09:53
oansonrajivk, done in this patch: https://review.openstack.org/#/c/373796/09:53
yuli_sfor the Ocata release do we want to swithc completely to ml2 and dump old plugin support09:53
oanson#link Centralised configuration blueprint https://blueprints.launchpad.net/dragonflow/+spec/centralize-config-options09:53
yuli_s?09:53
oansonyuli_s, yes.09:53
*** tovin07_ has quit IRC09:53
oansonIt is not urgent, but it should be done within the 4-6 weeks.09:53
yuli_sok,\09:54
oansonI can do that, seeing as it's just deleting a couple of files09:54
xiaohhuiI have this work https://bugs.launchpad.net/dragonflow/+bug/1618792 which might similar to dumping plugin.py09:54
openstackLaunchpad bug 1618792 in DragonFlow "RFE: Use ml2 as default option for devstack" [Wishlist,In progress] - Assigned to Hong Hui Xiao (xiaohhui)09:54
*** bogdando has quit IRC09:54
oansonxiaohhui, this is an important step in the way. Yes.09:55
*** sdake has joined #openstack-meeting-409:55
oansonBut it looks like it's merged :)09:55
xiaohhuiI plan to add more code for it,09:55
xiaohhuicurrently it is just update the sample local.conf files09:56
oansonYou want dragonflow's plugin.sh to set the variables by default?09:56
xiaohhuiyes,09:56
oansonxiaohhui, sounds good!09:56
yuli_sgood idea09:56
oansonI also want to discuss https://bugs.launchpad.net/dragonflow/+bug/1638151 . jingting: I added a comment to the bug, could you please reply?09:56
openstackLaunchpad bug 1638151 in DragonFlow "Router schedule error in L3 router plugin as there are multi-external network" [High,New] - Assigned to rajiv (rajiv-kumar)09:56
oansonIt is the only high priority bug that isn't marked 'in progress'.09:57
rajivkI went through the details for this bug.09:57
*** armax has joined #openstack-meeting-409:57
rajivkI it seems like, during update of the router at neutron side it fails.09:58
xiaohhuiThis is actually the issue that dragonflow don't support multi-external network now.09:58
nick-ma_it uses router scheduler but it failed to do it in dragonflow.09:58
xiaohhuiIf br-ex is configured in neutron, the same exception will report09:58
oansonWe are running out of time.09:59
oansonIf you all could share your information on the bug, we could take it from there09:59
rajivklet's discuss it on IRC channel of Dragonflow09:59
oanson#link https://bugs.launchpad.net/dragonflow/+bug/163815109:59
openstackLaunchpad bug 1638151 in DragonFlow "Router schedule error in L3 router plugin as there are multi-external network" [High,New] - Assigned to rajiv (rajiv-kumar)09:59
oansonrajivk, Sure.09:59
xiaohhuiI want to bring this review out  https://review.openstack.org/#/c/339975/10:00
*** sdake_ has joined #openstack-meeting-410:00
oansonThanks everyone for coming. We can continue in #openstack-dragonflow .10:00
*** thorst_ has joined #openstack-meeting-410:00
xiaohhuiIt is legacy from N release10:00
xiaohhuiOK10:00
oansonxiaohhui, one we have a Newton branch (I'll take care of is ASAP), we can back port important patches10:01
oansonI suggest we'll discuss it once the patch is merged into master10:01
oansonThanks again10:01
oanson#endmeeting10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:01
openstackMeeting ended Mon Nov  7 10:01:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-07-09.00.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-07-09.00.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-07-09.00.log.html10:01
*** qwebirc53104 has joined #openstack-meeting-410:01
*** qwebirc53104 has quit IRC10:02
*** armax has quit IRC10:02
*** sdake has quit IRC10:03
*** bauwser is now known as bauzas10:03
*** asettle has joined #openstack-meeting-410:05
*** zhurong_ has quit IRC10:05
*** thorst_ has quit IRC10:07
*** yuval has left #openstack-meeting-410:10
*** asettle has quit IRC10:11
*** asettle has joined #openstack-meeting-410:11
*** yamahata has quit IRC10:11
*** sambetts|afk is now known as sambetts10:12
*** gongysh has quit IRC10:13
*** sdake_ is now known as sdake10:25
*** limao has quit IRC10:38
*** hujie has left #openstack-meeting-410:39
*** irenab has quit IRC10:43
*** eyalb has quit IRC10:44
*** bobmel has joined #openstack-meeting-410:48
*** bobmel has quit IRC10:53
*** eyalb has joined #openstack-meeting-410:59
*** thorst_ has joined #openstack-meeting-411:05
*** ad_rien_ has joined #openstack-meeting-411:12
*** thorst_ has quit IRC11:12
*** ad_rien_ has quit IRC11:13
*** ad_rien_ has joined #openstack-meeting-411:13
*** ad_rien_1 has joined #openstack-meeting-411:18
*** ad_rien_ has quit IRC11:18
*** _degorenko|afk is now known as degorenko11:20
*** markvoelker has joined #openstack-meeting-411:32
*** caowei has joined #openstack-meeting-411:33
*** irenab has joined #openstack-meeting-411:36
*** markvoelker has quit IRC11:38
*** eyalb has quit IRC11:47
*** dimak has quit IRC11:53
*** mohankumar has joined #openstack-meeting-411:54
*** rtheis has joined #openstack-meeting-412:09
*** thorst_ has joined #openstack-meeting-412:10
*** qwebirc34710 has joined #openstack-meeting-412:13
*** thorst_ has quit IRC12:17
*** qwebirc34710 has quit IRC12:19
*** zhurong has joined #openstack-meeting-412:25
*** ad_rien_1 has quit IRC12:27
*** ad_rien_ has joined #openstack-meeting-412:28
*** janonymous has joined #openstack-meeting-412:31
*** yfauser has joined #openstack-meeting-412:40
*** sdake has quit IRC12:40
*** sdake has joined #openstack-meeting-412:40
*** tinwood has quit IRC12:41
*** berendt has quit IRC12:41
*** tinwood has joined #openstack-meeting-412:44
*** GB21 has quit IRC12:46
*** leo_wang has quit IRC12:46
*** Kevin_Zheng has quit IRC12:47
*** leo_wang has joined #openstack-meeting-412:48
*** Kevin_Zheng has joined #openstack-meeting-412:48
*** yuli_s has quit IRC12:48
*** limao has joined #openstack-meeting-412:49
*** thorst_ has joined #openstack-meeting-412:50
*** thorst_ has quit IRC12:50
*** thorst_ has joined #openstack-meeting-412:52
*** limao has quit IRC12:53
*** kylek3h has quit IRC12:57
*** bobh has joined #openstack-meeting-412:59
*** bobh has quit IRC12:59
*** bobh has joined #openstack-meeting-413:00
*** woodard has joined #openstack-meeting-413:02
*** janki has quit IRC13:02
*** limao has joined #openstack-meeting-413:15
*** limao_ has joined #openstack-meeting-413:16
*** limao has quit IRC13:19
*** markvoelker has joined #openstack-meeting-413:21
*** dave-mccowan has joined #openstack-meeting-413:23
*** ddellav has quit IRC13:26
*** bobh has quit IRC13:26
*** ddellav has joined #openstack-meeting-413:27
*** kylek3h has joined #openstack-meeting-413:30
*** kylek3h has quit IRC13:30
*** kylek3h has joined #openstack-meeting-413:30
*** mchiappero has joined #openstack-meeting-413:31
*** bobh has joined #openstack-meeting-413:32
*** links has quit IRC13:40
*** reedip_ has joined #openstack-meeting-413:42
*** vikasc has joined #openstack-meeting-413:44
*** bobh has quit IRC13:45
*** julim_ has quit IRC13:47
*** sdake has quit IRC13:48
*** mohankumar has quit IRC13:51
*** yedongcan has joined #openstack-meeting-413:55
*** uck has joined #openstack-meeting-413:55
*** sshnaidm is now known as sshnaidm|afk13:57
*** amotoki has quit IRC13:58
*** ivc_ has joined #openstack-meeting-413:58
*** lmdaly has joined #openstack-meeting-413:59
*** apuimedo has joined #openstack-meeting-413:59
*** Julien-zte has joined #openstack-meeting-414:00
*** pc_m has joined #openstack-meeting-414:01
*** klamath has joined #openstack-meeting-414:01
*** klamath has quit IRC14:01
*** garyloug has joined #openstack-meeting-414:01
*** caowei has quit IRC14:01
*** klamath has joined #openstack-meeting-414:01
apuimedo#startmeeting kuryr14:02
openstackMeeting started Mon Nov  7 14:02: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:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: kuryr)"14:02
openstackThe meeting name has been set to 'kuryr'14:02
*** lserpietri has joined #openstack-meeting-414:02
apuimedoHello everybody and welcome to another Kuryr weekly IRC meeting14:02
apuimedowho's here to chat?14:02
vikasco/14:02
garylougo/14:02
lmdalyo/14:02
limao_o/14:02
yedongcano/14:02
ivc_o/14:02
*** Drago1 has joined #openstack-meeting-414:03
* pc_m lurking14:03
Drago1o/14:03
*** Drago1 is now known as Drago14:03
*** caowei has joined #openstack-meeting-414:03
apuimedoWelcome everybody!14:03
ltomasboo/14:03
*** baoli has joined #openstack-meeting-414:03
apuimedo#topic kuryr-lib14:03
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:03
apuimedoToday I'll be pushing the new version of the kuryr-lib CNI driver14:04
apuimedomissing still the OVO binding :/14:04
mchiapperoo/14:05
apuimedoanything else on kuryr-lib?14:05
apuimedo#topic kuryr-libnetwork14:06
*** tonytan4ever has joined #openstack-meeting-414:06
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:06
*** oanson has quit IRC14:06
apuimedo#info mchiappero and lmdaly reported a bug in how we handle the creation and deletion of interfaces in libnetwork that impacts us specially when working in container-in-vm mode14:07
irenabsorry for joining late14:07
*** cleong has joined #openstack-meeting-414:07
*** zhurong has quit IRC14:07
apuimedoThe issue is about when we delete and create the virtual devices for the container14:07
apuimedothey report that libnetwork expects deletion on deleteendpoint, whereas we were doing it in 'leave'14:08
irenabapuimedo, link?14:08
apuimedosure14:08
mchiapperomaybe bug is a misleading term14:08
*** amotoki has joined #openstack-meeting-414:09
mchiapperoif you have good contacts with any folk in docker let's check with them14:09
apuimedodarn, can't find the link now14:09
apuimedomchiappero: banix does, but he didn't join today14:09
mchiapperohttps://github.com/docker/libnetwork/issues/152014:09
limao_https://bugs.launchpad.net/neutron/+bug/163918614:09
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)14:09
apuimedolimao_: that's a different one :P14:09
apuimedoplenty of bugs to go around14:10
apuimedo:P14:10
apuimedowe14:10
limao_yeah..14:10
apuimedowe'll get to it14:10
limao_just find..14:10
apuimedoanyway. I'll find it later14:10
mchiapperoI tried once again to ping someone in #docker-network14:10
*** beekneemech is now known as bnemec14:10
mchiapperowithout success14:10
mchiapperotried pinging mrjana14:10
mchiapperonothing14:10
apuimedothe fact of the matter is that libnetwork attempts to move the device after the 'leave'. Which is good because we are supposed to delete the ipvlan/macvlan devices14:10
apuimedoand for that they have to be in the host namespace (so we find them)14:11
apuimedowith veths we do not have the problem14:11
apuimedodue to the fact that if we delete teh host side veth14:11
apuimedothe other one gets removed as well14:11
apuimedoso we got a pass with doing things earlier14:11
janonymouso/14:11
janonymoussorry got late14:12
apuimedoI believe that mchiappero and lmdaly have a patch in the works for solving this14:12
apuimedojanonymous: no worries14:12
apuimedoso I wait eagerly to get it in ;-)14:12
mchiapperowe'll be pushing shortly14:13
apuimedo#action mchiappero lmdaly to push the libnetwork fix for container device deletion ordering14:13
mchiapperothe missing piece is the doc change14:13
apuimedomchiappero: you can definitely put that on a follow up patch14:13
apuimedonow, on to the bug limao mentioned14:13
*** amotoki has quit IRC14:13
apuimedo#link https://bugs.launchpad.net/neutron/+bug/163918614:13
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo)14:13
*** bobmel has joined #openstack-meeting-414:14
apuimedo#info ltomasbo has been checking the vlan-aware-vms neutron reference implementation for completeness14:14
apuimedo#info ltomasbo has found out that Neutron QoS does not get applied to the container subports14:14
*** syed_ has joined #openstack-meeting-414:14
ltomasboyep, and find out that QoS cannot be applied on trunk ports14:14
ltomasboneither parent not subports14:14
irenabDSCP marking as well?14:15
apuimedoltomasbo: I'd rather say 'cannot be applied on trunk ports with the current plumbing'14:15
apuimedo:P14:15
ltomasbodidn't try, but perhaps that will work14:15
apuimedoirenab: that will only affect real hw, won't it?14:15
irenabI just think saying QoS cannot be applied to trunk ports is too generic14:16
apuimedo(and possibly customized tc rules at the host's egress, of coure)14:16
apuimedoirenab: I agree with that sentiment14:16
apuimedo:-)14:16
apuimedoltomasbo is looking at other ways to enable it14:16
irenabapuimedo, seems its in neutron domain to fix, right?14:16
apuimedoso subports and parent ports get the same level of QoS14:16
apuimedoirenab: it is14:16
apuimedoltomasbo works on both sides ;-)14:16
ltomasboyep, it is in vlan-aware-vm part14:17
irenabgreat, thanks14:17
apuimedoltomasbo: maybe you can explain a bit the two ways that you are looking at (container per vlan and networking per vlan)14:17
ltomasboapuimedo: actually it is not that they get the same QoS14:17
apuimedos/networking/network/14:17
ltomasbois that it is not enforce at all14:17
ltomasbodue to the way the VMs are connected to the br-int when in vlan-aware-vm mode14:18
apuimedoltomasbo: I meant that they should get the get QoS applied as if they were unrelated ports14:18
irenabapuimedo, can you please give a quick update on the nested case progress?14:18
apuimedos/get QoS/QoS/14:18
*** tonytan4ever has quit IRC14:19
ltomasboand yes, I can explain what I've been trying for the containers in vlan-aware-vms14:19
apuimedoirenab: that is what we are doing. ltomasbo will now explain a bit about his experiments14:19
apuimedofor kuryr-libnetwork we covered the bug in interface deletion earlier14:19
*** tonytan4ever has joined #openstack-meeting-414:19
ltomasboyep, I've been trying two different ways of providing vlan networks to nested containers14:19
apuimedowhen serving the container-in-vm case14:19
ltomasbothe first scenario is when we have one subport (one vlan) per container14:20
ltomasboindependently of if they are on the same neutron network or not14:20
irenabltomasbo, vlan maps to the network of type vlan?14:20
irenabor just vlan for Container separation on host?14:21
apuimedothis means that connectivity between containers on the same machine always goes down to br-int on the host. So security groups are applied, QoS may get applied there as well once it is fixed, but you can only have 4096 container on the host14:21
ltomasboit is vlan just up to the trunk port14:21
ltomasbotrunk bridge, sorry14:21
apuimedowell, less than that, but in the ballpark14:22
apuimedo:P14:22
ltomasboand then it will be encapsulated as the neutron network (vlan, vxlan, ...)14:22
apuimedoirenab: vlan to separate inside the VM14:22
irenabltomasbo, got it, thanks14:22
ltomasbothe other way is also using ipvlan14:22
ltomasboand have one subport per network14:22
apuimedoirenab: in the previous way, you basically have the VM eth0 and kuryr createds eth.X vlan devices and moves them into the containers14:23
*** bobh has joined #openstack-meeting-414:23
ltomasboand then, inside the VM, all the container belonging to the same network, will get connected through the same subport14:23
ltomasbobut they need to create a port and include it into the allowed address pair, as in the current ipvlan implementation14:24
apuimedoso there's two calls to do to neutron. Create a port and make it a subport of the VM trunk port14:24
apuimedo(in the previous way)14:24
*** Drago has quit IRC14:24
ltomasboapuimedo: yes14:25
irenabapuimedo, so the kuryr part that does it is already wip?14:25
ltomasboand in the second case, there is one to get the port and one to include it into the allowed pairs of the subport14:25
apuimedoin this other way (one vlan per network used for containers in the VM), there's also two calls. One to create the port to reserve the IP in the subnet, the other to update the port that is actually a subport of the VM so that it has the new IP as an allowed one14:25
apuimedoright14:25
vikaschttps://review.openstack.org/#/c/361993/14:25
apuimedovikasc: :-)14:26
vikascapuimedo, irenab i started this part :)14:26
irenabvikasc, cool!14:26
apuimedovikasc: we'd need to make it configurable for the two modes14:26
vikascapuimedo, yeah makes sense, for ipval as well14:26
vikasc*ipvlan14:27
irenabso back to the QoS problem14:27
apuimedo:-)14:27
irenabwhat is the use case, any libnetwork API or more looking forward case?14:27
apuimedo#action vikasc to work with ltomasbo to put the vlan management in sync with the two ways ltomasbo is experimenting with14:27
apuimedoirenab: well, it's mostly for when k8s adds QoS support14:28
apuimedoso we can map it to Neutron14:28
irenabapuimedo, is it planned for 1.6?14:28
apuimedoas part of the work to check that vlan aware VMs are 'ready' â„¢14:28
apuimedohaven't checked14:28
irenabI see, so more checking if it works as expected14:29
apuimedoso it is more of a priority for Neutron to get this fixed than for us :P14:29
vikascapuimedo, was wondering what pros vlan has ipvlan, cons is lower limit of 4096?14:29
apuimedowe have time14:29
*** makowals has quit IRC14:29
irenabthere is also proposal for CoS support (vlan prio)14:29
apuimedovikasc: the pros of using vlan per container are that you are getting full neutron networking to the containers, including SG14:30
apuimedofor Container network per vlan14:30
vikascapuimedo, ahh , got it. thanks14:30
apuimedothe advantage is that you are not limited to <4095 containers on the VM14:30
vikascapuimedo, scalibility vs control14:31
apuimedothe disadvantage is that if you wanted to have different security/policy applied to containers of the same container network14:31
apuimedoyou would not be able to let Neutron on the host handle it14:31
apuimedovikasc: that's a way to put it14:31
apuimedo;-)14:31
vikascapuimedo, makes sense14:31
*** sshnaidm|afk is now known as sshnaidm14:32
apuimedo#info limao has been working on revamping the rally tests, to test the cost we incur on container creation going to neutron14:32
apuimedoit will probably get merged this week14:32
*** makowals has joined #openstack-meeting-414:32
apuimedoso we'll have better data to take into account when deciding default networking modes14:33
apuimedo(and we can track perf regressions hopefully)14:33
irenabapuimedo, short question regarding k8s implementation14:35
apuimedoirenab: let's move over to the topic then14:35
apuimedo:-)14:35
apuimedo#topic kuryr-kubernetes14:35
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:35
apuimedoirenab: go ahead!14:35
apuimedo:-)14:35
irenabis there  any list of working items, trello board to track the work you , vikasc and ivc_ currently doing?14:36
* apuimedo is ashamed14:36
apuimedoI have the trello board14:36
apuimedobut I have not updated it since the week before the summit14:37
apuimedoI'll put it up to date again today14:37
apuimedolet me put the link14:37
* vikasc was a bit idle for some time and will be catching up on reviewing ivc_ patches14:37
irenabthanks a lot! it will be very helpful for reviews14:37
ivc_too late vikasc, toni already merged those :P14:37
vikascivc_, :D14:38
ivc_but i've got 2-3 more on the way, just need the cni driver in kuryr-lib14:38
vikascivc_, will try out merged code then14:38
apuimedo#link https://trello.com/b/1Ij919E8/networking14:39
apuimedoif anybody is missing access, let me know and I'll add you14:39
apuimedoivc_: you need to rebase the handler patch14:39
apuimedohttps://review.openstack.org/#/c/391329/14:40
ivc_apuimedo, you mean namespace?14:40
apuimedoyup14:40
ivc_oh we wont need it for some time now14:40
apuimedobut IIRC it also needs other changes14:40
ivc_it will just lurk there with 'wip' status14:40
apuimedosince you changed the approach of having watcher per namespace resource to the one of the prototype (one watcher per resource, and let the handlers care, if necessary, abou the namespaces)14:41
*** yfauser has quit IRC14:41
apuimedoivc_: got it14:41
apuimedoanybody can feel free to take items from that board14:41
ivc_yup. it will get used once we get to sec-groups/network per namespace14:42
apuimedobut if there's already somebody on it, do talk to each other14:42
apuimedoivc_: right14:42
*** makowals has quit IRC14:42
apuimedoirenab: did you have some other question on the k8s front?14:42
apuimedothe summary is, ivc_ is waiting for my kuryr-lib CNI patch14:42
apuimedoand in the meantime we can prepare the WIP of the other handlers14:43
irenabI just wanted to see the plan, since had silly questions on the patch ivc_ posted last week :-)14:43
apuimedoand prototype the cluster membership, since it is quite orthogonal14:43
irenabI will check the board14:43
*** banix has joined #openstack-meeting-414:43
apuimedothere's rarely silly questions14:43
*** jlvill-travel is now known as jlvillal14:43
apuimedoexcept whether salmiak is better than chocolate. That would be silly14:44
irenab:-)14:44
vikascthere is a saying.. questions are never silly, answers can be :)14:44
apuimedo:-)14:44
ivc_apuimedo, what other handlers do we expect besides podport and service?14:44
irenabendpoints?14:44
apuimedoivc_: I was implicitly referring to the service one (which we read from endpoints)14:45
ivc_irenab, thats service14:45
irenabnetwork policy14:45
apuimedoI think it can be put as WIP more or less like the namespaces one is14:45
apuimedoirenab: also14:45
ivc_network policy we'll probably need to handle in podport mostly14:45
apuimedoI'd suggest that whoever wants to do that, take a look at how the ovn k8s implementation did it, so that we can have some reference14:46
ivc_https://review.openstack.org/#/c/376045/14:46
ivc_^ service/endpoints14:46
apuimedoivc_: we will need to watch the policy objects14:46
*** Drago has joined #openstack-meeting-414:46
irenabapuimedo, do you have a reference to ovn?14:46
apuimedosure14:46
ivc_apuimedo, yes, but my point is that we prolly cant start on policies before we finish port bindings14:47
apuimedoirenab: https://github.com/openvswitch/ovn-kubernetes14:47
irenabivc_, agree14:47
irenabapuimedo, thanks14:47
*** hongbin has joined #openstack-meeting-414:47
*** yfauser has joined #openstack-meeting-414:47
apuimedoivc_: it can't be tested. But one can start checking how others mapped it14:47
apuimedoand start prototyping14:47
apuimedoor at least breaking down things to do in the trello board14:48
irenabsorry, have to leave. Will catch up on meeting log14:48
apuimedoirenab: do you think you could take up the checking part?14:48
apuimedook irenab14:48
apuimedothanks for joining14:48
irenabapuimedo, will check if I have cycles to spend on it14:48
apuimedoivc_: thanks for the link to the services patch, it escaped my eye14:48
apuimedothanks irenab14:48
apuimedoany other topic on k8s?14:49
apuimedoivc_:14:49
*** reedip_ has quit IRC14:49
ivc_got some ideas about net.policies and labels, that we can have a sec.group per label14:49
ivc_i.e. multiple labels -> multiple sec.groups14:50
ivc_but need to experiment with that14:50
apuimedosame here14:50
apuimedoI have some ideas, but need to check if it will work out with the selectors14:51
apuimedo#topic open discussion14:52
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:52
apuimedoanybody else has other topics?14:52
*** julim has joined #openstack-meeting-414:52
apuimedo#action apuimedo to update the trello board14:53
apuimedoalrigth then. Thank you all for joining!14:54
apuimedo#endmeeting14:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:54
openstackMeeting ended Mon Nov  7 14:54:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:54
mchiapperothank you14:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-07-14.02.html14:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-07-14.02.txt14:54
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-07-14.02.log.html14:54
vikascbbye14:54
*** Drago has left #openstack-meeting-414:54
ltomasbobye14:54
mchiapperobye14:54
*** pc_m has left #openstack-meeting-414:54
*** yedongcan has left #openstack-meeting-414:57
*** makowals has joined #openstack-meeting-414:58
*** caowei has quit IRC14:59
*** lmdaly has left #openstack-meeting-414:59
sigmavirus#startmeeting craton15:00
openstackMeeting started Mon Nov  7 15:00:07 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
suloo/15:00
sigmavirus#help15:00
sigmavirus#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: craton)"15:01
sigmavirus#link https://etherpad.openstack.org/p/craton-meetings15:01
suloo/ again15:01
sigmavirus^ Today's agenda15:01
sigmavirus(although there's nothing there for today)15:01
*** shananigans has joined #openstack-meeting-415:01
sigmavirus#chair sulo15:01
openstackCurrent chairs: sigmavirus sulo15:01
*** reedip_ has joined #openstack-meeting-415:01
* sigmavirus couldn't remember the octothorpe command15:01
sigmavirus#chair jimbaker15:01
openstackCurrent chairs: jimbaker sigmavirus sulo15:01
*** jerms has quit IRC15:02
sigmavirus#link http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-10-31-15.00.txt15:02
sigmavirusLast week's summary15:02
sigmavirusSince jimbaker still seems to be on PTO, let's just run down the action items from last week15:02
suloright i dont have the writeup yet15:02
sigmavirus#topic Review action items15:02
*** openstack changes topic to "Review action items (Meeting topic: craton)"15:02
sigmavirus#info We'll carry forward the action item for jimbaker and sulo to do a summary/write-up for the summit meetings15:03
*** uck has quit IRC15:03
sulocool sounds good15:03
sigmavirus#action jimbaker to send summary to openstack-dev with [craton] tag from what happened in Barcelona15:03
sigmavirus#action sulo to send summary to openstack-dev with [craton] tag from what happened in Barcelona15:03
sigmavirus(It only assigned the action item to jim last week so, adding two distinct ones)15:03
sulook15:03
sigmavirus#topic updates15:04
*** openstack changes topic to "updates (Meeting topic: craton)"15:04
sigmavirusAny updates on your end sulo?15:04
*** chrisspencer has joined #openstack-meeting-415:04
suloso looks like participation is thin today ..15:04
suloyes15:04
chrisspencero/15:04
sulohi chrisspencer15:04
sigmavirusAnd now we're 3 :)15:04
suloso i am working on few work items, namely search by variables15:04
chrisspencerwho decided it was a good idea to change the clocks?15:04
chrisspencerwe just keep them the same here in AZ :)15:05
sulothere is a small bug in get /data15:05
suloand getting create calls to allow variables15:05
sulochrisspencer: yeah i hear you15:06
*** banix_ has joined #openstack-meeting-415:06
suloexpect PR's for all of it today15:06
sigmaviruschrisspencer: it's supposed to help farmers and save energy but it does neither ;)15:06
sigmavirussulo: that sounds ominous15:06
sigmavirus;)15:06
*** banix has quit IRC15:07
*** banix_ is now known as banix15:07
*** mchiappero has left #openstack-meeting-415:07
suloheh15:07
*** apuimedo has left #openstack-meeting-415:07
sulomostly simple changes .. shouldnt break too much ;)15:07
suloi am going to start some work on workflow as well this week15:08
sigmavirusawesome15:09
sulowe can discuss more tomorrow during the dev vidyo meeting15:09
sigmavirusThat sounds good to me15:09
sigmavirusAnything else sulo?15:09
suloi think thats all from my side15:09
*** ivc_ has left #openstack-meeting-415:09
sigmaviruschrisspencer: since you're the only other one here, do you have any updates?15:10
*** amotoki has joined #openstack-meeting-415:10
chrisspencerI don't, haven't really spent any significant time on craton other than code reviews15:11
sigmavirusYour reviews have been sincerely appreciated, chrisspencer15:11
sigmavirusAs for me, I'm just doing more work on our tests. Still pondering  a solution to remove all the duplicated code between each of the shells commands15:12
*** tuan_luong has joined #openstack-meeting-415:12
sigmavirus#topic Patches needing code review15:13
*** openstack changes topic to "Patches needing code review (Meeting topic: craton)"15:13
sigmavirusIf anyone has something they need reviewed, feel free to drop it here preceded by `#link `15:13
*** spotz_zzz is now known as spotz15:13
sulolooks like nothing from me .. i need to fix the one that i have pending15:13
sigmavirus#link https://review.openstack.org/39391015:13
sigmavirusThat's nothing urgent, but it's simple15:14
sigmavirusJust making it match the other shells unit tests that we have15:14
*** lserpietri has left #openstack-meeting-415:14
suloah cool15:15
sigmavirus#topic Q&A / Wrap up / Idle chatter15:15
*** openstack changes topic to "Q&A / Wrap up / Idle chatter (Meeting topic: craton)"15:15
sigmavirusAnything else from anyone?15:15
sigmavirusWith only three of us, we can probably wrap this up 45 minutes earlier than expected :P15:16
sulo:)15:16
*** irenab has quit IRC15:16
sulook lets end it .. see you guys later15:17
*** woodard has quit IRC15:17
chrisspencerlater15:17
*** shananigans has left #openstack-meeting-415:17
sigmavirus#topic End meeting15:17
*** openstack changes topic to "End meeting (Meeting topic: craton)"15:17
sigmavirus#info Only 3 of us showed up so we're ending early this week15:18
sigmavirus#endmeeting15:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:18
openstackMeeting ended Mon Nov  7 15:18:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-07-15.00.html15:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-07-15.00.txt15:18
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-07-15.00.log.html15:18
*** chrisspencer has left #openstack-meeting-415:18
*** oanson has joined #openstack-meeting-415:19
*** rbak has joined #openstack-meeting-415:20
*** oshidoshi has quit IRC15:29
*** galstrom_zzz is now known as galstrom15:32
*** yamahata has joined #openstack-meeting-415:33
*** links has joined #openstack-meeting-415:35
*** automagically has left #openstack-meeting-415:36
*** numans has quit IRC15:36
*** dtardivel has quit IRC15:41
*** serverascode has quit IRC15:41
*** sripriya has quit IRC15:41
*** coolsvap has quit IRC15:42
*** izaakk has quit IRC15:42
*** carl_baldwin has quit IRC15:42
*** johnsom has quit IRC15:42
*** cloudnull has quit IRC15:42
*** ChrisPriceAB has quit IRC15:42
*** ChrisPriceAB has joined #openstack-meeting-415:42
*** vdrok has quit IRC15:42
*** MarkAtwood has quit IRC15:42
*** alanmeadows has quit IRC15:42
*** dpyzhov has quit IRC15:42
*** uli-k has quit IRC15:42
*** skath has quit IRC15:42
*** csatari has quit IRC15:42
*** masteinhauser has quit IRC15:42
*** cargonza has quit IRC15:42
*** ashtokolov has quit IRC15:42
*** nikhil has quit IRC15:42
*** qwang has quit IRC15:42
*** wolsen has quit IRC15:42
*** sweston has quit IRC15:42
*** kozhukalov has quit IRC15:42
*** amit213 has quit IRC15:42
*** margaret has quit IRC15:42
*** alex_didenko has quit IRC15:42
*** dougwig has quit IRC15:42
*** zhiyan has quit IRC15:42
*** Kevin_Zheng has quit IRC15:42
*** raddaoui has quit IRC15:42
*** RaginBajin has quit IRC15:42
*** zeestrat has quit IRC15:42
*** raginbaj- is now known as raginbajin15:42
*** yfauser has quit IRC15:43
*** nkrinner_afk has quit IRC15:43
*** dasanind_ has quit IRC15:43
*** erikmwilson has quit IRC15:43
*** cjloader has quit IRC15:43
*** fungi has quit IRC15:43
*** odyssey4me has quit IRC15:43
*** FrankZhang has quit IRC15:43
*** toan has quit IRC15:43
*** dtardivel has joined #openstack-meeting-415:44
*** ashtokolov has joined #openstack-meeting-415:44
*** wolsen has joined #openstack-meeting-415:44
*** zhiyan has joined #openstack-meeting-415:45
*** dpyzhov has joined #openstack-meeting-415:45
*** Kevin_Zheng has joined #openstack-meeting-415:45
*** csatari has joined #openstack-meeting-415:45
*** izaakk has joined #openstack-meeting-415:45
*** coolsvap has joined #openstack-meeting-415:45
*** nikhil has joined #openstack-meeting-415:45
*** dougwig has joined #openstack-meeting-415:45
*** sripriya has joined #openstack-meeting-415:45
*** trinaths has joined #openstack-meeting-415:46
*** sweston has joined #openstack-meeting-415:46
*** vdrok has joined #openstack-meeting-415:46
*** johnsom has joined #openstack-meeting-415:46
*** qwang has joined #openstack-meeting-415:46
*** skath has joined #openstack-meeting-415:46
*** cargonza has joined #openstack-meeting-415:46
*** alex_didenko has joined #openstack-meeting-415:47
*** toan has joined #openstack-meeting-415:47
*** margaret has joined #openstack-meeting-415:47
*** amit213 has joined #openstack-meeting-415:47
*** alanmeadows has joined #openstack-meeting-415:48
*** zeestrat has joined #openstack-meeting-415:48
*** RaginBajin_ has joined #openstack-meeting-415:48
*** kozhukalov has joined #openstack-meeting-415:48
*** serverascode has joined #openstack-meeting-415:48
*** carl_baldwin has joined #openstack-meeting-415:48
*** cloader89 has joined #openstack-meeting-415:48
*** odyssey4me has joined #openstack-meeting-415:48
*** erikmwilson has joined #openstack-meeting-415:48
*** cloader89 is now known as cjloader15:48
*** FrankZhang has joined #openstack-meeting-415:49
*** raddaoui has joined #openstack-meeting-415:49
*** cloudnull has joined #openstack-meeting-415:50
*** makowals has quit IRC15:51
*** MarkAtwood has joined #openstack-meeting-415:52
*** masteinhauser has joined #openstack-meeting-415:52
*** dave-mccowan has quit IRC15:53
*** dasanind_ has joined #openstack-meeting-415:54
*** nkrinner_afk has joined #openstack-meeting-415:54
*** fungi has joined #openstack-meeting-415:55
*** spzala has joined #openstack-meeting-415:55
*** uli-k has joined #openstack-meeting-415:56
*** hshiina has joined #openstack-meeting-415:57
*** banix has quit IRC15:57
*** tuan_luong has quit IRC15:58
*** Sukhdev has joined #openstack-meeting-416:00
SukhdevFolks, time for Ironic-neutron integration meeting16:01
sambettso/16:01
hshiinao/16:01
trinathso/16:01
Sukhdev#startmeeting ironic_neutron16:01
openstackMeeting started Mon Nov  7 16:01:57 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:02
jroll\o16:02
*** zenoway has quit IRC16:02
Sukhdev#topic: Agenda16:02
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:02
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_November_7.2C_201616:02
*** zenoway has joined #openstack-meeting-416:02
SukhdevWelcome to first meeting after the summit16:02
SukhdevHope everybody is fully recovered from travels by now16:02
Sukhdev#topic: Announcements16:03
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:03
SukhdevAnybody has any announcements?16:03
sambettsPort groups API patch merged16:03
*** makowals has joined #openstack-meeting-416:03
Sukhdevyup - that is good news16:04
SukhdevI updated it on the agenda16:04
Sukhdevlets dive into the agenda16:04
hshiinanova schedule was announced  http://lists.openstack.org/pipermail/openstack-dev/2016-October/106423.html16:04
jroll^^16:04
hshiinaspec freeze is o-1, nov 1716:04
jrollneed to get that nova portgroups spec merged16:04
hshiinait's important16:05
sambettsNova team accepted attach/detach BP but we need to review/merge the Ironic RFE/spec first16:05
*** dave-mccowan has joined #openstack-meeting-416:06
*** yamahata has quit IRC16:06
sambettswow thats 1 week away.. .16:06
*** zenoway has quit IRC16:06
Sukhdevyup - its almost upon us16:07
Sukhdevlets quickly go through the agenda items16:08
Sukhdev#topic Security Groups16:08
*** openstack changes topic to "Security Groups (Meeting topic: ironic_neutron)"16:08
SukhdevI posted the documentation patch for this16:09
Sukhdev#link: https://review.openstack.org/#/c/393962/16:09
Sukhdevwhen ever you have a moment, please have a look at it16:10
Sukhdevfor the patch - https://review.openstack.org/#/c/36145116:10
Sukhdevsambetts and I had a brief discussion on Friday regarding the flag security_group_enabled16:11
Sukhdevi.e. if the security_group_enabled flag False, and SGs are configured, how to deal with this16:11
SukhdevI checked on the neutron and nova side as to how this is handled.16:12
*** pcaruana has quit IRC16:12
Sukhdevbasically, if this flag is set to false and somebody tries to set security groups at the time of nova boot - the instance fails16:13
Sukhdevin our case it is slightly different - as everything is being set/done during the init16:14
Sukhdevfor tenant networks, it will have the same behavior - however, how do we want to deal with it when this happens for provisioning or cleaning networks16:14
Sukhdevwe can take two approaches -16:15
Sukhdev1 ) Since all of these operations are managed by admin, we should simply document it16:15
Sukhdev2) we fail the operation16:16
Sukhdevor may be both actullay16:16
*** sdake has joined #openstack-meeting-416:16
Sukhdevany thoughts?16:16
jrollboth seems right to me16:17
jrollif someone has configured some security group, they expect that port to be locked down, we shouldn't allow a port to be up that isn't locked down the way they expect16:17
jrollif that makes sense16:17
*** berendt has joined #openstack-meeting-416:18
*** lserpietri has joined #openstack-meeting-416:19
*** lserpietri has left #openstack-meeting-416:19
Sukhdevthe way the SG patch is written, it will behave like that - i.e. port_create() will fail and log the exception16:19
*** sdake has quit IRC16:20
Sukhdevl just noticed sambetts comment about it on the patch -16:21
sambettsSorry for being slow to respond, I was in another call, I put a more detailed https://review.openstack.org/#/c/361451/14/ironic/common/neutron.py16:21
SukhdevI think option 2 in your comment - i.e. misconfiguration seems more appropriate16:21
jroll+116:22
sambettsthe only reason I prefer option 1 is that port security can be enabled and disabled at will in the neutron API, however the secuirty groups in the ironic configuration can only be disabled by editing the ironic config file and restarting ironic, so it the admin wants to debug something and turns off port secuirty it'll prevent all ironic deployments16:23
jrollsambetts: as an operator, I never want to be surprised with something less secure than I expect16:24
jrollis why I'm on the option 2 side16:24
Sukhdevsambetts : that scenario is not really applicable in this case - it is the same operator who is adding both options16:24
*** sdake has joined #openstack-meeting-416:25
sambettsI'm talking about post having Ironic running, I don't want to have to restart ironic once its running to do something which in other cases can simply be enabled/disable via an API16:25
jrollyeah, I get it, but I think it can put someone in a "dangerous" position16:26
Sukhdevsambetts : i chatted with both nova and neutron PTLs about this on Friday after our discussion - it is used to fail the instance - in case somebody tries to specify SG, when they should not be16:27
sambettsyeah they changed it in mitaka to just not apply the SG right?16:28
Sukhdevin our case, these operations are managed by the admin16:28
*** tonytan4ever has quit IRC16:29
SukhdevI mean to say is that the net effect of this mis-configuration is that the instance is faied16:29
*** tonytan4ever has joined #openstack-meeting-416:30
* sambetts wonders if this is the sort of check we should have on the neutron network driver validate() function 16:30
*** belmoreira has quit IRC16:30
*** admin0 has left #openstack-meeting-416:30
SukhdevI am of the openion that we update the documentation - where we talk about the provisioning/cleaning network creation16:32
Sukhdevactually, the patch that I pushed for documentation - I should add text to describe this16:32
*** krtaylor has quit IRC16:33
*** limao_ has quit IRC16:33
*** garyloug has quit IRC16:34
Sukhdevthoughts?16:34
*** garyloug has joined #openstack-meeting-416:35
jrollyes, agree16:35
sambettsI think we should definatly document it, but I wonder if we should fail earlier in the process if the network has port security disabled16:35
jrollyeah, I wouldn't be opposed to checking in validate16:36
Sukhdevsambetts : failing earlier does not really help - as you pointed out earlier - if somebody changes the network properties after everything is running16:37
sambettse.g. make the nodes configured the neutron network interface fail validation or have an explict check so that we don't fire off N port creates even though we know they are going to fail16:37
*** ruriryan has left #openstack-meeting-416:38
*** iyamahat has joined #openstack-meeting-416:38
Sukhdevso, this is really a weird scenario - I can see the usefulness if there are multiple operators16:39
*** spzala has quit IRC16:39
Sukhdevfailing earlier helps if someone creates networks and SGs and also sets this flag to false - which is kind of weird :-)16:39
*** spotz is now known as spotz_zzz16:40
*** spzala has joined #openstack-meeting-416:40
*** vishwanathj has joined #openstack-meeting-416:40
sambettsSukhdev: nova runs node validation has part of its resource discovering process and will prevent nova scheduling instances on the node if they are misconfigured16:40
*** berendt has quit IRC16:41
jrollsambetts: no, validation happens post-schedule16:41
jrollbut agree, it will save some time/resources16:41
Sukhdevsee here - https://github.com/openstack/nova/blob/14.0.1/nova/network/neutronv2/api.py#L78316:42
sambettsjroll: ? really?! I'm sure nodes that fail validation don't show up as available to nova?16:42
*** spotz_zzz is now known as spotz16:42
Sukhdevthis is where this is checked16:42
jrollsambetts: yeah, it happens here https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L76316:42
*** trinaths has left #openstack-meeting-416:43
jrollsambetts: it also happens between enroll and manageable, so you're partially right16:43
*** berendt has joined #openstack-meeting-416:44
*** spzala has quit IRC16:44
Sukhdevnova only checks this flag at the time of port create16:44
*** reedip_ has quit IRC16:45
Sukhdevsambetts : even if we go with the idea of checking this flag - what would you see the end-result? - not fail the operation?16:46
sambettsNo fail it, but we'd fail here: https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L76316:47
sambettsbefore we've even starting deployment16:47
*** spzala has joined #openstack-meeting-416:47
sambettsbut this is something we can always expand on later16:47
*** shaohe_feng_ has joined #openstack-meeting-416:48
Sukhdevhmm...16:48
*** lihi has quit IRC16:48
*** shaohe_f- has joined #openstack-meeting-416:48
SukhdevI really believe this is an issue of misconfiguration - and, we can come back and this check here if it becomes an issue -16:50
SukhdevI mean add this check here16:50
*** shaohe_feng has quit IRC16:50
jrollI mean... we agreed to add a check. why not add it sooner in the deploy process?16:50
sambettsjroll: we technically don't need the check right now, it'll just catch the failure like any other port create error right now16:51
jrolls/add a check/have it fail/16:51
*** spzala has quit IRC16:51
jroll:)16:51
*** shaohe_feng has joined #openstack-meeting-416:52
Sukhdev+116:52
*** shaohe_feng_ has quit IRC16:52
jrollso, agree to fail early in validate()?16:52
sambettsI guess the only potential arguement might be to do with validate being syncronous and making an external call */me ducks*16:52
*** shaohe_f- has quit IRC16:52
jrollsambetts: it already hits the bmc, if neutron ever gets slower than a bmc we have bigger problems :)16:53
*** spzala has joined #openstack-meeting-416:53
jrollnet-show, anyway16:53
sambettstrue true16:53
sambettsdoes validate hit the BMC?16:53
jrollyes16:53
sambettsfor power or something?16:54
persiaSome folk talk about running neutron on fairly low-spec switch hardware.  Some BMCs have fairly high-clock cores.  Take care with assumptions.16:54
jrolloh wait, apparently we do not: https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ipmitool.py#L77416:54
jroll:/16:54
jrollpersia: fair point16:54
* Sukhdev time check - 5 min16:55
Sukhdevlets draw some conclusions16:55
sambettsI'm happy with the patch as it is today if we're happy for it to be a misconfiguration16:56
*** sdake has quit IRC16:56
*** jerms has joined #openstack-meeting-416:56
sambettsI've removed my -116:56
jrollI'm still happiest with doing this in validate(), but okay with current status quo too16:56
SukhdevI think we can come back with a new patch to address it16:57
*** berendt has quit IRC16:57
*** spzala has quit IRC16:57
SukhdevI will push an update to the documentation patch to describe this misconfiguration patch16:57
* Sukhdev 2 min left16:58
Sukhdevanything critical to discuss?16:58
sambettsnothing from me as far as I can remember16:59
SukhdevThanks folks, this was a very good discussion -16:59
Sukhdevsee ya'll next week when US will have new president :-)16:59
Sukhdevbye17:00
sambetts:/17:00
*** shaohe_feng has quit IRC17:00
sambettscya o/17:00
Sukhdev#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Mon Nov  7 17:00:18 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-11-07-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-07-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-07-16.01.log.html17:00
*** shaohe_feng has joined #openstack-meeting-417:01
*** shaohe_f- has joined #openstack-meeting-417:02
*** shaohe_f| has joined #openstack-meeting-417:02
*** vishwanathj has quit IRC17:03
*** krtaylor has joined #openstack-meeting-417:03
*** shaohe_f- has quit IRC17:04
*** krtaylor has quit IRC17:05
*** iyamahat has quit IRC17:05
*** shaohe_feng has quit IRC17:06
*** shaohe_f| has quit IRC17:06
*** woodard has joined #openstack-meeting-417:07
*** ppiela_ has joined #openstack-meeting-417:07
*** matrohon has quit IRC17:09
*** jovon has joined #openstack-meeting-417:09
*** krtaylor has joined #openstack-meeting-417:11
*** shaohe_feng has joined #openstack-meeting-417:13
*** caboucha has joined #openstack-meeting-417:17
*** shaohe_feng has quit IRC17:18
*** links has quit IRC17:20
*** berendt has joined #openstack-meeting-417:22
*** banix has joined #openstack-meeting-417:22
*** shaohe_feng has joined #openstack-meeting-417:22
*** unicell1 has quit IRC17:23
*** shaohe_feng_ has joined #openstack-meeting-417:25
*** shaohe_feng has quit IRC17:26
*** shaohe_feng has joined #openstack-meeting-417:26
*** anilvenkata has quit IRC17:26
*** numans has joined #openstack-meeting-417:28
*** shaohe_feng_ has quit IRC17:30
*** Sukhdev has quit IRC17:30
*** shaohe_feng has quit IRC17:30
*** asettle has quit IRC17:33
*** ppiela_ has quit IRC17:37
*** shaohe_feng_ has joined #openstack-meeting-417:37
*** shaohe_feng_ has quit IRC17:40
*** iyamahat has joined #openstack-meeting-417:41
*** shaohe_feng has joined #openstack-meeting-417:42
*** iyamahat has quit IRC17:45
*** shaohe_feng_ has joined #openstack-meeting-417:46
*** shaohe_feng_ has quit IRC17:46
*** shaohe_feng_ has joined #openstack-meeting-417:47
*** shaohe_feng has quit IRC17:49
*** hemanthm|away is now known as hemanth17:49
*** shaohe_feng_ has quit IRC17:51
*** shaohe_feng has joined #openstack-meeting-417:51
*** shaohe_feng_ has joined #openstack-meeting-417:53
*** automagically has joined #openstack-meeting-417:53
*** cdelatte has joined #openstack-meeting-417:54
*** hshiina has left #openstack-meeting-417:54
*** shaohe_f- has joined #openstack-meeting-417:55
*** ad_rien_ has quit IRC17:55
*** shaohe_feng has quit IRC17:56
*** shaohe_feng has joined #openstack-meeting-417:57
*** shaohe_feng_ has quit IRC17:58
*** ralonsoh has quit IRC17:58
*** shaohe_f- has quit IRC17:59
*** shaohe_feng has quit IRC18:00
*** degorenko is now known as _degorenko|afk18:00
*** unicell has joined #openstack-meeting-418:05
*** garyloug has quit IRC18:05
*** neiljerram has quit IRC18:06
*** dave-mccowan has quit IRC18:06
*** yamahata has joined #openstack-meeting-418:06
*** dave-mccowan has joined #openstack-meeting-418:11
*** shaohe_feng has joined #openstack-meeting-418:12
*** shaohe_feng has quit IRC18:14
*** shaohe_feng has joined #openstack-meeting-418:14
*** shaohe_feng_ has joined #openstack-meeting-418:18
*** shaohe_feng has quit IRC18:18
*** shaohe_feng_ is now known as shaohe_feng18:18
*** yamahata has quit IRC18:19
*** ad_rien_ has joined #openstack-meeting-418:20
*** yamahata has joined #openstack-meeting-418:22
*** sshnaidm is now known as sshnaidm|brb18:26
*** yamahata has quit IRC18:31
*** iyamahat has joined #openstack-meeting-418:32
*** dtardivel has quit IRC18:34
*** ad_rien_ has quit IRC18:39
*** armax has joined #openstack-meeting-418:39
*** spzala has joined #openstack-meeting-418:54
*** markvoelker_ has joined #openstack-meeting-418:54
*** Sukhdev has joined #openstack-meeting-418:55
*** markvoelker has quit IRC18:56
*** markvoelker has joined #openstack-meeting-418:57
*** s3wong has joined #openstack-meeting-418:58
*** hemanth is now known as hemanth|lunch18:59
*** markvoelker_ has quit IRC18:59
*** sambetts is now known as sambetts|afk18:59
*** iyamahat has quit IRC19:07
*** d0ugal has quit IRC19:30
*** d0ugal has joined #openstack-meeting-419:31
*** d0ugal has quit IRC19:31
*** d0ugal has joined #openstack-meeting-419:31
*** hemanth|lunch is now known as hemanth19:31
*** anilvenkata has joined #openstack-meeting-419:31
*** dave-mccowan has quit IRC19:39
*** yamahata has joined #openstack-meeting-419:39
*** armax has quit IRC19:44
*** ad_rien_ has joined #openstack-meeting-419:50
*** sshnaidm|brb is now known as sshnaidm19:52
*** dave-mccowan has joined #openstack-meeting-419:53
*** yamahata has quit IRC19:54
*** woodster_ has joined #openstack-meeting-419:56
*** spotz is now known as spotz_zzz19:57
*** ad_rien_ has quit IRC20:09
*** uxdanielle has joined #openstack-meeting-420:15
*** yifei has quit IRC20:23
*** yifei has joined #openstack-meeting-420:23
*** jmccrory has quit IRC20:24
*** jmccrory has joined #openstack-meeting-420:25
*** d0ugal has quit IRC20:26
*** wirehead_ has left #openstack-meeting-420:26
*** d0ugal has joined #openstack-meeting-420:27
*** d0ugal has quit IRC20:27
*** d0ugal has joined #openstack-meeting-420:27
*** uxdanielle has quit IRC20:28
*** spotz_zzz is now known as spotz20:39
*** spzala has quit IRC20:40
*** revon has joined #openstack-meeting-420:40
*** oanson has quit IRC20:41
*** matrohon has joined #openstack-meeting-420:41
*** iyamahat has joined #openstack-meeting-420:45
*** armax has joined #openstack-meeting-420:47
*** automagically has left #openstack-meeting-420:48
*** banix_ has joined #openstack-meeting-420:53
*** banix__ has joined #openstack-meeting-420:54
*** banix has quit IRC20:55
*** banix__ is now known as banix20:55
*** banix_ has quit IRC20:57
*** anilvenkata has quit IRC20:58
*** MeganR has joined #openstack-meeting-421:00
*** Rockyg has joined #openstack-meeting-421:00
*** mriedem has joined #openstack-meeting-421:00
*** julim has quit IRC21:17
*** uck has joined #openstack-meeting-421:21
*** spzala has joined #openstack-meeting-421:22
*** spzala has quit IRC21:27
*** yfauser has joined #openstack-meeting-421:28
*** mriedem has left #openstack-meeting-421:30
*** Jeffrey4l has quit IRC21:35
*** spzala has joined #openstack-meeting-421:35
*** cleong has quit IRC21:38
*** yamahata has joined #openstack-meeting-421:41
*** myatsenko has quit IRC21:43
*** iyamahat has quit IRC21:44
*** banix has quit IRC21:45
*** baoli has quit IRC21:45
*** rtheis has quit IRC21:51
*** bobmel has quit IRC22:00
*** MeganR has quit IRC22:00
*** armax has quit IRC22:01
*** yamahata has quit IRC22:06
*** caboucha has quit IRC22:07
*** woodard has quit IRC22:10
*** thorst_ has quit IRC22:10
*** iyamahat has joined #openstack-meeting-422:14
*** krtaylor has quit IRC22:22
*** tonytan4ever has quit IRC22:23
*** iyamahat has quit IRC22:29
*** jcdfr has joined #openstack-meeting-422:30
*** matrohon has quit IRC22:31
*** jcdfr has quit IRC22:31
*** iyamahat has joined #openstack-meeting-422:39
*** uxdanielle has joined #openstack-meeting-422:46
*** bobmel has joined #openstack-meeting-422:47
*** kylek3h has quit IRC22:51
*** limao has joined #openstack-meeting-422:56
*** limao_ has joined #openstack-meeting-422:58
*** yfauser_ has joined #openstack-meeting-422:59
*** yfauser has quit IRC22:59
*** limao has quit IRC23:01
*** spotz is now known as spotz_zzz23:06
*** spotz_zzz is now known as spotz23:06
*** jovon has quit IRC23:07
*** bobh has quit IRC23:10
*** baoli has joined #openstack-meeting-423:11
*** galstrom is now known as galstrom_zzz23:11
*** rbak has quit IRC23:28
*** Jeffrey4l has joined #openstack-meeting-423:31
*** Julien-zte has quit IRC23:32
*** cdelatte has quit IRC23:33
*** armax has joined #openstack-meeting-423:36
*** limao_ has quit IRC23:46
*** thorst_ has joined #openstack-meeting-423:47
*** sshnaidm is now known as sshnaidm|away23:53
*** gibi_ has quit IRC23:56
*** gibi has joined #openstack-meeting-423:56

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