Monday, 2017-02-06

*** Jeffrey4l has joined #openstack-meeting-400:02
*** yfauser has joined #openstack-meeting-400:05
*** yfauser has quit IRC00:10
*** thorst_afk has quit IRC00:19
*** thorst_afk has joined #openstack-meeting-400:20
*** thorst_afk has quit IRC00:20
*** dimak has quit IRC00:25
*** dimak has joined #openstack-meeting-400:26
*** lihi has quit IRC00:26
*** lihi has joined #openstack-meeting-400:27
*** bobh has quit IRC00:30
*** l4yerffeJ has joined #openstack-meeting-400:32
*** ricolin has joined #openstack-meeting-400:42
*** SerenaFeng has joined #openstack-meeting-400:56
*** yfauser has joined #openstack-meeting-401:07
*** yfauser has quit IRC01:11
*** zhurong has joined #openstack-meeting-401:13
*** Julien-zte has joined #openstack-meeting-401:13
*** yfauser has joined #openstack-meeting-401:13
*** yfauser has quit IRC01:18
*** yifei_ has joined #openstack-meeting-401:18
*** limao has joined #openstack-meeting-401:19
*** gongysh has joined #openstack-meeting-401:28
*** bobh has joined #openstack-meeting-401:32
*** gongysh has quit IRC01:35
*** tovin07 has joined #openstack-meeting-401:49
*** l4yerffeJ_ has joined #openstack-meeting-401:50
*** l4yerffeJ_ has quit IRC01:50
*** l4yerffeJ_ has joined #openstack-meeting-401:50
*** Jeffrey4l_ has joined #openstack-meeting-401:51
*** l4yerffeJ has quit IRC01:52
*** gongysh has joined #openstack-meeting-401:52
*** Jeffrey4l has quit IRC01:53
*** yfauser has joined #openstack-meeting-402:14
*** yfauser has quit IRC02:19
*** baoli has joined #openstack-meeting-402:21
*** spzala has quit IRC02:21
*** baoli has quit IRC02:22
*** thorst_afk has joined #openstack-meeting-402:30
*** thorst_afk has quit IRC02:30
*** hongbin has joined #openstack-meeting-403:03
*** yfauser has joined #openstack-meeting-403:15
*** yfauser has quit IRC03:20
*** toan has quit IRC03:33
*** mhayden has quit IRC03:34
*** hughsaunders has quit IRC03:34
*** hughsaunders has joined #openstack-meeting-403:36
*** toan has joined #openstack-meeting-403:36
*** l4yerffeJ_ has quit IRC03:37
*** yfauser has joined #openstack-meeting-403:37
*** l4yerffeJ_ has joined #openstack-meeting-403:37
*** mhayden has joined #openstack-meeting-403:37
*** yfauser has quit IRC03:42
*** SerenaFeng has quit IRC03:47
*** amotoki has quit IRC03:56
*** sdake has joined #openstack-meeting-404:00
*** psachin has joined #openstack-meeting-404:04
*** zhurong has quit IRC04:04
*** l4yerffeJ_ has quit IRC04:06
*** l4yerffeJ_ has joined #openstack-meeting-404:06
*** links has joined #openstack-meeting-404:09
*** amotoki has joined #openstack-meeting-404:11
*** hieulq has joined #openstack-meeting-404:14
*** jokke__ has quit IRC04:14
*** gongysh has quit IRC04:19
*** hongbin has quit IRC04:21
*** adisky_ has joined #openstack-meeting-404:29
*** sp__ has joined #openstack-meeting-404:32
*** unicell has joined #openstack-meeting-404:34
*** v1k0d3n has quit IRC04:36
*** yfauser has joined #openstack-meeting-404:38
*** yfauser has quit IRC04:43
*** woodard has joined #openstack-meeting-404:45
*** david-lyle has joined #openstack-meeting-404:46
*** woodard has quit IRC04:50
*** zhurong has joined #openstack-meeting-404:50
*** david-lyle_ has joined #openstack-meeting-404:50
*** david-lyle has quit IRC04:50
*** trinaths has joined #openstack-meeting-404:52
*** david-lyle_ is now known as david-lyle04:52
*** benj_ has quit IRC04:55
*** amotoki has quit IRC05:04
*** bobh has quit IRC05:05
*** janki has joined #openstack-meeting-405:05
*** gongysh has joined #openstack-meeting-405:10
*** l4yerffeJ_ has quit IRC05:14
*** sdake has quit IRC05:18
*** limao has quit IRC05:21
*** david-lyle has quit IRC05:21
*** limao has joined #openstack-meeting-405:22
*** mattmceuen has quit IRC05:26
*** zhurong has quit IRC05:26
*** amotoki has joined #openstack-meeting-405:35
*** SerenaFeng has joined #openstack-meeting-405:37
*** yfauser has joined #openstack-meeting-405:39
*** yfauser has quit IRC05:43
*** limao has quit IRC05:48
*** limao has joined #openstack-meeting-405:52
*** salv-orlando has joined #openstack-meeting-406:00
*** yfauser has joined #openstack-meeting-406:00
*** thorst_afk has joined #openstack-meeting-406:04
*** yfauser has quit IRC06:05
*** bobh has joined #openstack-meeting-406:05
*** thorst_afk has quit IRC06:09
*** limao has quit IRC06:09
*** limao has joined #openstack-meeting-406:09
*** bobh has quit IRC06:10
*** revon has joined #openstack-meeting-406:11
*** limao has quit IRC06:14
*** liuyulong_ is now known as liuyulong06:16
*** links has quit IRC06:19
*** janki has quit IRC06:25
*** limao has joined #openstack-meeting-406:32
*** yfauser has joined #openstack-meeting-406:33
*** links has joined #openstack-meeting-406:35
*** sp__ has quit IRC06:44
*** links has quit IRC07:05
*** bobh has joined #openstack-meeting-407:06
*** nkrinner_afk is now known as nkrinner07:07
*** bobh has quit IRC07:10
*** limao has quit IRC07:16
*** limao has joined #openstack-meeting-407:17
*** links has joined #openstack-meeting-407:17
*** iyamahat has joined #openstack-meeting-407:18
*** limao has quit IRC07:21
*** tovin07 has quit IRC07:21
*** yamamoto has quit IRC07:25
*** janki has joined #openstack-meeting-407:33
*** limao has joined #openstack-meeting-407:36
*** mfedosin has joined #openstack-meeting-407:36
*** haijie has joined #openstack-meeting-407:36
*** iyamahat has quit IRC07:39
*** salv-orl_ has joined #openstack-meeting-407:49
*** haijie has quit IRC07:49
*** salv-orlando has quit IRC07:52
*** pcaruana has joined #openstack-meeting-407:55
*** nkrinner has quit IRC08:00
*** nkrinner has joined #openstack-meeting-408:00
*** zhurong has joined #openstack-meeting-408:03
*** bobh has joined #openstack-meeting-408:07
*** pcaruana has quit IRC08:07
*** pcaruana has joined #openstack-meeting-408:07
*** bobh has quit IRC08:11
*** benj_ has joined #openstack-meeting-408:24
*** yuli_s has quit IRC08:34
*** SerenaFeng has quit IRC08:34
*** dtardivel has joined #openstack-meeting-408:34
*** yuli_s has joined #openstack-meeting-408:34
*** yamamoto has joined #openstack-meeting-408:35
*** links has quit IRC08:45
*** links has joined #openstack-meeting-408:45
*** yamamoto has quit IRC08:47
*** limao has quit IRC08:51
*** limao has joined #openstack-meeting-408:52
*** salv-orl_ has quit IRC08:52
*** ralonsoh has joined #openstack-meeting-408:54
*** limao has quit IRC08:57
oanson#startmeeting Dragonflow09:01
openstackMeeting started Mon Feb  6 09:01:29 2017 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:01
openstackThe meeting name has been set to 'dragonflow'09:01
oansonAll right, who's here for the weekly?09:01
lihiHi09:01
dimakHello09:01
xiaohhuihello09:01
oansonSurprisingly, if I start the meeting in the correct channel, everyone is here :)09:02
*** SerenaFeng has joined #openstack-meeting-409:02
irenabhi09:02
oansonWe'll wait another minute, and then we'l start09:02
oansonAll right09:03
oansonI'm going to veer of the agenda for a second09:03
oansonI got the Dragonflow logo from the illustration team09:03
oansonlihi should have the link read any second now09:03
lihihttp://www.tiikoni.com/tis/view/?id=436a5d809:04
lihi:)09:04
oansonWhat do you guys think?09:04
irenablooks like question mark up down09:04
xiaohhuiit looks like a sea horse to me...09:05
lihiIf you want to give direct feedback on your mascot to the designers, go here: http://tinyurl.com/OSmascot09:05
oansonIt is a sea horse, yes.09:05
oansonI understood that we had to choose an animal that was real, not manmade, and not extinct09:05
oansonSo gsagie, the former PTL, chose a sea horse09:05
lihiWell, a sea horse kinda looks like a question mark up down09:06
xiaohhuiWhat is this log for?09:06
xiaohhuilog->logo09:06
oansonI think it is going to replace the network cable dragon logo we have now on all our project docs09:06
xiaohhuiI see09:07
oansonI think maybe ask it to be thinner, and have the spikes on the back more pronounced. Might make it a bit more dragon-ish09:08
lihiIt might be nice09:09
oansonAll right. So as lihi said, you can also give your comments directly here: http://tinyurl.com/OSmascot09:10
oansonLet's move on09:10
oanson#topic Roadmap09:11
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:11
oansonIPv6 - lihi, any updates?09:11
*** hshan has joined #openstack-meeting-409:11
lihiI had some unexpected isues with the unit tests, but I should  be done soon. I'm also refactoring a bit the sg code. It contains a lot of duplicate code09:12
oansonlihi, I see. Well, any cleanup to the code is appreciate as well.09:12
oansonDo you think it will be done by the PTG?09:13
lihiyes09:13
oansonCool.09:13
oansonNB refactor - dimak, I saw there are a lot of patches up09:14
oansonThey also look like they are coming along nicely.09:14
dimakyeah, primarily waiting for your +1's (or -1's)09:14
oansonSince this is a major overhaul, I'd like everyone to put their stamp of approval before we move forwards with this09:14
oansonI know it's a lot of code, but dimak did break it down for us, so it should be ... manageable :)09:15
oansondimak, I also understand you are building the SFC on top of it?09:15
dimakYeah, I also postponed some stuff09:15
dimakYes, I'm working primarily on SFC over the new models now09:15
dimaktrying to get the fullstack test I have to work09:16
oansonWe will need to move the models from the legacy structure to the refactored structure. Is that something you can do, or are you fully booked with SFC?09:16
dimakI can do that as soon as we converge on the basic framework09:17
irenaboanson, me and dimak started to check openAPI spec to prepare automation for the schema generation09:17
oansonGreat.09:17
oansonirenab, sounds good. How's that going?09:17
dimakYeah, once we have all the models in the new format we can relatively easily generate large parts of the api declaration09:17
irenabwe need to see if to keep model definition as a single piece or split db and api parts09:18
oansonThat's our REST API out-of-the-box?09:18
oansonIn general, we'll want to split the models of to be by topic09:19
irenabyes09:19
oansone.g. routers and l3 in one file, floating IPs in another, BGP (when it lands) in another, etc.09:19
irenaboanson, feature09:19
irenabtopic is abit overloaded term09:19
oansonYes, feature :)09:19
oansonWhich reminds me, the spec was merged yesterday evening09:20
irenabseems that openAPI spec documentation has nice tagging feature, to filter relevant APIs by tags09:20
oanson(Or this morning, according to time difference)09:20
dimakoanson, we should also examine the translation between db-stored data and api objects09:20
irenabso we can use tag = feature09:20
oansonirenab, that's a good idea09:21
oansondimak, what do you mean?09:21
dimakbecause api is expected to be backwards compatible09:21
dimakand some things present in api objects we might not want in the database09:21
oansondimak, yes, but only after the first version we have it09:21
oansonIt won't have to be backwards compatible to a time before API, and by the looks of it, it won't make it into Ocata09:22
dimakyeah09:22
oansonThere's just too little time to stabalise it, especially if we will need backwards compatibility09:22
dimakI just meant that db and api might need to diverge at some point09:22
irenabdimak, +109:23
oansonI guess we'll have to cross that bridge when we get there. We have to minimise API breaking changes, and see how to support backwards compatibility if we have to.09:24
oansonNeutron have a deprecation system, but I don't like it very much...09:24
oansonSeeing as we were on the broken end of such a change a few times :)09:24
irenaboanson, we just need to keep in mind the backward compatibility, not to break existing clients after first version is released09:24
oansonYes.09:25
oansonAnything else for API?09:25
irenabopenAPI also provides tools to generate clients in different launguages09:25
oansonThat's a powerful feature!09:26
irenabso once we are doen with model definition, seems the rest should not be too time consuming09:26
oansonThat was the plan when we started :)09:26
dimakWe'll still have to implement some kind of server to translate api to nb db09:27
*** sshnaidm is now known as sshnaidm|afk09:27
oansondimak, doesn't openAPI provide that too?09:27
irenabplease check the latest spec version and my replies to recent comments09:27
dimakoanson, You can generate a server with stubs09:28
dimakI don't we'd like rebasing on top of it each time09:28
oansonWe'll have to see what it provides exactly, then. The way we use it, the implementation of these stubs may be automated.09:28
dimakmaybe better to write someothing of our own with some magic to translate paths to models automatically09:28
oansondimak, no. These things should change only if the models change09:29
oansondimak, possibly. I was playing around with python bottle, which looks like it can do it :)09:29
oansonBut one step at a time09:29
*** tovin07 has joined #openstack-meeting-409:29
dimakoanson, we should also note that api spec is dependent on the models loaded09:29
oansondimak, sorry?09:30
dimakWe talked about dynamic loading of features09:30
oansonAh. Yes. Of course.09:30
dimake.g. apps + service plugins09:30
oansonWe have to support API for all loaded models, and not support API for models that aren't loaded.09:30
*** salv-orlando has joined #openstack-meeting-409:31
dimakthis means that the set of models we support is different for each configuration09:31
dimakwhat about 3rd party?09:31
oansonYes. But all have to be implemented, and only those that are loaded, should be supported by the API09:31
dimakI meant that if I have an out-of-tree feature I want to support09:32
oansonFor 3rd party, we will have to provide some way to extend our API. If everything is done automagically, that wouldn't be a problem.09:32
irenabwe will havCen we delay a bit the dynamic loading, at least till we have basic stuff working?09:32
irenabCan we delay a dynamic part?09:32
oansonirenab, no worries. Right now we're only planning ahead. It's not like dimak already has it all written. (dimak, right?)09:32
dimakheh, not yet09:33
irenaboanson, I won't be suprised to see it during the afternoon :-)09:33
oansonHe said he doesn't have it written yet. So it will take him at least until09:33
oansonthe evening09:33
oansonAll right. Let's move on.09:34
oansondistributed sNAT09:34
oansonthe second implementation has been uploaded. But I will talk with ishafran. It looks like he squashed the two commits.09:34
oansonI will ask him to un-squash them.09:34
oansonTAP-as-a-Service - yuli_s are you in?09:35
*** links has quit IRC09:35
dimakIt looks like the snat patch is on top of the abandoned patch09:35
oansondimak, that sounds strange. But I'll ask ishafran organise it so it's digestible09:36
irenabI also talked with ishafran regarding the ml2 driver change, I proposed different approach and we will continue the discussion09:36
oansonirenab, you want to elaborate?09:36
*** ishafran has joined #openstack-meeting-409:37
oansonishafran, right on time :)09:37
ishafranHi09:37
irenabthe lates patch includes changes to  ml2 df driver, I suggested a bit different approach that does not require ml2 driver modification.09:37
*** itamaro has joined #openstack-meeting-409:38
itamaroHi09:38
irenabbut I think we still need some time to discuss it offline09:38
oansonSure.09:39
irenabin short, get port_created notification outside of the ml2 driver and create compute tenant gw port09:39
oansonirenab, as in a second mechanism driver?09:39
irenaboanson, more like l3 service09:39
irenabbut maybe another l2 driver can work as well09:40
oansonIf Neutron supports that, it would be great. I though ports and l2 were only accessible via the mechanism driver?09:40
ishafranI am actually did not find alternative pre/post commit mechansim except mech_driver since our talk yesterday09:40
irenabishafran, will show you what I meant09:40
oansonAll right. As irenab said, let's take this offline.09:41
oansonShould we continue?09:41
ishafranlets take tit offline09:41
oansonTap-as-a-Service - I understand that yuli_s is setting up a taas environment, and then he'll start the implementation09:42
oanson(He is also working with the Rally croud on something else)09:42
oansoncrowd*09:43
oansonAll right. Anything else for roadmap?09:43
oanson#topic Open Discussion09:44
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:44
oansonThe floor is for the taking09:44
xiaohhuiI have one question about storing port unique key in reg09:44
xiaohhuiin table 0 we store it in reg6, but in all other tables we store it in reg709:44
xiaohhuiand the value in reg6 seems only be used by metadata app09:45
dimakI though it reg6 is used for source port and reg7 for the dest09:45
oansonreg6 is the source port's ID09:45
oansondimak beat me to it :)09:45
xiaohhuiI see it09:45
xiaohhuithanks guys09:45
oansonThe thing is, only metadata actually needs to know the source (So far)09:45
oansonIn theory, I guess reg6 can be winged for the in_port (like in port sec)09:46
*** SerenaFeng has quit IRC09:47
oansonThe floor is free again.09:47
oansonAll right. Thanks everyone.09:48
oanson#endmeeting09:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:48
openstackMeeting ended Mon Feb  6 09:48:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-02-06-09.01.html09:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-02-06-09.01.txt09:48
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-02-06-09.01.log.html09:48
*** Julien-zte has quit IRC09:50
*** itamaro has quit IRC09:50
*** ishafran has quit IRC09:50
*** sshnaidm|afk is now known as sshnaidm09:53
*** barmaley has joined #openstack-meeting-409:56
*** zhurong has quit IRC09:56
*** barmaley has quit IRC09:58
*** sambetts|afk is now known as sambetts10:06
*** neiljerram has joined #openstack-meeting-410:14
*** jokke_ has joined #openstack-meeting-410:16
*** ricolin has quit IRC10:25
*** yamamoto has joined #openstack-meeting-410:45
*** zhurong has joined #openstack-meeting-410:45
*** yamamoto has quit IRC10:48
*** alij has joined #openstack-meeting-410:52
*** amotoki has quit IRC10:55
*** alij has quit IRC11:06
*** alij has joined #openstack-meeting-411:06
*** alij has quit IRC11:09
*** alij has joined #openstack-meeting-411:10
*** alij has quit IRC11:15
*** rfolco has joined #openstack-meeting-411:17
*** alij has joined #openstack-meeting-411:17
*** yamamoto has joined #openstack-meeting-411:20
*** links has joined #openstack-meeting-411:21
*** alij has quit IRC11:21
*** alij has joined #openstack-meeting-411:23
*** links has quit IRC11:25
*** alij has quit IRC11:28
*** yamamoto has quit IRC11:31
*** aarefiev_afk is now known as aarefiev11:35
*** amotoki has joined #openstack-meeting-411:35
*** gongysh has quit IRC11:39
*** yfauser has quit IRC11:52
*** yfauser has joined #openstack-meeting-411:52
*** alij has joined #openstack-meeting-411:53
*** yfauser has quit IRC11:57
*** alij has quit IRC11:57
*** alij has joined #openstack-meeting-411:59
*** alij has quit IRC12:01
*** amotoki has quit IRC12:03
*** yamamoto has joined #openstack-meeting-412:04
*** pbourke has quit IRC12:05
*** pbourke has joined #openstack-meeting-412:05
*** yamamoto has quit IRC12:08
*** bobh has joined #openstack-meeting-412:10
*** amotoki has joined #openstack-meeting-412:10
*** dave-mccowan has joined #openstack-meeting-412:14
*** bobh has quit IRC12:15
*** rwallner has joined #openstack-meeting-412:18
*** sdague has joined #openstack-meeting-412:23
*** rwallner has quit IRC12:28
*** rwallner has joined #openstack-meeting-412:30
*** rwallner_ has joined #openstack-meeting-412:30
*** amotoki has quit IRC12:33
*** rwallner has quit IRC12:34
*** salv-orlando has quit IRC12:37
*** thorst_afk has joined #openstack-meeting-412:39
*** salv-orlando has joined #openstack-meeting-412:40
*** trinaths has quit IRC12:50
*** limao has joined #openstack-meeting-412:52
*** yfauser has joined #openstack-meeting-412:53
*** yfauser has quit IRC12:57
*** yfauser has joined #openstack-meeting-413:08
*** julim has quit IRC13:08
*** janki has quit IRC13:09
*** bobh has joined #openstack-meeting-413:09
*** janki has joined #openstack-meeting-413:09
*** sdague has quit IRC13:10
*** yfauser has quit IRC13:12
*** sdague has joined #openstack-meeting-413:12
*** sdague_ has joined #openstack-meeting-413:12
*** amotoki has joined #openstack-meeting-413:12
*** sdague_ has quit IRC13:15
*** woodard has joined #openstack-meeting-413:17
*** v1k0d3n has joined #openstack-meeting-413:19
*** yfauser has joined #openstack-meeting-413:19
*** woodard has quit IRC13:21
*** kylek3h_away has quit IRC13:21
*** h37 has joined #openstack-meeting-413:23
*** xingchao has joined #openstack-meeting-413:24
*** SerenaFeng has joined #openstack-meeting-413:25
*** gongysh has joined #openstack-meeting-413:26
*** bobh has quit IRC13:28
*** Jeffrey4l_ has quit IRC13:32
*** Jeffrey4l_ has joined #openstack-meeting-413:34
*** rwallner_ has quit IRC13:36
*** sdake has joined #openstack-meeting-413:37
*** rwallner has joined #openstack-meeting-413:37
*** amotoki has quit IRC13:38
*** sdake_ has joined #openstack-meeting-413:40
*** sdake has quit IRC13:44
*** SerenaFeng has quit IRC13:46
*** woodard has joined #openstack-meeting-413:46
*** SerenaFeng has joined #openstack-meeting-413:46
*** woodard has quit IRC13:47
*** dims_ has quit IRC13:47
*** woodard has joined #openstack-meeting-413:47
*** kylek3h_away has joined #openstack-meeting-413:47
*** alraddarla has joined #openstack-meeting-413:48
*** SerenaFeng has quit IRC13:48
*** dims has joined #openstack-meeting-413:48
*** salv-orl_ has joined #openstack-meeting-413:49
*** Bluebell_ has joined #openstack-meeting-413:51
*** salv-orlando has quit IRC13:52
*** limao has quit IRC13:54
*** limao has joined #openstack-meeting-413:55
*** yedongcan has joined #openstack-meeting-413:57
*** reedip_ has joined #openstack-meeting-413:57
*** Jeffrey4l_ has quit IRC13:58
*** limao has quit IRC13:58
*** edleafe- is now known as edleafe13:59
*** limao has joined #openstack-meeting-413:59
*** ivc_ has joined #openstack-meeting-413:59
*** uck has joined #openstack-meeting-413:59
apuimedo#startmeeting kuryr14:00
openstackMeeting started Mon Feb  6 14:00:26 2017 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: kuryr)"14:00
openstackThe meeting name has been set to 'kuryr'14:00
apuimedoHello everybody and welcome to another Kuryr weekly IRC meeting14:00
apuimedoWho's here for the meeting?14:00
ivc_o714:00
limaoo/14:00
alraddarlao/14:01
yedongcano/14:01
mchiapperoo/14:01
*** julim has joined #openstack-meeting-414:01
irenabhi14:01
apuimedogood. Nice showing!14:02
apuimedo#topic kuryr-lib14:02
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:02
ltomasboo/14:02
*** garyloug has joined #openstack-meeting-414:02
apuimedo#info hongbin has sent a patch for fixing the kuryr-libnetwork devref https://review.openstack.org/#/c/426644/14:03
garylougo/14:03
*** joedborg has joined #openstack-meeting-414:03
apuimedoAs you can see, that patch is to openstack/kuryr, where the devref used to live. I think it is overdue that we move it to openstack/kuryr-libnetwork14:03
apuimedoAnybody opposes that?14:04
apuimedo(my proposal is to merge this patch and then move the content)14:04
irenab+114:04
*** Bluebell_ has left #openstack-meeting-414:04
janonymouso/14:05
limao+114:05
mchiappero+114:05
*** matrohon has joined #openstack-meeting-414:05
yedongcanagree14:05
apuimedogood14:06
apuimedoanybody volunteers?14:06
apuimedo:P14:06
mchiappero-114:06
mchiappero:P14:06
alraddarlaI can do it14:07
apuimedogreat!14:07
apuimedothanks14:07
apuimedo#action alraddarla to move the kuryr-libnetwork devref to openstack/kuryr-libnetwork14:08
apuimedogood14:08
*** joedborg has quit IRC14:08
apuimedo#action apuimedo, limao, irenab to review https://review.openstack.org/#/c/427533/14:08
*** cathrichardson has joined #openstack-meeting-414:08
apuimedoAnything else about kuryr-lib?14:09
*** david-lyle has joined #openstack-meeting-414:09
*** zhurong has quit IRC14:09
apuimedogood. Moving on!14:10
apuimedo#topic kuryr-libnetwork14:10
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:10
*** joedborg has joined #openstack-meeting-414:11
*** cathrich_ has quit IRC14:11
apuimedo#info There's been some work on optimizing the subnetpool handling https://review.openstack.org/420610 and https://review.openstack.org/42792314:12
apuimedoIt's a really good thing14:12
apuimedoThere's a good number of patches to improve kuryr-libnetwork this week. I think that after these subnetpool and tag patches that are posted we should cut a release and branch out Ocata14:13
apuimedo#action apuimedo limao vikas and irenab to review https://review.openstack.org/#/q/project:openstack/kuryr-libnetwork14:13
apuimedoDo you agree on having these in for branching ocata and cutting a release?14:14
* apuimedo looking for feedback on things that we may need to wait for or things we should delay14:14
irenabapuimedo: I am not sure, but seems we may missed the proper dates: http://git.net/ml/openstack-dev/2017-01/msg00317.html14:14
apuimedoirenab: AFAIK we are not bound to official release dates since we are release-independent14:15
irenabapuimedo: great, then its ok14:15
apuimedo#action apuimedo to check with openstack/release if we can cut an ocata branch at a later date14:15
apuimedoThis, of course, would mark the first time that we cut a release branch and backport fixes14:16
*** david-lyle has quit IRC14:16
apuimedoIf anybody wants to volunteer to be handle the first line of reviews for kuryr-libnetwork backports it will be great14:17
*** cathrichardson has left #openstack-meeting-414:17
apuimedoAnything else on kuryr-libnetwork?14:17
*** pc_m has joined #openstack-meeting-414:17
*** baoli has joined #openstack-meeting-414:18
apuimedovery well. Moving on!14:18
apuimedoI can feel people are waiting for the coming section14:18
apuimedo#topic kuryr-kubernetes14:19
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:19
apuimedo#info the first patch for Kubernetes ClusterIP services support has been approved and is being merged https://review.openstack.org/#/c/427440/14:20
*** salv-orl_ has quit IRC14:20
*** rwallner has quit IRC14:20
apuimedo#info One or two more patches are still expected for having functional Kubernetes ClusterIP services backed by neutron-lbaasv214:20
*** joedborg has quit IRC14:21
apuimedoivc_: can you describe a bit the remaining patches that are coming up?14:21
*** rwallner has joined #openstack-meeting-414:21
ivc_apuimedo sure14:21
apuimedothanks14:21
ivc_there are 2 parts left from https://review.openstack.org/#/c/376045/14:21
apuimedo#link https://review.openstack.org/#/c/376045/14:22
ivc_the driver and the Endpoints handler14:22
*** Julien-zte has joined #openstack-meeting-414:23
apuimedovery well14:23
apuimedolooking forward to them14:23
ivc_for clarity it would probably make sense to keep them separate14:23
apuimedoAgreed14:23
ivc_to avoid really huge patches ofc14:23
apuimedoyes, let's be benevolent towards reviewers :-)14:24
ivc_but the problem with that is that you wont be able to verify the first patch14:24
apuimedoof course14:24
apuimedoit's the price to pay. Gerrit should have whole branch merge at once14:25
apuimedobut oh well. Maybe some day14:25
irenabivc_: you can keep patches dependant14:25
*** rwallner has quit IRC14:26
apuimedo#info ltomasbo has been driving work on resource pools with a spec https://review.openstack.org/427681 and a basic implementation of Port resource reutilization https://review.openstack.org/42668714:26
ivc_irenab yes but what im saying is if i add driver first there's no code that would use it14:26
apuimedoirenab: I meant more for testing and CI14:26
apuimedothere was some discussion on the channel on the merit of the resource management approach between ivc_ and ltomasbo14:27
ltomasboapuimedo, I'm still working on that patch14:28
ivc_ltomasbo the patch or the devref?14:28
ltomasboand I believem the advantage for the nested case will be larger14:28
apuimedoivc_: was arguing for an increased focus on reutilization of the already bound and set up ovs devices14:28
apuimedowhile the patch currently is optimizing for Neutron interactions14:28
*** cleong has joined #openstack-meeting-414:28
ltomasboas the port is plugged to the VM and attached as a subport, so it will only be to link the veth to the VM vnic14:28
* apuimedo trying to fill in onlookers, please correct if I misrepresented it14:29
ltomasboon the patch, I will also update the devref14:29
ivc_i'm still confident we need to delay this optimisation until we get daemon/exec split14:29
apuimedoltomasbo: IIUC in the nested case, it will only be about creating a new vlan device (and then updating the subport name), is that right?14:29
ltomasbomy idea is to have a pool of subports, already with their own vlan14:30
ltomasboand then it is just a matter of linking the container to an already available subport/vlan14:30
*** hongbin has joined #openstack-meeting-414:30
ltomasboso, it will be just changing subport name14:30
hongbino/14:30
ivc_ltomasbo have you performed any benchmarks?14:30
*** superdan is now known as dansmith14:30
ltomasbotrying to, but I need a bigger machine14:30
apuimedoivc_: that may be. I wonder if even without the split we can reuse the bound devices and save the ovs agent dance14:31
ltomasbobut I'll definitely do14:31
ivc_ltomasbo it would be nice to have some profiling details before we start optimising14:31
irenabivc_: did you do some profiling?14:31
apuimedohongbin: nice to see you. We'll do the fuxi section after this one (thanks for the kuryr-libnetwork work, we already talked about it earlier)14:31
ivc_irenab a bit14:31
ltomasboyes, but it will be also dependant on the concurrence of port creation14:32
hongbinapuimedo: ack14:32
ivc_on a devstack env running inside vm14:32
*** rwallner has joined #openstack-meeting-414:32
ltomasbowe have measure some delays of up to 10 seconds when creating several ports in parallel, around 1014:32
irenabivc_: so you see the RPC part is more meaningful than neutron api calls?14:32
apuimedowhich brings me to14:32
apuimedowe should really get this in https://review.openstack.org/#/c/422946/14:32
ivc_irenab from what i've seen the call to neutron's port_create takes much less time than the polling for status==ACTIVE14:33
apuimedoivc_: Since I prefer you to work on the driver and handler service patches, mind if I take over that patch and address irenab's comments?14:33
ivc_irenab but port_create also degrades as you increase the number of concurrent requests14:33
apuimedoivc_: it degrades a lot14:34
apuimedothat's why batch creation will be useful14:34
ivc_yup14:34
irenabsounds like both optimizations are useful14:34
ltomasboand even more for subports...14:34
ltomasboyep, I agree on that14:34
apuimedoltomasbo: I'd say, even more for non vlan-aware-VMs pod-in-VM, IIRC the worst perf was when you do a lot of calls to add allowed-address-pairs14:35
apuimedoirenab: they are. I agree though that the order matters14:35
apuimedoand we should be looking to perform the split soon14:35
ivc_but optimising vif binding later will require a bit different approach than optimising port_create with pooling now14:35
ivc_so my point is generally about not wasting time on pool now and wait until we can do both optimisations14:36
apuimedoivc_: I favor working on both parts of the spec14:36
ivc_which requires the split14:36
irenabI suggest to finilize the next optimization step over the devref that ltomasbo proposed14:36
ltomasboapuimedo, in pod in vms you need to call allowed-address-pairs, but in vlan-aware-vms you need to call attach_subport14:36
apuimedoivc_: I don't think working on the devref is wasting time14:36
ivc_irenab yes, but the patch could wait14:36
ltomasboso, similar I assume14:37
apuimedoand the patch is sorta PoC14:37
ivc_apuimedo irenab ltomasbo also i think that should not be a devref, but rather a spec14:37
irenabivc_: for split, optimization?14:37
ivc_followed by bp14:37
apuimedoltomasbo: I'm more comfortable batching attach_subport than I am with allowed_address-paris14:37
ivc_irenab for optimisation14:37
apuimedo*pairs14:37
ltomasboapuimedo, sure!14:38
irenabapuimedo: ivc_ ltomasbo do you want to set some chat to converge on the optimization?14:38
ivc_irenab sure14:39
*** baoli has quit IRC14:39
ltomasbook14:39
*** joedborg has joined #openstack-meeting-414:39
apuimedoI think we all agree on what needs to be done. It's a bit of a matter of setting priorities14:39
irenabof course anyone else who is willing to join is more than welcome14:40
apuimedosplit before or split after14:40
apuimedobasically14:40
apuimedoI'll send an invite14:40
irenabapuimedo: thanks14:40
ivc_we had that planned long ago, i just did not expect someone to start working on it that early :)14:40
*** xingchao has quit IRC14:40
apuimedoivc_: people scratch their own itch when it itches14:40
apuimedo:P14:41
irenablets just kmake sure there is an alignment14:41
ivc_true14:41
apuimedo#action apuimedo to send an invite to a video meeting about resource management to mailing list14:41
apuimedochanging topics a bit14:41
apuimedoI've been researching on external access to services14:42
apuimedoparticularly the load balancer type14:42
*** spzala has joined #openstack-meeting-414:42
apuimedoI'll send a proposal soon. The idea is to make ivc_'s service handler allocate a fip and annotate for it14:42
apuimedoand have the existing k8s openstack cloudprovider add an option to use kuryr netowrking, which means it will jsut wait for the annotation and report it14:43
irenabapuimedo: fip for vip?14:43
apuimedoirenab: fip, the vip is already handled by ivc_'s code14:43
irenaballocate fip for vip?14:44
apuimedoI've been trying to reach Angus Lees on #openstack-containers without success, I'll try email14:44
apuimedoirenab: that's right14:44
irenabapuimedo: try k8s slack14:44
apuimedoirenab: right. I'll check if he's there14:44
apuimedothanks14:44
*** xingchao has joined #openstack-meeting-414:44
irenabhttps://kubernetes.slack.com/messages/sig-openstack/14:44
apuimedoI've also been investigating on openshift router pod, which gives routed access to services14:45
apuimedoI think it gives a nice alternative (or at least some food for thought)14:45
apuimedobasically what it does is have a pod that loadbalances the access to the endpoints14:46
*** baoli has joined #openstack-meeting-414:46
apuimedothis way (although not with openshift's impl) one can work around the udp limitations14:46
ivc_apuimedo loadbalances how?14:46
*** uck has quit IRC14:46
apuimedoivc_: openshift uses haproxy, so it's a no for UDP14:46
apuimedobut it checks the endpoints itself14:46
apuimedothe one they have is just for http and https14:47
mchiapperoirenab: cannot access14:47
apuimedoso you only need one fip for all the services14:47
apuimedoit resolves based on service name14:47
apuimedofqdn14:47
ivc_apuimedo that reminds me of haproxy we have in LBaaS14:47
apuimedowhich is interesting14:47
apuimedo(and could be useful for ingress controllers)14:47
apuimedoanyway, for udp I suppose you'd do something like ipvs on a pod14:47
irenabmchiappero: you should register from here: http://slack.k8s.io/14:47
mchiapperoirenab: thanks14:48
irenabsorry, need to leave14:48
*** sdake_ is now known as sdake14:49
apuimedoirenab: thanks for joining14:49
*** xingchao has quit IRC14:49
apuimedoivc_: anyway, this was basically a food for thought14:49
*** matrohon has quit IRC14:49
apuimedosince we may have users that don't want a full FIP for a service, and sharing load balancers brings some complications as we already discussed other times14:49
ivc_apuimedo i'd love to see k8s driver in octavia14:49
apuimedoivc_: me too14:50
apuimedobut AFAIK nobody is driving it yet14:50
apuimedoivc_: I'll try to inquire about that in Atlanta14:50
apuimedoAnything else about kuryr-kubernetes?14:50
ivc_apuimedo doesn't seem as if there's a lot of work to make that driver14:51
apuimedoivc_: with haproxy? Probably not14:51
ivc_yep14:51
*** thorst_afk is now known as thorst_14:51
apuimedoit's more about HOW14:51
ivc_i'd say more about WHO :)14:51
*** numans has joined #openstack-meeting-414:52
apuimedoin other words, I don't suppose they'd like to tie it to Kuryr, so...14:52
apuimedoalright14:52
apuimedomoving on14:52
apuimedo#topic fuxi14:53
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:53
hongbinhi14:53
apuimedohongbin: sorry for the short time14:53
apuimedo#chair hongbin14:53
openstackCurrent chairs: apuimedo hongbin14:53
hongbinnp , i don't have too much to update this week14:53
hongbinjust a note that the kubernetes-fuxi proposal has been approved: https://review.openstack.org/#/c/423791/14:53
hongbinalso, at last week, contributors submitted several fixes: https://review.openstack.org/#/q/project:openstack/fuxi14:54
hongbini personally mainly worked on the kuryr-libnetwork, so don't have too much at fuxi last week14:54
hongbinapuimedo: ^^14:54
apuimedothanks again for the kuryr-libnetwork work14:54
apuimedo:-)14:55
hongbinmy pleasure14:55
apuimedolimao: please help me review the fuxi patches14:55
apuimedo#topic general discussion14:55
*** openstack changes topic to "general discussion (Meeting topic: kuryr)"14:55
limaoapuimedo: sure14:55
apuimedo#info I will be posting the calendar for the VTG this week14:55
apuimedoplease check the mailing list and let me know if there are any incompatibilities14:56
alraddarlaWon't be able to join any of the PTG sessions....they are way too early in my time zone :P14:57
*** jchhatbar has joined #openstack-meeting-414:57
apuimedoPlease remember to vote for the sessions you want to see on https://etherpad.openstack.org/p/kuryr_virtual_gathering_2017h114:58
apuimedoalraddarla: you mean VTG14:58
apuimedo:-)14:58
*** janki has quit IRC14:58
alraddarlayes, sorry VTG*14:58
apuimedoalraddarla: East coast?14:58
alraddarla:)14:58
alraddarlacentral14:58
apuimedolike hongbin maybe14:59
apuimedook, I'll move it to later time14:59
apuimedoalraddarla: but do vote14:59
apuimedo:-)14:59
apuimedoVery well, if there is anything else, bring it up on the channel14:59
apuimedoThanks to all of you for joining in the meeting!14:59
apuimedo#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Mon Feb  6 14:59:39 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-02-06-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-02-06-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-02-06-14.00.log.html14:59
jimbaker#startmeeting craton15:00
openstackMeeting started Mon Feb  6 15:00:00 2017 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
jimbaker#chair sigmavirus sulo jimbaker15:00
*** openstack changes topic to " (Meeting topic: craton)"15:00
openstackThe meeting name has been set to 'craton'15:00
*** alraddarla has left #openstack-meeting-415:00
openstackCurrent chairs: jimbaker sigmavirus sulo15:00
*** limao has left #openstack-meeting-415:00
sigmaviruso/15:00
jimbaker#link https://etherpad.openstack.org/p/craton-meetings15:00
jimbakersigmavirus, please take the chair15:00
*** pc_m has left #openstack-meeting-415:00
*** git-harry has joined #openstack-meeting-415:01
sigmavirusSo I'm editing the agenda now =<15:01
*** yedongcan has quit IRC15:01
sigmavirus#topic Roll Call15:01
*** openstack changes topic to "Roll Call (Meeting topic: craton)"15:01
jimbakero/15:01
thomasemo/15:02
*** lakerzhou has joined #openstack-meeting-415:02
git-harryhi15:02
sigmavirushi errybody15:02
*** limao_ has joined #openstack-meeting-415:02
*** limao_ has quit IRC15:02
*** limao has joined #openstack-meeting-415:02
sigmavirus#topic Action Items from Last Meeting15:02
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: craton)"15:02
sigmavirus#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-01-30-15.00.html15:02
sigmavirus#note There were no action items apparently15:03
jimbakerindeed15:03
sigmavirus#topic Stand-Up15:03
*** openstack changes topic to "Stand-Up (Meeting topic: craton)"15:03
sigmavirus#note I'll go round the channel asking folks for their updates15:04
sigmavirus#topic Stand-Up thomasem15:04
*** openstack changes topic to "Stand-Up thomasem (Meeting topic: craton)"15:04
thomasemGot my dev environment up and working cleanly15:04
thomasemfamiliarized myself a bit with the project through patches for a couple of bugs15:04
*** jchhatbar has quit IRC15:05
thomasemI added variables support for /projects which is in review (and I believe close to ready to merge): https://review.openstack.org/#/c/42777715:05
*** ivc_ has left #openstack-meeting-415:05
*** gongysh has quit IRC15:05
*** baoli has quit IRC15:05
thomasemI added CLI support for the existing /projects functionality in master, which is in review and has one +2: https://review.openstack.org/#/c/428996/15:05
thomasemI threw up a quick fix for a little logic bug I found this morning: https://review.openstack.org/#/c/429725/15:05
*** baoli has joined #openstack-meeting-415:05
sigmavirusSounds like a productive 1st week thomasem15:06
jimbakerthomasem, thanks for that work, and sounds like some reviews to prioritize15:06
thomasemYep! Thanks!15:06
thomasemAs of today, wondering what I want to work on next15:06
thomasemI filed 6 bugs over the past week15:06
thomasemOne I could quickly attack is the project admin permissions that sulo and I chatted about this morning https://bugs.launchpad.net/craton/+bug/166219915:07
openstackLaunchpad bug 1662199 in craton "incorrect permissions for Projects CRUD" [Undecided,New]15:07
thomasemAnd there are several others here https://bugs.launchpad.net/craton/+bugs?search=Search&field.bug_reporter=thomas-maddox15:07
jimbakergood to look at the project with fresh eyes15:07
sigmavirusCool, let's discuss that later in the meeting?15:07
jimbakeryes15:07
thomasemBlocked by this patch https://review.openstack.org/#/c/427032/3 for adding support for projects variables15:08
thomasemdone. :)15:08
jimbakerthomasem, ack15:08
sigmavirus#topic Stand-Up git-harry15:08
*** openstack changes topic to "Stand-Up git-harry (Meeting topic: craton)"15:08
*** woodard_ has joined #openstack-meeting-415:09
git-harryRelated to the spec I put up about documenting/improving the variable API, I'm refactoring that part of the code to strip out all the duplication. This should simplify any work identified by that spec.15:09
*** woodard has quit IRC15:10
git-harryCurrently sorting out the tests for it and then it should be done.15:10
git-harrydone15:10
sigmavirus#topic Stand-Up jimbaker15:11
*** openstack changes topic to "Stand-Up jimbaker (Meeting topic: craton)"15:11
jimbakercomplete  https://review.openstack.org/#/c/427032 (variable support in the CLI for regions, cells, hosts; demoed last week)15:11
jimbakerminor refactoring plan for the alembic migration to better support FK, PK constraint setup, in support of15:12
jimbakerRBAC WIP posted15:12
jimbakerdone15:12
sigmavirus#topic Stand-Up sulo15:12
*** openstack changes topic to "Stand-Up sulo (Meeting topic: craton)"15:12
* sigmavirus thinks sulo is here15:12
*** hongbin has quit IRC15:13
suloyes o/15:13
suloif i missed that earler15:13
sulohave a few outstanding patches that i need to finish15:13
suloon cli and and need to cleanup the spec (needs more reviews)15:13
sulobut right now looking at exposing parent/child relational data15:13
suloin resources15:13
suloand in the mean time looking at making15:14
jimbaker+1, this is very important work that toan has expressly asked for ASAP15:14
sulonetwork-x related resouces more robust as well15:14
sigmavirusjimbaker: the parent/child relational data?15:14
suloright now it looks like sellotaped stuff a litte15:14
*** mfedosin has quit IRC15:14
suloall my fault ofcourse15:14
sulodone15:14
sigmavirusjimbaker: let's discuss that when we prioritize reviews15:14
sulosigmavirus: so each device can have a parent device15:15
jimbakersigmavirus, yes, the parent-child data15:15
sigmavirus#topic Stand-Up sigmavirus15:15
*** openstack changes topic to "Stand-Up sigmavirus (Meeting topic: craton)"15:15
jimbakersulo, let's wait15:15
sulowe are not exposing it in the rest api15:15
git-harryjimbaker: is that requirement captured anywhere/15:15
*** mfedosin has joined #openstack-meeting-415:15
jimbakergit-harry, yes, in dusty's doc15:15
sigmavirusI'm finishing up the client related work for pagination as well as testing it. Still trying to decide how to display pagination to the cli15:15
sigmavirusI need to investigate how other OS clients do it and what makes sense for us15:16
*** baoli has quit IRC15:16
sigmavirusI don't see Syed or Jovon in here15:17
sigmavirus(or in #craton for that matter)15:17
*** iyamahat has joined #openstack-meeting-415:17
sigmavirus#topic This Week's Priorities15:17
*** openstack changes topic to "This Week's Priorities (Meeting topic: craton)"15:17
*** yamahata has joined #openstack-meeting-415:17
sigmavirusIt seems we will want to prioritize the parent/child relationship work. It would be good to get that into a spec15:17
sulojimbaker: can you link the WIP for rbac ?15:17
jimbakersigmavirus, do any such tools support some cleverness like exporting their markers to the shell, such as via eval?15:17
sigmavirusPerhaps we should work on turning Dusty's doc into a set of specs15:17
sulosigmavirus: +115:18
jimbakersigmavirus, first: let's put it up in an etherpad15:18
jimbakerso it's public15:18
jimbakeri can take as an action item15:18
sigmavirus#action jimbaker to turn dusty's doc into an etherpad15:18
suloits very difficutl to look at 10 different places to see req's so let just put it in LP15:18
jimbakerthen usual breakdown into blueprints15:18
jimbakeret15:18
jimbakeretc15:18
thomasem+1!15:18
sulodont have to be specs .. lets make LP issues that can turn into specs later ?15:18
sigmavirussulo: blueprints or issues work15:19
*** baoli has joined #openstack-meeting-415:19
*** baoli has quit IRC15:19
sigmavirusblueprints would be better if we plan to turn them into specs15:19
jimbakersulo, it's not directly actionable in that way - there's some overlap with completed work for example15:19
sigmaviruswe can then break down work items into individual issues like I did for pagination15:19
suloyeah i agree, just saying it would be nice to have it all in one place15:19
jimbakerbut we could put in as a bug or something15:19
*** sneti_ has joined #openstack-meeting-415:19
sigmavirussulo: understood15:20
jimbakerthe resolution of which is a check off - there's a spec for each req15:20
*** sneti_ has quit IRC15:20
jimbakeror it's already done, just needs demoing15:20
jimbakerthat sort of thing15:20
jimbakerthat might be a blueprint that links to other blueprints. but in lp somehow15:20
sigmavirus#action jimbaker once the etherpad is created, add reviewing it as a standing item to our meeting template15:20
sigmavirusjimbaker: that's possible15:21
jimbakersigmavirus, +1 to doing this review15:21
sigmavirusOkay, so after the parent/child prioritized work, what else is a priority15:21
*** garyloug has quit IRC15:21
sigmavirusthomasem: can you #link the review blocking you?15:21
thomasem#link https://review.openstack.org/#/c/427032/315:22
jimbakerantonym asked us about bulk set/get of resources and their variables last week15:22
sulojimbaker: is the rabc sutff posted, the wip patch ?15:22
jimbakersulo, no15:22
suloah15:22
jimbakeras i said, that's what i will be doing15:22
sulogotcha15:22
jimbakerawesome15:23
suloi thought you meant you posted it to review as wip15:23
jimbakerso back to bulk support15:23
jimbakersulo, i wish15:23
jimbakerbut it will be there soon enough!15:23
git-harrybulk set == cell/region variables?15:23
jimbakerso antonym asked us about why no update to the ansible-inventory endpoint15:23
sigmavirusantonym: you need a batch API? do we have a user story for that? I advocated for it early on, but I assume you need it sooner rather than later15:23
*** cwolferh has quit IRC15:24
*** erikmwilson has quit IRC15:24
jimbakersigmavirus, right now it's up to work that story out15:24
jimbakerup to us15:24
*** erikwilson has joined #openstack-meeting-415:24
antonymyeah, ideally if we want to load up all of the information about a host up and keep it updated periodically it would be nice to batch it up15:24
jimbakeror all of the hosts in a given project, that sort of thing15:25
jimbakerwe can update a host in just a couple of ops at this time, it would be straightforward to make this one op if we wanted15:26
*** v1k0d3n has quit IRC15:26
git-harrySo who's going to pick up the spec for this?15:27
jimbakerso i suggested a scheme of a payload that is a list of resources to be updated/set, with json data for each15:27
jimbakergit-harry, might be something you are interesting in working on?15:27
sigmavirusgit-harry: I can since I have some ideas around batch APIs but after pagination work is done15:27
*** v1k0d3n has joined #openstack-meeting-415:27
sigmavirusor thomasem can work on this15:27
jimbakerok, so at least one volunteer. or three15:28
jimbaker:)15:28
thomasemHappy to15:28
jimbakersome stepping up, others being volunteered :)15:28
sigmavirusAs meeting chair, it's my job to voluntell15:28
thomasemOh. Well, either way. It'd be exploratory and educational for me.15:28
jimbakersigmavirus, +115:28
sigmavirus#action git-harry and thomasem should decide who will write the spec15:29
*** garyloug has joined #openstack-meeting-415:29
thomasemHahahaha15:29
sigmavirushashtag helping15:29
*** garyloug has left #openstack-meeting-415:29
thomasemI propose a Sicilian battle of wits.15:30
sigmavirusOkay, with thomasem's blocking review, what else do we have?15:30
sigmavirusthomasem: never go up against a Sicilian when death is on the line15:30
jimbakergit-harry, thomasem, should be straightforward for say PUT. i assume it gets more interested once we bring in pagination and presumably JSON PATCH15:30
thomasemYeah15:30
sigmavirusAlso a batch API will need the ability to check the status since it will be an async create15:31
sigmavirusHaving a response held up while we create 700 devices would be ridiculous15:31
thomasemVery much so15:31
sigmavirus#action sigmavirus to update pagination API work to add functional tests now that sulo's work has landed15:32
jimbakersigmavirus, ahh, interesting detail. we have pushed async out of the craton api server until now15:32
jimbakereg using something like taskflow for workflow support15:32
sigmavirus#action sigmavirus to finish up testing on cli15:32
sigmavirusjimbaker: well the server (especially given how we're "deploying" it in our docker container) will not be able to handle this synchronously15:32
sigmavirusNor would anyone expect a batch API to return anything other than a 20215:33
jimbakersigmavirus, i would assume that no one would deploy the api server as it is in that docker container15:33
*** rbak has joined #openstack-meeting-415:33
jimbakeror Dockerfile setup to be precise15:33
sigmavirusjimbaker: that's a mighty big assumption15:33
thomasemYeah. Actually, when did we want me to start working on, like, docker-compose and such for that?15:33
*** limao has quit IRC15:33
sigmavirusthomasem: that won't belong in craton itself15:33
jimbakersigmavirus, that's why thomasem has been looking at the right deployment scheme15:34
jimbakercode is fine. it's just a matter of proper deployment15:34
git-harrywouldn't that live in openstack-ansible?15:34
sigmavirusgit-harry: so openstack-ansible is going to deploy its own dependency?15:34
thomasemsigmavirus: I had this: https://blueprints.launchpad.net/craton/+spec/docker-compose-dev-environment15:34
jimbakerexactly. it's going to be a recommended setup, maybe using docker compose. but something robust15:34
thomasemas well15:35
jimbakerand no dependency on ansible15:35
jimbakeror at least not OSA15:35
sigmavirusthomasem: if we're only using compose for dev that's fine15:35
git-harrysigmavirus: in terms of the way it's deployed I would expect support to want it consistent.15:35
*** cwolferh has joined #openstack-meeting-415:35
sigmavirusThat said, I'd expect actual priorities to.. y'know.. take priority15:35
thomasemRight15:35
*** klindgren has joined #openstack-meeting-415:35
sigmavirusgit-harry: it's a chicken and egg problem15:36
thomasemAlright, so, if I'm supposed to be looking at deployment schemes, where do we really want to start with that? A spec?15:36
sigmavirusthomasem: production deployment schemes? That should be docs only15:36
git-harrysigmavirus: an OSA role can stand alone so not really.15:37
sigmaviruscraton itself shouldn't also have the code to deploy it, just the documented architecture15:37
*** Liuqing has joined #openstack-meeting-415:37
*** klindgren__ has quit IRC15:37
thomasemsigmavirus: okay, cool. I'll throw together a BP (if one doesn't exist) to address that and get us something to iterate on as a suggested deployment.15:37
suloso whats the priority list again ? I missed what priority items we decided to work on now15:38
sigmavirussulo: I don't think we've decided on much honestly15:38
thomasem#action thomasem to create BP, with initial thoughts, regarding suggested production deployment documentation15:38
sigmavirusWe keep getting bogged down in details15:38
sulolets decide that ... i think that becoming more and more important and pressing15:38
*** cdelatte has joined #openstack-meeting-415:38
jimbaker+10015:38
jimbakercannot go production unless we finalize these details. but15:39
jimbakerwe have a very simple architecture15:39
sigmavirus(Until we add the workflow engine)15:39
jimbakerfrom what needs to be deployed15:39
sigmavirus=P15:39
thomasemhah, yeah. workflow is going to be the meaty part15:39
jimbakersigmavirus, yes, but even then, we have had discussions of simplifying that deployment as well15:40
*** beekneemech is now known as bnemec15:40
thomasemCan anyone point me to this discussion?15:40
*** Liuqing has quit IRC15:40
jimbakerthomasem, over on #craton presumably15:40
jimbakerbut in a nutshell, this is having workers take advantage of containers15:41
sigmavirusSo for *this week*15:41
git-harrythere is a spec15:41
sigmavirusParent/child relation work?15:41
jimbakersulo, want to elaborate15:41
jimbaker?15:41
suloparent/child ?15:41
jimbakerso the schema captures15:42
sigmavirusI'm asking if we want to prioritize that for *this week* (sorry for the ambiguity)15:42
jimbakersigmavirus, it is the highest priority item for this week15:42
suloyes, i am looking at it this week, will create appropriate spec15:42
sigmavirus#info Parent/Child Relationship work is the highest priority work for this week15:42
sigmavirusAfter that then, we have ... what?15:43
sulothe whole thing depends on how involved we want this for networking deivices15:43
sulothats what i am looking at today15:43
jimbakersigmavirus, that would be finishing up the WIP for resource setters we demoed15:43
sulofor devices its pretty simple each device has parent_id15:43
sulobut if we want to draw "cab view"15:43
sulothen it goes into networking devices15:43
jimbakerand then RBAC published as WIP15:43
sigmavirus#info After Parent/Child Relationship work, finishing up resource setters work is the highest priority15:44
sulohow netwoks connect to devices ot interfaces etc15:44
suloanyway will create spec accordingly15:44
jimbakersulo, thanks15:44
*** rbak_ has joined #openstack-meeting-415:44
jimbakereven something simple that shows this working will be helpful for being demoable this week15:44
sigmavirusOkay, then what?15:45
jimbakerin terms of being demoable? it will allow us to better understand the problem, and to see if that would work for toan, antonym, and others15:47
*** rbak has quit IRC15:47
git-harryjimbaker: do you have to give another demo soon?15:47
git-harryis there a deadline you are working towards for these tasks?15:47
sigmavirusjimbaker: I'm talking this week's priorities still15:47
jimbakergit-harry, toan asked for parent/child for this week15:47
sulowait, that just one priority item, what are other items15:48
sigmavirussulo: we have two so far15:48
sigmavirusParent/Child & The setters work from the demo15:48
suloand RBAC ?15:48
sulothere is demo ?15:48
jimbakeryes, but only parent/child is necessary for the week15:48
sigmavirusOkay15:48
sigmavirusSo we're done with priorities then15:48
sigmavirusGreat15:48
jimbakerthat's the only thing we were explicitly asked to do. cool!15:49
sigmavirus#topic Open Discussion15:49
*** openstack changes topic to "Open Discussion (Meeting topic: craton)"15:49
git-harryWe need a better way of tracking this stuff15:49
suloi am not following this ...15:49
sulowhat demo is this now ?15:49
*** galstrom_zzz is now known as galstrom15:49
thomasemBetter way of tracking... priorities? Upcoming demos?15:49
thomasemBoth?15:49
jimbakerhah! just tracking it seems15:49
thomasemYep. Agreed wholeheartedly.15:49
sigmavirussulo: the last demo, jimbaker demo'd some setters work?15:50
jimbakerso farid is joining us tomorrow15:50
thomasemIt's a huge mental burden to try and glean it from re-reading scrollback.15:50
sigmavirusthomasem: that's what meeting minutes are for15:50
git-harrythomasem: everything.15:50
sigmavirusWell we have LaunchPad for blueprints/bugs that people don't use consistently for tracking that information15:50
sigmavirusWe have Gerrit for tracking in progress reviews15:51
thomasemI suppose I meant more for the state of things point-in-time.15:51
sulook let me suggest, we track this priority items somewhere, i prefer LP .. one palce for all things15:51
sigmavirusWe don't have much for tracking what is a priority though besides the meeting minutes15:51
git-harrysigmavirus: non of that tracks Rackspace priorities/deadlines etc15:51
jimbakerfarid will be working as the dev manager for the project, to help do things like rollups, and make sure that everyone has the info they need15:51
sigmavirusgit-harry: this is an OpenStack project. Rackspace priorities should be tracked elsewhere15:51
git-harrysigmavirus: agreed, but given the way we are currently blurring that boundary I'm raising it here.15:52
jimbakerit's good to track what our users expect15:53
jimbakerrackspace, nokia, whomever15:53
git-harryour users are Rackspace15:53
sigmavirusAnd presently the only people we have who are bold enough to call themselves users are Rackspace15:53
git-harryeveryone here works for Rackspace15:54
sigmavirusgit-harry: other organizations have expressed interest15:54
git-harrysigmavirus: sure but we're not making that distinction15:54
jimbakeryes, and so if we start with a user-centered focus, we are good15:54
git-harrysigmavirus: all the talk about demos, priorities etc relates to Rackspace15:54
sigmavirusgit-harry: well we're also not making it easy for them to collaborate15:54
jimbakergit-harry, demos for rackspace only came up recently. but since they are users, there's no conflict15:55
jimbakereverything we have been asked to do, we have already intended to work on15:56
jimbakerit's just a question of how our users have helped us with prioritization, that's all15:56
jimbakerand better understanding the problem15:56
jimbakeri see no conflict here15:57
sigmavirusjimbaker: git-harry isn't claiming conflict, he's claiming we should call this "Rackspace Craton" not "OpenStack Craton"15:57
sigmavirus(if I understand correctly)15:58
git-harryyes15:58
*** lakerzhou has quit IRC15:58
jimbakeri hope we can ensure it's openstack craton. that's certainly our mission here15:58
jimbakeri heard that repeatedly stressed from all stakeholders in rackspace, fwiw15:59
jimbakerbut it's up to us to deliver! :)15:59
git-harryIt's not that Rackspace shouldn't be represented it just seems that we are using OpenStack systems to manage the Rackspace side of it.15:59
*** hongbin has joined #openstack-meeting-415:59
jimbakerlet's move this discussion over to #craton15:59
jimbaker#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Feb  6 15:59:53 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
sigmavirusYeah, we're out of time15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-06-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-06-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-06-15.00.log.html16:00
*** git-harry has left #openstack-meeting-416:00
*** h37 has quit IRC16:05
*** Syed__ has joined #openstack-meeting-416:10
*** Julien-zte has quit IRC16:11
*** Julien-zte has joined #openstack-meeting-416:12
*** armax has joined #openstack-meeting-416:12
*** sacharya has joined #openstack-meeting-416:12
*** Julien-zte has quit IRC16:12
*** Julien-zte has joined #openstack-meeting-416:13
*** Julien-zte has quit IRC16:13
*** Julien-zte has joined #openstack-meeting-416:14
*** Julien-zte has joined #openstack-meeting-416:16
*** Julien-zte has quit IRC16:16
*** xingchao has joined #openstack-meeting-416:24
*** armax has quit IRC16:25
*** klindgren_ has joined #openstack-meeting-416:29
*** tonytan4ever has joined #openstack-meeting-416:31
*** klindgren has quit IRC16:32
*** unicell has quit IRC16:32
*** limao has joined #openstack-meeting-416:34
*** baoli has joined #openstack-meeting-416:35
*** salv-orlando has joined #openstack-meeting-416:36
*** iyamahat has quit IRC16:38
*** iyamahat has joined #openstack-meeting-416:38
*** pcaruana has quit IRC16:38
*** uck has joined #openstack-meeting-416:38
*** limao has quit IRC16:39
*** xingchao has quit IRC16:41
*** cwolferh has quit IRC16:45
*** joedborg has quit IRC16:51
*** baoli has quit IRC16:56
cargonzao/16:58
thedaco/16:59
cargonzawill wait for a few mins. before I start the meeting...16:59
beisnero/17:01
wolseno/17:01
*** rwallner has quit IRC17:01
cargonzalets start17:01
cargonza#startmeeting charms17:01
openstackMeeting started Mon Feb  6 17:01:45 2017 UTC and is due to finish in 60 minutes.  The chair is cargonza. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: charms)"17:01
openstackThe meeting name has been set to 'charms'17:01
iceyo/17:02
*** rwallner has joined #openstack-meeting-417:02
cargonza#topic: Review ACTIONS points from previous meeting..17:02
*** openstack changes topic to ": Review ACTIONS points from previous meeting.. (Meeting topic: charms)"17:02
cargonza#action: jamespage talk py27 retirement with TC as PTL17:03
cargonza#subtopic: jamespage talk py27 retirement with TC as PTL17:03
cargonzaanyone have an update?17:03
thedacWe have people at FOSDEM/cfgmgmtcamp so we are likely to miss updates on some of these.17:04
*** armax has joined #openstack-meeting-417:04
cargonzaok... lets move on then...17:04
*** cwolferh has joined #openstack-meeting-417:04
cargonza#subtopic: cholcombe close bugs against ceph-fs17:04
cargonzacholcombe, any update?17:04
*** cholcombe has joined #openstack-meeting-417:06
cholcombeo/17:06
*** rwallner has quit IRC17:06
*** jovon has joined #openstack-meeting-417:06
cholcombecephfs-update you're waiting on?17:06
cargonzaack17:07
cholcombewell we have amulet tests on it17:07
cholcombethey're passing they've landed17:07
beisnercholcombe, reminder: need to go through this, confirm each is fix-committed, and update the bugs accordingly: https://bugs.launchpad.net/charm-ceph-fs17:07
cholcombebeisner, ack17:07
cholcombeyeah there's one last thing where the layer needs to be moved under openstack17:08
*** Swami has joined #openstack-meeting-417:08
cargonza#action: cholcombe to review https://bugs.launchpad.net/charm-ceph-fs and provide update for each item.17:08
cholcombewill do17:08
beisnercholcombe, that'll need to be proposed ASAP in order for ceph-fs to make the freeze/release cut.17:08
cholcombebeisner, ok i'll start on it today17:08
cargonzacholcombe: who do you need to help you to move the layer under open stack?17:09
cholcombecargonza, nobody. i just need to propose the goverance and project change17:09
cargonzaok17:09
cholcombesame exact thing the gluster charm is going through17:09
cargonzaok17:09
cargonzaanything else?17:09
cholcombei'll look through those bug reports17:10
cargonzak thx17:10
cargonzalets move on...17:10
cargonza#subtopic: jamespage to send out ether pad link to list for charms planning for mon/tues of PTG week.17:10
cargonzaI think this is done...17:11
cargonzalooking for the link17:11
*** dims has quit IRC17:11
cargonzahttps://etherpad.openstack.org/p/openstack-charms-ptg-pike17:12
cargonzalets move on...17:12
cargonza#subtopic: all- brainstorm PTG schedule and objectives17:12
cargonzaany thoughts?17:13
thedacI added the openstack-loadbalancer17:13
thedaccontinued discussion ^^17:13
cargonzathx thedac17:13
cargonzaall - please update the ether pad for topics to discuss... thx...17:14
cargonzalets move on if nothing else...17:14
beisnerwe will need to overcome the bundle vs. juju deploy vs. juju-deployer issues.  i anticipate further convo needed there.17:14
*** klindgren has joined #openstack-meeting-417:14
cargonzaplease add it to the etherpad beisner...17:14
cargonzathx!17:14
beisneryep will do cargonza17:14
cargonza#topic: STATE of Charm Development & Release17:15
*** openstack changes topic to ": STATE of Charm Development & Release (Meeting topic: charms)"17:15
thedacFeature freeze this Thur, 2017-02-09, @EOB and 17.02 release on 2017-02-2317:15
*** klindgren_ has quit IRC17:15
cargonzayup!17:15
cargonzaif there is nothing else, lets move on...17:16
beisnerfyi, i'll circulate a 17.02 release checklist later this wk, as in the past.17:17
*** jose-phillips has joined #openstack-meeting-417:17
cargonzaok17:17
cargonzanext topic...17:17
cargonza#topic: High Priority Bugs -  https://bugs.launchpad.net/openstack-charms17:17
*** openstack changes topic to ": High Priority Bugs - https://bugs.launchpad.net/openstack-charms (Meeting topic: charms)"17:17
*** dims has joined #openstack-meeting-417:18
cargonzaany insights? bug triage and fix should ramp up more after the 2/9, correct?17:19
beisnergenerally only crit bugs get attention during freeze, correct?17:19
beisnerwe just need to make sure that those are appropriately triaged.17:19
thedacCritical bug list  http://j.tinyurl.com/jdn5hbv17:20
cargonzaack..17:20
*** psachin has quit IRC17:20
*** harlowja has joined #openstack-meeting-417:20
cargonzaok lets move on -- we got a plan for critical bugs...17:21
beisnerhmm, thedac cargonza - that last link misses the new charms that aren't under juju charms collection LP project17:21
cargonza#topic: Openstack Events17:21
*** openstack changes topic to ": Openstack Events (Meeting topic: charms)"17:21
cargonzabeisner, ack... lets correct it.17:22
thedacbeisner: you are right. We need a second link as it is a different LP project17:22
beisneryep we do17:22
*** bdx has joined #openstack-meeting-417:22
thedacopenstack-charms project version: http://j.tinyurl.com/zycpvyv17:23
cargonzaok... thx... move on?17:23
thedacyes17:23
beisnerwoot thx thedac17:23
cargonza#topic: Openstack Events Part 217:23
*** openstack changes topic to ": Openstack Events Part 2 (Meeting topic: charms)"17:23
cargonzaCharmer Summit is happening at the moment...17:24
beisnerthedac, cargonza, cholcombe - i'll elevate any release blockers in that ceph-fs list to crit for the purpose of tracking the release work17:24
cholcombebeisner, ok17:24
cargonzaPTG project planned on 2/20 to 2/2417:24
cholcombebeisner, there's a ipv6 bug that i need to solve17:25
thedac#link https://www.openstack.org/ptg/17:25
cargonzaany other events?17:25
beisnerconfig mgmt camp underway right now :)17:26
*** uck has quit IRC17:26
beisnerbut i think we already covered that17:27
*** uck has joined #openstack-meeting-417:27
cargonzaok. lets move on...17:27
cargonza#topic Open Discussion17:27
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:27
cargonzaanyone have new or old topics to discuss?17:28
bdxhey, hows it going all? just wondering, is there any work being done to enable nova-lxd to use a ceph based backend?17:28
cargonzabdx, ack there is...17:28
cargonzaworking it in the 17.04 release17:28
bdxcargonza: thats awesome! mind sharing some high level details of how that will happen?17:29
cargonzaI don't have the info at the moment. rockstar is currently working the design.17:30
bdxnice, thx17:31
cargonzaI'll see if rockstar can reach out to you or I will have some info later in the week... I'll reach out to you directly...17:31
cargonzait would be good to see if you have a use case we need to consider also.17:32
cargonzaany other items to discuss?17:32
cargonzaok. then... lets end the meeting17:33
cargonzathx all!17:33
cargonzanext chair is tinwood17:33
beisnerthx cargonza17:33
cargonzaon 2/2017:33
thedacthanks, cargonza17:33
cargonza#endmeeting17:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:33
openstackMeeting ended Mon Feb  6 17:33:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-02-06-17.01.html17:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-02-06-17.01.txt17:33
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-02-06-17.01.log.html17:33
*** spzala has quit IRC17:39
*** rwallner has joined #openstack-meeting-417:39
*** baoli has joined #openstack-meeting-417:43
*** uck has quit IRC17:45
*** reedip_ has left #openstack-meeting-417:47
*** rwallner has quit IRC17:47
*** harlowja has quit IRC17:49
*** klindgren has left #openstack-meeting-417:50
*** rwallner has joined #openstack-meeting-417:51
*** portdirect_away is now known as portdirect17:52
*** iyamahat has quit IRC17:55
*** ralonsoh has quit IRC17:56
*** yamahata has quit IRC17:56
*** rwallner has quit IRC17:59
*** tonytan4ever has quit IRC18:04
*** tonytan4ever has joined #openstack-meeting-418:04
*** unicell has joined #openstack-meeting-418:07
*** spzala has joined #openstack-meeting-418:08
*** sambetts is now known as sambetts|afk18:11
*** anilvenkata has joined #openstack-meeting-418:13
*** iyamahat has joined #openstack-meeting-418:24
*** iyamahat has quit IRC18:32
*** iyamahat has joined #openstack-meeting-418:32
*** anilvenkata has quit IRC18:33
*** pcaruana has joined #openstack-meeting-418:36
*** nkrinner is now known as nkrinner_afk18:40
*** rwallner has joined #openstack-meeting-418:42
*** harlowja has joined #openstack-meeting-418:44
*** rbak_ has quit IRC18:45
*** yamahata has joined #openstack-meeting-418:45
*** uck has joined #openstack-meeting-418:46
*** uck has quit IRC18:50
*** galstrom is now known as galstrom_zzz18:52
*** dharinic is now known as dharinic|lunch18:52
*** sambetts|afk has quit IRC18:55
*** sambetts_ has joined #openstack-meeting-418:56
*** degorenko has quit IRC19:01
*** sdague has quit IRC19:07
*** degorenko has joined #openstack-meeting-419:07
*** pcaruana has quit IRC19:11
*** s3wong has joined #openstack-meeting-419:15
*** mfedosin has quit IRC19:17
*** rbak has joined #openstack-meeting-419:22
*** rbak has quit IRC19:23
*** numans has quit IRC19:24
*** rbak has joined #openstack-meeting-419:24
*** salv-orlando has quit IRC19:25
*** numans has joined #openstack-meeting-419:25
*** kberger has joined #openstack-meeting-419:37
*** kberger has quit IRC19:37
*** kberger has joined #openstack-meeting-419:38
*** vishnoianil has quit IRC19:39
*** dharinic|lunch is now known as dharinic19:43
*** mfedosin has joined #openstack-meeting-419:43
*** jovon has quit IRC19:50
*** galstrom_zzz is now known as galstrom20:03
*** dtardivel has quit IRC20:04
*** david-lyle has joined #openstack-meeting-420:16
*** sdague has joined #openstack-meeting-420:17
*** yfauser has quit IRC20:19
*** yfauser has joined #openstack-meeting-420:19
*** yfauser has quit IRC20:24
*** salv-orlando has joined #openstack-meeting-420:25
*** rfolco has quit IRC20:30
*** vishnoianil has joined #openstack-meeting-420:30
*** _ody has joined #openstack-meeting-420:34
* _ody really needs to get znc on auto launch20:34
_odyww20:34
*** _ody has left #openstack-meeting-420:34
*** MeganR has joined #openstack-meeting-420:35
*** salv-orlando has quit IRC20:36
*** salv-orlando has joined #openstack-meeting-420:37
*** matrohon has joined #openstack-meeting-420:44
*** Jeffrey4l has joined #openstack-meeting-420:44
*** rfolco has joined #openstack-meeting-420:46
*** rfolco has quit IRC20:46
*** cdelatte has quit IRC20:46
*** Rockyg has joined #openstack-meeting-420:47
*** Jeffrey4l has quit IRC20:49
*** Jeffrey4l has joined #openstack-meeting-420:51
*** Jeffrey4l has quit IRC20:55
*** numans has quit IRC20:56
*** Jeffrey4l has joined #openstack-meeting-420:56
*** Jeffrey4l has quit IRC20:57
*** Jeffrey4l has joined #openstack-meeting-420:58
*** david-lyle has quit IRC21:02
*** hoangcx has joined #openstack-meeting-421:02
*** Jeffrey4l has quit IRC21:03
*** numans has joined #openstack-meeting-421:03
*** rwallner has quit IRC21:03
*** rwallner has joined #openstack-meeting-421:06
*** Jeffrey4l has joined #openstack-meeting-421:06
*** yamamoto has joined #openstack-meeting-421:06
*** rwallner_ has joined #openstack-meeting-421:07
*** rwallner has quit IRC21:10
*** Jeffrey4l has quit IRC21:11
*** rwallner_ has quit IRC21:11
*** julim has quit IRC21:12
*** yamamoto has quit IRC21:14
*** jovon has joined #openstack-meeting-421:14
*** hoangcx_ has joined #openstack-meeting-421:16
*** markvoelker has joined #openstack-meeting-421:17
*** hoangcx has quit IRC21:17
*** yamamoto has joined #openstack-meeting-421:17
*** markvoelker_ has quit IRC21:18
*** hoangcx_ is now known as hoangcx21:18
*** Jeffrey4l has joined #openstack-meeting-421:18
*** galstrom is now known as galstrom_zzz21:19
*** markvoelker_ has joined #openstack-meeting-421:19
*** yfauser has joined #openstack-meeting-421:20
*** cleong has quit IRC21:21
*** markvoelker has quit IRC21:22
*** yfauser has quit IRC21:24
*** david-lyle has joined #openstack-meeting-421:27
*** Jeffrey4l has quit IRC21:28
*** yamamoto has quit IRC21:29
*** yfauser has joined #openstack-meeting-421:29
*** yfauser has quit IRC21:34
*** Jeffrey4l has joined #openstack-meeting-421:36
*** sdague_ has joined #openstack-meeting-421:41
*** uck has joined #openstack-meeting-421:48
*** uck has quit IRC21:52
*** Swami has quit IRC21:54
*** thorst_ has quit IRC21:57
*** rwallner has joined #openstack-meeting-422:02
*** MeganR has quit IRC22:02
*** hoangcx has quit IRC22:03
*** rwallner has quit IRC22:06
*** mfedosin has quit IRC22:09
*** matrohon has quit IRC22:10
*** yamamoto has joined #openstack-meeting-422:11
*** Rockyg has quit IRC22:12
*** thorst_ has joined #openstack-meeting-422:17
*** thorst_ has quit IRC22:22
*** yfauser has joined #openstack-meeting-422:30
*** galstrom_zzz is now known as galstrom22:31
*** mjturek has quit IRC22:35
*** yfauser_ has joined #openstack-meeting-422:36
*** baoli has quit IRC22:36
*** yfauser has quit IRC22:38
*** tonytan4ever has quit IRC22:38
*** yfauser_ has quit IRC22:40
*** kylek3h_away has quit IRC22:50
*** galstrom is now known as galstrom_zzz22:51
*** sacharya_ has joined #openstack-meeting-422:51
*** cdelatte has joined #openstack-meeting-422:53
*** sacharya_ has quit IRC22:54
*** sacharya has quit IRC22:54
*** sacharya has joined #openstack-meeting-422:54
*** cdelatte has quit IRC22:55
*** uck has joined #openstack-meeting-422:56
*** rockyg has joined #openstack-meeting-422:57
*** rbak has quit IRC22:59
*** sacharya has quit IRC23:00
*** sacharya has joined #openstack-meeting-423:02
*** sacharya has quit IRC23:06
*** thorst_ has joined #openstack-meeting-423:10
*** rockyg has quit IRC23:14
*** spzala has quit IRC23:17
*** thorst_ has quit IRC23:19
*** hongbin_ has joined #openstack-meeting-423:25
*** salv-orl_ has joined #openstack-meeting-423:26
*** unicell1 has joined #openstack-meeting-423:26
*** igormarnat__ has joined #openstack-meeting-423:27
*** ildikov_ has joined #openstack-meeting-423:27
*** kozhukalov_ has joined #openstack-meeting-423:27
*** mchiappe1o has joined #openstack-meeting-423:27
*** Dmitrii-Sh_ has joined #openstack-meeting-423:27
*** dasanind_ has joined #openstack-meeting-423:27
*** nikhil_ has joined #openstack-meeting-423:27
*** nikhil_ is now known as Guest449123:27
*** wolsen_ has joined #openstack-meeting-423:28
*** sulo_ has joined #openstack-meeting-423:28
*** chigang__ has joined #openstack-meeting-423:28
*** cargonza_ has joined #openstack-meeting-423:28
*** zerick_ has joined #openstack-meeting-423:29
*** harmw_ has joined #openstack-meeting-423:29
*** dosaboy_ has joined #openstack-meeting-423:30
*** sdague has quit IRC23:30
*** johnsom_ has joined #openstack-meeting-423:31
*** sballe__ has joined #openstack-meeting-423:31
*** jwagner- has joined #openstack-meeting-423:32
*** tdurakov_ has joined #openstack-meeting-423:32
*** lihi- has joined #openstack-meeting-423:32
*** electrichead has joined #openstack-meeting-423:32
*** yantarou_ has joined #openstack-meeting-423:33
*** mmedvede_ has joined #openstack-meeting-423:33
*** shaohe_feng_ has joined #openstack-meeting-423:33
*** ddellav_ has joined #openstack-meeting-423:33
*** salv-orlando has quit IRC23:34
*** unicell has quit IRC23:34
*** hongbin has quit IRC23:34
*** neiljerram has quit IRC23:34
*** lihi has quit IRC23:34
*** shaohe_feng has quit IRC23:34
*** jwagner has quit IRC23:34
*** mordred has quit IRC23:34
*** ddellav has quit IRC23:34
*** mchiappero has quit IRC23:34
*** Dmitrii-Sh has quit IRC23:34
*** harmw has quit IRC23:34
*** dosaboy has quit IRC23:34
*** chigang has quit IRC23:34
*** bcafarel has quit IRC23:34
*** johnsom has quit IRC23:34
*** igormarnat_ has quit IRC23:34
*** nikhil has quit IRC23:34
*** xgerman has quit IRC23:34
*** ildikov has quit IRC23:34
*** zerick has quit IRC23:34
*** syjulian has quit IRC23:34
*** mmedvede has quit IRC23:34
*** redrobot has quit IRC23:34
*** tdurakov has quit IRC23:34
*** kozhukalov has quit IRC23:34
*** cargonza has quit IRC23:34
*** sballe_ has quit IRC23:34
*** dasanind has quit IRC23:34
*** sulo has quit IRC23:34
*** yantarou has quit IRC23:34
*** wolsen has quit IRC23:34
*** shaohe_feng_ is now known as shaohe_feng23:34
*** lihi- is now known as lihi23:34
*** yantarou_ is now known as yantarou23:34
*** igormarnat__ is now known as igormarnat_23:35
*** mmedvede_ is now known as mmedvede23:35
*** Dmitrii-Sh_ is now known as Dmitrii-Sh23:35
*** dasanind_ is now known as dasanind23:35
*** chigang__ is now known as chigang23:36
*** ildikov_ is now known as ildikov23:36
*** kozhukalov_ is now known as kozhukalov23:36
*** wolsen_ is now known as wolsen23:36
*** Guest4491 is now known as nikhil23:36
*** syjulian has joined #openstack-meeting-423:36
*** sballe__ is now known as sballe_23:36
*** cargonza_ is now known as cargonza23:37
*** yfauser has joined #openstack-meeting-423:37
*** tdurakov_ is now known as tdurakov23:37
*** johnsom_ is now known as johnsom23:37
*** sdake has quit IRC23:39
*** mordred has joined #openstack-meeting-423:40
*** neiljerram has joined #openstack-meeting-423:40
*** bcafarel has joined #openstack-meeting-423:41
*** yfauser has quit IRC23:41
*** Prem_ has joined #openstack-meeting-423:42
*** uck has quit IRC23:47
*** uck has joined #openstack-meeting-423:48

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