Wednesday, 2018-03-21

*** browny_ has joined #openstack-meeting00:00
*** amodi has joined #openstack-meeting00:02
*** sshank has quit IRC00:02
*** cloudrancher has quit IRC00:05
*** browny_ has quit IRC00:09
*** browny_ has joined #openstack-meeting00:24
*** song has joined #openstack-meeting00:29
*** tovin07_ has joined #openstack-meeting00:38
*** yamamoto has joined #openstack-meeting00:43
*** TxGirlGeek has quit IRC00:48
*** chenyb4 has joined #openstack-meeting00:48
*** yamamoto has quit IRC00:48
*** claudiub has quit IRC00:50
*** hongbin has joined #openstack-meeting00:51
*** armax has joined #openstack-meeting00:51
*** felipemonteiro_ has joined #openstack-meeting00:52
*** fnaval has quit IRC00:53
*** felipemonteiro__ has joined #openstack-meeting00:54
*** xuzhuang has joined #openstack-meeting00:54
*** Yipei has joined #openstack-meeting00:56
*** fnaval has joined #openstack-meeting00:56
*** felipemonteiro_ has quit IRC00:58
*** cyg has joined #openstack-meeting00:58
zhiyuan#startmeeting tricircle00:58
openstackMeeting started Wed Mar 21 00:58:54 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:58
*** openstack changes topic to " (Meeting topic: tricircle)"00:58
openstackThe meeting name has been set to 'tricircle'00:58
*** annabelleB has quit IRC00:59
zhiyuanlet's go through our features00:59
zhiyuanfirst, mutable configuration01:00
songi have pull a pr for this.01:00
zhiyuanyes, I see the patch. the launcher is updated, do we need to also update our configuration definition?01:02
*** julim has joined #openstack-meeting01:02
*** zxh has joined #openstack-meeting01:02
songyou mean our old configuration definition can not meet the new launcher?01:03
*** oddzeng has joined #openstack-meeting01:03
*** diablo_rojo has quit IRC01:04
*** browny_ has quit IRC01:04
zhiyuanI guess we need to define some configuration options as "mutable"?01:04
songoh, i follow the nova path to do it. i will see how to do it later.01:06
songs /path/patch01:06
*** chyka has joined #openstack-meeting01:07
*** harlowja has quit IRC01:07
zhiyuanfine, I think at first we can make log level mutable01:07
songand the debug level mutable?01:08
songoh that is the same sorry.01:08
zhiyuanyeah, log level as debug :)01:08
*** gcb has joined #openstack-meeting01:08
songagree with it.01:09
*** browny_ has joined #openstack-meeting01:09
zhiyuannext, new l3 networking model01:10
zhiyuanI see the updated spec, can we associate segment with AZ? so we know the segment belongs to which region01:11
*** chyka has quit IRC01:12
Yipeii think so, since segments can be associated with aggregate01:13
*** browny_ has quit IRC01:14
*** browny_ has joined #openstack-meeting01:16
*** zhujintao has joined #openstack-meeting01:16
zhiyuancool, so the information is enough01:16
zhiyuandoes routed network support updating segment after it's attached to a router?01:17
*** zhujintao1 has joined #openstack-meeting01:18
*** zhujintao1 has left #openstack-meeting01:18
*** zhujintao1 has joined #openstack-meeting01:19
Yipeinot tested, i can try it offline. but i think it is supposed to support that01:19
*** zhujintao has quit IRC01:21
zhiyuanok, I suggest you can discuss the whole process briefly in the spec. like when the local external network is created, it's created synchronously or asynchronously?01:23
zhiyuanand whether to support segment update at the first step01:24
*** oddzeng has quit IRC01:24
Yipeiok, got it01:25
zhiyuannext, security group deletion01:26
zhiyuanI see the smoke test fails with a new error01:27
*** dmacpher has joined #openstack-meeting01:27
xuzhuanghave tested in single node with two pods, tested successfully01:27
songI have review the code last day.zhuang zhuang can have a try.01:27
*** browny_ has quit IRC01:28
zhiyuan'unicode' object has no attribute 'keys', the error message01:28
xuzhuangto song, i have checked but the code is lately01:29
*** felipemonteiro_ has joined #openstack-meeting01:32
*** felipemonteiro__ has quit IRC01:32
zhiyuanthe code that raises exception is:01:33
zhiyuan"/opt/stack/new/neutron/neutron/pecan_wsgi/hooks/", line 226, in _exclude_attributes_by_policy01:33
zhiyuanfor attr_name in data.keys():01:34
zhiyuandata is supposed to be a dict, but it's a string actually01:34
songto xuzhuang not the same for check_resource_not_in_deleting01:34
zhiyuanneed to check why data is not a dict01:34
zhiyuanoh, yes, check_resource_not_in_deleting is a bit different01:39
songso may merge the new code and rerun. have a look.01:40
xuzhuangdifference in check_resource_not_in_deleting is for re-delete, joehuang commented network deleting for supporting re-delete01:40
songbut our spec is not so.01:42
*** wanghao has joined #openstack-meeting01:43
songour spec for this come from local return 404 and from user return in deleting.01:43
xuzhuangi think the difference in check_not_deleting doesn't cause smoke test fail01:45
*** yamamoto has joined #openstack-meeting01:45
zhiyuanthe implementation in the patch will raise exception to local neutron when network is in deletion, this may affect local neutron01:47
*** caowei has joined #openstack-meeting01:48
xuzhuangoh, should return ResourceNotFound?01:49
zhiyuanthat's right01:49
songand if do not use my new code will affect the logic for network resource delete.see the get_network function in
xuzhuangoh, i got it, thank you zhiyuan song01:50
zhiyuanactually, at the end of delete-network, the deleting-resource record is removed, so we can re-delete01:50
songyou are welcome!01:51
*** yamamoto has quit IRC01:51
zhiyuanbut we need to ensure deleting-resource record is always removed01:51
zhiyuanor provide a tool to manually remove the record01:52
songjust clear the database table for the deleting record?01:52
zhiyuancurrently, if exception happens during delete network, the record won't be removed since the remove is at the end of "delete network"01:53
songyes,that is true.01:53
*** amodi has quit IRC01:53
zhiyuanuse a try-catch to catch all exception so we can remove the record any time01:54
*** dangtrinhnt has joined #openstack-meeting01:54
songin the finally?01:55
zhiyuanyes, and the try-catch block should include all the "may-raise-exception" code01:55
*** browny_ has joined #openstack-meeting01:56
xuzhuangif we remove the record, local neutron may use it continuly01:56
zhiyuanremove at the end of deletion01:57
zhiyuanand so will be after the process of local neutron01:58
zhiyuanwe only use deleting-resource to lock the in-delete resource during deletion01:59
songthat is all right.01:59
zhiyuanoh, time's up. xuzhuang, please try updating the function to the latest version02:00
xuzhuangoh, hi jiawei the path haven't updated since jun 2017,02:01
xuzhuangok ok02:01
zhiyuanand for the metering patch, maybe you can talk about it in our offline group02:01
songand out team zxh have pull a path for slove the port delete. would you help to review it!thank you !02:01
zhiyuanlet's discuss this offline :)02:02
zhiyuanthanks for attending, bye~02:02
*** openstack changes topic to "OpenStack Meetings ||"02:03
openstackMeeting ended Wed Mar 21 02:03:00 2018 UTC.  Information about MeetBot at . (v 0.1.4)02:03
openstackMinutes (text):
*** zhujintao1 has left #openstack-meeting02:03
*** xuzhuang has quit IRC02:03
*** mriedem has quit IRC02:06
*** jamesmcarthur has joined #openstack-meeting02:18
*** huzhj has joined #openstack-meeting02:19
*** huzhj has quit IRC02:21
*** huzhj has joined #openstack-meeting02:21
*** huzhj has left #openstack-meeting02:22
*** kaisers_ has joined #openstack-meeting02:25
*** browny_ has quit IRC02:27
*** kaisers has quit IRC02:29
*** song has quit IRC02:30
*** wanghao has quit IRC02:34
*** browny_ has joined #openstack-meeting02:35
*** dangtrinhnt has quit IRC02:35
*** yamamoto has joined #openstack-meeting02:37
*** psachin has joined #openstack-meeting02:38
*** zhurong has joined #openstack-meeting02:40
*** Zames has joined #openstack-meeting02:45
*** salv-orl_ has joined #openstack-meeting02:48
*** andreas_s has joined #openstack-meeting02:49
*** salv-orlando has quit IRC02:51
*** Zames has quit IRC02:51
*** andreas_s has quit IRC02:53
*** cyg has quit IRC02:53
*** yamamoto has quit IRC02:55
*** felipemonteiro_ has quit IRC02:55
*** lhx_ has joined #openstack-meeting02:57
*** epico has joined #openstack-meeting03:07
*** browny_ has quit IRC03:07
*** ricolin has joined #openstack-meeting03:09
*** hongbin has quit IRC03:19
*** ricolin has quit IRC03:22
*** rbudden has quit IRC03:23
*** browny_ has joined #openstack-meeting03:24
*** browny_ has quit IRC03:28
*** iyamahat_ has quit IRC03:33
*** jamesmcarthur has quit IRC03:44
*** zhurong has quit IRC03:44
*** yamamoto has joined #openstack-meeting03:45
*** wanghao has joined #openstack-meeting03:54
*** links has joined #openstack-meeting04:00
*** links has quit IRC04:00
*** wanghao has quit IRC04:02
*** browny_ has joined #openstack-meeting04:04
*** Zames has joined #openstack-meeting04:04
*** jaypipes has quit IRC04:05
*** jaypipes has joined #openstack-meeting04:06
*** Zames has quit IRC04:06
*** yamamoto has quit IRC04:07
*** yamamoto has joined #openstack-meeting04:08
*** ekcs has joined #openstack-meeting04:11
*** Zames has joined #openstack-meeting04:18
*** Zames has quit IRC04:23
*** browny_ has quit IRC04:26
*** radeks has joined #openstack-meeting04:29
*** radeks has quit IRC04:30
*** radeks has joined #openstack-meeting04:30
*** yamamoto has quit IRC04:33
*** chyka has joined #openstack-meeting04:34
*** epico has quit IRC04:35
*** epico has joined #openstack-meeting04:35
*** harlowja has joined #openstack-meeting04:39
*** chyka has quit IRC04:39
*** tobiash has left #openstack-meeting04:41
*** cloudrancher has joined #openstack-meeting04:43
*** browny_ has joined #openstack-meeting04:46
*** wanghao has joined #openstack-meeting04:46
*** cloudrancher has quit IRC04:47
*** cloudrancher has joined #openstack-meeting04:48
*** ekcs has quit IRC04:49
*** cloudrancher has quit IRC04:49
*** cloudrancher has joined #openstack-meeting04:50
*** browny_ has quit IRC04:51
*** cloudrancher has quit IRC04:54
*** harlowja has quit IRC04:56
*** cloudrancher has joined #openstack-meeting05:02
*** browny_ has joined #openstack-meeting05:04
*** Yipei has quit IRC05:04
*** wanghao has quit IRC05:06
*** Yipei has joined #openstack-meeting05:06
*** lpetrut has joined #openstack-meeting05:06
*** cloudrancher has quit IRC05:06
*** wanghao has joined #openstack-meeting05:14
*** wanghao has quit IRC05:22
*** wanghao has joined #openstack-meeting05:22
*** wanghao has quit IRC05:23
*** armax has quit IRC05:29
*** sridharg has joined #openstack-meeting05:30
*** browny_ has quit IRC05:35
*** browny_ has joined #openstack-meeting05:41
*** claudiub has joined #openstack-meeting05:43
*** browny_ has quit IRC05:45
*** browny_ has joined #openstack-meeting05:49
*** wanghao has joined #openstack-meeting05:50
*** kaisers_ has quit IRC05:56
*** kaisers has joined #openstack-meeting05:56
*** sidx64 has joined #openstack-meeting06:02
*** masuberu has quit IRC06:04
*** sidx64 has quit IRC06:05
*** zhurong has joined #openstack-meeting06:06
*** sidx64 has joined #openstack-meeting06:07
*** sidx64 has quit IRC06:08
*** browny_ has quit IRC06:08
*** sidx64 has joined #openstack-meeting06:09
*** ihrachys has quit IRC06:15
*** lpetrut has quit IRC06:19
*** e0ne has joined #openstack-meeting06:20
*** marios has joined #openstack-meeting06:27
*** yamamoto has joined #openstack-meeting06:28
*** radeks has quit IRC06:30
*** masber has joined #openstack-meeting06:31
*** dbecker has quit IRC06:31
*** radeks has joined #openstack-meeting06:32
*** gus has quit IRC06:34
*** lpetrut has joined #openstack-meeting06:35
*** sdake has quit IRC06:35
*** gus has joined #openstack-meeting06:36
*** jbadiapa has joined #openstack-meeting06:36
*** sdake has joined #openstack-meeting06:37
*** sdake has quit IRC06:37
*** sdake has joined #openstack-meeting06:37
*** e0ne has quit IRC06:40
*** browny_ has joined #openstack-meeting06:43
*** jamesmcarthur has joined #openstack-meeting06:44
*** dbecker has joined #openstack-meeting06:46
*** jamesmcarthur has quit IRC06:48
*** gongysh has joined #openstack-meeting06:55
*** lpetrut has quit IRC06:55
*** ykatabam has quit IRC07:03
*** browny_ has quit IRC07:03
*** browny_ has joined #openstack-meeting07:03
*** browny_ has quit IRC07:04
*** kiennt26 has joined #openstack-meeting07:04
*** masber has quit IRC07:05
*** masber has joined #openstack-meeting07:06
*** JillS has quit IRC07:08
*** sidx64_ has joined #openstack-meeting07:11
*** salv-orl_ has quit IRC07:12
*** sidx64 has quit IRC07:14
*** alexchadin has joined #openstack-meeting07:14
*** salv-orlando has joined #openstack-meeting07:16
*** sidx64_ has quit IRC07:16
*** sidx64 has joined #openstack-meeting07:17
*** rcernin has quit IRC07:21
*** andreas_s has joined #openstack-meeting07:26
*** chenyb4 has quit IRC07:30
*** yamamoto has quit IRC07:32
*** chenyb4 has joined #openstack-meeting07:33
*** diablo_rojo has joined #openstack-meeting07:34
*** browny_ has joined #openstack-meeting07:35
*** ricolin has joined #openstack-meeting07:36
*** ricolin_ has joined #openstack-meeting07:38
*** ricolin has quit IRC07:41
*** dmacpher has quit IRC07:42
*** ricolin_ has quit IRC07:51
*** ricolin has joined #openstack-meeting07:51
*** priteau has joined #openstack-meeting07:52
*** yamahata has joined #openstack-meeting07:55
*** rbartal has joined #openstack-meeting08:00
*** yamamoto has joined #openstack-meeting08:00
diablo_rojo#startmeeting fc_sig08:01
openstackMeeting started Wed Mar 21 08:01:32 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:01
*** openstack changes topic to " (Meeting topic: fc_sig)"08:01
openstackThe meeting name has been set to 'fc_sig'08:01
diablo_rojogmann, mattoliverau08:01
diablo_rojoHello :)08:02
diablo_rojoAnyone else here for the First Contact SIG meeting?08:02
mattoliverauis this where we start adding people to the ping list (it is a wiki) ;)08:03
diablo_rojomattoliverau, quite possibly :)08:03
*** yamamoto has quit IRC08:03
mattoliveraushall we give another minute or so?08:04
diablo_rojoThere were a few others around last week. cmurphy masayukig and thingee ?08:04
diablo_rojomattoliverau, yeah probably a good idea08:04
mattoliverauI've seen cmurphy online (well on the Suse internal side)08:04
diablo_rojoMight be busy with some internal meeting or something.08:04
diablo_rojoThat's okay.08:04
mattoliverauCool so how's everyones week been?08:05
diablo_rojoGood so far.08:05
diablo_rojohad a workday today with annabelleB which was fun08:06
diablo_rojomattoliverau, yours?08:06
mattoliverauoh yeah, much better week then last :) finally over sickness and jetlag so feeling great :)08:06
gmann_its holiday today in tokyo and snowing since morning08:06
*** HeOS has joined #openstack-meeting08:07
*** priteau has quit IRC08:07
diablo_rojoHa ha ha can't escape the snow08:07
mattoliveraulol, sure you can just come here :)08:07
gmann_and my duty of cooking full day for wife :)08:07
diablo_rojoI saw there was a #Beastfromtheeast2 that hit Ireland this last weekend08:07
mattoliveraulol, really08:07
diablo_rojomattoliverau, yep, read an interview of the croke park staff about how they handled the last one and they mentioned us :)08:08
mattoliverauawww, thats nice, they were great!08:08
diablo_rojoWell.. in the interest of getting to bed before 2AM, I think I might get things rolling...08:08
mattoliveraukk, we've waited enough :)08:09
diablo_rojo#topic New Contributor Patches08:09
gmann_yea let's start08:09
*** openstack changes topic to "New Contributor Patches (Meeting topic: fc_sig)"08:09
diablo_rojoSo! Who did their homework?08:09
gmann_i did 3 patch review only (1 tempest, 2 nova)08:09
diablo_rojoI reviewed two I think? And then poked mattoliverau to do the swift ones.08:09
*** browny_ has quit IRC08:09
mattoliveraukinda, I tracked down some swift newbie patches.. they were kinda old. One already -2ed months ago :S08:10
diablo_rojoSo I feel like I accomplished it.08:10
diablo_rojogmann_, I think I only asked for three to get us started.08:10
diablo_rojomattoliverau, yeah that was an issue I had too, not many new ones, most were older08:10
mattoliveraubut have added the gerrit search to my main menu as a dashboard so make sure I look at it at least once a day08:10
gmann_ok then i also did :)08:11
diablo_rojoCool :)08:11
gmann_mattoliverau: nice idea, ll add to mine too for early feedback if any08:11
diablo_rojoI think, so long as there are comments and its not just empty, thats kind of where we are looking to help08:11
diablo_rojoOh man. That sentence made no sense after I typed it and hit enter08:12
diablo_rojoLet me try again.08:12
mattoliverauwelcome to my entire irc life :P08:12
diablo_rojoSo long as its not completely ignored that's what we are trying to do?08:12
diablo_rojoIs that better?08:12
diablo_rojoBasically we don't want neglected patches.08:12
gmann_yea :)08:12
diablo_rojoThings that never got updates that are siting out there is sad, but hopefully by being responsive, they will also be responsive and then we can suck them in :)08:13
mattoliverauso long as there are eyes. though we may need more coverage on other projects. But if I notice something new from another project I might just friendly ping a liasion ;)08:13
*** yamamoto has joined #openstack-meeting08:13
diablo_rojomattoliverau, yes! that is what they are there for, though our coverage still could use some help.08:14
diablo_rojoI plan to attend the project onboarding rooms and try to get some more for our list.08:14
diablo_rojoin Vancouver08:14
diablo_rojoYou are all welcome to help me :)08:14
mattoliveraugreat idea08:15
diablo_rojoI also have all the emails addresses of those speaking in them so if I don't make it, I can always email them.08:15
diablo_rojomattoliverau, I think notmyname was going to try to get you to help with Swift's room.08:15
*** ykatabam has joined #openstack-meeting08:15
*** yamamoto has quit IRC08:16
*** yamamoto has joined #openstack-meeting08:16
mattoliverauoh sure :)08:16
gmann_i can ask few of  my colleague from tacker, kolla etc to add their name08:16
mattoliverauI'd be there anyway, cause I like to meet people interested in helping08:16
diablo_rojogmann_, that would be awesome!08:17
diablo_rojowe need support for both of those projects :)08:17
gmann_sure, ll get their name tomorrow on wiki08:17
diablo_rojomattoliverau, awww aren't you nice to the newbies :)08:18
*** markstur has joined #openstack-meeting08:18
diablo_rojogmann_, awesome!08:18
diablo_rojoAnywho, ideally, we all try to do a few more reviews of these new contributor patches/poke at liaisons to pick up ones that haven't gotten attention.08:18
diablo_rojoFor next week.08:18
mattoliverauyeah, cause then I can trick em in doing the stuff I want done but don't have the time :P08:18
diablo_rojogmann_, need the link again?08:18
diablo_rojomattoliverau, that is 100% of the reason why I set storyboard up to get an outreachy intern08:19
diablo_rojo#topic Ask.OpenStack.Org Questions08:19
*** openstack changes topic to "Ask.OpenStack.Org Questions (Meeting topic: fc_sig)"08:19
mattoliverauI haven't seen anything new, but I did up vote the good answers ;)08:20
diablo_rojomattoliverau, awesome :) I saw my bait question got some answers.08:20
diablo_rojogmann_, perfect :)08:20
gmann_yea its all very old question and not new one08:21
*** Zames has joined #openstack-meeting08:21
diablo_rojogmann_, you also tried to answer some and it was pending review or something?08:21
gmann_yea that got posted.08:21
diablo_rojoCool :)08:21
diablo_rojoI honestly don't know who all the moderators are right now.08:21
diablo_rojogmann_, how many karma did you get for it?08:21
gmann_10 is needed08:22
diablo_rojoRIght, but how many did you get for answering a question?08:22
diablo_rojoOut of curiousity.08:22
gmann_for that i got only 1. but after 10 moderator is not needed08:22
mattoliverauonly 9 to go :P08:22
gmann_i think it is 1 per 1 answer08:22
*** markstur has quit IRC08:22
diablo_rojoOkay, good to know. That seems like a meager amoung.08:23
gmann_1 min08:23
gmann_i answered 2 query and seems i got 11 karma now08:23
diablo_rojoDang. I wonder what the breakdown is then.08:23
mattoliverauoh nice08:23
mattoliverauI voted one up08:23
mattoliveraumaybe that increased your karma08:24
diablo_rojoIn Launchpad you can see what the karma came from08:24
diablo_rojomattoliverau, yeah maybe08:24
mattoliverauie considered a good answer?08:24
diablo_rojoThat makes sense.08:24
diablo_rojoYou get karma for how helpful people think your answer is?08:24
gmann_i see08:24
*** wanghao has quit IRC08:24
*** chyka has joined #openstack-meeting08:24
diablo_rojoI guess there isn't much more to talk about on this topic. I think we just keep an eye out for new questions and answer them as we see them.08:25
mattoliverauoh I have 26 karma.. wow08:25
mattoliverauseems I've used this in the past08:25
mattoliveraubut can't remember when08:25
mattoliverauahh 2 swift answers08:26
*** wanghao has joined #openstack-meeting08:26
*** Zames has quit IRC08:26
diablo_rojoI somehow have 21 karma08:26
mattoliverauwe 3 can now all answer all the things. apparently I've been a member since 201408:27
diablo_rojoHa, I was still in college :)08:27
gmann_but seems like still my answer is not poste yet on this  -
*** krenczewski has quit IRC08:28
diablo_rojogmann_, strange I wonder if that one is still waiting in a moderator queue from before you had the necessary number of karma08:28
mattoliveraudiablo_rojo: I forget you're so young. get off my lawn :P08:29
gmann_yea seems so, anyways not so urgent08:29
*** chyka has quit IRC08:29
diablo_rojomattoliverau, I get that a lot. From what I understand you have sand, not a lawn :P08:29
diablo_rojogmann_, well if it doesn't post by next week I can poke around and see who manages the moderation queue08:30
mattoliverauthats true, but I can colour it green if you want08:30
gmann_diablo_rojo: sure, thanks08:30
diablo_rojoI know our intern had been, but she left a couple of months ago now.08:30
diablo_rojomattoliverau, just like the river in Chicago for St. Patrick's day.08:30
diablo_rojoOkay, anything else on this topic?08:30
*** sidx64 has quit IRC08:30
gmann_nothing from me08:31
mattoliveraunope, standard homework I guess, keep an eye on it :)08:31
diablo_rojo#Topic New Contributor of the Week08:31
*** openstack changes topic to "New Contributor of the Week (Meeting topic: fc_sig)"08:31
*** tesseract has joined #openstack-meeting08:31
diablo_rojoKinda skipped this one before, was supposed to be a part of the first topic but oh well. Circling back now.08:31
*** browny_ has joined #openstack-meeting08:31
*** sidx64 has joined #openstack-meeting08:32
diablo_rojoWas there any patch either of you reviewed or anyone you chatted with of note this last week?08:32
*** sidx64 has quit IRC08:32
mattoliverauno really anything that stands out to me.. definitly not the -2'ed patch that would have broken all of swift with a simple middleware "fix" :P08:32
gmann_not in that category actually, still waiting for author to respond which i feel they are not active may be so cannot propose their name08:33
*** sidx64 has joined #openstack-meeting08:33
mattoliveraubut I forgot about this part, so wasn't on my mind when looking08:33
diablo_rojoThe only one I had isn't super new, she just finished an outreachy internship08:34
gmann_if good progress/response from them on patch soon then i will propose the name08:34
diablo_rojoShe has been attending the woo biweekly meetings and working on some other stuff.08:34
*** sidx64 has quit IRC08:34
mattoliveraugmann_: cool08:34
diablo_rojoNot 100% familiar with what all she has done, but might be one we could propose.08:35
mattoliveraudiablo_rojo: well if she doesn't anything cool soon then add her ;)08:35
mattoliverau*does anything cool08:35
diablo_rojoI also think a more reasonable goal might be to have a contributor of the month rather than week.08:35
*** krenczewski has joined #openstack-meeting08:35
mattoliverauknowing how slow patches move in openstack land08:35
gmann_yea, month looks reasonble time08:35
mattoliverauand if we get more then 1 we can vote or have more then one ;)08:35
diablo_rojoSounds good to me. I am totally fine with having more than one- if we have that many.08:36
gmann_+1 motivation is always good08:36
diablo_rojoI expect there will be a bit of an influx here shortly with the next round of outreachy interships getting set up.08:36
mattoliveraucool :) I look forward to seeing all the awesome stuff they will do08:37
*** browny_ has quit IRC08:37
diablo_rojoOkay so maybe oikiki if I can find out more about what she actually has been working on :) And prospects of more in the future- I had three different people talking to me asking about working on StoryBoard so *fingerscrossed*08:38
diablo_rojo#topic Rollover of #openstack-101 to #openstack-dev08:38
*** openstack changes topic to "Rollover of #openstack-101 to #openstack-dev (Meeting topic: fc_sig)"08:38
diablo_rojoDoesn't seem like thingee is online right now so unless anyone has seen progress of this.. there's not much to say that I know of.08:39
diablo_rojo(he had volunteered last time)08:39
diablo_rojoIts definitely a thing we need to get done ASAP though.08:39
gmann_diablo_rojo: so final conclusion is  to move to #openstack-dev right? there were discussion on ML with off topic too :)08:40
mattoliveraumaybe we should follow up with him via the mailing list. In case he's stuck (and not here)08:40
*** masber has quit IRC08:40
diablo_rojoYeah I saw that, I asked for rationale but didn't really see any response.08:40
diablo_rojomattoliverau, yeah I can see if he has any progress on it when I wake up tomorrow. Or if he needs help or anything.08:41
diablo_rojoAnything else from either of you on this topic?08:41
mattoliveraumy vote for what it's worth is for openstack-dev. Because openstack is _very_ ops centric. And like fungi says dev means so much more in my opinion then just developer.08:42
diablo_rojoMy rationale as well.08:42
diablo_rojoThe FC SIG was also created initially to help with new contributors looking to help develop openstack.08:42
diablo_rojoAnother reason why I argue for #openstack-dev08:43
diablo_rojo#topic Forum Topics08:43
*** openstack changes topic to "Forum Topics (Meeting topic: fc_sig)"08:43
diablo_rojoSo, despite being originally focused on development, it would be great to get a few operators involved and at least aware of what we do/what resources exist08:44
diablo_rojoSo if we see people struggling, we can point them to those operator liaison people.08:44
diablo_rojoHave project liaison types but for operators08:44
diablo_rojoWe can point them at the ops ml, but I see a lot of things go unanswered there08:44
diablo_rojoand in the regular openstack ml08:44
diablo_rojoLong story short, think we should do a forum session08:45
mattoliverauPlus sometimes it's good to ask an op about what a dev is working on, I've found it hugely helpful at times08:45
*** lpetrut has joined #openstack-meeting08:45
mattoliverauie, does this sound stupid.. or does this config option actually make sense.08:46
mattoliverauor how do you tune that thing so we can look at auto-tuning08:46
*** wanghao has quit IRC08:46
diablo_rojomattoliverau, agreed. I think there is a huge void that separates the two groups and there doesn't need to be. OpenStack would benefit greatly from the groups being more tightly coupled.08:46
gmann_diablo_rojo: we gave little intro in tokyo ops meetup about Firstcontact SIG  and about required operator involvement also08:46
diablo_rojogmann_, oh awesome!08:46
diablo_rojoHow did that go?08:46
gmann_not much interest :) but they know it now08:47
diablo_rojoKnowing is half the battle I guess?08:47
diablo_rojoI think it would be good for us to meet at the forum to go over resources again and kind of do a state of the union at the very least08:48
diablo_rojonot sure how we can frame it to pull in more operators08:48
diablo_rojoso I am all ears on that aspect08:48
*** phil has joined #openstack-meeting08:48
diablo_rojoCould really use some more operator input on the contributor guide in particular.08:48
*** lpetrut has quit IRC08:48
*** lpetrut_ has joined #openstack-meeting08:48
*** phil is now known as Guest2228108:49
diablo_rojoMaybe something to stew on for next time.08:49
mattoliverauSwift has the ops runbook in our documentation08:49
diablo_rojoForum submissions just opened so we have some time to figure out how to frame it08:49
*** markstur has joined #openstack-meeting08:49
mattoliverauthat was gifted to us from the HP guys when they moved on08:49
diablo_rojomattoliverau, I will have to check that out.08:50
gmann_i think it is great to have this time so that we can get early feedback08:50
*** claudiub has quit IRC08:50
diablo_rojoSee if I can abstact anything into the guide.08:50
diablo_rojogmann_, +108:50
cmurphyoops sorry :( I was getting a new workstation sorted out08:50
diablo_rojocmurphy, no worries :)08:50
diablo_rojoNew lappys are always an allowed distraction in my book.08:51
diablo_rojoI think we are onto the last topic I had? If no one has anything else about a forum session for now.08:51
*** tesseract has quit IRC08:51
diablo_rojoI suppose I can make an etherpad for planning and send that out for people to put ideas into08:52
mattoliverauLink it on the wiki as well08:52
gmann_yea, about to write ^^ that08:52
*** tesseract has joined #openstack-meeting08:52
gmann_it will hep to get more ideas08:52
diablo_rojomattoliverau, can do08:52
* diablo_rojo read gmann_ 's previous message correctly and then saw the 'help' and got confused and concerned simultaneously08:53
gmann_heh :)08:53
diablo_rojoOkay, last topic.08:53
diablo_rojo#topic sandbox & ci-sandbox patches08:53
*** openstack changes topic to "sandbox & ci-sandbox patches (Meeting topic: fc_sig)"08:54
*** tesseract has quit IRC08:54
diablo_rojoSeems there are a lot of welcome new contributor patches here...08:54
*** markstur has quit IRC08:54
diablo_rojoBut not many of them are legit patches.08:54
diablo_rojoAnd a lot of them have been around for years.08:54
diablo_rojoDoes anyone know if its cool if we just go and Abandon a bunch of them?08:54
diablo_rojoOr who's job that is?08:55
diablo_rojoAlso, 5 min left.08:55
diablo_rojoTHEN I GET TO SLEEP YAY08:55
cmurphywhy do they need to be abandoned? it doesn't hurt anyone to leave them there08:55
diablo_rojocmurphy, I guess I have no real reason other than my OCD saying we need to clean them up08:56
diablo_rojoA need to have my inbox at 0 before I go to bed.08:56
diablo_rojoAnd to clear all phone notifications before setting it down.08:56
gmann_we do in projects also. cleanup old patches by abandoning them with msg to author about they can restore if needed08:57
diablo_rojogmann_, yeah that was my thought.08:57
diablo_rojoI guess I can look at the gerrit repo to see who has core status08:57
*** tesseract has joined #openstack-meeting08:57
gmann_and in our caes they not need to be restore, so we can have a very friendly and thanks msg with FirstContact SIG link08:57
cmurphyeveryone has core on sandbox08:57
diablo_rojogmann_, yeah I like that idea08:58
mattoliverauwell now that's it filtered out of the gerrit search I don't see them, so I can happily ignore em ;P08:58
diablo_rojoDon't need to be particularly aggressive with cleaning them up, but if its >18 months..08:59
mattoliveraumaybe a part of the OUI training can be to abandon your sandbox patches when your done.. so you know how to ;)08:59
gmann_yea, or we clean that time only with merging them08:59
diablo_rojomattoliverau, or to talk about how its not a bad thing, it happens08:59
gmann_merging new one during OUI08:59
diablo_rojogmann_, yeah09:00
diablo_rojoSomething we can talk about in the next OUI meeting for sure09:00
*** sidx64 has joined #openstack-meeting09:00
diablo_rojoLooks like we are at time.09:00
diablo_rojoSo everyone try to review another couple patches or delegate a few to a project liaison09:00
diablo_rojoAnd thats all I have for this week :)09:01
mattoliverauOh I can deligate.. but probably should ask them first :P09:01
mattoliveraunight o/09:01
*** openstack changes topic to "OpenStack Meetings ||"09:01
openstackMeeting ended Wed Mar 21 09:01:29 2018 UTC.  Information about MeetBot at . (v 0.1.4)09:01
openstackMinutes (text):
diablo_rojomattoliverau, night night o/09:01
*** Yipei has left #openstack-meeting09:01
diablo_rojocmurphy, did you want to be on the ping list?09:01
gmann_thanks diablo_rojo and gn09:02
cmurphydiablo_rojo: yes that would help me09:02
*** sidx64 has quit IRC09:02
diablo_rojoI can add you tomorrow or if you want to add yourself:
mattoliveraudiablo_rojo: go to sleep09:02
cmurphyi'll add, good night diablo_rojo09:02
diablo_rojogmann_, Night! Have a good rest of your evening.09:02
mattoliveraucmurphy: have fun setting up your new workstation :)09:02
*** arxcruz|off is now known as arxcruz09:04
*** zhurong has quit IRC09:04
*** marios has quit IRC09:05
*** markstur has joined #openstack-meeting09:05
*** marios has joined #openstack-meeting09:05
*** browny_ has joined #openstack-meeting09:08
*** sidx64 has joined #openstack-meeting09:09
*** browny_ has quit IRC09:10
*** browny_ has joined #openstack-meeting09:10
*** markstur has quit IRC09:10
*** zhurong has joined #openstack-meeting09:14
*** electrofelix has joined #openstack-meeting09:14
*** masber has joined #openstack-meeting09:20
*** jesusaur has quit IRC09:21
*** jesusaur has joined #openstack-meeting09:24
*** browny_ has quit IRC09:26
*** lhx_ has quit IRC09:27
*** lhx_ has joined #openstack-meeting09:27
*** browny_ has joined #openstack-meeting09:28
*** gongysh has quit IRC09:30
*** Zames has joined #openstack-meeting09:41
*** yamamoto has quit IRC09:42
*** Zames has quit IRC09:43
*** yamamoto has joined #openstack-meeting09:43
*** Zames has joined #openstack-meeting09:46
*** yamamoto has quit IRC09:48
*** yamamoto has joined #openstack-meeting09:48
*** yamamoto has quit IRC09:48
*** Zames has quit IRC09:48
*** browny_ has quit IRC09:48
*** Zames has joined #openstack-meeting09:49
*** Zames has quit IRC09:52
*** Zames has joined #openstack-meeting09:53
*** browny_ has joined #openstack-meeting09:54
*** claudiub has joined #openstack-meeting09:55
*** browny_ has quit IRC09:57
*** Zames has quit IRC10:00
*** sridharg has quit IRC10:03
*** sidx64 has quit IRC10:04
*** sidx64 has joined #openstack-meeting10:05
*** egallen has joined #openstack-meeting10:06
*** priteau has joined #openstack-meeting10:11
*** epico has quit IRC10:14
*** browny_ has joined #openstack-meeting10:18
*** browny_ has quit IRC10:23
*** tovin07_ has quit IRC10:23
*** marios has quit IRC10:25
*** marios has joined #openstack-meeting10:25
*** alexchadin has quit IRC10:27
*** alexchadin has joined #openstack-meeting10:28
*** alexchadin has quit IRC10:30
*** alexchadin has joined #openstack-meeting10:35
*** sidx64 has quit IRC10:36
*** egallen has quit IRC10:36
*** egallen has joined #openstack-meeting10:37
*** tssurya has joined #openstack-meeting10:37
*** sapd_ has quit IRC10:38
*** sapd has joined #openstack-meeting10:39
*** sidx64 has joined #openstack-meeting10:40
*** markstur has joined #openstack-meeting10:40
*** fzdarsky has joined #openstack-meeting10:41
*** erlon has joined #openstack-meeting10:43
*** chenyb4 has quit IRC10:43
*** markstur has quit IRC10:45
*** egallen has quit IRC10:45
*** alexchadin has quit IRC10:46
*** yamamoto has joined #openstack-meeting10:48
*** caowei_ has joined #openstack-meeting10:50
*** caowei has quit IRC10:51
*** yamahata has quit IRC10:52
*** yamamoto has quit IRC10:54
*** caowei_ has quit IRC10:54
*** browny_ has joined #openstack-meeting10:55
*** zhurong has quit IRC10:55
*** yamamoto has joined #openstack-meeting10:56
*** e0ne has joined #openstack-meeting10:59
*** yamamoto has quit IRC11:01
*** chyka has joined #openstack-meeting11:02
*** yamamoto has joined #openstack-meeting11:02
*** numans is now known as numans_afk11:05
*** yamamoto has quit IRC11:06
*** chyka has quit IRC11:07
*** fnaval has quit IRC11:09
*** TxGirlGeek has joined #openstack-meeting11:14
*** yamamoto has joined #openstack-meeting11:16
*** yamamoto has quit IRC11:16
*** alexchadin has joined #openstack-meeting11:16
*** armax has joined #openstack-meeting11:16
*** TxGirlGeek has quit IRC11:19
*** egallen has joined #openstack-meeting11:20
*** armax has quit IRC11:21
*** cschwede has joined #openstack-meeting11:23
*** diman has joined #openstack-meeting11:25
*** kopecmartin has joined #openstack-meeting11:26
*** egallen has quit IRC11:27
*** sidx64 has quit IRC11:29
*** numans_afk is now known as numans11:29
*** sidx64 has joined #openstack-meeting11:33
*** dmacpher has joined #openstack-meeting11:34
*** sidx64 has quit IRC11:34
*** claudiub has quit IRC11:35
*** claudiub has joined #openstack-meeting11:36
*** diman has quit IRC11:37
*** rbudden has joined #openstack-meeting11:38
*** e0ne has quit IRC11:42
*** diman has joined #openstack-meeting11:43
*** browny__ has joined #openstack-meeting11:43
*** markstur has joined #openstack-meeting11:44
*** browny_ has quit IRC11:44
*** browny_ has joined #openstack-meeting11:45
*** Zames has joined #openstack-meeting11:45
*** diman has quit IRC11:47
*** browny__ has quit IRC11:48
*** yamamoto has joined #openstack-meeting11:48
*** Zames has quit IRC11:48
*** markstur has quit IRC11:48
*** browny__ has joined #openstack-meeting11:51
*** yamamoto has quit IRC11:52
*** browny_ has quit IRC11:53
*** sidx64 has joined #openstack-meeting11:53
*** sidx64 has quit IRC11:55
*** sidx64 has joined #openstack-meeting11:56
*** sidx64 has quit IRC11:58
*** tpsilva has joined #openstack-meeting11:59
*** e0ne has joined #openstack-meeting12:00
*** erlon has quit IRC12:02
*** e0ne has quit IRC12:02
*** rbudden has quit IRC12:03
*** ansmith has joined #openstack-meeting12:03
*** yamamoto has joined #openstack-meeting12:03
*** sidx64 has joined #openstack-meeting12:04
*** rfolco has joined #openstack-meeting12:05
*** sidx64 has quit IRC12:06
*** dprince has joined #openstack-meeting12:06
*** pchavva has joined #openstack-meeting12:07
*** yamamoto has quit IRC12:08
*** erlon has joined #openstack-meeting12:08
*** sidx64 has joined #openstack-meeting12:10
*** sidx64 has quit IRC12:11
*** raildo has joined #openstack-meeting12:12
*** raildo has quit IRC12:14
*** e0ne has joined #openstack-meeting12:15
*** yamamoto has joined #openstack-meeting12:18
*** lhx_ has quit IRC12:20
*** yamamoto has quit IRC12:22
*** efried has quit IRC12:23
*** sambetts|afk is now known as sambetts12:24
*** efried has joined #openstack-meeting12:24
*** raildo has joined #openstack-meeting12:24
*** sidx64 has joined #openstack-meeting12:27
*** dprince has quit IRC12:29
*** artom has joined #openstack-meeting12:29
*** sgrasley1 has quit IRC12:30
*** artom has quit IRC12:31
*** yamamoto has joined #openstack-meeting12:33
*** artom has joined #openstack-meeting12:34
*** gman-tx has joined #openstack-meeting12:36
*** sridharg has joined #openstack-meeting12:38
*** yamamoto has quit IRC12:38
*** edmondsw has joined #openstack-meeting12:40
*** VW has joined #openstack-meeting12:41
*** gcb has quit IRC12:42
*** yamamoto has joined #openstack-meeting12:48
*** jamesmcarthur has joined #openstack-meeting12:50
*** chenyb4 has joined #openstack-meeting12:50
*** yamamoto has quit IRC12:53
*** jamesmcarthur has quit IRC12:53
*** Guest22281 has quit IRC12:57
*** diman has joined #openstack-meeting12:57
*** diman has quit IRC12:57
*** zhongjun has quit IRC12:59
*** browny__ has quit IRC13:00
*** felipemonteiro_ has joined #openstack-meeting13:01
*** egallen has joined #openstack-meeting13:01
*** eharney has joined #openstack-meeting13:01
*** felipemonteiro__ has joined #openstack-meeting13:02
*** yamamoto has joined #openstack-meeting13:03
*** mjturek has joined #openstack-meeting13:03
*** SerenaFeng has joined #openstack-meeting13:04
*** dprince has joined #openstack-meeting13:05
*** SerenaFeng has quit IRC13:05
*** SerenaFeng has joined #openstack-meeting13:06
*** felipemonteiro_ has quit IRC13:06
*** diman has joined #openstack-meeting13:07
*** yamamoto has quit IRC13:08
*** rbudden has joined #openstack-meeting13:09
*** egallen has quit IRC13:09
*** SerenaFeng has quit IRC13:12
*** diman has quit IRC13:14
*** diman has joined #openstack-meeting13:16
*** armax has joined #openstack-meeting13:17
*** dustins has joined #openstack-meeting13:18
*** yamamoto has joined #openstack-meeting13:18
*** fnaval has joined #openstack-meeting13:20
*** diman has quit IRC13:20
*** mriedem has joined #openstack-meeting13:20
*** armax has quit IRC13:22
*** _pewp_ has quit IRC13:22
*** yamamoto has quit IRC13:22
*** alexchad_ has joined #openstack-meeting13:24
*** alexchadin has quit IRC13:25
*** awaugama has joined #openstack-meeting13:26
*** tssurya has quit IRC13:26
*** edleafe- has joined #openstack-meeting13:28
*** edleafe has quit IRC13:29
*** edleafe- is now known as edleafe13:29
*** browny_ has joined #openstack-meeting13:30
*** eharney has quit IRC13:30
*** diman_ has joined #openstack-meeting13:31
*** caowei has joined #openstack-meeting13:31
*** yamamoto has joined #openstack-meeting13:33
*** designbybeck has joined #openstack-meeting13:34
*** diman_ has quit IRC13:35
*** browny_ has quit IRC13:36
*** browny_ has joined #openstack-meeting13:37
*** yamamoto has quit IRC13:38
*** tssurya has joined #openstack-meeting13:40
*** browny_ has quit IRC13:42
*** dtrainor has quit IRC13:42
*** dklyle has joined #openstack-meeting13:44
*** david-lyle has quit IRC13:44
*** yamamoto has joined #openstack-meeting13:48
*** psachin has quit IRC13:48
*** dtrainor has joined #openstack-meeting13:48
*** gman-tx has quit IRC13:52
*** yamamoto has quit IRC13:53
*** ykatabam has quit IRC13:54
*** alexchad_ is now known as alexchadin13:54
*** rbudden has quit IRC13:58
*** dtrainor has quit IRC13:58
*** rbudden has joined #openstack-meeting14:00
*** cloudrancher has joined #openstack-meeting14:01
*** sgrasley1 has joined #openstack-meeting14:02
*** gman-tx has joined #openstack-meeting14:03
*** bobh has joined #openstack-meeting14:03
*** yamamoto has joined #openstack-meeting14:03
*** SerenaFeng has joined #openstack-meeting14:05
*** yamamoto has quit IRC14:07
*** hongbin has joined #openstack-meeting14:08
*** simon-AS5591 has joined #openstack-meeting14:09
*** aagate has joined #openstack-meeting14:10
*** browny_ has joined #openstack-meeting14:10
*** Zames has joined #openstack-meeting14:14
*** annabelleB has joined #openstack-meeting14:14
*** Zames has quit IRC14:16
*** yamamoto has joined #openstack-meeting14:18
*** esberglu has joined #openstack-meeting14:19
*** tssurya has quit IRC14:20
*** yamamoto has quit IRC14:23
*** lhx_ has joined #openstack-meeting14:23
*** rpioso|afk is now known as rpioso14:25
*** chenyb4 has quit IRC14:26
*** diman has joined #openstack-meeting14:32
*** gouthamr has joined #openstack-meeting14:32
*** yamamoto has joined #openstack-meeting14:33
*** tssurya has joined #openstack-meeting14:34
*** mjturek has quit IRC14:35
*** mjturek has joined #openstack-meeting14:35
*** diman has quit IRC14:37
*** yamamoto has quit IRC14:38
*** egallen has joined #openstack-meeting14:40
*** browny_ has quit IRC14:42
*** armax has joined #openstack-meeting14:44
*** yamamoto has joined #openstack-meeting14:46
*** yamamoto has quit IRC14:46
*** felipemonteiro__ has quit IRC14:47
*** felipemonteiro__ has joined #openstack-meeting14:47
*** sidx64 has quit IRC14:49
*** browny_ has joined #openstack-meeting14:49
*** alexchadin has quit IRC14:50
*** felipemonteiro_ has joined #openstack-meeting14:52
*** markstur has joined #openstack-meeting14:53
*** browny_ has quit IRC14:54
*** rbudden has quit IRC14:55
*** felipemonteiro__ has quit IRC14:55
*** rbudden has joined #openstack-meeting14:57
*** markstur has quit IRC14:57
*** yamahata has joined #openstack-meeting15:00
*** amodi has joined #openstack-meeting15:00
*** iyamahat has joined #openstack-meeting15:00
*** dtrainor has joined #openstack-meeting15:02
*** browny_ has joined #openstack-meeting15:03
*** SerenaFeng has quit IRC15:06
*** felipemonteiro__ has joined #openstack-meeting15:07
*** sidx64 has joined #openstack-meeting15:07
*** browny_ has quit IRC15:08
*** felipemonteiro_ has quit IRC15:11
*** electrofelix has quit IRC15:12
*** sidx64 has quit IRC15:14
*** ykatabam has joined #openstack-meeting15:17
*** ykatabam has quit IRC15:17
*** sridharg has quit IRC15:22
*** sridharg has joined #openstack-meeting15:25
*** sridharg has quit IRC15:25
*** sridharg has joined #openstack-meeting15:25
*** egallen has quit IRC15:28
*** VW_ has joined #openstack-meeting15:28
*** egallen has joined #openstack-meeting15:30
*** kbyrne has quit IRC15:30
*** egallen has quit IRC15:30
*** VW has quit IRC15:30
*** browny_ has joined #openstack-meeting15:32
*** VW_ has quit IRC15:32
*** VW has joined #openstack-meeting15:32
*** yamamoto has joined #openstack-meeting15:33
*** diman has joined #openstack-meeting15:34
*** kbyrne has joined #openstack-meeting15:35
*** browny_ has quit IRC15:38
*** diman has quit IRC15:39
*** browny_ has joined #openstack-meeting15:40
*** sgrasley1 has quit IRC15:42
*** kiennt26_ has joined #openstack-meeting15:46
*** eharney has joined #openstack-meeting15:48
*** VW has quit IRC15:50
*** chyka has joined #openstack-meeting15:50
*** VW has joined #openstack-meeting15:50
*** sgrasley1 has joined #openstack-meeting15:52
*** mjturek has quit IRC15:56
*** bswartz has joined #openstack-meeting15:56
*** mjturek has joined #openstack-meeting15:56
*** walshh has joined #openstack-meeting15:57
*** mjturek has quit IRC15:57
*** caowei has quit IRC15:58
*** rbartal has quit IRC15:58
*** munimeha1 has joined #openstack-meeting15:58
*** iyamahat has quit IRC15:58
*** caowei has joined #openstack-meeting15:58
jungleboyj#startmeeting Cinder16:00
openstackMeeting started Wed Mar 21 16:00:22 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
*** yamahata has quit IRC16:00
jungleboyjCourtesy ping:  jungleboyj DuncanT diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlontpsilva patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro lpetrut16:00
geguileohi! o/16:00
*** efried is now known as efried_rollin16:01
jungleboyjHello everyone.16:01
jungleboyjDon't have  a large agenda today so I am sure we will run out of time.16:02
jungleboyje0ne:  Thank you.16:02
jungleboyjsmcginnis:  Is here.  Now I can start.  ;-)16:03
jungleboyj#topic announcements16:03
*** openstack changes topic to "announcements (Meeting topic: Cinder)"16:03
jungleboyjSo, first announcement is a reminder that we have an etherpad for Forum Topic planning:16:04
jungleboyjSo far the only ideas in there are the ones I have put.  Anyone have proposals?16:04
* jungleboyj hears crickets16:04
jungleboyjI will need to be proposing things soon, so if you have topics, please add them.16:05
jungleboyjSo, I also wanted to note that I have seen an uptick in reviews from some people from the PTG.16:06
jungleboyjThank you for the help!16:06
jungleboyjIt is appreciated.  We have been able to get a new driver merged and make progress on our specs.16:06
jungleboyjThink it is a good start for Rocky.16:06
SwansonSo we are not off to a Rocky start? *chortle*16:07
*** mjturek has joined #openstack-meeting16:07
* jgriffith throws a mule at Swanson 16:07
jungleboyjjgriffith:  ++16:08
jgriffithfollowed by a bag of snakes16:08
jungleboyjSo, also, just a reminder to register for the Vancouver Summit if you are able to go.  Hope to see a number of you there.16:08
jungleboyjOk, moving on before jgriffith  Gets really violent16:09
jungleboyj#topic Rocky Priorities review ...16:09
*** openstack changes topic to "Rocky Priorities review ... (Meeting topic: Cinder)"16:09
jungleboyjNot a lot of activity in here this week.16:10
jungleboyje0ne:  Any luck getting the spec for generic backup updated?16:10
jungleboyjSorry if I missed it.16:10
*** mjturek has quit IRC16:10
e0nejungleboyj: I'm working on it. hope to finish it in next two days16:10
*** sgrasley1 has quit IRC16:11
*** caowei has quit IRC16:11
jungleboyje0ne:  Sounds good.  I don't think I have seen reviews come through for other patches that need to be added to the list.16:11
*** sgrasley1 has joined #openstack-meeting16:11
jungleboyje0ne: eharney smcginnis  Appreciate help getting stuff added in there if you see it.16:11
jungleboyjOk, don't have much more to dig into there then.16:13
jungleboyj#topic HA Check-in16:13
*** openstack changes topic to "HA Check-in (Meeting topic: Cinder)"16:13
*** browny_ has quit IRC16:13
jungleboyjgeguileo:  Do you have HA all working and tested?16:13
* jungleboyj giggles16:13
jungleboyjgeguileo:  Any progress to report?16:14
geguileoI've just started looking at an HA A-A replication issue that Jon Bernard brought to my attention16:14
geguileoI'll start working on the document after I fix those issues16:15
jungleboyjgeguileo:  That makes sense.16:15
jungleboyjIt is good we are finding bugs and getting those fixed before more people start using it.16:16
*** andreas_s has quit IRC16:16
jungleboyjgeguileo:  Thank you for continuing to push that.16:17
*** aagate has quit IRC16:17
jungleboyj#topic New Driver Support Matrix ...16:17
*** openstack changes topic to "New Driver Support Matrix ... (Meeting topic: Cinder)"16:17
jungleboyjSo, I am working on putting together the new feature-classification based version of the Support Matrix16:17
jungleboyjThis is a mind numbing task but I think the result is going to be great.16:18
*** boden has joined #openstack-meeting16:18
*** browny_ has joined #openstack-meeting16:18
jungleboyjI am finding that the old matrix on the Wiki is very out of date with drivers listed that don't exist anymore.16:18
jungleboyjI am also find that many drivers are completely undocumented.16:18
e0nejungleboyj: will it be autogenerated from sources?16:19
smcginnisI think that has been very poorly maintained for some time.16:19
* jungleboyj glares at the Huawei people16:19
jungleboyje0ne: No, but it will be generated from an INI file that is easily maintained.16:19
jungleboyjWhen a driver changes we just need to make sure the change also updates the matrix.16:19
e0nejungleboyj: sounds good16:19
jungleboyjMuch better than the current process.16:20
jungleboyjJust getting it created is a bit of a nightmare.16:20
smcginnisI could see this eventually being groundwork for automatically generating that ini source, but we probably have a lot of work to do first before we can get there.16:20
*** rledisez has quit IRC16:20
jungleboyjsmcginnis:  ++16:20
jungleboyjBaby steps.16:20
jungleboyjSo, my question to the team is as follows.16:21
jungleboyjA number of drivers have, in the Wiki, multiple entries for one driver based on model number.16:21
jungleboyjDell/EMC and Huawei ... Is that something I should be reflecting in what I am putting in this new support matrix?16:21
smcginnisThere may be differences.16:22
*** browny_ has quit IRC16:22
jgriffithjungleboyj: sadly it seems like those are different devices/drivers so you probably will have to16:22
smcginnisMaybe put them all in for now, then we can see if we can clean it up some once it's there?16:22
geguileoI agree with jgriffith16:22
geguileodifferent entries16:23
jungleboyjjgriffith:  :-(  ok.16:23
jungleboyjI was guessing that was the answer.16:23
jungleboyjsmcginnis:  I am going to need some help mapping the Huawei entries in the Wiki to drivers.16:23
smcginnisjungleboyj: I probably will too.16:24
jungleboyjtommylikehu:  ^^16:24
smcginnisjungleboyj: Maybe we can get some... yeah, tommylikehu. :)16:24
*** kopecmartin has quit IRC16:24
jgriffithjungleboyj: sorry Charlie16:24
*** mjturek has joined #openstack-meeting16:24
jungleboyjjgriffith:  It is ok.  This is going to be a great improvement once done.16:25
jungleboyjOk, so, I will get all the different models represent.  Probably going to be another week or so before I have a WIP pushed up for people to look at.16:26
*** andreas_s has joined #openstack-meeting16:26
jungleboyjThen will need some help from people to verify it for Vendor drivers.16:26
*** masber has quit IRC16:27
jungleboyjAny questions or comments there?16:27
smcginnisThanks for working on that.16:28
jungleboyjsmcginnis:  Welcome.  It will be good.16:28
jungleboyj#topic Open Discussion16:29
*** openstack changes topic to "Open Discussion (Meeting topic: Cinder)"16:29
jungleboyjThat was all I had for this week.  Anything else people want to talk about?16:29
jungleboyjIs tommylikehu  Not here?16:30
jgriffithWorking on trying to get cinderclient python-bindings to actually work16:30
jungleboyjHe is pushing the backup across AZ issue.16:30
jungleboyjjgriffith:  How so?16:30
jgriffithIf anybody else has ever gone down that rabbit hole give me a ping16:30
jgriffithjungleboyj: it doesn't work currently/still/again16:30
*** andreas_s has quit IRC16:30
* jungleboyj has obviously not been down that rabbit hole.16:31
jgriffithcan't authenticate16:31
smcginnisjungleboyj: It's not backup across AZs, if you are referring to the latest ML discussion.16:31
jgriffithwe have an outdated example in the docs still and on the github readme:
jungleboyjsmcginnis:  Shared backups?16:31
smcginnisjungleboyj: There's some customer desire (or a customer has been told this would be the way to do it) for sharing a backup.16:31
*** egallen has joined #openstack-meeting16:32
*** boden has left #openstack-meeting16:32
jungleboyjsmcginnis:  Thank you.  Yes, I misspoke there.16:32
jungleboyjjgriffith:  Ok.  Wasn't aware that was broken.  Thanks for taking a look at it.16:32
smcginnisSo it could be across AZs, but it is also across owners.16:32
*** browny_ has joined #openstack-meeting16:33
jgriffithjungleboyj: it's "my pleasure"16:33
jgriffithok.. not really16:33
jungleboyjsmcginnis:  What are your thoughts there?16:33
smcginnisjgriffith: What's the issue? It can't authenticate as a library, or even as a CLI?16:33
jungleboyjjgriffith:  You aren't selling me there.16:33
jgriffithsmcginnis: as a lib16:33
smcginnisjungleboyj: My feedback was pretty much what has been stated. That's not what backup was intended for, no matter the similarities to AWS snapshots. Glance images sound like the more correct solution for OpenStack.16:34
jgriffithsomething with our client init and newer versions of keystone16:34
smcginnisjgriffith: That's not good.16:34
smcginniskeystoneauth changes?16:34
jgriffithtried using the keystone v1 session method as well, and ran into problems there.16:34
*** diman has joined #openstack-meeting16:34
jgriffithYeah, most likely; but I think *old* Keystone changes... not sure16:35
jungleboyjsmcginnis:  ++ Yeah, using Glance makes more sense.16:35
jungleboyjlbragstad:  Any input here ^^^16:35
jgriffithhopefully I'll figure it out today and I can update our docs16:35
jungleboyjSounds good.16:35
smcginnisjungleboyj: Err, I mean, we should definitely share backups. It's what the customer wants.16:35
* lbragstad reads scrollback16:36
jungleboyjThanks to everyone for making doc changes and dealing with me harping on that.16:36
smcginnislbragstad: Mix discussions. The parts about authentication not working for cinderclient as a lib.16:36
jungleboyjsmcginnis:  You also are not selling me on that statement.16:36
smcginnisjungleboyj: :)16:36
* jungleboyj is all for making customers happy but not increasing complexity.16:36
lbragstadjgriffith: ah - are you using keystoneauth with cinder client?16:37
*** kiennt26_ has quit IRC16:37
*** browny_ has quit IRC16:37
jgriffithlbragstad: *trying* to16:37
jgriffithbut in general just trying to use python bindings to init a Client16:37
lbragstadok - what does cinderclient use now to do authentication?16:38
geguileosmcginnis: it's shared backups or transferring backups?16:38
jungleboyjgeguileo:  Shared.16:38
smcginnisgeguileo: Shared.16:38
lbragstadjgriffith: like - directly?16:38
*** gyee has joined #openstack-meeting16:38
smcginnisgeguileo: So I agree with your last bit there, but that's not what he's asking for.16:38
jgriffithlbragstad: there are two options... the first is direct via Client.__init__16:39
smcginnisLike snapshots, it may make sense to be able to transfer backups.16:39
geguileosmcginnis: we don't allow sharing volumes, right?16:39
smcginnisgeguileo: Right. They have to transfer them.16:39
jgriffithThe other is going out to auth_v1 and creating a session, then trying to feed that in to Client init16:39
geguileosmcginnis: then same thing for backups16:39
*** diman has quit IRC16:39
smcginnisSo really the only "sharing" is glance images, AFAIK.16:39
geguileosmcginnis: as it should be16:39
smcginnisgeguileo: I agree. I mean no, I don't. Yes I do. I'm trapped! :)16:40
jungleboyjsmcginnis:   He he he16:40
jgriffithlbragstad: kinda like this:
* smcginnis hopes his boss doesn't read this16:40
jgriffithlbragstad: main difference being Nova works, Cinder doesn't :)16:40
lbragstadoh - sure16:40
jungleboyjsmcginnis:  Don't worry, Lenovo is hiring.16:40
smcginnisjungleboyj: LOL16:40
geguileosmcginnis: I don't know if there would be a way to share volumes using the upload to glance in cinder that actually creates a cinder volume16:41
*** dmacpher has quit IRC16:41
lbragstadjgriffith: so - you are using ksa to get auth, and build a session, but when you pass that to clientclient.client.Client, it blows up?16:41
jungleboyjsmcginnis:  Does Glance howere solve his problem of having the images available in multiple AZs.16:41
geguileosmcginnis: I haven't tested it, but they could use image_upload_use_cinder_backend16:42
geguileosmcginnis: They probably do...16:42
jgriffithlbragstad: correct, or if I try and use the other method and feed OS vars into the init that fails to auth16:42
lbragstadjgriffith: do you have a trace from cinderclient?16:42
jgriffithin other words, Cinder Client is just not right16:42
* jungleboyj is loving the split brain meeting here.16:42
*** egallen has quit IRC16:42
jgriffithI don't but I can ping you later with info if you want to have a look and help out?16:42
lbragstadjgriffith: sure - getting clients to consume sessions from ksa should be a pretty established pattern16:43
geguileojgriffith: I think my conversation with smcginnis is over now, since I'm ok to do transfers, but not sharing16:43
smcginnisMe too.16:43
jungleboyjgeguileo: smcginnis  So we are in agreement that we still say no to that request and then smcginnis  will have terrets afterwards.16:44
lbragstadjgriffith: i know we decoupled that approach keystoneclient a while back when we moved everything to ksa (since keystoneclient used to build it's own sessions)16:44
lbragstadapproach with*16:44
geguileojungleboyj: I don't want shared backups for sure16:44
jungleboyjThat would seem to break the security model for Volumes as the backups are of Volumes.16:45
*** mjturek has quit IRC16:46
*** mjturek has joined #openstack-meeting16:47
jungleboyjOk.  So, things have quited down.16:47
jungleboyjlbragstad:  Thanks for helping out jgriffith16:47
lbragstadyeah - no problem, let me know if you get a trace and i can take a look16:47
jungleboyjsmcginnis: geguileo  I think we will stand with the decision from the PTG on shared backups.16:47
geguileojungleboyj: +116:47
jungleboyjAny other topics for today?16:47
*** VW has quit IRC16:47
*** rledisez has joined #openstack-meeting16:48
*** VW has joined #openstack-meeting16:48
jungleboyjI will take that as a no.16:49
jungleboyjThanks to everyone for joining the meeting today.16:49
jungleboyjThanks for your work on Cinder!16:49
jungleboyjTalk to you all next week!16:49
*** openstack changes topic to "OpenStack Meetings ||"16:50
openstackMeeting ended Wed Mar 21 16:50:06 2018 UTC.  Information about MeetBot at . (v 0.1.4)16:50
openstackMinutes (text):
*** lhx_ has quit IRC16:51
*** e0ne has quit IRC16:51
*** mjturek has quit IRC16:52
*** mjturek has joined #openstack-meeting16:53
*** mjturek has quit IRC16:53
*** mjturek has joined #openstack-meeting16:54
*** walshh has quit IRC16:57
*** browny_ has joined #openstack-meeting16:59
*** ionutbalutoiu has quit IRC17:01
*** bradjones has quit IRC17:03
*** browny_ has quit IRC17:03
*** browny_ has joined #openstack-meeting17:06
*** marios has quit IRC17:08
*** erlon has quit IRC17:08
*** marios has joined #openstack-meeting17:08
*** browny_ has quit IRC17:11
*** felipemonteiro__ has quit IRC17:11
*** felipemonteiro__ has joined #openstack-meeting17:11
*** ionutbalutoiu has joined #openstack-meeting17:11
*** marios has quit IRC17:19
*** browny_ has joined #openstack-meeting17:20
*** erlon has joined #openstack-meeting17:25
*** rbowen has quit IRC17:28
*** rbowen has joined #openstack-meeting17:29
*** diman has joined #openstack-meeting17:30
*** lpetrut_ has quit IRC17:32
*** diman has quit IRC17:34
*** toan has quit IRC17:37
*** homerp_ has quit IRC17:37
*** gus has quit IRC17:38
*** gmann_ has quit IRC17:38
*** cloudrancher has quit IRC17:39
*** homerp has joined #openstack-meeting17:39
*** _alastor__ has quit IRC17:39
*** andreaf has quit IRC17:39
*** gus has joined #openstack-meeting17:39
*** andreaf_ has joined #openstack-meeting17:39
*** _alastor__ has joined #openstack-meeting17:39
*** gmann_ has joined #openstack-meeting17:40
*** rbudden has quit IRC17:40
*** felipemonteiro_ has joined #openstack-meeting17:40
*** cloudrancher has joined #openstack-meeting17:40
*** toan has joined #openstack-meeting17:41
*** sridharg has quit IRC17:41
*** andreaf_ is now known as andreaf17:41
*** felipemonteiro__ has quit IRC17:41
*** cloudrancher has quit IRC17:44
*** Drankis has joined #openstack-meeting17:47
*** simon-AS5591 has quit IRC17:48
*** browny_ has quit IRC17:51
*** haleyb has quit IRC17:56
*** e0ne has joined #openstack-meeting17:58
*** sambetts is now known as sambetts|afk18:00
*** felipemonteiro__ has joined #openstack-meeting18:02
*** browny_ has joined #openstack-meeting18:05
*** ricolin has quit IRC18:05
*** VW_ has joined #openstack-meeting18:05
*** VW_ has quit IRC18:05
*** VW_ has joined #openstack-meeting18:06
*** felipemonteiro_ has quit IRC18:06
*** VW has quit IRC18:08
*** browny_ has quit IRC18:10
*** VW_ has quit IRC18:13
*** VW has joined #openstack-meeting18:13
*** sgrasley1 has quit IRC18:18
*** ircuser-1 has quit IRC18:20
*** lpetrut has joined #openstack-meeting18:20
*** EmilienM is now known as mimi18:21
*** mimi is now known as EmilienM18:21
*** cloudrancher has joined #openstack-meeting18:23
*** harlowja has joined #openstack-meeting18:24
*** diman has joined #openstack-meeting18:26
*** amodi has quit IRC18:27
*** cloudrancher has quit IRC18:28
*** haleyb has joined #openstack-meeting18:30
*** diman has quit IRC18:31
*** rbudden has joined #openstack-meeting18:39
*** tssurya has quit IRC18:42
*** yamamoto has quit IRC18:43
*** andreas_s has joined #openstack-meeting18:45
*** rbowen has quit IRC18:46
*** Swami has joined #openstack-meeting18:48
*** andreas_s has quit IRC18:50
*** cloudrancher has joined #openstack-meeting18:51
*** lpetrut has quit IRC18:51
*** raildo has quit IRC18:52
*** browny_ has joined #openstack-meeting18:52
*** cloudrancher has quit IRC18:54
*** cloudrancher has joined #openstack-meeting18:57
*** lpetrut has joined #openstack-meeting19:00
*** Mridu has joined #openstack-meeting19:00
*** cloudrancher has quit IRC19:02
SotK#startmeeting storyboard19:02
openstackMeeting started Wed Mar 21 19:02:16 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
diablo_rojoHello :)19:02
SotK#link Agenda19:03
diablo_rojoBoom. Made some changes to the agenda.19:04
SotK#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"19:04
SotKSahara migrated!19:04
diablo_rojoGaining traction :)19:04
*** sidx64 has joined #openstack-meeting19:05
fungiexcellent news19:05
*** brault has joined #openstack-meeting19:05
SotKand the agenda is full of plans for more19:06
diablo_rojonext week we will have more exciting annoucements :)19:06
SotK#topic In Progress Work19:06
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:06
SotKI re-sent the patch to fix syntax highlighting19:06
diablo_rojoSotK, will review today/tomorrow.19:07
*** brault_ has quit IRC19:07
diablo_rojoI have two patches out- one for private labels in the webclient, the other for a fix to the migration script to hopefyully stop making duplicate entries for users in the db.19:07
diablo_rojoBoth already have +2's from fungi- thanks fungi :)19:07
SotKI will try to find some time to review them this week19:08
fungiwe've noticed that the lp query api is feeding us "old" openids rather than ones, and this has resulted in duplicate accounts. i'm working on correcting and deduplicating these, but the main challenge will be finding all the tables which have a column for user ids as the columns aren't consistently named for that19:08
diablo_rojoSotK, that would be awesome. They are both sure small so aside from testing the second one, it shouldn't take too long.19:09
fungirelated to the seconf patch diablo_rojo mentioned19:09
SotKI can't promise anything as I've had approximately 0 free time so far this week19:09
diablo_rojoSotK, fair :)19:09
*** diman has joined #openstack-meeting19:09
SotKthis is also why I have failed to see if master is copying fonts properly despite saying I'd do it on monday :(19:09
fungiworst case i'll single-core approve the migrate script fix for rewriting openid urls before i do the next migration (probably friday)19:10
SotKfungi: I can try to make a list of the relevant fields at some point this week, that sounds like a short enough task I can fit it in somewhere19:10
*** cloudrancher has joined #openstack-meeting19:10
diablo_rojoLooked like corvus is in need of help with the db model too.19:10
fungiluckily the test migrations on storyboard-dev have caused the same problem, so i have both an easy place to test the deduplication work _and_ a place to test that subsequent test migrations with diablo_rojo's patch work as advertised19:11
SotKyeah, I didn't have any obvious pointers after a quick glance at it, I will also try to fit looking into that in somewhere xD19:11
diablo_rojoEasy peasy- and some day I might have perms to do test migrations there too :)19:12
fungiSotK: if you think you can, that would be a huge help to me. otherwise i anticipate just reading through the entirety of the db schema picking out column names which "look like user ids"19:12
* diablo_rojo cringes at the thought19:12
fungi(and hoping for the best)19:12
SotKdiablo_rojo: I would be happy to +1 a patch to the place that patches go to grant that permission19:13
fungiif i at least know which columns are user ids, then i can work out which ones need rewriting vs which ones need their duplicate rows deleted19:13
*** felipemonteiro__ has quit IRC19:13
*** felipemonteiro__ has joined #openstack-meeting19:13
fungidiablo_rojo: has that system-config change to get you access to sb-dev.o.o not merged yet?19:14
diablo_rojofungi, it hasn't was going to poke at clarkb today about it19:14
fungii'll try to drum up another reviewer to approve it19:14
diablo_rojofungi, that works too :)19:14
fungiclarkb may be hesitant to approve without another non-foundation-staff core reviewer giving a +219:14
diablo_rojofungi, oh yeah that makes sense.19:15
clarkbya I've tried to follow fungi's example there19:15
*** cloudrancher has quit IRC19:15
diablo_rojoGood practice to have.19:15
fungiespecially where granting exceptional access to things comes into play19:15
corvusit has a non-foundation +2 now :)19:15
fungithanks corvus!!!19:15
diablo_rojoThank you corvus :)19:16
*** cdub has quit IRC19:16
SotK\o/ nice19:16
*** sidx64 has quit IRC19:17
diablo_rojoSo hopefully that gets merged soon and I can carryon running all the test migrations there19:17
SotKthat would be good19:17
SotKanything else in progress not being covered further down the agenda?19:18
diablo_rojoSotK, indeed, especially since there seems to be an increasing interest in what it the end result looks like.19:18
*** rpioso is now known as rpioso|afk19:18
diablo_rojoSotK, don't think so.19:18
SotKoh, I did also for fun get a low priority patch for redesigning the dashboard a bit into a reviewable state over the weekend19:18
*** cloudrancher has joined #openstack-meeting19:18
*** erlon has quit IRC19:18
SotK#topic Migration Updates19:19
*** openstack changes topic to "Migration Updates (Meeting topic: storyboard)"19:19
SotKthis is an exciting looking section19:19
diablo_rojoIronic wants to migrate this week- Friday.19:19
diablo_rojoI also was notified that the UI squad in tripleO is ready to go.19:20
diablo_rojoSo Friday will be a full day of migrations.19:20
fungiyep, i'll hopefully have the account deduplication tested and completed by then19:20
SotKsounds great :D19:21
SotKhopefully they go well19:21
diablo_rojoI also need to circle back to an email thread I have with Vitrage about migration- they asked a lot of the same questions- how do I differentiate bugs and new features?19:21
fungieither way i can do the imports friday19:21
diablo_rojoI didn't have the will power to answer the other way.19:21
*** amodi has joined #openstack-meeting19:21
fungijust the deduplication script (once i write it) will take longer the more db content we have19:22
diablo_rojofungi, sounds like the sooner the better on that one then19:22
fungiyeah, but either way it's still just a fire-and-forget and odds are we're talking about a runtime difference on the order of seconds19:23
fungii'm more concerned with additional new users of sb.o.o getting confused by the extra accounts19:23
*** dprince has quit IRC19:23
diablo_rojofungi, yeah that can be offputting.19:23
*** dprince has joined #openstack-meeting19:23
fungiso still, the sooner the better19:23
diablo_rojoOnly other thing I have is that I'm currently running openstacksdk migrations and so far so good. I migrated three of the launchpad projects so far- I thiiiink there is one or two more left.19:24
diablo_rojoThey've all been pretty quick too.19:25
diablo_rojoThat's all from me for now :)19:25
SotKthanks for all your work on this diablo_rojo and fungi :)19:25
SotK#topic Open Discussion19:26
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:26
*** browny_ has quit IRC19:26
diablo_rojoSotK, you skipped the outreachy intern topic, but we can cover it here :)19:26
*** eharney has quit IRC19:26
openstackRemoving item from minutes: #topic Open Discussion19:26
SotK#topic Outreachy Intern!19:26
*** openstack changes topic to "Outreachy Intern! (Meeting topic: storyboard)"19:27
diablo_rojoWas chatting with Mridu this morning :)19:27
fungii still haven't started on the mysql 4-byte unicode adjustment... which test migrations were failing due to extended codepoints?19:27
diablo_rojoShe is working on applying to be an intern.19:27
fungioh, i jumped the gun on open discussion, sorry19:27
*** tosky has joined #openstack-meeting19:27
diablo_rojofungi, heat was struggling with that one... there was another. I will try to remember and let you know.19:27
diablo_rojofungi, oh it was mistral I think19:27
fungihelps to have test cases19:28
diablo_rojofungi, indeed it does :)19:28
*** eharney has joined #openstack-meeting19:28
diablo_rojoSo, intern.19:28
SotKdiablo_rojo: cool, I guess we should have some stories in mind to point people at during the application stage?19:28
fungiany news on sweksha who also popped into the channel?19:28
diablo_rojoSotK, yeah. I have been pointing to the make cli commands and the make tests not suck one19:29
*** dustins_ has joined #openstack-meeting19:29
diablo_rojofungi, sadly not.19:29
fungii think improving testing for the project would be at or near #1 for me, if they're interested in hacking on that19:29
SotKyeah I agree19:29
diablo_rojoI talked to vkmc and she didn't have sweksha's info so I don't have any way of contacting them unless they come back.19:29
diablo_rojofungi SotK agree. So I pointed Mridu at that this morning :)19:30
MriduHi all. I am Mridu. I am looking forward to contribute to the project. Work more on Python. And learn to code better. Through this opportunity. :)19:30
fungihi Mridu! and welcome19:31
diablo_rojoMridu, we are thrilled to have you :)19:31
SotKwelcome Mridu!19:31
diablo_rojoI pointed her at going through all the tasks tests and checking that they actually cover all the api functions for tasks.19:31
MriduThank you so much :)19:31
diablo_rojoUnless there is somewhere else we want her to start on tests?19:31
*** dustins has quit IRC19:32
MriduStill curious on knowing this project involves more of testing or more of development?19:32
diablo_rojoThere are pretty equal opportunities of both I would say.19:33
diablo_rojoOur tests need a lot of help, but there are still a lot of things to be developed :)19:34
fungiparticularly where it comes to developing tests19:34
diablo_rojoAnd anything you develop has to be tested to be merged.19:34
*** salv-orlando has quit IRC19:34
diablo_rojofungi, lol :)19:34
fungibasically, we have a lot of features which got added in recent years with limited or sometimes even no test coverage at all19:34
Mriduanything that levels up the coding skills. And helps me gain confidence. I am fine with it :)19:34
*** salv-orlando has joined #openstack-meeting19:35
diablo_rojoMridu, perfect :) I think you are in the right place then :)19:35
fungiso it's hard for us to know when subsequent changes break those features unless we have also developed regression tests to check that they continue to work19:35
fungitests are definitely code, though19:35
Mridubased on what fungi, is saying it seems. Lots and lots of tests. :p19:35
SotKI think there is likely to be opportunity for both, but yeah, our tests are lagging behind everything else a lot atm19:35
*** radeks_ has joined #openstack-meeting19:36
fungisometimes some of the most complicated kinds of software development, since it involves thinking about mocking out or similarly faking parts of existing software so that you can test other parts efficiently19:36
fungier, test are sometimes some of the most complicated kinds of software development19:36
fungii should give up on typing today19:36
*** sidx64 has joined #openstack-meeting19:37
fungibut yeah, developing tests is still very much a kind of software development19:37
*** efried_rollin is now known as efried19:37
diablo_rojofungi, I typed whole sentences that made no sense last night during the fc sig meeting- I wouldn't sweat a few typos.19:37
*** tesseract has quit IRC19:38
Mriduhahaha. Also, I am a bit confused with the choices. There are 2-3 projects under Openstack which one to opt for. Also, is this the right place to ask such a question in first place.19:38
*** browny_ has joined #openstack-meeting19:38
*** diman has quit IRC19:38
*** radeks has quit IRC19:38
diablo_rojoMridu 2-3 projects that have outreachy intern slots?19:38
diablo_rojoI think there are two.19:38
fungidiablo_rojo: i read that meeting log. seemed like an excellent one19:38
*** salv-orlando has quit IRC19:38
Mridu see.19:39
diablo_rojoStoryboard and one on Redfish it looks like.19:40
MriduYes yes19:40
MriduOne is there on Keynote - SAML as well19:40
fungikeystone, yes19:41
fungialso a (incomplete?) one for qinling, looks like19:41
diablo_rojoyeah looks like it19:41
Mriducomplete or incomplete I am unaware about that.19:42
*** radeks_ has quit IRC19:42
*** erlon has joined #openstack-meeting19:42
*** radeks_ has joined #openstack-meeting19:43
diablo_rojoIt might be completed.19:43
*** dprince has quit IRC19:43
diablo_rojoMridu, well, it depends on what your interests are which project you want to jump into I suppose. Of the options I think we have the most flexbility in coming up with work to fit your interests, but I might be biased :)19:44
*** browny_ has quit IRC19:44
*** yamamoto has joined #openstack-meeting19:44
* persia is biased19:44
MriduWhat is SAML project about?19:44
*** salv-orlando has joined #openstack-meeting19:44
SotKI am also biased, but agree with diablo_rojo19:44
MriduThese are the 2 projects where I can see skill level 5 that is needed :')19:45
persiaStoryboard is the best intern project for OpenStack because it lets one code in more languages, leverages more different testing components, and has active users all over the OpenStack developer community, allowing one to build strong relationships that will serve later.19:45
persiaStoryboard is also one of the few projects with full continuous deployment, so one can see the effects of one's work immediately (although the deployment was broken, last I checked)19:45
fungiMridu: the #openstack-keystone channel can probably give you better answers about that one, but saml is "security assertion markup language" (a standard to serialize authn/authz data)19:46
diablo_rojoMridu, so Keystone is actually the OpenStack project you would be working on for the SAML one. That project is focused on authetication, service discovery and authorization.19:46
diablo_rojoBasically it comes down to- do you like the idea of developing a task tracker tool or are you more interested in authentication and authorization?19:47
MriduSomething that serves more end users I would go for that19:48
fungiit's hard to compare the end users of keystone (who are mostly interacting with it through a remote api) and the users of storyboard (which has a ui)19:49
*** yamamoto has quit IRC19:49
fungiyou could consider that the "end users" of keystone are other applications (which may be run by people, or may be run by yet other applications still)19:50
MriduI also don't know. I will give this a shot. Let's see what happens. :)19:50
diablo_rojoWonderful :)19:50
SotKexcellent :)19:50
diablo_rojoSotK, now you can go to open discussion :)19:51
SotK#topic Open Discussion19:51
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"19:51
fungiyes! whether you want to work on storyboard or one of the other openstack projects, or on other free software completely, i think it's still awesome. free software always needs more people19:51
diablo_rojofungi, +119:51
*** rfolco is now known as rfolco|ruck19:51
Mriduyeah. That's right19:52
MriduThank you all for helping out :)19:52
fungiand thank you for wanting to help out too19:53
*** sidx64_ has joined #openstack-meeting19:53
diablo_rojoMridu, happy to help :) If you need anything else getting started- we all hang out in the #storyboard channel19:53
*** cloudrancher has joined #openstack-meeting19:54
*** VW has quit IRC19:54
*** VW has joined #openstack-meeting19:54
*** sidx64 has quit IRC19:55
*** browny_ has joined #openstack-meeting19:55
fungiwhile we're here, did anyone happen to have ideas off the tops of their heads about the problem corvus encountered with session management in tests?19:56
fungi#link WIP: test subscribers and permissions19:57
SotKnot off the top of my head no19:57
*** eharney has quit IRC19:57
SotKI will attempt to give it some thought when I have time19:58
*** annabelleB has quit IRC19:58
fungi#link mysterious failure19:58
diablo_rojoPerhaps more mysterious is how the few are passing19:59
diablo_rojoWheneverything else fails19:59
*** sidx64 has joined #openstack-meeting19:59
*** egarbade has quit IRC19:59
fungiwell, that pep8 failure is just a style consistency nit "imports not in alphabetical order"20:00
*** browny_ has quit IRC20:00
SotKwe're out of time20:00
*** sidx64_ has quit IRC20:00
SotKthanks for coming all20:01
fungithanks SotK!20:01
*** openstack changes topic to "OpenStack Meetings ||"20:01
openstackMeeting ended Wed Mar 21 20:01:04 2018 UTC.  Information about MeetBot at . (v 0.1.4)20:01
diablo_rojoBack to the #storyboard channel :)20:01
openstackMinutes (text):
diablo_rojoThanks SotK !20:01
fungiit's like the bat cave, but cooler20:01
*** egarbade has joined #openstack-meeting20:03
*** tssurya has joined #openstack-meeting20:05
*** radeks_ has quit IRC20:07
*** annabelleB has joined #openstack-meeting20:10
*** radeks_ has joined #openstack-meeting20:11
*** erlon has quit IRC20:11
*** eharney has joined #openstack-meeting20:13
*** priteau has quit IRC20:15
*** gman-tx has quit IRC20:19
*** cloudrancher has quit IRC20:20
*** tosky has left #openstack-meeting20:22
*** sgrasley1 has joined #openstack-meeting20:24
*** gouthamr has quit IRC20:26
*** browny_ has joined #openstack-meeting20:30
*** sgrasley1 has quit IRC20:32
*** salv-orlando has quit IRC20:32
*** sgrasley1 has joined #openstack-meeting20:32
*** Mridu has quit IRC20:38
*** gman-tx has joined #openstack-meeting20:39
*** yamamoto has joined #openstack-meeting20:45
*** mattia has joined #openstack-meeting20:46
*** sgrasley1 has quit IRC20:48
*** radeks_ has quit IRC20:48
*** yamamoto has quit IRC20:51
*** gman-tx has quit IRC20:51
*** m_kazuhiro has joined #openstack-meeting20:52
*** patchbot has joined #openstack-meeting20:55
*** acoles has joined #openstack-meeting20:59
*** browny_ has quit IRC21:00
*** browny_ has joined #openstack-meeting21:00
notmynameswift team meeting time21:00
*** timburke has joined #openstack-meeting21:00
notmyname#startmeeting swift21:00
openstackMeeting started Wed Mar 21 21:00:27 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 meeting?21:00
rledisezhi o/21:00
notmynameclayg: tdasilva: cschwede: acoles: ping21:01
*** esberglu has quit IRC21:01
acolesI'm here21:01
notmynameagenda for this week is at ...21:01
*** torgomatic has joined #openstack-meeting21:02
notmyname#topic bugs, oh my!21:02
*** openstack changes topic to "bugs, oh my! (Meeting topic: swift)"21:02
openstackLaunchpad bug 1755554 in OpenStack Object Storage (swift) "Percent signs in object names cause trouble for versioned_writes" [High,Confirmed]21:02
notmynamelast week kota_ and timburke suggested they may have a chance to look at this bug21:03
notmynamekota_: timburke: did you look at it since the last meeting?21:03
timburkei think i said i could look at it, but probably not that week ;-)21:03
kota_sorry i didn't. but i think this week I can have it rather than the last week.21:03
timburkei was right on that account21:03
notmynamebut now it's a new week!21:03
*** zaitcev has joined #openstack-meeting21:04
notmynameok, thanks21:04
mattoliverautimburke and how's this week looking?21:05
notmynameIMO it's an important bug that I'd like to see closed in the next release we do, but I don't think we'll be releasing in the next few days or anythign like that :-)21:05
timburkemattoliverau: *shrug* who knows? we'll see where feature/deep goes21:05
notmynamekota_: thanks. I'll bring it up again next week to ask about it again21:06
kota_notmyname: ok21:06
notmynamespeaking of "next release", that's a great segue into the next topic...21:06
notmyname#topic feature/deep plans21:06
*** openstack changes topic to "feature/deep plans (Meeting topic: swift)"21:06
notmynameI updated that page with some feature/deep21:07
notmyname...and hit enter too early...21:07
notmynameI updated that page with some feature/deep scheduling info21:07
kota_oh feature/deep is close to the final landing proposal.21:08
mattoliverauOh exciting21:08
zaitcevWell, it is.21:08
notmyname"where do these dates come from?" you ask. great question21:09
notmynamefull disclosure, there's some internal dates/goals we're trying to hit at swiftstack related to container sharding. these dates are somewhat related to that, but the upstream work is driving them (more that the other way around)21:10
*** eharney has quit IRC21:10
*** pchavva has quit IRC21:11
notmynameso talking with acoles and timburke and clayg about what can be done and what's a thing that can be released that will actually help users got us to these date goals21:11
notmynamethe scope is not to have feature/deep support automatically sharding every container in a cluster and all new containers that are created21:11
zaitcevThank goodness someone found a business goal for the sharding after all these years.21:11
claygzaitcev: you a fan of the big containers?21:12
notmynamezaitcev: I think we've all seen pain around big containers from customers :-)21:12
*** bnemec is now known as sin-master21:12
*** sin-master is now known as bnemec21:12
notmynameI think it will be wonderful to have everything automatically sharded all the time. but it's not a reasonable thing to have in an initial release21:12
notmynamethe initial goal is to have tools to identify big containers (or container shards) via recon and then shard a container via an "expert operator"21:13
*** VW has quit IRC21:13
*** esberglu has joined #openstack-meeting21:14
notmynamelater, we can make sure we automatically start sharding big stuff, but that will force us to solve the leader election problem (which container sets the shard ranges in a distributed system)21:14
notmynamealso, I like initially having it triggered by hand so that an operator can monitor it without having the whole cluster automatically do something with little recourse21:14
*** raildo has joined #openstack-meeting21:15
notmynameso an existing swift cluster operator will be able to identify big containers and run some bin/ scripts to start it sharding. later, recon stats may identify a particular shard of that container is getting big, and the process can repeat21:15
notmynamedoes all that make sense? what do you think? mattoliverau, zaitcev, tdasilva, kota_, rledisez21:16
zaitcevSounds good to me.21:16
tdasilvanotmyname: so the whole sharding process will be manual?? meaning even to create new shards requires operator?21:16
rledisezI totally agree to not have auto sharding at first21:16
timburketdasilva: baby steps -- we'll get the human out of the loop eventually21:17
notmynametdasilva: correct. an operator will run a 'find-and-write-the-shard-ranges' script to kick it off21:17
mattoliverauSounds like a good reduced scope and first step. Then slowly turn on the smarts as we go.21:17
kota_sounds reasonable. do it manually, then make it as automatic. that wey is well as what tiering also will do.21:17
zaitcevYou know even in kernel hugepages are not automatically enabled.21:18
notmynamein addition to not making it automatic, it means we don't yet have to solve distributed consensus for which container replica gets to choose the shard ranges21:18
tdasilvatimburke: i understand the reasoning, was more really just trying to understand the actual process...21:18
notmynameok :-)21:18
zaitcevwait, I thought 0-th replica was always the master.21:19
mattoliverauBesides having control before handing it completely over feels better, until we know we trust this sharding thing :)21:19
kota_one thing, i'm worried about the schedule. s3api should be later than the feature/deep proposal... or not?21:19
acolestdasilva: when shards grow large, they will need to be manually sharded in exact same way as original container was21:19
timburkezaitcev: gets messy when you rebalance :-/21:19
acolestdasilva: human kicks off the process but daemon takes care of the shard sharding itself21:19
mattoliverauStep 1 no leader election, step 2 basic election, step 3 full leader election (if we ever need it)21:20
notmynamekota_: yeah, that schedule conflict is tricky. I was hoping that with a reduced scope for s3api, the merge would be simpler and require less time from everyone. and that we'd be able to get it done before feature/deep21:20
*** rbudden has quit IRC21:21
acolesas timburke says, the concern with fully automatic sharding is we need a robust leader election, and choosing node index 0 is not robust enough currently without further work21:21
tdasilvaacoles: thanks, don't want to take time from this meeting, we can probably continue on #openstack-swift later..21:21
acolesbut FWIW all probe tests *do* run fully automatically21:21
acoleswe're just proposing that for production the auto sharding should be off by default21:22
mattoliverauAnd there's an auto shard option just will be turned off by default with a warning.21:22
kota_notmyname: appreciated your polite consideration21:22
notmynamekota_: but depending on how the s3api work goes, it may in fact become a conflict21:22
mattoliverauOr what acoles said21:22
kota_notmyname: this (or the next) week, I'll try to figure out the conflict with feature/deep and feature/s3api21:23
notmynamekota_: thank you. that will be very helpful21:23
*** awaugama has quit IRC21:24
notmynameso with those proposed dates about feature/deep, I'd like to hold off the next swift release until feature/deep merges21:24
timburkefwiw, the only conflicts (right now) between the two feature branches are in .gitreview (for obvious reasons), .zuul.yaml, and test/functional/__init__.py21:24
notmynameit also means that in a few weeks (ie April 16), we'll need a lot of help from everyone for reviewing a merge to master21:24
kota_i don't think we have much conflict because s3api doesn't touch existing Swift master code so much.21:24
*** SerenaFeng has joined #openstack-meeting21:24
kota_but... the serious problem is lack of reviewers.21:25
kota_it looks like no reviews on my s3api patches in the last week...21:25
notmynamenote, the April 16 "propose to master" date for feature/deep is what I'd expect the earliest to be. and a May 8 "merged to master" is what I'd hope the latest to be21:25
notmynamekota_: that is an excellent point21:26
kota_timburke: thx your confirmation on the conflict!21:26
notmynameI think that means we can do one of two things about feature/s3api21:26
*** ansmith has quit IRC21:26
notmyname(1) hold off on it until *after* feature/deep merges21:26
notmyname(2) ask people to review feature/s3api and hope it doesn't impact ongoing work to finish feature/deep21:27
*** priteau has joined #openstack-meeting21:27
notmynamekota_: what would you prefer?21:27
kota_(2) is. but I don't know how much hard for others to find their time.21:28
notmynameok, thank you.21:28
notmynamewhat does everyone else think?21:28
kota_I'd try to pick up easy ones as possible to ask someone.21:28
kota_when asking.21:28
*** SerenaFeng has quit IRC21:29
*** gman-tx has joined #openstack-meeting21:29
zaitcevWell... I was going to look at s3api. Seemed simpler :-)21:29
*** markstur has joined #openstack-meeting21:29
*** sidx64 has quit IRC21:30
notmynamethe current goal for feature/s3api is to simply bring in the swift3 codebase and resolve test/doc/utils/dependency duplication. *not* to add major new functionality21:30
notmynamekota_: we can check how others feel right now, but in my opinion, if you merge stuff to the feature branch on your own, that's ok because the scope of feature/s3api isn't huge21:31
notmyname...and will be reviewed as a whole when merged to master21:32
*** felipemonteiro_ has joined #openstack-meeting21:32
tdasilvakota_: fwiw, i started reviewing and got side tracked :(21:32
*** salv-orlando has joined #openstack-meeting21:32
kota_notmyname: got it. try to merge quick with my own decision on the feature branch.21:33
notmynamefurthermore, I do not think feature/s3api should need approval from everyone in order to land on master. again, the scope and code is rather constrained21:33
notmynamekota_: that's my opinion. what does everyone else think?21:33
timburkeyeah, i think i'm fine with all of that21:33
kota_ok. cleanup can be progressed by myself. the docs, i'd want helps still though.21:35
kota_but part of stuff can be done with the strategy21:35
notmynamethat's understandable. but I don't think we need to write a bunch of new docs just to import swift321:35
*** felipemonteiro__ has quit IRC21:35
* notmyname admits he hasn't looked at what docs exist for swift3... maybe it's nothing21:36
kota_notmyname: oh21:36
notmynamekota_: but, yes, please ask for docs help where you need help. we should definitely help out with that21:37
kota_is it ok that docs is just imported from swift3 too...?21:37
*** salv-orlando has quit IRC21:38
tdasilvakota_: are you ok if I upload new patchset to your docs patch?21:38
notmynameI think so. but docs probably take more integration with the existing docs tree. I think that should be relatively simple, though. at least simpler than writing whole new docs21:38
mattoliverauYeah, they should at least be the basis, let's not rewrite everything if we don't have too.21:38
notmynamemattoliverau: right. exactly21:38
acoleskota_: notmyname : sorry I was distracted, but I agree that merging own patches on feature branch is ok21:39
notmynamemattoliverau: tdasilva: will either of you be able to help kota_ with this feature branch? IMO, if the three of you say it's good, I'm happy to see it land21:39
tdasilvabtw, kota is not really rewriting all the docs, but they do need some fixups, instructions how to enable and's a good effort21:40
notmynametdasilva: ah, good point. thanks for the clarification21:41
patchbotpatch 552853 - swift (feature/s3api) - Update S3api Docs21:41
tdasilvanotmyname: yeah, i rreally want to help kota and will do what i can to help21:41
notmynametdasilva: thanks21:41
mattoliverauI'll see what I can do, I'm also trying to keep up with sharding reviews and py3, but knowing the s3api scope I'll try and help where I can21:42
notmynamemattoliverau: yeah, that makes sense21:42
kota_thank you tdasilva, mattoliverau and notmyname21:42
tdasilvamattoliverau: yeah, i'm atm putting s3api ahead of py321:43
tdasilvajust cause py3 is more longer term21:43
notmynameso to sum up all of that ... any more questions or concerns about feature/deep timeline goals and feature/s3api work?21:43
timburkebut eventually -- we're gonna have *all* of the 3s!21:43
zaitcevnobody make a joke about that please21:44
notmynameok, moving on. thanks for working through it21:44
notmyname#topic LOSF update21:44
*** openstack changes topic to "LOSF update (Meeting topic: swift)"21:44
notmynamethis morning (US time), we had a meeting with rledisez about their LOSF work21:45
notmynamerecording is at21:45
tdasilvazaitcev: you will eventually get it how funny it is to make 'eventually' jokes ;)21:45
kota_nice. I'll check out it.21:45
notmynamethe very quick summary is: it's going well with initial tests and OVH is starting some bigger scale tests soon21:46
notmynameand rledisez and alex will be working on getting their code upstream. I'll set up a feature branch for that (but later, not immediately)21:46
notmynamethere are 3 patches that are needed upstream, though, that are proposed already. these are listed on the priority review page21:47
*** yamamoto has joined #openstack-meeting21:47
notmynamerledisez: what did I miss? any further updates there?21:47
rledisezno, it seems complete. about the 3 patches, 2 already got one +2, one need some feedback as it's quite big (tests are not completely passing yet, but feedbacks welcome)21:48
mattoliverauI started looking at one the other day, I'll try and get back to it today.21:49
rledisezthx mattoliverau21:50
notmynameone concern I shared this morning is that OVH is starting to deploy this code in their production clusters (which is really cool), but it's not been integrated upstream. this means that there's a pre-existing migration concern when we actually get to review the LOSF code21:50
notmynamethis is why I want to get the LOSF code reviewable in the open ASAP21:50
torgomaticit sounds like migration isn't really a huge deal; you stand up a new node running LOSF for objects and let replication do its job21:50
notmynamein the short term (next few days? next week?) i hope rledisez and alex will be able to share updates to design docs21:51
torgomaticif they need to migrate from LOSF format 1 to LOSF format 2, then it's the same procedure21:51
rledisezbut we tried to anticipate that, the on-disk format is versioned so we can evolve it without breaking things (hopefuly)21:51
notmynameyep. sounds great :-)21:51
mattoliveraurledisez: good thinking :)21:52
notmynamelast topic for today...21:52
notmyname#topic slogging testing21:52
*** openstack changes topic to "slogging testing (Meeting topic: swift)"21:52
kei-ichiThank you for giving me a time. About unittest modification policy for slogging.21:52
notmynamekei-ichi: you had another question about slogging for us?21:52
kei-ichiYes, I found some dependency between slogging and swift. How should I remove swift dependency ? Dependency is like following.21:53
kei-ichiex1: from initial process of unittest, slogging unittest uses swift directory like '../swift/' .21:53
*** yamamoto has quit IRC21:53
kei-ichiex2: swift itself is imported from slogging code for many purposes.(raise swift exception, to utilize swift test utility, ...)21:53
kei-ichiex3: unittest uses configuration file in swift repository...21:53
kei-ichiI think it is not good that those dependency is remained. So is it okay to copy those kind of files from swift to slogging ?21:53
kei-ichi(In our heat-dashboard(split out from Horizon as Heat GUI), there was same problems between Heat-GUI part and Horizon. In this case, we copied all dependent code to heat-dashboard basically.)21:53
*** priteau has quit IRC21:54
notmynameI think that's totally up to you. your example 1 seems a bit awkward and perhaps could be improved, but slogging importing swift code seems normal to me21:54
notmynamebut generally, I don't think you need our permission to update slogging :-)21:54
notmynamekei-ichi: what do you think is best for slogging and maintaining it?21:54
*** rbudden has joined #openstack-meeting21:55
*** pcaruana has quit IRC21:55
kei-ichinotmyname thanks! I think I agree to your proposal.21:56
torgomaticFWIW, in ProxyFS (another project using Swift code), we started off importing a bunch of code from Swift, and then any time it changed and broke things, we'd copy those functions into the ProxyFS codebase21:56
kei-ichiBasically I remove dependency, but maybe keep using swift itself.21:56
notmynameclayg: swoslo?21:56
notmynamealso, no ;-)21:57
torgomaticAs long as the licenses are compatible, I don't think there's a problem copying code over.21:57
*** rfolco|ruck is now known as rfolco|off21:57
kei-ichitorogomatic thanks! I'll look at that.21:57
mattoliverauExcept for potential maintenance21:57
timburkei wonder if swift-on-file's experience might offer guidance...21:57
notmynamemattoliverau: and that's up the an individual project to decide what they want to do21:57
kei-ichiThat wil be really helpful for me :)21:57
mattoliverauOh yeah I agree21:58
kota_swift3 import many of swift ;-)21:58
notmynameI think we've covered everything that needs covering this week, and we're just about out of our allotted time.21:58
notmynameanyone have anything else to bring up?21:58
*** salv-orlando has joined #openstack-meeting21:59
zaitcevPUT+POST is ready, for real this time. Even tests.21:59
kota_but not locate the code in the repo like ex1 kei-ichi suggested...21:59
notmynamezaitcev: ah yes!21:59
notmynamezaitcev: thanks for updating that21:59
kei-ichiThanks everyone !! current my opinion. Swift itself -> keep using. Other utility kind of files or direct reference to filesystem -> copy from swift.21:59
notmynameI'll put it back on the priority reviews page21:59
notmynamethanks everyone for coming. thank you for your work on swift22:00
*** openstack changes topic to "OpenStack Meetings ||"22:00
openstackMeeting ended Wed Mar 21 22:00:21 2018 UTC.  Information about MeetBot at . (v 0.1.4)22:00
*** zaitcev has left #openstack-meeting22:00
openstackMinutes (text):
*** patchbot has left #openstack-meeting22:00
*** acoles has left #openstack-meeting22:00
*** timburke has left #openstack-meeting22:01
*** torgomatic has left #openstack-meeting22:02
*** ykatabam has joined #openstack-meeting22:07
*** raildo has quit IRC22:15
*** lpetrut has quit IRC22:22
*** yamahata has joined #openstack-meeting22:24
*** e0ne has quit IRC22:24
*** munimeha1 has quit IRC22:25
*** rcernin has joined #openstack-meeting22:25
*** felipemonteiro_ has quit IRC22:29
*** felipemonteiro_ has joined #openstack-meeting22:29
*** bobh has quit IRC22:30
*** d0ugal has quit IRC22:34
*** d0ugal has joined #openstack-meeting22:37
*** dustins_ has quit IRC22:44
*** andreas_s has joined #openstack-meeting22:47
*** markstur has quit IRC22:47
*** tssurya has quit IRC22:48
*** iyamahat has joined #openstack-meeting22:49
*** yamamoto has joined #openstack-meeting22:49
*** cdub has joined #openstack-meeting22:49
*** hongbin has quit IRC22:50
*** andreas_s has quit IRC22:51
*** gman-tx has quit IRC22:51
*** esberglu has quit IRC22:51
*** yamamoto has quit IRC22:54
*** fnaval has quit IRC22:56
*** rbudden has quit IRC22:58
*** m_kazuhiro has quit IRC23:01
*** masber has joined #openstack-meeting23:04
*** 21WAAHMAC has joined #openstack-meeting23:05
*** raildo has joined #openstack-meeting23:06
*** edmondsw has quit IRC23:07
*** tpsilva has quit IRC23:09
*** 21WAAHMAC has quit IRC23:09
*** fnaval has joined #openstack-meeting23:16
*** fnaval has quit IRC23:16
*** fnaval has joined #openstack-meeting23:17
*** salv-orlando has quit IRC23:26
*** salv-orlando has joined #openstack-meeting23:26
*** salv-orlando has quit IRC23:30
*** chyka has quit IRC23:39
*** Adri2000 has quit IRC23:40
*** Adri2000 has joined #openstack-meeting23:41
*** felipemonteiro_ has quit IRC23:41
*** gyee has quit IRC23:45
*** claudiub has quit IRC23:51
*** yamamoto has joined #openstack-meeting23:51
*** yamamoto has quit IRC23:55

Generated by 2.15.3 by Marius Gedminas - find it at!