Wednesday, 2016-04-20

*** _JZ_ has joined #openstack-swift00:01
*** garthb__ has quit IRC00:04
*** haomaiwang has joined #openstack-swift00:21
*** haomaiwang has quit IRC00:26
*** lyrrad has quit IRC00:26
*** Suyi has joined #openstack-swift00:51
*** StraubTW has joined #openstack-swift01:00
*** Suyi has quit IRC01:26
*** StraubTW has quit IRC01:30
*** StraubTW has joined #openstack-swift01:31
*** rohit_ has quit IRC01:37
*** sgundur1 has left #openstack-swift01:52
*** mwheckmann has joined #openstack-swift02:01
notmynamereminder to those online now, no meeting tomorrow02:01
*** lakshmiS has quit IRC02:19
*** dmorita has quit IRC02:26
*** gyee has quit IRC02:27
*** dmorita has joined #openstack-swift02:27
openstackgerritTim Burke proposed openstack/swift: Close all versioned_writes subrequests' app_iters  https://review.openstack.org/30793702:30
*** dmorita has quit IRC02:32
*** delattec has quit IRC02:40
*** sekrit is now known as CIA02:44
*** sgundur1 has joined #openstack-swift02:44
*** sgundur1 has left #openstack-swift02:44
*** dmorita has joined #openstack-swift02:50
*** tsimp06 has joined #openstack-swift02:52
*** dmorita has quit IRC02:55
*** sgundur1 has joined #openstack-swift02:59
*** sgundur1 has left #openstack-swift02:59
*** mingdang1 has joined #openstack-swift03:06
janonymousntata: Hello, Please use this patch for testr and modify it according to requirements: https://review.openstack.org/#/c/257053/03:16
patchbotjanonymous: patch 257053 - swift - Using ostestr to run unittests03:16
notmynamejanonymous: are you still working on that one? I think ntata is going to do a different one first03:17
notmynameor to rephrase, are you still interested in porting the unittests to use testr?03:18
janonymousnotmyname: Hey03:18
notmynamejanonymous: and do we get to see you next week in austin?!03:18
janonymousnotmyname: that patch does the porting except the merge conflict part :)03:18
notmynamejanonymous: from a quick glance at it (not a full review), I agree with tdasilva's -1. looks like a good start, but perhaps in the wrong place03:20
janonymousnotmyname: ntata can continue on that after doing the priority first no problem, i am involved with my company's project's release so could not give much time on that03:20
notmynameah, ok03:20
*** links has joined #openstack-swift03:21
janonymousnotmyname: yes i am planning to see awesome swifties :)03:21
notmynamejanonymous: eg the idea of having a single runner that takes the test type is interesting. I like that. but probably the wrapper scripts (.functests, etc) should be updated to call that, instead of doing it in something called "functests". that's confusing03:21
janonymousnotmyname: Sure it could be used as a base patch, it needs improvement for sure03:21
notmynamejanonymous: great! I'm glad you'll make it :-)03:21
janonymousnotmyname: :)03:23
janonymousnotmyname: are the session's topic decided ?03:25
notmynamejanonymous: yep. they're scheduled, and you can see the ehterpads in the channel topic03:26
janonymousnotmyname: great !!03:26
*** asettle has quit IRC03:27
janonymousnotmyname: I will go through the etherpad :), Hope to see all of you in summit :)03:29
*** sgundur1 has joined #openstack-swift03:29
*** sgundur1 has left #openstack-swift03:29
*** dmorita has joined #openstack-swift03:30
*** dmorita has quit IRC03:37
*** dmorita has joined #openstack-swift03:38
*** asettle has joined #openstack-swift03:43
*** nadeem has joined #openstack-swift03:50
*** ekarlso has quit IRC04:11
*** hosanai has quit IRC04:13
*** hosanai has joined #openstack-swift04:14
*** ChanServ sets mode: +v hosanai04:14
*** mingdang1 has quit IRC04:16
*** klrmn has quit IRC04:19
*** ekarlso has joined #openstack-swift04:24
*** dmorita has quit IRC04:25
*** SkyRocknRoll has joined #openstack-swift04:58
*** mwheckmann has quit IRC05:01
*** ppai has joined #openstack-swift05:31
*** asettle has quit IRC05:32
*** asettle has joined #openstack-swift05:33
*** nadeem has quit IRC05:37
*** nadeem has joined #openstack-swift05:47
*** chip_ has joined #openstack-swift05:49
*** chip_ has quit IRC05:52
*** chip_ has joined #openstack-swift05:53
*** asettle has quit IRC05:55
*** asettle has joined #openstack-swift05:55
*** ChubYann has quit IRC05:56
*** zaitcev has quit IRC06:05
*** chip_ has quit IRC06:16
*** rcernin has joined #openstack-swift06:21
*** dmorita has joined #openstack-swift06:25
*** dmorita has quit IRC06:29
*** sheel has joined #openstack-swift06:47
*** tesseract has joined #openstack-swift06:47
*** tesseract is now known as Guest6708206:48
*** asettle has quit IRC06:55
*** asettle has joined #openstack-swift06:56
*** a1|away is now known as JelleB06:59
*** permalac has joined #openstack-swift07:00
*** janonymous has quit IRC07:01
*** janonymous has joined #openstack-swift07:03
*** asettle has quit IRC07:03
*** acoles_ is now known as acoles07:08
mattoliverauhosanai, kota_: haven't seen you guys on today. This is a reminder that there is _no_ swift meeting tomorrow morning, so you can sleep in.07:10
mattoliverauacoles: hey man!07:10
acolesmattoliverau: hey! hows it going? have read your parenting comments in scrollback :D did I say nothing can prepare you?07:13
kota_mattolivearu: hey man! just be online to look logs but unfortunately I'm going to be offline soon.07:13
kota_mattoliveau: but thanks07:13
kota_acoles: o/07:13
acoleskota_: hi07:13
janonymousmattoliverau, kota_, acoles: o/07:14
kota_janonymous: hello07:14
kota_janonymous: will you be in Austin/07:14
kota_?07:14
janonymouskota_: yes :)07:15
janonymouskota_: wbu ?07:15
*** chmouel has joined #openstack-swift07:15
kota_janonymous: sure, i'm looking forwared to meeting you there ;)07:15
*** acoles is now known as acoles_07:16
janonymouskota_: Sure, me too :)07:16
janonymouskota_: when is your arrival and departure?07:18
*** acoles_ is now known as acoles07:18
acolesah, no meeting today07:18
acolescschwede: did you see ^^07:19
kota_janonymous: flight in monday, deart at friday morning, this time my travel is too shorter than previous ones for some private reasons.07:19
cschwedeacoles: Good Morning Alistair! Not yet, so thanks for the heads up - a little more sleep tonight ;)07:20
acolescschwede: yes! I for one need it!07:20
janonymouskota_: Ohhkay :)07:20
kota_good morning cschwede.07:21
janonymouscschwede: o/07:21
acolesmahatic_: hi just saw your comments on patches - are you able to work more on that today? (just wondering if i should pick anything up)07:21
cschwedekota_: janonymous: Hello & good afternoon :)07:21
*** jlvillal has quit IRC07:22
*** jlvillal has joined #openstack-swift07:22
mahatic_acoles: hello, yup should be able to push a patchset today. Will do it as early I can07:24
mattoliverauacoles: all is well, looking forward to sleeping on the long flight to Austin ;)07:25
mahatic_acoles: I couldn't get to them early in the day, had some quarterly updates to attend07:25
*** rledisez has joined #openstack-swift07:32
acolesmahatic_: great thank you07:34
acolesmattoliverau: yes, sleep is the new currency ;)07:35
*** mmcardle has joined #openstack-swift07:35
*** Psy has joined #openstack-swift07:43
*** Psy has left #openstack-swift07:44
*** nadeem has quit IRC07:55
*** kirubak has joined #openstack-swift08:09
kirubakkirubak08:09
*** jordanP has joined #openstack-swift08:14
*** mingdang1 has joined #openstack-swift08:17
*** jmccarthy has quit IRC08:18
*** jistr has joined #openstack-swift08:18
*** jmccarthy has joined #openstack-swift08:18
*** joeljwright has joined #openstack-swift08:20
*** ChanServ sets mode: +v joeljwright08:20
*** dosaboy_ is now known as dosaboy08:24
*** asettle has joined #openstack-swift08:42
*** Guest66327 has quit IRC08:43
*** david-lyle has quit IRC08:59
*** david-lyle has joined #openstack-swift09:00
*** stantonnet has quit IRC09:02
*** mingdang1 has quit IRC09:03
*** stantonnet has joined #openstack-swift09:04
*** kei_yama has quit IRC09:09
*** asettle has quit IRC09:11
*** asettle has joined #openstack-swift09:17
*** asettle has quit IRC09:54
*** asettle has joined #openstack-swift09:54
*** asettle has quit IRC09:59
*** geaaru has joined #openstack-swift10:03
openstackgerritMahati Chamarthy proposed openstack/swift: crypto - byok support in keymaster  https://review.openstack.org/30781110:08
*** asettle has joined #openstack-swift10:10
openstackgerritMahati Chamarthy proposed openstack/swift: crypto - byok support in keymaster  https://review.openstack.org/30781110:16
*** hosanai has quit IRC10:18
openstackgerritAnkur Jain proposed openstack/swift: Invalid parameter does not return 400  https://review.openstack.org/29922510:29
nttHi, I'm trying to use the directory path based configuration in openstack swift (kilo). It seems that if I enable for example openstack-swift-account.service at boot, it doesn't load /etc/swift/account-server/1.conf and /etc/swift/account-server/2.conf but try to load /etc/swift/account-server.conf (that doesn't exist). It works normally if I use swift-init account start10:38
nttsomeone can help me pleasE?10:38
*** oshritf has joined #openstack-swift10:45
openstackgerritMahati Chamarthy proposed openstack/swift: crypto - Encrypt flag for probe tests  https://review.openstack.org/21697410:50
*** jordanP has quit IRC10:55
mahatic_acoles: i think the rebases and changes are done - ready to review i guess11:08
* mahatic_ is afk11:09
*** asettle has quit IRC11:20
*** asettle has joined #openstack-swift11:21
*** dmorita has joined #openstack-swift11:26
*** haomaiwang has joined #openstack-swift11:27
*** mingdang1 has joined #openstack-swift11:27
*** dmorita has quit IRC11:31
*** ppai has quit IRC11:35
*** mmcardle has quit IRC11:42
*** ppai has joined #openstack-swift11:49
*** asettle has quit IRC11:49
*** daemontool has joined #openstack-swift11:50
*** haomaiwang has quit IRC12:01
*** SkyRocknRoll has quit IRC12:05
*** ppai has quit IRC12:10
*** cdelatte has joined #openstack-swift12:17
*** ppai has joined #openstack-swift12:24
*** mmcardle has joined #openstack-swift12:35
*** asettle has joined #openstack-swift12:37
*** admin6 has joined #openstack-swift12:37
*** asettle has quit IRC12:42
*** links has quit IRC12:46
*** mwheckmann has joined #openstack-swift12:47
*** klamath has joined #openstack-swift12:51
*** klamath has quit IRC12:51
*** klamath has joined #openstack-swift12:52
*** oshritf has quit IRC12:52
*** NM has joined #openstack-swift12:58
*** aimeeU has joined #openstack-swift13:02
*** StraubTW has quit IRC13:08
*** kirubak has quit IRC13:12
tdasilvagood morning13:26
*** jordanP has joined #openstack-swift13:31
*** haomaiwang has joined #openstack-swift13:31
*** StraubTW has joined #openstack-swift13:34
nttHi, I'm trying to use the directory path based configuration in openstack swift (kilo). It seems that if I enable for example openstack-swift-account.service at boot, it doesn't load /etc/swift/account-server/1.conf and /etc/swift/account-server/2.conf but try to load /etc/swift/account-server.conf (that doesn't exist). It works normally if I use swift-init account start13:35
nttsomeone can help me pleasE?13:35
*** esker has quit IRC13:37
*** dmsimard has left #openstack-swift13:40
*** ppai is now known as ppai|afk13:43
*** haomaiwang has quit IRC13:44
*** cdelatte has quit IRC13:48
ppai|afkntt, hi13:50
ppai|afkntt, it's because of the way the .service scripts have been written13:51
ppai|afkntt, http://pkgs.fedoraproject.org/cgit/rpms/openstack-swift.git/tree/openstack-swift-account.service?h=f2313:51
admin6Hi all, I’ve have a starting cluster whit a 14 partition power for account and container rings (in replica 4) but only 6 disks currently setup into them. When i perform a rebalance, I got messages like :13:51
admin6  part, devs_for_part)))13:52
*** links has joined #openstack-swift13:52
ppai|afkntt,  take a look at this: http://pkgs.fedoraproject.org/cgit/rpms/openstack-swift.git/tree/openstack-swift-account@.service?h=f2313:53
admin6RingValidationWarning: The partition 2206 has been assigned to duplicate devices13:53
admin6Do  you think I should care about these errors, and wil they vanish if a13:54
admin6if I add additional disks into my rings?13:54
*** sgundur1 has joined #openstack-swift14:00
*** _JZ_ has quit IRC14:01
*** cdelatte has joined #openstack-swift14:02
glangeadmin6: your partion power might be too small14:03
glangethat's only 16k partitions14:03
glangeit might be difficult to get an even distribution of data with that few partitions14:04
glangeand that duplicate device error isn't good14:04
admin6too small? I was thinking on the opposite that it were too big for such a few disks inside it14:07
admin6and you’re right, I’ve only 16384 patition in these rings14:08
*** ametts has joined #openstack-swift14:11
glangeI believe the more partitions, the better chance of even distrubuition of replicas14:11
glangelike if you only had 5 partitions, it seems a lot more likely that one of them would have way more replicas than another14:11
glangeand that chance reduces as you add more partitions14:11
glangewe have some big clusters, but we have 1 million plus partitions14:12
glangeplus, more partitions are better when they have to move14:13
glangebut ask around, maybe what you are doing is ok -- those are just what I think/am guessing14:13
admin6glange: So I’ll try with a much higher partition power to see if that helps, thanks. However, I had an object ring with erasure coding 9+3 (so declared with 12 "replicas"), that I started with very few disks and a partition power of 19 wich got same type of errors. Reducing the partition power to 18 grealy enhance the number of "duplicate devices" error messages14:18
admin6(greatly enhance : drastically reduced)14:19
glangethat's possible14:19
*** mingdang1 has quit IRC14:23
*** esker has joined #openstack-swift14:29
*** esker has quit IRC14:29
*** esker has joined #openstack-swift14:30
*** arch-nemesis has joined #openstack-swift14:33
*** arch-nemesis has joined #openstack-swift14:34
*** ntt has quit IRC14:39
*** hosanai has joined #openstack-swift14:42
*** ChanServ sets mode: +v hosanai14:42
*** sgundur has joined #openstack-swift14:45
*** haomaiwang has joined #openstack-swift14:52
openstackgerritAlistair Coles proposed openstack/swift: crypto - byok support in keymaster  https://review.openstack.org/30781114:53
*** nadeem has joined #openstack-swift14:58
*** garthb has joined #openstack-swift14:58
acolesmahatic_: your byok patch has been really useful to me for putting together a demo for next week14:59
*** ppai|afk is now known as ppai15:01
*** ppai_ has joined #openstack-swift15:06
*** amit213 has quit IRC15:06
*** ppai has quit IRC15:08
*** amit213 has joined #openstack-swift15:08
*** haomaiwang has quit IRC15:09
mahatic_acoles: nice! good luck with the demo15:09
claygacoles: hey!  are you at home?  I have a question for you boys...15:12
acolesclayg: i'm here15:12
claygacoles: I went to see a band last night "The Savages" - they're from London and they're pretty good!15:12
claygacoles: have your boys ever heard of these gals?15:12
acolesclayg: oic yeah i would need to ask the boys, i haven't heard of them15:13
clayg:)15:13
acoleswhere did they play?15:13
claygk, they were pretty raucous - not sure if they're really that big in the London rock scene but we had a good time15:14
claygThe Fillmore15:14
*** cdelatte has quit IRC15:15
*** cdelatte has joined #openstack-swift15:17
acolesclayg: looks good. whenever I think I know what the boys are into it seems they have moved on :)15:17
acolesclayg: i was looking for gigs in Austin since its the music capital of somewhere15:19
acolesopenstack falls between paul simon and F1 grand prix i think15:19
*** jordanP has quit IRC15:21
claygacoles: of the WORLD - the whole world man - and they hid it in the middle of Texas to keep out the yellow-bellies15:21
*** haomaiwang has joined #openstack-swift15:22
jrichlilol15:22
claygacoles: i'd go see paul simon although I probably don't know his solo stuff as well15:22
claygis F1 grand prix... a... band?15:22
acoleslol15:23
acolesclayg: you're confusing it with The Cars...now that was A band15:24
*** StraubTW has quit IRC15:26
claygyeah that'd be good - wikipedia says they're mostly still alive and doing shows as of 2015 - maybe there's still hope!?15:27
*** thingee has left #openstack-swift15:27
*** esker has quit IRC15:28
*** esker has joined #openstack-swift15:28
notmynamegood morning15:32
*** StraubTW has joined #openstack-swift15:32
*** links has quit IRC15:32
*** dmorita has joined #openstack-swift15:34
*** siva_krishnan_ has quit IRC15:34
*** dmorita has quit IRC15:35
*** esker has quit IRC15:36
*** haomaiwang has quit IRC15:36
*** siva_krishnan_ has joined #openstack-swift15:36
notmynamelooks like it's been repeated enough (thanks!) but reminder that there is not meeting this week15:42
notmynameand of course no meeting next week either, in lieu of the summit15:43
*** cdelatte has quit IRC15:43
notmynameacoles: how's "have a good feature branch for the summit" looking?15:45
acolesnotmyname: good news is that with mahatic's help we should have some BYOK support15:46
notmynamecool15:46
acolesbut i'm wary of merging copy middleware on the feature branch - feels like its making work, so we may not be quite there15:47
acolesi can propose it so its on gerrit15:47
acolesbut unpicking it could be painful15:47
openstackgerritMerged openstack/swift: crypto - Update container with correct etag on POST  https://review.openstack.org/30599515:48
tdasilvaacoles: we have one +2 :)15:48
*** lakshmiS has joined #openstack-swift15:49
jrichlire: unpicking could be painful: +115:49
acolestdasilva: yeah i saw, on decoupling versioned writes correct? :) but IDK, i'm guessing the actual middleware patch has had less review time?15:49
*** siva_krishnan_ has quit IRC15:49
tdasilvaacoles: yeah, i'm just looking for anything to be optimistic about :)15:50
acolestdasilva: heh15:50
*** cdelatte has joined #openstack-swift15:50
acolesnotmyname: i'm scripting a demo cos i know my hands will be too shakey to type!15:51
jrichliyeah, I think we all did a great job getting most of the branch "todos" worked.  but COPY not being there is the big one.  still some little todos, but there was a llot15:52
jrichliof progress15:52
*** gyee has joined #openstack-swift15:54
notmynameacoles: that is absolutely the thing to do :-)15:54
notmyname(scripting a demo)15:54
*** mmotiani_ has joined #openstack-swift15:57
*** mmotiani_ has quit IRC15:57
*** nadeem has quit IRC15:58
*** mmotiani_ has joined #openstack-swift15:59
*** ntata- has joined #openstack-swift16:00
*** siva_krishnan_ has joined #openstack-swift16:02
timburkegood morning16:08
*** cdelatte has quit IRC16:10
*** _JZ_ has joined #openstack-swift16:11
*** cdelatte has joined #openstack-swift16:12
*** ppai_ has quit IRC16:13
*** cdelatte has quit IRC16:14
*** lakshmiS has quit IRC16:15
*** lakshmiS has joined #openstack-swift16:15
*** cdelatte has joined #openstack-swift16:16
*** ChubYann has joined #openstack-swift16:17
*** hosanai has quit IRC16:17
*** SkyRocknRoll has joined #openstack-swift16:18
admin6Hi chat, Could one explain me what means error message type : "RingValidationWarning: The partition 1968 has been assigned to duplicate devices" when rebalancing a ring. I’m still fighting with this.16:19
claygadmin6: how old is this ring?16:20
admin6it’s a fresh one declared today16:20
*** mingyu has joined #openstack-swift16:21
claygadmin6: it *means* that multiple replicas of the partition 1968 (good year) have been assigned to a device - it shouldn't happen - so we validate against.16:21
claygit's like a constraint16:21
claygadmin6: that's *fascinating* - do you think you could reproduce the error?  If you created a ring with the same params again?16:22
*** jistr has quit IRC16:22
claygoh... maybe it's less facinating that I thought - that's a Warning - not an error16:22
admin6clayg: yes I can, I’m just playing with new rings to understand this error16:23
claygif you're running idk, swift 2.5? 2.4?  somewhere in there it was just broken - it's when we started emiting the warning16:23
admin6clayg: warning ;-)16:23
claygit's fixed now!  get you some swift 2.7!  you should almost definately not get that invalid state on a fresh ring with swift 2.716:23
*** lyrrad has joined #openstack-swift16:24
admin6I think It’s swift 2.6, (at least client python swift-client is 2.6)16:25
claygi have no idea if the client and storage system have related version numbers16:26
clayghow did you install swift?16:26
admin6sorry it’s version 2.5.0 : version embebed in ubuntu 15.1016:27
claygbummer :'(16:28
claygluckily ring balancing is out of band to the servers and the format hasn't changed - so you can use swift-ring-builder from 2.7 with services installed on swift 2.5 (although I'd recommend just upgrading everyting because swift 2.7 is *awsome*)16:29
*** arch-nemesis has quit IRC16:29
claygbut... i suppose the part placement algorithm *did* work back then - it just took some be carefuls - e.g. you have to have as many devices as you do replicas?  Can't put 3 replicas of each part on two devices without duplicate assignments16:31
*** jmccarthy1 has quit IRC16:31
admin6ok. I think I’ll choose the upgrade solution :-)  Are you interrested in getting the commands I used to reproduce the context?16:31
*** cdelatte has quit IRC16:31
claygthere's also some futzy stuff if you have zones that don't have roughly equal weights in them - or fewer failure-domains than replicas at any given tie16:32
admin6clayg: no, I always have more disks than the number of replicas in all the rings (even the erasure coding one with 12 "replicas")16:32
claygnot... terribly so?  as i recall it was sort of trivial to break the old placement stuff - like there was litterly dozens of things that could go wrong and many of them weren't even that uncommon or esoteric16:33
claygok, gl with the upgrade solution - if you wanna do a swift-ring-builder-analyzer template that might be useful - i could at least sanity check you -> http://docs.openstack.org/developer/swift/overview_ring.html#module-swift.cli.ring_builder_analyzer16:35
claygadmin6: but you could just upgrade too - i bet new swift will be great - eyes forward!16:36
*** cschwede has quit IRC16:36
admin6clayg; Ok, many thanks for your expertise16:36
*** tmoreira has quit IRC16:37
*** tmoreira has joined #openstack-swift16:41
*** cschwede has joined #openstack-swift16:43
*** arch-nemesis has joined #openstack-swift16:43
*** david-nesher has joined #openstack-swift16:45
*** Guest67082 has quit IRC16:46
*** mingyu has quit IRC16:47
*** zul has quit IRC16:48
*** cdelatte has joined #openstack-swift16:50
*** joeljwright has quit IRC16:52
*** rledisez has quit IRC16:52
*** chuck__ has joined #openstack-swift16:54
*** mingyu has joined #openstack-swift16:54
*** sgundur has quit IRC16:57
*** sbezverk has joined #openstack-swift16:58
*** thumpba has joined #openstack-swift16:58
sbezverkHello, we have to change default rsync port to different value, do you see any problem in using a non-default port and is there any dependecies hardcoded in configuration files for a default port?16:59
*** NM has quit IRC16:59
*** sgundur- has joined #openstack-swift16:59
*** sgundur- has left #openstack-swift17:00
claygsbezverk: yes I believe that doesn't work by default?17:01
*** sgundur has joined #openstack-swift17:01
claygwell... i could be wrong... is possible device metadata get's interpolated into the rsync_module template - so you might be able to annotate devices - i'm not sure it's described in the docs?17:02
sbezverk+clayg thank you for your reply in kolla project we run swift in docker containers and due to some security issues have to change default port17:02
claygsbezverk: ok, it's a good use case - let me check something17:03
sbezverk+clayg I cannot find any references or guidelines for this non-default port scenario17:03
claygyeah - it's a little janky -> http://docs.openstack.org/developer/swift/misc.html#swift.common.utils.rsync_module_interpolation17:04
clayglooking at the source the device "meta" key *is* interpolated into the rsync_module - but there's no defined k/v syntax - so it'd be a weird coupling - but it might work - i've never tried it17:05
*** SkyRocknRoll has quit IRC17:07
sbezverk+clayg are you saying that it might work without any additional configuration?17:07
claygno17:07
claygit might work with additional sort of baroque undocumented configuration - but it also might now17:08
clayg*not17:08
claygi was gunna bring up my dev instance and see if I could get you a little script to pay with17:08
sbezverk+clayg I would really appreciate if you do that17:09
sbezverk+clayg at this point for us it is a show stopper, as we have to run as root17:09
notmynameFYI, the proposed design summit split that was talked about a while back seems to be a done deal. the conversation seems to only be about the details of how each thing will work instead of if it will happen http://lists.openstack.org/pipermail/foundation-board/2016-April/000226.html17:10
openstackgerritAndy McCrae proposed openstack/swift: Allow fallocate_reserve to be a percentage  https://review.openstack.org/28801117:12
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/17434317:13
*** klrmn has joined #openstack-swift17:16
notmynameglange: are you going to be at the summit?17:18
*** _JZ_ has quit IRC17:19
claygsbezverk: so you can deifnately stick a devices meta field into your rsync module - i think the syntax would line up such that you can make the rsync command come out pointint to a non-default port if you just fill in whatever port your rsync daemons are configured to listen on as "meta" on the device when building the ring and then update your rsync_module config opiton on your *-replicator sections -> https://gist.github.c17:21
*** haomaiwang has joined #openstack-swift17:21
notmynameclayg: that cut off in the middle of the gist url17:22
claygboooo!17:22
clayghttps://gist.github.com/clayg/93bcc37ec4f5fc7ab028f07ac430514817:22
sbezverk+clayg thank you17:22
*** NM has joined #openstack-swift17:22
*** zaitcev has joined #openstack-swift17:22
*** ChanServ sets mode: +v zaitcev17:22
*** diazjf has joined #openstack-swift17:23
*** mmcardle has quit IRC17:24
*** mingdang1 has joined #openstack-swift17:24
sbezverk+clayg when we deploy kolla we use master source and would like to continue doing so. Do you think swift team could expose rsync port parameter in the configuration file, so we do not have to hack the code.17:25
claygsbezverk: the rsync_module template may need to be more like... idk "rsync://{replication_ip}:{meta}/object" ???17:25
*** ober37 has joined #openstack-swift17:25
claygsbezverk: the default seems to be "{replication_ip}::object" which gets joined into in front of '<device>/objects/<part>'17:26
claygsbezverk: testing from the command line rsync doesn't seem to like "{replication_ip}:{meta}::object" - but was ok with "rsync://{replication_ip}:{meta}/object" - so you will probably have to play around with the exact syntax17:27
claygsbezverk: yeah i mean I think it would just be documenting this configuration?  I'm trying to tell you how you can configure swift for this - if it works you could document it for the next guy - probably somewhere in http://docs.openstack.org/developer/swift/replication_network.html17:28
*** pc6411 is now known as pchng17:28
*** mingdang1 has quit IRC17:28
sbezverk+clayg sure thing at first I thought it would require code change17:29
sbezverk+clayg if it is just to figure out right syntax for configuration item then it is exactly what we need.17:30
*** yarkot has joined #openstack-swift17:32
tdasilvanotmyname: so basically they are replacing mid-cycle meetups with an developer oriented event planned by the foundation17:33
claygsbezverk: ok, I think i have enough info in the gist - you need to update the config option - but also annotate your devices in the ring with metadata17:33
*** diazjf has quit IRC17:33
notmynametdasilva: yes. (maybe?)17:33
claygnotmyname: they can take our design summits - but they can never take our FREEEDOOOOOM^wMid-Cycles17:35
claygi love how the reaction to wow - the project organized mid-cycles are more productive than the foundation organized event - let's have the foundation organize the mid-cycle!17:35
tdasilvalol17:36
tdasilvanice way of looking at it17:36
notmynamethat's the way it looks, but it's also something that we should be a part of next week and as any discussion continues17:37
claygtdasilva: it's probably terribly unproductive acctually - i'm sort of a cynic17:37
notmyname(but to be fair, the way I saw it happen was "here's an idea..." followed by "well now that this idea is happening...")17:37
tdasilvabut also reducing the developers meeting time from 4 to 2 times a year17:37
tdasilvaclayg: no worries, i'm the same17:37
notmynametdasilva: but it doesn't. there's still the summits17:37
notmynameand meeting together less often is the wrong way to go!17:37
tdasilvanotmyname: yeah, but there wouldn't be a "design" time at the summit17:38
notmynameand if there is still some need to have other in-person meetings (mid-mid-cyles?), then that's 6 international trips a year for some people! that's terrible17:38
tdasilvajust marketing summit with user <> developer time17:38
claygtdasilva: you try putting more than 5 swift developers in the same city and see if there's no design going on17:38
tdasilvalol17:38
tdasilvaclayg: can't argue with that17:38
notmynametdasilva: but there is. the summits still have a place for the devs to talk to users/ops about what needs to be done17:39
notmynameand the new event is for figuring out how to do those things17:39
notmyname(I don't think you can actually separate those conversations, though. that's like uber-waterfall design)17:39
notmyname"We still expect many key developers will attend the the community-wide Summit events"   <--- tdasilva, that includes you. congratulations17:40
tdasilvanotmyname: talk about the "what" and in 3 months talk about the "how"17:40
claygnotmyname: I basically just hear you saying we'll have 4 foundation events a year to schedule our project organized events inbetween - if that means we would have done both jrichli's and acoles's events w/i the same OS relase I'm totally down17:41
clayg... acctually it sounds exahusting17:41
tdasilvaclayg: that would be 6 events17:41
notmynamesomeone pointed out to me that we're getting close to 10% of a year (or more) in travel related to swift. that's a lot more than some people signed up for17:42
claygyeah seems like a lot - i'm good on... 4 events a year - crap... that's what we already have tho?17:42
tdasilvaright, yeah, i've thought of that 10% number also17:42
notmynameyeah. right now we're at 4 times a year. once a quarter, basically17:42
clayghrmmm...17:43
claygmaybe the *can* take our mid-cycles :'(17:43
*** Suyi has joined #openstack-swift17:45
tdasilvai'm also wondering about the plan to put these new PTGs in "cheaper" cities. I would this it's still a 1K people event, so there will be a need for a medium size city17:46
notmynametdasilva: "don't worry. it's just the devs. you can put them in the cheap city" ;-)17:46
*** dmorita has joined #openstack-swift17:48
*** dmorita has quit IRC17:48
notmynamehere's the cross-project session for discussing it17:48
*** dmorita has joined #openstack-swift17:48
notmynamehttps://www.openstack.org/summit/austin-2016/summit-schedule/events/947817:48
claygtdasilva: was there a post on the ML recently about this?  I've never heard of this "PTG"?17:48
tdasilvai bet you can't find a venue to host 1k people in westford or longmont17:49
notmynameclayg: yeah, I just linked it above (probably when you were writing that rsync gist)17:49
notmynameclayg: http://lists.openstack.org/pipermail/foundation-board/2016-April/000226.html17:49
zaitcevAlbuquerque easily hosts 1000-people events, and it's only 600,000 people in the metro area.17:50
notmynameand the two most recent posts on http://ttx.re talk about it17:50
*** mwheckmann has quit IRC17:50
notmynamehttps://www.youtube.com/watch?v=e8TUwHTfOOU17:50
tdasilvaclayg: so yeah, i'm putting together this email that notmyname just linked with an earlier email when they were proposing the idea. One of the reasons was that a smaller devs event could be hosted in "cheaper" cities, didn't have to be tokyo or paris or barcelona17:50
timburkezaitcev: but what if we miss that left turn on the way home and never get back?17:51
jrichliwell, at least http://ttx.re has some better arguments than the mail I had read in the past17:52
jrichlinot that i like it ...17:52
ahale_"dev kings listening to grievances in their throne hall" - I've not been to a summit since boston, is there actually a throne hall now?17:53
claygnotmyname: oh sorry - you didn't need to re-link i had it in scrollback - dunno why it's not in my inbox yet tho?  does that information only matter to "foundation-board"?  good think notmyname is like hacker news for openstack ML's17:53
*** sgundur- has joined #openstack-swift17:53
*** daemontool has quit IRC17:53
*** sgundur has quit IRC17:54
clarkbahale_: there have been ops feedback sessions since atlanta iirc17:54
clarkbclayg: it is an open list but you have to subscribe or troll the archive17:54
claygthe rooms in the hotel in Toyko did sorta have a throne room feel to it yeah...17:54
tdasilvagotta write that down somewhere...could make to a slide one day:  "notmyname is like hacker news for openstack ML's" ;)17:55
clarkbthe board has a separate private list for private things iirc17:55
redboThat doesn't seem very four opens.17:56
clarkbI think it has to do with legal issues17:56
glangenotmyname: I'm not going to the summit -- we are sending quite a few people though17:56
clarkbwhich necessarily cannot be public?17:56
notmynameglange: ok17:56
clarkbthere was a whole thing about it a couple years back17:56
clayg'and become true "OpenStack" contributors' <- totally a goal of mine17:56
notmynameyeah, the openness of the foundation ML was a big deal...right what clarkb said17:57
notmynameso the legal stuff about pay and stuff like that is still private, but everything else is now open (wasn't originally)17:57
*** esker has joined #openstack-swift17:59
*** ChubYann has quit IRC18:07
*** StraubTW has quit IRC18:13
*** garthb has quit IRC18:19
*** ChubYann has joined #openstack-swift18:20
*** StraubTW has joined #openstack-swift18:20
*** nadeem has joined #openstack-swift18:29
*** nadeem has quit IRC18:31
*** haomaiwang has quit IRC18:35
*** daemontool has joined #openstack-swift18:35
*** mwheckmann has joined #openstack-swift18:37
*** haomaiwang has joined #openstack-swift18:37
*** nadeem has joined #openstack-swift18:37
*** garthb has joined #openstack-swift18:51
*** mwheckmann has quit IRC18:54
*** joeljwright has joined #openstack-swift19:00
*** ChanServ sets mode: +v joeljwright19:00
*** tqtran has joined #openstack-swift19:00
*** StraubTW has quit IRC19:01
acolesjoeljwright: did you see there is no meeting tonight?19:02
joeljwrightyes, Isaw, thanks :)19:02
joeljwrightgives me more time for other work...19:03
joeljwrightacoles: how's your Austin prep coming?19:03
*** rcernin has quit IRC19:05
*** aimeeU has quit IRC19:06
acolesjoeljwright: its coming along ok thanks19:07
acolesgood night19:07
jrichlinight!19:07
joeljwrightnight!19:08
*** acoles is now known as acoles_19:08
*** mwheckmann has joined #openstack-swift19:08
*** StraubTW has joined #openstack-swift19:08
*** joeljwright has quit IRC19:08
*** StraubTW has quit IRC19:08
*** StraubTW has joined #openstack-swift19:09
*** Suyi has quit IRC19:12
*** Suyi has joined #openstack-swift19:12
*** haomaiwang has quit IRC19:13
*** sheel has quit IRC19:15
*** nadeem has quit IRC19:27
openstackgerritDaisuke Morita proposed openstack/swift: Update Metadata after 'sync' op in account/container replicator  https://review.openstack.org/30249419:27
*** haomaiwang has joined #openstack-swift19:27
*** nadeem has joined #openstack-swift19:28
*** siva_krishnan_ is now known as siva_krishnan19:28
openstackgerritMerged openstack/swift: Require account/container metadata be UTF-8  https://review.openstack.org/28575419:30
*** rcernin has joined #openstack-swift19:31
*** ametts has quit IRC19:33
*** haomaiwang has quit IRC19:33
*** haomaiwang has joined #openstack-swift19:36
*** haomaiwang has quit IRC20:02
*** mariusv has quit IRC20:08
*** nadeem has quit IRC20:11
*** mingyu has quit IRC20:13
*** haomaiwang has joined #openstack-swift20:17
*** thumpba has quit IRC20:23
*** NM has quit IRC20:32
*** geaaru has quit IRC20:34
*** haomaiwang has quit IRC20:36
*** haomaiwang has joined #openstack-swift20:38
*** haomaiwang has quit IRC20:39
*** nadeem has joined #openstack-swift20:42
*** asettle has joined #openstack-swift20:42
*** mingyu has joined #openstack-swift20:43
*** nadeem has quit IRC20:45
*** asettle has quit IRC20:45
*** nadeem has joined #openstack-swift20:46
*** mingyu has quit IRC20:48
*** _JZ_ has joined #openstack-swift20:52
*** daemontool has quit IRC20:56
*** esker has quit IRC20:56
*** m_kazuhiro has joined #openstack-swift20:59
notmynamezaitcev: have you played with ceph's bluestore? based on my initial read about it, it looks pretty interesting21:13
notmynamegranted, I've only read a blog about it...21:16
pdardeaui'm trying to follow-up on keystone/swift integration pain points at summit21:17
notmynamepdardeau: +121:18
pdardeauanyone remember the specifics?21:18
pdardeaui'm trying to rope in some keystone guys so that we can have some cross-project discussion on it21:18
notmynamepdardeau: a lot of it is around CLI/SKD integration issues. session objects, when to use which auth version and how to figure that out without 2 dozen different CLI options21:18
pdardeaui remember: scalability limits with keystone, keystone api versioning pain, too simplistic policy.json, desire for something like saio but for keystone21:19
notmynamekeeping token info across requests in the CLI21:19
*** m_kazuhiro has quit IRC21:19
notmynameah, the policy.json was a comment donagh had made about the samples, not what's possible21:19
notmynamebut yeah, we've got the policy.json work too that hisashi is working on21:20
pdardeauif anyone is interested in meeting up with keystone guys at summit, please let me know and i'll try to set up informal discussion21:20
notmynamefrom a dev side, setting up a simplistic, stable keystone for testing would help with further dev/integration work from the swift side21:20
notmynamepdardeau: thanks21:21
pdardeaunotmyname: thx for clarifications21:21
notmynamethere's the "received wisdom" (which AFAIK hasn't been retested in a while) about keystone not able to handle the load from busy swift clusters21:22
*** sbezverk has quit IRC21:25
*** sbezverk has joined #openstack-swift21:27
*** _JZ_ has quit IRC21:27
stevemarnotmyname: pdardeau you guys are more than welcome to crash a keystone design session or two21:31
stevemarkeystoners don't bite :)21:31
notmynamestevemar: so are fernet tokens a thing everyone should be using today? or not yet? or not ever?21:34
pdardeaustevemar: cool. i might do that21:34
stevemarnotmyname: they should totally be used today21:34
stevemarnotmyname: IIRC, mfisch is using them today in production at TWC21:34
stevemarpretty sure rax and ibm clouds are using them too21:35
notmynamestevemar: cool. but he does nova. I want to hear what Vinsh says for using them with swift ;-)21:35
stevemarnotmyname: i would hope it didn't matter what service is using it21:36
notmynamestevemar: with fernet, does each auth request get a new token (within some short amount of time)? IOW are they cachable or would swift see a new one every time for every request?21:36
stevemarthe policy stuff is sadly still an issue :(21:36
notmynamestevemar: right. just that nova loads are generally lower than swift loads :-)21:36
stevemarnotmyname: they would see a new one, its the way they are validated that is different21:37
notmynamewhich means that the load to keystone (req/sec) would go up when using fernet. specifically, it goes up by the cache-hit rate with uuid tokens21:38
stevemarwith fernet you don't have to go back to keystone to validate, they are validated offline21:38
stevemarlet me double check if they are cachable...21:38
* stevemar looks at code21:38
*** CaioBrentano has quit IRC21:41
notmynamestevemar: thanks for the info21:42
VinshFernet all the way +121:43
stevemarVinsh: \o/21:43
notmynameVinsh: cool, that's good to hear21:43
Vinshbeen swifting and ferneting for a solid year.   Transition wasn't even a thing users detected.21:43
redboI don't know how applicable it is to our auth (which is only keystone-ish), but we had some problems with people whose scripts authenticate frequently, and they get new tokens every time now.21:44
*** cdelatte has quit IRC21:44
* Vinsh same team as mfisch btw.21:45
stevemarnotmyname: so, in keystonemiddleware (keystone_authtoken), it's smart enough to cache tokens so you don't have to do that for every request21:45
stevemarVinsh: nice to meet you :)21:45
VinshFernet Tokens are cachable, some digging I did on that last week confirms.   Hi stevemar :)21:45
stevemarVinsh: i know mfisch, unfortunately :O21:45
notmynamestevemar: thanks21:46
Vinshstevemar: Indeed :)21:46
VinshI thought I read in the summit talk he is doing that fernet will be the standard soon and all other tokens deprecated (in the O release).21:48
timburkenotmyname: there's a decent start on allowing swiftclient to use sessions in patch 298968 - i even did a follow-up to add a v1 plugin in patch 300697 so swift devs could get a feel for it against tempauth/swauth21:49
patchbottimburke: https://review.openstack.org/#/c/298968/ - python-swiftclient - Adding keystoneauth sessions support21:49
patchbottimburke: https://review.openstack.org/#/c/300697/ - python-swiftclient - Add v1password keystoneauth plugin21:49
timburkethat first patch still doesn't have us instantiating any sessions ourselves, but it'll allow other projects to pass in sessions when creating Connections21:51
*** lakshmiS has quit IRC21:53
notmynametimburke: that sounds like progress21:53
timburkedefinitely. and we can work backwards from there a bit: start instantiating our own sessions given some auth args to Connection; allow SwiftService to accept a session and safely share it across threads; have SwiftService instantiate a session from auth args...21:56
notmynamepdardeau: ^ ;-)21:56
pdardeaunotmyname, timburke got it, thx!21:59
timburkenow that we've got the optparse -> argparse transition out of the way, the ultimate goal is to get rid of most/all of our --os-* options and let keystoneauth handle them through loading.register_auth_argparse_arguments and loading.load_auth_from_argparse_arguments21:59
*** asettle has joined #openstack-swift22:01
jamielennoxtimburke: whilst i love people using the keystone loading for that, you might want to jump straight to os-client-config22:06
sbezverk+clayg ping22:07
*** marcusvrn_ has quit IRC22:13
timburkejamielennox: it's taken me this long just to wrap my head around the keystone bits. one step at a time :-)22:20
jamielennoxtimburke: :) it's great swift is looking at it because it22:23
jamielennox's the last holdout, just saying you'll have mordred around pretty quick replacing it with os-c-c for the whole OS_CLOUD= thing22:23
claygsbezverk: pong22:23
*** gyee has quit IRC22:25
mattoliveraumorning22:26
*** asettle has quit IRC22:26
*** asettle has joined #openstack-swift22:27
clayglol @ timburke22:28
*** mingyu has joined #openstack-swift22:33
*** StraubTW has quit IRC22:33
sbezverk+clayg I tried configuring follwoing your guidelines22:33
sbezverk+clayg I generated rings using new R syntax22:33
sbezverkI see now this message in the log, I wanted to check with you if it is expected22:34
sbezverkswift-object-replicator: Can't find itself 192.168.80.25 with port 6000 in ring file, not replicating22:34
*** mwheckmann has quit IRC22:35
*** arch-nemesis has quit IRC22:36
claygsbezverk: no that's probably not right - what "R syntax"22:36
*** mingyu has quit IRC22:37
sbezverk+clayg object.builder add z1-192.168.80.25:6000R192.168.80.25:10873/d1 122:42
sbezverkin the doc you gave me the link, they suggested to use this format when building rings22:42
claygsbezverk: ok yeah that format is fine - but you need d1_<rsync_port> for the rsync_module with the {meta} thing to work22:48
claygthe replication ip and port is for replication object servers - if you're not running a object-server process on 10873 that's probably not what you ment to put in the ring22:48
claygr1z1-192.168.80.25:6000/d1_10873 should let you use a rsync_module template like 'rsync://{ip}:{meta}/object' or something close to that22:49
claygsbezverk: ^22:50
*** nadeem has quit IRC22:52
sbezverk+clayg so I need to rebuild ring with 6000/d1_10873 right?22:56
claygsbezverk: worth a shot22:56
claygi have to bounce pretty quick - if you're still fighting with it you could ask someone else here - or drop me a message and I'll probably see it later22:57
sbezverk+clayg sure thing, will try it, who would you suggest to ping with this?22:58
claygoh idk - just ask - people like to help - except glange22:59
claygglange: ;)22:59
sbezverk+clayg thanks23:05
*** mingdang1 has joined #openstack-swift23:06
*** Suyi has quit IRC23:07
*** Suyi has joined #openstack-swift23:07
*** km__ has joined #openstack-swift23:08
*** km__ is now known as Guest8162123:08
sbezverkfolks could you please check new rings I rebuild for a non-default rsyncd port: http://paste.openstack.org/show/494902/23:16
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:18
*** ozialien has joined #openstack-swift23:20
*** Lickitysplitted_ has quit IRC23:36
*** Lickitysplitted has joined #openstack-swift23:36
*** kei_yama has joined #openstack-swift23:36
*** thumpba has joined #openstack-swift23:38
zaitcevnotmyname: Sorry, I have not touched bluestore. I don't even know what that is. I know that Sage wanted to create a user-mode filesystem or store... But I thought that was called "newstore".23:39
notmynamezaitcev: I think that was the code name23:40
*** lakshmiS has joined #openstack-swift23:41
*** _JZ_ has joined #openstack-swift23:44
*** asettle has quit IRC23:47
*** asettle has joined #openstack-swift23:47
*** mingyu has joined #openstack-swift23:48
*** mwheckmann has joined #openstack-swift23:50
*** jamielennox is now known as jamielennox|away23:51
*** sbezverk has quit IRC23:52
*** mingyu has quit IRC23:53
*** sbezverk has joined #openstack-swift23:56
*** rickyrem has quit IRC23:58
*** rickyrem has joined #openstack-swift23:58

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