Wednesday, 2017-04-26

kota_good morning00:16
timburkegood morning kota_!00:21
kota_hi timburke o/00:21
kota_thx for reviewing the composite ring patch. I responded to it. And more, I did for some swift3/liberasurecode reviews00:22
kota_timburke: ^^00:23
kota_timburke: reading the irc log for a few days ago, we've had a bunch of pending liberausrecode patches?00:23
timburkei saw! thank you. i'll have to think more about dealing with that 404->204 translation...00:24
timburkeyeah, a  fair few. most of them have been sitting there a while, though https://review.openstack.org/#/q/is:open+(project:openstack/pyeclib+OR+project:openstack/liberasurecode)+-label:Code-Review-1%252Cself+-label:Code-Review%252B2%252Cself00:25
timburkei probably wouldn't have noticed either, except that i finally got around to writing https://review.openstack.org/#/c/459023/00:25
patchbotpatch 459023 - liberasurecode - Consistently use zlib for crc3200:25
kota_alright, it looks good query00:27
openstackgerritMerged openstack/pyeclib master: Add explicit info for immeasurable throughput  https://review.openstack.org/41344400:30
*** Sukhdev has quit IRC00:33
*** vinsh has quit IRC00:34
*** vinsh has joined #openstack-swift00:35
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873600:38
*** mariusv has quit IRC00:45
*** mariusv has joined #openstack-swift00:47
*** mariusv has quit IRC00:47
*** mariusv has joined #openstack-swift00:47
*** nikivi has quit IRC00:55
*** nikivi has joined #openstack-swift00:58
*** dmellado has quit IRC01:00
*** ejat has quit IRC01:00
*** Administrator_ is now known as zhugaoxiao01:00
*** jlvillal has quit IRC01:01
*** ejat has joined #openstack-swift01:01
*** ejat has quit IRC01:01
*** ejat has joined #openstack-swift01:01
*** dmellado has joined #openstack-swift01:02
*** nikivi has quit IRC01:06
*** jlvillal has joined #openstack-swift01:06
*** nikivi has joined #openstack-swift01:12
*** sgundur- has quit IRC01:14
*** sgundur- has joined #openstack-swift01:14
*** nikivi has quit IRC01:19
*** tdasilva has quit IRC01:21
*** nikivi has joined #openstack-swift01:21
*** tdasilva has joined #openstack-swift01:25
clayg_i don't get it... ring zipping was supposed to be *simpler*01:45
*** vint_bra has quit IRC01:50
*** JimCheung has quit IRC01:50
*** m_kazuhiro has joined #openstack-swift01:57
m_kazuhirogood morning01:57
*** JimCheung has joined #openstack-swift02:10
*** JimCheung has quit IRC02:15
openstackgerritClay Gerrard proposed openstack/swift master: Make add_dev complain louder about missing keys  https://review.openstack.org/45991402:31
*** zhurong has joined #openstack-swift02:33
*** arunman has joined #openstack-swift02:35
timburkeclayg: so the dispersion command requires a builder? what does it need from there that isn't in the resultant ring?02:36
*** arunman has quit IRC02:57
*** bkopilov_ has quit IRC02:57
*** bkopilov has quit IRC02:57
*** zhurong has quit IRC03:15
*** gkadam has joined #openstack-swift03:19
*** psachin has joined #openstack-swift03:21
clayg_timburke: I think you're asking "why can't the dispersion command run on a .ring.gz" - and I don't think I have a great answer03:54
clayg_timburke: the reason historically it wasn't implemented that way is probably two-fold 1) no one gives a shit about .ring.gz's; the builders are *everything* 2) at rebalance the expensive to build dispersion report data structure with all of it's tier counting gets written back/cached into the .builder03:56
*** m_kazuhiro_ has joined #openstack-swift04:02
*** m_kazuhiro has quit IRC04:05
*** JimCheung has joined #openstack-swift04:09
*** klrmn has quit IRC04:09
*** JimCheung has quit IRC04:14
*** psachin has quit IRC04:21
*** psachin has joined #openstack-swift04:23
*** bkopilov has joined #openstack-swift04:33
*** bkopilov_ has joined #openstack-swift04:33
*** JimCheung has joined #openstack-swift04:51
*** JimCheung has quit IRC04:51
*** zhurong has joined #openstack-swift05:07
*** cshastri has joined #openstack-swift05:07
*** flwang1 has quit IRC05:07
*** arunman has joined #openstack-swift05:20
*** ivru has joined #openstack-swift05:27
*** darrenc has quit IRC05:28
*** darrenc has joined #openstack-swift05:28
*** cshastri has quit IRC05:36
*** cshastri has joined #openstack-swift05:41
*** zhurong has quit IRC05:52
*** adriant has quit IRC06:00
*** geaaru has quit IRC06:03
*** SkyRocknRoll has joined #openstack-swift06:10
*** flwang1 has joined #openstack-swift06:10
*** zhurong has joined #openstack-swift06:25
*** ChubYann has quit IRC06:27
*** zhurong has quit IRC06:33
*** JimCheung has joined #openstack-swift06:37
*** hseipp has joined #openstack-swift06:38
*** d0ugal has quit IRC06:39
*** d0ugal has joined #openstack-swift06:41
*** JimCheung has quit IRC06:41
*** iMe has joined #openstack-swift06:51
*** iMe has quit IRC06:58
*** tesseract has joined #openstack-swift07:04
*** m_kazuhiro_ has quit IRC07:05
openstackgerritMerged openstack/swift master: Make add_dev complain louder about missing keys  https://review.openstack.org/45991407:14
*** pcaruana has joined #openstack-swift07:19
*** zhurong has joined #openstack-swift07:27
*** cshastri has quit IRC07:29
*** cshastri has joined #openstack-swift07:29
*** hseipp has quit IRC07:32
acolesgood morning07:45
kota_acoles: good morning07:45
*** hseipp has joined #openstack-swift07:50
*** zhurong has quit IRC08:08
*** mvk has quit IRC08:18
mattoliverauacoles: morning08:25
openstackgerritJoel Wright proposed openstack/swift master: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537108:26
*** jaosorior_away is now known as jaosorior08:28
*** PavelK has quit IRC08:30
*** gkadam is now known as gkadam-afk08:33
*** PavelK has joined #openstack-swift08:41
*** kei_yama has quit IRC08:41
*** mvk has joined #openstack-swift09:00
*** zhurong has joined #openstack-swift09:22
*** zhurong has quit IRC09:37
*** bkopilov_ has quit IRC09:57
*** bkopilov_ has joined #openstack-swift09:57
*** silor has joined #openstack-swift10:29
*** gkadam-afk is now known as gkadam10:30
*** gkadam has quit IRC10:31
*** gkadam has joined #openstack-swift10:31
*** gkadam is now known as gkadam-afk10:31
*** oshritf has joined #openstack-swift10:40
openstackgerritAlistair Coles proposed openstack/swift master: Fix SSYNC failing to replicate unexpired object  https://review.openstack.org/45692110:57
*** bkopilov has quit IRC11:02
*** bkopilov_ has quit IRC11:03
openstackgerritMerged openstack/swift master: Update version from Newton to Ocata  https://review.openstack.org/45346711:10
*** silor1 has joined #openstack-swift11:22
*** gkadam-afk is now known as gkadam11:23
*** silor has quit IRC11:24
*** silor1 is now known as silor11:24
openstackgerritAlistair Coles proposed openstack/swift master: Add probe test for ssync of unexpired metadata to an expired object  https://review.openstack.org/46007311:30
acolesclayg_: ^^ hacked your probe test for unexpired object. TBH I'm not sure which test module it best fits.11:30
acolesrledisez: fyi ^^11:31
*** klamath has joined #openstack-swift11:59
*** klamath has quit IRC11:59
*** klamath has joined #openstack-swift12:00
*** arunman has quit IRC12:14
*** _JZ_ has joined #openstack-swift12:19
*** SkyRocknRoll has quit IRC12:46
*** bkopilov has joined #openstack-swift12:47
*** bkopilov_ has joined #openstack-swift12:48
*** jordanP has quit IRC12:56
*** jordanP has joined #openstack-swift12:56
*** gkadam has quit IRC13:12
*** cshastri has quit IRC13:19
*** tongli has joined #openstack-swift13:20
*** cshastri has joined #openstack-swift13:22
*** geaaru has joined #openstack-swift13:27
*** jaosorior is now known as jaosorior_away13:36
*** geaaru has quit IRC13:52
*** geaaru has joined #openstack-swift13:52
*** catintheroof has joined #openstack-swift13:56
*** chlong has joined #openstack-swift13:58
*** mhks has joined #openstack-swift14:03
*** arunman has joined #openstack-swift14:04
*** psachin has quit IRC14:11
openstackgerritMerged openstack/swift master: Update version in controller-install-rdo  https://review.openstack.org/45680314:38
*** vint_bra has joined #openstack-swift14:44
*** JimCheung has joined #openstack-swift14:46
*** JimCheung has quit IRC14:51
*** tongli has quit IRC15:00
*** klrmn has joined #openstack-swift15:00
*** catintheroof has quit IRC15:10
*** catintheroof has joined #openstack-swift15:11
notmynamegood morning15:11
*** catintheroof has quit IRC15:11
acolesnotmyname: o/15:12
notmynameoh, inteesting. the gate is going to start using systemd. I'm not sure exactly what the implications of that are, but I know it makes people very passionate15:13
notmynamehttps://review.openstack.org/#/c/460062/15:13
patchbotpatch 460062 - openstack-dev/devstack - make USE_SCREEN=False imply USE_SYSTEMD=True15:13
*** tonanhngo has quit IRC15:15
notmynameand FYI fron the ML http://lists.openstack.org/pipermail/openstack-dev/2017-April/115958.html15:21
notmyname^ request for comment on logging a request ID across openstack projects15:22
clarkbnotmyname: one big thing with systemd is it should make clayg's devstack use case of "restart everything" much simpler15:25
clarkbsince you just tell systemctl to restart devstack15:26
notmynameclarkb: I'm a big fan of doing things that make clayg's life simpler15:26
*** pxwang has joined #openstack-swift15:40
*** Sukhdev_ has joined #openstack-swift15:41
*** pxwang has quit IRC15:41
*** jordanP has quit IRC15:42
*** jordanP has joined #openstack-swift15:42
*** klrmn has quit IRC16:00
*** oshritf has quit IRC16:01
clayg_Lol16:11
*** joeljwright has joined #openstack-swift16:17
*** ChanServ sets mode: +v joeljwright16:17
PavelKnotmyname: hi. is it possible to merge patch 458486 with 458485 into stable/newton?16:18
patchbothttps://review.openstack.org/#/c/458486/ - swift (stable/newton) - Fix race when consolidating new partition16:18
notmynamePavelK: yes, I need to take a look at the open backports16:20
notmynamePavelK: but I have a question for you on that. why does a patch on the backport branch matter to you? (as opposed to on master)16:21
*** jaosorior_away is now known as jaosorior16:22
PavelKnotmyname: we would like to update new release of Newton in prod.16:22
notmynamePavelK: ok. why do you want to stick to newton instead of the subsequent releases on master?16:24
PavelKthere is a reason (I didn't hesitate why) to have a more stable release than current stable.. or how to say it. So we plan a big update to newton... hurray16:26
*** jaosorior has quit IRC16:26
*** jaosorior has joined #openstack-swift16:27
*** jaosorior is now known as jaosorior_away16:27
PavelK*not hesitate but deliberate...16:27
*** JimCheung has joined #openstack-swift16:28
*** hseipp has quit IRC16:28
notmynamePavelK: yeah, that was what I'd love to understand better. you can update the deployed code, but you're wanting to only updated to backported patches instead of master16:29
notmynamePavelK: your company is the first (only?) one I know of that is actively updating to stable branches instead of master16:30
notmynameand to be clear, I don't think you're wrong or other people are right. I'm just trying to understand so that we the community can do better things for users16:30
notmynamebut I'm sure you've noticed that we're not great at keeping backports updated (ie you've always got to bug people to review/land them)16:31
PavelKnotmyname: sometimes. we have previous patches as a patch of old release but now there are about 5 patches to be deloyed and newton is candidate for our prod.16:31
*** jamielennox is now known as jamielennox|away16:31
notmynameI'm not sure if that's because we don't see a lot of people deploying stable or people don't deploy stable often because we don't update it frequently16:32
notmynameyeah, I think I understand what you're doing (keeping/applying patches to older releases). but I don't yet understand why you're doing that16:34
notmynameI'd imagine that there's a generic reason of "we don't deploy from master because it's less tested" or something like that. but (1) I think master is probably *more* tested than anything else upstream and (2) we don't break upgrades16:36
notmynameI mean, clearly we try for (2), but we're not perfect (ie bugs)16:36
notmynamemaybe it's just my "cowboy developer" mentality? ;-)16:37
notmynameagain, I don't think you're doing it wrong. just differently than what most of my experience with swift has been. and I've also seen people get less likely to upgrade the older their deployment is (fear of more massive changes), so I'd really hate to see you get pulled into that16:40
notmynamePavelK: related question... do you deploy from an arbitrary commit that you choose or do you only deploy from something tagged upstream?16:41
PavelKwhen I joined CDN team there was 3 releases old stable and we updated to 1 year old stable - it is tested by all of you and we had all bug fixes merged (or patched when .deb builded). I can't give you an answer why we welcome Newton so late...16:41
notmynameeg if a patch has landed on a stable branch but there isn't a new tag on the stable branch yet, would you be able to deploy it?16:41
*** stradling has joined #openstack-swift16:43
*** stradling has quit IRC16:43
PavelKnotmyname: I try to have these two patches in next release of Newton. But if it will not be we will add patch when building our .deb package.16:46
notmynameok16:47
PavelKnotmyname: onovy can give you better answer. I have to say good by today, my baby calls for a bath :-)16:47
notmynameheh ok :-)16:47
notmynamegood night16:48
PavelKthanks. have a good day16:48
*** Sukhdev_ has quit IRC16:48
onovynotmyname: we can deploy without tag, but it's not ideal16:48
onovyideal is to merge all stable patches and make new release16:48
onovyi will upload this bugfix release to debian stretch then16:48
onovy"we don't deploy from master because it's less tested" // yep, that's reason for stable releases16:49
*** chsc has joined #openstack-swift16:50
*** chsc has joined #openstack-swift16:50
notmynameonovy: do you think master is less tested than the stable branches?16:50
onovyeverytime we deployed latest version, we found some bugs. so we will try to deploy older stable release (newton) and lets see if it will be better16:50
onovymaster is not always production ready16:50
*** tesseract has quit IRC16:51
onovy+my motivation is for Debian package16:51
notmynameseems like a catch-22. not prod ready until it's deployed in prod and the bugs are found ;-)16:51
onovyas i sad before, newton is somehow special, because it will be in stretch for years16:51
onovyyep, so we can wait to someone else to deploy it and fix it :))16:52
notmynamelol16:52
onovyand because fixies are visible in master, if i backport fixies to stable, it's obviously more stable16:52
onovybecause it doesn't contain "new bugs" from new release16:52
onovyand old all know bug is fixed16:52
*** geaaru has quit IRC16:52
*** klrmn has joined #openstack-swift16:53
notmynameI've got this vague feeling that something we're doing wrt testing, releases, openstack cycles, stable backports, ... something.. is off. there's somethign that's not quite right. but I can't quite put my finger on what it is16:54
notmynamebut it's related to what you just said16:54
onovybtw: this is never ending discussion, we are talking about it in Debian community16:54
onovyif stable "branches" is wrong, Debian is wrong too16:54
onovyand Ubuntu too16:54
onovywhy is distro maintaining old version of software, just with fixies?16:54
notmynamea question many people have asked (and a reason many other distros and package managers have been invented to work around)16:55
clarkbonovy: fwiw some of us do think its wrong and run rolling distros...16:55
onovyclarkb: i know16:55
onovybut in company where you have thousands of servers of ten of admins it's impossible to maintaing rolling distro16:56
clarkboh sure there are different use cases for both16:56
onovywe need to call "apt upgrade" with security fixies and be sure nothing will break16:56
clarkbmy point was that rolling distros do exist and have many users as does debian so hard to say they are both wrong16:56
onovyif you have one or two home/community servers, rolling updates is perfect16:56
onovyfor my BOTH is correct16:56
onovyand it depends on usecase you have16:56
onovy*for me16:57
onovyfor example for Desktop is Debian useless16:57
notmynamethe slowness of distro updates is arguably a major reason why stuff like pip exists at all16:57
onovy(my DD colleages will blame me :)16:57
onovynotmyname: pip exists not only for distro slownes16:58
onovypip is needed for non linux (non distros) world for example16:58
notmynamenot only, true. I'm just guessing that if distros didn't have really old versions of libraries, pip would have taken a lot longer to invent16:58
onovybut really, it's not needed to argue why stable or rolling updates is better16:58
onovywe have really big stable distros and really big rolling updates based distros16:59
clarkbya mostly just wanted to point out both are valid use cases16:59
onovyclarkb: and i agree :)16:59
timburkegood morning16:59
notmynameI've definitely complained about the "you aren't running the latest nightly build of all your dependencies? wow." mindset before16:59
notmynameso maybe it's a case of "stable for all my dependencies, bleeding edge for me"?17:00
notmynameah, I have a meeting. gotta run17:00
*** mvk has quit IRC17:00
onovymorning17:00
onovyand afk sry :)17:00
openstackgerritAlistair Coles proposed openstack/swift master: Add Composite Ring Functionality  https://review.openstack.org/44192117:03
openstackgerritAlistair Coles proposed openstack/swift master: Add CompositeRingBuilder class  https://review.openstack.org/45382717:03
stradling_Hi, folks -- n00b question. I have Swift/Keystone working (newton,CentOS 7,https) and tried to layer in SSL, without success. I've traced it to my ssl.conf, I think -- does anyone have a working ssl.conf I could use as a crib?17:04
*** geaaru has joined #openstack-swift17:13
MooingLemurI think for prod, you'd want to put something like haproxy in front rather than using python crypto17:16
jrichlifyi: i am still fighting sickness.  wont be at meeting today17:29
acolesjrichli: get well!17:30
*** mvk has joined #openstack-swift17:32
openstackgerritAlistair Coles proposed openstack/swift master: Add composite ring doc  https://review.openstack.org/45150017:38
*** pcaruana has quit IRC17:40
*** hseipp has joined #openstack-swift18:03
*** _JZ_ has quit IRC18:03
*** tonanhngo has joined #openstack-swift18:05
*** cshastri has quit IRC18:05
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873618:20
*** gyee has joined #openstack-swift18:26
*** geaaru has quit IRC18:37
*** arunman has quit IRC18:38
notmynameI'm landing https://review.openstack.org/#/c/459423/ to get the SHA for the 2.14.0 release18:41
patchbotpatch 459423 - swift - authors/changelog for 2.14.018:41
timburkenotmyname: noticed a duplicate in the AUTHORS -- how much do you care?18:43
notmynametimburke: where?18:44
timburkenotmyname: rledisez has two entries18:44
notmynamebah18:45
timburke(which probably also means the mailmap needs updating)18:45
notmynameok, no loss fixing it now (ie burned gate time). I'll push a change18:45
openstackgerritJohn Dickinson proposed openstack/swift master: authors/changelog for 2.14.0  https://review.openstack.org/45942318:46
notmynametimburke: thanks18:48
*** hseipp has quit IRC18:52
timburkesorry...more comments18:58
timburkenot sure i care enough to block it, but...at least i left them18:59
*** ChubYann has joined #openstack-swift19:00
notmynametimburke: good comments, thanks19:01
timburkenotmyname: also, what was your branch point? i was surprised that http://docs-draft.openstack.org/23/459423/2/check/gate-swift-releasenotes/3ebab24//releasenotes/build/html/ didn't list ocata, since cschwede and i landed https://review.openstack.org/#/c/434785/19:03
patchbotpatch 434785 - swift - Update reno for stable/ocata (MERGED)19:03
notmynametimburke: but I don't want to block for those comments19:03
notmynametimburke: last patch set was rebased tip of master19:03
timburkeah, cool. so the +1 Verified results should have it19:04
clayg_whooo reno!19:04
timburkei want my link! i was promised a link if we did all this!19:05
openstackgerritAlistair Coles proposed openstack/swift master: Experimental swift-ring-composer CLI to build composite rings  https://review.openstack.org/45150719:06
acoleskota_: clayg_ : I updated this ^^ to illustrate how patch 453827 works19:07
patchbothttps://review.openstack.org/#/c/453827/ - swift - Add CompositeRingBuilder class19:07
clayg_i was looking at that - so awesome!19:08
timburkewe've at least got something at https://docs.openstack.org/releasenotes/swift/ but nothing at https://releases.openstack.org/teams/swift.html or https://releases.openstack.org/ocata/index.html yet :-/19:08
acoleskota_: clayg : we have a chain now of composite_builder -> CompositeRingBuilder class -> docs -> cli :/19:09
clayg_acoles: i think you're onto something with that interface!19:10
acolesclayg_: it's all your work! I just misinterpret, type, push, repeat :P19:10
clayg_@acoles @kota_ any chance I could talk you into squashing it as composite_builder & docs -> cli so that we can merge composite_builder & docs?19:10
clayg_acoles: :'(19:11
clayg_oh *weird* the whitebackround makes me want to @ tag people!?19:11
acolesclayg_: you're on irccloud again?19:11
notmynameclayg_ is irccloud and clayg is irssi right?19:11
clayg_acoles: I'm on both - but I'm using this one more - it's not *terrible*19:11
clayg_notmyname: yeah that's it19:11
clayg_i might drop the irssi and just use this - I mean ... it's just text chat - how hard is it to get that right?19:12
patchbotirccloud! it's like slack! but for IRC!19:12
clayg_I use irssi for goodness sakes - it's not like I have a really high bar for quality irc interfaces19:12
notmynameclayg_: lol19:12
acolesclayg_: kota_ +1 for squashing if we are happy with the dependent patches19:13
notmynameyou'd think text chat would be pretty good, but it keeps getting reinvented everywhere (and normally poorly)19:13
clayg_it's fine19:13
notmynamethere's text chat in a game I play. no tab complete, no different colors for different people, no keyboard "go to start/end of line"19:14
clayg_ctrl-a ctrl-e work in irccloud but not ctrl-u :'(19:14
clayg_LORD KNOWS CLAYG NEEDS CTRL-U19:14
clayg_probably more than he uses it :\19:15
acolesnotmyname: I wrote something by hand recently, now that *was* weird ;)19:15
clayg_i take notes on paper all the time19:15
clayg_arrows - it's all about the arrows19:15
clayg_and little symbols like "++" and "???"19:15
acolesclayg_: yep, me too, but in this case someone else was supposed to be able to read it19:15
clayg_or "*" the "*" is key19:15
notmynameyou do! you come to a meeting with a pad of paper. and you write on it. someone says something, clayg_ writes soemthign down19:15
*** _JZ_ has joined #openstack-swift19:15
clayg_acoles: that's not gunna work!19:15
notmynamemight just be doodles.. I dunno19:16
notmynamebut everyone else is like "this guy is BUSINESS. he wrote it down!"19:16
acolesnotmyname: I think he writes 'half-wit' whenever I speak19:16
clayg_i take my kids to the grocery story - "here you take the list" - "dad, what does this say" - "good point, kiddo - sorry"19:16
acolesclayg_: "it says cookies"19:16
clayg_rofl19:17
clayg_I feel like my phone should stop buzzing - WHILE I'M IN THIS CHAT?19:17
clayg_stupid phone19:17
* acoles back later19:17
notmynameclayg_: can irccloud do emoji? if so I might have to switch ;-)19:17
clayg_😄19:18
clayg_yes it does!19:18
claygOMG - irssi does :smile:19:18
claygoh.. no only if it's on a line by itself?19:18
clayg_:smile"19:18
clayg_ack!19:18
clayg_😄19:18
clayg_wait... 😄19:18
claygno i guess it's more like irclcoud *sends* unicode?19:19
claygwhat do other people see!?  this is madness!?  is it blue for you too!?19:19
notmynameI see the emoji face from irrccloud nick19:19
*** mhks has left #openstack-swift19:20
timburkei see emojis, except foe the irssi message19:20
timburkei wonder... does anyone's client only expect plane-0 unicode? 🌴19:23
clayg_ok, I think irssi just correctly displays unicode when the irccloud client sends them19:23
claygtimburke: irssi displayed the palm tree correctly19:23
*** silor has quit IRC19:33
claygacoles: rledisez: if patch 456921 works - how is it not a fix for lp bug #165232319:47
openstackLaunchpad bug 1652323 in OpenStack Object Storage (swift) "ssync syncs an expired object as a tombstone, probe test_object_expirer fails" [Medium,Confirmed] https://launchpad.net/bugs/165232319:47
patchbothttps://review.openstack.org/#/c/456921/ - swift - Fix SSYNC failing to replicate unexpired object19:47
*** jamielennox|away is now known as jamielennox19:52
clayg_  X-Object-Meta-Expired: False what is that?19:52
clayg_oh, just some bs object meta - nm19:53
clayg_ok, so patch 456921 definitely still replicates an expired object as tombstone - and if you pull out the "fix" for lp bug #1653836 the test_expirer_delete_returns_outdated_412 probetest goes back to flakey - so at least that makes sense - but I guess I still don't understand what subset of expired + ssync stupidity patch 456921 gets rid off19:59
openstackLaunchpad bug 1652323 in OpenStack Object Storage (swift) "duplicate for #1653836 ssync syncs an expired object as a tombstone, probe test_object_expirer fails" [Medium,Confirmed] https://launchpad.net/bugs/165232319:59
patchbothttps://review.openstack.org/#/c/456921/ - swift - Fix SSYNC failing to replicate unexpired object19:59
patchbothttps://review.openstack.org/#/c/456921/ - swift - Fix SSYNC failing to replicate unexpired object19:59
clayg_i'll keep looking19:59
openstackgerritMerged openstack/swift master: Improve test_get_valid_utf8_str coverage  https://review.openstack.org/45777620:09
*** cbartz has joined #openstack-swift20:15
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873620:16
clayg_ok, i guess i'm satisfied - this specific case is really about rebalancing a metadata-updated-no-longer-expired object20:20
*** _JZ_ has quit IRC20:25
openstackgerritTim Burke proposed openstack/swift master: Make write_builder work with fractional replicas  https://review.openstack.org/46030220:32
*** Sukhdev has joined #openstack-swift20:39
*** cbartz has quit IRC20:43
*** joeljwright has quit IRC20:52
kota_morning20:55
timburkegood morning kota_20:55
kota_hi timburke20:55
mattoliverauMorning20:55
*** joeljwright has joined #openstack-swift20:55
*** ChanServ sets mode: +v joeljwright20:55
timburkegood morning mattoliverau20:56
timburkeand joeljwright20:56
kota_mattoliverau: o/20:56
joeljwrightmorning/evening/afternoon!20:56
joeljwrightI suppose I could have just said 'hello'20:57
notmynamejoeljwright: you're back :-)20:57
joeljwright:)20:57
notmynamejoeljwright: how was skiing?20:57
*** m_kazuhiro has joined #openstack-swift20:57
joeljwrightnotmyname: it was amazing20:57
joeljwrighteverything from 1.5 feet of fresh snow to warm spring conditions20:58
joeljwright:)20:58
joeljwrightwas nice to get home again after a month though20:59
notmynamesounds nice20:59
notmynameteam meeting time in #openstack-meeting20:59
acolesclayg: bug 1652323 is due to the sender's object being expired. the facility to open an expired diskfile that we are proposing may help fix that bug, since the *sender* could open the expired diskfile and send it's data and metadata. but IMHO t it is a different bug and should be a different patch.21:04
openstackbug 1652323 in OpenStack Object Storage (swift) "ssync syncs an expired object as a tombstone, probe test_object_expirer fails" [Medium,Confirmed] https://launchpad.net/bugs/165232321:04
acolesclayg: also, to fix that bug ^^ when rebuilding an EC frag, we'd need a way to tell all the other nodes that we want to get frags from that they should send them even though their diskfiles are apparently expired :/21:08
openstackgerritMerged openstack/swift master: authors/changelog for 2.14.0  https://review.openstack.org/45942321:31
*** oshritf has joined #openstack-swift21:31
*** geaaru has joined #openstack-swift21:35
*** flwang1 has quit IRC21:44
*** chlong has quit IRC21:48
*** m_kazuhiro has quit IRC21:48
clayg_acoles: ugh21:52
*** joeljwright has quit IRC21:53
clayg_I feel like maybe we messed up with expired .data files - perhaps that should have been at the object-server layer?21:54
clayg_because there you could always say "if we see some metadata that looks expired *and* not replication mode - special case"21:54
clayg_but for just opening then and working with the diskfiles themselves - it's just a piece of meta like any other21:54
clayg_and mostly ignored - unless you're a client request21:55
*** flwang1 has joined #openstack-swift21:56
acolesclayg_: +121:57
acolesclayg_: auditor maybe cares too? but I agree, it's wrong side of the interface21:57
*** flwang1 has quit IRC22:06
*** klamath has quit IRC22:06
openstackgerritTim Burke proposed openstack/swift master: Sync metadata in 'rsync_then_merge' in db_replicator  https://review.openstack.org/30249422:12
openstackgerritTim Burke proposed openstack/swift master: Make write_builder work with fractional replicas  https://review.openstack.org/46030222:18
*** flwang1 has joined #openstack-swift22:33
*** oshritf has quit IRC22:46
openstackgerritTim Burke proposed openstack/swift master: Fix sporadic failure in test/unit/obj/test_server.py  https://review.openstack.org/46034122:55
*** vint_bra has quit IRC23:00
openstackgerritTim Burke proposed openstack/swift master: Fix sporadic failure in TestObjectController.test_container_update_async  https://review.openstack.org/46034623:09
*** Sukhdev has quit IRC23:37
*** kei_yama has joined #openstack-swift23:40
*** Sukhdev has joined #openstack-swift23:42
*** chsc has quit IRC23:47

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