Monday, 2016-10-31

*** thorst has quit IRC00:00
*** hippiepete has quit IRC00:02
*** hippiepete has joined #openstack-meeting-400:21
*** thorst has joined #openstack-meeting-400:23
*** thorst has quit IRC00:26
*** thorst has joined #openstack-meeting-400:27
*** thorst has quit IRC00:31
*** thorst has joined #openstack-meeting-400:31
*** thorst has quit IRC00:37
*** yifei has joined #openstack-meeting-400:58
*** yifei has quit IRC01:04
*** yifei1 has joined #openstack-meeting-401:04
*** yifei1 is now known as yifei01:06
*** armax has quit IRC01:20
*** thorst has joined #openstack-meeting-401:37
*** bobh has joined #openstack-meeting-401:39
*** thorst has quit IRC01:41
*** thorst has joined #openstack-meeting-401:41
*** thorst has quit IRC01:42
*** bobh has quit IRC01:44
*** tovin07 has joined #openstack-meeting-401:46
*** hieulq has joined #openstack-meeting-401:52
*** bobh has joined #openstack-meeting-402:05
*** liwei has joined #openstack-meeting-402:14
*** markvoelker has joined #openstack-meeting-402:17
*** thorst has joined #openstack-meeting-402:26
*** thorst has quit IRC02:27
*** krtaylor has joined #openstack-meeting-402:29
*** armax has joined #openstack-meeting-402:29
*** armax has quit IRC02:31
*** thorst has joined #openstack-meeting-402:31
*** thorst has quit IRC02:31
*** thorst has joined #openstack-meeting-402:32
*** thorst has quit IRC02:36
*** armax has joined #openstack-meeting-402:36
*** liwei has quit IRC02:53
*** liwei has joined #openstack-meeting-403:08
*** armax has quit IRC03:23
*** alij has joined #openstack-meeting-403:42
*** Jeffrey4l has joined #openstack-meeting-403:44
*** bobh has quit IRC03:50
*** andymaier has joined #openstack-meeting-404:11
*** alij has quit IRC04:33
*** links has joined #openstack-meeting-404:48
*** andymaier has quit IRC04:48
*** alij has joined #openstack-meeting-404:51
*** andymaier has joined #openstack-meeting-404:52
*** alij has quit IRC04:56
*** andymaier has quit IRC05:10
*** alij has joined #openstack-meeting-405:13
*** alij has quit IRC05:17
*** alij has joined #openstack-meeting-405:20
*** alij has quit IRC05:25
*** andymaier has joined #openstack-meeting-405:32
*** thorst has joined #openstack-meeting-405:35
*** andymaier has quit IRC05:36
*** thorst has quit IRC05:40
*** alij has joined #openstack-meeting-405:49
*** alij has quit IRC05:51
*** alij has joined #openstack-meeting-405:51
*** stanchan has quit IRC06:00
*** alij has quit IRC06:09
*** alij has joined #openstack-meeting-406:12
*** alij has quit IRC06:21
*** yfujioka has joined #openstack-meeting-406:22
*** alij has joined #openstack-meeting-406:22
*** alij has joined #openstack-meeting-406:22
*** yfujioka has quit IRC06:22
*** alij has quit IRC06:26
*** alij has joined #openstack-meeting-406:26
*** alij has quit IRC06:30
*** alij has joined #openstack-meeting-406:31
*** liwei has quit IRC06:41
*** liwei has joined #openstack-meeting-406:57
*** belmoreira has joined #openstack-meeting-406:59
*** irenab has joined #openstack-meeting-407:31
*** portdirect has quit IRC07:31
*** portdirect has joined #openstack-meeting-407:34
*** Jeffrey4l has quit IRC07:34
*** xiaohhui has joined #openstack-meeting-407:52
*** vsaienk0 has quit IRC07:57
*** vishnoianil has joined #openstack-meeting-407:59
*** alij_ has joined #openstack-meeting-408:00
*** alij_ has quit IRC08:00
*** alij has quit IRC08:00
*** alij has joined #openstack-meeting-408:01
*** alij has quit IRC08:08
*** amotoki has joined #openstack-meeting-408:15
*** yuanwei_ has joined #openstack-meeting-408:19
*** alij has joined #openstack-meeting-408:23
*** alij has quit IRC08:30
*** alij has joined #openstack-meeting-408:30
*** alij has quit IRC08:31
*** alij has joined #openstack-meeting-408:31
*** gongysh has joined #openstack-meeting-408:32
*** mrunge has quit IRC08:35
*** vishnoianil has quit IRC08:36
*** alij has quit IRC08:36
*** alij has joined #openstack-meeting-408:36
*** mrunge has joined #openstack-meeting-408:39
*** alij has quit IRC08:41
*** kbyrne has quit IRC08:56
*** lihi has joined #openstack-meeting-408:58
*** oanson has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Oct 31 09:00:18 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
xiaohhuihello09:00
oansonHi. Welcome. Who is here for the dragonflow meeting?09:00
lihio/09:01
*** ruriryan has joined #openstack-meeting-409:01
oansonAll right, let's start. The stragglers will join later09:01
oanson#topic Ocata Roadmap09:02
*** openstack changes topic to "Ocata Roadmap (Meeting topic: Dragonflow)"09:02
oansonSo there was a summit in Barcelona. We are looking at several directions09:02
*** dimak has joined #openstack-meeting-409:02
oansonThe Ocata work will be summarised here: https://etherpad.openstack.org/p/dragonflow-ocata09:02
dimakHey09:02
*** ntr0py has joined #openstack-meeting-409:02
oanson#link Ocata Roadmap etherpad https://etherpad.openstack.org/p/dragonflow-ocata09:02
oansonThe hot topics are deployment, SFC, ipv6, NAT, and LB09:03
*** hujie has joined #openstack-meeting-409:03
oansonSomeone contacted me for load balancing. I will talk to him, since he was supposed to upload a spec.09:03
oansonAdditionally, from my personal experience, we should supply networking troubleshooting tools09:04
oansonTo assist both developers trying to understand why their packets are missing09:04
oansonAnd users/operators/deployers to understand why their customers' packets are missing09:05
yuli_shello09:05
oansonyuli_s, hi09:05
oansonany takers?09:05
nick-ma_hi09:05
oansonnick-ma_, hi09:05
hujieHi09:05
oansonAll right, I guess we'll get back to that09:06
oansonThe next hot topic is SFC. dimak will start looking into it09:06
dimakok09:06
oansonNote that this is a huge undertaking, so this won't happen by next week :)09:06
dimak:)09:07
oansondimak, I suggest you start by reviewing networking-sfc, the IETF standards draft, and there's a review09:07
oanson(1 sec, I'll find it)09:07
dimakrfc7665?09:07
oanson#link networking-sfc SFC graph API https://review.openstack.org/#/c/388802/09:07
nick-ma_networking-sfc needs load balancing for a kind of port group. I discussed with the team in Austin.09:07
oansondimak, yes09:08
oansonAll SFC docs are summarised here: https://datatracker.ietf.org/wg/sfc/documents/09:08
oanson#link SFC docs https://datatracker.ietf.org/wg/sfc/documents/09:08
oansonnick-ma_, yes. That is a very important feature for them09:08
oansondimak, please take that into account in the spec.09:09
oansonPlease don't forget the security considerations as well.09:09
dimaki'll go over it09:09
oansonNext up is deployment09:09
oansonThe nice people from Strato agreed to write an openstack-puppet module.09:10
yuli_sgreat news09:10
hujiefor dragonflow?09:10
oansonI started working with the guys in openstack-ansible on a dragonflow module. The progress can be seen here: https://review.openstack.org/#/c/391524/09:10
oansonhujie, yes09:10
hujiegood09:11
oansonI want to skip ahead to the IPv6, and come back to the other things later09:11
oansonIn IPv6, lihi started looking into it09:11
oansonMany of our applications don't support IPv6. I saw in the review that it was suggested to say the Dragonflow doesn't support IPv6 at all.09:12
*** tinx has joined #openstack-meeting-409:12
oansonI would like to avoid that. It will give off the wrong impression.09:12
oansonI would prefer each application which doesn't support IPv6 to shamefully admit it, and have it fixed09:12
yuli_s;)09:12
*** alij has joined #openstack-meeting-409:13
nick-ma_+109:13
oansonI also think it would be best if lihi marks each such application as she finds them during her tests, and then fix them later, one by one.09:13
oansonlihi, would that be all right?09:13
lihiYeah09:13
oansonGreat.09:14
lihiI already started to do so09:14
oansonGreat.09:14
oansonTap-as-a-service09:14
*** hujie has quit IRC09:14
yuli_sthis is cool service ;)09:14
oansonThis is a new feature that was displayed in the summit. It doesn't seem complex, but needs a carrier.09:14
oansonI mention it since it came up in the fishbowl. I think it could be a DF application, which shouldn't change the rest of the framework. But I didn't give it a lot of thought.09:15
*** iberezovskiy|off is now known as iberezovskiy09:15
yuli_si can probably take it09:15
nick-ma_is it of high priority?09:15
oansonyuli_s, if you have time09:15
yuli_sthanks09:16
oansonnick-ma_, I don't think so.09:16
oansonMostly, I think it is small enough to slip in between the big things, and will be good PR09:16
*** hujie has joined #openstack-meeting-409:16
oansonand would help towards writing troubleshooting tools09:16
nick-ma_that makes sense.09:16
oansonI think the same goes for VLAN aware VMs, but I haven't read the spec on that.09:17
oansonDocumentation:09:17
oansonI would like to enforce function documentation on our code. Any function longer than ~3 lines should have a docstring. It can be a short, single line explaining the gist of the function.09:17
ntr0py\o/09:18
oansonJust so that new contributors and reviewers can understand what a called function does without having to read through tens of lines of code.09:18
nick-ma_+109:18
oansonI will start enforcing this for patches submitted since 1st Nov. (Tomorrow)09:19
dimak+109:19
lihi+1 as well :)09:19
nick-ma_along with unit test.09:19
oansonnick-ma_, yes.09:19
oansonOur unit test framework is advanced enough (thanks to xiaohhui and others) that we can enforce that too09:19
xiaohhui:)09:20
oansonFor the docs, it may be useful to write a pep8 hack. For unit tests, there's a coverage library which may help enforcing that new methods are tested.09:20
oansonBut this requires research, and can be done manually for now09:20
oansonThere was also a request for a migration tool. I started working on it with a guy from Orange in the contributors meeting. I will followup on it. It is both very interesting and very important work.09:22
oansonI hope this work will also pave the way for an external, non-Neutron/openstack API which will facilitate testing and external port deployments09:22
nick-ma_migration from ml2 ovs dvr?09:22
oansonnick-ma_, yes09:22
oansonSince everything is in the Neutron database, and all we need is the NB database populated, I think it should be fairly simple.09:23
*** liwei has quit IRC09:23
oansonI would be happy if anyone who takes a Roadmap item will update the etherpad. This way we can keep track of who does what.09:23
oansonI think there is one last roadmap item: Backend drivers.09:24
oansone.g. supporting P4 and eBPF in addition to OVS/OpenFlow09:24
oansonThis sounds very interesting, but I suspect we are out of hands at the moment.09:24
nick-ma_there is also an integration in OVS upstream to support eBPF.09:25
*** bobmel has joined #openstack-meeting-409:25
oansonnick-ma_, yes. I think that's one of the reasons eBPF is so interesting.09:25
nick-ma_Do you want to follow the ovs or do it ourselves, implementing eBPF control plane?09:25
oansonI was thinking ourselves, so that we won't be tied to OVS09:25
nick-ma_that's cool.09:26
*** bobmel has quit IRC09:26
nick-ma_eBPF is in production, but P4, I don't know.09:26
*** bobmel has joined #openstack-meeting-409:26
oansonI think P4 only has compilation to OpenFlow, or implemented in hardware by some smartnics.09:27
oansonOn one hand it's very flexible. On the other, if no one implements it, it won't help us much :)09:27
*** bobmel has quit IRC09:27
nick-ma_yes.09:27
oansonAny other roadmap items you want to discuss?09:27
nick-ma_dragonflow's northbound api interface?09:28
*** bobmel has joined #openstack-meeting-409:28
oansonYes.09:28
*** bobmel has quit IRC09:28
oansonThe plan is to support our own independent API. This allows dragonflow to be used without Neutron/Openstack, such as in kubernetes, as external ports, testing, etc.09:29
nick-ma_yes.09:29
hujiedoes dragonflow need to do something for dpdk?09:29
nick-ma_i did it before, a simple integration. you can have a try in your hardware environment.09:29
nick-ma_ovs-dpdk09:30
hujieok I see09:30
oansonre standalone api, I think orange will help as part of the migration tool work.09:30
oansonI'll discuss it with the person I met09:30
oanson#topic Performance09:32
*** openstack changes topic to "Performance (Meeting topic: Dragonflow)"09:32
nick-ma_do you wanna land it in the next release? our own api means our own virtual topology definition.09:32
oansonnick-ma_, in theory yes, but I don't think we have the hands for it09:32
nick-ma_ok.09:32
oansonIn performance, there were several discussion of data-plane tests, and Rally came up as the de facto standard for control plane testing09:33
oansonyuli_s, could you look at the Rally gate test, and understand why it is unstable?09:33
yuli_si will take a look09:33
oansonThere are also several options for data-plane testing: Shaker, PerfKit, Browbeat (which is a wrapper). We need to select a direction, and implement a gate test here too. Preferably, cross-node.09:34
oansonyuli_s, could you review the options here to?09:34
yuli_syes, sure09:34
oansonObviously, not everything for next week. But I would like to have the two gate tests up and stable by the end of the cycle09:34
oansonyuli_s, and this should go hand-in-hand with the work you are doing now.09:35
yuli_sok09:36
oansonThank you.09:36
yuli_s;)09:36
oansonAnything else for performance?09:36
yuli_snop, I came in yesterday from a long vocation, so no new findings till now09:36
*** thorst has joined #openstack-meeting-409:36
oanson#topic Bugs09:37
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"09:37
oansonI see there are a bunch of High bugs, but it looks like they are all in progress.09:37
oansonI would like to stress bug-fixing this cycle, but I am not sure how we'll do it in addition to the new features we want.09:38
oansonWe'll review our progress next week and decide. Maybe will take 2 months for features, and 2 months for bug fixing.09:38
oansonI don;t know yet, and would really appreciate suggestions :)09:38
nick-ma_There are also lots of ongoing patches in the gerrit. :-)09:38
*** woodard has joined #openstack-meeting-409:38
oansonYes. :)09:39
oansonBetween the summit, and the holiday that was forced upon us the week before, I didn't do my bit in reviewing.09:39
oansonI will catch up this week.09:39
*** woodard has quit IRC09:39
oansonAnything else for bugs?09:40
nick-ma_that's ok.09:40
xiaohhuiCan we assign a bug triager as neutron does?09:40
oansonxiaohhui, sure.09:40
xiaohhuiWe can swift the role every(two) week09:40
xiaohhuiswitch09:40
oansonxiaohhui, that's a good idea.09:40
*** thorst has quit IRC09:41
lihiThere's an issue with the port status notifier driver09:41
oansonI can take the next two weeks, and we'll find a volunteer afterwards.09:41
oansonIs jingting here?09:41
xiaohhuiGreat, let's see how it is going09:41
lihiThe driver is missing, and devstack fails09:42
hujiejingting is coming09:42
hujiewait a min09:42
xiaohhuiMaybe you need to update your dragonflow by running "python setup.py install"09:42
xiaohhuiI remember I see similar problem09:42
oansonI think I ran into this using a etcd/zmq setup, but didn't have time to review it. Maybe it should be disabled unless redis is used?09:43
nick-ma_i didn't see any redis-related code in port status notifier.09:44
oansonI thought only the redis driver was written, but I may remember wrong.09:44
oansonlihi, if xiaohhui's suggestion doesn't help, please open a critical bug with your local.conf.09:45
dimakyes, it needs redis to work for now or disabled explicitly if not using redis09:45
dimaki came across this as well09:46
lihiI will check and update09:46
*** jingting has joined #openstack-meeting-409:46
oansonlihi, if the issue repeats, we can start by disabling the feature for non-redis configuration.09:46
lihiok09:47
oansonIf I recall correctly, the driver could be modified to be general (and not redis-specific) easily, but since it's critical, I want the fastest, simplest solution first.09:47
nick-ma_yes, i think so.09:48
oansonjingting, in case you missed what we discussed earlier: In some cases devstack fails on the port notification driver. We're not sure if it's for non-redis setups only, or if Dragonflow simply has to be re-installed after a git pull.09:48
oansonjingting, Would you mind taking over testing it? If it is indeed a non-redis configuration thing, the feature should be disabled for non-redis configurations.09:49
oansonAt least until a generic driver is written (which may be extracted from the current redis driver)09:50
jingtingyes, the feature should be disable in non-redis configuration09:50
oansonjingting, could you please upload a patch to do that?09:50
oansonThanks.09:51
*** bobmel has joined #openstack-meeting-409:51
oanson#topic Open Discussion09:51
*** bobmel has quit IRC09:51
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:51
oansonThe floor is for the taking.09:51
jingtingYes, I will do it09:51
oansonIf there is nothing else...09:52
oansonThanks everyone for coming.09:53
nick-ma_thanks all.09:53
xiaohhuibye~09:53
oansonLet's hope this cycle will be as successful as the previous one! :)09:53
oanson#endmeeting09:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:53
openstackMeeting ended Mon Oct 31 09:53:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-10-31-09.00.html09:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-10-31-09.00.txt09:53
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-10-31-09.00.log.html09:53
*** tovin07 has quit IRC09:55
*** dimak has quit IRC09:58
*** bobmel has joined #openstack-meeting-410:03
*** ntr0py has left #openstack-meeting-410:08
*** xiaohhui has quit IRC10:19
*** sambetts_ is now known as sambetts10:21
*** qwebirc67560 has joined #openstack-meeting-410:30
*** qwebirc67560 has quit IRC10:31
*** portdirect has quit IRC10:36
*** alij has quit IRC10:39
*** alij has joined #openstack-meeting-410:39
*** hujie has quit IRC10:39
*** alij has quit IRC10:42
*** alij has joined #openstack-meeting-410:42
*** hujie has joined #openstack-meeting-410:43
*** neiljerram has joined #openstack-meeting-410:46
*** hujie has quit IRC10:46
*** hujie has joined #openstack-meeting-410:47
*** hujie has quit IRC10:49
*** hujie has joined #openstack-meeting-410:50
*** hujie has quit IRC10:52
*** alij has quit IRC10:52
*** hujie has joined #openstack-meeting-410:53
*** aarefiev has joined #openstack-meeting-410:53
*** hujie has quit IRC10:53
*** alij has joined #openstack-meeting-410:54
*** alij_ has joined #openstack-meeting-410:58
*** alij_ has quit IRC10:58
*** alij has quit IRC10:58
*** alij has joined #openstack-meeting-410:58
*** berendt has joined #openstack-meeting-411:05
*** rtheis has joined #openstack-meeting-411:10
*** clayton has quit IRC11:10
*** clayton has joined #openstack-meeting-411:12
*** alij has quit IRC11:16
*** alij has joined #openstack-meeting-411:17
*** berendt has quit IRC11:22
*** alij has quit IRC11:28
*** uli-k has joined #openstack-meeting-411:45
*** bobh has joined #openstack-meeting-411:49
*** cdelatte has joined #openstack-meeting-411:53
*** gongysh has quit IRC11:53
*** uli-k has quit IRC11:55
*** thorst has joined #openstack-meeting-411:55
*** _degorenko|afk is now known as degorenko11:56
*** alij has joined #openstack-meeting-411:56
*** uli-k_ has joined #openstack-meeting-411:56
*** berendt has joined #openstack-meeting-411:59
*** alij has quit IRC12:01
*** fkautz has quit IRC12:03
*** berendt has quit IRC12:04
*** fkautz has joined #openstack-meeting-412:05
*** clayton has quit IRC12:06
*** uli-k_ is now known as uli-k12:06
*** clayton has joined #openstack-meeting-412:07
*** bobh has quit IRC12:26
*** kylek3h_away has quit IRC12:27
*** berendt has joined #openstack-meeting-412:29
*** portdirect has joined #openstack-meeting-412:39
*** links has quit IRC12:50
*** uck has joined #openstack-meeting-412:50
*** dave-mccowan has joined #openstack-meeting-412:53
*** kylek3h_away has joined #openstack-meeting-412:59
*** kylek3h_away has quit IRC12:59
*** kylek3h_away has joined #openstack-meeting-413:00
*** julim has joined #openstack-meeting-413:03
*** tonytan4ever has joined #openstack-meeting-413:10
*** klamath has joined #openstack-meeting-413:13
*** klamath has quit IRC13:13
*** klamath has joined #openstack-meeting-413:14
*** bobmel_ has joined #openstack-meeting-413:22
*** bobmel has quit IRC13:24
*** kylek3h_away is now known as kylek3h13:25
*** limao has joined #openstack-meeting-413:28
*** berendt has quit IRC13:35
*** mohankumar_ has joined #openstack-meeting-413:37
*** bobmel_ has quit IRC13:38
*** singlethink has joined #openstack-meeting-413:39
*** bloatyfloat has left #openstack-meeting-413:50
*** mohankumar_ has quit IRC13:51
*** ivc_ has joined #openstack-meeting-413:52
*** tonytan4ever has quit IRC13:56
*** tonytan_brb has joined #openstack-meeting-413:56
*** rbak has joined #openstack-meeting-413:56
*** julim has quit IRC13:58
*** yfauser has joined #openstack-meeting-413:58
*** yfauser has left #openstack-meeting-413:59
*** apuimedo has joined #openstack-meeting-414:02
apuimedo#startmeeting kuryr14:02
openstackMeeting started Mon Oct 31 14:02:07 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
apuimedoHello everybody and welcome to the first post Ocata Summit Kuryr weekly IRC meeting14:02
apuimedoI expect most of the people to be on holiday or still traveling back14:02
ltomasbohi!14:02
limaoo/14:02
apuimedobut let's see if we get somebody to join14:02
*** yfauser has joined #openstack-meeting-414:03
apuimedoivc_: irenab: you there?14:03
ivc_o/14:04
apuimedovery well, let's get started14:04
apuimedofirst of all, I want to thank you for joining in the work sessions14:05
*** bobh has joined #openstack-meeting-414:05
apuimedo#topic kuryr-libnetwork14:05
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:05
*** oanson has quit IRC14:05
apuimedo#action need to get the ipvlan/macvlan that was used for the demo commited upstream14:06
*** tonytan_brb has quit IRC14:06
*** hemanthm|away is now known as hemanthm14:06
apuimedolimao: you wanted to submit a vlan driver and some network QoS options too, right?14:06
limaoYes14:07
limaoQoS option14:07
ltomasbolimiting max rate?14:07
*** irenab has quit IRC14:07
*** berendt has joined #openstack-meeting-414:07
limaothere is three kind of qos14:07
apuimedothe idea would be to define it as one of the libnetwork option key-values14:07
limaocurrently in neutron14:08
apuimedoand that then it would apply to the ports of that docker neutron-backed network14:08
apuimedoright14:08
limaoyes14:08
ltomasbowould that be needed for the trunk port use case?14:09
ltomasbowill not be enough to apply the QoS in the subport?14:09
*** Drago1 has joined #openstack-meeting-414:09
limaoCurrently it can be only done in network level14:10
apuimedoltomasbo: I'm unsure of how it behaves in neutron in subports14:10
ltomasbonever try it either14:10
limaoYeah, I can try it to see what it happened14:10
apuimedothat would be great14:11
ivc_apuimedo, unless something changed drastically, subports are very similar to regular ports, so qos should work for them14:11
apuimedo#action limao to check how network QoS applies in neutron to ports and subports14:11
apuimedoivc_: yes, but it's a bit of a question whether trunk port restrictions apply to subports14:12
apuimedoat least in my mind14:12
apuimedo(I did not read the ref impl)14:12
*** ruriryan has left #openstack-meeting-414:12
ivc_apuimedo, do we want qos on trunk or subport level?14:12
ivc_or both?14:13
ltomasboI guess subport level, right?14:13
apuimedowell, if it would be possible to support it in both it would be great, but our biggest concern is to have it working at the subport level14:13
ivc_it might be interesting to be able to prioritise one subports over others14:14
*** julim has joined #openstack-meeting-414:14
ivc_that would probably require qos on trunk port14:15
limaoYeah, container level qos14:16
ivc_aye14:16
apuimedowell, subport QoS means that the host must be able to classify by subport origin14:16
apuimedoand apply different htb/hsfc classes14:16
apuimedothat's how I expect it to work14:16
limaowith ipvlan/macvlan, neutron will not support it14:17
apuimedobut again, no idea how it was actually implemented14:17
apuimedolimao: right. We'll have to add that14:17
limaowith ovs driver, neutron use qos in ovs14:17
apuimedo#action talk with Neutron folks about other segmentation types14:17
*** berendt has quit IRC14:18
apuimedolimao: you wanted to add the vlan driver to kuryr-lib, right?14:18
limaoapuimedo: vlan driver?14:18
limaoI'm not sure which part you are talking about14:19
*** vdrok has quit IRC14:19
*** briancurtin has quit IRC14:19
*** spotz_zzz is now known as spotz14:20
apuimedolimao: well, we have ipvlan and macvlan, this was about adding vlan14:20
apuimedofor container-in-vm14:20
*** akwasnie has quit IRC14:20
apuimedobut I think you mentioned using it for having vlan with bare-metal also14:20
limaoNo need add vlan driver in kuryr14:21
limaomacvlan and ipvlan can work in baremetal14:21
apuimedowell, you need the container device to come out tagged14:21
limaothe vlan is in neutron side14:21
apuimedofor neutron default segmentation14:21
ltomasboaren't they go to be directly connected to the ethX.vlan?14:21
*** vdrok has joined #openstack-meeting-414:21
limaoNo do not need container device go out with tagged14:22
apuimedobasically when you join an endpoint to the container14:22
*** dpyzhov has quit IRC14:22
ltomasboeach container to each vlan? or there may be containers in the same vlan?14:22
apuimedoyou need to created a vlan device linked to eth0 of the VM14:22
*** d0ugal has joined #openstack-meeting-414:22
limaosame baremetal host with same vlan14:22
apuimedoand then, on the host side, neutron agent will handle it for you14:22
*** briancurtin has joined #openstack-meeting-414:22
*** akwasnie has joined #openstack-meeting-414:23
limaoapuimedo: if you are talking about macvlan and ipvlan work on baremetal server which created by ironic, it did not need add vlan driver in kuryr14:23
*** dpyzhov has joined #openstack-meeting-414:24
limaoit(Baremetal server) can work with currently vm-nested macvlan and ipvlan14:24
apuimedook14:25
apuimedoso not for the baremetal case14:25
apuimedobut we still need vlan for the nested case14:25
*** berendt has joined #openstack-meeting-414:25
apuimedoso that we can use default neutron subport segmentation14:25
apuimedoltomasbo: will you look into that?14:26
ltomasbobtw, I asked jlibosva and he says: the qos is applied on port on br-int, which in this case is an spi- port14:26
ivc_apuimedo, you mean vlan-aware-vms?14:26
ltomasboI will test it, yes vlan-aware-vm plus kuryr14:26
apuimedoltomasbo: great14:26
ltomasboand automatize the binding14:26
apuimedoivc_: yup14:27
limaooh... you mean vlan-aware-vms , sorry for misunderstand14:27
*** singlethink has quit IRC14:27
apuimedolimao: no, no. When I first asked you, I was asking about both cases ;-)14:27
limaohttps://review.openstack.org/36199314:28
limaoHas vikas choudhary started some work on this?14:29
* apuimedo checking14:29
apuimedoright. This work needs to be resumed14:30
apuimedobut, IIRC, the vlan will be passed as part of the vif oslo versioned object14:30
apuimedoso not much management will be needed14:31
limaoYeah, then we need to sync with vikasc about the status14:31
apuimedo#action apuimedo to sync with vikasc about vlan manager patch14:31
ivc_limao, looking at that review, i'm not sure if "For each container, a subport will be created in neutron and a vlan will14:31
ivc_    be allocated" is right (vlan is per-network/subnet, not per port), i'll take a closer look on that patch14:31
apuimedo#topic kuryr-lib14:32
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:32
apuimedonow that the summit is over, I can resume the cni work14:32
apuimedothe other item is the oslo versioned object binding interface14:32
limaoivc_ : thanks , it is a patch by vikasc14:32
apuimedo#action apuimedo to work on a binding interface that supports oslo versioned vif objects14:33
apuimedowell, and the vlan stuff we just talked about14:33
apuimedoanything else about kuryr-lib?14:33
apuimedo#topic kuryr-kubernetes14:36
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:36
*** yfauser has left #openstack-meeting-414:37
apuimedo#info Today we got a couple devstack fixes merged https://review.openstack.org/390820 https://review.openstack.org/39111614:37
apuimedo#info we also merged more handler patches https://review.openstack.org/388658 https://review.openstack.org/388506 https://review.openstack.org/38619214:37
apuimedo#info and a watcher patch https://review.openstack.org/37604314:37
apuimedowe are missing the kuryr-lib cni part14:37
apuimedoand we'll be able to test the port translation handlers14:38
apuimedoand have CI for that14:38
*** tuan_luong_ has joined #openstack-meeting-414:39
apuimedoanything else about kuryr-kubernetes?14:40
*** uck has quit IRC14:40
*** uck has joined #openstack-meeting-414:41
ivc_only that we decided to use plugins14:41
apuimedoivc_: can you expand on that14:42
apuimedoso I can put it on an #info ?14:42
*** makowals has quit IRC14:43
ivc_well we discussed during summit work sessions that we want to make it configurable what handlers are enabled14:43
apuimedoah, right14:43
ivc_its already in the architecture, just need to implement the framework14:43
apuimedo#action apuimedo to send the summit meeting notes14:43
apuimedothanks ivc_ for the reminder14:45
ivc_i've posted some notes on etherpads during sessions14:45
apuimedoit will help me with sending the notes :-014:45
apuimedo:-)14:45
ivc_maybe you could salvage something from there :)14:45
apuimedoI'll definitely do14:45
*** uck has quit IRC14:45
apuimedootherwise I'll forget even more14:45
apuimedo#topic open discussion14:46
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:46
apuimedodoes anybody have another topic to talk about?14:46
ivc_did we get some attention from other teams/communities during summit?14:46
*** berendt has quit IRC14:47
apuimedowe did have a joint session with Magnum14:47
*** uxdanielle has joined #openstack-meeting-414:47
apuimedoand they helped us understand better their requirements14:47
ivc_like that someone mentioned opendaylight guys have some interest in kuryr14:47
apuimedoyes, I think we'll get some odl people to work on kuryr14:48
apuimedoalso nfv people14:48
apuimedoand kolla-kubernetes14:48
apuimedoportdirect showed us a prototype he has https://github.com/portdirect/harbor for deploying openstack on top of kubernetes with kuryr-kubernetes (he uses a modified midokura PoC)14:49
apuimedoI think he uses it with OVN instead of the ref impl14:50
ivc_we also working on having ost on top of k8s in mirantis :)14:50
apuimedoivc_: You should definitely check out his PoC14:50
apuimedomaybe he can make us an online demo on bluejeans14:50
apuimedothe idea is that harbor will need less code if we can get its pieces into kuryr and kolla kubernetes14:51
ivc_https://www.openstack.org/videos/video/mirantis-evolve-or-die-enterprise-ready-openstack-upgrades-with-kubernetes14:51
ivc_i think thats the session14:51
apuimedoivc_: is that the work of the tcpcloud people?14:51
ivc_aye14:51
apuimedocool14:51
apuimedoI wonder if mirantis has considered joining in kolla-kubernetes14:52
ivc_can't say for sure14:53
apuimedo;-)14:54
apuimedoalright. Anything else before we close the meeting?14:54
*** makowals has joined #openstack-meeting-414:55
apuimedovery well then14:56
apuimedothanks you all for joining14:56
apuimedo#endmeeting14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:56
openstackMeeting ended Mon Oct 31 14:56:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-10-31-14.02.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-10-31-14.02.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-10-31-14.02.log.html14:56
*** syed_ has joined #openstack-meeting-414:58
*** Drago1 has left #openstack-meeting-414:58
*** Tuan_ has joined #openstack-meeting-414:59
sigmavirus#startmeeting craton15:00
openstackMeeting started Mon Oct 31 15:00:03 2016 UTC and is due to finish in 60 minutes.  The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: craton)"15:00
openstackThe meeting name has been set to 'craton'15:00
sigmavirus#chair jimbaker15:00
openstackCurrent chairs: jimbaker sigmavirus15:00
sigmavirus#link https://etherpad.openstack.org/p/craton-meetings15:00
sigmavirus#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: craton)"15:00
*** chrisspencer has joined #openstack-meeting-415:00
chrisspencero/15:01
syed_o/15:01
sigmavirusIt seems like jimbaker and sulo are still readjusting from their travels to Spain15:01
sigmavirusThere's nothing on the Agenda for today15:01
*** tuan_luong_ has quit IRC15:01
lcastello/15:01
sigmavirus#topic updates15:02
*** openstack changes topic to "updates (Meeting topic: craton)"15:02
sigmavirusLet's just roll through some updates from folks. Shall we start with syed_ ?15:02
syed_Sounds cool15:02
*** jovon has joined #openstack-meeting-415:02
sigmavirussyed_: how's the keystone testing going?15:03
syed_Was working with Keystone auth and got that resolved, probably will be doing some more tests and then start with horizon folks15:03
syed_its going well till now, works fine, thanks15:03
syed_digging into the functional testing aspect of craton, so probably will be updating on that later this week15:03
syed_and waiting to get updates on how the summit went :)15:04
sigmaviruschrisspencer: how about you?15:05
chrisspencergot my last couple outstanding reviews commited and was able to provide a couple +1s for others15:05
sigmavirusjovon: any updates?15:06
jovonworking on cleaning the doc fixes and implementing devices15:08
*** Tuan_ has quit IRC15:08
sigmavirusanyone else have updates?15:10
syed_I am good15:10
sigmaviruslcastell: any updates on your end?15:11
* sigmavirus knew he missed someone ;)15:11
lcastellI'll try to start testing the client integration with the horizon plugin this week15:11
lcastellI've been caught in other projects and ss far I haven't had the chance to start testing sigmavirus15:12
*** mdorman has joined #openstack-meeting-415:12
sigmavirusWell jimbaker and sulo haven't showed up. My stalling tactic has failed15:12
*** limao_ has joined #openstack-meeting-415:13
sigmavirus#action jimbaker and sulo to send summaries from Barcelona to the mailing list with the [craton] tag so we can all live vicariously through their memories15:13
sigmavirus#topic Q&A/Wrap-up15:13
*** openstack changes topic to "Q&A/Wrap-up (Meeting topic: craton)"15:13
sigmavirusDoes anyone have any questions before I close out this meeting?15:13
jovonno. thank you15:14
syed_Thanks15:14
sigmavirusThanks y'all15:14
sigmavirus#info Ending the meeting early as there's not much to discuss15:14
sigmavirus#endmeeting15:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:14
openstackMeeting ended Mon Oct 31 15:14:44 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-10-31-15.00.html15:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-10-31-15.00.txt15:14
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-10-31-15.00.log.html15:14
*** mdorman has left #openstack-meeting-415:15
*** limao has quit IRC15:15
*** chrisspencer has left #openstack-meeting-415:15
*** turvey has joined #openstack-meeting-415:19
*** baoli has joined #openstack-meeting-415:21
*** krtaylor has quit IRC15:33
*** limao_ has quit IRC15:35
*** Jeffrey4l has joined #openstack-meeting-415:38
*** Jeffrey4l has quit IRC15:39
*** Jeffrey4l has joined #openstack-meeting-415:40
*** ivc_ has left #openstack-meeting-415:41
*** Jeffrey4l has quit IRC15:41
*** apuimedo has quit IRC15:42
*** Jeffrey4l has joined #openstack-meeting-415:42
*** irenab has joined #openstack-meeting-415:47
*** bobh_ has joined #openstack-meeting-415:52
*** bobh has quit IRC15:53
*** bobmel has joined #openstack-meeting-415:54
*** m1dev____ has joined #openstack-meeting-415:56
*** makowals has quit IRC15:59
*** Tamayo has joined #openstack-meeting-416:05
*** lihi has quit IRC16:06
*** bobmel_ has joined #openstack-meeting-416:08
*** iyamahat has joined #openstack-meeting-416:10
*** bobmel has quit IRC16:11
*** stevelle has left #openstack-meeting-416:13
*** bobmel has joined #openstack-meeting-416:13
*** makowals has joined #openstack-meeting-416:14
*** bobmel_ has quit IRC16:17
*** yamahata has joined #openstack-meeting-416:17
*** makowals has quit IRC16:17
*** makowals has joined #openstack-meeting-416:22
*** kfox1111_ is now known as kfox111116:23
*** khushbu has joined #openstack-meeting-416:29
*** links has joined #openstack-meeting-416:31
*** julim_ has joined #openstack-meeting-416:35
*** makowals has quit IRC16:36
*** julim has quit IRC16:37
*** makowals has joined #openstack-meeting-416:37
*** kbyrne has joined #openstack-meeting-416:41
*** links has quit IRC16:42
*** tuan_luong has joined #openstack-meeting-416:51
*** david-lyle has joined #openstack-meeting-416:51
*** Jeffrey4l has quit IRC16:52
*** tuan_luong has quit IRC16:54
*** d0ugal has quit IRC16:54
*** iyamahat has quit IRC16:58
*** iyamahat has joined #openstack-meeting-416:58
*** d0ugal has joined #openstack-meeting-416:58
*** d0ugal has quit IRC16:58
*** d0ugal has joined #openstack-meeting-416:58
*** belmoreira has quit IRC16:58
*** mjturek has joined #openstack-meeting-416:59
*** krtaylor has joined #openstack-meeting-417:00
gnuoy\o17:01
tinwoodo/ gnuoy17:01
gnuoytinwood, lets give other peeps a few mins17:01
tinwoodok17:01
*** devananda|summit is now known as devananda17:02
gnuoyok, I'm going in...17:02
gnuoy #startmeeting charms17:02
gnuoy#startmeeting charms17:03
openstackMeeting started Mon Oct 31 17:03:01 2016 UTC and is due to finish in 60 minutes.  The chair is gnuoy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: charms)"17:03
openstackThe meeting name has been set to 'charms'17:03
gnuoyI'm guessing beisner and jamespage aren't here ?17:03
beisnero/17:03
gnuoy\o17:03
gnuoyFrom last time : ACTION: beisner regular upgrade tests17:04
gnuoyshould I carry that forward?17:04
*** bobmel has quit IRC17:04
gnuoy#topic Review ACTION points from previous meeting17:04
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:04
beisnerwe have charm upgrade mojo specs running daily, and openstack package upgrade mojo specs running at the same frequency17:04
*** bobmel has joined #openstack-meeting-417:05
gnuoywas that action supposed to cover multi release upgrades as well or not?17:05
gnuoyL-M->N17:05
beisnergnuoy, i'm lost in the context of that action though.  was that for the multi-upgrade path?  ie. i -> j -> k -> l -> m -> n17:05
gnuoyhaha17:05
gnuoynot sure, let me check17:05
gnuoybeisner, err I don't see it in the previous meeting summary tb h17:06
gnuoylets move on17:06
beisnerok, let's call it multi-step upgrade and carry that forward17:07
gnuoyack17:07
gnuoy#action beisner mutli-step upgrades17:07
gnuoy#topic State of Development for next Charm Release17:07
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:07
gnuoytinwood, hows the manilla charm?17:07
tinwoodgetting very close now.  Now handling multiple conversations in the interface, and needing to write tests, but it was basically working until I split it up.17:08
gnuoytinwood, kk, theres a cephfs charm too right?17:08
tinwoodgnuoy, wrt to manila, no, but now very easy to add one.17:09
gnuoykk17:09
tinwoodor as a separate cephfs charm?17:09
gnuoyI think there is a seperate cephfs charm but I may be making that up17:09
tinwoodWe need to check with the storage charm folks.17:10
tinwoodI'll take an action if you'd like?17:10
*** thorst has quit IRC17:10
gnuoy#action tinwood update at the next meeting wrt manilla and cephfs charms17:10
gnuoytinwood, thanks17:10
tinwoodnp17:10
*** thorst has joined #openstack-meeting-417:11
gnuoyTheres been some requests for openstack dashboard integration which I'll try and take a look soon17:11
gnuoyanything else anyone wants to point at for 17.01 ?17:11
*** thorst_ has joined #openstack-meeting-417:12
gnuoy...17:12
gnuoy#topic High Priority Bugs17:12
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:12
gnuoySo, I think rabbit + DNS has raised its head again17:12
gnuoyI mean: Rabbit - ~DNS17:12
gnuoyhttps://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/158490217:13
openstackLaunchpad bug 1584902 in rabbitmq-server (Juju Charms Collection) "Setting RabbitMQ NODENAME to non-FQDN breaks on MaaS 2.0" [High,New] - Assigned to James Page (james-page)17:13
gnuoyI think17:13
gnuoyanything else?17:13
gnuoyok then17:14
gnuoy#topic Openstack Events17:14
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:14
gnuoyWell ODS was just a thing17:14
tinwoodHow was it17:15
*** m1dev____ has quit IRC17:15
gnuoygood thanks17:15
*** thorst has quit IRC17:15
gnuoythe fishbowls and working session on the friday were really good17:15
gnuoythedac and I are going to work up a spec for the single API haproxy solution17:16
tinwoodsounds good.17:16
*** thorst_ has quit IRC17:16
gnuoy#action gnuoy Loadbalancer spec17:16
beisnerfood for thought: i believe rmq can now cluster with nodenames being IP address, if we stop using sname (ie. use long name).  i'd like to see us try that.  ultimately, until we get consistent dns records from the underlying tooling, i think anything we do will be brittle.17:17
gnuoyI'm going to plough on unless anyone has anything else for events?17:17
gnuoy#topic Open Discussion17:17
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:17
tinwoodnope, I'm good.17:17
gnuoyAnything to openly discuss?17:18
gnuoy...17:18
tinwoodno, I'm good.17:19
gnuoyOk, next meeting is two weeks time same time (17:00 UTC) and thedac is chairing!17:19
gnuoy#endmeeting17:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:19
openstackMeeting ended Mon Oct 31 17:19:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-10-31-17.03.html17:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-10-31-17.03.txt17:19
tinwoodthanks gnuoy :)17:19
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-10-31-17.03.log.html17:19
beisnero/ thanks gnuoy17:19
gnuoynp17:19
tinwoodhave a good evening.17:19
*** thorst has joined #openstack-meeting-417:21
*** thorst has quit IRC17:21
*** thorst has joined #openstack-meeting-417:22
*** thorst has quit IRC17:26
*** thorst has joined #openstack-meeting-417:26
*** armax has joined #openstack-meeting-417:29
*** crinkle has left #openstack-meeting-417:31
*** uck has joined #openstack-meeting-417:43
*** dave-mccowan has quit IRC17:49
*** Tamayo has quit IRC17:52
*** s3wong has joined #openstack-meeting-417:55
*** iyamahat has quit IRC17:58
*** julim_ has quit IRC18:00
*** asettle has joined #openstack-meeting-418:00
*** julim has joined #openstack-meeting-418:00
*** sambetts is now known as sambetts|afk18:17
*** hemanthm is now known as hemanthm|lunch18:18
*** dave-mccowan has joined #openstack-meeting-418:19
*** portdirect_ has joined #openstack-meeting-418:21
*** uck_ has joined #openstack-meeting-418:24
*** uck has quit IRC18:24
*** portdirect has quit IRC18:24
*** khushbu has quit IRC18:26
*** uck_ has quit IRC18:27
*** uck has joined #openstack-meeting-418:27
*** iberezovskiy is now known as iberezovskiy|off18:28
*** armax has quit IRC18:35
*** asettle has quit IRC18:47
*** asettle has joined #openstack-meeting-418:48
*** asettle has quit IRC18:48
*** asettle has joined #openstack-meeting-418:48
*** tonytan4ever has joined #openstack-meeting-418:50
*** asettle has quit IRC18:52
*** asettle has joined #openstack-meeting-418:52
*** spotz is now known as spotz_zzz18:57
*** Rockyg has joined #openstack-meeting-419:01
*** hemanthm|lunch is now known as hemanthm19:03
*** baoli has quit IRC19:09
*** piet has joined #openstack-meeting-419:09
*** vishwanathj has joined #openstack-meeting-419:12
*** vishwanathj has quit IRC19:25
*** liangy has joined #openstack-meeting-419:25
*** vishwanathj has joined #openstack-meeting-419:26
*** apuimedo has joined #openstack-meeting-419:30
*** vishwanathj has quit IRC19:31
*** vishwanathj has joined #openstack-meeting-419:32
*** apuimedo has quit IRC19:37
*** spotz_zzz is now known as spotz19:38
*** jovon has quit IRC19:47
*** vishwanathj has quit IRC19:58
*** vishwanathj has joined #openstack-meeting-419:59
*** portdirect_ is now known as portdirect20:08
*** dave-mccowan has quit IRC20:15
*** cdelatte has quit IRC20:17
*** iyamahat has joined #openstack-meeting-420:19
*** julim has quit IRC20:34
*** d0ugal has quit IRC20:40
*** d0ugal has joined #openstack-meeting-420:42
*** krtaylor has quit IRC20:43
*** dave-mccowan has joined #openstack-meeting-420:45
*** piet has quit IRC20:45
*** m1dev has joined #openstack-meeting-421:01
*** m1dev has quit IRC21:03
*** m1dev has joined #openstack-meeting-421:03
*** tonytan4ever has quit IRC21:13
*** apuimedo has joined #openstack-meeting-421:14
*** vishwanathj has quit IRC21:17
*** vishwanathj has joined #openstack-meeting-421:18
*** thorst has quit IRC21:19
*** bobh_ has quit IRC21:19
*** bobh has joined #openstack-meeting-421:19
*** thorst has joined #openstack-meeting-421:19
*** m1dev has quit IRC21:22
*** bobh has quit IRC21:23
*** rtheis has quit IRC21:23
*** thorst has quit IRC21:23
*** hippiepete has quit IRC21:26
*** Rockyg has quit IRC21:27
*** vishwanathj has quit IRC21:29
*** vishwanathj has joined #openstack-meeting-421:30
*** vishwanathj has quit IRC21:36
*** vishnoianil has joined #openstack-meeting-421:37
*** vishwanathj has joined #openstack-meeting-421:37
*** kylek3h has quit IRC21:37
*** vishwanathj has quit IRC21:37
*** dave-mccowan has quit IRC21:38
*** vishwanathj has joined #openstack-meeting-421:38
*** thorst has joined #openstack-meeting-421:45
*** thorst has quit IRC21:49
*** krtaylor has joined #openstack-meeting-422:07
*** rbak has quit IRC22:29
*** armax has joined #openstack-meeting-422:37
*** thorst has joined #openstack-meeting-422:37
*** klamath has quit IRC22:52
*** hemanthm is now known as hemanthm|away22:52
*** apuimedo has quit IRC22:56
*** uck_ has joined #openstack-meeting-423:00
*** uck has quit IRC23:00
*** thorst has quit IRC23:03
*** thorst has joined #openstack-meeting-423:04
*** spotz is now known as spotz_zzz23:07
*** apuimedo has joined #openstack-meeting-423:07
*** asettle has quit IRC23:11
*** thorst has quit IRC23:17
*** kylek3h has joined #openstack-meeting-423:22
*** apuimedo has quit IRC23:32
*** apuimedo has joined #openstack-meeting-423:43
*** iyamahat has quit IRC23:46
*** uck_ has quit IRC23:53

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