Wednesday, 2018-04-18

*** annabelleB has quit IRC00:02
*** yamamoto has joined #openstack-meeting00:03
*** yamamoto has quit IRC00:07
*** mjturek has quit IRC00:13
*** fnaval has joined #openstack-meeting00:20
*** fnaval has quit IRC00:20
*** liusheng has quit IRC00:20
*** fnaval has joined #openstack-meeting00:20
*** liusheng has joined #openstack-meeting00:21
*** Tom-Tom has joined #openstack-meeting00:22
*** yamahata has quit IRC00:23
*** yamamoto has joined #openstack-meeting00:24
*** Yipei has joined #openstack-meeting00:25
*** iyamahat has quit IRC00:25
*** Yipei has quit IRC00:26
*** hoangcx_ has quit IRC00:26
*** Tom-Tom has quit IRC00:27
*** yamamoto has quit IRC00:29
*** lhx_ has joined #openstack-meeting00:29
*** song has joined #openstack-meeting00:31
*** Yipei has joined #openstack-meeting00:31
*** Tom-Tom has joined #openstack-meeting00:31
*** Tom-Tom has quit IRC00:36
*** bobh has joined #openstack-meeting00:37
*** markmcclain has quit IRC00:44
*** yamamoto has joined #openstack-meeting00:44
*** zhiyuan has joined #openstack-meeting00:46
*** markmcclain has joined #openstack-meeting00:49
*** yamamoto has quit IRC00:51
*** xuzhuang has joined #openstack-meeting00:57
zhiyuan#startmeeting tricircle00:59
openstackMeeting started Wed Apr 18 00:59:27 2018 UTC and is due to finish in 60 minutes.  The chair is zhiyuan. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:59
*** openstack changes topic to " (Meeting topic: tricircle)"00:59
openstackThe meeting name has been set to 'tricircle'00:59
*** zhujintao has joined #openstack-meeting00:59
zhiyuanYipei, have you done some tests on the routed network gateway solution we discussed last week?01:00
*** liuzz has joined #openstack-meeting01:01
Yipeinot jet, i am working on it.01:01
Yipeitrying to create a blank port when adding gateway port when updating the router01:02
*** salv-orlando has joined #openstack-meeting01:02
Yipeithen, i think i also need to test the floating ip creation01:03
*** fzdarsky_ has joined #openstack-meeting01:03
*** dmacpher has joined #openstack-meeting01:04
*** yamahata has joined #openstack-meeting01:04
zhiyuanyeah, the default fip creation will allocate ip from the external subnet so we need to change01:04
*** salv-orl_ has quit IRC01:04
*** cyg has joined #openstack-meeting01:05
Yipeiok, got it, i will speed up, i can spend more time on the feature in the next two month01:06
*** dmsimard is now known as dmsimard|off01:06
Yipeimy personal business has come to an end recently01:06
*** fzdarsky|afk has quit IRC01:07
*** yamamoto has joined #openstack-meeting01:07
*** fzdarsky_ has quit IRC01:07
*** zxh has joined #openstack-meeting01:07
*** bobh has quit IRC01:09
*** bobh has joined #openstack-meeting01:09
zhiyuansong, what about the "local resource name" feature?01:11
*** fzdarsky_ has joined #openstack-meeting01:11
songhi,zhiyuan.for this pb use top_name plus top_id to set the name of bottom we just only need to check in the tricircle cli whether the top_id is equal to top_name and nothing more need to do.01:12
*** yamamoto has quit IRC01:12
*** bobh has quit IRC01:14
*** harlowja has quit IRC01:16
zhiyuancurrently for some resources like network and subnet, the name of local resource is the ID of central resource, we need to (1) use name+ID to set the local resource name (2) change the local resource query filter from "ID as name" to "name+ID as name"01:17
zhiyuanyou can see in the function that we are listing resource with filter: key: name, value: ele_['id']01:19
*** beekhof has joined #openstack-meeting01:20
songoh, got it. thank you!do this change may have big effect in our test?01:21
*** markstur has quit IRC01:21
zhiyuansmoke test needs some changes, in the "check" task set, we query some local resources by their name as central resource ID: name: preparation@router@id01:26
zhiyuanbut not all the resources01:26
songoh, that is good.01:27
*** yamamoto has joined #openstack-meeting01:28
zhiyuanfor unit tests, it will be fine if the helper "FakeClass" in tricircle/tests/unit/ is used. the query filter is not hard-coded in the "FakeClass" so I think no effect after we change the name from "ID" to "name+ID"01:30
*** bobh has joined #openstack-meeting01:31
*** yamamoto has quit IRC01:32
songit is really a good news.we plan to finish the code this week and see how much effect to the smoke test.01:33
*** janki has joined #openstack-meeting01:33
*** blair has quit IRC01:36
*** jamesmcarthur has joined #openstack-meeting01:36
zhiyuanoh, our task runner also need some changes. currently it doesn't support expression in yaml file, so you cannot define the filter in yaml like "name: router@id + router@name"01:38
*** Tom-Tom has joined #openstack-meeting01:38
*** hongbin_ has joined #openstack-meeting01:40
songso the task runner will need to add filer in yaml for this it!01:40
*** salv-orlando has quit IRC01:41
*** salv-orlando has joined #openstack-meeting01:42
zhiyuanenable task runner to process expression so we can pass like "name: router@id+router@name" or "name: concat(router@id, router@name)" in yaml01:43
*** bobh has quit IRC01:43
*** blair has joined #openstack-meeting01:44
songok, that is no problem.we will use a general method not hard code with it.:)01:46
zhiyuanfine :)01:47
zhiyuanother topics?01:47
xuzhuangno from me01:48
Yipeino for me01:48
songon for me01:48
songno for me01:48
*** openstack changes topic to "OpenStack Meetings ||"01:48
openstackMeeting ended Wed Apr 18 01:48:40 2018 UTC.  Information about MeetBot at . (v 0.1.4)01:48
openstackMinutes (text):
*** xuzhuang has quit IRC01:49
*** yamamoto has joined #openstack-meeting01:49
*** zhiyuan has quit IRC01:49
*** jamesmcarthur has quit IRC01:50
*** slaweq has joined #openstack-meeting01:50
*** Yipei has quit IRC01:53
*** armax has quit IRC01:54
*** slaweq has quit IRC01:55
*** yamamoto has quit IRC01:55
*** ianychoi_ is now known as ianychoi01:57
*** Tom-Tom has quit IRC01:58
*** lhx_ has quit IRC01:58
*** ekcs has quit IRC01:59
*** song has quit IRC02:00
*** salv-orl_ has joined #openstack-meeting02:00
*** salv-orlando has quit IRC02:03
*** Nel1x has quit IRC02:11
*** yamamoto has joined #openstack-meeting02:12
*** yamamoto has quit IRC02:17
*** Tom-Tom has joined #openstack-meeting02:18
*** cyg has quit IRC02:18
*** Tom-Tom has quit IRC02:18
*** Tom-Tom has joined #openstack-meeting02:18
*** Nel1x has joined #openstack-meeting02:29
*** dklyle has joined #openstack-meeting02:31
*** yamamoto has joined #openstack-meeting02:32
*** artom_ has joined #openstack-meeting02:34
*** lkwan has joined #openstack-meeting02:34
*** artom_ has quit IRC02:34
*** artom_ has joined #openstack-meeting02:35
*** artom has quit IRC02:36
*** yamamoto has quit IRC02:39
*** ianychoi has quit IRC02:44
*** psachin has joined #openstack-meeting02:48
*** jchhatbar has joined #openstack-meeting02:51
*** janki has quit IRC02:53
*** ricolin has joined #openstack-meeting02:53
*** yamamoto has joined #openstack-meeting02:55
*** VW has joined #openstack-meeting02:59
*** yamamoto has quit IRC03:00
*** kaisers has joined #openstack-meeting03:05
*** kaisers has quit IRC03:10
*** yamamoto has joined #openstack-meeting03:16
*** epico has joined #openstack-meeting03:16
*** ianychoi has joined #openstack-meeting03:20
*** yamamoto has quit IRC03:21
*** fnaval has quit IRC03:21
*** fnaval has joined #openstack-meeting03:25
*** yamamoto has joined #openstack-meeting03:37
*** lpetrut_ has joined #openstack-meeting03:41
*** harlowja has joined #openstack-meeting03:43
*** yamamoto has quit IRC03:43
*** markstur_ has joined #openstack-meeting03:44
*** VW has quit IRC03:46
*** armax has joined #openstack-meeting03:50
*** jamesmcarthur has joined #openstack-meeting03:50
*** slaweq has joined #openstack-meeting03:51
*** lkwan has quit IRC03:54
*** jamesmcarthur has quit IRC03:54
*** slaweq has quit IRC03:56
*** yamamoto has joined #openstack-meeting04:00
*** salv-orl_ has quit IRC04:04
*** yamamoto has quit IRC04:04
*** salv-orlando has joined #openstack-meeting04:04
*** hongbin_ has quit IRC04:07
*** harlowja has quit IRC04:12
*** lpetrut_ has quit IRC04:13
*** lpetrut_ has joined #openstack-meeting04:19
*** gyee has quit IRC04:20
*** yamamoto has joined #openstack-meeting04:21
*** kaisers has joined #openstack-meeting04:22
*** kaisers has quit IRC04:23
*** kaisers has joined #openstack-meeting04:23
*** yamamoto has quit IRC04:25
*** kaisers has quit IRC04:27
*** yamamoto has joined #openstack-meeting04:41
*** lpetrut_ has quit IRC04:44
*** yamamoto has quit IRC04:48
*** yamamoto has joined #openstack-meeting04:48
*** fnaval has quit IRC04:50
*** aeng has joined #openstack-meeting04:51
*** claudiub|2 has joined #openstack-meeting04:51
*** jchhatbar has quit IRC04:59
*** kaisers has joined #openstack-meeting04:59
*** jchhatbar has joined #openstack-meeting05:00
*** jchhatbar has quit IRC05:01
*** jchhatbar has joined #openstack-meeting05:01
*** jchhatbar has quit IRC05:02
*** jchhatbar has joined #openstack-meeting05:03
*** pcaruana has joined #openstack-meeting05:05
*** anilvenkata has joined #openstack-meeting05:09
*** markstur_ has quit IRC05:18
*** pcaruana has quit IRC05:19
*** lpetrut_ has joined #openstack-meeting05:23
*** sridharg has joined #openstack-meeting05:23
*** bkopilov has quit IRC05:24
*** armax has quit IRC05:25
*** Alex_Staf has joined #openstack-meeting05:27
*** kaz has joined #openstack-meeting05:32
*** armax has joined #openstack-meeting05:34
*** lpetrut_ has quit IRC05:35
*** zhurong has joined #openstack-meeting05:36
*** krtaylor has quit IRC05:37
*** e0ne has joined #openstack-meeting05:42
*** marios has joined #openstack-meeting05:46
*** krtaylor has joined #openstack-meeting05:50
*** kaz has quit IRC06:06
*** lhx_ has joined #openstack-meeting06:08
*** ykatabam has quit IRC06:09
*** sidx64 has joined #openstack-meeting06:11
*** psachin has quit IRC06:11
*** Tom-Tom_ has joined #openstack-meeting06:13
*** Tom-Tom has quit IRC06:16
*** gmann has quit IRC06:21
*** kambiz has quit IRC06:23
*** lpetrut has joined #openstack-meeting06:26
*** kambiz has joined #openstack-meeting06:26
*** jchhatba_ has joined #openstack-meeting06:30
*** e0ne has quit IRC06:31
*** dklyle has quit IRC06:32
*** dklyle has joined #openstack-meeting06:32
*** jchhatbar has quit IRC06:33
*** sidx64_ has joined #openstack-meeting06:38
*** dmacpher has quit IRC06:38
*** ykatabam has joined #openstack-meeting06:40
*** sidx64 has quit IRC06:40
*** sidx64 has joined #openstack-meeting06:42
*** ildikov has joined #openstack-meeting06:43
*** jchhatba_ is now known as janki06:44
*** sidx64_ has quit IRC06:44
*** mordred has quit IRC06:45
*** links has joined #openstack-meeting06:46
*** dklyle has quit IRC06:47
*** mordred has joined #openstack-meeting06:48
*** pcaruana has joined #openstack-meeting06:50
*** alexchadin has joined #openstack-meeting06:59
*** rcernin has quit IRC07:00
*** bobmel has joined #openstack-meeting07:09
*** zigo has quit IRC07:11
*** gmann has joined #openstack-meeting07:13
*** zigo has joined #openstack-meeting07:14
*** kopecmartin has joined #openstack-meeting07:15
*** ykatabam has quit IRC07:15
*** links has quit IRC07:29
*** tesseract has joined #openstack-meeting07:29
*** zhurong has quit IRC07:30
*** psachin has joined #openstack-meeting07:33
*** ykatabam has joined #openstack-meeting07:38
*** links has joined #openstack-meeting07:46
*** yamamoto has quit IRC07:49
*** yamamoto has joined #openstack-meeting07:49
*** links has quit IRC07:52
*** sidx64 has quit IRC07:52
*** tssurya has joined #openstack-meeting07:52
*** kaisers_ has joined #openstack-meeting07:53
*** phil has joined #openstack-meeting07:53
*** phil is now known as Guest6714707:54
*** kaisers has quit IRC07:55
*** fzdarsky_ is now known as fzdarsky07:55
*** yamamoto_ has joined #openstack-meeting07:56
*** sidx64 has joined #openstack-meeting08:00
diablo_rojo#startmeeting fc_sig08:00
openstackMeeting started Wed Apr 18 08:00:19 2018 UTC and is due to finish in 60 minutes.  The chair is diablo_rojo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: fc_sig)"08:00
openstackThe meeting name has been set to 'fc_sig'08:00
diablo_rojogmann, mattoliverau, cmurphy08:00
diablo_rojocmurphy, hello :)08:00
cmurphysorry i missed last week, was on vacation08:00
*** yamamoto has quit IRC08:00
diablo_rojocmurphy, no problem :) Go somewhere fun?08:00
*** radeks has joined #openstack-meeting08:01
cmurphydiablo_rojo: yes! I went to Iceland08:01
diablo_rojocmurphy, OH MAN thats awesome!08:01
diablo_rojoFavorite part?08:01
cmurphythe auroras and the giant glacier08:02
diablo_rojoOh yeah I bet the auroras are pretty easy to see there08:02
diablo_rojomattoliverau, said he might be a little late so we can give him a few minutes to show up before we get started08:04
diablo_rojo#link Today's Agenda08:04
diablo_rojoin case anyone wants to add anything last minute08:04
mattoliveraumake it08:05
*** sidx64 has quit IRC08:05
mattoliveraumade it08:05
mattoliverautho apparently I can't type08:05
mattoliveraudiablo_rojo: you can stop watching youtube now :P08:06
diablo_rojomattoliverau, wasn't watching this time :P08:06
diablo_rojoSo without further ado, lets get this party started!08:06
diablo_rojo#topic New contributor patches!08:06
*** openstack changes topic to "New contributor patches! (Meeting topic: fc_sig)"08:06
diablo_rojoHave we noticed any areas that we are struggling to get a liaison to help with? I can work on filling out the list again.08:08
mattoliverauI looked.. there wasn't much in the last 7 days at least.08:08
diablo_rojoTempted to send something to the ML and be like I'm signing up PTL's. If you don't want on my list, find another person to delegate.08:08
mattoliverauoh, there are some more from about about 30 mins about now..08:08
gmannyes, no new one and almost old one are with review comments08:08
*** sidx64 has joined #openstack-meeting08:08
*** mugsie has quit IRC08:09
diablo_rojoI feel like we've mostly caught up with things, but I wanted to see if anyone else noticed there were places we had holes and things weren't being covered.08:10
diablo_rojoMaybe we start circling back to the ones that we added other project cores to that still havent gotten attention?08:11
* diablo_rojo is just spitballing08:11
*** electrofelix has joined #openstack-meeting08:11
mattoliverauyeah, anything that doesn't have any votes might be good candidates for a relook, even if old08:11
mattoliverauespecially if we find there still on first patchset08:11
diablo_rojoSimultaneously there are a lot that are just waiting on updates from these new contributors too.08:11
mattoliverauthat kinda looks bad08:11
mattoliverauyeah, I noticed that too08:12
diablo_rojoI suppose if we get super desperate we can email the gerrit email about the patch to see if they aren't working on OpenStack anymore.08:12
mattoliveraubut hopefully there would be a + or - 1 for those08:12
diablo_rojoAnd abandon if they arent.08:12
* diablo_rojo continues to muse aloud08:12
gmanni usually post reply to abandon on gerrit but does not work.08:13
gmannasking them on email is good idea08:13
diablo_rojogmann, yeah I suppose if its older than x months we can just abandon with comments on the patch.08:13
diablo_rojoAnd if its only y months old we can email and check in to see if they need help or have moved on?08:14
diablo_rojoWhat we want to set as x & y as can be up for debate08:14
gmannfirst we message and after week we abandon. that is usually we do in nova and QA08:14
mattoliverauI'll try and find the abandon code I had that would keep track and even email if they looked stale.. I got sidetracked with tags this week.08:14
diablo_rojogmann, oh thats a good system08:14
*** sidx64 has quit IRC08:14
diablo_rojomattoliverau, no worries, that was super helpful08:15
* diablo_rojo hasn't been the most productive in this area lately08:15
diablo_rojoI might be juggling a lot right now lol08:15
mattoliverauwhatever you do, don't burn the cadle from both ends for too long. Don't want you to burn out08:16
diablo_rojoSo what do we want to make the practice? First comment. X weeks/months with no response and email? Y weeks pass after and then we comment again and abandon?08:16
diablo_rojomattoliverau, Just tuesday night/wednesday mornings. The rest of the week I go to bed by like 12 :)08:17
diablo_rojoSo x be 1 month? Or more?08:17
cmurphywe don't necessarily have the power to abandon things, only project cores or the owner can do that08:17
diablo_rojoAnd y be like 1 week?08:17
diablo_rojocmurphy, true08:17
cmurphyand different projects might have different policies on abandoning things08:17
diablo_rojoI guess it only applies to the projects we can touch.08:18
diablo_rojocmurphy, what does keystone do?08:18
mattoliveraumy swift abandoner did something similar. a -1 with no updates for 4 weeks, then it'll automatically email. Then wait 2 more weeks and add them to a list for a human to review (slow to auto abandon)08:18
cmurphydiablo_rojo: if the patch is clearly going no where we abandon after like a year08:18
cmurphywe have some around that are older than that because it's possible they could get picked up again08:18
mattoliverauthat way a core would have to look at the "possibly" abandoned patch.08:18
diablo_rojocmurphy, okay cool so a little more easy going about things.08:19
diablo_rojomattoliverau, makes sense08:19
*** bkopilov has joined #openstack-meeting08:19
*** sambetts|afk is now known as sambetts08:19
diablo_rojoits interesting to see how different each project handles things :)08:19
* mattoliverau can blow dust off the old code and look at changing it to suite our needs... and laugh at how bad my coding was back then :P08:20
diablo_rojoI guess the more important part about this discussion is emailing them and seeing if they need help rather than the abandoning- thats just my need to clean things up coming through again lol08:20
cmurphy++ reaching out is the important part08:21
mattoliverauyeah, I agree. if they're new, we don't want to say.. your only patch might be abandoned.. that's kinda not friendly and scary08:21
diablo_rojomattoliverau, agreed08:21
*** mugsie has joined #openstack-meeting08:21
*** mugsie has quit IRC08:21
*** mugsie has joined #openstack-meeting08:21
diablo_rojoSo maybe nevermind the abandoning part but if we haven't seen any activity in a month we should email (and probably post a comment saying we have done for the sake of organization)08:22
diablo_rojoOh wow an extra '+' :)08:23
cmurphythat was an accident08:23
cmurphybut i'll stand by it08:23
diablo_rojoDang, and here I thought I had said something that awesome08:23
*** slaweq has joined #openstack-meeting08:23
diablo_rojoSo new homework then! Go back over the things you've reviewed with no responses and email people :)08:24
mattoliverauoh cool, if you want to look at my old bad code.. it's on my github:
diablo_rojo#action if a new contributor hasn't uploaded a new patchset or posted a reply comment in >= 1 month, send them an email and see if they need help08:24
* diablo_rojo opens tab for tomorrow08:24
mattoliverauit doesn't actually abandon, just makes a list of things that need follow up.. ie an email has been sent and still no response08:25
diablo_rojoDo we want to come up with some sort of generic template email?08:25
diablo_rojomattoliverau, sounds like what we want to do08:25
* diablo_rojo can add that to her todo list for between now and the next meeting08:25
diablo_rojoIn the meantime, feel free to wing it.08:25
diablo_rojoAnything else on this topic?08:26
gmannand how we list patch that who emailed, to avoid multiple emails  :)08:26
mattoliverauthat's what the tool was for :)08:26
diablo_rojoaction item for you then mattoliverau :)08:27
mattoliverauI'll try setting it up and having a play before next week.08:27
*** ssbarnea_ has joined #openstack-meeting08:27
diablo_rojo#action mattoliverau will try to get his abandon_notifier script up and running for next weeks meeting08:27
diablo_rojoOh! and one last thing- my new storyboard contributor hasn't gotten their first patch merged yet to be the new contrib of the month so..we could probably do someone else in the meantime08:28
mattoliverau...and maybe change it's name :)08:28
*** lhx_ has quit IRC08:28
diablo_rojomattoliverau, that too :)08:28
*** lhx_ has joined #openstack-meeting08:28
diablo_rojoNext topic?08:30
mattoliverauWell I don't have anyone in mind, so yours might just have to be _next_ months contributor of the month :)08:30
diablo_rojoWorks for me08:30
mattoliverauwe did say it didn't have to be every month08:30
mattoliveraubut if I see anyone I'll ping y'all08:30
diablo_rojoI remember that discussion from last meeting08:30
diablo_rojoOkay moving on then.08:30
diablo_rojo#topic Ask.o.o08:30
*** openstack changes topic to "Ask.o.o (Meeting topic: fc_sig)"08:30
diablo_rojoSo, no new things that I saw, but it seems we have a lot of new tags we could look at that mattoliverau found08:30
* diablo_rojo is combining standing items with other items08:30
mattoliverauthat's ok08:31
gmannyea no new question there. though i replied nova and qa one which were not related to new contributors08:31
diablo_rojoI agree community, development, developer, and gettingstarted could be added to our list08:31
mattoliverauI didn't know where to put the list, so added it to the end08:31
diablo_rojomattoliverau, works just fine.08:32
diablo_rojoI feel like basics, beginner, newbie and noob (or n00b if you prefer) are all generic enough that we might get a lot of operations-y things in with them08:32
diablo_rojoThat being said, once we get some operator friends in our awesome group I am 100% cool with adding those as well08:33
mattoliverauthough if we have to filter with our eyes a little it isn't too bad08:33
diablo_rojoI just would be less helpful at responding to those.08:33
diablo_rojomattoliverau, fair point08:33
mattoliverauI mean, it wouldn't mean we'd reply to everything that turned up.08:33
mattoliverauI picked the tags that might include people looking for help contributing08:34
mattoliveraubut yeah, some seem too general.08:34
*** Tom-Tom_ has quit IRC08:34
diablo_rojoYeah I can see myself using those if I was new still :)08:34
diablo_rojoI also haven't heard back from Jimmy about if there were any he wanted us to add to our list.08:35
diablo_rojoI dunno. Thoughts from gmann or cmurphy ?08:35
mattoliverauI just went through the list.. found a bunch. Then went and did a search in ask.o.o for each one. Things that came up with nothing.. removed from the list. Things that popped up that _could_ potentually be relevent I kept in. Though your right there is alot of overlap..08:35
diablo_rojomattoliverau, obviously we just need ops-y friends to help us and then we can add them all to the list08:36
gmannsame, all of them (mentioned on wifi)are good to track08:36
*** Tom-Tom has joined #openstack-meeting08:36
mattoliverauI erred on the side of keeping things in, cause there easy to remove.. but not necessarily easy to find again (crazy wall of tags)08:36
* gmann was trying to build single query with all tags but need to check later08:36
mattoliveraudiablo_rojo: great idea!08:36
diablo_rojogmann, yeah we can do that later08:36
*** e0ne has joined #openstack-meeting08:36
diablo_rojomattoliverau, I submitted the forum topic and reserved space if it doesn't get accepted so it will be on the schedule one way or another08:37
diablo_rojoThat's about all I can do right now.08:37
diablo_rojoOnce forum topics are chose I plan to tweet up a storm about all my sessions08:37
mattoliverauI know, you've done great!08:37
diablo_rojoI am kind of getting ahead of the agenda..08:38
diablo_rojoSticking to tags for now.08:38
*** zhurong has joined #openstack-meeting08:38
mattoliverauI think you've just rolled the rest of the topics into 1 :P08:38
diablo_rojoSo adding community, development, developer, and gettingstarted08:39
cmurphysounds good08:39
diablo_rojogmann, did you want to make a query for all of them and update the agenda with it?08:39
gmanndiablo_rojo: yea08:39
diablo_rojoCool thanks :)08:39
diablo_rojoOkay so next topic?08:40
diablo_rojo#topic #openstack-101 is no more!08:40
*** openstack changes topic to "#openstack-101 is no more! (Meeting topic: fc_sig)"08:40
diablo_rojoSelf explanatory08:40
diablo_rojoBut thanks to mattoliverau and dmsimard|off for getting that done :)08:40
gmannthanks mattoliverau  dmsimard|off08:41
diablo_rojoThank you also for updating the training-guides OUI slides too.08:41
diablo_rojomattoliverau, ^^08:41
mattoliverauno worries. I went on an openstack-101 hunt :)08:41
diablo_rojoKILL ALL THE 101 MENTIONS08:41
mattoliverauand turns out getting an irc channel removed... not too hard. if you have infra's help of course ;)08:42
diablo_rojoI thiiiink there is a master list of channels in a wiki somewhere? Might want to find that and update it too.08:42
diablo_rojoIf there is one and I am not crazy.08:42
mattoliverauoh yeah, there could be. good point08:42
diablo_rojomattoliverau, good to know08:42
diablo_rojoSo much duplicated info. It will be a wonderful day when the contributor guide is the source.08:43
diablo_rojoAnywho, next topic!08:43
diablo_rojo#topic Forum Planning08:43
*** openstack changes topic to "Forum Planning (Meeting topic: fc_sig)"08:43
diablo_rojoSo we have the two proposed forum topics08:43
diablo_rojoI think we are into voting now or something?08:44
* diablo_rojo can't remember exactly how that works08:44
gmannno voting actually but yes we can comment.08:44
gmanni think i did for both08:44
diablo_rojoI had seen that cdent and gmann had commented on the orgazing base reqs for contribution one08:44
diablo_rojoWill have to look at the other.08:44
diablo_rojoBut yes! please comment and promote :)08:44
mattoliverauoh, we can comment. I'll try and remember to do that thing tomorrow08:45
diablo_rojomattoliverau, awesome :)08:45
* diablo_rojo goes to look up when decisions will be made by08:45
diablo_rojoNext week ish?08:46
diablo_rojoApril 22nd?08:46
diablo_rojoOr May 2 for final decisions and scheduling?08:46
mattoliverauoh.. ok that's soon08:46
diablo_rojoNot sure who is actually on the Forum Selection Committee either08:47
diablo_rojo     2 delegates from the Technical Committee08:47
diablo_rojo    2 delegates from the User Committee08:47
diablo_rojo    2 OpenStack Foundation staff members08:47
diablo_rojoBut no names08:47
mattoliveraucmurphy is a little quiet.. hmm.08:47
diablo_rojoI can't believe how close we are to the end of April already.08:47
mattoliverauyeah. isn't the 22nd a Sunday.08:48
gmanncmurphy has to play both role :)08:48
mattoliverauI guess that's ok. I'd have thought it would be a Friday or something. but 2 extra days is good08:48
*** links has joined #openstack-meeting08:48
diablo_rojo#link Forum Topic on Forming base reqs08:48
cmurphyi'm not on the selection committee08:49
diablo_rojo#link Forum topic on getting ops involved and doing a state of the union08:49
diablo_rojo^^ links for commenting on :)08:49
diablo_rojocmurphy, any idea who is?08:49
cmurphyI think it's TheJulia and pabelanger08:49
diablo_rojoCool. Good to know :)08:49
diablo_rojoI think that was all I had for that topic. Anyone else got anything else?08:50
diablo_rojo(10 min left)08:50
gmannnothing from me08:51
*** bobmel has quit IRC08:51
diablo_rojo#topic Open Discussion08:51
*** openstack changes topic to "Open Discussion (Meeting topic: fc_sig)"08:51
*** bobmel has joined #openstack-meeting08:51
diablo_rojocmurphy, did you find out if you can come early to Vancouver for OUI?08:51
diablo_rojomattoliverau, I think you have a patch in the contrib guide that has comments on it that needs addressing.08:51
diablo_rojoabout the ssh keys08:51
mattoliveraudiablo_rojo: oh cool, I'll take a look08:52
cmurphydiablo_rojo: I will be there Sunday so I can probably come in the morning for OUI but I'm not sure if it's that helpful to only come for part of one day08:52
diablo_rojomattoliverau, yeah ianychoi commented but voted 0 so you wouldnt know if you didn't go look at it08:52
diablo_rojocmurphy, we will take all the help we can get :)08:53
cmurphyokay then I'll show up :)08:53
mattoliveraudiablo_rojo: ahh, thanks for the heads up.08:53
diablo_rojoCome, hang out (we ususally have breakfast) and then you can sneak out when smcginnis does08:53
diablo_rojomattoliverau, no problem :)08:53
cmurphybreakfast ftw08:54
diablo_rojoYeah, we have a sponsor I think so there should be food. If not, mtreinish has a habit of showing up with donuts and things.08:54
diablo_rojoThankfully the gym I go to has a location in the convention center lol08:55
mattoliverauoh yeah, the donuts!!08:55
gmannor i can bring japanese fruite cake or somehting :)08:55
gmannfruit rice cake :)08:55
diablo_rojomattoliverau, you need to send along tim tams08:55
diablo_rojogmann, sounds fancy :)08:55
mattoliveraulol, I should.08:55
gmanntim tams wow08:55
diablo_rojomattoliverau, yes you should :)08:55
diablo_rojo(five min left)08:55
* diablo_rojo should have had that monster closer to 8 rather than 1008:56
diablo_rojoI think that concludes all the things I wanted to talk about.08:58
mattoliverauI think we might be done. diablo_rojo, did you want an early mark and get some sleep?08:58
diablo_rojoIf there's nothing else from anyone we can call it.08:58
mattoliveraucall it... do it.. you know you wanna08:58
diablo_rojomattoliverau, if I can- a little wired right now, but I should go to sleep since I have another meeting in like..6 hours.08:58
diablo_rojoOkay calling it!08:59
diablo_rojoThanks everyone :)08:59
gmannthanks :)08:59
*** openstack changes topic to "OpenStack Meetings ||"08:59
openstackMeeting ended Wed Apr 18 08:59:23 2018 UTC.  Information about MeetBot at . (v 0.1.4)08:59
mattoliverauthank you08:59
openstackMinutes (text):
cmurphysee ya08:59
diablo_rojoToodles :)08:59
* diablo_rojo tries to go to bed08:59
*** lhx_ has quit IRC09:03
*** lhx_ has joined #openstack-meeting09:04
*** lhx_ has quit IRC09:07
*** trinaths has joined #openstack-meeting09:11
*** alexchadin has quit IRC09:24
*** alexchadin has joined #openstack-meeting09:26
*** sidx64 has joined #openstack-meeting09:29
*** sidx64 has quit IRC09:30
*** sidx64 has joined #openstack-meeting09:34
*** zhujintao has quit IRC09:36
*** zhujintao has joined #openstack-meeting09:38
*** Alex_Staf has quit IRC09:42
*** alexchadin has quit IRC09:49
*** zxh has quit IRC09:51
*** zxh has joined #openstack-meeting09:52
*** asdasd has joined #openstack-meeting09:56
*** zhurong has quit IRC09:57
*** wanghao has joined #openstack-meeting10:02
*** hoangcx has joined #openstack-meeting10:26
*** zhipeng has joined #openstack-meeting10:27
*** pcaruana has quit IRC10:27
*** slagle has quit IRC10:44
*** Tom-Tom has quit IRC10:47
*** Tom-Tom has joined #openstack-meeting10:47
*** e0ne has quit IRC10:48
*** zz9pzza has quit IRC10:51
*** e0ne has joined #openstack-meeting10:51
*** Tom-Tom has quit IRC10:51
*** asdasd has quit IRC10:53
*** zz9pzza has joined #openstack-meeting10:56
*** zhipeng has quit IRC11:08
*** slagle has joined #openstack-meeting11:11
*** Tom-Tom has joined #openstack-meeting11:13
*** HeOS has joined #openstack-meeting11:13
*** hoangcx_ has joined #openstack-meeting11:17
*** Tom-Tom has quit IRC11:17
*** hoangcx has quit IRC11:20
*** zhipeng has joined #openstack-meeting11:27
*** Kevin_Zheng has quit IRC11:30
*** zhipeng has quit IRC11:34
*** yamamoto_ has quit IRC11:36
*** hoangcx has joined #openstack-meeting11:37
*** hoangcx_ has quit IRC11:39
*** radeks has quit IRC11:41
*** Guest67147 has quit IRC11:44
*** hoangcx_ has joined #openstack-meeting11:45
*** epico has quit IRC11:45
*** hoangcx has quit IRC11:45
*** gmann has quit IRC11:51
*** ykatabam has quit IRC11:51
*** julim has quit IRC12:00
*** rfolco|off is now known as rfolco12:01
*** raildo has joined #openstack-meeting12:01
*** yamamoto has joined #openstack-meeting12:03
*** tpsilva has joined #openstack-meeting12:05
*** alexchadin has joined #openstack-meeting12:08
*** lhinds- is now known as lhinds12:08
*** rbowen has quit IRC12:12
*** hoangcx has joined #openstack-meeting12:13
*** trinaths has quit IRC12:14
*** gmann has joined #openstack-meeting12:15
*** hoangcx_ has quit IRC12:15
*** edmondsw has joined #openstack-meeting12:15
*** sgrasley1 has quit IRC12:16
*** zhujintao has left #openstack-meeting12:19
*** dbecker has joined #openstack-meeting12:19
*** pcaruana has joined #openstack-meeting12:19
*** rbowen has joined #openstack-meeting12:21
*** hoangcx_ has joined #openstack-meeting12:23
*** hoangcx has quit IRC12:24
*** hoangcx_ is now known as hoangcx12:26
*** alexchadin has quit IRC12:26
*** pchavva has joined #openstack-meeting12:27
*** diman has joined #openstack-meeting12:30
*** diman has quit IRC12:34
*** edleafe- has joined #openstack-meeting12:35
*** edleafe has quit IRC12:35
*** edleafe- is now known as edleafe12:35
*** alexchadin has joined #openstack-meeting12:36
*** erlon_ has joined #openstack-meeting12:41
*** erlon has quit IRC12:41
*** erlon_ has quit IRC12:42
*** mjturek has joined #openstack-meeting12:43
*** erlon has joined #openstack-meeting12:43
*** erlon has quit IRC12:43
*** radeks has joined #openstack-meeting12:43
*** dustins has joined #openstack-meeting12:44
*** erlon has joined #openstack-meeting12:45
*** sidx64 has quit IRC12:46
*** apetrich_ has joined #openstack-meeting12:48
*** zhipeng has joined #openstack-meeting12:48
*** artom_ has quit IRC12:48
*** liuzz_ has joined #openstack-meeting12:51
*** liuzz has quit IRC12:51
*** jamesmcarthur has joined #openstack-meeting12:51
*** sidx64 has joined #openstack-meeting12:53
*** apetrich_ has quit IRC12:55
*** erlon has quit IRC12:56
*** erlon_ has joined #openstack-meeting12:56
*** erlon has joined #openstack-meeting13:00
*** erlon_ has quit IRC13:00
*** ssbarnea_ has quit IRC13:00
*** erlon_ has joined #openstack-meeting13:03
*** erlon has quit IRC13:04
*** erlon_ has quit IRC13:04
*** ssbarnea_ has joined #openstack-meeting13:05
*** erlon has joined #openstack-meeting13:05
*** donghao has joined #openstack-meeting13:05
*** erlon has quit IRC13:06
*** erlon has joined #openstack-meeting13:07
*** erlon has quit IRC13:07
*** erlon has joined #openstack-meeting13:08
*** erlon has quit IRC13:10
*** tobiash has left #openstack-meeting13:11
*** erlon has joined #openstack-meeting13:12
*** erlon has quit IRC13:12
*** erlon has joined #openstack-meeting13:13
*** julim has joined #openstack-meeting13:14
*** erlon has quit IRC13:14
*** erlon has joined #openstack-meeting13:15
*** erlon has quit IRC13:15
*** erlon has joined #openstack-meeting13:16
*** erlon has quit IRC13:16
*** erlon has joined #openstack-meeting13:17
*** lhx_ has joined #openstack-meeting13:26
*** parus has joined #openstack-meeting13:30
*** e0ne has quit IRC13:34
*** fnaval has joined #openstack-meeting13:35
*** fnaval has quit IRC13:35
*** fnaval has joined #openstack-meeting13:36
*** jamesmcarthur has quit IRC13:37
*** jamesmcarthur has joined #openstack-meeting13:38
*** annabelleB has joined #openstack-meeting13:40
*** bobmel_ has joined #openstack-meeting13:41
*** awaugama has joined #openstack-meeting13:42
*** e0ne has joined #openstack-meeting13:44
*** Kevin_Zheng has joined #openstack-meeting13:45
*** bobmel has quit IRC13:45
*** wanghao has quit IRC13:46
*** psachin has quit IRC13:46
*** wanghao has joined #openstack-meeting13:46
*** arnewiebalck has joined #openstack-meeting13:47
*** sidx64 has quit IRC13:47
*** sidx64 has joined #openstack-meeting13:51
*** eharney has joined #openstack-meeting13:53
*** jamesmcarthur has quit IRC13:57
mugsie#startmeeting Designate14:00
openstackMeeting started Wed Apr 18 14:00:59 2018 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: Designate)"14:01
openstackThe meeting name has been set to 'designate'14:01
mugsie#topic Roll Call14:01
*** openstack changes topic to "Roll Call (Meeting topic: Designate)"14:01
*** donghao has quit IRC14:03
*** esberglu has joined #openstack-meeting14:03
*** kiennt26_ has joined #openstack-meeting14:04
mugsiefrickler: daidv bnemec meeting ping14:04
frickleroh, a meeting o/14:05
mugsieI have put 4 reminders in my calander to make sure :)14:05
mugsie#topic Bug Triage14:06
*** openstack changes topic to "Bug Triage (Meeting topic: Designate)"14:06
openstackLaunchpad bug 1758013 in Designate ""also_notifies" section is not purged by designate when removing it from "pools.yaml" file" [Undecided,New]14:07
mugsiethis looks like a legitimate bug14:07
mugsieI think the object changes tracking thing is not fully working14:07
mugsieor we are doing a merge, and not taking the lack of a key to be empty14:08
mugsie]but a real bug non the less14:08
fricklerdeleting from hashes is always difficult, maybe the workaround is indeed the correct solution14:08
fricklerbut I didn't look in detail yet14:09
mugsiethat is all the new untriaged bugs14:09
*** wanghao_ has joined #openstack-meeting14:10
mugsie#topic Backports14:10
*** openstack changes topic to "Backports (Meeting topic: Designate)"14:10
*** anilvenkata has quit IRC14:10
mugsiethe only one may be bba6022a Update auth_uri option to www_authenticate_uri ? but I am not sure if that is worth it14:11
*** artom has joined #openstack-meeting14:11
*** fabian_ has joined #openstack-meeting14:11
mugsiethe d72c6520 Ensure we do not pass invalid data for A records patch only applied to rocky14:11
fricklerthat doesn't look suitable for a backport, too (the auth_uri)14:11
mugsieit does change the api actually, so no14:12
mugsie#topic Open Discussion14:12
*** openstack changes topic to "Open Discussion (Meeting topic: Designate)"14:12
*** bobh has joined #openstack-meeting14:13
mugsieany off agenda items - I know daidv wanted to talk about rolling upgrsdes, but I dont see them14:13
fricklerjust fyi I started rewriting our jobs in zuul v3 native
mugsiei saw that work starting - thanks :)14:13
fricklerbut seems that will still take a bit of work14:13
*** wanghao has quit IRC14:14
mugsieyeah - if you need any help let me know - I think it is a good thing to get done14:14
*** dklyle has joined #openstack-meeting14:15
mugsieit looks like the pdns server is not being configured for some reason14:15
frickleryes, I didn't have time to look into it because of pip 10 yet14:15
fricklermaybe I should start with bind9 instead14:15
mugsieit looks like the pdns server is not being configured for some reason14:16
mugsieIt may be easier alright, as bind is a simpler config14:16
mugsiemy damn internet is soooooo flaky today :/14:16
frickleranother topic is "use http code constant instead of int" - do you agree that if we do this, we should change all constants?14:17
mugsieIf we do it, yes14:17
mugsieI am not convinced of the value personally14:17
frickleryes, I wouldn't push it myself, but I won't object if it is done properly, too14:18
mugsieyea - that is ny feeling14:18
frickleralso just noting that the ReviewPriority thing seems to be working fine so far. not sure though how to integrate that in the dashboard14:19
mugsiethe dashboard should be updated with it14:19 has 2 sections on top, Urgent and Priority Fixes14:20
*** rpioso|afk is now known as rpioso14:20
frickleroh, you added that already, now I need to update my copy of that ;)14:21
mugsieit is just the start to be fair, and if anyone has idea about how to change how we do things with it let me know14:21
*** fabian_ is now known as chenyb414:22
mugsiethere is also
mugsiewhich might be useful for some people14:22
mugsie is the link i will keep updated14:22
* frickler likes the classification: small/big/aging ;)14:23
mugsieyeah, i need to tweek the aging one a bit, but it is important14:23
fricklero.k., so then there is the topic of changing the meeting time. I think we discussed this earlier already, but I don't remember the outcome. I guess eanderson would also like to attend14:25
mugsieI think office hours may suit better14:25
mugsieany other topics?14:25
mugsieignore ^14:26
mugsie(my internet lagged and nothing was showing -_-)14:26
bnemecFWIW, Oslo has a wayward changes section in its dash:
bnemecAlthough I'm amused its set at 2 days.14:26
mugsieThere is no time that suits everyone unfortunately14:27
mugsiebnemec: from a different time? :P14:27
mugsiefrickler: you are UTC-1 right?14:27
fricklerUTC+2 right now, UTC+1 in the winter14:27
*** armax has joined #openstack-meeting14:28
mugsiebnemec: is -5, and eanderson is -814:28
bnemecIs he in Hawaii or something?14:28
* bnemec would like to be in Hawaii right now14:28
mugsieI can try another doodle, or just say x day is in the morning UTC and y day is in the evening UTC14:28
mugsiewest coast of the US14:29
fricklerprobably -7 then with dst currently?14:29
bnemecOh, that should only be 2 hours off of me.14:29
mugsie#action mugsie mail the -dev list with options, and get feedback14:29
mugsiefrickler: yeah14:30
mugsiebnemec: oh, you are central? I thought you were eastern14:30
bnemecYep, Minnesota.  Where we are about to get our third spring blizzard of the year.14:30
frickleroh, I saw pictures from Lambeau field14:31
mugsieweather is wild right now, eh?14:31
* mugsie is happy - dublin is 19C right now :)14:31
bnemecI was actually pretty lucky.  Some places got 18 inches of snow last weekend.14:31
*** jamesmcarthur has joined #openstack-meeting14:32
fricklerberlin has 23C, so I'm also not complaining. except not being able to be in the sun ;)14:32
bnemecIt's Minnesota, so we'll go from freezing and snow to hot and humid in the space of about three days. :-)14:33
mugsiewe do that, just not usually with snow14:34
mugsieapart from that one time ...14:34
mugsieOK, any other topics? or will we call it for today?14:34
bnemecI guess a quick update on TripleO integration:14:35
mugsieoh - yes please14:35
bnemecMy patches have started to merge, so we should have Designate in TripleO for Rocky.14:35
bnemecI still have more work to do to configure pools correctly, but I should be able to get that done this cycle.14:35
bnemecAnd I'm sure dozens of other little things that I haven't considered, but at least the base will be there. :-)14:36
mugsieyeah, there is always one more little thing around the corner14:37
bnemecOtherwise that's it for me.  Oslo PTLing is still eating a lot of time, so we'll see how that shakes out over time.14:37
mugsiecool - as always, if you need anything from us, shout :)14:38
mugsiethanks all! have a good day14:39
*** openstack changes topic to "OpenStack Meetings ||"14:39
openstackMeeting ended Wed Apr 18 14:39:22 2018 UTC.  Information about MeetBot at . (v 0.1.4)14:39
openstackMinutes (text):
*** lpetrut has quit IRC14:40
*** hongbin_ has joined #openstack-meeting14:40
*** sgrasley1 has joined #openstack-meeting14:41
*** VW has joined #openstack-meeting14:45
*** alexchadin has quit IRC14:47
*** lseki has joined #openstack-meeting14:52
*** aagate has joined #openstack-meeting14:53
*** yamamoto has quit IRC14:53
*** felipemonteiro has joined #openstack-meeting14:54
*** rajinir has joined #openstack-meeting15:00
*** rbrndt has joined #openstack-meeting15:02
*** rbrndt has left #openstack-meeting15:02
*** alexchadin has joined #openstack-meeting15:02
*** markstur has joined #openstack-meeting15:07
*** markstur has quit IRC15:07
*** markstur has joined #openstack-meeting15:08
*** cgoncalves_ has quit IRC15:08
*** alexchadin has quit IRC15:16
*** cloudrancher has quit IRC15:18
*** niraj_singh has quit IRC15:19
*** cloudrancher has joined #openstack-meeting15:19
*** zhipeng has quit IRC15:19
*** kiennt26_ has quit IRC15:22
*** HeOS has quit IRC15:23
*** alexchadin has joined #openstack-meeting15:25
*** hamdyk has joined #openstack-meeting15:27
*** lpetrut has joined #openstack-meeting15:34
*** dklyle has quit IRC15:38
*** ganso has joined #openstack-meeting15:40
*** yamahata has quit IRC15:42
*** chenyb4 has quit IRC15:43
*** hemna_ has quit IRC15:52
*** alexchadin has quit IRC15:53
*** yamamoto has joined #openstack-meeting15:53
*** lkwan has joined #openstack-meeting15:54
*** links has quit IRC15:55
*** annabelleB has quit IRC15:55
*** sgrasley1 has quit IRC15:58
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Apr 18 16:00:08 2018 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
jungleboyjCourtesy ping:  jungleboyj DuncanT diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlon tpsilva patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut16:00
*** yamamoto has quit IRC16:00
_pewp_jungleboyj \( ・_・)16:00
*** annabelleB has joined #openstack-meeting16:02
jungleboyjOk, looks like we have a pretty good quorum here.16:02
jungleboyjeharney:  Good.  Was hoping to see you as well.  :-)16:03
jungleboyjLets get started16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:03
jungleboyjSo, I am planning to cut milestone 1 today.16:04
jungleboyjWant to make sure to stay on top of that.16:04
*** gman-tx has joined #openstack-meeting16:04
jungleboyjNothing really major to announce with milestone 1 though.  I did get the schedule for Cinder out on the web.16:05
* jungleboyj is such a slacker16:05
jungleboyjJust a reminder to watch the mailing list as the TC campaigning has started.16:05
jungleboyjLooks like good candidates out there.16:05
*** harlowja has joined #openstack-meeting16:06
jungleboyjI have also gotten our Forum topics posted.  So, we will see what comes of that.16:06
jungleboyjOur agenda for today for everyone's reference.16:06
jungleboyjI think that is all we have for announcements.16:07
jungleboyj#topic Rocky Priorities Review16:07
*** slaweq has quit IRC16:07
*** openstack changes topic to "Rocky Priorities Review (Meeting topic: Cinder)"16:07
jungleboyjSo, I see that we have gotten through some of the specs and got them merged.  Thank you!16:07
*** jamesmcarthur has quit IRC16:07
jungleboyjI have updated the Rocky Specs/reviews accordingly.16:07
*** efried is now known as efried_rollin16:07
*** jamesmcarthur has joined #openstack-meeting16:07
*** slaweq has joined #openstack-meeting16:07
jungleboyjHope as we go toward milestone 2 we will see more reviews show up in here.16:08
jungleboyjOne question.16:08
jungleboyje0ne:  We have the same spec under Generic Backup Implementation as well as Scheduler FIxes/improvements.16:08
jungleboyjIs that right?16:08
jungleboyje0ne:  ?16:09
e0nejungleboyj: scheduler improvements will be addressed separately from generic backups16:10
jungleboyjBeuler ... Beuler ......16:10
jungleboyjOk, so I thought you were going to push up some changes to the Generic Backup spec based on discussion at the PTG.16:10
erlonjungleboyj, that is actually another topic16:11
jungleboyjerlon:  That was what I thought.16:11
e0nejungleboyj: I need to speed with geguileo. mayby I messed something16:11
erlonthe scheduler improvements is already listed on the top16:11
jungleboyjerlon:  Right.16:11
jungleboyjSo, that link in there is wrong.16:11
e0nehere is a second spec according to scheduler
jungleboyje0ne:  Are you still planning on pushing an update to the Generic Backup Implementation spec?16:12
e0nejungleboyj: I'll ask Gorka and let you know our decision16:12
jungleboyje0ne:  Ok.  Sounds good.16:12
e0nejungleboyj: at least, I need to add something backups via scheduler related things16:13
*** slaweq has quit IRC16:13
jungleboyjOk, I won't spend more time on this if you are working on it.16:13
e0neI've got working PoC, so it will be easier now16:13
jungleboyje0ne:  Good.16:14
jungleboyjgeguileo: Are you here?16:14
erlone0ne, that name of that spec (support placement) is very misleading16:14
geguileojungleboyj: I am16:14
tommylikehuerlon:  ok..16:14
jungleboyjHey!  Here is your weekly harassment.16:15
e0neerlon: I agree. We'll have a conversation at the Summit too16:15
erlone0ne, nice16:15
jungleboyjgeguileo:  Any HA development updates?16:15
geguileonop  :-(16:16
jungleboyje0ne:  Cool.  Please make sure to pull me in on that.16:16
jungleboyjgeguileo: Ok.16:16
jungleboyj#topic HA development progress16:17
*** openstack changes topic to "HA development progress (Meeting topic: Cinder)"16:17
jungleboyjNo updates for this week.16:17
jungleboyj#topic Ocata backport from driverfixes progress16:17
*** openstack changes topic to "Ocata backport from driverfixes progress (Meeting topic: Cinder)"16:17
*** yamahata has joined #openstack-meeting16:17
jungleboyjsmcginnis: Thank you for all the work you put in to moving things from driverfixes/ocata to stable/ocata16:17
jungleboyjI have gone through and looked at all of those.16:17
jungleboyjeharney:  Do you want to look at all of those or should I just merge them so we can move on?16:18
eharneyi'll pick through some more of them shortly16:18
jungleboyjeharney:  Ok, smcginnis was wondering if I should just merge them but I would feel better having you take a look if you can.16:19
*** jamesmcarthur has quit IRC16:19
eharneyi think quite a lot of them were already +W'd and just waiting on the beginning of the series to get approved, right?16:19
smcginnisThere's just a few that haven't been approved yet. All have at least one +2.16:19
eharneythere are only like 5 left, i'll look at them today16:19
smcginnisThanks. It would be good to get driverfixes and stable in sync.16:20
jungleboyjsmcginnis:  ++16:20
e0nesmcginnis: +116:20
jungleboyjeharney:  Thank you!16:20
jungleboyjNext topic.16:21
jungleboyj#topic  ``volume:extend_attached_volume`` policy rule mechanism does not allow backends that do not support this feature to be handled separetely, creating a bad user experience16:21
*** openstack changes topic to "``volume:extend_attached_volume`` policy rule mechanism does not allow backends that do not support this feature to be handled separetely, creating a bad user experience (Meeting topic: Cinder)"16:21
jungleboyjContinued discussion from last week.16:21
jungleboyjlseki:  You here?16:21
lsekiwe talked about using a extra-spec/capability instead of policy rule16:22
jungleboyjSo, we didn't come to a conclusion on this last week.16:22
lsekiso, I'm not sure if it would be a bugfix or a feature16:22
gansoas per our discussion last week, it seemed to be considered a bug16:23
jungleboyjganso:  Right.  We didn't properly consider this when the feature was implemented.16:23
smcginnisYep, that's my take of it - it's a bug.16:23
gansobut adding a new extra-spec/capability as  a bugfix seems like a possible stretch of a bugfix16:23
lsekiconsidering it as a bug, we could backport it to pike/queens16:24
jungleboyjWell, before we talk about backporting lets come to agreement as to how we want to resolve it.16:24
gansojungleboyj: I assumed we reached agreement on the extra-spec/capability approach16:25
* erlon miss the old voting balots16:25
jungleboyjOk, so we will need drivers that support extending a volume to report it as a capability ...16:26
gansoand the capability should default to False16:26
SwansonWait, what?16:26
erlonSwanson, what what?16:26
jungleboyjerlon: what what what?16:26
SwansonWhy false?16:27
SwansonNow I have to do work to support something I think I can just do. (He said, not checking.)16:27
gansoSwanson: because it is something that backends should explicitly report that they support, rather than assume they do if they do nothing, which could lead to bad user experience16:27
erlonSwanson, False so people that supports move that to true, and you dont have driver that does not support reporting true16:27
jungleboyjSwanson:  Defaulting to true doesn't really resolve the problem.16:28
gansoSwanson: in that case, if you already do, the person implementing this bugfix should add the capability reporting line of code to all drivers that support it16:28
smcginnisI think most do support it. True would keep the existing behavior.16:28
smcginnisOtherwise if it is working for someone now, then they upgrade, suddenly they need to change config to keep doing what they were doing.16:28
SwansonWouldn't people who don't support it and don't want people using them to have a suck experience wouldn't they change it to false?16:28
eharneywhat is the behavior of the API if the driver doesn't support this?16:28
jungleboyjOk ...16:28
jungleboyjSwanson:  True.16:29
smcginniseharney: I believe it would attempt to, fail, and report that back to the user.16:29
smcginnisSo no real difference here.16:29
smcginnisIf it's True that is.16:29
smcginnisOtherwise, it will just start failing for everyone until they figure out what changed.16:29
gansosmcginnis: when they upgrade the new code should already include the new capability being reported for drivers that support it16:29
eharneythe volume would just revert to in-use, right?16:29
gansosmcginnis: it could fail in a bad way if it is not properly handled in the driver16:30
*** kopecmartin has quit IRC16:30
*** sgrasley1 has joined #openstack-meeting16:30
*** gyee has joined #openstack-meeting16:30
erloneharney, that would only make sense during volume creation, if the volume is already created and the BE does not support, the extra-spec will not be used16:30
gansoeharney: in NetApp's case, it remains detached with status "in-use", so it is a broken situation16:31
gansoeharney: and would require a ticket to reset the state16:31
smcginnisganso: Wait, this is extending an in-use volume I thought.16:31
eharneyyeah something isn't adding up here16:31
gansoeharney: this is just an example of what could possibly happen. We intend to fix that to prevent that situation regardless of the new implementation we are discussing here16:32
gansosmcginnis, eharney: yes our driver currently has a bug in this workflow that detaches while trying to extend while it is attached16:32
eharneyi thought the whole source of limitations w.r.t. in-use extend was about what nova/the hypervisor supported16:32
smcginnisganso: Well that's a bigger issue then. It should not detach the volume. That's bad.16:32
smcginniseharney: ++16:33
eharneysmcginnis: right16:33
gansosmcginnis: yes, we are going to fix it regardless16:33
smcginnisganso: But that doesn't have anything to do with the current topic.16:33
smcginnisganso: That's just a bug in the netapp driver.16:33
jungleboyjsmcginnis:  ++16:33
gansosmcginnis: but we are talking about the user experience here, of which the user would have already created a volume and finds out cannot be extended because the backend does not support it16:33
smcginnisganso: So the volume stays in the in-use state as you said above.16:33
gansosmcginnis: yes, it was just an example of what could happen if we leave the default to True and drivers don't handle this kind of situation16:34
smcginnisSo what's the bad experience.16:34
smcginnisEither the volume fails to extend or it works.16:34
eharneythere is another approach too16:34
smcginnisAnd why it fails to extend doesn't matter if it's disabled or not supported.16:34
eharneywe discussed at one point allowing the extend to succeed, but not having it really take effect until a detach/reattach was done later16:34
gansosmcginnis: defaulting to False avoids that for drivers that do not handle it16:34
smcginnisAnd f's all the other's that do and changes existing nbehavior.16:34
*** lpetrut has quit IRC16:35
SwansonMy point.16:35
gansosmcginnis: actually no, because it will never ask the driver to extend the volume online as it will not be supported, since it would default to False16:35
smcginnisAnd it won't ask the drivers that do support it either becuase it would default to False from what you are saying though.16:35
jungleboyjganso:  But doesn't that appear the same to the end user.16:35
gansosmcginnis: sorry I didn't get your last message ^16:36
gansosmcginnis: s/get/understand16:36
smcginnisI don't care about drivers that don't support it. It's a basic storage operation to extend a volume. If you're storage fails, get new storage.16:36
smcginnisWe shouldn't hobble all the storage that does work for the few that don't.16:36
gansosmcginnis: well I don't really see a problem with that, it could go either way, my suggestion was to False, and find the ones that should report True. The opposite works too.16:37
*** jamesmcarthur has joined #openstack-meeting16:37
jungleboyjSo, if we add the capability, we default to true.  Then users who have an environment that have a combination of storage that does or doesn't support it can use the extra spec and make sure they don't schedule to that storage if they need the capability.16:37
smcginnisjungleboyj: ++16:38
gansojungleboyj: +116:38
jungleboyjIf the storage provider doesn't update their capabilities ... well, tough.16:38
eharneyit sounds like it might make more sense to add a capability that says that this is not supported16:38
eharneyif it's really a rare situation16:38
eharneythen by default everything just does what it should16:38
jungleboyjeharney:  Hmmm.16:38
gansojungleboyj: since I know my storage does not support it, I'll make sure to update my capabilities. I can't speak for others though. They might face bugs and it will be their problem then16:38
eharneyotherwise we make the majority of deployers worry about a capability for no reason16:39
jungleboyjganso: smcginnis erlon  Thoughts on eharney  proposal?16:40
gansoeharney: do we know if the majority of drivers support it?16:40
eharneyganso: i'm not sure, but my guess is that most do... was hoping someone here knows :)16:40
erlonjungleboyj, I prefer this approach, defaults goes True, and we report false16:41
smcginniseharney: Isn't that proposal basically the same as defaulting it to true and having drivers report false if they do not?16:41
gman-txseems like it16:41
gansosmcginnis: only if the majority supports. Otherwise default to False. That's what eharney implied16:41
jungleboyjDo we have other capabilities that report an in-ability16:42
jungleboyjThat is my only concern there.16:42
eharneysmcginnis: maybe16:42
erlonjungleboyj, there may be, dont remember any on top of my head now16:42
eharneyi'm not sure it's a great idea16:43
jungleboyjOk.  Lets not spend more time on this.  Lets add the capability and default to true.16:43
jungleboyjI think that is consistent with what we do elsewhere.16:43
erloneharney, the default value or the hole idea?16:43
eharneyi'm still not sure why we want to add a driver capability for something that isn't mostly about the driver... but ok16:43
*** anilvenkata has joined #openstack-meeting16:44
gansoerlon: hole idea :P16:44
jungleboyjganso:  He he he.16:44
jungleboyjeharney:  This is where you flip a table16:44
smcginniseharney: I think in this case it is about the driver. At least one specific one for storage that doesn't support extending volumes.16:44
eharneya capability is also not going to work for anyone who has multiple different compute hypervisors16:44
*** sidx64 has quit IRC16:44
gansosmcginnis: +116:45
eharneysmcginnis: in the case we are talking about today yes... but i don't think it was when we designed this16:45
gansoalright. About backporting... Anything against it?16:46
jungleboyjDon't think so.  It is a bug fix.16:46
jungleboyjsmcginnis:  ^^^ ?16:46
smcginnisI want to see the fix first. :)16:46
jungleboyjsmcginnis:  ++  Makes sense.16:46
jungleboyjLets push up the proposed fix, we can review and move on.16:47
gansolseki: did we address all your concerns?16:47
lsekiganso: yep16:47
jungleboyjlseki:  Like the cat that comes in and starts a fight between the dogs and then watches.  :-)16:47
eharneyso what about people who actually are using the policy?16:47
lsekijungleboyj: hahahahah16:47
eharneythat still works too?16:48
gansoeharney: it should continue to work, but I'd suggest to remove the policy, or at least deprecate it16:48
gansoeharney: as the capability will be handling it16:48
SwansonPolicy is policy, driver support is another thing?16:48
eharney... if they went and configured volume types etc, it's not going to just handle it on upgrade out of the box16:48
tommylikehuSwanson: +116:49
gansoperhaps I missed some context when this was originally implemented. What was the purpose of this policy?16:49
gansoeharney: even if it defaults to True?16:49
*** lhx_ has quit IRC16:49
jungleboyjCan we move on from this as we have two other topics.  We can come back if time allows otherwise lets handle it through the code review.16:49
gouthamrpolicy prevents users from using the API16:49
gansojungleboyj: ok16:50
jungleboyjganso:  Thanks.16:50
eharneyapi policy changes combined with new capabilities sound like something more appropriate for spec review than code review to me16:50
*** jamesmcarthur has quit IRC16:50
erloneharney, and therefore it goes out of the scope of a bug16:51
jungleboyjOy ... Moving on ...16:51
jungleboyj#topic How to name volume type's reserved extra spec key or what's our naming schema for this purpose.16:51
*** openstack changes topic to "How to name volume type's reserved extra spec key or what's our naming schema for this purpose. (Meeting topic: Cinder)"16:51
jungleboyjtommylikehu:  ^^^^16:51
tommylikehuwe have decided to use reserved extra specs to address availability-zone volume type feature during ptg. but we havn't decided what exactly naming rules for the reserved keys.16:51
*** luizbag has joined #openstack-meeting16:52
eharneymy input is the naming should not be "os-extended:"16:52
eharneybecause that's basically a random string as far as extra specs go16:52
tommylikehuyeah. that's what I use in my code patch:)16:52
jungleboyjYeah, that means nothing to me.16:54
eharneyworse than nothing, it means "api extension" to me... which it's... not16:54
jungleboyjeharney:  So any idea what would be better?16:54
tommylikehueharney:  what's your suggestion?16:54
eharneywhat are these again?  keys that have a special meaning within cinder?16:55
tommylikehuyeah, that's what I thought16:55
eharneyyou wrote it, i'm just asking for clarity :)16:55
tommylikehuit means it's a reserved key for cinder16:56
*** yamamoto has joined #openstack-meeting16:56
jungleboyjcinder-key: or reserved-key:16:56
tommylikehujungleboyj:  both works for me16:57
eharneyhow is it being "reserved" here different from something like a key used to control, for example, replication?16:57
eharneyi.e. we already have a number of keys like this, right?16:57
jungleboyj3 minutes left16:57
tommylikehucause it's different, we use this in the extra spec, but it will not be used when performing capability filtering as others do16:58
jungleboyjYeah that was how I thought this was different.16:58
jungleboyjNot an extra spec for the driver.16:58
eharneywill there be other cases of needing keys like this in the future?16:59
jungleboyjeharney:  Possibly.16:59
tommylikehuit could be16:59
jungleboyjLets finish this in the review now that people are aware of it.16:59
smcginnisI thought there were some other reserved keys like this.16:59
tommylikehusmcginnis:  which are in the format of prefix: name?17:00
eharneysmcginnis: me too... it's hard to name the field before we come up with a solid definition of what it means...17:00
eharneydon't call it "os-" anything please17:00
*** yamamoto has quit IRC17:00
jungleboyjtommylikehu: eharney smcginnis  Can we finish this in the review?17:00
smcginnistommylikehu: Not sure, but I thought there was something already implemented. Been a very long time since I've looked at that code.17:00
jungleboyjeharney:  I agree.17:00
smcginnisGuess we'll have to.17:00
jungleboyj#topic Push to merge NVMeOF cinder changes17:01
*** openstack changes topic to "Push to merge NVMeOF cinder changes (Meeting topic: Cinder)"17:01
jungleboyjI think this is just a request to look at the reviews.17:01
gansotime check17:01
jungleboyjhamdyk:  Correct?17:01
hamdykHi everyone17:01
hamdykjungleboyj: yes17:01
lsekihamdyk: hi17:01
gansohamdyk: welcome17:01
Swansonsmcginnis never ran over time.17:01
jungleboyjOk.  We will take a look.17:01
jungleboyjAnd that is the meeting.17:01
smcginnisSwanson: Hah!17:01
jungleboyjSwanson:  :-p17:02
hamdykcan you take a look at the patches and merge thim17:02
jungleboyjhamdyk:  Will do.17:02
hamdykI think we in a good shape there17:02
jungleboyjThanks everyone!17:02
*** openstack changes topic to "OpenStack Meetings ||"17:02
openstackMeeting ended Wed Apr 18 17:02:23 2018 UTC.  Information about MeetBot at . (v 0.1.4)17:02
openstackMinutes (text):
*** e0ne has quit IRC17:02
jungleboyjerlon:  I don't think anyone has the time after us scheduled.17:02
*** Leo_m has joined #openstack-meeting17:02
erlonjungleboyj, I hear people walking in the door, I think they was just bassing by :p17:03
*** lseki has left #openstack-meeting17:05
*** aagate has quit IRC17:10
*** gman-tx has quit IRC17:11
*** gyee has quit IRC17:12
*** devananda has joined #openstack-meeting17:14
*** tssurya has quit IRC17:23
*** sambetts is now known as sambetts|afk17:23
*** cloudrancher has quit IRC17:24
*** cloudrancher has joined #openstack-meeting17:25
*** raildo has quit IRC17:28
*** cloudrancher has quit IRC17:28
*** cloudrancher has joined #openstack-meeting17:29
*** electrofelix has quit IRC17:33
*** Kevin_Zheng has quit IRC17:34
*** esberglu has quit IRC17:35
*** cloudrancher has quit IRC17:36
*** marios has quit IRC17:37
*** ekcs has joined #openstack-meeting17:37
*** raildo has joined #openstack-meeting17:37
*** janki has quit IRC17:37
*** cloudrancher has joined #openstack-meeting17:37
*** bobh has quit IRC17:41
*** harlowja has quit IRC17:44
*** Leo_m_ has joined #openstack-meeting17:46
*** esberglu has joined #openstack-meeting17:47
*** Tom-Tom has joined #openstack-meeting17:48
*** Leo_m has quit IRC17:48
*** sridharg has quit IRC17:52
*** Tom-Tom has quit IRC17:52
*** jamesmcarthur has joined #openstack-meeting17:54
*** yamamoto has joined #openstack-meeting17:56
*** raildo has quit IRC17:58
*** sgrasley1 has quit IRC18:01
*** yamamoto has quit IRC18:02
*** lpetrut has joined #openstack-meeting18:03
*** ganso has left #openstack-meeting18:04
*** parus has quit IRC18:05
*** radeks has quit IRC18:05
*** raildo has joined #openstack-meeting18:10
*** lpetrut has quit IRC18:10
*** pcaruana has quit IRC18:12
*** bobh has joined #openstack-meeting18:16
*** lpetrut has joined #openstack-meeting18:18
*** harlowja has joined #openstack-meeting18:18
*** tssurya has joined #openstack-meeting18:20
*** kaisers_ has quit IRC18:22
*** harlowja_ has joined #openstack-meeting18:23
*** harlowja has quit IRC18:24
*** e0ne has joined #openstack-meeting18:32
*** bobh has quit IRC18:39
*** bobh has joined #openstack-meeting18:40
*** ricolin has quit IRC18:47
*** yamamoto has joined #openstack-meeting18:57
*** annabelleB has quit IRC19:00
*** kaisers has joined #openstack-meeting19:01
*** felipemonteiro_ has joined #openstack-meeting19:01
SotKanyone here for the storyboard meeting?19:01
* fungi raises hand19:01
SotK#startmeeting storyboard19:02
openstackMeeting started Wed Apr 18 19:02:26 2018 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: storyboard)"19:02
openstackThe meeting name has been set to 'storyboard'19:02
SotK#link Agenda19:02
SotK#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:03
*** yamamoto has quit IRC19:03
* diablo_rojo was too slow updating the agenda so... winging it?19:03
*** HeOS has joined #openstack-meeting19:03
SotKthat is my usual approach to such situations19:04
*** bobh has quit IRC19:04
diablo_rojoI'll do better next time!19:04
fungii got teh gerrit service on leaving comments on stories in as of saturday19:04
SotKthanks for fixing that19:05
diablo_rojoI saw its working already which is awesome!19:05
diablo_rojoI will give Senlin the heads up that its not an issue anymore19:05
fungiturned out to just need configuration updated for gerrit 2.13/newer its-storyboard plugin19:05
diablo_rojoor whichever project that was19:05
*** raildo has quit IRC19:05
diablo_rojoEasy fix.19:05
fungi#link Comment on linked stories for review state changes19:05
fungithat was the patch which ultimately did it19:05
*** felipemonteiro has quit IRC19:05
*** hafnix has joined #openstack-meeting19:06
*** hafnix has left #openstack-meeting19:06
*** kaisers has quit IRC19:06
SotKwe also had some more migrations right?19:07
diablo_rojoNot only will it unblock a project- it also removes one of the things on our 'blocking migration' tag list19:07
diablo_rojoSotK, yes we did!19:07
diablo_rojoOpenStackSDK OpenStackClient (thanks fungi again)19:07
diablo_rojoAnd I think TripleO- validations squad?19:09
*** artom has quit IRC19:09
*** artom has joined #openstack-meeting19:10
SotK#topic Migration Updates19:10
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:10
SotKspeaking of migrations...19:10
*** ssbarnea_ has quit IRC19:10
SotKdo we have more lined up?19:10
diablo_rojoI started rerunning test migrations that had previously failed for the lack of utf8mb4 support and so far they are all passing19:10
SotKthat is good news19:10
diablo_rojoSotK, as of right now for this week I don't think so (aside from maybe another TripleO squad if we can figure that out)19:11
*** cloudrancher has quit IRC19:11
diablo_rojoI need to circle back to a few that said they were basically ready to go- Barbican comes to mind19:11
diablo_rojoI just need to go door knocking again.19:11
*** cloudrancher has joined #openstack-meeting19:12
*** numans has quit IRC19:12
*** numans has joined #openstack-meeting19:13
diablo_rojoProgress can still be followed here:19:13
*** pcaruana has joined #openstack-meeting19:13
diablo_rojoAlso, was thinking it might be time to dust off the release goal and propose it for Stein soon?19:13
SotKI think that could make sense, I feel like we have some momentum now at least19:14
*** tesseract has quit IRC19:15
diablo_rojoMuch more than we did last round at least.19:15
diablo_rojoI don't think there is a ton to update other than the individual project stuff.19:15
SotK#topic In Progress Work19:16
*** felipemonteiro__ has joined #openstack-meeting19:16
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:16
*** raildo has joined #openstack-meeting19:17
diablo_rojoThere are a lot of patches out there waiting for another +2 :)19:17
diablo_rojoWent ahead and updated the project creator to stop telling new projects to use launchpad too19:18
funginow that i'm done figuring out the story commenting i was going to work on getting stories indexed in web search engines, but mordred pointed out that the angularjs migration once complete will allow us to make use of their "universal" server-side rendering19:18
fungi#link Angular Universal19:19
SotKheh, I will do my best to provide some +2s at some point19:19
diablo_rojofungi, thats convenient- lessens the workload for us right?19:19
*** felipemonteiro_ has quit IRC19:20
fungiin theory, but only if we get through the angular refactor19:20
*** pcaruana has quit IRC19:20
diablo_rojoSotK, no worries, should be a bunch of easy things if you get some spare time :)19:21
SotKyeah, universal will be nice I think if we can somehow find time to convert to modern angular and verify that nothing broke19:21
fungior at least that nothing _new_ broke ;)19:23
diablo_rojoGood point :)19:23
SotKheh, true19:23
SotKI plan to actually do some useful things this week, such as fix the project selection bug that practically everyone hits19:23
diablo_rojoSotK, +119:23
fungiSotK: oh that will be awesome if you get to it. thanks!!!19:23
SotKand also look at fixing the board issues that were encountered the other day19:24
fungipeople who are using sb regularly get used to the project selection quirk once they know about it, but new users reporting bugs on projects they're using won't really be likely to figure it out19:24
*** efried_rollin is now known as efried19:24
SotKyeah, it seems like the kind of thing that's really frustrating for new folk and leaves a bad first impression19:25
diablo_rojo+2 for fixing things that leave bad impressions19:25
SotKthe boards issues were less "bad first impression" bugs and more "this makes boards really annoying" issues19:26
fungiso anyway, aside from lifting the robots.txt and seeing if google manages to index stories (because unlike most other search engines they apparently have javascript savvy crawling implemented) i'll probably start looking next at the testing issues which are blocking fixing the private story e-mail notifications19:27
diablo_rojoSounds like a good plan to me.19:27
funginot that i have any expectation i'll be able to figure them out, but they seem important19:28
diablo_rojoOur intern should get notification they were selected the end of the week so hopefully will have a few more hands helping out19:28
SotKalso sounds like a good plan to me19:28
diablo_rojofungi, investigation helps even if you can't figure out how to fix it yet19:29
*** ayoung has joined #openstack-meeting19:29
fungiright, at least i might suss out a little more and we can give someone additional context19:29
diablo_rojoSotK,  if you can get that one patch that just explains the private tag in the webclient merged I can reach out to glance and we could migrate them Friday probably19:30
SotKsure, I'll look at that tonight19:30
SotK(I'm aware I've said similar for about a month but I actually have my test instance on my lap now)19:31
diablo_rojoHa ha ha no worries. We know you don't do this for your dayjob anymore.19:32
SotKanything else in progress?19:34
diablo_rojoWhat else we got going?19:34
diablo_rojoDon't think so.19:34
fungii noticed that its-storyboard doesn't have a feature to assugn/unassign tasks on change state transitions19:34
*** Nel1x has quit IRC19:34
fungiprobably a high-ish priority but will require someone with some java smarts19:35
*** bobh has joined #openstack-meeting19:35
fungi#link Plugin to integrate with the Storyboard Issue Tracking System19:35
fungisounds like the necessary account query filter by openid might already be implemented in the storyboard api19:35
*** imacdonn has quit IRC19:35
diablo_rojofungi, ah yes :) That would be good. Also good work containing your excitement19:35
*** imacdonn has joined #openstack-meeting19:36
fungiso we'd just need something which could use the openid gerrit has on hand for the committer id to figure out to whom it needs to assign a corresponding sb task on active states, and unassign on a transition to abandon state19:37
*** dustins_ has joined #openstack-meeting19:37
diablo_rojoSeems pretty simple...but I also would have to look back through my java text books lol19:38
*** artom has quit IRC19:38
SotKyeah, sounds pretty doable, it just needs us to find someone enthused about writing java19:39
fungithere are a number of other its-.* plugins hosted in the same place, but i didn't spot any of them doing bug assignment or somilar so this may be breaking new ground as far as a plugin getting access to the account_external_ids table in gerrit19:39
*** felipemonteiro__ has quit IRC19:39
*** felipemonteiro__ has joined #openstack-meeting19:40
fungihopefully that isn't somehow disallowed by gerrit's plugin interface, otherwise the rest should be straightforward i expect19:40
*** dustins has quit IRC19:41
*** awaugama has quit IRC19:43
diablo_rojoMakes sense.19:44
diablo_rojoHypothetically simple until you dig in :)19:44
SotKhopefully it is possible19:44
SotKanything else in progress?19:44
fungiwe can probably also lean on zaro__ with questions if we get stuck on that since he wrote the original plugin19:44
fungihe's been really helpful answering my questions so far, anyway (thanks!!!)19:45
diablo_rojoNoted :)19:46
diablo_rojoDon't think so19:46
*** ssbarnea_ has joined #openstack-meeting19:47
SotK#topic Blocking Migration Stories19:47
*** openstack changes topic to "Blocking Migration Stories (Meeting topic: storyboard)"19:47
diablo_rojoCrossed one or two off the list this last week19:48
SotKyep, nice work folk :)19:48
diablo_rojoCan't remember what we have left to knock out- I remember a lot of them being sort of opinion-y19:49
*** ayoung has quit IRC19:50
SotKI think most of the remaining ones are opinion-y or already in review19:51
diablo_rojoProgress then!19:51
diablo_rojoThe irc bot would be cool- hopefully we can get an intern on that one19:51
fungisearch engine indexing and task assigning have the potential to turn into blockers depending on whether teams who are considering migration didn't know about them and didn't think to check19:51
SotKhopefully we can get them addressed before that happens :)19:53
*** Nel1x has joined #openstack-meeting19:53
fungihere's hoping, yes19:53
diablo_rojoLittle do they all know they can see our public logs for these meetings :)19:54
SotK#topic Open Discussion19:54
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:54
diablo_rojoSotK, coming to vancouver? :)19:55
diablo_rojoPlease please please!19:55
fungiin my opinion, any teams who are following the sb meetings are totally welcome to help us prioritize things19:56
diablo_rojoAnd welcome to help too if something is bothering them that badly :)19:56
*** e0ne has quit IRC19:56
fungimaybe someone who likes to hack in java in their spare time will read it ;)19:56
SotKfungi: +119:56
SotKdiablo_rojo: idk yet, but most likely not I think19:56
diablo_rojoSotK, someday19:57
fungiit _is_ a really long trip from the uk19:59
*** yamamoto has joined #openstack-meeting19:59
diablo_rojoIts true19:59
diablo_rojoBut still.19:59
SotKyeah, it is really far :)20:00
SotKanything else will need to be in #storyboard20:00
SotKthanks all20:00
*** openstack changes topic to "OpenStack Meetings ||"20:01
openstackMeeting ended Wed Apr 18 20:00:56 2018 UTC.  Information about MeetBot at . (v 0.1.4)20:01
openstackMinutes (text):
diablo_rojoThanks SotK!20:01
*** eharney has quit IRC20:01
*** yamamoto has quit IRC20:04
*** erlon has quit IRC20:09
*** torgomatic has joined #openstack-meeting20:18
*** Nel1x has quit IRC20:25
*** edwarnicke_ is now known as edwarnicke20:27
*** lpetrut has quit IRC20:30
*** mriedem has joined #openstack-meeting20:34
*** ssbarnea_ has quit IRC20:37
*** ssbarnea_ has joined #openstack-meeting20:37
*** julim has quit IRC20:39
*** yamamoto has joined #openstack-meeting20:44
*** Nel1x has joined #openstack-meeting20:45
*** dmellado has quit IRC20:45
*** acoles has joined #openstack-meeting20:46
*** gouthamr has quit IRC20:46
*** sidx64 has joined #openstack-meeting20:46
*** stevebaker has quit IRC20:48
*** sidx64_ has joined #openstack-meeting20:49
*** m_kazuhiro has joined #openstack-meeting20:51
*** sidx64 has quit IRC20:51
*** patchbot has joined #openstack-meeting20:54
*** dbecker has quit IRC20:55
*** timburke_ has joined #openstack-meeting20:58
notmynameswift meeting time21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Apr 18 21:00:33 2018 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
notmynamewho's here for the swift team meeting?21:00
claygrledisez_: !!!21:01
*** luizbag has quit IRC21:01
notmynameagenda for this week is the same as last week:21:01
notmynamebut we have a whole week's worth of new info about each topic! :-)21:02
notmyname is still open and it fixes a high-priority bug21:02
patchbotpatch 555245 - swift - Fix versioned writes error with url-encoded object...21:02
notmynamestill needs reviewers, and it should land before the next swift release.21:02
notmynameas we get closer to a release at some point, I'll bug people more about it specifically21:03
notmyname(so in this case, there is *not* a week's worth of more info on it)21:03
timburke_thanks for the fix kota_! sorry that i haven't gotten to reviewing it :-(21:04
notmynameok... feature/s3api, feature/deep, and torgomatic's consistency engine work. all of these are wrapped up together this week21:04
notmynamelet's see how I can untangle them for the meeting21:04
notmynamefirst up, I'll give a summary of where we are with feature/deep (and acoles can correct me where I'm off)21:04
notmynamegood news with feature/deep is that we deployed it to a test cluster at the end of last week and ran it on a 145M row DB21:05
*** zaitcev has joined #openstack-meeting21:05
notmynamebad news is that it didn't work perfectly21:05
notmynametimburke_ did a lot of great work to get that tested and diagnosed21:05
notmynamethe major issue that came up is related to DB replication21:05
notmynameie replication during the sharding process obviously needs some work so that a lot of DB rows aren't moved unnecessarily21:06
notmynametimburke_: is that a resaonable, albeit brief, summary?21:06
timburke_notmyname: idk what you're talking about -- that was *fantastic* news! *way* better to have it fail now21:06
notmynameyes, it was fantastic to see it running and finding issues before we merge it :-)21:07
*** slaweq has joined #openstack-meeting21:08
timburke_but yeah, definitely a lurking issue with db replication -- i saw my nice beautiful tiny db (that should eventually only have shard ranges) take on ~12M object rows21:08
notmynameif you remember from a while back, we'd set a goal of proposing feature/deep to master this week21:08
acolesnotmyname: specifically we are now planning to stop replicating objects between peers when they could be moved to shards. before we still had some replication happening as well as sharding21:08
notmynametimburke_: acoles: right. thanks for the clarification21:08
*** ykatabam has joined #openstack-meeting21:08
notmynameso regarding a merge proposal to master, the short answer is "it's not happening this week"21:09
notmynameacoles and clayg and timburke_ have been working hard on the replication issues (and other things) in order to get something that works21:09
*** bnemec has quit IRC21:09
notmynameour new goal is to have a feature/deep proposal to master next week21:10
notmynamein part, that's going to be based on later tests this week of the fixes that have been proposed running in a real cluster21:10
*** bnemec has joined #openstack-meeting21:11
mattoliverauNice work timburke_ and acoles, sorry if it was something I missed. Is there anything I can do to help?21:11
notmynamein general, there's a couple of assurances I want to give to everyone: first, and most importantly, we won't merge something to master that doesn't work21:11
notmynamenobody is going to propose a merge to master (much less approve it) in order to meet a date we set for ourselves21:11
acolesmattoliverau: nope it's nothing you missed21:11
notmynameand secondly, again, it's great we're finding this stuff now21:12
acolesmattoliverau: is where we're at and it is quite possibly more in your original direction of thinking21:12
patchbotpatch 549678 - swift (feature/deep) - Stop replicating object rows when container could ...21:12
*** pchavva has quit IRC21:12
*** slaweq has quit IRC21:12
timburke_it was also an idea i'd had knocking around in my head since the ptg -- once we know where the rows should go, we should be trying to get them there asap, not kick them over to another server to deal with them21:13
notmynameso for everyone else, we will need everyone's help to review the merge to master. and it looks like that's coming quickly. the goal is next week21:13
mattoliverauOk, I'll review it today and try and get up to speed.21:13
notmynametorgomatic has already started looking at it in order to be able to better review it21:13
acolesmattoliverau: IIRC you were 'usync only' once sharding and we're now looking at 'nothing'21:13
*** stevebaker has joined #openstack-meeting21:14
notmynamewhich brings me to the consistency engine work that torgomatic was working on (rooted at patch 555563)21:14
patchbot - swift - Multiprocess object replicator21:14
*** jamesmcarthur has quit IRC21:14
mattoliverauWell handoffs sharding to the right place is good too, so data does move, just to the right place. Ie a new form of replication21:14
notmynamethat stuff is still open, still a great improvement to swift, but on hold until after feature/deep lands21:15
acolesmattoliverau: yep21:15
timburke_mattoliverau: yeah, that was my key takeaway too -- and in particular, we're *not harming durability* by doing that21:15
notmynameany questions on feature/deep or torgomatic's patch chain?21:15
notmynametdasilva: as we mentioned last week (I think it was clayg's idea), I'd still like to set up a video chat around the time of a merge proposal so that we can all talk about the general design and to help with our review process21:16
tdasilvasounds good21:17
mattoliverautimburke_: +121:17
notmynamerledisez_: kota_: m_kazuhiro: does all of that make sense? sound good?21:17
notmynamekota_: ah, you answered my question before I finished typign :-)21:17
mattoliverau+1 to the video as well21:18
rledisez_notmyname: looks ok to me21:18
notmynameacoles: clayg: timburke_: anything to add about feature/deep right now?21:18
kota_for video call ;)21:18
acolesnotmyname: not from me21:18
notmynameok, that brings us to the topic of feature/s3api21:19
notmynameI've talked to nearly all of you about this topic during the last week21:19
notmynamelet me paste the summary in here so that we're all talking about the same thing and also so that it is recorded in meeting logs21:19
notmynamefeature/s3api is ready to be proposed to master. this is a simple import of swift3's functionality and code into swift's repo21:20
notmynameif we do that, the advantage is that we have s3 support as a first-class part of swift. IMO this is very good for adoption and marketing of swift21:20
notmynameit's also good because it means we can remove "cruft" from swift3 and stop having to worry about compatibility matrixes (which version of swift vs swift version of swift3)21:21
notmynameand we'll get s3 testing with patches to swift21:21
notmynamethat is all great21:21
notmynamewe originally wanted to make some breaking changes to s3api so that we could enable more functionality in the future. for example, we need a better way to map buckets to accounts and containers so that we can support public ACLs and more of the bucket api21:21
notmynameif we do that as we land s3api, ie if it's included in the first merge to master, then we've got the advantage of "here's a new thing named something new that doesn't completely work with the old" but that's ok, because it's all new21:22
notmynameif we don't do that breaking work now, then we may (probably will?) have to worry more about migrations and support in the future when we get around to actually doing that work21:22
notmynameso we could still try to do that breaking-change work to get the better bucket mapping. and do that before trying to import swift3 code21:22
notmynameor we could delay that work and merge what we have now21:23
notmyname if we delay, it's not a delay until a specific later date. it's a delay to "unscheduled", despite a clean merge being ready now21:23
notmynameso... that gets to the question. as I see it, we have 3 options. which do you prefer21:23
notmyname(1) community merges feature/s3api now as a swift3 import, and we accept the impact it has to feature/deep work21:23
notmyname(2) we designate a couple of people in the community to review and merge feature/s3api into master as it is now. we agree to let them do this without wider community input. ie it's like a normal patch to master with 2 cores and all the rest of us decide to be ok with the added s3 capability. this likely implies that those focusing in feature/deep will keep doing so and delegate authority on21:24
notmyname feature/s3api to others21:24
notmyname(3) we delay merging feature/s3api until an undetermined date in the future. essentially this means unscheduling the work and accepting that future work will never be as simple as it is right now. at least we'll have merge conflicts and at most we'll have the additional refactoring work too21:24
*** ekcs has quit IRC21:24
notmynameok, copy/paste wall done :-)21:24
notmynameas i said, I talked to most of you during the past week about this21:24
notmynamehere's the consensus:21:24
*** ekcs has joined #openstack-meeting21:25
notmynamewe should do option 2. and whoever the review champions are should keep in mind that they can call out to the rest of us if soemthing big is found21:25
zaitcevand the designated champions are...21:26
notmynameso here is the actual question for this meeting to everyone here: do you support this agreement. ie are we all ok with this as the way forward as a group?21:27
notmynamezaitcev: good question. let's make sure everyone agrees first :-)21:27
mattoliverauSo option 2 with a little bit of 1 (if something big is found)21:27
notmynamemattoliverau: correct21:27
*** apetrich_ has joined #openstack-meeting21:27
mattoliverauIf we knew how it worked it could be a great time to use the meeting vote option :p21:28
mattoliverauBut it's +1 from me21:28
clayglol @ mattoliverau21:28
claygnotmyname: sounds like a great plan!21:28
kota_let me correct the difference of 1 and 221:29
notmyname#vote do you support the community designating reviewers for feature/s3api in order to merge it now, knowing that it will cause future pain for migrations whenever we get around to scheduling the bucket mapping work? yes, no21:29
notmynameyeah, that didn't work :/21:29
tdasilvai know i asked again, but just to try to clarify...if we named it swift3 for now with an eye on one day having s3api as a new middleware with all the work we want, would that help at all? or not really?21:29
tdasilvas/asked again/asked before21:30
notmynametdasilva: IMO, not really. the hard part is because it will be in swift, and swift must have a migration plan21:30
notmyname...plan for everything we have in swift21:30
notmynamewe may need to rename it in the future. that may be part of a future breaking change plan21:30
*** zaitcev_ has joined #openstack-meeting21:31
notmynamekota_: for (1) it means we'd all review it and delay feature/deep work. for (2), it means we'd treat it more like a normal patch to swift and we'd have 2 +2s and land it21:31
timburke_....but knowing us, we'll still end up supporting the old name indefinitely :-/21:31
claygtimburke_: that's the spirit!21:32
kota_notmyname: make sense, and the voting message concrete me to catch up. 2 has still the pain on the migration issue for un-developed features.21:32
*** timburke_ is now known as timburke21:33
notmynamekota_: correct. both (1) and (2) have pain for future un-developed features21:33
notmynamein my opinion, because the future work for refactoring is completely unscheduled, we should land what we have available now. the benefits of having upstream s3 api support (technical and otherwise) outweigh future migration work that we haven't yet started to work on21:34
*** zaitcev has quit IRC21:34
claygnotmyname: well said!21:34
claygnotmyname: one in the hand two in the bush!21:35
notmynameany other comments on this particular question? if not, let's move on to choosing who the reviewers will be21:36
notmynameie move forward with option 2 as I've presented it21:36
* notmyname pauses in case anyone is typing something long21:36
acolesI'm ok with us moving forwards with option 2, there's no ideal solution21:37
m_kazuhiroI like option 2 :)21:38
notmynamenow for the big question! zaitcev_ said it... "who are the designated reviewers for feature/s3api?"21:38
*** ykatabam has quit IRC21:38
*** kaisers has joined #openstack-meeting21:38
zaitcev_Some kind of migration from swift3 is needed anyway, I'm afraid. Currently we're trying to wash our hands by making a middleware under a different name.21:38
*** niknak5555 has joined #openstack-meeting21:39
*** jamesmcarthur has joined #openstack-meeting21:40
notmynamenot everyone volunteering at once :-)21:40
notmynameso, obviously, feature/deep is taking a lot of time21:40
notmynamethe point of option 2 is to impact that work as little as possible21:40
notmynamewhich means at least acoles, clayg, and timburke cannot review feature/s3api21:41
kota_zaitcev_: at the point of migration from swift3, i added a few changes to support the migration (e.g.
patchbotpatch 557623 - swift (feature/s3api) - Change sysmeta name from swift3 to s3api (MERGED)21:41
kota_at feature/s3api, so I'd keep the migration path as possible.21:41
notmynametorgomatic and mattoliverau are questionable because they're somewhat involved with feature/deep21:42
notmynamekota_ is the primary author of feature/s3api, so probably shouldn't be one of the reviewers (but we may reconsider that)21:42
*** jamesmcarthur has quit IRC21:42
*** kaisers has quit IRC21:42
notmynamesooo... who's left?21:42
kota_notmyname: it's what i thought but can be volunteer to fix the patch/ answer some questions21:43
*** tobberydberg has quit IRC21:43
notmynameof all of us here in the meeting, we've got rledisez_, m_kazuhiro, zaitcev_, tdasilva, and myself21:43
zaitcev_the answer is obvious, we still have myself, tdasilva, cschwede.21:43
zaitcev_oh, yeah, Romain21:43
notmynamehas anyone seen cschwede? I didn't count him because I haven't seen him around in a long time21:44
*** bobh has quit IRC21:44
zaitcev_He's stuck in meetings whole day every day.21:44
mattoliverauAnd my time is currently limited with a bunch going on.. but if no one else will I'll find some time. But it might not be the fastest reviews21:44
*** bobh has joined #openstack-meeting21:44
tdasilvanotmyname: did you have a schedule in mind?21:45
notmynamethe goal of reviewing feature/s3api merge is (1) is it a faithful import of swift3 (2) does it make any major changes that cause for concern (3) is it maintainable code21:45
tdasilvai.e., do you want to see it merged before feature/deep or is it completely orthogonal?21:45
notmyname(any other major criteria for review of this feature branch?)21:45
notmynameI would hope it would land before feature/deep21:46
*** eharney has joined #openstack-meeting21:46
notmynameI *could* start specifically asking people :-)21:47
*** VW_ has joined #openstack-meeting21:47
mattoliverauOk, I'll start reviewing it today, maybe between tdasilva, kota_, zaitcev, m_kazuhiro and anyone else we can get enough eyes to get a consensus.21:48
notmynamemattoliverau: thank you21:48
*** Tom-Tom has joined #openstack-meeting21:48
notmynamebut I'd also like one other person specifically (instead of "and a few other people...")21:49
tdasilvanotmyname: can we putdown redhat for now?21:49
m_kazuhiroI will try to review it.21:49
*** apetrich_ has quit IRC21:49
*** zaitcev_ is now known as zaitcev21:49
notmynametdasilva: redhat in general? :-)21:49
tdasilvaheh, i mean: tdasilva, cschwede or zaitcev21:50
notmynameyeah, that's what I meant :-)21:50
notmynametdasilva: m_kazuhiro: thanks21:50
notmynameok, here's the summary21:51
zaitcevI have it on my todo list, but I am afraid to volunteer, given that I've not yet done it21:51
*** tobberydberg has joined #openstack-meeting21:51
*** VW has quit IRC21:51
notmynamemattoliverau, tdasilva (or zaitcev or cschwede) and m_kazuhiro will review feature/s3api merge to master. when they have approved it, we are all ok with that code merging to master without further review21:52
notmynamekota_: this means you or I need to propose the actual merge to master from feature/s3api. I can do that or help you if you want to21:52
zaitcevthat... sounds like no change from the usual practices, actually.21:52
*** sidx64_ has quit IRC21:52
zaitcevoh, yeah, that would be the best21:52
*** VW_ has quit IRC21:53
zaitcevthen I can comment on that review for the merge as a whole21:53
*** ykatabam has joined #openstack-meeting21:53
notmynamezaitcev: it's the same as normal patches to master. it's a bit different than what we normally do for bigger stuff on feature branches21:53
kota_either is fine to me. and i can continue to work on it to address issues from the reviewers anyway21:53
notmynameany objections from anyone? this is your chance to say something21:53
*** Tom-Tom has quit IRC21:53
notmynamekota_: I think we need to review an actual merge proposal to master. not a large patch chain21:53
kota_ah, just a merge commit21:54
notmynameall right. let's do it21:54
notmynamekota_: I can make a merge commit to master right after this meeting so it will be ready after you have breakfast21:55
kota_notmyname: thanks ;)21:55
notmynamethank you to everyone for helping me work though this and for helping us all figure out the cost/benefit tradeoffs for our ongoing work21:56
*** niknak5555 has quit IRC21:56
acolesnotmyname: thank you!21:56
notmynamethat gets us to the end of this week's meeting. maybe by the next meeting we'll have feature/s3api merged and feature/deep proposed to master!21:57
notmynamethanks for coming and for your work on swift21:57
*** openstack changes topic to "OpenStack Meetings ||"21:57
openstackMeeting ended Wed Apr 18 21:57:15 2018 UTC.  Information about MeetBot at . (v 0.1.4)21:57
openstackMinutes (text):
*** hemna_ has joined #openstack-meeting21:57
*** patchbot has left #openstack-meeting21:57
*** acoles has left #openstack-meeting21:57
*** zaitcev has left #openstack-meeting21:57
*** m_kazuhiro has quit IRC21:57
*** timburke has left #openstack-meeting21:57
*** rfolco is now known as rfolco|off21:59
*** yamamoto_ has joined #openstack-meeting22:04
*** felipemonteiro_ has joined #openstack-meeting22:06
*** yamamoto has quit IRC22:08
*** dustins_ has quit IRC22:10
*** felipemonteiro__ has quit IRC22:10
*** aeng has quit IRC22:14
*** aeng has joined #openstack-meeting22:14
*** aagate has joined #openstack-meeting22:17
*** Leo_m_ has quit IRC22:18
*** Leo_m has joined #openstack-meeting22:19
*** esberglu has quit IRC22:22
*** markstur has quit IRC22:27
*** claudiub|2 has quit IRC22:29
*** felipemonteiro_ has quit IRC22:29
*** felipemonteiro_ has joined #openstack-meeting22:29
*** rcernin has joined #openstack-meeting22:31
*** wanghao_ has quit IRC22:36
*** edmondsw has quit IRC22:41
*** jamesmcarthur has joined #openstack-meeting22:46
*** bobh has quit IRC22:47
*** bobh has joined #openstack-meeting22:47
*** tssurya has quit IRC22:51
*** bobh has quit IRC22:55
*** wanghao has joined #openstack-meeting22:56
*** wanghao has quit IRC22:58
*** wanghao has joined #openstack-meeting22:58
*** wanghao has quit IRC23:03
*** fnaval has quit IRC23:05
*** tpsilva has quit IRC23:06
*** slaweq has joined #openstack-meeting23:09
*** hamdyk has quit IRC23:10
*** raildo has quit IRC23:11
*** jamesmcarthur has quit IRC23:12
*** slaweq has quit IRC23:13
*** mjturek has quit IRC23:14
*** cloudrancher has quit IRC23:17
*** jamesmcarthur has joined #openstack-meeting23:17
*** hongbin_ has quit IRC23:18
*** andreaf has quit IRC23:18
*** andreaf has joined #openstack-meeting23:18
*** cschwede has quit IRC23:20
*** cschwede has joined #openstack-meeting23:21
*** jamesmcarthur has quit IRC23:26
*** shaohe_feng has quit IRC23:29
*** shaohe_feng has joined #openstack-meeting23:30
*** mriedem has quit IRC23:32
*** hoangcx_ has joined #openstack-meeting23:33
*** felipemonteiro_ has quit IRC23:35
*** hoangcx has quit IRC23:36
*** jamesmcarthur has joined #openstack-meeting23:38
*** kaisers has joined #openstack-meeting23:39
*** HeOS has quit IRC23:40
*** ekcs has quit IRC23:41
*** Zames has joined #openstack-meeting23:41
*** jamesmcarthur has quit IRC23:42
*** Nel1x has quit IRC23:43
*** Zames has quit IRC23:44
*** kaisers has quit IRC23:45
*** eharney has quit IRC23:49
*** hoangcx_ is now known as hoangcx23:54
*** cloudrancher has joined #openstack-meeting23:58

Generated by 2.15.3 by Marius Gedminas - find it at!