Tuesday, 2016-12-13

notmynamedid you get that step done?00:05
JimCheungyes, it's done00:05
notmynameok, now to tie it all together00:08
notmynamebut first, a footnote00:08
notmynameJimCheung: garyj: do you expect to be contributing to swift itself, or do you expect to keep changes limited to the EC libraries?00:08
JimCheungWe would like to contribute to the EC libraries in the near future00:09
notmynameyeah, that's what I'd expect00:10
notmynameso with "official" openstack projects, like swift but not liberasurecode, there's a CLA that must be signed before you can submit a patch00:10
JimCheungAlso, we would like to contribute the swift itself as well00:10
notmynamein order to sign the CLA you also have to have an openstack account (again with the same email)00:11
JimCheungOkay, we can wait on that for now00:11
notmynameand then you sign that in gerrit (gerrit == review.openstack.org)00:11
JimCheungGot it00:13
garyjwe can get familiarized with the process at the liberasurecode level before moving to the broader swift codebase00:13
notmynameof course00:14
notmyname(sorry, having about 3 conversations at once here) ;-)00:14
notmynameok, so now we can get the code and tie it all together00:14
notmynameat this point, I know you've already got liberasurecode (hereafter "libec" because that's shorter to type) cloned locally00:14
notmynameso in that libec directory, you need to run `git review -s`. this will set up a remote called "gerrit" and install a commit hook00:16
notmynamethe commit hook will add a gerrit change-id to the end of commit messages. all patches proposed have to have it00:16
notmynameand if you have local patches that don't have it, then a `git commit --amend` will add it00:16
notmynameok, so after `git review -s`, run `git fetch --all` to get the gerrit remote and you're pretty much done with the setup00:17
JimCheungGot it00:17
notmynameok, so let's do a small test patch to show you how it works. make a change locally, commit it localy, then run `git review`00:19
notmynamelike just change a text file or something00:19
notmynameit should put an alert in here and make it available for us all to see in gerrit00:19
notmynamelet me know if you see something you don't expect00:21
JimCheungApparently, got a bit of a problem with git, review is not a git command.  Seems the pip install didn't work properly00:24
notmynamehmm00:24
notmynameis `git-review` on your path?00:24
JimCheungNo00:25
JimCheunggit: 'review' is not a git command. See 'git --help'.00:25
zaitcevIt is a separate package in most distributions.00:26
JimCheungokay00:26
notmynameFWIW on my mac it got put in /usr/local/bin/git-review00:33
notmyname(I use my mac for testing and git fu and a linux box for running/testing the code)00:34
notmynameJimCheung: garyj: any luck?00:41
notmynameFWIW, it's https://pypi.python.org/pypi/git-review that you're wanting to have00:42
JimCheungseems there's some issue with my python install.  Reinstalling it now00:42
notmynameoh my00:43
*** asettle has joined #openstack-swift00:50
*** asettle has quit IRC00:55
notmynameJimCheung: garyj: ok, just for a summary of what happens after you submit some code, tests get automatically run against it, people look at it and make comments, often you end up submitting a different version, and then someone clicks the "approve" button and more tests are run and it gets committed upstream01:01
*** diogogmt has joined #openstack-swift01:01
garyjgot it01:01
notmynameso here's the one big difference that I've seen in openstack and openstack-related projects that is different from most non-openstack projects: each change is one and only one commit01:01
notmynamethis means that you squash your work into one change locally before submitting it for review01:02
notmynameif you don't--if you push up some local feature branch--every commit in that branch will be a separate code review01:02
notmynamethat's almost never what you mean to do01:02
JimCheungOkay, that's good to know01:03
notmyname(there are times that's used, but it's one of those circumstances where if you know to do it, you also know enough to know when to do it)01:03
notmynameso that gets around to the "what do I do once a reviewer asks for changes?" step. but I don't want to get too far ahead of where you are01:07
notmynamebut also, since it's the end of the day for me, I'll write it down so you can read over it. but feel free to ask questions of anyone in here01:08
notmynamewhen i'm working on a patch, I keep it locally in a (single-commit) local branch. that way i can easily check it out and work on it some more01:09
notmynamegerrit will rebase changes on top of each other, depending on when they land, so merge commits aren't unusual (they aren't common, but they aren't rare either)01:09
*** tqtran has quit IRC01:10
notmynameso i check out the old patch, sometimes `git rebase master` if needed, and make the changes. then I `git commit --amend` the existing commit (the very important part is to keep the same change-id in the commit message)01:10
notmynamethen it's another `git review` to push it up for review and the cycle repeats01:11
JimCheungSeems I need a .gitreview file01:12
*** _JZ_ has quit IRC01:12
notmynameI think `git review -s` sets that up01:12
notmynameor actually, that shoudl be in the repo, i think01:13
notmynameyeah, there's one in libec already01:13
kota_good morning notmyname01:14
notmynamehello kota_!01:14
kota_sorry i wasn't01:14
kota_notmyname: and i have to leave soon to update my passport, will see irc logs or i could be available tommorow morning at irc01:14
notmynameno worries01:14
kota_notmyname: either is fine but anyway, it's great to know new backend may be available in the future in liberasurecode/pyeclib01:15
notmynamekota_: I wanted to introduce you to JimCheung and garyj. They've been working locally on some additions to libec to add support for their proprietary EC algo01:15
garyjgood morning kota_01:15
kota_notmyname: sure01:15
notmynamefrom what they've said, it reminds be a little of the one you have from NTT01:15
kota_garyj: hello!01:16
JimCheungHi Kota!01:16
notmynamebut they say there's is faster than anyone else's ever and the best thing ever created01:16
notmyname;-)01:16
garyj:)01:16
kota_JimCheung: Hi!01:16
notmyname*their's01:16
JimCheungHaha!01:16
garyjsliced bread01:16
notmynamegaryj: which, interestingly enough was only invented in the early 1920s01:16
kota_sounds great01:17
notmynamekota_: they're interested in contributing upstream, so they stopped by today to get started (and I wanted to intro them to you). IIRC, they're in the same time zone as me01:17
kota_ok, I will take a time in my morning to collaborate them.01:18
kota_notmyname: ^^01:18
JimCheungThanks Kota!01:18
garyjthat's great. thank you01:18
kota_garyj, JimCheung: please let me know anything you need to help01:18
JimCheungThanks!  I'm sure we can use the help!01:19
kota_garyj, JimCheung: looking at irc log, you've already get the first way to push something to upstream.01:19
* kota_ is thinking the next step to me is waiting their patches?01:20
JimCheungStill trying.  Have some issues with git review.01:20
notmynamekota_: yep. totally. nothing specific to do right now, other than all of us to help some new contributors get involved ;-)01:20
kota_k, probably notmyname can help you on gerrit usage better than me :P01:21
JimCheungHere’s the error I got - No '.gitreview' file found in this repository. We don't know where your gerrit is. Please manually create a remote named "gerrit" and try again.01:22
notmynameJimCheung: you're runnign this from inside the libec directory?01:22
JimCheungYes. My local copy01:22
JimCheungI'll do another pull and try again01:23
notmynameJimCheung: where are you pulling from?01:23
* kota_ is leaving for now to go somewhere for my business and will look at logs again01:23
notmynamekota_: thanks for popping in01:23
kota_notmyname: sure01:24
notmynameJimCheung: https://github.com/openstack/liberasurecode is the github mirror01:24
garyjkota_: c u later.01:24
JimCheungBye Kota01:25
notmynameJimCheung: if you clone from the github mirror, it should Just Work (tm)01:29
notmynameJimCheung: garyj: i'm starting to get the pings from home, so I need to take off. I'll likely be online later tonight, and of course I'll be here tomorrow. (others in different timezones have different schedules--perks of a global community)01:34
JimCheungThanks for your help!01:35
notmynameJimCheung: garyj: i'm glad you stopped by, and i'm looking forward to seeing your integration with libec01:35
garyjnotmyname: thank you. we will work though the gerrit issues01:35
*** vint_bra has joined #openstack-swift01:37
*** asettle has joined #openstack-swift01:52
*** asettle has quit IRC01:56
openstackgerritMerged openstack/swift: tempurls with a prefix-based scope  https://review.openstack.org/27404801:58
*** klrmn has quit IRC02:13
*** garyj has quit IRC02:14
*** bkopilov has quit IRC02:30
*** JimCheung has left #openstack-swift02:37
*** vint_bra has quit IRC02:39
*** chlong has quit IRC02:45
*** dmorita has quit IRC02:48
*** asettle has joined #openstack-swift02:52
*** dmorita has joined #openstack-swift02:57
*** asettle has quit IRC02:57
*** chlong has joined #openstack-swift02:59
*** dmorita has quit IRC03:01
*** Worry has joined #openstack-swift03:26
*** raginbajin has quit IRC03:27
*** raginbajin has joined #openstack-swift03:32
*** chsc has joined #openstack-swift03:33
*** chsc has joined #openstack-swift03:33
*** klrmn has joined #openstack-swift03:37
*** garyj has joined #openstack-swift03:38
*** Worry has quit IRC03:39
*** garyj has quit IRC03:40
*** Worry has joined #openstack-swift03:40
*** Worry has quit IRC03:50
*** bkopilov has joined #openstack-swift03:50
*** asettle has joined #openstack-swift03:53
*** asettle has quit IRC03:58
*** Jeffrey4l has quit IRC03:58
*** diogogmt has quit IRC04:00
*** winggundamth has quit IRC04:02
*** Jeffrey4l has joined #openstack-swift04:03
*** winggundamth has joined #openstack-swift04:06
*** psachin has joined #openstack-swift04:06
*** klrmn1 has joined #openstack-swift04:08
*** klrmn has quit IRC04:10
*** links has joined #openstack-swift04:22
*** abhitechie has joined #openstack-swift04:25
*** garyj has joined #openstack-swift04:27
*** garyj has left #openstack-swift04:28
*** dfflanders has quit IRC04:48
*** asettle has joined #openstack-swift04:54
*** asettle has quit IRC04:59
*** abhinavtechie has joined #openstack-swift05:05
hugokuoDec 11 03:06:16 mspol13 container-server: 10.175.107.70 - - [11/Dec/2016:11:06:16 +0000] "DELETE /d349/639/.expiring_objects/1481414367" 409 - "DELETE http://localhost/v1/.expiring_objects/1481414367" "tx8485dd8b6da44ddc823cd-00584d3328" "proxy-server 20658" 0.0014 "-" 32573 -05:05
*** chsc has quit IRC05:05
*** sanchitmalhotra1 has joined #openstack-swift05:05
*** sanchitmalhotra has quit IRC05:05
*** sanchitmalhotra1 is now known as sanchitmalhotra05:05
*** aagrawal has joined #openstack-swift05:06
hugokuoWhat would be the possibility that expirer got 409  ?05:06
hugokuoIt's Swift 2.7.0.1 .05:06
*** tqtran has joined #openstack-swift05:07
*** abhitechie has quit IRC05:08
*** abhitechie has joined #openstack-swift05:09
*** abhinavtechie has quit IRC05:10
*** sanchitmalhotra has quit IRC05:10
*** sanchitmalhotra has joined #openstack-swift05:11
*** tqtran has quit IRC05:11
*** aagrawal has quit IRC05:11
zaitcevI guess when you have 2 expirers...05:17
*** abhinavtechie has joined #openstack-swift05:18
*** aagrawal has joined #openstack-swift05:20
*** abhitechie has quit IRC05:22
*** sanchitmalhotra1 has joined #openstack-swift05:22
*** abhinavtechie has quit IRC05:23
*** sanchitmalhotra has quit IRC05:23
*** sanchitmalhotra1 is now known as sanchitmalhotra05:23
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix stats calculation in object-reconstructor  https://review.openstack.org/28394605:27
*** ppai has joined #openstack-swift05:28
*** abhinavtechie has joined #openstack-swift05:30
*** garyj has joined #openstack-swift05:32
*** abhitechie has joined #openstack-swift05:32
*** aagrawal has quit IRC05:33
*** abhinavtechie has quit IRC05:35
*** abhinavtechie has joined #openstack-swift05:36
*** hseipp has joined #openstack-swift05:36
*** sanchitmalhotra has quit IRC05:38
*** sanchitmalhotra has joined #openstack-swift05:38
*** abhitechie has quit IRC05:39
*** aagrawal has joined #openstack-swift05:46
*** ppai has quit IRC05:48
*** abhinavtechie has quit IRC05:49
hugokuo@zaitcev interesting... let me take a look05:52
hugokuoAlso, just discovered a behaviour which looks like a bug. https://gist.github.com/HugoKuo/abb04c0237fa961ab1104675c59fd2fb05:52
hugokuoThe object-replicator creates hundred connections while the concurrency == 105:53
hugokuoRe: object-expirer 409 , there's just one expirer in the system05:54
*** asettle has joined #openstack-swift05:55
*** asettle has quit IRC06:00
*** abhinavtechie has joined #openstack-swift06:06
*** tovin07 has quit IRC06:06
*** tovin07__ has joined #openstack-swift06:06
mattoliverauhugokuo: a 409 is usually raised by the container server if its trying to delete a container with objects still in it. so could be the same thing here, is it happening when trying to delete the container?06:07
*** aagrawal has quit IRC06:09
hugokuo@mattoliverau yup. It expirer attempted to delete an entry of exipiring_object. It's a container entry. v1/.expiring_objects/148141436706:11
hugokuoso that means the container can't be delete sine there're still have expired object in the queue waiting for purging06:12
mattoliverauyeah, there must still be objects in the container.06:15
*** ppai has joined #openstack-swift06:20
*** abhinavtechie has quit IRC06:23
*** abhinavtechie has joined #openstack-swift06:23
*** hseipp has quit IRC06:25
*** ppai has quit IRC06:26
*** links has quit IRC06:34
*** tovin07__ has quit IRC06:34
*** PavelK has joined #openstack-swift06:34
*** tovin07__ has joined #openstack-swift06:35
*** tovin07__ has quit IRC06:35
*** tovin07__ has joined #openstack-swift06:35
*** links has joined #openstack-swift06:38
*** abhitechie has joined #openstack-swift06:40
*** abhinavtechie has quit IRC06:40
*** tovin07__ is now known as tovin07_afk06:42
*** tovin07_afk has quit IRC06:50
*** asettle has joined #openstack-swift06:56
*** garyj has quit IRC06:57
*** ppai has joined #openstack-swift06:58
*** garyj has joined #openstack-swift07:00
*** garyj has left #openstack-swift07:00
*** asettle has quit IRC07:01
*** dmorita has joined #openstack-swift07:02
*** sams-gleb has joined #openstack-swift07:05
*** dmorita has quit IRC07:07
*** abhitechie has quit IRC07:15
*** Jeffrey4l has quit IRC07:24
*** Jeffrey4l has joined #openstack-swift07:25
*** dmorita has joined #openstack-swift07:48
*** dmorita has quit IRC07:53
*** asettle has joined #openstack-swift07:57
*** asettle has quit IRC08:02
*** zackmdavis has quit IRC08:03
*** zackmdavis has joined #openstack-swift08:04
*** rcernin has joined #openstack-swift08:05
*** oshritf has joined #openstack-swift08:06
*** pcaruana has joined #openstack-swift08:10
*** tqtran has joined #openstack-swift08:10
*** tqtran has quit IRC08:14
*** rcernin has quit IRC08:22
*** rcernin has joined #openstack-swift08:25
*** rledisez has joined #openstack-swift08:28
*** JimCheung has joined #openstack-swift08:36
*** geaaru has joined #openstack-swift08:37
*** garyj has joined #openstack-swift08:38
*** JimCheung has quit IRC08:41
*** garyj has quit IRC08:43
*** kelepirci has joined #openstack-swift08:46
kelepircihello all08:47
kelepircijust quick question.08:47
kelepirciis it safe to delete quarantined objects?08:47
kelepirciit is taking too much space08:47
*** wanghua has joined #openstack-swift08:49
*** cbartz has joined #openstack-swift09:00
*** jordanP has joined #openstack-swift09:00
*** joeljwright has joined #openstack-swift09:17
*** ChanServ sets mode: +v joeljwright09:17
*** asettle has joined #openstack-swift09:20
*** asettle has quit IRC09:22
*** asettle has joined #openstack-swift09:22
*** mvk has quit IRC09:23
*** sanchitmalhotra1 has joined #openstack-swift09:39
*** sanchitmalhotra has quit IRC09:39
*** sanchitmalhotra1 is now known as sanchitmalhotra09:39
*** sanchitmalhotra has quit IRC09:44
*** sanchitmalhotra has joined #openstack-swift09:45
*** sanchitmalhotra has quit IRC09:52
*** sanchitmalhotra has joined #openstack-swift09:52
*** mvk has joined #openstack-swift09:54
*** kelepirci has quit IRC09:57
*** links has quit IRC10:16
*** acoles_ is now known as acoles10:24
*** sanchitmalhotra has quit IRC10:27
*** sanchitmalhotra1 has joined #openstack-swift10:27
*** bkopilov has quit IRC10:28
openstackgerritGábor Antal proposed openstack/swift: Use more specific asserts in test/unit/obj tests  https://review.openstack.org/34283010:28
*** sanchitmalhotra1 is now known as sanchitmalhotra10:29
*** links has joined #openstack-swift10:29
*** asettle has quit IRC10:30
*** asettle has joined #openstack-swift10:36
*** asettle has quit IRC10:37
*** asettle has joined #openstack-swift10:37
*** sams-gleb has quit IRC10:37
*** sams-gleb has joined #openstack-swift10:38
*** garyj has joined #openstack-swift10:40
openstackgerritGábor Antal proposed openstack/swift: Use more specific asserts in test/unit/common  https://review.openstack.org/34278110:42
*** sams-gleb has quit IRC10:42
*** garyj has quit IRC10:44
*** sams-gleb has joined #openstack-swift10:56
*** daemontool has joined #openstack-swift11:02
*** psachin has quit IRC11:03
*** sanchitmalhotra has quit IRC11:05
*** tqtran has joined #openstack-swift11:12
*** sanchitmalhotra has joined #openstack-swift11:12
*** zhugaoxiao has joined #openstack-swift11:13
*** links has quit IRC11:15
*** psachin has joined #openstack-swift11:16
*** tqtran has quit IRC11:17
*** sanchitmalhotra has quit IRC11:23
*** sanchitmalhotra1 has joined #openstack-swift11:23
*** mvk has quit IRC11:24
*** amoralej|off is now known as amoralej11:25
*** sanchitmalhotra1 is now known as sanchitmalhotra11:25
*** links has joined #openstack-swift11:32
*** sanchitmalhotra1 has joined #openstack-swift11:32
*** sanchitmalhotra has quit IRC11:34
*** sanchitmalhotra1 has quit IRC11:37
*** mvk has joined #openstack-swift11:37
*** sanchitmalhotra has joined #openstack-swift11:38
*** zhugaoxiao has quit IRC11:56
*** zhugaoxiao has joined #openstack-swift11:56
openstackgerritGábor Antal proposed openstack/swift: Use more specific asserts in test/unit/common/middleware  https://review.openstack.org/34277012:26
*** garyj has joined #openstack-swift12:42
*** bkopilov has joined #openstack-swift12:46
*** garyj has quit IRC12:46
*** mingyu has joined #openstack-swift12:50
*** mingyu has quit IRC12:53
timssHi. I'm able to set ACLs using `swift -r|-w project_id:user_id`, and list contents of the container with a token of the ACL user with `swift --os-auth-token TOKEN --os-storage-url http://../v1/AUTH_ID/container list`. But is it possible to do the last part without having to define storage URL and token, i.e. normal environment/--os-* credentials and specify container with something like `swift list`?13:00
timssIt seems to only allow container name.13:00
*** siva_krish has joined #openstack-swift13:01
*** kei_yama has quit IRC13:02
*** abhitechie has joined #openstack-swift13:02
*** dmorita has joined #openstack-swift13:05
*** vint_bra has joined #openstack-swift13:07
*** dmorita has quit IRC13:09
*** abhitechie has quit IRC13:13
*** tqtran has joined #openstack-swift13:14
*** juzuluag has joined #openstack-swift13:16
*** tqtran has quit IRC13:18
timssHm, seems only the storage url is required. Pretty cool, but the user would have to know the account (AUTH_)/storage URL though, not only the project/container. Or?13:19
*** asettle has quit IRC13:19
*** asettle has joined #openstack-swift13:19
*** juzuluag has quit IRC13:25
*** PavelK has quit IRC13:29
*** JimCheung has joined #openstack-swift13:34
*** JimCheung has quit IRC13:39
openstackgerritShashirekha Gundur proposed openstack/python-swiftclient: modify 'swift <sub_command> —help' display  https://review.openstack.org/39011913:41
*** amoralej is now known as amoralej|lunch13:44
tdasilvatimss: not sure I understand your question, but if you define env. variables: ST_AUTH, ST_USER, ST_KEY then you should be able to run something like `swift list`13:45
timsstdasilva: Sorry, it got a bit clunky in my effort to be concise. I guess the question is if it's possible to do operations such as `swift list` on containers in other projects/accounts based on ACL, without knowing the storage URL or account/AUTH_ of the container in the other project.13:50
timssLets say user 'foo' do `swift post -r <bar_project_uuid>:* testcontainer`. A user in project 'bar' can then do `OS_STORAGE_URL=http://../v1/AUTH_<foo_project_uuid> swift list testcontainer`.13:51
timssBut can a user in 'bar' list contents of 'testcontainer' when (s)he only knows the domain/name of the project and container, and not the storage URL/account id of the owner of the container?13:52
timssOr would a 'bar' user have to ask 'foo' for their account/storage URL (AUTH_) details?13:53
*** dmsimard has left #openstack-swift13:59
tdasilvatimss: I *think* you would have to know their account/storage URL. I'm trying to think if you could get that info from keystone, but i'm not sure if it's possible14:04
timsstdasilva: all right, that sounds plausible. I was trying to think of a way myself, but couldn't find any :)14:04
timssIt's not too critical, but will require my users to understand how a storage URL works14:05
tdasilvatimss: there are more folks in PT timezone that come in later that might be able to give you a better answer14:06
timsstdasilva: All right, thanks!14:06
*** dmsimard has joined #openstack-swift14:21
*** dmsimard has left #openstack-swift14:24
*** dmsimard has joined #openstack-swift14:28
*** abhitechie has joined #openstack-swift14:28
*** dmsimard has quit IRC14:28
*** dmsimard has joined #openstack-swift14:30
*** daemontool has quit IRC14:33
*** siva_krish has quit IRC14:34
*** amoralej|lunch is now known as amoralej14:36
*** abhitechie has quit IRC14:41
*** abhitechie has joined #openstack-swift14:42
openstackgerritMahati Chamarthy proposed openstack/swift: Move documented reclaim_age option to correct location  https://review.openstack.org/37441914:42
*** garyj has joined #openstack-swift14:44
*** abhinavtechie has joined #openstack-swift14:45
*** abhitechie has quit IRC14:47
*** garyj has quit IRC14:48
*** ppai has quit IRC14:48
*** dmsimard has left #openstack-swift14:49
*** psachin has quit IRC14:50
*** sams-gleb has quit IRC14:51
*** sams-gleb has joined #openstack-swift14:51
*** wanghua has quit IRC14:56
*** sams-gleb has quit IRC14:56
*** abhinavtechie has quit IRC15:00
*** abhitechie has joined #openstack-swift15:03
*** sams-gleb has joined #openstack-swift15:09
*** abhitechie has quit IRC15:13
*** chlong has quit IRC15:13
*** tqtran has joined #openstack-swift15:15
openstackgerritGábor Antal proposed openstack/swift: Use more specific asserts in test/unit/common/middleware  https://review.openstack.org/34277015:15
*** abhitechie has joined #openstack-swift15:18
*** tqtran has quit IRC15:20
*** siva_krish has joined #openstack-swift15:22
*** siva_krish has quit IRC15:30
*** links has quit IRC15:42
*** siva_krish has joined #openstack-swift15:45
*** siva_krish has quit IRC15:54
*** rcernin has quit IRC16:04
*** daemontool has joined #openstack-swift16:07
*** pcaruana has quit IRC16:09
*** _JZ_ has joined #openstack-swift16:11
*** chsc has joined #openstack-swift16:16
*** chsc has joined #openstack-swift16:16
*** tqtran has joined #openstack-swift16:17
openstackgerritMerged openstack/swift: Py3: Make test_manager py3 compatable  https://review.openstack.org/34779916:20
*** tqtran has quit IRC16:21
*** vint_bra has quit IRC16:22
*** siva_krish has joined #openstack-swift16:24
*** chsc has quit IRC16:25
-openstackstatus- NOTICE: Launchpad SSO is not currently working, so logins to our services like review.openstack.org and wiki.openstack.org are failing; the admins at Canonical are looking into the issue but there is no estimated time for a fix yet.16:26
*** ChanServ changes topic to "Launchpad SSO is not currently working, so logins to our services like review.openstack.org and wiki.openstack.org are failing; the admins at Canonical are looking into the issue but there is no estimated time for a fix yet."16:26
*** tsg has joined #openstack-swift16:27
*** oshritf has quit IRC16:31
notmynamegood morning16:35
openstackgerritAlistair Coles proposed openstack/swift: Add test for configured reclaim_age being used  https://review.openstack.org/41031116:39
*** garyj has joined #openstack-swift16:45
*** chlong has joined #openstack-swift16:46
*** asettle__ has joined #openstack-swift16:49
*** garyj has quit IRC16:49
*** asettle has quit IRC16:53
*** garyj has joined #openstack-swift16:56
*** rcernin has joined #openstack-swift17:00
*** Jeffrey4l has quit IRC17:00
*** Jeffrey4l has joined #openstack-swift17:00
*** asettle__ is now known as asettle17:01
*** ChanServ changes topic to "Let's talk, we're nice. | Ideas: https://wiki.openstack.org/wiki/Swift/ideas | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews"17:03
-openstackstatus- NOTICE: Canonical admins have resolved the issue with login.launchpad.net, so authentication should be restored now.17:03
*** htruta` is now known as htruta17:07
*** mvk has quit IRC17:07
*** abhitechie has quit IRC17:07
*** abhitechie has joined #openstack-swift17:08
*** asettle has quit IRC17:15
*** garyj has quit IRC17:18
*** garyj has joined #openstack-swift17:19
*** chsc has joined #openstack-swift17:21
*** chsc has joined #openstack-swift17:21
*** diogogmt has joined #openstack-swift17:23
*** rcernin has quit IRC17:24
*** klamath has joined #openstack-swift17:27
*** klamath has joined #openstack-swift17:28
*** dmorita has joined #openstack-swift17:28
*** rcernin has joined #openstack-swift17:35
*** rcernin has quit IRC17:35
*** JimCheung has joined #openstack-swift17:40
*** JimCheung has left #openstack-swift17:43
openstackgerritTim Burke proposed openstack/swift: py3: port common/ring/, common/linkat.py, and common/utils.py  https://review.openstack.org/40139717:43
claygnotmyname: nice write up this morning!17:47
notmynamethanks17:47
notmynameit's the kind of day where someone asks a 2 dozen work question and I respond with a small novella17:47
notmyname;-)17:48
claygan epic battle between in which the heroes of availability come to bear against the evil forces of failure and uncertainty!17:49
clayg*bare17:50
claygmaybe?17:50
claygi guess i had it right the first time17:51
*** siva_krish has left #openstack-swift17:53
*** rledisez has quit IRC17:53
*** jordanP has quit IRC17:55
*** mingyu has joined #openstack-swift17:58
*** abhitechie has quit IRC18:02
*** tqtran has joined #openstack-swift18:06
*** geaaru has quit IRC18:07
*** daemontool has quit IRC18:08
*** abhitechie has joined #openstack-swift18:13
*** asettle has joined #openstack-swift18:14
notmyname2.12.0 release notes proposed to https://review.openstack.org/#/c/409924/18:16
patchbotpatch 409924 - swift - Swift 2.12.0 authors/changelog updates18:16
notmynameI'll add the yaml file after it goes through review (I know people will find stuff!)18:17
*** siva_krish has joined #openstack-swift18:20
acolesif a middleware __init__ has an error what's the *right thing* that should happen: middleware __init__ raises exception or middleware calls sys.exit? (I'm looking at patch 393388 and seems we are inconsistent in places)18:20
patchbothttps://review.openstack.org/#/c/393388/ - swift - Raise ValueError if a config section does not exist18:20
*** chsc has quit IRC18:20
acolesI feel like whatever is loading middleware should catch exceptions and handle then how it sees fit.18:21
acolesthem*18:21
*** diogogmt has quit IRC18:22
notmynameacoles: yeah, it does look odd that there's the inconsistency18:25
notmynameacoles: I don't think it really matters, as long as (1) when someone sees the exit/error it's obvious what didn't work and (2) consistency is preferred18:26
acolesI suspect that in keymaster the sys.exit happens simply because that's what readconf did (which is the bug) - so not by design, just side-effect18:26
*** mingyu has quit IRC18:26
acolesyep, consistency is good, except when it comes to under-performance ;)18:27
*** joeljwright has quit IRC18:32
notmynameoh yay! https://review.openstack.org/#/c/274048/ landed!18:34
patchbotpatch 274048 - swift - tempurls with a prefix-based scope (MERGED)18:34
notmynamehmm...means that it needs to be referenced in the changelog18:35
*** chsc has joined #openstack-swift18:35
*** chsc has joined #openstack-swift18:35
*** cbartz has left #openstack-swift18:44
*** acoles is now known as acoles_18:44
*** silor1 has joined #openstack-swift18:50
notmynameFYI http://lists.openstack.org/pipermail/openstack-dev/2016-December/108875.html18:56
notmyname"[openstack-dev] Golang technical requirements"18:56
*** abhinavtechie has joined #openstack-swift18:59
*** dmorita has quit IRC19:00
*** dmorita has joined #openstack-swift19:01
*** abhitechie has quit IRC19:03
*** diogogmt has joined #openstack-swift19:03
*** diogogmt has quit IRC19:04
*** diogogmt has joined #openstack-swift19:05
*** douglascorrea has joined #openstack-swift19:07
*** asettle has quit IRC19:08
*** abhinavtechie has quit IRC19:13
*** rcernin has joined #openstack-swift19:14
notmyname2.7.1 and 2.10.1 just landee19:14
notmyname*landed19:14
tdasilvai remember seeing a table of releases somewhere...19:15
notmynameyeah, I'll got update it19:16
notmynameif you're referring to https://wiki.openstack.org/wiki/Swift/version_map19:16
tdasilvayes! thanks!19:16
notmynamedone19:18
notmynamenot sure on the right visualization on that for stable releases, but that should work19:19
*** garyj has quit IRC19:33
*** garyj has joined #openstack-swift19:34
*** silor1 has quit IRC19:34
*** oshritf has joined #openstack-swift19:38
*** garyj has quit IRC19:38
*** jordanP has joined #openstack-swift20:02
*** jordanP has quit IRC20:04
*** douglascorrea has quit IRC20:05
*** douglascorrea has joined #openstack-swift20:06
*** dmorita has quit IRC20:09
*** dmorita has joined #openstack-swift20:10
*** douglascorrea has quit IRC20:11
*** dmorita has quit IRC20:14
*** dmorita has joined #openstack-swift20:14
*** abhitechie has joined #openstack-swift20:17
*** amoralej is now known as amoralej|off20:17
tdasilvanotmyname: might need to update changelog again once patch 391090 merges ;)20:17
patchbothttps://review.openstack.org/#/c/391090/ - swift - SLO: Make etag and size_bytes fully optional20:17
*** abhinavtechie has joined #openstack-swift20:31
*** dfflanders has joined #openstack-swift20:31
*** abhitechie has quit IRC20:32
notmynameFWIW, there's now an #openstack-meeting-520:45
*** _david_cole_soho has joined #openstack-swift21:01
*** tsg has quit IRC21:08
_david_cole_sohoI seem to have gotten myself into a pickle with 2.10 and Encryption at Rest.   A week ago I upgraded to 2.10 and enable Encryption at Rest.   I upgraded the software but on one out of nine backend (ACO) servers I did not restart the processes (doh!)     .  For about 3 days 8 ouf of 9 were running 2.10 and one was running 2.7.  This issue was resolved mid last week.      The issue I have now is that  I have invalid etags in21:10
_david_cole_sohocontainer listings, I think this impacts < 20% of the new objects that were added in that three day period.     If I HEAD the object which has the invalid etag in the container listing, the object etag is correct.   After waiting over the weekend for one of the backend auditors to ‘sort it out’, the etags are still incorrect.   Does anyone have any thoughts on fixing this issue?21:10
claygnotmyname: because lp bug #1491605 has the effect of making all the reconstructor concurrency run on a single disk and effect performance during a rebalance i bumped it up to "high" - but medium might be more correct21:10
openstackLaunchpad bug 1491605 in OpenStack Object Storage (swift) "Reconstructor jobs are ordered by disk instead of randomized" [High,Confirmed] https://launchpad.net/bugs/149160521:10
notmynameclayg: ack21:11
clayg_david_cole_soho: it's not immediately obvious to me why the etags are incorrect in this scenario - my naieve initial thought is that a restarted proxy would encrypt while an un-restarted proxy would not - the object itself should be either encrypted or not and all metadata should match - as the encryption is aways done at the proxy, notated on the object and passed unmodified and more-or-less transparently through the storage21:13
*** douglascorrea has joined #openstack-swift21:14
timburkeclayg: i think the trouble is that there were encrypting proxies running without the x-backend-container-update-override-etag (or whatever; i forget exactly) header support in the object nodes21:15
claygtimburke: yup - i was slow - but i'm think i'm there - it's the "more-or-less transparently"21:15
claygif a new proxy was talking to an old object server - screwed21:15
timburkeit's the ... yeah, that bit exactly :-)21:16
timburkethat's my fear as well :-/21:16
_david_cole_sohoIt would have been a new proxy talking to an old object server21:16
claygit's weird - i feel like *someone* said turning on encryption on a standing cluster was mis-feature - dunno who said that - but I feel like they said it *a lot*21:16
mattoliveraumorning21:17
jrichlipretty sure that was you, clayg ;-)21:18
clayg_david_cole_soho: how many accounts/users/containers do you have on the system?21:18
timburkeeven *detecting* the problem is somewhat problematic... i guess you might be able to have something go through the object servers looking for etag mismatches, then update the x-timestamp to be something like <old ts>_0000000001, and try the container update again?21:18
_david_cole_sohoIt was my understanding that enabling encryption on an existing cluster would work , but with the caveat that there is no background scrub to encrypt older objects21:19
clayg_david_cole_soho: my current thinking is a onetime audit of the container db layer to remove offesnive rows so that replicator can sort things out might be one path forward21:19
claygit's rather operationally intensive tho - to my knowledge no one has reported on this experience to date21:19
claygtimburke: I think you could just delete the rows on the container db's as long as you reset the sync poitns21:20
claygif none of the object-server replicas repoted an encrypted etag it's probably no worse than just being an old object21:20
claygthe trick is only deleting rows where you think you can find a replacement21:20
*** asettle has joined #openstack-swift21:21
clayg... so the script might have to go one replica at a time?  If two are effected it could take multiple sweeps... it's kinda gross21:21
clayg_david_cole_soho: what's the cardinality on container db's21:21
claygor object count for that matter21:21
_david_cole_sohoIf maintaining timestamps was not a prority, could I GET and then re-PUT each of the objects to fix the container listings ?21:22
timburkedefinitely.21:23
_david_cole_sohoI don’t think I can script deleting rows from the sqllite container DB, avoiding all the pitfalls that entails, but I can probably scan for bad objects and script a GET/PUT cycle21:24
tdasilvawhat about a COPY?21:25
claygsame thing as kota's re-put script21:25
clayghttps://launchpadlibrarian.net/292772595/reputter.py21:27
*** tsg has joined #openstack-swift21:30
*** chlong has quit IRC21:30
_david_cole_sohothank you. I will take a look21:30
*** siva_krish has quit IRC21:30
openstackgerritBryan Keller proposed openstack/swift: Use case-insensitive headers in proxy-server  https://review.openstack.org/41040721:34
*** Jeffrey4l has quit IRC21:35
*** douglascorrea has quit IRC21:35
*** douglascorrea has joined #openstack-swift21:36
*** amoralej|off is now known as amoralej21:36
*** asettle has quit IRC21:39
*** douglascorrea has quit IRC21:41
*** oshritf has quit IRC21:43
*** tsg has quit IRC21:46
*** Jeffrey4l has joined #openstack-swift21:47
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873621:50
*** sams-gleb has quit IRC21:55
*** sams-gleb has joined #openstack-swift21:55
*** asettle has joined #openstack-swift21:58
*** sams-gleb has quit IRC22:00
*** amoralej is now known as amoralej|off22:01
*** siva_krish has joined #openstack-swift22:02
*** douglascorrea has joined #openstack-swift22:05
*** tsg has joined #openstack-swift22:07
*** asettle has quit IRC22:09
openstackgerritJohn Dickinson proposed openstack/swift: Swift 2.12.0 authors/changelog updates  https://review.openstack.org/40992422:12
*** mvk has joined #openstack-swift22:32
*** garyj has joined #openstack-swift22:36
*** garyj has quit IRC22:40
openstackgerritJohn Dickinson proposed openstack/swift: Swift 2.12.0 authors/changelog updates  https://review.openstack.org/40992422:40
openstackgerritMerged openstack/python-swiftclient: modify 'swift <sub_command> —help' display  https://review.openstack.org/39011923:00
*** _JZ_ has quit IRC23:00
openstackgerritMerged openstack/swift: SLO: Make etag and size_bytes fully optional  https://review.openstack.org/39109023:02
*** chsc has quit IRC23:11
*** siva_krish has quit IRC23:21
*** klamath has quit IRC23:29
*** garyj has joined #openstack-swift23:38
*** garyj has quit IRC23:43
*** JimCheung has joined #openstack-swift23:45
JimCheungHello notmyname: It appears the git review issues from yesterday has been resolved.23:49
notmynameJimCheung: yay!23:50
JimCheungThanks for the help!23:50
notmynameJimCheung: so `git review -s` to set up the repo, and then `git review` to upload a patch for review23:50
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925023:52
openstackgerritJohn Dickinson proposed openstack/swift: Swift 2.12.0 authors/changelog updates  https://review.openstack.org/40992423:52
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873623:53
notmynameJimCheung: I just did it myself^23:53
JimCheungrepo is setup.  We'll need to package up all the changes in one commit to submit.23:53
*** kei_yama has joined #openstack-swift23:54
notmynamegreat23:56
JimCheungmay take a little while before submitting.  Need to do some refactoring.  ;-)23:59

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