Monday, 2016-09-19

*** zhurong has quit IRC00:07
*** gongysh has quit IRC00:12
*** admcleod_ has joined #openstack-meeting-400:19
*** admcleod has quit IRC00:20
*** tuanla_ has joined #openstack-meeting-400:27
*** sdake has quit IRC00:28
*** spzala has joined #openstack-meeting-400:28
*** thorst has joined #openstack-meeting-400:29
*** spzala has quit IRC00:33
*** thorst has quit IRC00:37
*** spotz_zzz is now known as spotz00:42
*** hieulq has joined #openstack-meeting-400:45
*** limao has joined #openstack-meeting-400:48
*** baoli has quit IRC00:56
*** baoli has joined #openstack-meeting-400:59
*** baoli has quit IRC00:59
*** baoli has joined #openstack-meeting-400:59
*** zhurong has joined #openstack-meeting-401:09
*** yamamoto has joined #openstack-meeting-401:14
*** thorst has joined #openstack-meeting-401:14
*** thorst has quit IRC01:15
*** thorst has joined #openstack-meeting-401:16
*** tonytan_brb has joined #openstack-meeting-401:19
*** tonytan4ever has quit IRC01:21
*** thorst has quit IRC01:24
*** david-lyle has joined #openstack-meeting-401:27
*** david-lyle has quit IRC01:31
*** bpokorny has joined #openstack-meeting-401:38
*** baoli has quit IRC01:39
*** baoli has joined #openstack-meeting-401:40
*** bobh has quit IRC01:40
*** salv-orl_ has joined #openstack-meeting-401:41
*** bpokorny has quit IRC01:43
*** zhurong has quit IRC01:43
*** zhurong has joined #openstack-meeting-401:44
*** woodard has joined #openstack-meeting-401:44
*** baoli has quit IRC01:45
*** salv-orlando has quit IRC01:45
*** woodard has quit IRC01:49
*** jamesdenton has joined #openstack-meeting-401:50
*** spotz is now known as spotz_zzz01:50
*** dkehn has quit IRC01:56
*** Sukhdev has joined #openstack-meeting-401:59
*** coolsvap has joined #openstack-meeting-402:01
*** bobh has joined #openstack-meeting-402:06
*** dkehn has joined #openstack-meeting-402:07
*** thorst has joined #openstack-meeting-402:22
*** thorst has quit IRC02:29
*** zhurong has quit IRC02:39
*** caowei has joined #openstack-meeting-402:41
*** baoli has joined #openstack-meeting-402:42
*** zhurong has joined #openstack-meeting-402:43
*** baoli has quit IRC02:47
*** yamamoto has quit IRC02:53
*** janonymous has joined #openstack-meeting-402:57
*** jingting has quit IRC03:00
*** jingting has joined #openstack-meeting-403:05
*** baoli has joined #openstack-meeting-403:07
*** uck has joined #openstack-meeting-403:14
*** bobh has quit IRC03:24
*** markvoelker has joined #openstack-meeting-403:25
*** thorst has joined #openstack-meeting-403:26
*** baoli has quit IRC03:32
*** thorst has quit IRC03:34
*** yamamoto has joined #openstack-meeting-403:53
*** yamamoto has quit IRC04:01
*** jingting has quit IRC04:02
*** jingting has joined #openstack-meeting-404:07
*** salv-orl_ has quit IRC04:12
*** salv-orlando has joined #openstack-meeting-404:13
*** yamamoto has joined #openstack-meeting-404:28
*** limao has quit IRC04:29
*** uck has quit IRC04:31
*** thorst has joined #openstack-meeting-404:32
*** psachin_ has joined #openstack-meeting-404:32
*** yamamoto has quit IRC04:37
*** davidlenwell has quit IRC04:37
*** thorst has quit IRC04:39
*** tuanla_ has quit IRC04:48
*** davidlenwell has joined #openstack-meeting-404:49
*** janki has joined #openstack-meeting-404:57
*** uck has joined #openstack-meeting-404:58
*** uck has quit IRC04:58
*** limao has joined #openstack-meeting-404:59
*** pcaruana has quit IRC05:05
*** icey has quit IRC05:14
*** yamamoto has joined #openstack-meeting-405:19
*** tuanla_ has joined #openstack-meeting-405:24
*** prateek_ has joined #openstack-meeting-405:31
*** mfedosin has joined #openstack-meeting-405:34
*** thorst has joined #openstack-meeting-405:37
*** baoli has joined #openstack-meeting-405:44
*** thorst has quit IRC05:45
*** baoli has quit IRC05:49
*** yamamoto has quit IRC05:49
*** vishnoianil has quit IRC05:50
*** tonytan_brb has quit IRC05:52
*** uck has joined #openstack-meeting-405:52
*** uck has quit IRC05:57
*** vishnoianil has joined #openstack-meeting-406:01
*** GB21 has joined #openstack-meeting-406:03
*** jichen has joined #openstack-meeting-406:07
*** pcaruana has joined #openstack-meeting-406:17
*** dtardivel has joined #openstack-meeting-406:24
*** yamamoto has joined #openstack-meeting-406:29
*** thorst has joined #openstack-meeting-406:42
*** uck has joined #openstack-meeting-406:48
*** thorst has quit IRC06:49
*** uck has quit IRC06:52
*** s3wong has joined #openstack-meeting-407:11
*** s3wong has quit IRC07:11
*** berendt has joined #openstack-meeting-407:11
*** coolsvap is now known as _coolsvap_07:13
*** Sukhdev has quit IRC07:21
*** matrohon has joined #openstack-meeting-407:37
*** jingting has quit IRC07:41
*** salv-orl_ has joined #openstack-meeting-407:41
*** ricolin has joined #openstack-meeting-407:42
*** yamamoto has quit IRC07:43
*** salv-orlando has quit IRC07:44
*** yamamoto has joined #openstack-meeting-407:45
*** tonytan4ever has joined #openstack-meeting-407:46
*** thorst has joined #openstack-meeting-407:47
*** tonytan4ever has quit IRC07:51
*** alexchadin has joined #openstack-meeting-407:52
*** amitkqed has quit IRC07:53
*** amitkqed has joined #openstack-meeting-407:54
*** thorst has quit IRC07:55
*** xiaohhui_ has joined #openstack-meeting-407:58
*** yamamoto has quit IRC08:02
*** yamamoto has joined #openstack-meeting-408:03
*** xiaohhui_ has quit IRC08:04
*** oshidoshi has joined #openstack-meeting-408:05
*** cjloader has quit IRC08:13
*** antonym has quit IRC08:13
*** cloader89 has joined #openstack-meeting-408:14
*** antonym has joined #openstack-meeting-408:15
*** oshidoshi has left #openstack-meeting-408:21
*** yamamoto has quit IRC08:35
*** yamamoto has joined #openstack-meeting-408:36
*** yamamoto has quit IRC08:40
*** yamamoto has joined #openstack-meeting-408:40
*** yamamoto has quit IRC08:40
*** yamamoto has joined #openstack-meeting-408:41
*** yamamoto has quit IRC08:46
*** neiljerram has joined #openstack-meeting-408:49
*** neiljerram has quit IRC08:49
*** thorst has joined #openstack-meeting-408:51
*** neiljerram has joined #openstack-meeting-408:52
*** thorst has quit IRC08:58
*** lihi has joined #openstack-meeting-408:59
*** oanson has joined #openstack-meeting-408:59
*** hujie has joined #openstack-meeting-409:00
*** xiaohhui has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Sep 19 09:00:38 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
*** anilvenkata has joined #openstack-meeting-409: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
oansonAll right. Who is here for the meeting?09:00
xiaohhuihi09:00
lihio/09:01
hujieHi09:01
oansonnick-ma, are you here?09:01
*** jingting has joined #openstack-meeting-409:01
oansonIt looks like I forgot to set up an agenda, so we'll follow last week's, and I'll do better next time :)09:02
oanson#topic Roadmap09:02
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:02
oansonThe good news is that ML2 fullstack tests are working09:02
oansonAnd it looks like both ML2 and core plugin fullstack tests are stable09:02
xiaohhuigreat09:02
oansonThat includes security groups.09:03
oansonI think this is very good news. Thanks everyone for a great effort in this department.09:03
xiaohhuioanson: have you insert some ml2 specific options for ml2 fullstack test?09:03
oansonxiaohhui, yes, the fullstack-ml2 uses the mechanism driver + ML209:04
oansonBut nothing beyond that.09:04
oansonIs there something you think should be there?09:04
xiaohhuiI am checking the failed fullstack in ml2 for vlan network, I wonder where did the network_vlan_ranges set?09:05
xiaohhuiIt looks like by default it will be empty09:05
oansonIIRC (I looked into it a while back) it's a Neutron configuration. We may need to set it in plugin.sh, or understand what's Neutron's defaults.09:05
xiaohhuineutron's default is an empty list...09:06
*** edleafe has quit IRC09:07
xiaohhuihttps://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_vlan.py#L3509:07
*** edleafe has joined #openstack-meeting-409:07
hujiewhat about in /etc/neutron/plugins/ml2/ml2_conf.ini?09:07
oansonSame for flat networks: https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/type_flat.py#L3309:07
oansonLooks like '*' means any flat/vlan networks, and empty list to disable the feature09:08
oanson'*' not supported for vlan09:08
xiaohhuiThat is also my understanding09:08
xiaohhuihujie: In my ml2 env, the ml2_conf.ini will not have network_vlan_ranges.09:09
oansonFor the tests, we can add a fake network, with a fake OVS bridge. We can maybe attach to it some tap devices to make sure the network connection works.09:09
*** _degorenko|afk is now known as degorenko09:09
oansonAnd use set_override in the configuration for the tests09:10
oansonI can help writing something if needed.09:10
xiaohhuiYeah, we may need further look to the test. I am not sure if set_override will work in fullstack, because in fullstack, the test runs after everything is set up.09:11
oansonSome code to create a br-<vlan network>, attach a tap device to it, attach it to br-int using the physical network code, and see that packets make it as expected09:11
oansonWe can update the local.conf generated by the fullstack test to include the relevant information09:12
oansonAnd have plugin.sh read the information and update the configuration files.09:12
oansonThis is something we probably need in devstack anyway09:12
xiaohhuiyes, I think we should push some fake config to the ml2 fullstack env09:12
oansonWe can even have devstack attach automatically the external interfaces, but this should wait for a different patch09:13
oanson(According to config, of course)09:13
xiaohhuiI remember devstack have such config for user to config vlan/flat. I just can't recall the details09:14
xiaohhuiit should be in a different patch09:14
xiaohhuiWe can focus on the current patch to make it pass the fullstack first09:14
oansonYes.09:15
oansonBut we should align ourselves to devstack configuration. Either in this patch (if possible) or next patch if too complex.09:15
oansonWe can cut out any default configuration and construction for now.09:15
oansonxiaohhui, is this reasonable? Or still too much?09:16
xiaohhuiI think it makes sense.09:16
oansonGreat! :)09:16
oansonIs this item closed for now?09:17
xiaohhuiyeah09:17
oansonGreat. Thanks!09:17
oansonThe next item is port status notification09:17
oansonI think jingting's patch is very close to being ready for merge, with a few minor issues09:17
jingtingyes, i will fix it soon09:18
oansonPackaging will wait for Ocata. it isn't reasonable that it will be ready by the summit. I think there is enough work with VLAN/flat networks, port status, and the other things we're working on.09:19
oansonThe QoS code is also in review. I was mainly reviewing the North Bound, and I see nick-ma is reviewing the south bound as well.09:20
oansonhujie, I see the db consistency patch stopped making progress.09:22
oansonAre you still working on it>?09:22
hujiesorry, I paid my most time working on HWS+dragonflow test currently09:23
oansonI see.09:23
hujieand I will try my best to working on it09:23
oansonThis means that patch https://review.openstack.org/#/c/331132/ is also halted for now (remote port function)?09:23
hujiedb consistency\remote port\bug fix09:23
hujieI'll try to fix remote port this week09:24
oansonBecause I think it is very close to being finished, and it would be a strong feature for Newton (cloud inter-operability and the such)09:24
oansonGreat. Thanks!09:24
hujieI'll try to working on db consistency next week:)09:24
oansonVery good.09:25
oanson#topic Performance09:25
*** openstack changes topic to "Performance (Meeting topic: Dragonflow)"09:25
oansonyuli_s isn't in today09:25
oansonBut he sent me the results.09:25
xiaohhuiIs there any work item to improve performance?09:26
hujiewhat's the result??09:27
oansonIn a test of 4000+ df controller nodes, 1 Neutron server, and redis spread over (I think, because I can't find it in the email) 8 servers09:27
*** sambetts|afk is now known as sambetts09:27
oansonxiaohhui, once we have results, we can decide if they are good enough.09:27
*** dshakhray has joined #openstack-meeting-409:27
oansonhujie, one sec, I am trying to read this cryptic email :)09:27
hujieok :)09:27
oansonCreation of 50 subnets took ~49 seconds. That means ~1 subnet / second.09:27
oansonWhich I think is good results.09:28
oansonCreating a port per subnet took 17 seconds. i.e. 50 ports in 17 seconds is almost 3 ports/second09:28
*** yuval has joined #openstack-meeting-409:28
oansonCreating 5 ports per subnet (in addition) takes ~86 seconds, which is also almost 3 ports per second (2.9).09:29
oansonThere were 250 ports created in that test.09:29
hujiewhat's the performance data for native Neutron without dragonflow?09:29
*** uck has joined #openstack-meeting-409:29
oansonI don't have that. I can look up the performance benchmarks for the reference implementation for next meeting.09:29
hujieok thanks09:30
oansonIf we'll manage to keep the environment, we may be able to compare with OVN, opendaylight, etc.,09:30
oansonOn the other hand, I am not sure this is where we should invest our time.09:30
oansonI think it is important first and foremost to verify that we operate fast enough to be deployed in a cloud of thousands of nodes.09:30
oansonIIRC, we wanted to reach 10000 :)09:31
oansonBut I find these numbers very hopeful.09:31
oansonWe don't have permanent servers for this, but the best thing would be to re-run this benchmark automatically on a weekly basis. But this is a long-term dream for now :)09:32
oansonThat's what I have for now.09:32
xiaohhuiThanks oanson for sharing09:32
oanson#topic Bugs09:33
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"09:33
hujiedo you want to add stress test?09:33
oansonhujie, yes. What did you have in mind?09:33
oansonI think the tempest and rally should do something like that as well, but they have to be stabalised.09:34
*** uck has quit IRC09:34
hujieI just wonder whether the db cluster is stable enough in the stress test09:34
oansonThis is definitely something that needs to be tested.09:35
hujieok good thx09:35
oansonThis may also be the instability we see in the rally and tempest tests.09:35
hujieok let's move on please :)09:36
oansonIn bugs, I see that all high importance bugs are assigned09:36
oansonThere were a few Undecided, but I changed that.09:36
oansonSince there is nothing critical, I think we can move on.09:37
oanson#topic Open Discussion09:37
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:37
oansonThe floor is for the taking09:37
hujiewhat's the most important feature for us to support in the future?09:38
xiaohhuiAnd is there a plan in O release?09:39
oansonThere are plans for O release.09:39
oansonI think the most important thing for O release is deployment. I will make sure I have the time to work on this09:39
oansonI am looking into openstack-ansible, and nick-ma mentioned that he may be looking into kolla. If anyone wants to look into openstack-puppet or Fuel, that would be great09:40
oanson(But not urgent. That's for next cycle)09:40
oansonAdditionally, there are many Neutron features we can implement, e.g. FW, LB, VPN, etc.09:40
oansonFull IPv6 support is important09:40
oansonThese are the options that immediately spring to mind09:41
xiaohhuiWhat about the snat?09:41
hujiein the etc...09:41
oansonxiaohhui, yes.09:41
oansonWhatever potential deployers think is important. I would really like to get our user-base to grow09:42
*** jorgem has quit IRC09:42
*** yamamoto has joined #openstack-meeting-409:42
oansonI hope in the Barcelona summit to meet both deployers and developers, and get a clear picture of what are the priorities09:42
hujieyes09:42
oansonI also have a personal dream of SFC, but I don't know if that would fit Ocata. It may have to wait for P cycle, but I will see if I can catch the networking-sfc people in the summit as well.09:43
oansonI will organise a list on etherpad, so we will have a more organised vision09:44
*** jorgem has joined #openstack-meeting-409:44
hujieok thx09:45
oansonOf course, this is a democracy. If there is something you want, I would love to hear it!09:45
oansonOnce the etherpad will be ready, you could just add it there as we go.09:46
hujiedoes Ashed still working on dragonflow?09:46
oansonhujie, yes.09:47
hujieok good09:47
*** tonytan4ever has joined #openstack-meeting-409:47
oansonBut he is taking a less technical role, and a more community role09:47
hujieok got it :)09:47
oansonAnything else?09:48
xiaohhuiNothing from me09:48
hujieIt's the supper time in beijing :)09:48
oansonAll right.09:48
oansonThe enjoy your meal.09:48
*** yamamoto has quit IRC09:48
xiaohhuiThanks~09:48
oansonIt's lunch time here, so we're hungry too :)09:48
hujiethx :)09:48
oansonThanks for coming, and for a great effort!09:49
oanson#endmeeting09:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:49
openstackMeeting ended Mon Sep 19 09:49:08 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-09-19-09.00.html09:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-09-19-09.00.txt09:49
*** yuval has left #openstack-meeting-409:49
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-09-19-09.00.log.html09:49
*** xiaohhui has quit IRC09:49
*** tonytan4ever has quit IRC09:52
*** aderyugin has quit IRC09:55
*** velovec has joined #openstack-meeting-409:55
*** velovec is now known as aderyugin09:56
*** tinwood has quit IRC09:57
*** tinwood has joined #openstack-meeting-409:59
*** zhurong has quit IRC10:00
*** thorst has joined #openstack-meeting-410:08
*** limao has quit IRC10:11
*** ricolin has quit IRC10:20
*** lihi has left #openstack-meeting-410:27
*** thorst has quit IRC10:35
*** sdague has joined #openstack-meeting-410:51
*** mfedosin has quit IRC10:51
*** aunnam has quit IRC11:00
*** aunnam has joined #openstack-meeting-411:01
*** aunnam has quit IRC11:02
*** aunnam has joined #openstack-meeting-411:03
*** rtheis has joined #openstack-meeting-411:04
*** nishpatwa_ has quit IRC11:04
*** dasanind has quit IRC11:04
*** dharinic has quit IRC11:04
*** shasha_tavil has quit IRC11:04
*** aunnam_ has quit IRC11:04
*** pumaranikar has quit IRC11:04
*** _sigmavirus24 is now known as sigmavirus11:06
*** sigmavirus has joined #openstack-meeting-411:06
*** tuanla_ has quit IRC11:07
*** uck has joined #openstack-meeting-411:17
*** shasha_tavil has joined #openstack-meeting-411:18
*** caowei has quit IRC11:18
*** uck has quit IRC11:22
*** alexchadin has quit IRC11:22
*** aunnam_ has joined #openstack-meeting-411:23
*** dharinic has joined #openstack-meeting-411:27
*** zenoway has joined #openstack-meeting-411:42
*** thorst has joined #openstack-meeting-411:42
*** oanson has left #openstack-meeting-411:45
*** thorst has quit IRC11:46
*** tonytan4ever has joined #openstack-meeting-411:48
*** sdake has joined #openstack-meeting-411:49
*** markvoelker has quit IRC11:51
*** tonytan4ever has quit IRC11:52
*** mfedosin has joined #openstack-meeting-412:00
*** icey has joined #openstack-meeting-412:00
*** woodard has joined #openstack-meeting-412:01
*** bobh has joined #openstack-meeting-412:01
*** barmaley has joined #openstack-meeting-412:03
*** alexchadin has joined #openstack-meeting-412:04
*** woodard has quit IRC12:06
*** GB21 has quit IRC12:07
*** yamamoto has joined #openstack-meeting-412:08
*** sdake has quit IRC12:13
*** sdake has joined #openstack-meeting-412:14
*** hemanthm|vto is now known as hemanthm12:15
*** yamamoto has quit IRC12:15
*** baoli has joined #openstack-meeting-412:16
*** baoli has quit IRC12:16
*** baoli has joined #openstack-meeting-412:16
*** baoli_ has joined #openstack-meeting-412:17
*** baoli has quit IRC12:21
*** karthiks has joined #openstack-meeting-412:22
*** markvoelker has joined #openstack-meeting-412:22
*** GB21 has joined #openstack-meeting-412:23
*** alexchadin has quit IRC12:27
*** alexchadin has joined #openstack-meeting-412:28
*** GB21 has quit IRC12:29
*** kylek3h has quit IRC12:36
*** david-lyle has joined #openstack-meeting-412:38
*** bobh has quit IRC12:40
*** caowei has joined #openstack-meeting-412:40
*** GB21 has joined #openstack-meeting-412:41
*** david-lyle has quit IRC12:43
*** tonytan4ever has joined #openstack-meeting-412:48
*** tonytan4ever has quit IRC12:53
*** jingting has quit IRC12:56
*** jingting has joined #openstack-meeting-412:57
*** uck has joined #openstack-meeting-413:00
*** vishwanathj has joined #openstack-meeting-413:04
*** alexchadin has quit IRC13:04
*** alexchadin has joined #openstack-meeting-413:05
*** kylek3h has joined #openstack-meeting-413:05
*** woodard has joined #openstack-meeting-413:07
*** woodard has quit IRC13:07
*** prateek_ has quit IRC13:08
*** woodard has joined #openstack-meeting-413:08
*** limao has joined #openstack-meeting-413:14
*** bobh has joined #openstack-meeting-413:14
*** thorst_ has joined #openstack-meeting-413:17
*** limao_ has joined #openstack-meeting-413:18
*** pablochacin has joined #openstack-meeting-413:18
*** bnemec has joined #openstack-meeting-413:19
*** jichen has quit IRC13:20
*** limao has quit IRC13:21
*** bobh has quit IRC13:22
*** zhurong has joined #openstack-meeting-413:23
*** thorst_ has quit IRC13:24
*** bobh has joined #openstack-meeting-413:28
*** GB21 has quit IRC13:28
*** limao_ has quit IRC13:33
*** limao has joined #openstack-meeting-413:33
*** tonytan4ever has joined #openstack-meeting-413:37
*** hongbin has joined #openstack-meeting-413:38
*** limao has quit IRC13:39
*** limao has joined #openstack-meeting-413:40
*** anilvenkata has quit IRC13:41
*** salv-orlando has joined #openstack-meeting-413:42
*** iurygregory has joined #openstack-meeting-413:45
*** salv-orl_ has quit IRC13:45
*** automagically has left #openstack-meeting-413:46
*** vikasc has joined #openstack-meeting-413:47
*** qwebirc72142 has joined #openstack-meeting-413:52
*** yedongcan has joined #openstack-meeting-413:53
*** ivc_ has joined #openstack-meeting-413:55
*** liuyulong_ has joined #openstack-meeting-413:56
*** tonanhngo has joined #openstack-meeting-413:56
*** liuyulong has quit IRC13:59
*** dshakhray has quit IRC14:00
*** limao_ has joined #openstack-meeting-414:01
apuimedo#startmeeting kuryr14:01
openstackMeeting started Mon Sep 19 14:01:30 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: kuryr)"14:01
openstackThe meeting name has been set to 'kuryr'14:01
*** lmdaly has joined #openstack-meeting-414:01
apuimedoHello! Who's here for the kuryr meeting?14:01
vikasco/14:01
limao_o/14:01
tonanhngoo/14:01
*** rbak has joined #openstack-meeting-414:01
lmdalyo/14:01
ivc_o/14:02
*** vhoward has joined #openstack-meeting-414:02
apuimedo#info vikasc, limao_, tonanhngo, lmdaly, ivc_ and apuimedo present14:03
apuimedoThank you for joining14:03
apuimedo#topic kuryr-lib14:03
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:03
*** woodster_ has joined #openstack-meeting-414:03
apuimedohttps://wiki.openstack.org/wiki/Meetings/Kuryr#Meeting_September_19th.2C_201614:03
*** uck has quit IRC14:03
apuimedo#topic kuryr-lib: REST/rpc14:04
*** openstack changes topic to "kuryr-lib: REST/rpc (Meeting topic: kuryr)"14:04
apuimedo#info vikasc has some patches for it already14:04
irenabapuimedo: will partially attend14:04
*** limao has quit IRC14:04
apuimedolmdaly: I would like to understand if the approach vikasc is pushing works for the PoC you have14:05
vikascapuimedo, https://review.openstack.org/#/c/342624/14:05
vikascapuimedo, this is the first patch toi be reviewd14:05
vikasc*to14:05
janonymouso/14:05
apuimedowelcome janonymous14:06
apuimedo#link https://review.openstack.org/#/c/342624/14:06
pablochacino/14:06
apuimedowelcome pablochacin14:06
apuimedovikasc: lmdaly: we have to make it in a way that is configurable with both approaches, address/pairs and trunk/subport14:07
apuimedovikasc: did you introduce such a config option already?14:07
vikascapuimedo, not yet14:07
vikascapuimedo, i have introduced, a configuration option to tell if baremetal or nested-containers14:08
apuimedoI'm aware14:08
apuimedoI think we can merge that one14:08
*** ddieterly has joined #openstack-meeting-414:09
vikascapuimedo, it is like one more variable applicable with nested-containers14:09
apuimedo#action apuimedo to review and possibly merge https://review.openstack.org/36202314:09
*** spzala has joined #openstack-meeting-414:09
apuimedo#action vikasc to add a second config patch for selecting the container-in-vm approach14:09
apuimedothe same setting should be used for both the host side and the VM side14:10
vikascapuimedo, so to answer your question.. not added yet this new configuration option in nested-containers case.14:10
apuimedovery well14:11
vikascapuimedo, by host side you mean on master node?14:11
apuimedowe'll get to that14:11
apuimedovikasc: right14:11
vikascapuimedo, yeah..right14:11
hongbino/14:11
apuimedovikasc: possibly we can run more than one master node and have them HAed with corosync-pacemaker14:11
apuimedowelcome hongbin14:12
vikascapuimedo, in my current understanding rpc patches will work for ip/macvlan approch as well14:12
*** banix has joined #openstack-meeting-414:12
apuimedogood14:12
apuimedo#action apuimedo irenab to review all the rpc patches14:12
apuimedo#topic kuryr-lib: specs/devref14:12
*** openstack changes topic to "kuryr-lib: specs/devref (Meeting topic: kuryr)"14:12
vikascapuimedo, i need to rebase rpc patches.. i was updating rest patches only by now14:13
vikascapuimedo, will do14:13
*** thorst_ has joined #openstack-meeting-414:13
*** spotz_zzz is now known as spotz14:13
vikascapuimedo, we should review first kuryr-lib repo patches14:13
apuimedo#info after going through the mailing list for a week, I think the option that generates the larger consensus is to keep the specs on openstack/kuryr and to put devrefs close to the code, i.e. in the repo where the implementation will go14:13
apuimedovikasc: absolutely14:13
*** irenab has quit IRC14:14
vikascapuimedo, i will understand from you HA scenario offline14:14
apuimedovikasc: sure, we can discuss it later14:15
apuimedo#topic kuryr-libnetwork: credential selection14:15
*** openstack changes topic to "kuryr-libnetwork: credential selection (Meeting topic: kuryr)"14:15
*** spotz is now known as spotz_zzz14:15
apuimedo#info: Keystone v3 support was merged, but Kuryr will still prefer cloud.yaml auth options over kuryr.conf, as it was doing up until now14:15
apuimedobanix brought my attention to it14:16
apuimedoand we should try reverting that preference in a way that doesn't break fullstack/rally tests.14:16
banixapuimedo: how is this done? i mean where is this being done?14:16
apuimedobanix: let me link it14:17
apuimedo#link https://github.com/openstack/kuryr-libnetwork/blob/master/kuryr_libnetwork/controllers.py#L74-L7614:18
*** vishnoianil has quit IRC14:18
*** devvesa has joined #openstack-meeting-414:18
apuimedofirst it goes to the cloud yaml in line 7414:18
apuimedootherwise it goes to getting it from kuryr.conf in L7614:18
*** galstrom_zzz is now known as galstrom14:18
apuimedoit's possible that just swapping those lines fixes it14:18
banixisee; now i remember; was done for the gate job at the time i think14:19
*** spotz_zzz is now known as spotz14:19
banixwill try after the call and let you know; may be can fix it before the release?14:20
*** wznoinsk has quit IRC14:20
apuimedovery well14:20
apuimedobanix: that would be ideal14:20
banixsure14:21
apuimedo#action banix to test swapping the lines14:21
apuimedo#info there is a new trello board to track work on Kuryr https://trello.com/b/1Ij919E814:21
*** raj_singh has joined #openstack-meeting-414:21
*** raj_singh has left #openstack-meeting-414:21
apuimedo#info committers to kuryr can ping me for being added as members to the trello team14:21
apuimedo#topic: kuryr-libnetwork: release14:22
*** openstack changes topic to ": kuryr-libnetwork: release (Meeting topic: kuryr)"14:22
apuimedo#info apuimedo sent a patch to get the kuryr-lib requirement in requirements.txt but it was rejected due to global requirements freeze14:22
apuimedo#action apuimedo to request an exception. Which should be granted since nobody else depends on it.14:23
apuimedo#topic: kuryr-libnetwork: container-in-vm14:24
*** openstack changes topic to ": kuryr-libnetwork: container-in-vm (Meeting topic: kuryr)"14:24
*** spotz is now known as spotz_zzz14:24
apuimedowell, we covered most of it in the kuryr-lib topic14:24
apuimedovikasc: anything to add that is kuryr-libnetwork specific?14:24
vikascapuimedo, i think thats pretty much all14:25
apuimedovery well14:25
apuimedo#topic kuryr-libnetwork:general14:25
*** openstack changes topic to "kuryr-libnetwork:general (Meeting topic: kuryr)"14:25
apuimedo#info dongcanye got a patch merged for adding endpoint operation info14:25
apuimedobanix: have you tried kuryr with the new swarm?14:26
banixwon’t work14:26
apuimedo:/14:26
banixnew swarm is tied to Docker Overlay driver14:26
banixthey say this will be fixed in 1.1314:26
apuimedobanix: it can't use any remote/ipam drivers?14:26
banixno14:26
banixas in 1.1214:27
vikasc:D14:27
apuimedogood Lord14:27
apuimedothat is disappointing14:27
apuimedobanix: do you know when 1.13 is coming?14:27
*** diga has joined #openstack-meeting-414:27
banixif you use the new swarm; not sure if you can disable it14:27
*** wznoinsk has joined #openstack-meeting-414:27
apuimedo#info Docker 1.12 swarm mode is not compatible with Kuryr, expected to be fixed on 1.1314:27
banixnot sure; in a couple of months? :)14:28
vikascapuimedo, would it make sense to add this under "limitations"?14:28
apuimedo(屮゚Д゚)屮14:28
banixi think so14:28
apuimedoyes, please14:28
apuimedolet's do that14:28
banixsure14:28
apuimedo#action banix to update *limitations* with the swarm issue14:29
vikascapuimedo, i can do this14:29
apuimedooops14:29
vikascnp14:29
apuimedobanix: vikasc: whoever feels like doing it. I put banix since he can maybe add the backstory links14:29
vikascsure14:29
*** piet has joined #openstack-meeting-414:29
apuimedoFinally, I want to draw attention to the multitenancy story for kuryr-libnetwork14:30
apuimedobanix: do I remember it properly that we do not receive any env var on enpoint joining request?14:30
apuimedobut we can on the other hand receive network operation options14:31
apuimedoon network commands14:31
banixyes14:31
*** spotz_zzz is now known as spotz14:31
banixbut the options are limited to network create only if my info is not outdated14:31
apuimedothat's what I remember as well14:32
banixwhich may be good enough14:32
banixwe had done some work around multi tenancy; let me revisit and get back to you all14:32
apuimedobanix: what I was thinking was, that when users create the networks, they provide keystone auth info14:32
apuimedoand then, when joining a network, we do not check, but match on Docker's network uuid14:33
apuimedowe find the network that has the docker network uuid tag14:33
apuimedoand create the port there, and bind14:33
*** thorst_ has quit IRC14:33
banixyes thats an option14:34
apuimedobanix: please, check that workaround and let us now on #openstack-kuryr ;-)14:34
apuimedomoving on14:34
apuimedo#topic kubernetes: devstack14:34
*** openstack changes topic to "kubernetes: devstack (Meeting topic: kuryr)"14:34
*** thorst_ has joined #openstack-meeting-414:34
*** marst has quit IRC14:34
apuimedo#info apuimedo started WIP patch for kubernetes devstack14:34
apuimedo#link https://review.openstack.org/37143214:35
apuimedoit consists on running etcd3, kubernetes-api, kubernetes-controller-manager and kubernetes-scheduler all in docker containers14:35
apuimedoraven, kubelet and CNI on the bare metal14:35
*** syed_ has joined #openstack-meeting-414:35
apuimedoI still have some issues with run_process and docker run, but I think I'll be able to solve it soon enough14:36
apuimedoafter that, we can start having gates when we add new kubernetes integration code14:36
vikascapuimedo, thanks for the great effort!!!14:36
apuimedoyou're welcome14:36
*** irenab has joined #openstack-meeting-414:36
devvesa+114:36
apuimedoany question on the kubernetes devstack?14:36
apuimedodevvesa: nice to see you14:37
devvesathanks. I've been late today14:37
apuimedono problem14:37
apuimedoyou made it in time for your section14:37
devvesaSo the -1 Workflow on the devstack patch means that it fails?14:37
apuimedoyes14:37
*** irenab has quit IRC14:37
vikascwhy raven in bm?14:37
apuimedoit's for me to tell people that I need to fix stuff14:37
pablochacinapuimedo: the usual concern about the future of hyperkube14:38
devvesaI prefer a WIP on message commit14:38
apuimedovikasc: so that you can edit code while developing and you don't need to regenerate a container for it14:38
devvesabecause I understood that it was not meant to be merged14:38
*** irenab has joined #openstack-meeting-414:38
vikascapuimedo, cool14:38
apuimedopablochacin: hyperkube doesn't seem to be going away, if it does, though14:38
apuimedowe'll use an all in one binary14:38
devvesalast time i download the last version released on the hyperkube container (1.3.7)14:38
apuimedoI'll set up a job somewhere that compiles it14:38
apuimedoand downloads it14:39
devvesaso they kind of maintain it14:39
hongbinapuimedo: i think you want to make the version of hyperkube configurable14:39
apuimedodevvesa: both gcr.io and quay.io are maintaining their own versions of it14:39
apuimedohongbin: I made it configurable ;-)14:39
apuimedohttps://review.openstack.org/#/c/371432/3/devstack/settings14:39
apuimedothe devstack design is14:39
hongbinapuimedo: looks good14:40
apuimedoyou can enable disable each service and point your local.conf to existing services if you have them14:40
*** david-lyle has joined #openstack-meeting-414:40
apuimedoand you can also specify etcd/hyperkube versions and origin14:40
apuimedo(in case somebody prefers quay's more than gcr14:40
apuimedofor example14:40
irenabapuimedo: it requires a bit of documentation, since too many options can be confusing14:40
apuimedoirenab: good point14:41
*** jovon has joined #openstack-meeting-414:41
apuimedo#action apuimedo to make a local.conf.sample with a lot of comments that explain the options14:41
irenabapuimedo: or blog :-)14:41
vikascapuimedo, +114:41
apuimedoirenab: if you can, review the patch reminding me to add that to local.conf.sample14:41
pablochacinapuimedo: do you know what magnun project is doing? they also need kubernetes, right?14:41
irenabapuimedo: sure14:41
apuimedopablochacin: you have here the best person to answer that14:42
apuimedohongbin: ^^14:42
pablochacin:-/14:42
*** mfedosin has quit IRC14:42
vikasc:)14:42
hongbinmagnum does something similiar (pull docker image for kube components)14:42
*** thorst_ has quit IRC14:42
hongbinkubelet is provided by the os14:43
apuimedoIdeally, we should have a container registry in infra14:43
apuimedothat can be used for jobs, kolla, official OpenStack containers, etc14:43
apuimedobut I think that's not ready yet14:43
*** thorst_ has joined #openstack-meeting-414:43
apuimedo#topic py3 asyncio progress14:43
*** openstack changes topic to "py3 asyncio progress (Meeting topic: kuryr)"14:43
apuimedodevvesa: pablochacin: any news on that front?14:44
devvesaapuimedo: the expected ones this week: 014:44
banixby the way, i think we will have kuryr in kole by the next release14:44
devvesasorry but we have been busy in other stuff14:44
irenabbanix: Kolla?14:45
apuimedodevvesa: very well. That's perfectly understandable14:45
apuimedoyes14:45
banixyes14:45
apuimedoI'll put an #info in open discussion about it :-)14:45
*** david-lyle has quit IRC14:45
apuimedoI should have done it in the kuryr-libnetwork topic14:45
apuimedoI'm in the moon14:45
banixsorry for digression14:45
apuimedo#topic kubernetes: py2/3 eventlet14:45
*** openstack changes topic to "kubernetes: py2/3 eventlet (Meeting topic: kuryr)"14:45
devvesaapuimedo: sorry if you already said it, but... any news on the CNI plugin?14:46
devvesas/plugin/driver14:46
*** marst has joined #openstack-meeting-414:46
apuimedodevvesa: nope, finishing devstack first, so I can have it gated14:46
apuimedo#info ivc_ pushed a devref that designs a very different approach than the one apuimedo's devref was pushing for14:46
devvesaperfectly understandable :)14:46
apuimedoWe had a videochat discussion (video available on demand)14:47
banixlink please14:47
apuimedo#action devvesa vikasc pablochacin irenab to review https://review.openstack.org/#/c/369105/14:48
apuimedoalso, ivc_ started implementing one of it's first pieces, the port provider14:48
ivc_just a note, https://review.openstack.org/#/c/369105/ is wip and i'm hoping to update it soon with more recent information14:48
apuimedo#link https://review.openstack.org/#/c/370284/14:49
apuimedothanks ivc_14:49
apuimedoivc_: any other news?14:49
ivc_yup cleaning up other parts14:49
ivc_and sort of refactoring the service/endpoints dependencies issue14:50
apuimedoivc_: can't wait to see about that in the devref14:50
apuimedo:-)14:50
ivc_actually there's no more dependency issue :)14:50
ivc_so i'm removing all the junk code related to it now14:50
ivc_got it sorted out by applying lbaas pool annotation to endpoints instead of service14:51
apuimedoivc_: now I'm even looking forward to seeing it more14:51
*** tri2sing has joined #openstack-meeting-414:51
apuimedointeresting14:51
irenabivc_: using lbaasV2?14:52
ivc_irenab yes14:52
apuimedoso until you see endpoint event with annotation, you send it to /dev/null14:52
irenabgreat14:52
apuimedonice idea14:52
ivc_apuimedo yup14:52
apuimedoivc_: but it pisses me off. Why didn't I think about doing it like that....14:53
apuimedoanyway, let's move on14:53
ivc_apuimedo ")14:53
apuimedo#topic open discussion14:53
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:53
banixhere are related patches regarding Kuryr integration in Kolla: https://review.openstack.org/#/c/298894/  https://review.openstack.org/#/c/364662/  https://review.openstack.org/#/c/370382/14:54
*** uck has joined #openstack-meeting-414:54
apuimedo#info huikang scored a big buzzer beater for Kuryr getting it inside Kolla's newton release just as the clock was expiring. I can't thank enough all the efforts from huikang, sdake, inc0 and Jeffrey14:54
banix+114:55
apuimedoit will be very nice for kuryr-libnetwork development to be able to use kolla instead of devstack :-)14:55
vikascmacvlan v/s ipvlan14:55
apuimedo#info In order to be on more consumer ready kolla usage, we should have RPM/deb packages and add kolla code to consume those as well14:56
apuimedoright14:56
apuimedolimao_: vikasc: lmdaly please, explain about the macvlan/ipvlan. I gotta run14:56
apuimedo#chair banix14:56
openstackCurrent chairs: apuimedo banix14:56
apuimedobanix: please finish the meeting14:56
banixk14:57
irenab3 mins left14:57
apuimedo#info limao made a very nice document manually testing the ipvlan proposal with macvlan https://lipingmao.github.io/2016/09/18/kuryr_macvlan_ipvlan_datapath_poc.html14:57
apuimedo(even using ipam)14:57
vikascOnly pro in using ipvlan seems to be the limit on number of virtual interfaces before interface enters promiscous mode14:58
limao_ipvlan need more high kernel version14:58
limao_http://hicu.be/macvlan-vs-ipvlan14:58
limao_a blog about pro and con14:59
hongbinyes, i would say the requirement of high kernel version will cause problem14:59
irenablimao_: thanks for sharing14:59
limao_maybe we can consider support both ipvlan and macvlan14:59
vikascIMO, promiscous mode should not be as major concern as latest kernel requirement14:59
*** uck has quit IRC14:59
banix#info a blog about pro and con : http://hicu.be/macvlan-vs-ipvlan14:59
lmdalyI see no issue with the possibility of introducing a macvlan option15:00
banixrunning out of time; should perhaps end now and continue on kuryr channel if need be15:00
banix#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Sep 19 15:00:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-09-19-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-09-19-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-09-19-14.01.log.html15:00
vikasclimao_, +1 for supporting both15:00
irenab+115:00
jimbaker#startmeeting craton15:00
openstackMeeting started Mon Sep 19 15:00:52 2016 UTC and is due to finish in 60 minutes.  The chair is jimbaker. 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
*** irenab has quit IRC15:01
jimbaker#topic rollcall15:01
*** openstack changes topic to "rollcall (Meeting topic: craton)"15:01
syed_o/15:01
jimbakerhi everyone, and welcome to this week's meeting on craton15:01
syed_Hi jim15:01
syed_i hope you are doing well15:01
jimbakersyed_, thanks, yes, i had a very good hike yesterday15:02
jimbakerso that always is a great way to prepare a solid foundation for the week15:02
syed_Good, i am glad15:02
jimbakerwhich is as we know, is actually related to what craton means (in this case, a solid foundation/platform for continents), and should do for the cloud15:03
*** pablochacin has left #openstack-meeting-415:03
jimbakersyed_, hopefully you had a nice weekend as well, and ready for some good progress on functional testing/container automation15:03
sulohola, o/15:04
syed_yeap i went to visit family, and ready for some things to be up15:04
jimbakersulo, hi15:04
syed_hey sulo15:04
jimbakersyed_, good to hear!15:04
*** bnemec has quit IRC15:04
*** yedongcan has left #openstack-meeting-415:05
jimbakerlooks like the core devs for craton are here, so let's proceed15:05
jimbaker#topic new meeting schedule15:06
*** openstack changes topic to "new meeting schedule (Meeting topic: craton)"15:06
jimbakersigmavirus, what is a good time for you on tuesday? i saw your note about a conflict15:06
*** bnemec has joined #openstack-meeting-415:07
jimbakerideally sulo can attend the client meeting, but we need a time that you can attend15:07
*** janki has quit IRC15:07
*** pbandark has joined #openstack-meeting-415:07
sigmavirusirc meetings are better for me honestly15:07
sigmavirusI can join that and a video call more easily than two video alls15:07
*** pcaruana has quit IRC15:07
jimbakersigmavirus, understood, but i think the rest of the team benefits from a video call, that's why we started doing them as well15:08
jimbakerwe can readily do demos, etc15:09
jimbakerand there's a training component as well15:09
sulofeel free to do meetings without me if thats what is needed15:09
*** qwebirc72142 has quit IRC15:09
jimbakersigmavirus, would 1600 UTC work for you? otherwise we can push into US afternoon15:09
* sulo is more than happy to not attend meetings15:10
jimbakersulo, agreed - i think i can represent you just fine on the client side15:10
sigmavirusjimbaker: can we schedule it outside of this?15:10
jimbakersigmavirus, sounds good - but we need to get this resolved today15:11
*** bobh has quit IRC15:11
sigmavirusjimbaker: 1600 utc looks fine on my calendar15:11
*** caowei has quit IRC15:11
jimbakersigmavirus, thanks!15:12
jimbakerlcastell, i assume 1600 UTC also works for you. same with jovon and syed_15:12
jimbakermoving on15:12
jovonworks fine15:13
syed_+115:13
jimbaker#topic outstanding changes15:13
*** openstack changes topic to "outstanding changes (Meeting topic: craton)"15:13
jimbaker#topic outstanding change reviews15:13
*** openstack changes topic to "outstanding change reviews (Meeting topic: craton)"15:13
jimbakersulo, i know you have a number of reviews i need to do for you. the only one that i have pushed back is query by variables, pending some refactoring work i'm doing on the api15:14
jimbakerothers here: are you being blocked by reviews, and if so, any prioritization we should be aware of as we start off this week?15:15
syed_I am good for now. Thanks15:15
jimbakersyed_, sounds good. feel free to ping me about docker-py as it comes up15:16
syed_yes i need some clarifications on few things for it15:16
syed_i will once the meeting is over15:16
syed_thanks15:16
jimbakersyed_, cool15:16
suloeveryone start doing reivews ... this is one of the most important thing that is getting ignored15:16
jovonI currently am blocked by turvey's API change. i15:17
jimbakersulo, i don't think we are ignoring them. but we certainly need to keep them prioritized15:17
suloeven if you cant merge, everyone can certainly do +1's15:17
sulo-1 etc15:17
jimbakersulo, agreed on that15:17
jovonagreed sulo15:17
*** psachin_ has quit IRC15:18
*** pbourke has quit IRC15:18
jimbakereven minor nits are important to point out. sometimes what looks minor is also important15:18
jimbakerso many eyeballs here15:18
*** pbourke has joined #openstack-meeting-415:18
*** dshakhray has joined #openstack-meeting-415:18
jimbakerjovon, details on turvey's API change?15:18
suloif we think we dont have enough reviewers, perhaps we need to send a community email to get some more ppl aware that they can help with this15:18
jimbakersulo, +115:19
jimbaker#action jimbaker what can you do for craton? email the community15:19
suloi have some screencast that i need to share .. so i might add a help note when i send out the vidyo15:19
jovonhe has submitted an update to the doc. I need his patch to be merged before i can complete mine as it pertains to the same set15:19
suloor video even15:20
jimbakersulo, right, thanks for putting those together15:20
jimbakerjovon, got it, we will get turvey's review through15:20
sulojimbaker: you talking about the one i did for JC ?15:20
jimbakersulo, just in general, but yes15:21
jovonthank you15:21
suloright, yeah i dont like that one .. the one i intend to send will be better15:21
jimbakersulo, practice makes perfect15:21
sulodidnt have enough time on that15:21
jimbakerso the net of this is: all of us need to do reviews. these can be great to do when stuck on something else15:24
*** alexchadin has quit IRC15:24
jimbakeralso this is a chance to learn what the codebase does15:24
jimbakerby trying out functionality15:24
jovon+115:24
*** alexchadin has joined #openstack-meeting-415:24
jimbakernew REST API in a change from sulo? give it a try from curl15:24
syed_sounds good !15:25
jimbakerbtw, i assume everyone knows how to pull in a change from gerrit so they can actually try stuff out locally15:25
jimbakerbut if not: look at the downloads link15:26
jimbaker:)15:26
jovonroger that ty!15:27
jimbakertime to wrap up this topic, feel free to ask more on #craton - and please demand your reviews get done!15:28
jimbaker#topic dev issues15:28
*** openstack changes topic to "dev issues (Meeting topic: craton)"15:28
jimbakersulo, do you want to start with the label discussion?15:28
jimbakeri assume this is with respect to OSA modeling15:28
suloso, labels - how do we want to use it ?15:29
jimbakersulo, my assumption has been is that labels are used for logical groupings15:29
jimbakerthey are not part of the network topology (which we just added with networks, netdevices, and interfaces). they are not part of a physical containment (the device tree)15:30
jimbakerso we can labels like "service:compute"15:30
*** thorst_ has quit IRC15:31
suloso whats the benifit of doing this in a separate table vs just puttig lables in device model15:31
jimbakerobviously we can do the same with variables on a given device - that's why i was describing labels as duals to variables15:31
jimbakersulo, well i think they are in fact already are15:31
sulo?15:31
*** thorst_ has joined #openstack-meeting-415:31
jimbakerlabels have a many-to-many relationship to devices15:32
*** david-lyle has joined #openstack-meeting-415:32
jimbakerso they already are there in the device model. at least in the relational sense15:32
*** alexchadin has quit IRC15:32
jimbakerin craton's inventory model, devices are the central concept15:33
jimbaker(we can all agree on that)15:33
suloright, what i am saying is whats the benifit of having this relationship vs just tracking it per device on the devices model15:33
suloit only makes sense to do this if we were doing more with it15:34
jimbakersulo, they are pretty light weight right now15:34
suloi am trying to understand (i forget the discussion) what we were trying to drive with labels15:34
jimbakeri think the only complexity is that we let them have variables15:34
sulothat too15:34
jimbakerif we eliminate that, they become very simple15:35
jimbakersulo, so the idea is that we want to be able to look up various logical groupings efficiently, by using relational queries15:35
jimbakermuch as we do with cell or region15:35
suloso does that need k:v labels ?15:36
jimbakerso i can label a device by how it's grouped with power; or what its function is (it's for storage, or for compute, or whatever)15:36
jimbakersulo, i think that's just a useful convention that we can support15:36
jimbakerand let's map to say http://kubernetes.io/docs/user-guide/labels/15:37
jimbakersulo, note they have a similar design concept: "We don’t want to pollute labels with non-identifying, especially large and/or structured, data. Non-identifying information should be recorded using annotations."15:38
jimbakerwhat  they call annotations is definitely close to what we are describing as variables15:38
suloso what i am syaing is i dont see why we couldnt just do this with variables .. it seems like exact the same thing .. we just need to track it differently .. example: label_x15:39
sulobut maybe its a good idea to do it separately15:39
jimbakersulo, i absolutely agree that it can be done in this way15:40
jimbakerbut perhaps many of the things we might do a variable query would be better done with a label. it would certainly be far more efficient15:40
sulolike what ?15:40
jimbakerjust to get in some details: on mysql we are not even mapping json columns to mysql's json type15:41
jimbakerthis is in part because mariadb doesn't yet have support for mysql's json type15:41
jimbakerand the sqlalchemy_utils package currently doesn't look at specific db impl - for mysql, it just does TEXT15:42
jimbakerbut this will change over time15:42
jimbakerat some point, queries that involve json columns will be able to use json indexing15:42
jimbakerbut we would need to do some work15:43
sulodoesnt that apply to everything that uses JSON type ?15:43
jimbakerwhereas with labels, we get that indexing for free, since it's purely relational15:43
jimbakersulo, right, but we usually are less concerned about this15:44
sulooh, you saying it can only be string:string mapping for labels ?15:44
jimbakersulo, yes15:44
jimbakerthe label name is currently just a string15:44
jimbakeri want to support splitting it into two strings, because the k:v convention is pretty nice as seen in kube15:45
suloyeah, i am thinking about <string>: JSONType15:45
jimbakerbut yeah, the :v part will not grow to be arbitrary JSON. that would be bad15:45
jimbakerthen we would just have a more awkward, non relational thing in labels. i wouldn't even know how to model as we have it now :)15:46
suloso how would we represent multiple group memebership in labels ?15:46
jimbakersulo, labels are many to many with devices15:46
jimbakerso we get that for free15:47
jimbakerthe one thing we don't have is any label hierarchy. but i don't see the need for that15:48
jimbakerthat thinking was mostly inspired by a desire to implement a DAG for network modeling. but instead we came up with a better modeling of that, which is actually quite sweet imho15:48
*** ddieterly is now known as ddieterly[away]15:50
suloso i am not sure i am on the same page as you here ...15:50
jimbakersulo, i suggest we move this discussion over to #craton15:50
*** hshiina has joined #openstack-meeting-415:51
*** jwagner is now known as jwagner_lunch15:51
suloyeah, i think this is a much longer discussion .. lets move to #craton after this meeting15:51
jimbakercool15:51
*** bpokorny has joined #openstack-meeting-415:51
*** bpokorny has quit IRC15:51
jimbakerother dev topics that we should cover?15:52
*** bpokorny has joined #openstack-meeting-415:52
sulowhere are we with worker code ?15:52
jimbakeri will mention that my goals for this week include: refactoring of the flask api; craton-specific backend for taskflow15:53
sulois that something we are clear with in terms of how to model ...15:53
jimbakersulo, so i put that gist up last week15:53
jimbakeri will revisit as a blueprint. today sounds right to me15:54
*** bpokorny has quit IRC15:54
sulook cool ... i think we are coming to the point where some sort of worker impl will be required soon15:54
*** Sukhdev has joined #openstack-meeting-415:54
jimbakersulo, the key piece is going to be scheduling the task graph, which we have decided to break into two pieces15:54
suloto drive some of the osa integration etc15:54
*** bpokorny has joined #openstack-meeting-415:54
*** ddieterly[away] is now known as ddieterly15:55
*** zhurong has quit IRC15:55
jimbakersulo, yeah, so that's really about wrapping the ansible-playbook command and especially using the callback api15:55
jimbakerfor ansible/OSA specifically15:55
jimbakerthe general piece is the two level task graph scheduling15:55
sulook cool. that sounds like you have it under control ;)15:56
jimbakersulo, more that i'm juggling them, but sure :)15:57
*** aimeeu__ has joined #openstack-meeting-415:57
jimbakerjust need to keep everything in the air, not so bad. just remember: if we juggle too much, it all falls to the ground ;)15:57
sulojimbaker: heh, upto 5 pins allowed15:58
jimbakerexacty15:58
jimbakertime to wrap up this meeting15:58
jimbaker#topic questions/goodbyes15:58
*** openstack changes topic to "questions/goodbyes (Meeting topic: craton)"15:58
jimbakerso really this means - take your questions over to  #craton15:59
jimbakerbecause there's no time left15:59
jimbakerthanks everyone!15:59
jovonthanks15:59
*** bpokorny has quit IRC15:59
jimbaker#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Mon Sep 19 15:59:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-09-19-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-09-19-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-09-19-15.00.log.html16:00
*** tri2sing has quit IRC16:00
*** acabot has quit IRC16:00
*** mjturek has joined #openstack-meeting-416:00
Sukhdev#startmeeting ironic_neutron16:00
openstackMeeting started Mon Sep 19 16:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:00
openstackThe meeting name has been set to 'ironic_neutron'16:00
*** nishpatwa_ has joined #openstack-meeting-416:01
Sukhdevwho is here to attend Ironic-neutron meeting?16:01
mjtureko/16:01
*** tonanhngo has quit IRC16:01
*** jichen has joined #openstack-meeting-416:01
Sukhdevmjturek : Hi16:01
*** bpokorny has joined #openstack-meeting-416:02
mjturekhey Sukhdev, happy monday :)16:02
*** uck has joined #openstack-meeting-416:02
SukhdevI am on vacation for two weeks - did not have time to prepare the agenda - so, will use the last week's16: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_September_12.2C_201616:03
sambettso/16:03
hshiinao/16:03
SukhdevI am on the road with limited access to internet - thought I run it quickly16:04
Sukhdev#topic: Announcements16:04
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:04
SukhdevSo, the port groups are pushed to next release16:05
Sukhdevdoes anybody know about the Security Groups?16:05
Sukhdevhttps://review.openstack.org/#/c/361451 - this has not gone anywhere16:05
Sukhdevjroll : so, did we decide to push the SG to next release as well - or is it still up for discussion?16:06
sambettsI think its a similar story, however we did notice that we need to document correcting the default security groups if we don't merge that code16:06
sambettsI think jroll added a node to our install guide about it16:07
*** devvesa has quit IRC16:07
sambettsI think the patch might be still up for review16:07
sambettsSukhdev: https://review.openstack.org/#/c/369385/16:08
Sukhdevsambetts : as long as neutron networks are used, the default SG are in play and those are documented as part of neutron docs16:08
*** matrohon has quit IRC16:08
sambettsSukhdev: right but we need to document what ports etc you have to enable to make Ironic work16:08
Sukhdev#link: https://review.openstack.org/#/c/369385/16:08
Sukhdevsambetts : right16:09
SukhdevI will review the patch later in the day when I have some free moments16:09
hshiinaIronic cores seems to have decided to push the SG in Ocata at last week ironic meeting.16:10
sambettsif we don't have that doc patch and we don't merge the sec group support then I envision many support calls asking why the ramdisk can't talk to ironic16:10
Sukhdevhshiina : thanks for the update16:10
Sukhdevsambetts : actually, it may not be that bad - as long ML2 drivers are doing the right thing16:11
*** bobh has joined #openstack-meeting-416:11
Sukhdevdefault SG allow the DHCP to work - so, that instance get the IP address - even when no SG specified -16:12
sambettsSukhdev: if Ml2 drivers are supporting sec groups then the default sec group will lock the network down won't it? The default rules are very strict16:12
sambettsI though16:12
sambettsthought*16:12
Sukhdevhowever, the tftp of image may be problematic16:12
Sukhdevright - the instance probably will get IP address - but, may not progress any further -16:13
sambettsand things like the ISCSI / http communications, so they are all mentioned in jroll's patch :)16:13
Sukhdevso, the right course of action is the operator updates the default SG and launches the BM -16:13
Sukhdevupdate the default SG - means add ingress rules to the SG16:14
sambettsyeah there are a few different rules to add, including ingress and egress for certain communications16:15
Sukhdevdefault SG rules (I believe) are allow all egress TCP/UDP16:15
SukhdevI will look at jroll's patch and make a comment about this -16:16
sambettsah cool! that makes things a little simpler then16:16
*** bobh has quit IRC16:16
*** thorst_ has quit IRC16:18
SukhdevDo we need to discuss anything else today?16:18
*** thorst_ has joined #openstack-meeting-416:18
sambettsnothing from me16:19
SukhdevIf not, lets wrap it up - I can go back to my breakfast - I am on vacation :-):-)16:19
SukhdevBTW, I am off next week as well16:19
Sukhdevshall we cancel next week's meeting?16:19
SukhdevOr sambetts can you run it?16:20
*** pbandark has quit IRC16:20
sambettsI can run it if we have stuff to talk about16:20
Sukhdevsambetts : I am sure you can think about stuff to discuss :-)16:20
sambetts:)16:20
Sukhdevthanks for volunteering, sambetts16:20
Sukhdevhshiina : anything you would like to discuss?16:21
*** iyamahat has joined #openstack-meeting-416:21
hshiinanothing16:21
Sukhdevcool - thanks16:22
SukhdevOK - we are done then16:22
SukhdevThanks folks16:22
hshiinathanks16:22
Sukhdevsee you in two weeks16:22
Sukhdevbye16:22
sambettsenjoy your vacation!16:22
sambettso/16:22
Sukhdev#endmeeting16:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:22
openstackMeeting ended Mon Sep 19 16:22:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-09-19-16.00.html16:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-09-19-16.00.txt16:22
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-09-19-16.00.log.html16:22
*** Sukhdev has quit IRC16:23
*** thorst_ has quit IRC16:25
*** thorst_ has joined #openstack-meeting-416:26
*** GB21 has joined #openstack-meeting-416:28
*** Sukhdev has joined #openstack-meeting-416:28
*** Sukhdev has quit IRC16:33
*** hshiina has left #openstack-meeting-416:34
*** Sukhdev has joined #openstack-meeting-416:35
*** zenoway has quit IRC16:35
*** Sukhdev has quit IRC16:35
*** zenoway has joined #openstack-meeting-416:35
*** krtaylor has quit IRC16:38
*** Sukhdev has joined #openstack-meeting-416:38
*** Swami has joined #openstack-meeting-416:39
*** zenoway has quit IRC16:40
*** thorst_ has quit IRC16:41
*** degorenko has quit IRC16:42
*** degorenko_away is now known as degorenko16:42
*** Sukhdev has quit IRC16:43
*** revon has joined #openstack-meeting-416:47
*** cholcombe has joined #openstack-meeting-416:47
*** yamamoto has joined #openstack-meeting-416:47
*** thorst_ has joined #openstack-meeting-416:48
*** lmdaly has quit IRC16:49
*** automagically has joined #openstack-meeting-416:49
*** bpokorny has quit IRC16:50
*** bpokorny has joined #openstack-meeting-416:51
*** bobh has joined #openstack-meeting-416:52
*** bpokorny has quit IRC16:55
*** bobh has quit IRC16:55
*** jwagner_lunch is now known as jwagner16:56
*** spzala has quit IRC16:56
*** aunnam has quit IRC16:57
*** spzala has joined #openstack-meeting-416:57
*** bpokorny has joined #openstack-meeting-416:58
*** aunnam has joined #openstack-meeting-416:59
dameso/17:00
*** dames is now known as thedac17:00
*** gnuoy has joined #openstack-meeting-417:00
icey\o17:00
gnuoyo/17:00
*** aunnam has quit IRC17:00
gnuoy#startmeeting charms17:00
openstackMeeting started Mon Sep 19 17:00:44 2016 UTC and is due to finish in 60 minutes.  The chair is gnuoy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
cargonzao/17:00
*** openstack changes topic to " (Meeting topic: charms)"17:00
openstackThe meeting name has been set to 'charms'17:00
tinwoodo/17:01
gnuoyI'm standing in for the PTL until he pops along17:01
gnuoy#topic Review ACTION points from previous meeting17:01
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:01
gnuoy#subtopic tinwood to update charm guide with refactored charms_openstack bits17:01
beisnero/17:01
gnuoytinwood, I was wondering if I could take that action if you haven't done it?17:01
tinwoodsure; I was away so couldn't get to it.17:02
*** spzala has quit IRC17:02
gnuoy#action gnuoy update charm guide with refactored charms_openstack bits17:02
gnuoy#subtopic jamespage to review current newton specs against plan17:02
*** diga has quit IRC17:02
gnuoyLets circle back to that when he arrives17:02
jamespageo/17:02
wolseno/17:02
jamespagesorry I'm late17:03
gnuoyah, here he is17:03
*** ntpttr is now known as ntpttr_17:03
gnuoyjamespage, : jamespage to review current newton specs against plan17:03
gnuoyreviewing action from previous meeting ^17:03
*** ntpttr_ is now known as ntpttr17:03
jamespageyeah carry that forward pls17:03
gnuoy#chair jamespage17:03
openstackCurrent chairs: gnuoy jamespage17:03
*** GB21 has quit IRC17:03
jamespageta17:04
gnuoy#action jamespage  review current newton specs against plan17:04
jamespagewas that it for previous actions?17:04
gnuoyjamespage, yep17:04
*** ntpttr is now known as ntpttr_away17:04
*** ntpttr_away is now known as ntpttr17:04
jamespage#topic State of Development for next Charm Release17:05
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:05
*** thorst_ has quit IRC17:05
*** ntpttr is now known as ntpttr_wfh17:05
*** ddieterly is now known as ddieterly[away]17:05
gnuoyThe Freeze it is a comin17:05
*** ntpttr_wfh is now known as ntpttr17:05
jamespageok so headlines - feature freeze is week on thursday - 29th september;  bugfixes only past that date17:05
iceyWinter is coming17:05
jamespageso features need to be reviewed and landed by the end of 29th17:06
jamespageanything past that - apply for a feature freeze on the openstack-dev ML17:06
jamespage[charms] feature freeze exception: <name>17:06
beisneror work on tests, we can still land tests :-)17:06
jamespagethats true17:06
jamespageI have one more cross charm feature to land:17:07
jamespage#link https://review.openstack.org/#/c/37254817:07
tinwoodtechnically, it's not a feature unless it has tests :)17:07
gnuoyah yes17:07
jamespagethat's the proof - sets the application version for a deployed charm17:07
*** uck has quit IRC17:08
beisnerI sent a mail to the list a while back about removing tests/charmhelpers and pulling that into the test's venv instead.  Anyone have a chance to think about that or look at it?  the one poc is merge-conflict atm, but principle remains workable.17:08
jamespagealso don't forget its 16.10 bug squash day on thursday17:08
beisnerit removes 2K lines of cargo-code17:08
beisnerper repo17:08
*** uck has joined #openstack-meeting-417:08
jamespagebeisner, hmm - I'll have to dig that out but in principle +117:08
*** yamamoto has quit IRC17:08
jamespagecharms on a diet - nice17:08
beisnerit'd be one more stable/master bit to flip every time we release, but, sed.17:09
jamespagebeisner, if you have cycles to refresh, I'll review17:09
jamespageok next up17:10
beisnerok i'll rebase and update, will circulate the poc when ready.  thx17:10
jamespage#topic High Priority Bugs17:10
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:10
jamespageanything nasty biting us atm? I'm aware of a few ks v3 compat issues17:10
gnuoyswift-proxy and ceilometer are having keystone v3 headaches17:10
gnuoyjamespage, fwiw we skipped a small agenda item17:11
gnuoy"Rotate the chair"17:11
*** thorst_ has joined #openstack-meeting-417:11
jamespageoh sorry17:11
gnuoynp17:11
jamespagedid I do the last one as well?17:11
jamespageok we should rotate things17:11
* beisner spins around17:11
gnuoyShall we stick names in https://etherpad.openstack.org/p/openstack-charms-weekly-meeting and just pop off the list17:11
*** yamamoto has joined #openstack-meeting-417:11
jamespagegnuoy, +117:12
gnuoykk17:12
tinwood+117:12
jamespagegnuoy, can you populate the list and pop me off the top please?17:12
gnuoywill do17:12
jamespage#action gnuoy to make list of chairs and schedule17:12
*** automagically has left #openstack-meeting-417:12
*** uck has quit IRC17:13
jamespageI'm also aware of two bugs in the storage charms - cholcombe and icey will be looking into those17:13
jamespagespecifically pruning osd and swift storage devices from updatedb17:13
cholcombejamespage, right17:13
jamespageand tweak the scheduler for osd devices17:13
cholcombeshould be pretty small changes17:13
jamespagecholcombe, great!17:14
jamespageyeah - quick wins to largish problems IMHO17:14
sdakei see i was paged anything relating to this meeting?17:14
jamespagecholcombe, lets make sure we cover the charm upgrade use-case17:14
jamespagesdake, I don't think so17:14
sdakejamespage roger thanks17:14
cholcombejamespage, sounds good17:14
jamespage#topic OpenStack Events17:14
*** openstack changes topic to "OpenStack Events (Meeting topic: charms)"17:15
jamespagewell one largish one on the horizon17:15
jamespagehttps://etherpad.openstack.org/p/ocata-charm-summit-planning17:15
*** unicell has quit IRC17:15
jamespageI've added some items for our fishbowl sessions; we also have two workroom sessions scheduler17:15
jamespagemy feel is we could give one fishbowl back atm unless we can think of other things that need discussing?17:15
jamespagethoughts?17:16
*** thorst_ has quit IRC17:16
tinwoodHow long is a fishbowl?  25 mins?17:16
tinwood35?17:16
jamespage40 minutes17:17
gnuoyjamespage, in my experience they can very easily get bogged down so its v. hard to tell17:17
jamespagewe're at about 55 mins timeboxed atm17:17
jamespageok lets stick with two slots then17:17
jamespagethey are back to back on the wednesday afternoon atm17:17
tinwoodyes, I was thinking that a couple of those topics could spiral.17:18
jamespagemoving on17:18
jamespage#topic Open Discussion17:19
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:19
*** yamamoto has quit IRC17:19
jamespagebad luck - you're stuck with me as PTL for the ocata cycle ;)17:19
*** yamamoto has joined #openstack-meeting-417:19
tinwood:)17:19
gnuoy\o/17:19
wolsen:)17:19
*** yamamoto has quit IRC17:19
beisnercongrats, jamespage :)17:19
thedacwhew!17:19
iceygrats!17:19
jamespagewell it was by default - seat was uncontested17:20
gnuoyI've added the people here on to the list of chairs for this meeting in the etherpad. Please take yourself off if you so desire17:20
jamespagelooks like gnuoy is up in two weeks time17:20
*** Rockyg has joined #openstack-meeting-417:21
gnuoyyep17:21
jamespagespeaking of which -do you think we should get that second slot on the other week?17:21
jamespageI'd be up for that - we could do weekly imho?17:21
gnuoyan APAC friendly slot?17:21
jamespageyeah - that was my thinking17:22
*** degorenko is now known as _degorenko|afk17:22
jamespageit might be quiet to start with, but we have a few users and contributors in asia now17:22
gnuoysure, we can give it a go17:22
wolsenI think there are definitely a few folks in the AP timeslot who would like that17:22
jamespage#action jamespage to identity alternate week slot and get scheduled17:22
jamespagewolsen, awesome17:23
jamespageok anything else?17:23
wolsenjamespage: when you pick a timeslot, I'll broadcast to the crew I know of17:23
jamespagewolsen, excellent17:23
jamespageok so17:23
jamespage#endmeeting17:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:23
openstackMeeting ended Mon Sep 19 17:23:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-09-19-17.00.html17:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-09-19-17.00.txt17:23
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-09-19-17.00.log.html17:23
jamespage+2 weeks folks17:23
thedacthanks, jamespage17:24
gnuoythanks jamespage17:24
tinwoodthanks both17:24
*** marst has quit IRC17:26
*** yamamoto has joined #openstack-meeting-417:27
*** tri2sing has joined #openstack-meeting-417:27
*** marst has joined #openstack-meeting-417:28
*** harlowja has joined #openstack-meeting-417:30
*** rbak has quit IRC17:30
*** armax has joined #openstack-meeting-417:31
*** rbak has joined #openstack-meeting-417:32
*** mbirru has joined #openstack-meeting-417:37
*** GB21 has joined #openstack-meeting-417:37
*** unicell has joined #openstack-meeting-417:42
*** dshakhray has quit IRC17:44
*** sarob has joined #openstack-meeting-417:47
*** sarob has quit IRC17:47
*** sarob has joined #openstack-meeting-417:48
*** s3wong has joined #openstack-meeting-417:50
*** armax has quit IRC17:53
*** _sarob has joined #openstack-meeting-417:54
*** bobh has joined #openstack-meeting-417:56
*** sarob has quit IRC17:56
*** armax has joined #openstack-meeting-417:57
*** ddieterly[away] is now known as ddieterly17:57
*** uck has joined #openstack-meeting-417:58
*** bobh has quit IRC18:01
*** yamahata has joined #openstack-meeting-418:02
*** GB21 has quit IRC18:07
*** banix has quit IRC18:09
*** krtaylor has joined #openstack-meeting-418:21
*** sdake_ has joined #openstack-meeting-418:23
*** amotoki has joined #openstack-meeting-418:25
*** sdake has quit IRC18:25
*** prateek_ has joined #openstack-meeting-418:27
*** uck has quit IRC18:28
*** uck has joined #openstack-meeting-418:29
*** bobh has joined #openstack-meeting-418:29
*** woodard_ has joined #openstack-meeting-418:30
*** woodard has quit IRC18:33
*** woodard_ has quit IRC18:34
*** cbouch has joined #openstack-meeting-418:34
*** ddieterly is now known as ddieterly[away]18:38
*** jingting has quit IRC18:38
*** jingting has joined #openstack-meeting-418:44
*** tonytan4ever has quit IRC18:45
*** ddieterly[away] is now known as ddieterly18:52
*** jingting has quit IRC18:52
*** liangy has joined #openstack-meeting-418:56
*** ddieterly has quit IRC18:57
*** dtardivel has quit IRC18:57
*** spzala has joined #openstack-meeting-418:59
*** _sarob has quit IRC19:00
*** galstrom is now known as galstrom_zzz19:00
*** banix has joined #openstack-meeting-419:00
*** sarob has joined #openstack-meeting-419:01
*** galstrom_zzz is now known as galstrom19:01
*** yamahata has quit IRC19:04
*** iyamahat has quit IRC19:04
*** yamahata has joined #openstack-meeting-419:05
*** jingting has joined #openstack-meeting-419:07
*** dshakhray has joined #openstack-meeting-419:09
*** piet has quit IRC19:11
*** yamamoto has quit IRC19:12
*** davidlenwell has quit IRC19:17
*** piet has joined #openstack-meeting-419:17
*** jorgem is now known as jorgem[away]19:18
*** armax has quit IRC19:19
*** armax has joined #openstack-meeting-419:22
*** armax has quit IRC19:22
*** banix has quit IRC19:23
*** armax has joined #openstack-meeting-419:27
*** davidlenwell has joined #openstack-meeting-419:29
*** ivc_ has quit IRC19:36
*** prateek_ has quit IRC19:38
*** _coolsvap_ has quit IRC19:42
*** salv-orl_ has joined #openstack-meeting-419:42
*** tonytan4ever has joined #openstack-meeting-419:42
*** salv-orlando has quit IRC19:45
*** sdake has joined #openstack-meeting-419:49
*** sdake_ has quit IRC19:52
*** banix has joined #openstack-meeting-419:52
*** thorst_ has joined #openstack-meeting-419:54
*** sarob has quit IRC19:57
*** sarob has joined #openstack-meeting-419:58
*** sambetts is now known as sambetts|afk19:58
*** sarob has quit IRC19:59
*** sarob has joined #openstack-meeting-420:00
*** iyamahat has joined #openstack-meeting-420:01
*** woodard has joined #openstack-meeting-420:09
*** woodard has quit IRC20:09
*** thorst_ has quit IRC20:10
*** woodard has joined #openstack-meeting-420:10
*** spotz is now known as spotz_zzz20:11
*** yamamoto has joined #openstack-meeting-420:13
*** yamamoto has quit IRC20:19
*** thorst_ has joined #openstack-meeting-420:25
*** janonymous has quit IRC20:28
*** vishnoianil has joined #openstack-meeting-420:30
*** vhoward has quit IRC20:32
*** vhoward has joined #openstack-meeting-420:33
*** Jeffrey4l_ has quit IRC20:34
*** Jeffrey4l_ has joined #openstack-meeting-420:35
*** vhoward has quit IRC20:38
*** spzala has quit IRC20:44
*** spzala has joined #openstack-meeting-420:45
*** spotz_zzz is now known as spotz20:47
*** spzala has quit IRC20:49
*** berendt has quit IRC20:51
*** thorst_ has quit IRC20:54
*** janonymous has joined #openstack-meeting-420:55
*** rainya has joined #openstack-meeting-420:55
*** sdague has quit IRC20:57
*** rainya_ has joined #openstack-meeting-420:59
*** rainya has quit IRC21:03
*** uck_ has joined #openstack-meeting-421:04
*** uck has quit IRC21:04
*** rocky_g has joined #openstack-meeting-421:04
*** sdague has joined #openstack-meeting-421:11
*** ddieterly has joined #openstack-meeting-421:14
*** baoli_ has quit IRC21:16
*** krtaylor has quit IRC21:20
*** ddieterly is now known as ddieterly[away]21:20
*** salv-orl_ has quit IRC21:25
*** jichen has quit IRC21:25
*** ddieterly[away] is now known as ddieterly21:25
*** salv-orlando has joined #openstack-meeting-421:25
*** woodard has quit IRC21:28
*** kylek3h has quit IRC21:30
*** rainya_ has quit IRC21:30
*** bnemec has quit IRC21:33
*** jichen has joined #openstack-meeting-421:33
*** cbouch has quit IRC21:34
*** bobh has quit IRC21:35
*** piet has quit IRC21:36
*** rtheis has quit IRC21:41
*** vishwanathj has quit IRC21:43
*** galstrom is now known as galstrom_zzz21:44
*** Swami has quit IRC21:49
*** ddieterly has quit IRC21:51
*** janonymous has quit IRC21:51
*** liangy has quit IRC21:51
*** mbirru has quit IRC21:51
*** harlowja has quit IRC21:51
*** wznoinsk has quit IRC21:51
*** mrhillsman has quit IRC21:51
*** sweston has quit IRC21:51
*** TheJulia has quit IRC21:51
*** wznoinsk has joined #openstack-meeting-421:51
*** liangy has joined #openstack-meeting-421:51
*** mrhillsman has joined #openstack-meeting-421:51
*** mbirru has joined #openstack-meeting-421:51
*** spzala has joined #openstack-meeting-421:52
*** janonymous has joined #openstack-meeting-421:52
*** TheJulia has joined #openstack-meeting-421:53
*** sweston has joined #openstack-meeting-421:53
*** jichen has quit IRC21:54
*** harlowja has joined #openstack-meeting-421:55
*** rocky_g has quit IRC22:05
*** dshakhray has quit IRC22:07
*** marst has quit IRC22:07
*** banix has quit IRC22:09
*** spotz is now known as spotz_zzz22:13
*** uck has joined #openstack-meeting-422:21
*** uck_ has quit IRC22:21
*** woodard has joined #openstack-meeting-422:22
*** woodard has quit IRC22:23
*** marst has joined #openstack-meeting-422:24
*** jovon has quit IRC22:26
*** tri2sing has quit IRC22:26
*** barmaley has quit IRC22:35
*** markvoelker has quit IRC22:36
*** Swami has joined #openstack-meeting-422:40
*** Swami_ has joined #openstack-meeting-422:40
*** tinwood has quit IRC22:41
*** tinwood has joined #openstack-meeting-422:42
*** yamahata has quit IRC22:52
*** iyamahat has quit IRC22:53
*** iyamahat has joined #openstack-meeting-422:54
*** amotoki has quit IRC22:54
*** janonymous has quit IRC22:58
*** rbak has quit IRC23:01
*** hongbin has quit IRC23:05
*** limao_ has quit IRC23:06
*** automagically has joined #openstack-meeting-423:13
*** thorst_ has joined #openstack-meeting-423:14
*** thorst_ has quit IRC23:25
*** Swami__ has joined #openstack-meeting-423:26
*** Swami has quit IRC23:30
*** sdague has quit IRC23:32
*** zhurong has joined #openstack-meeting-423:43
*** Swami_ has quit IRC23:45
*** Swami__ has quit IRC23:45
*** markvoelker has joined #openstack-meeting-423:48
*** markvoelker has quit IRC23:53
*** hogepodge has quit IRC23:53
*** hemanthm has quit IRC23:55
*** hemanthm has joined #openstack-meeting-423:55
*** hogepodge has joined #openstack-meeting-423:56

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