Friday, 2016-11-18

*** NKleppan has quit IRC00:02
*** kei_yama has quit IRC00:02
*** kei_yama has joined #openstack-swift00:03
*** catintheroof has joined #openstack-swift00:11
*** klamath has quit IRC00:14
*** siva_krish has joined #openstack-swift00:49
*** gyee has quit IRC00:53
*** catintheroof has quit IRC00:54
*** chlong has quit IRC01:11
kota_good morning01:38
*** zhugaoxiao has quit IRC01:47
*** siva_krish has quit IRC01:54
openstackgerritMerged openstack/swift: SLO: Concurrently HEAD segments  https://review.openstack.org/39168201:58
mattoliveraukota_: morning02:05
*** takashi_ has joined #openstack-swift02:12
*** dmorita has quit IRC02:28
*** dmorita has joined #openstack-swift02:48
*** dmorita has quit IRC02:53
notmynamekota_: thanks for the changelog review. I'm updating it now03:03
kota_notmyname: sure, sorry I'm in later timezone than you :-)03:04
notmynamekota_: I'm the late one! you're in teh early timezone :-)03:04
kota_hehe03:05
*** tqtran has quit IRC03:07
notmynameFWIW, if you have 2.11.0, save EC data, then roll back to 2.10.0, you cannot access the new data any more (404) because of the different filename03:09
notmynamebut auditing doesn't remove it03:10
notmynamehowever, I'd expect that losing a drive while you're in a rollback state could degrade durability03:10
notmynameI'll make a note to not roll back. good catch, kota_03:10
kota_notmyname: thanks for making sure the behavior so quickly.03:11
kota_that's while I was lunching03:12
notmynamekota_: so the pyeclib question is about landing the warning patch, tagging it, then bumping it in swift, then releasing swift?03:13
kota_notmyname: correct, if you want. but i think it's ok we handle it independently03:13
kota_notmyname: because, current requirements.txt is pyeclib>=1.3.1 so anytime we can find the log warning change when we bump the pyeclib version03:14
kota_for clean deployment though.03:15
notmynameright03:15
notmynameI'd say let's do it, but that would mean also waiting on the global-requirements update before we can land a change to our repo's requirements.txt03:15
kota_yeah, that's what I minded03:15
kota_so i don't have strong opinion to jugde which 1.doing that or 2.release swift and bump pyeclib later for now.03:17
notmynameif we release swift now, then bump pyeclib, do you think we should do another swift release then, too?03:17
notmynameeg 2.11.1?03:17
kota_hmm... i'm not sure we need warning log line so strongly03:19
kota_the warning log line is a mitigation and temtative solution until packagers making liberasurecode >=1.3.103:19
notmynamereally? I kinda feel like we should bump the requirements in swift asap and get that out to people03:19
kota_hmm03:20
notmynameok, if we wait to do a swift release, we're in the exact same situation as no swift release: people can still deploy a bad combination03:20
kota_notmyname: that's too bad03:20
notmynameif we release swift now and later do a dep bump, then they get new good stuff now and can a bad combination03:20
notmynameI think releasing now with what we have, then doing a dependency bump is best03:21
kota_ok, sounds great.03:21
notmynameand if we get it soon, then great. if not, that's too bad, but still better than just not releasing at all03:21
kota_kk03:22
kota_make sense03:23
kota_notmyname: anything else i can help you for the release?03:23
notmynamethanks. I was just wondering about one thing related to the .durables change03:24
notmynameif we can't downgrade after writing data, how do rolling proxy upgrades work? there will be a situation where some proxies will have 2.10 and some will have 2.11.03:25
notmynameprobably a good question for acoles_03:25
kota_i think the impl for non-.durable in the diskfile layer so the older proxy still can get conversation with the newer object servers which doesn't have .durable files.03:26
notmynameoh, right. it's all on the object layer. so that will be fine03:27
kota_IIRC03:27
notmynameyeah, that makes sense. my mistake03:27
kota_:-)03:29
notmynamekota_: I'm about to push a new version of the changelog. looking at it will help with the release. thanks :-)03:30
notmyname*about == after I get my kids in bed, so more like 30 min from now03:31
kota_notmyname: ok. enjoy with your kids ;-)03:31
*** sanchitmalhotra has joined #openstack-swift03:32
notmynameno fussing, we're good :-)03:44
notmynamemy kids do a lot of crazy things. but one thing they've always done well is bedtime03:44
kota_:-)03:49
openstackgerritJohn Dickinson proposed openstack/swift: 2.11.0 release notes  https://review.openstack.org/39921503:49
notmynamethre03:49
notmynameand this time I remembered the reno notes at the same time ;-)03:50
kota_nice03:50
*** dmorita has joined #openstack-swift03:50
*** klrmn has quit IRC03:54
*** dmorita has quit IRC03:55
*** psachin has joined #openstack-swift04:07
notmynamekota_: thanks. I'll land it and prep the -release repo patch for permission to release04:23
kota_notmyname: sounds good, thanks04:24
*** takashi has joined #openstack-swift04:51
*** takashi_ has quit IRC04:52
*** dmorita has joined #openstack-swift04:52
*** dmorita has quit IRC04:57
*** ppai has joined #openstack-swift05:37
openstackgerritMerged openstack/swift: 2.11.0 release notes  https://review.openstack.org/39921505:56
*** gabor_antal has quit IRC05:59
*** gabor_antal has joined #openstack-swift05:59
*** AbyssOne has quit IRC06:08
*** AbyssOne has joined #openstack-swift06:10
*** zaitcev has quit IRC06:16
*** mgagne has quit IRC06:18
*** sams-gleb has joined #openstack-swift06:18
*** timburke has quit IRC06:20
*** mgagne has joined #openstack-swift06:21
*** mgagne is now known as Guest5228506:21
*** timburke has joined #openstack-swift06:23
*** ChanServ sets mode: +v timburke06:23
*** dmorita has joined #openstack-swift06:25
notmynameFYI https://review.openstack.org/#/c/399387/06:30
patchbotpatch 399387 - releases - swift 2.11.0 release06:30
*** dmorita has quit IRC06:30
*** sams-gleb has quit IRC06:32
*** jamielennox is now known as jamielennox|away06:36
*** sanchitmalhotra has quit IRC06:58
*** ChubYann has quit IRC07:04
*** tesseract has joined #openstack-swift07:18
*** tesseract is now known as Guest9031307:18
*** klrmn has joined #openstack-swift07:26
openstackgerrithoward lee proposed openstack/python-swiftclient: Replace 'assertEqual(None, ...)' with 'assertIsNone(...)'  https://review.openstack.org/39941007:28
*** dmorita has joined #openstack-swift07:38
*** hseipp has joined #openstack-swift07:40
*** dmorita has quit IRC07:42
*** pcaruana has joined #openstack-swift07:45
*** jamielennox|away is now known as jamielennox08:03
*** openstackgerrit has quit IRC08:03
*** openstackgerrit has joined #openstack-swift08:03
*** amoralej|off is now known as amoralej08:12
*** klrmn has quit IRC08:15
*** hogepodge has quit IRC08:15
*** rledisez has joined #openstack-swift08:16
*** geaaru has joined #openstack-swift08:23
*** ayrus has joined #openstack-swift08:29
*** ayrus is now known as Guest3271608:30
*** lifeless has quit IRC08:45
kota_sorry cschwede, i added to -2 to patch 399237 to hold the state.08:45
patchbothttps://review.openstack.org/#/c/399237/ - swift - Avoid infinite loop while placing parts08:45
kota_cschwede: probably we ware looking at the same patch at the same time.08:46
*** lifeless has joined #openstack-swift08:47
cschwedekota_: ok - what issue did you found?08:49
kota_cscchwede: it may be small thing but i found the test doesn't fail w/o code change08:50
*** dmorita has joined #openstack-swift08:50
kota_cschwede: not sure i'm addressing to the right thing though, not yet looking at deeply08:50
kota_just starting to work08:50
cschwedekota_: the test runs infinitely w/o the code, i tested that - it just hangs08:51
kota_cschwede: oh, really? that means, I'm missing something, my local testing results in all tests passed.08:52
kota_w/o hangs08:52
kota_test_round_off_error (test.unit.common.ring.test_builder.TestRingBuilder) ... ok08:53
kota_hmmm08:53
Guest32716hiii all, i am using my swift cluster from last one month and i performed several upload and delete of object operations08:54
*** dmorita has quit IRC08:54
Guest32716but now i don't have any objects on my swift-cluster still the storage node is 23% filled08:55
Guest32716is swift will occupy the storage after deleting of objects also?08:56
kota_cschwede: ok. not yet reach out the reason why I didn't get failed but exactly the test for the rebalance looks to go infinite loop, https://gist.github.com/bloodeagle40234/e2ce7d55e140fdb88ff72a645cf7bcba09:01
kota_interesting, via nosetests test/unit/common/ring/test_builder.py -> not stuck  -  via python test/unit/common/ring/test_builder.py -> stuck at the test09:09
kota_caused from something like random seed???09:09
*** joeljwright has joined #openstack-swift09:20
*** ChanServ sets mode: +v joeljwright09:20
*** joeljwright1 has joined #openstack-swift09:22
kota_ugh!!! sorry cschwede, aboslutely my mistake found09:23
cschwedekota_: no worries, glad that you checked this!09:23
*** joeljwright1 has quit IRC09:24
kota_cschwede: I attached to the test code but I had mistake I attached also the change...09:24
*** joeljwright has quit IRC09:24
*** joeljwright has joined #openstack-swift09:25
*** ChanServ sets mode: +v joeljwright09:25
kota_and nosetests which refers repo inside catches the change but via python command it refers the installed dir outside of repo09:26
kota_that is the reason why i got 2 different result from the same tests09:27
kota_oops, gerrit seems to go odd state??? it gots +2 verified from jenkins but we don't have +A right now.09:28
kota_can we kick jenkins via adding +A again?09:28
cschwedekota_: yes, seems so - jenkins is restarting09:31
*** derekjhyang has quit IRC09:51
*** irclogger` has joined #openstack-swift09:54
openstackgerritKota Tsuyuzaki proposed openstack/swift: Don't overwrite built-in 'id'  https://review.openstack.org/39948409:54
kota_cschwede: a follow up for patch  39923709:55
patchbothttps://review.openstack.org/#/c/399237/ - swift - Avoid infinite loop while placing parts09:55
*** irclogger` has quit IRC09:55
*** sams-gleb has joined #openstack-swift10:00
*** acoles_ is now known as acoles10:06
*** ChanServ sets mode: +o acoles10:12
*** nikivi has joined #openstack-swift10:23
*** winggundamth has quit IRC10:28
Guest32716acoles are you there10:53
*** dmorita has joined #openstack-swift10:54
acolesGuest32716: hio10:57
Guest32716have you seen my question which i posted at 14:2510:58
*** dmorita has quit IRC10:58
Guest32716acoles: have you seen my question which i posted at 14:2511:00
acoleslooking11:01
acoles08:55 UTC ?11:02
*** McMurlock1 has joined #openstack-swift11:02
acolesGuest32716: swift stores "tomstone" files to record when an object was deleted so there will be some storage consumed even when no objects are in a cluster11:03
Guest32716acoles: it was occupied 100GB in my storage node11:03
acolesthese files should be cleaned up by the object auditor and/or replicator processes, but only after a reclaim_age period of time has passed, which IIRC is one week by default11:04
acolesalso, if you had some drives offline when object were deleted then you may still have some replicas of objects on those drives. That's why the tombstone files are created on deletion, to supersede any stale replicas.11:06
Guest32716acoles: thanks11:06
*** m3m0_ has joined #openstack-swift11:06
Guest32716acoles: i have one more doubt regarding my uploading speed11:06
*** McMurlock1 has quit IRC11:07
acoles...and, if the auditor ever found any corrupt data then it would move bad data file to quarantine directories on object servers which you'd need to clean up manually11:07
Guest32716acoles: i am using swift cluster which has two nodes and those are connected with 10Gbps network and i am seeing 5.1GB file taking 35 secs11:08
Guest32716is there any way to speed up my upload process11:08
m3m0_hello everyone, does anyone know if it is normal for swift to have "occasionally" long delays in the responses?11:09
Guest32716acoles: is there any parameter to 100% utilize all my cpu cores while uploading objects to swift?11:11
*** nikivi has quit IRC11:22
*** kei_yama has quit IRC11:23
onovynotmyname: hi, are you there?11:26
*** caiobrentano_ has joined #openstack-swift11:31
Guest32716acloes: are you there?11:36
*** caiobrentano_ has quit IRC11:38
*** caiobrentano_ has joined #openstack-swift11:39
openstackgerritMerged openstack/swift: Avoid infinite loop while placing parts  https://review.openstack.org/39923711:46
*** dmorita has joined #openstack-swift11:50
openstackgerritMerged openstack/python-swiftclient: Replace 'assertEqual(None, ...)' with 'assertIsNone(...)'  https://review.openstack.org/39941011:53
openstackgerritMerged openstack/swift: Don't overwrite built-in 'id'  https://review.openstack.org/39948411:53
*** dmorita has quit IRC11:55
*** takashi has quit IRC12:03
acolesGuest32716: could be that your 5GB put is disk io bound rather than CPU?12:03
*** asettle has joined #openstack-swift12:17
*** asettle has quit IRC12:18
*** derekjhyang has joined #openstack-swift12:21
*** hogepodge has joined #openstack-swift12:31
acolescschwede: re patch 398631, afaict it fixes a regression that came since Mitaka - prior to Mitaka the response code was 412, then the bug caused 500, the patch takes us back to 412. I'm inclined to merge this and if there is a proposal to change 412 to 400 then consider it separately. Are you ok with that?12:34
patchbothttps://review.openstack.org/#/c/398631/ - swift - Correctly send 412 Precondition Failed in copy mid...12:35
cschwedeacoles: ah ok, yes, makes sense, let’s merge this12:37
acolescschwede: ok, I'll add a not ein gerrit and +A12:37
acolesnote*12:37
cschwedeacoles: just did that :)12:37
acolescschwede: thanks!12:38
*** Guest32716 has quit IRC12:44
*** Jeffrey4l has quit IRC12:47
*** dmorita has joined #openstack-swift13:03
*** Jeffrey4l has joined #openstack-swift13:07
*** dmorita has quit IRC13:07
*** tqtran has joined #openstack-swift13:08
*** tqtran has quit IRC13:12
openstackgerritMerged openstack/swift: Correctly send 412 Precondition Failed in copy middleware  https://review.openstack.org/39863113:14
*** ppai has quit IRC13:15
*** asettle has joined #openstack-swift13:24
*** silor has joined #openstack-swift13:25
*** asettle has quit IRC13:28
*** silor has quit IRC13:32
*** silor1 has joined #openstack-swift13:32
*** silor1 is now known as silor13:35
*** amoralej is now known as amoralej|lunch13:42
*** dmellado is now known as dmellado|lunch13:50
*** jaakkos has quit IRC14:10
*** dmellado|lunch is now known as dmellado14:12
*** daemontool has joined #openstack-swift14:13
*** siva_krish has joined #openstack-swift14:20
*** daemontool has quit IRC14:21
*** daemontool has joined #openstack-swift14:21
*** dmorita has joined #openstack-swift14:29
*** derekjhyang has quit IRC14:31
*** dmorita has quit IRC14:34
*** amoralej|lunch is now known as amoralej14:42
*** tqtran has joined #openstack-swift14:42
*** siva_krish has quit IRC14:43
*** chlong has joined #openstack-swift14:52
*** asettle has joined #openstack-swift14:54
*** klamath has joined #openstack-swift14:55
*** asettle has quit IRC14:58
notmynameonovy: hello15:00
*** klamath has quit IRC15:05
*** klamath has joined #openstack-swift15:05
*** sams-gleb has quit IRC15:06
notmynamestory on swift http://superuser.openstack.org/articles/globo-openstack-swift/15:06
*** sams-gleb has joined #openstack-swift15:06
tdasilvalol, love the neymar stats, it has everything to do with the article15:08
acolesnotmyname: is that the story that was in the magazine in Barcelona?15:08
notmynameyep15:08
acolesnice15:08
notmynamejust published online today15:08
acolesnotmyname: linkedin pointed me to a nice interview you had done on newton features15:09
notmynamethe one by carol sliwa?15:09
notmynametechtarget?15:09
acolesyes.15:09
notmynameyeah, I liked how that turned out15:09
*** klrmn has joined #openstack-swift15:10
acolesthe email subject line was like "John Dickinson in the news" and my first thought was "OMG what's happened" :D15:10
notmynamelol15:10
*** sams-gleb has quit IRC15:11
openstackgerritAlistair Coles proposed openstack/swift: Make direct_client not override User-Agent  https://review.openstack.org/39963415:11
*** klrmn has quit IRC15:11
tdasilvahahaha15:11
*** deanman has joined #openstack-swift15:14
deanmanHello, I'm using swift CLI v3.0 to communicate with a OS Mitaka release but i get a authorization failure error. I've sourced the OS RC file and I'm able to use the openstack command. Is swift reusing these env. variables or do i have to pass them as arguements?15:16
tdasilvajrichli: good morning! Just saw your comment on patch 399275 and it was exactly what I was expecting. I think the challenging part with breaking down tests.py is trying to figure out what to do with TestCases that test two middlewares?15:18
patchbothttps://review.openstack.org/#/c/399275/ - swift - breaking down tests.py into smaller pieces15:18
tdasilvae.g., in the case of TestSloWithVersioning should it go with test_versioned_writes or a future test_slo file? or yet maybe a third file?15:18
tdasilvaI will also ask this same question on the patch, but wanted to bring it here first so that others could also weigh in15:19
notmynameso deanman had asked that question in #openstack, and I told him he should ask in here because I was about to step away. I'm hoping someone could help out15:20
notmynameFWIW, in the last few days swift's use of md5 in the ring and for etag has been raised as a potential blocker for deployers (to meet with checkbox compliance). seems that we're likely going to be asked about it again and to consider changing it15:22
tdasilvadeanman: swift client will use certain env. variables if they are set, i believe they are OS_USERNAME, OS_TENANT_NAME, OS_AUTH_URL15:22
*** siva_krish has joined #openstack-swift15:23
tdasilvaoh, and OS_PASSWORD15:23
joeljwrighttdasilva: you beat me be 0.5s15:23
joeljwrights/be/by15:23
tdasilvadeanman: oh, but if you really have more questions about the swift client joeljwright is the man to ask!!! ;)15:24
joeljwrightdeanman: happy to help if I can15:25
acolesjoeljwright needs a faster internet connection ;)15:26
tdasilvahehe15:26
*** sams-gleb has joined #openstack-swift15:26
deanmanThank you, i have sousourced the RC file so I assume that they are used. Nevertheless i get this auth error.15:26
deanmanI've even tried passing them as arguements, but i got the same response.15:27
acolesdeanman: fwiw swiftclient also picks up OS_IDENTITY_API_VERSION15:27
deanmanswift --auth $OS_AUTH_URL --os-username $OS_USERNAME --os-password $OS_PASSWORD stat --debug15:27
deanmanacoles: That arguement is not exported in my RC file15:28
deanmanis that something that an OS administrator should have setup up so that tenants that download RC files get them included?15:30
acolesassuming you are using keystone auth then you need --os-project-name (or have it in env)15:30
joeljwrightdeanman: are you using keystonev3?15:30
deanmanjoeljwright: I've sourced V2 RC file but i've also download V3.15:31
acolesand maybe joeljwright remembers but i think --os-identity-api-version=3 ? or 2.0 ?15:31
deanmanAre you suggesting to try out v3 ?15:31
joeljwrightdeanman: the collection of auth env variables you need depends on the auth system you're using15:32
joeljwrightI'm assuming you're using keystone auth15:33
deanmanjoeljwright: pardon my OS overall ignorance but in the OS i got access is called "Identity"15:34
*** sgundur_ has joined #openstack-swift15:34
*** lcurtis has joined #openstack-swift15:35
acolesclayg: anyone - can you think of any reason why this would break anything or be a bad idea - patch 39963415:35
patchbothttps://review.openstack.org/#/c/399634/ - swift - Make direct_client not override User-Agent15:35
joeljwrightdeanman: could you list the OS_* variables that are set in your environment and the error you receive when you try to use the swift client?15:36
joeljwrightyou need to have OS_AUTH_URL, OS_USERNAME, OS_PROJECT_NAME and OS_PASSWORD set (or passed as arguments)15:38
*** asettle has joined #openstack-swift15:41
*** sgundur_ has quit IRC15:44
*** pcaruana has quit IRC15:50
jrichlitdasilva: yes, the tests with combinations of features are hard to place.  I have commented on the patch.15:52
*** tqtran has quit IRC15:55
tdasilvajrichli: ack15:55
*** sgundur_ has joined #openstack-swift15:55
*** admin6_ has quit IRC15:55
*** sgundur_ has quit IRC15:59
deanmanjoeljwright: http://paste.ubuntu.com/23495954/16:01
deanmanjoeljwright: it seems like that the --os-identity-api-version made the difference and returned correctly16:01
*** sams-gleb has quit IRC16:01
*** sams-gleb has joined #openstack-swift16:02
joeljwrightthat's interesting, because if you have OS_PROJECT_NAME set it should default to v316:03
joeljwrightI'm glad it's working for you now though16:03
joeljwrightdeanman: does `swift --os-identity-api-version 3` work?16:04
deanmanjoeljwright: http://paste.ubuntu.com/23495979/16:05
*** daemontool has quit IRC16:05
joeljwrightdeanman: thanks for the feedback - it seems that the logic to choose the identity version isn't working quite right16:06
deanmanjoeljwright: http://paste.ubuntu.com/23495988/16:06
*** sams-gleb has quit IRC16:06
joeljwrightdeanman: Ah! I see why16:07
*** sams-gleb has joined #openstack-swift16:07
joeljwrightthe default to v3 when we see PROJECT/DOMAIN was added in 3.1.016:08
joeljwrightif you upgrade to 3.1.0 you should be able to just call `swift list` with those variables set in your env16:09
*** Guest90313 has quit IRC16:09
acolesjoeljwright: ah! I was about to say shouldn't the presence of a domain arg force v316:11
*** sams-gleb has quit IRC16:13
*** sams-gleb has joined #openstack-swift16:14
rlediseznotmyname: do you know if there is a time limit to register for the PTG? I can't find any informations about that on the website or eventbrite16:15
deanmanjoeljwright: well it seems that is not available on my distro (Ubuntu xenial) but i'll find how i can download latest. In the meantime what's the name of the equivalent OS_* var name for api i should set on my RC ?16:16
*** sams-gleb has quit IRC16:17
*** sams-gle_ has joined #openstack-swift16:17
*** sams-gle_ has quit IRC16:19
*** sams-gleb has joined #openstack-swift16:19
joeljwrightdeanman: I believe it's ST_AUTH_VERSION16:22
joeljwrightlet me have a quick check16:23
notmynamerledisez: no I don't know about any deadline for PTG registration. there might be a limit on tickets though. I don't know.16:23
notmynamerledisez: I will find out16:24
*** sams-gleb has quit IRC16:24
rlediseznotmyname: AFAIK, yes, there is limit on number of tickets: 50016:25
notmynameswift release done! https://review.openstack.org/#/c/399387/16:25
patchbotpatch 399387 - releases - swift 2.11.0 release (MERGED)16:25
joeljwrightdeanman: if you set ST_AUTH_VERSION=3 you should be able to run without setting the auth version as an option16:25
bkeller`it says there's 366 tickets left for the PTG16:26
notmynamerledisez: yeah, that's what I was just told. 500 cap, not close to that now, but will move to a waiting list mode if necessary16:27
deanmanjoeljwright: got it, cheers!16:29
*** SkyRocknRoll has joined #openstack-swift16:29
rledisezok, thx for the info (i just saw where to find the number of remaining tickets :))16:29
notmynamerledisez: from what I can tell, let me know if you'll be registering late, but even if you do, I should be able to make sure you have a ticket16:30
rlediseznotmyname: ok, thx for that. i'll try to get approval for travel quickly16:31
*** SkyRocknRoll has quit IRC16:32
notmynamehttps://twitter.com/notmyname/status/799651922059792384 for those that tweet16:34
*** sgundur_ has joined #openstack-swift16:34
*** psachin has quit IRC16:37
*** klrmn has joined #openstack-swift16:43
*** hseipp has quit IRC16:44
*** klrmn has quit IRC16:44
*** SkyRocknRoll has joined #openstack-swift16:46
*** abalfour has quit IRC16:48
pdardeaunotmyname: regarding md5, the osic security team recently did a first-pass audit of a number of openstack projects, and use of md5 was their only ding on swift16:48
*** abalfour has joined #openstack-swift16:49
hurricanerixpdardeau are you talking about the etag?16:49
*** hseipp has joined #openstack-swift16:50
pdardeauhurricanerix: my impression was that it was just out of principle (anywhere in the project)16:50
*** cbartz has left #openstack-swift16:51
*** tqtran has joined #openstack-swift16:52
hurricanerixWell, as far as I know, md5 is much faster than better "cryptographically strong" hashing algorithms.  So it depends on if what you are using it for.  If the thing doesn't need to be cryptographically strong (because it is not a security feature), then md5 is fine.  (and as far as I know, the etag is not meant to be a security feature).  Having said that, I think maybe people were working on a way where there16:53
hurricanerix could be alternate hashes used.  clayg might know more about that maybe though...16:53
pdardeauhurricanerix: went digging through emails to find the specifics "... identified a few possible issues like usage of md5 hashes. ... As a norm, the security team recommends against usage of insecure hash functions."16:54
hurricanerixI think etag is just meant to be a easy way for a client to tell if something changed.  and it isn't even defined as "md5", just something that should be unique. (I think)16:55
hurricanerixWe just happen to use a md5 for it.16:55
pdardeaui believe the mentioned security scan just did an automated scan through the source repos.16:56
hurricanerixBut I would argue that a insecure hashing function is fine in the context of something that is not sensitive from a security standpoint.16:56
hurricanerixAhh16:56
*** tqtran has quit IRC16:56
pdardeauor even crc in some cases16:57
*** siva_krish has left #openstack-swift16:58
*** sgundur_ has quit IRC17:00
*** rickflare has quit IRC17:07
hurricanerixpdardeau Yeah, I just re-read over the purpose of the Etag, and I don't see any reason using an md5 for it would be a problem. https://tools.ietf.org/html/rfc7232#section-2.317:07
redboIf they're smart, they're complaining about how we use md5 to pick the partition, not about etags.17:11
*** klrmn has joined #openstack-swift17:12
*** rledisez has quit IRC17:12
redboEven though that's kind of pretend too.  There should probably be a setting on the ring to use a more secure algorithm.17:12
*** hseipp has quit IRC17:22
hurricanerixredbo good point17:22
*** sgundur_ has joined #openstack-swift17:25
*** oshritf has joined #openstack-swift17:27
*** klamath has quit IRC17:31
*** Guest52285 is now known as mgagne17:33
*** mgagne has quit IRC17:33
*** mgagne has joined #openstack-swift17:33
*** SkyRocknRoll has quit IRC17:46
*** dmorita has joined #openstack-swift17:48
*** dmorita has quit IRC17:50
*** dmorita has joined #openstack-swift17:50
*** tqtran has joined #openstack-swift17:53
*** tqtran has quit IRC17:58
*** SkyRocknRoll has joined #openstack-swift17:59
*** asettle has quit IRC18:06
notmynameyeah, it's largely what pdardeau said18:11
timburkekota_: good call on 399484 -- thanks18:12
notmynamepeople have issues if `grep -r md5 /path/to/swift/source` returns anything18:12
*** sams-gleb has joined #openstack-swift18:14
notmynameIIRC torgomatic had a patch at some point where the ring algo what settable18:14
notmynamefrom my reading, BLAKE* hashing looks interesting. fast and secure18:14
timburkejoeljwright: on the env-var version detection, you're thinking of the OS_*_DOMAIN_* options 00 if any of those are set, we'll automatically go v318:16
timburkejust project isn't enough18:18
timburkenotmyname: given https://review.openstack.org/#/c/395237/ as a model, i don't even think it would be very difficult to do...18:21
patchbotpatch 395237 - swift - add byteorder information and logic to ring files18:21
joeljwrighttimburke: I didn't look at the change18:21
onovynotmyname: hi again :) i have question about stable branch18:22
joeljwrighttimburke: because the version was too old anyway18:22
joeljwright:(18:22
notmynametimburke: yeah, chanign the ring hash is likely fairly easy. changing the etag is likely close to impossible (without api version bumps)18:22
notmynameonovy: what's up?18:22
onovyyou are responsible for it review of it, right? or every core, with standard process?18:22
timburkeyup. etag's gonna be a pain to ever change18:23
claygtimburke: what about if we *just* did the `while parts > 0` change and the rounding in parts_wanted be what it may?  I doubt it would effect the final placement?18:23
notmynameonovy: it's slightly different than standard. it's good to have reviews as normal, but I'm the only one on the swift team who can land them (stable maint team can too)18:23
onovynotmyname: because i cherry-picked two patches: https://review.openstack.org/#/c/399531/ + https://review.openstack.org/#/c/399533/18:23
patchbotpatch 399531 - swift (stable/newton) - Set owner of drive-audit recon cache to swift user18:23
patchbotpatch 399533 - swift (stable/newton) - Fix signal handling for daemons with InternalClient18:23
timburkeclayg: did ya try it? 'cause that's where i started, too, and then it failed verification18:23
claygoh interesting - yeah I'll need to try it18:24
onovynewton version is somehow special for be, because it will land stretch stable. i want to have it bug free as much as possible18:24
onovy*for me18:24
*** hseipp has joined #openstack-swift18:24
notmynameonovy: cool. yeah, there's a few things proposed to stable/* that I hope to land today. (I had just cleared that queue yesterday!)18:25
notmynameonovy: and the other thing I'm wanting to do is actually tag something there18:25
openstackgerritMerged openstack/swift: Respect server type for --md5 check in swift-recon  https://review.openstack.org/24072618:25
onovynotmyname: cool. is it possible to do release of stable branch then? i know it's not up to you, but stable maint. But i think you should say: yes, do it :)18:25
onovyah, lol.18:25
*** oshritf has quit IRC18:26
notmynameonovy: yeah, AFAIK it's up to the stable maint team to release it. but also AFAIK, they've never actually done that for swift. so I figure we can do it18:26
onovysounds good18:26
claygtimburke: floats fucking suck18:31
timburkeclayg: yup18:32
*** hseipp has quit IRC18:32
*** SkyRocknRoll has quit IRC18:36
*** joeljwright has quit IRC18:40
*** acoles is now known as acoles_18:46
openstackgerritOndřej Nový proposed openstack/swift: object-replicator cleanup  https://review.openstack.org/39161718:47
openstackgerritShashirekha Gundur proposed openstack/python-swiftclient: modify 'swift <sub_command> —help' display  https://review.openstack.org/39011918:58
*** asettle has joined #openstack-swift19:08
*** geaaru has quit IRC19:13
*** sgundur_ has quit IRC19:19
openstackgerritTim Burke proposed openstack/swift: Reduce backend requests for SLO If-Match / HEAD requests  https://review.openstack.org/34753819:27
openstackgerritTim Burke proposed openstack/swift: Confirm receipt of SLO PUT with etag  https://review.openstack.org/39090119:28
*** tqtran has joined #openstack-swift19:29
*** zul has quit IRC19:30
notmynameFYI https://review.openstack.org/#/c/394600/ has landed in infra, which means that approximately tomorrow we'll have an XFS TMPDIR for our tests19:34
patchbotpatch 394600 - openstack-infra/project-config - enable an xfs tmpdir for swift tests (MERGED)19:34
*** klamath has joined #openstack-swift19:36
openstackgerritTim Burke proposed openstack/swift: SLO: Make etag and size_bytes fully optional  https://review.openstack.org/39109019:38
*** klamath has quit IRC19:43
*** deanman has quit IRC19:43
openstackgerritTim Burke proposed openstack/python-swiftclient: Accept more types of input for headers/meta  https://review.openstack.org/35947719:47
*** deanman has joined #openstack-swift19:48
*** zul has joined #openstack-swift19:49
openstackgerritTim Burke proposed openstack/python-swiftclient: Allow arbitrary content-types for directory markers  https://review.openstack.org/26068919:50
*** amoralej is now known as amoralej|off19:51
*** silor has quit IRC19:53
openstackgerritTim Burke proposed openstack/python-swiftclient: On auth failure, ignore passed-in tokens and retry  https://review.openstack.org/39975620:01
*** klrmn has quit IRC20:13
*** sgundur_ has joined #openstack-swift20:15
*** klamath has joined #openstack-swift20:19
*** klrmn has joined #openstack-swift20:21
*** sgundur_ has quit IRC20:24
openstackgerritThiago da Silva proposed openstack/swift: breaking down tests.py into smaller pieces  https://review.openstack.org/39927520:24
claygpatches be flying!20:26
timburkeclayg: the concurrent HEAD patch for SLO resulted in a couple merge conflicts for me, which caused me to go on a fix-all-the-conflicts spree20:27
timburkethat last one's new, though!20:27
timburkeer, not tdasilva's; that's a rebase. the auth failure one20:27
*** sgundur_ has joined #openstack-swift20:28
timburkeor maybe not. i should give tdasilva more credit -- i bet he's addressing comments!20:29
tdasilvatimburke: i was addressing jrichli comments, and now I just noticed that acoles_ also left comments - yay!20:30
tdasilvasorry for the noise20:31
*** klamath has quit IRC20:34
*** asettle has quit IRC20:45
timburkeidk, i think if anyone should apologize, it's me. and i'm not gonna!20:47
claygtimburke: that's the spirit!20:47
timburkeprogress!20:47
*** sgundur_ has quit IRC20:49
claygkota_: so to test isa_l_rs_cauchy you also have to add it in pyeclib yeah?  what's the related change for that?20:50
notmynameclayg: https://review.openstack.org/#/c/393276/20:50
patchbotpatch 393276 - pyeclib - ISA-L Cauchy support20:50
claygi just found it :)20:50
notmynameyeah, I had it right at the top of my screen when you asked20:51
claygpretty annoying backend definitions have to be statically updated in two different projects :\20:52
notmynameyes20:52
notmynameI've started thinking google's model of "everything in one repo" isn't too bad ;-)20:52
*** chlong has quit IRC20:53
claygit's just that we're not independently invested in making a great erasure code *library* - we're just making a storage system20:54
claygoh well20:54
notmynameyeah, I actually don't think we should include those in swift (other things though...)20:54
notmynamebut combining pyeclib and liberasurecode might not be terrible20:55
tdasilvaclayg, kota_ I remember on wed we were talking about keeping users from setting up systems with isa_l_rs_vand and m > 420:57
tdasilvai learned that ceph does the same, but they also limit k > 2120:58
tdasilvahttps://github.com/ceph/ceph/blob/master/src/erasure-code/isa/ErasureCodeIsa.cc#L366,L38020:58
tdasilvajust FYI...20:58
notmynameinteresting20:58
notmynameI remember tsg saying that you can't have total more than 3220:58
notmynamebut k less than 22 is new info20:58
*** caiobrentano_ has quit IRC20:59
*** silor has joined #openstack-swift21:03
tdasilvagotta run, have a good weekend everyone21:04
jrichlihave a good weekend, tdasilva!21:04
*** silor1 has joined #openstack-swift21:08
*** silor has quit IRC21:10
*** silor1 is now known as silor21:10
*** mweshi has joined #openstack-swift21:22
*** dmorita has quit IRC21:27
*** dmorita has joined #openstack-swift21:28
*** dmorita has quit IRC21:30
*** dmorita_ has joined #openstack-swift21:30
*** catintheroof has joined #openstack-swift21:31
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925021:33
*** Jeffrey4l has quit IRC21:33
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873621:34
*** sams-gleb has quit IRC21:42
*** sams-gleb has joined #openstack-swift21:42
*** sams-gleb has quit IRC21:43
*** sams-gleb has joined #openstack-swift21:43
*** sams-gleb has quit IRC21:44
*** siva_krish has joined #openstack-swift21:45
*** mweshi has quit IRC21:52
*** silor has quit IRC21:56
notmynametimburke: FYI the errors in the gate like https://review.openstack.org/#/c/391090/ are my fault and will be fixed as soon as https://review.openstack.org/#/c/399765/ takes effect21:57
patchbotpatch 391090 - swift - SLO: Make etag and size_bytes fully optional21:57
patchbotpatch 399765 - openstack-infra/project-config - Fix syntax error for tox-with-tmpdir-passed-in (MERGED)21:57
timburkenotmyname: yeah, i saw that the fix merged, thought that would be enough to resolve the gate. i can wait :-)21:58
*** asettle has joined #openstack-swift22:03
*** mweshi has joined #openstack-swift22:04
*** mweshi has quit IRC22:07
*** vint_bra has quit IRC22:11
*** dmorita_ has quit IRC22:55
*** dmorita has joined #openstack-swift22:55
*** dmorita has quit IRC23:00
*** dmorita has joined #openstack-swift23:04
*** dmorita has quit IRC23:22
*** dmorita has joined #openstack-swift23:23
*** dmorita has quit IRC23:24
*** dmorita has joined #openstack-swift23:24
*** Jeffrey4l has joined #openstack-swift23:31
*** klrmn has quit IRC23:47
*** lcurtis has quit IRC23:50

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