Wednesday, 2016-11-16

openstackgerritMerged openstack/swift: Document X-Openstack-Request-Id in all responses  https://review.openstack.org/39789600:06
*** _JZ_ has quit IRC00:10
*** zul has quit IRC00:13
si1verHello again. I'm still trying to get aws4 auth working with swift 3 in mitaka. I started over with a new test node following http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-install.html, http://docs.openstack.org/mitaka/install-guide-ubuntu/swift-controller-install.html, and http://docs.openstack.org/mitaka/config-reference/object-storage/configure-s3.html. I'm still not able to use aws credentials to access my te00:19
si1verThe instructions above from openstack.org do not mention s3 token, but it is mentioned in the repo readme at https://github.com/openstack/swift3. Is s3token required in addition to swift3?00:21
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873600:22
*** sgundur_ has joined #openstack-swift00:23
si1verI tried adding s3token to my main pipeline and get this error: LookupError: Entry point 's3token' not found in egg 'swift3'. Does that mean that s3token is not included in the ubuntu cloud archive package swift-plugin-s3?00:24
*** kei_yama has quit IRC00:24
openstackgerritJohn Dickinson proposed openstack/swift: Add checksum to object extended attributes  https://review.openstack.org/33632300:27
timburkesi1ver: yes, s3token is required when using swift3 with keystone. this middleware used to be provided as part of keystonemiddleware, but was moved into swift3's tree in the not-so-distant past00:28
timburkeyou might want to look at a slightly older version of the sample configs, like from https://github.com/openstack/swift3/blob/v1.10/etc/proxy-server.conf-sample#L14400:28
si1verOk I removed the swift-plugin-s3 package and ran git clone https://github.com/openstack/swift3.git and the setup script. Truing it now.00:28
timburkeor that :-)00:28
si1verso filter:s3token does not need auth creds in it? The older examples I found had them in there, but https://github.com/openstack/swift3 doesn't show them.00:29
si1verI have the same error now that I did on my previous test node, but I think I've got a better starting place for debugging now. "The request signature we calculated does not match the signature you provided. Check your key and signing method."00:30
timburkesi1ver: nope. i think those were cargo-culted in before. s3token basically takes the client's (slightly massaged & standardized) request, sends it as JSON to keystone, and says "here, you deal with it"00:31
timburkedo we see the keystone request in the proxy logs? or for that matter, the keystone logs00:31
si1verI see this in the proxy log: 'Nov 16 00:30:46 swift3 proxy-server: 10.0.5.94 10.0.5.94 16/Nov/2016/00/30/46 GET /ma-swift%3Fencoding-type%3Durl%26max-keys%3D1 HTTP/1.0 403 - aws-sdk-ruby2/2.6.19%20ruby/2.0.0%20x86_64-darwin14.1.0 - - 277 - tx3e8c4098e9bd454396558-00582ba8b6 - 0.0408 - - 1479256246.784826040 1479256246.825629950 -'00:31
si1verLooking for the keystone log lines for that request now.00:32
si1verma-swift is a container that I created with the normal python swift client as the demo user, which is the same user these ec2 creds were generated by.00:32
si1verkeystone says 'POST http://swift3:35357/v2.0/s3tokens' and 'Authorization failed. The request you have made requires authentication'00:33
si1verSo if I understand correctly, that means that swift itself failed to auth against keystone, so the user creds were never passed along. Does that sound right?00:34
timburkeonly that keystone request shouldn't require auth :-/ i'm not sure why keystone thinks that it does00:35
si1verIs s3tokens a new endpoint that I need to create? That's not mentioned in the docs.00:35
timburkepossibly. i know the func tests ensure the extension is defined in keystone's paste.ini at https://github.com/openstack/swift3/blob/master/swift3/test/functional/conf/keystone-paste.ini#L36-L37 (and enabled in the pipelines around lines 73 & 76)00:38
timburkewe almost certainly could use better docs00:38
si1verWell I'd love to help. :p00:38
si1verswift's been good to me00:38
openstackgerritJohn Dickinson proposed openstack/swift: Add checksum to object extended attributes  https://review.openstack.org/33632300:39
timburkeunfortunately, though, i've gotta run to pick up my daughter00:39
si1verNo sweat.00:39
timburkesi1ver: sorry i couldn't stick around to help more00:39
*** sgundur_ has quit IRC00:43
*** zul has joined #openstack-swift00:43
*** kei_yama has joined #openstack-swift00:58
*** tqtran has quit IRC01:41
*** juzuluag has joined #openstack-swift01:52
*** links has joined #openstack-swift01:55
*** links has quit IRC02:07
*** siva_krish has joined #openstack-swift02:11
*** winggundamth has quit IRC03:02
si1vertimburke: I got it working with s3curl, but I am still having trouble with other clients.03:04
*** winggundamth has joined #openstack-swift03:15
*** juzuluag has quit IRC03:17
si1verHostfiling s3.amazonaws.com to my testing node and proxying 80 to 8080 doesn't do the trick for the signature in the ruby aws client. Must be more to it, like maybe ssl.03:19
*** siva_krish has quit IRC03:19
*** dmorita has quit IRC03:22
*** dmorita has joined #openstack-swift03:23
*** dmorita has quit IRC03:27
*** sanchitmalhotra has quit IRC03:46
*** sanchitmalhotra has joined #openstack-swift03:47
*** psachin has joined #openstack-swift03:54
*** deep_1 has joined #openstack-swift03:59
*** siva_krish has joined #openstack-swift04:01
*** siva_krish has quit IRC04:01
*** Jeffrey4l has joined #openstack-swift04:03
mahaticgood morning04:24
*** SkyRocknRoll has joined #openstack-swift04:39
mattoliveraumahatic: morning04:40
mahaticmattoliverau: o/04:41
openstackgerritMahati Chamarthy proposed openstack/swift: remove empty db hash and suffix directories  https://review.openstack.org/33160104:42
*** klrmn has quit IRC04:59
*** darrenc is now known as darrenc_afk05:19
*** darrenc_afk is now known as darrenc05:57
*** Trixboxer has quit IRC06:09
*** ChubYann has quit IRC06:10
*** ppai has joined #openstack-swift06:22
*** sams-gleb has joined #openstack-swift07:04
*** pcaruana has joined #openstack-swift07:41
*** sams-gleb has quit IRC07:50
*** sams-gleb has joined #openstack-swift07:51
*** sams-gleb has quit IRC07:53
*** sams-gleb has joined #openstack-swift07:53
*** sams-gleb has quit IRC07:57
*** rledisez has joined #openstack-swift08:13
*** amoralej|off is now known as amoralej08:20
*** sams-gleb has joined #openstack-swift08:21
*** geaaru has joined #openstack-swift08:23
*** jordanP has joined #openstack-swift08:23
*** dmorita has joined #openstack-swift08:23
*** dmorita has quit IRC08:27
*** jordanP has quit IRC08:35
*** joeljwright has joined #openstack-swift08:43
*** ChanServ sets mode: +v joeljwright08:43
*** joeljwright1 has joined #openstack-swift08:57
*** kei_yama has quit IRC08:58
*** joeljwright2 has joined #openstack-swift08:59
*** joeljwright has quit IRC08:59
*** joeljwright1 has quit IRC09:02
*** jordanP has joined #openstack-swift09:23
*** joeljwright2 has quit IRC09:34
*** joeljwright has joined #openstack-swift09:34
*** ChanServ sets mode: +v joeljwright09:34
*** deep_1 has quit IRC09:35
*** takashi_ has joined #openstack-swift09:38
*** acoles_ is now known as acoles09:47
*** deep_1 has joined #openstack-swift09:50
*** hseipp has joined #openstack-swift09:56
*** dstepanenko_ is now known as dstepanenko10:13
*** asettle has joined #openstack-swift10:23
*** mvk has quit IRC10:30
*** donagh has joined #openstack-swift10:43
*** SkyRocknRoll has quit IRC10:43
*** sams-gle_ has joined #openstack-swift10:50
*** sams-gleb has quit IRC10:50
*** SkyRocknRoll has joined #openstack-swift10:52
*** mvk has joined #openstack-swift10:54
*** geaaru has quit IRC10:55
*** nikivi has joined #openstack-swift11:02
*** sanchitmalhotra has quit IRC11:06
*** geaaru has joined #openstack-swift11:09
*** nikivi has quit IRC11:23
*** deep_1 has quit IRC11:31
*** tqtran has joined #openstack-swift11:41
*** tqtran has quit IRC11:45
*** geaaru has quit IRC11:56
openstackgerritAlistair Coles proposed openstack/swift: Make tempurl functional tests clean up account keys  https://review.openstack.org/34675212:03
*** geaaru has joined #openstack-swift12:14
*** saltsa has quit IRC12:14
*** thurloat has quit IRC12:15
*** saltsa has joined #openstack-swift12:16
*** thurloat has joined #openstack-swift12:16
*** catintheroof has joined #openstack-swift12:23
*** deep_1 has joined #openstack-swift12:29
*** portante has quit IRC12:38
*** portante has joined #openstack-swift12:40
*** nexusz99 has joined #openstack-swift12:45
*** nexusz99 has quit IRC12:46
*** deep_1 has quit IRC12:46
*** takashi_ has quit IRC13:10
*** asettle__ has joined #openstack-swift13:15
*** asettle has quit IRC13:18
*** ppai has quit IRC13:19
*** _JZ_ has joined #openstack-swift13:22
*** jamielennox is now known as jamielennox|away13:25
*** asettle__ is now known as asettle13:25
*** bkopilov_ is now known as bkopilov13:28
*** siva_krish has joined #openstack-swift13:31
*** ouchkernel has quit IRC13:39
*** SkyRocknRoll has quit IRC13:39
*** ndk_ has quit IRC13:40
*** ndk_ has joined #openstack-swift13:42
*** tqtran has joined #openstack-swift13:42
*** siva_krish has left #openstack-swift13:44
*** tqtran has quit IRC13:47
*** Administrator_ has quit IRC13:51
*** Administrator_ has joined #openstack-swift13:52
*** amoralej is now known as amoralej|lunch13:52
*** ouchkernel has joined #openstack-swift14:05
*** deep_1 has joined #openstack-swift14:11
*** klamath has joined #openstack-swift14:13
*** Administrator_ has quit IRC14:13
*** Administrator_ has joined #openstack-swift14:14
openstackgerritAlistair Coles proposed openstack/swift: Make tempurl functional tests clean up account keys  https://review.openstack.org/34675214:16
*** amoralej|lunch is now known as amoralej14:32
tdasilvagood morning14:36
*** klamath has quit IRC14:40
*** klamath has joined #openstack-swift14:41
*** SkyRocknRoll has joined #openstack-swift14:43
*** tongli has joined #openstack-swift14:44
*** psachin has quit IRC14:51
*** sams-gle_ has quit IRC15:06
*** sams-gleb has joined #openstack-swift15:07
*** sams-gleb has quit IRC15:11
openstackgerritThiago da Silva proposed openstack/swift: Symlink implementation.  https://review.openstack.org/23216215:15
*** dmorita has joined #openstack-swift15:24
*** sams-gleb has joined #openstack-swift15:24
*** dmorita has quit IRC15:28
*** SkyRocknRoll has quit IRC15:34
*** SkyRocknRoll has joined #openstack-swift15:38
*** deep_1 has quit IRC15:43
*** tqtran has joined #openstack-swift15:44
*** tqtran has quit IRC15:48
timburkegood morning15:52
tdasilvatimburke: o/15:57
acolestdasilva: timburke o/16:02
tdasilvaacoles: hi! you asking me about cross-policy testing in symlinks led me to find a bug in the code :)16:03
acolestdasilva: great! I forget what I asked but glad it helped :)16:04
tdasilvaacoles: back in BCN you just asked if the func tests had cross-policy testing :)16:05
acolesright. because one symlinks is to link across policies.16:05
tdasilvaright16:06
openstackgerritThiago da Silva proposed openstack/swift: add policy info to swift-get-nodes  https://review.openstack.org/37271616:08
openstackgerritThiago da Silva proposed openstack/swift: Fix swiftdir option and usage of storage policy aliases  https://review.openstack.org/34469316:08
openstackgerritAlexis Lee proposed openstack/swift: fixup  https://review.openstack.org/39844416:09
jrichlitdasilva, acoles: nice16:12
acolestdasilva: you just helped me realise why my patch is failing in gate. serendipity at work :)16:14
timburkeacoles: i was just about to help out there :-)16:15
acolestdasilva: its failing cross policy versioning tests, which I remembered are skipped in gate16:15
tdasilvaacoles: http://logs.openstack.org/52/346752/6/check/gate-swift-tox-func-in-process-fast-post-ubuntu-xenial/d4f873c/console.html16:16
tdasilvathat?16:16
acolesyep16:16
acolescaused by calling the teardown when setup doesn't complete cos the tests skip16:17
acolesI don't see that OMM where I have multiple policies16:18
tdasilvaoh i see16:18
tdasilvaacoles: I was thinking about a patch to start "breaking down" the tests.py16:18
tdasilvainto smaller files16:18
timburkei love that idea16:18
acolestdasilva: pycharm would thank you, it groans a bit with the larger test files16:19
*** klrmn has joined #openstack-swift16:19
*** oshritf has quit IRC16:19
*** asettle has quit IRC16:20
*** asettle has joined #openstack-swift16:20
tdasilvahehehe16:20
tdasilvaacoles, timburke I thought one nice thing about test_symlink.py is that I was able to put the skip right on the setupModule16:21
tdasilvaskips the whole thing if symlinks is not in the pipeline16:22
*** deep_1 has joined #openstack-swift16:25
tdasilvantata: hi, I got to test your tempest plugin patch :)16:26
tdasilvantata: it worked out well, the downside was that I pretty much needed to setup everything I typically do for running functional tests anyway. Meaning download swift repo, install and setup /etc/swift/tests.conf16:27
tdasilvantata: so the only real change was running tempest instead of .functests16:28
*** caiobrentano_ has joined #openstack-swift16:36
*** siva_krish has joined #openstack-swift16:43
*** abalfour has quit IRC16:46
*** abalfour has joined #openstack-swift16:46
*** jistr is now known as jistr|biab16:48
notmynamegood morning16:50
notmynametimburke: thanks for https://review.openstack.org/#/c/398467/16:51
patchbotpatch 398467 - governance - Acknowledge remove-incubated-oslo-code for Swift16:51
timburkenp16:51
notmynameI had just started looking at where to make a patch, then I saw the email about your patch. yay16:52
openstackgerritAlistair Coles proposed openstack/swift: Make tempurl functional tests clean up account keys  https://review.openstack.org/34675216:53
acolesthis time be happy jenkins16:53
notmynamenice. looks like I finally got enough tests to skip so that https://review.openstack.org/#/c/336323/ passes the gate17:01
patchbotpatch 336323 - swift - Add checksum to object extended attributes17:01
notmynamenow to figure out https://review.openstack.org/#/c/394600/ for the infra side so that tests don't get skipped17:02
patchbotpatch 394600 - openstack-infra/project-config - enable xfs for swift in-process functests17:02
notmynameif anyone knows anything about zuul or CI, any help on that last patch is appreciated.17:02
*** klrmn has quit IRC17:09
*** vint_bra has joined #openstack-swift17:15
*** lxsli is now known as lxsli_away17:30
*** rledisez has quit IRC17:31
*** jistr|biab is now known as jistr17:36
*** sgundur_ has joined #openstack-swift17:39
*** sgundur_ has quit IRC17:45
*** dmorita has joined #openstack-swift17:46
*** david-lyle has quit IRC17:48
*** david-lyle has joined #openstack-swift17:48
*** hseipp has quit IRC17:51
*** SkyRocknRoll has quit IRC17:57
*** mvk has quit IRC17:58
*** cdelatte has joined #openstack-swift18:00
*** deep_1 has quit IRC18:02
*** klrmn has joined #openstack-swift18:02
claygtimburke: wow, nice work -> https://review.openstack.org/#/c/398467/1/goals/ocata/remove-incubated-oslo-code.rst18:04
patchbotpatch 398467 - governance - Acknowledge remove-incubated-oslo-code for Swift18:04
timburkeclayg: it was an awful lot of typing18:05
*** oshritf has joined #openstack-swift18:09
*** diogogmt has joined #openstack-swift18:13
*** catinthe_ has joined #openstack-swift18:13
*** tqtran has joined #openstack-swift18:13
*** catintheroof has quit IRC18:15
*** catintheroof has joined #openstack-swift18:15
*** geaaru has quit IRC18:16
*** oshritf has quit IRC18:16
*** tqtran has quit IRC18:18
*** catinthe_ has quit IRC18:18
openstackgerritAlistair Coles proposed openstack/swift: Add test for object updater user-agent header  https://review.openstack.org/39852318:21
*** caiobren_ has joined #openstack-swift18:25
*** thebloggu has joined #openstack-swift18:25
*** acoles is now known as acoles_18:26
*** caiobrentano_ has quit IRC18:28
*** Administrator_ has quit IRC18:32
*** Administrator_ has joined #openstack-swift18:32
notmynamefungi: do you have an example of a parameterized builder? I don't know how that works18:35
funginotmyname: the "contact" builder at the top of http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/macros.yaml has parameter substitution for {name}, {email} and {irc}18:40
notmynamefungi: ok. how are those passed in? where are they set?18:41
funginotmyname: like this job-template does: http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n190118:41
notmynamefungi: ah, ok. thanks18:43
*** joeljwright has quit IRC18:47
*** jordanP has quit IRC18:48
*** chlong has joined #openstack-swift18:53
*** clu_ has joined #openstack-swift19:04
*** thebloggu has quit IRC19:09
*** amoralej is now known as amoralej|off19:12
*** tqtran has joined #openstack-swift19:14
*** cbartz has quit IRC19:23
*** jamielennox|away is now known as jamielennox19:26
*** ChubYann has joined #openstack-swift19:32
*** hseipp has joined #openstack-swift19:35
*** tongli has quit IRC19:40
*** pcaruana has quit IRC19:51
*** dmorita has quit IRC20:03
*** dmorita has joined #openstack-swift20:04
notmynamefungi: why is there a "gate-{name}-tox-{envlist}-{node}" in python-jobs.yaml and also a "gate-{name}-python27-{node}" template? the only difference is the first calls tox with the envlist and the second calls python27. why isn't the -python27- wrapped into the more generic envlist one?20:11
openstackgerritTim Burke proposed openstack/swift: SLO: Concurrently HEAD segments  https://review.openstack.org/39168220:13
notmynamefungi: follow-up and reason for my question: can I (or why can't I) replace the 'python-jobs' entry for swift fo simply adding py27 to the envlist for the existing "gate-{name}-tox-{envlist}-{node}"?20:14
funginotmyname: gate-{name}-python27 came first and explicitly called tox -e py27, then later people wanted to add a bunch of jobs calling various tox targets and so gate-{name}-tox-{envlist} was born as a means of not having that same boilerplate copied dozens of times. we could move the existing tox-based templates to use that as a cleanup measure, though that will also slightly alter the job names as a20:14
fungiresult20:14
fungiinvestigating the second question/suggestion now20:15
notmynameok20:15
notmynamefungi: ok, there's more than just py27 in the python-jobs group. but it seems like the rest is still tox-based. hmm..maybe not all , though20:23
notmynamebut working through this, I can see some simplification I can make20:25
funginotmyname: sorry, trying to juggle a bunch of discussions in different places at once. yes looking at swift's entry in jenkins/jobs/projects.yaml you could add a gate-{name}-tox-{envlist}-{node} variant which runs the py27 env and then use that instead of or in addition to the normal gate-swift-python27 job in zuul/layout.yaml20:33
notmynamefungi: cool, thanks. I'll be pushing a new patch to project config soon for the xfs stuff. thanks for your help20:34
funginotmyname: though the need to be able to pass a value into the TEMPDIR envvar when invoking tox means you actually need to use a copy of that job-template with a slightly different name, and have it take a parameter for that path20:35
fungibut anyway, we can iterate on the review20:35
notmynameyeah. I think I got it passed around20:35
*** sgundur_ has joined #openstack-swift20:36
funginotmyname: also as an outcome of our cti discussion around this, i've got this amendment going on the tc meeting agenda for next week: https://review.openstack.org/39750220:38
patchbotpatch 397502 - governance - Acknowledge nominal prerequisites for tests20:38
notmynamefungi: ah, interesting. I like that. thanks :-)20:39
*** sgundur_ has quit IRC20:39
fungiyou're welcome. i dislike any appearance of hypocrisy in our policies, so happy to improve20:39
*** sgundur_ has joined #openstack-swift20:40
openstackgerritTim Burke proposed openstack/swift: Add X-Openstack-Request-Id to Access-Control-Expose-Headers  https://review.openstack.org/39798020:40
*** sgundur_ has quit IRC20:47
*** sgundur_ has joined #openstack-swift20:47
*** m_kazuhiro has joined #openstack-swift20:53
ntatatdasilva, yes! all the tempest plugin does is to invoke the tests through it rather than .functtests20:54
ntata:)20:54
mattoliveraumorning20:54
*** acoles_ is now known as acoles20:56
*** rcernin has joined #openstack-swift20:58
*** hseipp has quit IRC20:58
acolesmattoliverau: hi20:58
mattoliverauacoles: hey man20:59
notmynamemeeting time in #openstack-meeting20:59
*** joeljwright has joined #openstack-swift20:59
*** ChanServ sets mode: +v joeljwright20:59
kota_morning20:59
mattoliveraukota_: morning21:00
kota_morning mattoliverau21:01
*** tqtran is now known as tqtran-afk21:01
notmynamefungi: what's the difference between the jobs listed for a project in jenkins/jobs/projects.yaml and the ones listed under zuul/layout.yaml?21:05
funginotmyname: stuff under the "jenkins" subtree is configuration fed into jenkins-job-builder, while stuff under the "zuul" subtree is configuration fed into zuul. different software with different semantics and data model21:09
notmynamefungi:  but it seems that they basically need to mirror each other, right?21:09
fungiso while there is some relationship between them (mostly arbitrarily determined for consistency sake), it's an apples/oranges comparison21:10
funginotmyname: well, the jenkins job configuration defines job payloads, while the zuul configuration tells the scheduler when to run them under what conditions21:10
*** mvk has joined #openstack-swift21:11
fungiso to the extent that jobs need to be defined for zuul to be able to run them (we have a ci job to catch situations where that isn't the case) there is an interrelationship yes21:11
fungithough constructs in jenkins configuration such as job-groups and project-templates for zuul may be similarly named even though they're not entirely analogous structures21:13
fungi(e.g., "jenkins-jobs" is the name of a job-group in the jenkins-job-builder configuration and the name of a project-template in the zuul layout)21:13
fungier, i mean "python-jobs"21:13
fungithey're complimentary, but the similar names for them are merely out of convenience21:14
fungiit's also worth mentioning that this gets far less confusing in zuul v3, as the job playbooks and zuul layout are merged so this confusing distinction will be gone soon21:17
fungiit's mainly an artifact of our old use of jenkins as a job runner21:18
*** m_kazuhiro has quit IRC21:23
*** caiobren_ has quit IRC21:24
*** caiobrentano_ has joined #openstack-swift21:25
*** caiobrentano_ has quit IRC21:29
*** vint_bra has quit IRC21:30
*** catinthe_ has joined #openstack-swift21:32
*** Jeffrey4l has quit IRC21:33
*** cdelatte has quit IRC21:34
*** m_kazuhiro has joined #openstack-swift21:35
*** catintheroof has quit IRC21:36
*** jordanP has joined #openstack-swift21:39
*** sams-gleb has quit IRC21:41
*** sams-gleb has joined #openstack-swift21:42
*** sams-gleb has quit IRC21:42
*** sams-gleb has joined #openstack-swift21:43
*** sams-gleb has quit IRC21:45
*** jordanP has quit IRC21:46
openstackgerritMerged openstack/swift: Remove duplicated 'User-Agent' header from object-updater's requests  https://review.openstack.org/38899921:50
*** sgundur_ has quit IRC21:50
*** catintheroof has joined #openstack-swift21:51
*** catinthe_ has quit IRC21:51
openstackgerritTimur Alperovich proposed openstack/swift: Add the container_crawler library.  https://review.openstack.org/39860021:59
tdasilvatimur: ^^^ cool!21:59
*** sams-gleb has joined #openstack-swift22:01
claygso this warning... are we *also* going to check if you're running isa-l with parity > 422:02
claygkota_: tdasilva: notmyname: ^22:02
kota_clayg: good perspective22:02
jrichlitimur: nice22:02
kota_clayg: probably we can validate both the libec version and # of parities at the init22:03
claygand also... if you *are* using isa_l_rs_vand with parity > 4 - yeah liberasurecode 1.3.1 doesn't have a data durability issue - but the availabilty risk is still there22:03
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873622:03
*** clu_ has quit IRC22:04
kota_clayg: but still we hold it as warn??? i think if we assume it as like a kind of Validation Error, the user already deploys the parameter cannot use it anymore.22:04
*** clu_ has joined #openstack-swift22:04
claygkota_: that's my understanding yes, so the "warning" we eventually add to swift will not really matter the liberasure version22:05
kota_clayg: cannot get the stored data, i mean.22:05
notmynamewarning added to swift? I wouldn't think we'd do any changes there. we could, I guess, on storage policy validation22:05
*** sams-gleb has quit IRC22:05
*** m_kazuhiro has quit IRC22:05
*** sams-gleb has joined #openstack-swift22:05
*** joeljwright has quit IRC22:05
claygnotmyname: oh, the warning was going to be pyeclib?22:06
notmynamethat's what I understood22:06
kota_clayg, notmyname: I've thinking like as notmyname22:06
kota_'ve been22:07
timurI added mattoliverau to it too, but feel free to comment!22:07
notmyname(by which kota_ means that i copied him. it's his good idea) ;-)22:07
timurwould it be helpful to also add the follow-on commit that uses this library to implements the elasticsearch integration?22:07
claygok, well same difference - my point is that we have a combination of ec_type + k + m that is never good22:07
claygwe should try to disallow it really22:08
timburkei think we definitely want a warning in swift on known-problematic storage policy configurations. it'll be sucky noise for policies already in use, but invaluable when you're brining up your POC cluster22:08
timburkemaybe add some yes-i-know-i-screwed-up config option to silence it22:08
claygtimburke: i wouldn't mind requring the policy be marked deprecated22:08
claygtimburke: you can expose a new policy and rename this one legacy some such something w/e22:09
tdasilvaclayg: i'm not sure i understand the problem well, so basically users should never deploy EC with m > 4 with isa-l ???22:09
tdasilvaand there will be no fix to whatever problem exists today?22:10
claygisa_l_rs_vand, yes - kota_ is working on isa_l_rs_vand_cunch and libec 1.3.2 will allow that ec_type to work with m > 422:10
claygtdasilva: we can fix the durability issue but not the availability issue22:10
*** lifeless has quit IRC22:11
claygwe can sorta paper over it with some crazy shit in swift that make your k+m feel like a (k+1)+(m-1) *sometimes* but it's a pretty tenuous affair22:11
claygi would prefer to just deprecate support for such configurations22:11
kota_tdasilva, clayg: i sent the link for the description to tdasilva in private22:11
notmynameclayg: +122:11
tdasilvagot it22:11
claygesp if we have an alternative that works with libec 1.3.2 - which seems likely22:12
notmynamekota_: thanks. I was just about to ;-)22:12
*** lifeless has joined #openstack-swift22:12
tdasilvaclayg: +1 to your idea of deprecation support22:12
claygsorry - is this whole mess still under some advisory?  I'm sorta past all this22:12
notmynameyeah, but I just left a comment about it. https://bugs.launchpad.net/swift/+bug/163969122:13
openstacknotmyname: Error: malone bug 1639691 not found22:13
claygheh22:13
notmynamemalone?22:13
acoles+1 for deprecation. feels like that should happen as close to source of problem as possible - e.g. the lib shouldn't allow a config that is flawed (unless some flag is passed in to force it for backwards comaptibility)22:14
notmynameall the patches have been open. I just want to have a sane story to tell deployers before we give them a single link to say "oh no! it's broken"22:14
zaitcevIt says "The information on this page is private." but I can see it. How private is it?22:15
notmynameswift core can see it22:15
*** sams-gleb has quit IRC22:15
*** sams-gleb has joined #openstack-swift22:15
acolesgood night22:16
*** acoles is now known as acoles_22:16
kota_good night acoles22:16
kota_k, will try to the warning staff today, leave for break fast22:18
claygnotmyname: ok, so we have that - you need to upgrade to liberasurecode 1.3.1 - you need to reput objects in effected policy to repair coruption - you need to deprecate the policy and migrate data to a different policy22:18
claygthe different policy can either be a non isa-l policy; or isa_l_rs_vand m <= 4; or we need to review kota_'s isa_l_rs_vand_cunch and release libec 1.3.222:19
claygit's not a great story but thems the knocks22:20
*** sams-gleb has quit IRC22:20
notmynameright. honestly, I just want that written down in a linkable place and, ideally, also point to a re-putter script22:20
timburkekinda makes you wish https://review.openstack.org/#/c/209329/ was landed...22:20
patchbotpatch 209329 - swift - WIP: Changing Policies22:20
notmynameFYI proposed gate changes to use XFS https://review.openstack.org/#/c/394600/22:21
patchbotpatch 394600 - openstack-infra/project-config - enable an xfs tmpdir for swift tests22:21
claygtimburke: makes you wish it wasn't WIP - that's different from wishing it "was landed" ;)22:21
timburkeok ok, first one then the other :P22:22
claygtimburke: right, sorry22:22
claygnotmyname: well where do you want me to write it down exactly?  shouldn't we just work on isa_l_rs_cauchy?22:23
clayghttps://review.openstack.org/#/c/393263/22:23
patchbotpatch 393263 - liberasurecode - ISA-L Cauchy support22:24
claygfor me it's the next thing on my list after I merge liberasurecode packages and finish testing the reput script (which is basically the same as kota's script but tied into some other tooling we have for professional services)22:24
notmynameclayg: weren't we talking about opening some utils script we have a swiftstack? yeah, that. the reput one22:24
*** dmorita has quit IRC22:28
*** dmorita has joined #openstack-swift22:28
*** dmorita has quit IRC22:28
*** dmorita has joined #openstack-swift22:28
openstackgerritBryan Keller proposed openstack/swift: Send correct response for copy with invalid destination  https://review.openstack.org/39863122:30
claygmaybe - it's not really clear the baggage of that ecosystem in it's current state is a better solution to the problem at hand than the stand alone script kota attached to the bug report22:30
*** sams-gleb has joined #openstack-swift22:31
bkeller`acoles_: @wsgify-ing copy middleware involves changing a decent amount of it so i'll try that later22:32
*** sams-gleb has quit IRC22:35
*** sams-gleb has joined #openstack-swift22:35
*** sams-gleb has quit IRC22:40
abalfourn00b question, but since there's a +2 on https://review.openstack.org/#/c/395237 it's just waiting for a +1 Workflow to get pulled in, correct?22:52
patchbotpatch 395237 - swift - add byteorder information and logic to ring files22:52
*** catintheroof has quit IRC22:54
*** chlong has quit IRC22:59
notmynamehttps://bugs.launchpad.net/swift/+bug/1639691 changed to public, with mitigation info added in the last comment. this should give us a single place to point people to related to libec+isa-l with more than 4 parity23:02
openstackLaunchpad bug 1639691 in OpenStack Object Storage (swift) "EC: Swift can return corrupted Data and be able to go data lost at isa_l_rs_vand policy with >=5 parities" [Critical,Confirmed]23:02
claygnotmyname: yay!23:03
claygabalfour: yup, looks like mattoliverau is already looking at it23:04
*** tqtran-afk is now known as tqtran23:13
*** chlong has joined #openstack-swift23:16
*** dmorita has quit IRC23:18
*** dmorita has joined #openstack-swift23:19
abalfoursweet, thanks clayg.23:21
*** asettle has quit IRC23:23
*** dmorita has quit IRC23:24
*** diogogmt has quit IRC23:25
*** dfflanders has joined #openstack-swift23:25
*** chlong has quit IRC23:27
*** Jeffrey4l has joined #openstack-swift23:31
*** dmorita has joined #openstack-swift23:34
*** kei_yama has joined #openstack-swift23:35
*** dmorita has quit IRC23:37
*** zhugaoxiao has joined #openstack-swift23:38
*** Administrator_ has quit IRC23:40
*** dmorita has joined #openstack-swift23:49
*** cdelatte has joined #openstack-swift23:49
*** david-lyle_ has joined #openstack-swift23:50
*** _JZ_ has quit IRC23:51
*** david-lyle has quit IRC23:51
*** rcernin has quit IRC23:52
*** klamath has quit IRC23:53

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