Thursday, 2017-04-20

*** tonanhngo has quit IRC00:08
*** tonanhngo has joined #openstack-swift00:26
*** tonanhngo has quit IRC00:30
*** tonanhngo has joined #openstack-swift00:33
*** tonanhngo_ has joined #openstack-swift00:35
*** tonanhngo has quit IRC00:37
*** tonanhngo_ has quit IRC00:39
*** jerrygb has joined #openstack-swift00:50
*** catintheroof has quit IRC00:52
*** jerrygb has quit IRC00:56
*** gyee has quit IRC01:03
*** klrmn has quit IRC01:13
*** Sukhdev has quit IRC01:25
*** m_kazuhiro has joined #openstack-swift01:30
m_kazuhirogood morning01:31
*** JimCheung has quit IRC01:37
*** jerrygb has joined #openstack-swift01:43
*** chsc has joined #openstack-swift01:49
*** chsc has joined #openstack-swift01:49
charzm_kazuhiro: good morning01:54
m_kazuhirocharz: good morning!01:54
*** zhurong has joined #openstack-swift02:11
*** bkopilov has quit IRC02:13
*** klrmn has joined #openstack-swift02:35
*** gkadam has joined #openstack-swift02:53
*** jerrygb has quit IRC02:55
*** zhurong has quit IRC03:21
mattoliveraum_kazuhiro, charz morning03:25
*** zhurong has joined #openstack-swift03:27
*** zhurong has quit IRC03:31
*** Sukhdev has joined #openstack-swift03:33
m_kazuhiromattoliverau: morning!03:37
*** winggundamth has joined #openstack-swift03:39
*** Sukhdev has quit IRC03:40
*** bkopilov has joined #openstack-swift03:44
*** jerrygb has joined #openstack-swift04:15
*** m_kazuhiro_ has joined #openstack-swift04:21
*** m_kazuhiro has quit IRC04:22
*** zhurong has joined #openstack-swift04:31
*** jerrygb has quit IRC04:32
*** jerrygb has joined #openstack-swift04:32
*** JimCheung has joined #openstack-swift04:38
*** JimCheung has quit IRC04:42
*** psachin has joined #openstack-swift04:44
*** jerrygb has quit IRC04:47
mahaticmattoliverau: m_kazuhiro_ kota_ charz o/04:54
m_kazuhiro_mahatic: o/04:54
mattoliveraumahatic: morning04:57
kota_mahatic: morning04:57
*** chsc has quit IRC05:22
*** ivru has joined #openstack-swift05:26
*** ChubYann has quit IRC05:32
*** cshastri has joined #openstack-swift05:37
*** adriant has quit IRC05:50
ivruhttps://pbs.twimg.com/media/C9xpjGpXcAAzNvH.jpg:large06:10
*** tonanhngo has joined #openstack-swift06:10
*** zhurong has quit IRC06:12
*** rcernin has joined #openstack-swift06:28
*** klrmn has quit IRC06:28
ivruwrong channel, sorry guys06:34
*** hseipp has joined #openstack-swift06:40
*** pcaruana has joined #openstack-swift06:40
*** tesseract has joined #openstack-swift06:56
*** d0ugal has quit IRC06:56
*** tonanhngo_ has joined #openstack-swift07:03
*** tonanhngo has quit IRC07:04
*** jaosorior_away is now known as jaosorior07:11
*** zhurong has joined #openstack-swift07:11
*** m_kazuhiro_ has quit IRC07:22
*** jamielennox has quit IRC07:28
*** gkadam has quit IRC07:29
*** gkadam has joined #openstack-swift07:29
*** jamielennox has joined #openstack-swift07:42
*** geaaru has joined #openstack-swift07:48
*** foutatoro has joined #openstack-swift07:55
*** geaaru has quit IRC07:56
*** cbartz has joined #openstack-swift08:18
acolesgood morning08:20
*** vinsh_ has quit IRC08:22
acoleskota_: ping08:24
*** vinsh has joined #openstack-swift08:27
*** JimCheung has joined #openstack-swift08:39
*** JimCheung has quit IRC08:43
acoleskota_: I wanted to catch up with you re composite ring patches - I am wondering if we are ready to squash patch 449310 and patch 441921?08:46
patchbothttps://review.openstack.org/#/c/449310/ - swift - Add id to RingBuilder to differentiate rings in co...08:46
patchbothttps://review.openstack.org/#/c/441921/ - swift - Add Composite Ring Functionality08:46
acolesAlso I think there is a change still needed that clayg requested to how (if?) metadata is added to the ring (for it to not be completely unstructured but under a fixed key)08:47
kota_good morning, acoles08:48
kota_acoles: sorry, I was not able to look back again that but my first look for patch 449310 patch set 8 (the latest), i think it can be squashed into the parent08:50
patchbothttps://review.openstack.org/#/c/449310/ - swift - Add id to RingBuilder to differentiate rings in co...08:50
kota_i'm feeling08:51
kota_re: structured vs unstructured for the metadata. I don't have strong opinion that we should have structured. sometimes unstructured could be useful so I need to catch up the fear case we should prevent with unstructured metadata08:52
kota_from clayg08:52
kota_acoles: ^^08:52
acoleskota_: ok. thanks for looking.08:53
acoleskota_: I will do the squash, then we can continue the discussion with clayg re metadata08:53
acoleskota_: maybe i can put together a diff for the metadata so we understand what the change would be08:53
kota_acoles: diff at somewhere like gist/paste/another patch?08:56
acoleskota_: either a git or maybe easier to put a follow on patch on gerrit? then squash again if we agree?08:57
acoleswhat do you prefer?08:57
kota_acoles: just a confirmation, anywhere if i can reach is fine08:58
acoleskota_: ok09:01
kota_acoles: thanks09:08
kota_acoles: and sorry, i have to leave here today, will look at the logs tommorow morning to catch up what progressed at that time.09:08
acoleskota_: NP I will be away tomorrow back Monday. thanks!09:09
*** gkadam is now known as gkadam-afk09:26
openstackgerritRomain LE DISEZ proposed openstack/swift master: Fix SSYNC failing to replicate unexpired object  https://review.openstack.org/45692109:30
*** zhurong has quit IRC10:19
*** hosseini has joined #openstack-swift10:23
*** cshastri has quit IRC10:33
openstackgerritMerged openstack/swift master: Update swift version in storage-install-rdo.rst.  https://review.openstack.org/45680610:39
openstackgerritMerged openstack/swift master: Update swift version in storage-install-ubuntu.  https://review.openstack.org/45680810:43
*** cshastri has joined #openstack-swift10:45
*** tonanhngo has joined #openstack-swift10:53
*** tonanhngo_ has quit IRC10:54
*** geaaru has joined #openstack-swift10:54
*** mvk has quit IRC11:06
*** bkopilov has quit IRC11:07
*** jaosorior has quit IRC11:09
openstackgerritMerged openstack/swift master: Remove redundant assignments of self._datadir  https://review.openstack.org/45780711:10
*** zhurong has joined #openstack-swift11:17
*** jaosorior has joined #openstack-swift11:20
*** cshastri has quit IRC11:21
*** cshastri has joined #openstack-swift11:22
*** openstackgerrit has quit IRC11:32
*** winggundamth has quit IRC11:47
*** jerrygb has joined #openstack-swift11:49
*** jerrygb has quit IRC11:54
*** jerrygb has joined #openstack-swift12:09
*** klamath has joined #openstack-swift12:12
*** klamath has quit IRC12:12
*** klamath has joined #openstack-swift12:13
*** jerrygb has quit IRC12:14
*** mvk has joined #openstack-swift12:15
*** catintheroof has joined #openstack-swift12:27
*** catintheroof has quit IRC12:30
*** catintheroof has joined #openstack-swift12:30
*** catintheroof has quit IRC12:40
*** catintheroof has joined #openstack-swift12:41
*** catintheroof has quit IRC12:41
*** catintheroof has joined #openstack-swift12:41
*** catintheroof has quit IRC12:43
*** catintheroof has joined #openstack-swift12:43
*** bkopilov has joined #openstack-swift12:50
*** gkadam-afk has quit IRC12:51
*** jerrygb has joined #openstack-swift12:56
dewanee_hello guys13:09
*** ig0r_ has joined #openstack-swift13:35
*** chlong has joined #openstack-swift13:51
*** vint_bra has joined #openstack-swift13:52
dewanee_an update on the bulk delete operation14:11
dewanee_it just works14:11
dewanee_it was a configuration mistake on the proxy pipeline14:12
dewanee_we can currently delete files and folders in a container even as regular users provided the correct ACL are set14:13
*** xinli has joined #openstack-swift14:16
hugokuomorning guys14:18
hugokuoTwo questions here :14:18
*** Jeffrey4l has quit IRC14:19
hugokuo1. How Swift worker determine which TZ for logging ? We seen nodes have same TZ in CEST from date output.  But nodes have different TZ in Swift logs. I wonder how Swift pick TZ for logging in CentOS 614:20
hugokuo2. Do we have existing topic about the improvement for single token with high concurrency which causes timeout while proxy attempts to validate the token from the memcached host14:21
*** cshastri has quit IRC14:38
*** openstackgerrit has joined #openstack-swift14:39
openstackgerritPavel Kvasnička proposed openstack/swift master: WIP: DB replicator cleanup  https://review.openstack.org/44848014:39
openstackgerritPavel Kvasnička proposed openstack/swift master: DB replicator cleanup  https://review.openstack.org/44848014:39
*** psachin has quit IRC14:42
*** stephen_m has joined #openstack-swift14:49
notmynamehugokuo: perhaps related, https://review.openstack.org/#/c/331369/14:51
patchbotpatch 331369 - swift - Always set swift processes to use UTC (MERGED)14:51
*** ivru has quit IRC14:52
hugokuo@notmyname thx. is this patch will be delivered in next Swift release ?14:53
notmynamehugokuo: correct. it's not yet released in any upstream tag, but it's going to be in the next release (Real Soon Now)14:53
hugokuo@notmyname got it. thx14:53
*** bkopilov has quit IRC14:54
*** PavelK has quit IRC14:55
openstackgerritOndřej Nový proposed openstack/swift master: Fix unit tests on i386 and other archs  https://review.openstack.org/45853914:58
*** rcernin has quit IRC15:01
*** xinli has quit IRC15:07
*** xinli has joined #openstack-swift15:14
*** klrmn has joined #openstack-swift15:14
*** pcaruana has quit IRC15:14
*** oshritf_ has quit IRC15:15
notmynameonovy: my first thought when reading that commit message was "is onovy running on 32bit machines?!"15:19
notmynamebut I see that it's only about IO priority15:20
*** chsc has joined #openstack-swift15:26
*** Jeffrey4l has joined #openstack-swift15:31
*** ig0r_ has quit IRC16:01
*** newmember has joined #openstack-swift16:03
*** tonanhngo has quit IRC16:08
*** zhurong has quit IRC16:11
*** cbartz has quit IRC16:13
timburkedewanee_: glad to hear it! out of curiosity, what was the misconfiguration?16:22
*** newmember has quit IRC16:22
*** newmember has joined #openstack-swift16:23
*** foutatoro has quit IRC16:27
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873616:27
dewanee_timburke, was the lack of bulk support in the pipeline. And apparently clients are not that good in checking that capability16:29
dewanee_I still need to do some digging because a few of the explanation I gave myself in the past weeks proved to be wrong16:29
timburke:-/ that's unfortunate -- was this python-swiftclient? i know that one looks at /info, and bulk should only show up there if it's actually enabled...16:30
openstackgerritAlistair Coles proposed openstack/swift master: Add Composite Ring Functionality  https://review.openstack.org/44192116:33
openstackgerritAlistair Coles proposed openstack/swift master: Add CompositeRingBuilder class  https://review.openstack.org/45382716:33
openstackgerritAlistair Coles proposed openstack/swift master: Make composite_metadata an attribute of RingData  https://review.openstack.org/45858516:33
*** tesseract has quit IRC16:34
dewanee_I need to check with my collegue but afaik we were troubles also with that not accepting multiple files. I'll give you more details tomorrow.16:35
dewanee_*were having troubles16:36
timburkeoh! maybe something where https://review.openstack.org/#/c/454849/ would help?16:38
patchbotpatch 454849 - python-swiftclient - respect bulk delete page size and fix logic error16:38
*** JimCheung has joined #openstack-swift16:38
notmynametimburke: oh! I didn't see your last review comment there16:39
acoleskota_: clayg I made some more notes on etherpad about the interface to a possible CompositeRingBuilder class (under heading Do we pass builders or builder_files to a CompositeRingBuilder class?) - value your thoughts - https://etherpad.openstack.org/p/composite_rings16:39
*** geaaru has quit IRC16:40
timburkenotmyname: then i'm glad i brought it up :-)16:40
notmynametimburke: if you've still got that diff locally, please feel free to push it over. lgtm (at a quick glance)16:40
notmynameyeah, I was kinda busy the last few days and didn't get a chance to do much upstream.16:42
*** SkyRocknRoll has joined #openstack-swift16:43
*** _JZ_ has joined #openstack-swift16:44
openstackgerritTim Burke proposed openstack/python-swiftclient master: respect bulk delete page size and fix logic error  https://review.openstack.org/45484916:47
notmynametimburke: thanks16:47
*** jaosorior has quit IRC16:49
*** SkyRocknRoll has quit IRC16:50
timburkeman, i really should have looked at https://review.openstack.org/#/c/302494/ sooner :-( that patch should not have stood unreviewed for a year...16:54
patchbotpatch 302494 - swift - Sync metadata in 'rsync_then_merge' in db_replicator16:54
*** newmember has quit IRC16:56
*** vinsh has quit IRC17:00
*** vinsh has joined #openstack-swift17:02
*** mvk has quit IRC17:03
*** tonanhngo has joined #openstack-swift17:13
*** tonanhngo has quit IRC17:17
*** tonanhngo has joined #openstack-swift17:17
*** mvk has joined #openstack-swift17:25
*** ig0r_ has joined #openstack-swift17:26
*** hseipp has quit IRC17:34
openstackgerritTim Burke proposed openstack/swift master: fixup! Sync metadata in 'rsync_then_merge' in db_replicator  https://review.openstack.org/45780817:38
*** xinli has quit IRC18:08
claygfixup!  I like it for reviews, but not so much for the commit log?  Is it just a place holder commit message?18:10
timburkeclayg: i use it whenever i fully intend that it should just get squashed into the parent18:10
claygtimburke: full ack - love it - can I steal!?18:11
timburkeabsolutely!18:11
* clayg appropriates more brillance from timburke - nom nom nom18:12
*** Renich___ has joined #openstack-swift18:26
*** ChubYann has joined #openstack-swift18:26
timburkeclayg: i'm looking through the open backports... what are your thoughts on https://github.com/openstack/swift/commit/69f7be9 ? that UpgradeImpact makes me think pavel was probably right to not include that in the backports he proposed... but i figure i oughta get your feel for it, too18:27
*** SkyRocknRoll has joined #openstack-swift18:33
*** Sukhdev has joined #openstack-swift18:34
*** jerrygb has quit IRC18:39
*** Sukhdev has quit IRC18:40
*** Sukhdev has joined #openstack-swift18:40
claygtimburke: i think that is nbd18:42
*** Sukhdev has quit IRC18:43
claygtimburke: i always considered it mostly a doc bug - I think I sorta realized reclaim-age needed to be in DEFAULT section the first time I went to change the value18:43
claygOnly later I realized we had it doc'd wrong18:43
claygthen during doc fix people pointed out how insane the config plumbing was18:43
clayg... and the stupid bug where one place we like... ignored the configured value or some bs?18:43
claygthat's not "upgrade impact" - that's ftfy18:44
claygi just don't think it's a big enough deal to go backporting IMHO - unless someone is asking for it?18:44
*** PavelK has joined #openstack-swift18:45
timburkefor context, i'm looking at https://review.openstack.org/#/c/458485/ -- there were some minor differences as a result of that commit18:45
patchbotpatch 458485 - swift (stable/newton) - Better optimistic lock in get_hashes18:45
claygoh right - and the ftfy is like "if you run with a 1 second reclaim age it's weird" - but OMG dude - why are you running with a 1 second reclaim age!?  The actual impact on "sane" configurations was nominal - and fixing the plumbing doesn't stop you from putting one reclaime in reconstructor and another in replicator - or different values on different configs - which are both worse/operator-error18:46
PavelKtimburke: thanks. in newton is not merged "nice to have" fixes - so little changes were necessary18:46
claygPavelK: ohai!18:46
timburkebut now i'm starting to wonder how much *that* one really belongs on newton... i think ocata would make sense, given the stable policy, but it seems like https://review.openstack.org/#/c/433565/ was the one that really fixed the bug?18:46
patchbotpatch 433565 - swift (stable/newton) - Fix race in new partitions detecting new/invalid s... (MERGED)18:46
PavelKclayg: :-)18:47
claygugh, everytime with the _get_hashes *_*_get_hashes I hate myself so much :'(18:48
claygI don't really see what changed with patch 458485 from the backport18:48
patchbothttps://review.openstack.org/#/c/458485/ - swift (stable/newton) - Better optimistic lock in get_hashes18:48
timburkePavelK: yup, and i think clayg and i agree with your assessment that it was better to have a slightly-changed diff rather than include a not-really-necessary backport18:48
claygbut I'm sure PavelK did it right18:48
PavelKclayg: I'm back in the evening because another performance issue don't give me to have a rest...18:49
claygOH the reclaim_age - timburke you move too fast18:49
claygtimburke: is it weird you're constantly looking around where is everyone and we all a mile behind staring at our belly buttons18:49
*** Sukhdev has joined #openstack-swift18:50
claygPavelK: sorry to hear that, but always happy to get to chat with you :\18:50
*** SkyRocknRoll has quit IRC18:51
*** jerrygb has joined #openstack-swift18:51
timburkeclayg: PavelK definitely did it right. patch looks great, and i'll include some notes for notmyname to call out the differences and why they're fine. right now i'm mainly looking for why that patch *definitely* belongs on the 2.10.x series18:52
claygtimburke: probably the perforamnce thing were we rehash twice?  it's pretty crappy we've done that since the hash invalidations file hit.18:53
claygand the race/correctness w/e18:53
PavelKtimburke: and there was posibility of race contition when force_rewrite was used18:56
*** silor has joined #openstack-swift18:56
claygtypo in commit msg - maybe I should have left it?  I don't really know how to backport18:57
*** tonanhngo has quit IRC19:01
PavelKclayg: timburke: a race condition is for new hashes.pkl fiels - and there is next patch #458486 that solves another situation with new pkl file - and because it removes lines witch I don't like I will be happy merged it too and have it in production soon19:01
patchbothttps://review.openstack.org/#/c/458486/ - swift (stable/newton) - Fix race when consolidating new partition19:01
PavelKin that next patch was removed change of obj.test_reconstructor unit test because in stable/newton is another check that fails on unexpected file. I don't know what change made the difference but it seems correct that there is a difference in reconstructor behaviour.19:07
*** jerrygb has quit IRC19:07
*** silor has quit IRC19:08
timburkei'm a little sad that neither of those newton backports link to a bug in their commit messages :-/19:08
claygtimburke: yeah fix that?  lp bug #165153019:09
openstackLaunchpad bug 1651530 in OpenStack Object Storage (swift) "suffix hash invalidation may be lost" [Critical,Fix released] https://launchpad.net/bugs/165153019:09
timburkeclayg: related, or closes?19:10
claygidk?19:10
claygoh... wow, yeah idk!  :P19:10
timburkeyeah....19:10
claygI mean if it is *the* fix for *that* bug in the backport - the bug is alreayd closed19:10
claygask in #openstack-dev?19:10
claygthere's probably different processes that would work - not sure if there's good reasons to do one thing over something else19:11
timburkeno no, it's fine to put closes-bug in a backport -- that's to mark the bug as closed in that branch. but it seems like https://review.openstack.org/#/c/433565/ already claims to close the bug for newton?19:12
patchbotpatch 433565 - swift (stable/newton) - Fix race in new partitions detecting new/invalid s... (MERGED)19:12
timburkeso do we need all three patches to properly close the bug? or is the situation already better? is there some other bug that would better describe what these new backorts fix?19:13
claygGD, I can't keep all of them straight - it's possible some of the fixes we landed to master didn't get proper bug reports because we were under water trying to get it all fixed - so the book keeping at this point could be jacked - or maybe it just needs someone to do a table19:14
clayg<change on master> <bug> <backport> - and double check the p's and q's19:15
claygPavelK: you wouldn't happen to already have such a spreadsheet do you?19:15
PavelKtimburke: I do not recommend to delete any hashes.pkl manually before these two patches are in your production...19:17
timburkeduly noted :-)19:17
PavelKclayg: I'm not sure to understant your question. but I have a list of fixes that must be merged in production. that's reason why I would like to have these merged in next newton release19:22
*** newmember has joined #openstack-swift19:23
*** newmember has quit IRC19:27
*** newmember has joined #openstack-swift19:28
claygPavelK: i'm not even sure I can *remember* the mess that lead to this one https://gist.github.com/clayg/33f057fb1d9a9d5cc2fd84812e06a9fd - but I would say removing hashes.pkl in production is *fun*!19:28
PavelKclayg: off topic question: do you have unxpected data and ts files replication in your cluster? Unexpected means repeated data rsync and pushing .ts older than reclaim age?19:30
claygpushing .ts older than reclaim age... what's your configured reclaim age?19:31
claygbefore mahatic fixed that one thing I would have some clusters with inactive suffixes that could keep a .ts around after a reclaim because no one noticed it?19:32
claygbut I'm not aware of any rsync "noise" for old .ts getting shipped around except maybe ... from a old-primary?19:32
claygI'll keep an eye out for it19:33
PavelKclayg: There was an idea to delete hashes.pkl from some members when lp bug #1651530 was found...19:33
openstackLaunchpad bug 1651530 in OpenStack Object Storage (swift) "suffix hash invalidation may be lost" [Critical,Fix released] https://launchpad.net/bugs/165153019:33
*** newmember has quit IRC19:34
*** newmember has joined #openstack-swift19:35
PavelKclayg: I don't want to describe reason from you... I just want to know if you did notice it or not.19:35
PavelKI would like to know whether it is common problem or we just have a broken drive19:36
*** jerrygb has joined #openstack-swift19:36
claygare we talking about two different things 1) fallout from the suffix hashing bug (non trivial, we had rolled invalidations file to most deployments by the time you found it and the more we looked and did manual cleanups - the more we were glad it was fixed!)  2) something about rsyncing tombstones with timestamps older than recliam (which to my expereince and understanding so far if it's happening19:38
claygis unrelated to #1)19:39
PavelKtimburke: summary - the patch is in master and I think that it is not neccessary to find a bug for a commit message. A performance regression and a low likely race condition is described in patches and you can find it not neccessary. We will have it in prod. and I think that it will help others to.19:42
*** cebruns has quit IRC19:46
PavelKclayg: yes, tombstones few weeks old, few months and few years were replicated before existing patches were applied. The #2 think is not related with them.19:47
PavelKclayg: I'm happy that you don't have more problems with replicator and hope that we will not need a new patch :-)19:48
*** cebruns has joined #openstack-swift19:48
PavelKI have to leave, have a noce day :-)19:56
* notmyname back online19:58
*** PavelK has quit IRC20:03
*** spotz is now known as spotz_zzz20:15
*** spotz_zzz is now known as spotz20:17
*** Sukhdev has quit IRC20:28
*** stephen_m has quit IRC20:55
*** tonanhngo has joined #openstack-swift20:55
*** tonanhngo has quit IRC20:59
mattoliverauMorning21:04
notmynamehello mattoliverau21:06
onovynotmyname: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860638 :]21:16
openstackDebian bug 860638 in src:swift "swift: FTBFS on i386: Test failures" [Serious,Open]21:16
notmynameonovy: yeah, I saw that. your patch to swift's test will resolve that right?21:17
onovyyep21:17
onovyhttps://review.openstack.org/#/c/458653/ // preparing fixed package21:17
notmynamegreat21:17
patchbotpatch 458653 - deb-swift (debian/newton) - d/patches/FTBFS_i386.patch: Fixies FTBFS on i386 (...21:17
notmynameseems like your patch is ok. a nice follow-up would be to mock out the architecture and catch that we are doing the right thing on both ia64 and other platforms21:18
notmynameie a new test21:18
onovysounds good21:20
openstackgerritPete Zaitcev proposed openstack/swift master: PUT+POST and its development test  https://review.openstack.org/42791121:30
*** _JZ_ has quit IRC21:31
zaitcevokay, this should address Sam's critique at PTG21:31
zaitcevin time for Boston :-)21:31
zaitcevalthough I'm not coming21:31
notmyname"Swift’s object storage showed greater demand in this survey, with 16% of users provisioning more than 1 petabyte of storage, compared to just 4% reporting that amount provisioned one year ago.21:33
notmynameLast year, nearly half of users required more than 10 terabytes of Swift object storage. This year, nearly two-thirds of users require that amount."21:33
notmynamefrom https://www.openstack.org/assets/survey/April2017SurveyReport.pdf21:33
zaitcevHrm. Hopefuly it's not just a petabyte of useless VM snapshots21:34
notmynameI'm not here to judge your bytes. just to make sure they are stored safely :-)21:34
*** Renich___ is now known as Renich21:34
*** catintheroof has quit IRC21:34
zaitcevswift upload imas '[Leopard-Raws] Idolmaster Cinderella Girls Gekijou - 01 RAW (BS11 1280x720 x264 AAC).mp4'21:36
onovyfor us it's petabyte of useless video and image21:38
onovybetter than VM snapshosts?21:39
notmynameit's just a zero or one. (or 2**50 of them)21:41
pdardeau_5 years from now someone might look back and say this was the genesis of carbon credits by container (or storage policy)21:45
claygnotmyname: onovy: one time I think I wrote a diff to fix those damn tests - my comment on patch set 3 - https://review.openstack.org/#/c/423783/21:45
patchbotpatch 423783 - swift - IO Priority support on the AArch64 architecture (MERGED)21:45
claygthe point is the bytes are useless - eat arbys21:46
onovyclayg: right21:48
onovyworking too21:48
onovybtw: we really want Swift to work on ARM21:49
onovybecause we are building our hardware for storage21:49
notmynameonovy: that's really cool21:51
onovythanks for fixing endianity of ring :)21:51
onovybut to be honest, we are just experimenting with it now. we have standard amd64 servers today21:52
clarkbI know the linaro folks had openstack in general running on arm21:55
clarkbthey may have useful infos21:55
onovyyep, guys which are working on this project knows it21:56
onovybut thanks :)21:56
zaitcevi'd love to see an ARM server board with a real I/O. Everyone I found thus far always hooks SATA off a USB-to-SATA adapter, and it's awfully slow.21:58
onovyaa, we will be better :)21:59
onovyno USB-to-SATA adapter21:59
onovybut SATA SSD disk21:59
clarkbzaitcev: system76 starling pro is a neat looking arm system. But seems more compute density focused. But appears to have proper IO too22:00
clarkbpcie even22:00
*** Sukhdev has joined #openstack-swift22:06
*** tonanhngo has joined #openstack-swift22:08
*** tonanhngo has quit IRC22:10
*** klamath has quit IRC22:10
mattoliverauBtw sorry if I'm a bit distracted this week, will be trying to get back to some community stuff today.22:17
mattoliverauWhile I still have an army of cloud saio's22:17
notmynamedefinitely understandable22:17
notmynamemattoliverau: assuming swift-related job offers don't come raining down next week, one of the most helpful things you can do is make sure all your data/code/ideas are written down someplace we can read them22:19
mattoliverauYeah will do, I'll make sure the sharding Trello is updated, and wrangle the sharding patches into shape22:20
mattoliverauAs well ^22:21
*** jamielennox is now known as jamielennox|away22:25
timburkemattoliverau: fwiw, i'ma try to come back around to that early next week, take on the heart of it in container/sharder22:26
*** jamielennox|away is now known as jamielennox22:29
mattoliverautimburke: next week will be my last week at Rackspace, so how about we use that time to make sure you up to speed. Tho I'm not going to just disappear, unless the I get a job that doesn't let me work on Swift. But I'd make sure it isn't sudden.22:34
timburkemattoliverau: sounds like a plan22:36
*** peluse has joined #openstack-swift22:46
pelusewhat up people!?22:46
notmynamepeluse: !!!!!22:47
peluseI'm a little amazed my IRC client still works :)22:47
notmyname:-)22:47
notmynamepeluse: you're here to tell us you're back, right? ;-)22:47
peluseLOL, I wish!  I miss the Swift community for sure! I was seriously just checking to see if this thing stil worked and wanted to say Hi to all you guys22:48
pelusenotmyname: did U see my email yet? No hurry but maybe by Mon whatever you got would be great!22:49
notmynamepeluse: yes I did22:49
peluserock n roll22:49
notmynamepeluse: actually, interesting timing. I'll be working on something new for the boston summit22:49
notmynamebut likely won't be done by monday22:50
pelusewhere's everyone else?  off drinking maybe?22:50
pelusenotmyname: ahh, OK. I'll take anything in anyform.  Just informal use for my internal team here, that's all22:50
claygpeluse: good to hear from you my friend :)22:50
peluseI'm having the discussion Tue afternoon22:50
peluseclayg!!!22:50
notmynameactually, it's been a little more quiet lately22:50
notmynamegood to have a monday deadline. i'll get a response by then22:51
peluseexcellent...22:51
peluseclayg: they keeping *you* busy I hope :)22:51
claygi just sorta piddle with this and that - you know me22:51
peluserock n roll22:51
peluseallrighty... tell the rest of the gang I said "what up?" and next time I'm in the bay area I'll swing by for sure!!22:52
clayghave you invented any new technologies at Intel that are going to revolutionalize storage ... or are you taking this week off?22:52
notmynamelol22:52
claygpeluse: you're always welcome here22:52
peluseclayg: haha!  Yes of course!!  http://spdk.io22:53
claygpeluse: rock n roll ;)22:53
pelusebut I didn't invent any of that... its just what I'm about to start working on.  I took some vacation and sabbatical combined so last Thu was my first day back to work since the new year started if you can believe it!!22:53
openstackgerritTim Burke proposed openstack/swift master: Add support to increase object ring partition power  https://review.openstack.org/33729722:53
notmynamenice22:53
pelusein fact, its getting to be quitting time here soon.  time to crack a cold one :)22:54
openstackgerritTim Burke proposed openstack/swift master: Improve test_get_valid_utf8_str coverage  https://review.openstack.org/45777622:55
claygpeluse: I'll send you a cheers when I get off today!  thanks for stopping by22:55
peluseclayg: sound about right... take care man!22:56
*** peluse has quit IRC23:01
*** vinsh has quit IRC23:07
*** Sukhdev has quit IRC23:08
mattoliverauSigh, I step away, and when I get back I miss peluse :(23:15
claygawwww23:26
*** kei_yama has joined #openstack-swift23:33
mattoliverausounds like we need to find a way to integrate SPDK and then we may get peluse back ;)23:35
jrichlizaitcev: sorry you wont be at Boston (I wont either actually), and mattoliverau: sorry again to hear about the job, and peluse: sorry I missed you!23:36
pdardeau_mattoliverau: the new version of SPDK does open up some possibilities. there's now a blobstore api and even a lightweight filesystem (non-posix)23:38
*** jerrygb has quit IRC23:45
zaitcevI keep all my patches in depths of Jenkins just in case, although the amount and complexity are notwhere near container sharding, of course.23:55

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