Wednesday, 2015-01-07

*** david-lyle is now known as david-lyle_afk00:01
*** barra204 has joined #openstack-swift00:05
hogood morning guys00:05
mattoliverauho: morning00:09
homattoliverau: morning! morning!00:26
notmynamehi00:30
honotmyname: hi!00:32
*** Masahiro has joined #openstack-swift00:35
*** barra204 has quit IRC00:37
*** Masahiro has quit IRC00:39
*** elambert has quit IRC00:40
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix slo constraint according to the error message  https://review.openstack.org/14517700:51
*** ctennis has quit IRC00:52
*** ctennis has joined #openstack-swift00:52
*** Masahiro has joined #openstack-swift00:58
notmynameoverloaded ring weights. while I really like the idea as it's been explained to me, I feel that reviewing the patch is going to make my brain hurt01:14
notmynameif only it were commit messages that ran in prod instead of code01:14
notmyname /thanks torgomatic01:14
torgomaticif it was hard to write, it should be hard to read /s01:15
notmynameif commit messages were what ran in prod, I'd `git commit -am "made object server faster"`01:15
notmynamealso, `git commit -am "implemented erasure codes"`01:16
mattoliveraulol01:16
*** reed has quit IRC01:19
claygredbo: dfg: how up to date is git@github.com:redbo/goswiftobj.git with the other code you guys are trying out?01:19
*** reed has joined #openstack-swift01:22
*** nosnos has joined #openstack-swift01:27
redboclayg: not at all, we've been working on it quite a bit.  The plan is still to open source it, but general consensus is it should be not broken first.01:27
*** lcurtis has quit IRC01:28
*** addnull has joined #openstack-swift01:30
*** reed has quit IRC01:40
homattoliverau: In Dec 12, I talked about a patch https://review.openstack.org/#/c/89568 with you.02:02
homattoliverau: Then I sent an email to the owner but couldn't get any response.02:02
homattoliverau: I will wait for a response until Jan 12.02:02
homattoliverau: If I can not get any response, I would like to take it over to realize RBAC with Keystone. Is it possible?02:03
*** haomaiwang has joined #openstack-swift02:08
hoclayg: hi!02:31
hoclayg: if possible, i would like to have your re-review for https://review.openstack.org/#/c/133155/.02:33
*** SkyRocknRoll has joined #openstack-swift02:39
*** SkyRocknRoll has quit IRC03:09
*** nosnos has quit IRC03:20
*** fandi has quit IRC03:23
*** chlong has quit IRC03:41
*** chlong has joined #openstack-swift03:42
*** chlong has quit IRC03:42
*** chlong has joined #openstack-swift03:44
*** chlong has quit IRC03:48
*** chlong has joined #openstack-swift03:48
*** ppai has joined #openstack-swift03:56
*** ho__ has joined #openstack-swift04:05
*** ho has quit IRC04:07
*** nosnos has joined #openstack-swift04:15
*** gyee has quit IRC04:31
openstackgerritTushar Gohad proposed openstack/swift: Bump eventlet version to 0.16.0  https://review.openstack.org/14540305:07
*** ho has joined #openstack-swift05:11
*** ho__ has quit IRC05:13
*** addnull has quit IRC05:31
*** remix_auei has quit IRC05:37
*** remix_tj has joined #openstack-swift05:39
*** zaitcev has quit IRC05:42
*** lcurtis has joined #openstack-swift06:08
lcurtisim wondering if there is anyone on who might be able answer why objects and containers keep disappearing on me in swift?06:10
lcurtisor maybe most obvious cause06:10
holcurtis:  "keep disappearing"means not removed explicitly but looks disappering?06:16
lcurtiswell, from horizon, the container disappears06:16
lcurtisand then swift list 'container' not found06:18
lcurtisso in that regard...yes to your question06:18
holcurtis: i see. can you share the env?06:19
holcurtis: can you use same account for the access?06:20
lcurtisho: not sure what you mean06:20
holcurtis: i guess there are two candidates or more. first one is someone remove the objects. second one is you use different project-id for authentication.06:22
lcurtisno same project id06:22
lcurtisand user06:23
holcurtis: try to use same one.06:23
lcurtisyes i mean i use same project and user06:23
*** km has joined #openstack-swift06:23
holcurtis: sorry for mis-understanding. i have no idea...06:24
lcurtisthanks for your help all the same06:24
lcurtisi will try recreating...06:24
lcurtisgood night all...be back on tomorrow06:24
holcurtis: good night!06:25
wernite06:25
mattoliveraulcurtis: are you using the same proxy each time?06:27
*** ajay_ has joined #openstack-swift06:27
lcurtishmmm...perhaps06:28
ajay_I get: ImportError: No module named middleware.recon, when I start the swift deamon. Can anyone help?06:29
lcurtisusing etc hosts06:29
lcurtisso is probably hitting same proxy06:30
mattoliveraulcurtis: just wondering if your hitting different proxies (load balenced) and the if the rings don't match then the proxy may look for a container in a different place.... thus disappearing.06:36
mattoliveraulcurtis: does the container come and go, or does it simply disappear?06:36
lcurtisthats what it seems like06:36
mattoliveraudid you check the storage server logs? is there a permissions error or something causing the container to not actaully be saved to disk06:37
mattoliveraulcurtis: ^06:37
mattoliveraulcurtis: point directly to the IP of a proxy to make sure your going through it, and create a container (I use curl usually) and then see if it disappears, if it does probably a backend thing06:39
hoajay_: maybe description of confs is wrong,. first check [pipeline:main] section in the [account|container|object]-server.conf whether there is recon.06:40
hoajay_: then check [filter:recon] section whether the descption is correct.06:40
mattoliverauif its the backend start with the logs, check permissions, etc.06:40
mattoliveraulcurtis: ^06:40
*** lcurtis has quit IRC06:42
*** addnull has joined #openstack-swift06:42
*** lcurtis has joined #openstack-swift06:42
mattoliveraulcurtis: I'm sitting in car waiting at a train station for the wife to arrive, so probably wont be online for much longer.. but will be online tomorrow and I can try and help you work it out if you need :)06:42
lcurtismattoliverau--no worries06:43
lcurtismattoliverau That would be fantastic....i sincerely appreciate t06:43
lcurtisso many helpful people here06:44
mattoliverauCools, looks like the train is here, better get off the phone so I can drive. Night all06:46
*** addnull has quit IRC06:46
ajay_ho: Thanks for replying. I have used the conf file as it is given in here: http://docs.openstack.org/developer/swift/development_saio.html06:59
*** Masahiro has quit IRC07:03
*** Masahiro has joined #openstack-swift07:03
*** sandywalsh has quit IRC07:11
*** lcurtis has quit IRC07:11
*** sandywalsh has joined #openstack-swift07:13
*** silor has joined #openstack-swift07:22
*** Masahiro has quit IRC07:24
*** Masahiro has joined #openstack-swift07:30
*** Masahiro has quit IRC07:33
hoajay_: thanks for the info. offcource there is no problem in the doc. is it possible to remove recon entry from the pipelines? Or check recon entry in swift.egg-info/entry_points.txt, unn....07:55
*** fandi has joined #openstack-swift08:00
*** pcaruana|afk| is now known as pcaruana08:04
ajay_ho: I removed recon from pipeline. It solved the problem but gives a new error: ImportError: No module named catch_errors08:06
*** chlong has quit IRC08:07
hoajay_: removing recon entries means not use recon. i think if you remove catch_errors entry from the conf, you may get same error for other middlewares.08:13
*** addnull has joined #openstack-swift08:14
hoajay_: one question. did you execute the procedure "cd $HOME/swift; sudo python setup.py develop; cd -" in step4?08:14
ajay_ho: Yes. I followed the exact steps.08:17
ajay_I removed recon and got all the demons running except proxy.08:19
*** geaaru has joined #openstack-swift08:21
hoajay_: in your env, swift can solve app entries like [app:container-server] but can not solve filter entries08:22
*** addnull has quit IRC08:22
hoajay_: [filter:catch_errors]08:22
hoajay_: after you executed git clone in step3, you have swift dir. is it still remained in your env?08:25
ajay_ho: Yes. It is there.08:27
ajay_I removed catch_errors and all the middleware modules seems to give the same error.08:33
ajay_ho^08:33
ajay_ho: When I do "python -c 'import swift.common.middleware.catch_errors; print "SUCCESS"'" I get success.08:36
hoajay_: thanks. i think step4 doesn't work correctly,  the line "cd $HOME/swift; sudo python setup.py build; sudo python setup.py install; cd -" may work instead of step408:38
ajay_ho: No it still didn't work. Same error.08:42
ajay_I had already done python setup.py develop. And now I did a python setup.py build and install over it.08:44
*** addnull has joined #openstack-swift08:49
ajay_ho: /var/log/messages shows this: Executable '/usr/bin/swift-proxy-server' doesn't belong to any package and ProcessUnpackaged is set to 'no'08:51
*** Masahiro_ has joined #openstack-swift08:57
*** pcaruana has quit IRC08:59
*** nosnos has quit IRC09:00
hoajay_: i see... the message does not directly related to the case. it is one of the effect of this trouble.09:01
*** nosnos has joined #openstack-swift09:01
*** jordanP has joined #openstack-swift09:05
*** jordanP has joined #openstack-swift09:05
*** nosnos has quit IRC09:08
*** nosnos has joined #openstack-swift09:10
*** pcaruana has joined #openstack-swift09:12
*** jistr has joined #openstack-swift09:14
*** rledisez has joined #openstack-swift09:14
*** nellysmitt has joined #openstack-swift09:23
*** addnull has quit IRC09:33
*** acoles_away is now known as acoles09:41
*** esmute has quit IRC10:03
*** esmute has joined #openstack-swift10:06
*** addnull has joined #openstack-swift10:18
*** rledisez has quit IRC10:20
*** rledisez has joined #openstack-swift10:35
*** chlong has joined #openstack-swift10:38
*** Masahiro_ has quit IRC10:41
*** haomaiwang has quit IRC10:42
*** Masahiro has joined #openstack-swift10:43
*** NM has joined #openstack-swift10:45
*** Masahiro has quit IRC11:00
*** Masahiro has joined #openstack-swift11:00
*** Masahiro has quit IRC11:06
*** chlong has quit IRC11:08
*** mahatic has joined #openstack-swift11:31
NMMorning!11:32
NMajay_: did you solve your problem?11:32
ajay_Yes. Thanks. NM11:32
NMWhat happened?11:32
ajay_Ho, thank you11:32
ajay_[14:04] <ho> ajay_: thanks. i think step4 doesn't work correctly,  the line "cd $HOME/swift; sudo python setup.py build; sudo python setup.py install; cd -" may work instead of step411:33
ajay_This worked for me.11:33
hoajay_: great!11:34
*** Masahiro has joined #openstack-swift11:47
*** Masahiro has quit IRC11:47
*** Masahiro has joined #openstack-swift11:48
*** ppai has quit IRC11:51
hogood night!11:51
*** ho has quit IRC11:52
*** km has quit IRC11:53
*** david-lyle_afk is now known as david-lyle11:58
*** ajay_ has quit IRC12:03
*** ppai has joined #openstack-swift12:04
*** lpabon has joined #openstack-swift12:04
*** fandi has quit IRC12:08
openstackgerritPrashanth Pai proposed openstack/swift: fsync() on directories  https://review.openstack.org/12692312:19
*** Masahiro has quit IRC12:26
openstackgerritMerged openstack/swift: Only move too-close-together replicas when they can spread out.  https://review.openstack.org/14087912:31
*** tdasilva has quit IRC12:31
*** dmsimard_away is now known as dmsimard12:33
*** miqui has quit IRC12:36
*** nosnos has quit IRC12:43
*** nshaikh has joined #openstack-swift12:46
*** fandi has joined #openstack-swift12:50
openstackgerritMerged openstack/swift: Avoid unnecessary unlink() on every successful PUT  https://review.openstack.org/14394312:57
*** lpabon has quit IRC13:08
*** addnull has quit IRC13:08
*** david-lyle is now known as david-lyle_afk13:08
*** Masahiro has joined #openstack-swift13:27
*** ppai has quit IRC13:30
*** Masahiro has quit IRC13:32
*** SkyRocknRoll has joined #openstack-swift13:51
*** ppai has joined #openstack-swift13:55
*** NM has quit IRC13:56
*** tdasilva has joined #openstack-swift13:57
*** bill_az has joined #openstack-swift14:03
*** nshaikh has quit IRC14:06
openstackgerritMahati proposed openstack/swift: Implement OPTIONS verb for storage nodes.  https://review.openstack.org/14010314:11
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873614:14
*** ppai has quit IRC14:19
*** SkyRocknRoll has quit IRC14:41
*** lpabon has joined #openstack-swift14:42
*** SkyRocknRoll has joined #openstack-swift14:55
*** jistr has quit IRC14:57
*** jistr has joined #openstack-swift14:59
*** annegentle has joined #openstack-swift15:08
*** Masahiro has joined #openstack-swift15:16
*** Masahiro has quit IRC15:21
*** NM has joined #openstack-swift15:22
*** dkingshott has joined #openstack-swift15:35
*** elambert has joined #openstack-swift15:48
*** zaitcev has joined #openstack-swift16:04
*** ChanServ sets mode: +v zaitcev16:04
*** cdelatte has joined #openstack-swift16:15
*** cdelatte has quit IRC16:16
*** cdelatte has joined #openstack-swift16:16
*** jistr has quit IRC16:18
*** nellysmitt has quit IRC16:21
*** reed has joined #openstack-swift16:25
*** jistr has joined #openstack-swift16:34
*** gyee has joined #openstack-swift16:40
*** atan8 has joined #openstack-swift16:49
*** annegentle has quit IRC16:55
*** SkyRocknRoll has quit IRC16:59
notmynamegood morning17:00
mahaticgood morning!17:00
notmynamemahatic: how are you?17:01
mahaticnotmyname, I'm good. Went through ringmd517:02
mahaticalso, this one looks like it's ready for review https://review.openstack.org/#/c/140103/17:03
notmynamemahatic: great17:04
*** Masahiro has joined #openstack-swift17:05
pelusegood morning!17:05
mahaticit should have been ready yesterday except for my blatant mistake ;)17:05
notmynamepeluse: will you be around in a couple of hours for the team meeting?17:06
peluseyup17:08
*** atan8 has quit IRC17:09
notmynamegreat, thanks. I'll try to give a summary of EC from this week, but extra color and detail will probably best come from you :-)17:09
*** Masahiro has quit IRC17:10
notmynamemahatic: I'm going through email. I'll look at your patch right after17:12
pelusenotmyname, no problema17:12
mahaticnotmyname, sure, no problem17:14
* notmyname select all + mark as read17:14
notmyname /notreally17:14
*** atan8 has joined #openstack-swift17:15
*** jordanP has quit IRC17:24
*** rledisez has quit IRC17:25
notmynamemahatic: I'm looking right now. I suspect there will be a few other things to add to this patch. I'll leave comments in gerrit17:25
mahaticnotmyname, sure17:26
*** jistr has quit IRC17:26
*** atan8 has quit IRC17:29
notmynamemahatic: ok. just 2 things I think17:38
notmynamemahatic: first, and importantly, what you have right now looks really good!17:39
notmynamemahatic: if there weren't additional requirements, I'd +2 it as-is17:39
mahaticnotmyname, cool17:39
notmynamehowever, there are 2 things I think need to be handled17:39
notmynamefirst the simpler one17:39
mahaticokay17:40
notmyname...thinking...17:41
mahatic:D alright17:41
notmynamehttp://tools.ietf.org/html/rfc7231#section-4.3.7  <-- defines the OPTIONS verb17:41
notmynamethe initial thing we've talked about (the recon checker) will make an OPTIONS request to * since it's looking for server capabilities instead of the capabilities at a particular resource on that server17:42
mahaticright17:43
notmynamemy initial thought is that the OPTIONS should maybe only respond to OPTIONS *, but then I was thinking if the response would actually be any different for a specific path17:43
notmynamehmm..I guess an OPTIONS request to a specific path should probably have the right response code (eg 200 vs 404)17:44
mahaticsorry, was looking at the code, (reading what you wrote now)17:45
*** EmilienM is now known as EmilienM|afk17:45
notmynameya, it should. see the OPTIONS support in the proxy. (however, it also looks like the proxy's OPTIONS support doesn't handle * properly. that should get fixed later)17:46
mahaticyou are right about the response code part17:46
notmynamehmm17:47
*** david-lyle_afk is now known as david-lyle17:47
notmynamewell, that's not actually what the proxy OPTIONS request does either17:47
notmynameit checks to see if it's a valid path (format) and checks auth. but it doesn't actually check the particular resource (eg 404)17:48
openstackgerritMerged openstack/swift: Add undocumented options to keystoneauth sample config  https://review.openstack.org/14526617:48
notmynameand that happens pretty much just because those other checks come before the dispatch to the OPTIONS method17:48
mahatichmm, i'm looking17:49
notmynamemahatic: ok, for now that's probably all ok. ie as-is the storage node responds to any path in the OPTIONS request17:50
notmynameI don't think there's the requirement to return eg 404 if the object isn't there. that's a HEAD request17:50
notmynamenot OPTIONS17:50
*** lcurtis has joined #openstack-swift17:51
notmynameso "if valid path or *, return 200 OK with the right headers" seems reasonable. and that's what you have. although you didn't specifically code for *, it works17:51
notmynameok, issue 1 taken care of :-)17:51
mahaticnotmyname, as i see now, proxy OPTIONS does not handle much right? It has more to do with CORS?17:52
notmynamerigth17:52
mahatichmm17:52
notmynameand there's _no_way_ we're doing CORS on the storage nodes17:52
mahatic:D nice ;)17:52
notmynametorgomatic may have other feelings on this matter, and we should probably all study the RFC definition for OPTIONS to clarify what do to if the resource isn't found on the server17:52
notmynameok, for the second issue (and in the interest of time, since I have something in 7 minutes)17:53
notmynamethere is one case you aren't handling17:53
mahaticsure, go ahead17:53
notmynamethe allowed_methods should be updated based on the "replication_server" config settion. ie if it's a replication server, a call to non-REPLICATE will respond with HTTPMethodNotAllowed. that needs to be reflected in the Allow header on the OPTIONS response17:55
notmynamecoding that up and testing it, I suspect, will be "fun"*17:55
notmyname* not really17:55
notmynameI think that's what's missing from this patch before it can land17:55
mahaticheh, and I am still comprehending what I should be doing ;)17:56
notmynameI'll add that to gerrit comments17:56
mahaticsure17:56
mahaticnotmyname, I don't know this - so, a replication server will not respond to any headers?17:58
notmynamemahatic: ok, I'll be back online later to offer any clarity needed (or you can ask others here while I'm not around)17:58
mahaticokay17:58
notmynamemahatic: no, a replication server will only handle replication verbs. not normal client-request verbs (PUT/GET/etc)17:58
notmynamemahatic: see http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network17:59
notmynameok, I gotta run. I'll be back for the team meeting in an hour17:59
mahaticnotmyname, great, thanks for the link17:59
mahaticsure17:59
*** geaaru has quit IRC17:59
lcurtishello all...hopefully a few more quick questions as i set up cluster18:07
lcurtisis it possible to have different number of replicas in different region18:07
tdasilvalcurtis: I think you should be able to do that with different storage policies18:08
lcurtisand if we do 3 replicas, for example, can the 3rd replica be in different region18:08
*** acoles is now known as acoles_away18:08
tdasilvalcurtis: check this out: https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/18:09
*** jdaggett_ is now known as jdaggett18:10
lcurtisyes of course...thanks tdasilva...had read this before but it has been a while18:11
lcurtiswill have to revisit18:11
tdasilvalcurtis: I think that should help with the replica in different region question, then you just need to figure out how to deploy your storage policies for different number of replicas18:13
lcurtistdasilva...is this latest doc from swiftstack that you know of?18:13
tdasilvalcurtis: humm...not sure on that one, it was the first that came up on google :-)18:15
lcurtislol18:15
lcurtisright thats why i asked okay...18:15
tdasilvalcurtis: i remember reading it before, not sure if they have a more recent one18:15
lcurtislol...yes me too18:15
lcurtistrying to be the sme as I go... does not always work18:16
lcurtisthanks very much for the link tho...jogged my memory18:16
tdasilvawelcome :)18:17
lcurtisperhaps you know....is it possible to change number of replicas without affecting data18:18
tdasilvalcurtis: not sure I understand your question18:19
tdasilvalcurtis: do you mean you have data that is triple replicated at the moment and you want to reduce to 2x?18:20
lcurtisso is it a very impactful operation to increase replicas on the fly with a larger cluster18:20
lcurtisor vice versa18:20
lcurtisso if we start with 2 and want to go to 318:20
tdasilvahum...never actually tried that to be honest, so you would get a much better answer from the experts18:22
lcurtisyep...scouring documentation today18:23
lcurtisgood to know before we start ingesting tons of data i spose18:23
tdasilvamy guess is that technically it is possible, but it might be impact your cluster pretty heavily for a while...18:23
lcurtisyes indeed18:27
tdasilvalcurtis: just found this: http://docs.openstack.org/admin-guide-cloud/content/section_fractional-replicas.html plus if you are able to set up a dedicated replication network, that could help with lessening the impact on your cluster18:29
*** pberis has quit IRC18:29
lcurtisyes just found that a few minutes ago18:30
lcurtisyou rock18:30
lcurtisthanks fo much for that18:30
*** pberis has joined #openstack-swift18:30
lcurtisi feel a whole lot better for choosing swift for the community alone18:30
*** silor has quit IRC18:31
tdasilvalcurtis: make sure to test changing replica counts in a saio environment first...like I said before I never actually tried this myself...adding to my todo list now :-)18:34
claygnotmyname: my calendar still doesn't work - what time is the swift meeting18:34
lcurtis;) yes indeed...guess we better set up a sandbox real quick18:35
tdasilvaclayg: hi, meeting is in 25 min18:36
*** bkopilov has quit IRC18:41
*** silor has joined #openstack-swift18:42
torgomaticnotmyname: i looked into OPTIONS *, but I couldn't get curl to make such a request, so limiting the path to * makes it annoying to test.18:43
*** annegentle has joined #openstack-swift18:52
*** lihkin has joined #openstack-swift18:53
*** Masahiro has joined #openstack-swift18:53
*** kota_ has joined #openstack-swift18:54
*** acoles_away is now known as acoles18:56
*** bkopilov has joined #openstack-swift18:57
*** cutforth has joined #openstack-swift18:57
*** Masahiro has quit IRC18:58
notmynameclayg: swift meeting is now18:59
notmynametorgomatic: really? curl http://foo/* doesn't work?18:59
*** lihkin1 has joined #openstack-swift19:00
torgomaticNo, that is a path of /*, so the request line is OPTIONS /* HTTP/1.119:01
torgomaticBasically a path not starting with / doesn't fit an URL, so it's really obnoxious to generate such a request.19:01
*** imkarrer has quit IRC19:02
notmynameah ok19:02
*** lihkin has quit IRC19:02
zaitcevok how? I don't understand what Sam is saying.19:02
zaitcevNeeds to drop the slash?19:03
torgomaticI couldn't even get requests (the library) to do it from a repl; that's when I gave up.19:03
zaitcevI see. telnet(1) is too old-school.19:03
zaitcevOkay I'm sorry already19:03
zaitcevjeez19:04
zaitcevMy sinus hurts19:04
zaitcevAnd I called my daugher a "stupid little b*tch" because she did not want to listen to my explanations of proper braking procedures.19:05
zaitcevsomething is not right with my mind19:05
notmynamewow19:05
*** silor has quit IRC19:14
*** annegentle has quit IRC19:20
*** annegentle has joined #openstack-swift19:21
*** itarchitectkev has joined #openstack-swift19:21
itarchitectkevnotmyname, so Swift all works great when keystone is running http, but moving to ssl https I get auth errors. I don't see any ssl errors but could do with finding out how I can debug.19:22
notmynameitarchitectkev: hmmm...interesting19:24
notmynameitarchitectkev: I'm in the swift team meeting right now, but let me know what you've done and what you're seeing19:25
swifterdarrellitarchitectkev: first Q that comes to mind: is everything using "real" or self-signed certs? are you having to do --insecure type stuff?19:25
itarchitectkevnotmyname, no problem. I've only just started to tackle this today so not in any hurry.19:25
itarchitectkevswifterdarrell, self signed certs. is there an --insecure option to some configs in swift?19:26
itarchitectkevcontext: keystone https with self certs work fine with nova, glance, cinder, keystone.19:26
swifterdarrellitarchitectkev: not sure, but my first bet on any problem that shows up with https is cert trust ;)19:27
swifterdarrellitarchitectkev: anyway, it's something to dig into19:27
notmynameitarchitectkev: ya, in the swift CLI you have to tell it that self-signed certs are ok19:27
itarchitectkevyeah, when I was troubleshooting nova stuff and having to use --insecure, I saw SSL errors in the debug. I don't see them with swift --debug19:27
itarchitectkevnotmyname, ah balls. missed that option. still not working, but that implies I've something else wrong.19:28
*** atan8 has joined #openstack-swift19:29
zaitcevthat option is only for client. but authtoken middleware must have something similar19:29
itarchitectkevzaitcev, yeah - in the nova/glance/etc they have an option to do an insecure check. can't see that in swift.19:31
zaitcevhttps://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token.py#L26219:31
cschwedeitarchitectkev: https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L27219:32
cschwedeoh, zaitcev was faster. never mind :)19:32
notmynamehmm...I think I just saw a patch this morning to add docs for keystone options that are currently not documented. maybe that's one?19:32
itarchitectkevbut I'm not seeing ssl errors in the debug.19:33
itarchitectkevcschwede, zaitcev nice. I'll give that a go.19:33
zaitcevour etc/proxy-server.conf.example hasn't got right lines for keystonemiddleware, we need to refresh19:33
zaitcevcan't send people to source all the time like now19:34
acolesnotmyname: that was keystoneauth, this is authtoken19:34
*** mahatic has quit IRC19:34
notmynameoh. ok19:35
acoleswould be neat if we could crossreference the keystonemiddleware config samples rather than maintaining our own19:37
notmynameacoles: "just" port everything to oslo.config. done!19:37
*** dank has joined #openstack-swift19:37
notmyname(don't really do that)19:38
*** mahatic has joined #openstack-swift19:39
*** dkingshott has quit IRC19:41
glangehaha19:43
acolesnotmyname: you gave me like 11 seconds to make a start before retracting your permission :D19:45
*** kota_ has quit IRC19:45
notmyname:-)19:46
notmynameitarchitectkev: meeting done. do you have your next steps? or do you still have outstanding questions?19:46
mattoliveraucschwede: i wonder if we could have a delayed delete option which just sets the X-Delete-After flag to a OP set amount and told the user in the Delete response19:46
*** kota_ has joined #openstack-swift19:48
cschwedemattoliverau: that was my first idea. unfortunately this requires either fast-post, at least a metadata update. i was looking for a „cheap“ option (in terms of replication, traffic, etc)19:48
* torgomatic predicts that delayed-delete will end up with a bad case of scope creep19:48
mattoliveraucschwede: acoles just nees to get fast-post working :P19:48
zaitcevmaybe John can rule delayed-delete with iron fist19:49
zaitcevThe job of PTL is to say "NO"19:49
notmynameNOOOOOOOOOOOOoooooo........19:49
acolesmattoliverau: i'm trying man :S19:49
acolesmattoliverau: will you make hackathon?19:50
mattoliverauacoles: yup, I have approval :)19:50
acolesmattoliverau: cool19:50
torgomaticfirst it's ask an administrator to recover some deleted objects19:51
torgomaticthen it's self-service recovery of deleted objects19:51
torgomaticand then, of course, users will want to list their deleted objects19:51
acolestorgomatic: then its automatic?19:51
mattoliverautorgomatic: lol, so photorec meddleware :P19:51
notmynameit's not automatic. it's torgomatic! (new marketing slogan)19:52
torgomaticand that ignores the question of who pays for storage of deleted objects19:52
mattoliveraulol19:52
torgomaticnot to mention configurable retention periods based on a hundred million different characteristics19:52
*** atan8 has quit IRC19:52
acolesnotmyname: time for a new channel topic? :)19:52
mattoliverau+1 :P19:53
mattoliverauif someone out there wants to make t-shirts for the hackathon: "it's not automatic. it's torgomatic!"19:54
*** ChanServ changes topic to "It's not automatic, it's torgomatic!"19:54
* tdasilva thinks notmyname has new idea for swift shirt19:54
itarchitectkevnotmyname, sorry (kids bedtime here) - yes. I've got stuff to go on. thanks. (thanks zaitcev swifterdarrell).19:54
mattoliverautdasilva: great minds :)19:55
*** kota_ has quit IRC19:55
notmynameitarchitectkev: great!19:55
tdasilvalol19:55
torgomaticand then some bright spark is going to say "hey, why not store all deleted objects using erasure-coding so it's cheap to keep them around?"19:55
mattoliveraulol, and the swift buzz word cycle is complete :P19:56
* cschwede takes notes from torgomatic ideas19:57
itarchitectkevnotmyname zaitcev swifterdarrell -- adding insecure worked. I don't know why I didn't try that originally considering I used that to get over the nova/glance/etc stuff before pointing the in the direction of the certs. *shakes head*19:58
notmynameitarchitectkev: great!19:58
mattoliverauI might go find some breakfast, bbs19:58
acolescschwede: i think we have seen cases where an undelete 'button' would have been very welcome19:59
torgomaticcschwede: just in case you thought it'd be relatively easy ;)19:59
*** acoles is now known as acoles_away20:03
cschwedeacoles_away: yeah, me too. the question is if this feature is accessible by an user or only by an operator20:04
cschwedetorgomatic: hehe, i never thought this will be easy :) so, lot of options, lot of stuff to think about. thanks for your input!20:07
tdasilvacschwede: what do you think of obj. versioning handling deletes?20:07
torgomaticand finally, it'll gain the ability to send an email when a super-important deleted file has only 72 hours of life before expunging... that's how you know the feature is done: it includes sending email ;)20:07
cschwedetdasilva: might be an option too. depends if this is consumable by an end-user? or if an user can enable/disable this (like the current versioning)? in this case there is no protection for credential abuse20:09
cschwedetdasilva: my first idea had operators without any end-users in mind; for example IT departments that use Swift as distributed storage for their applications20:10
notmynamecschwede: new plan. just disable the DELETE verb ;-)20:10
cschwedetorgomatic: oh, easy. we simply integrate an email server into Swift. And to make it more comfortable, also an receiving mail server, so you can send a request by mail ;)20:11
notmynamecschwede: and of course swift will support the full smtp protocol so that it can be a central MTA to store all your mail20:11
torgomaticnow we're talking enterprise quality!20:11
cschwedenotmyname: that was also on my list (disable DELETE), but after some discussions i discarded that20:12
tdasilvacschwede: I guess I need to read up more on ACL to understand what a user could be allowed not allowed to do...20:13
cschwedetdasilva: so, my main idea was that it should be impossible to deactive using the API. Only enable/disable on the storage servers20:14
tdasilvacschwede: i see20:14
*** fandi has quit IRC20:17
*** EmilienM|afk is now known as EmilienM20:25
*** cutforth has quit IRC20:34
*** pberis has quit IRC20:34
*** pberis has joined #openstack-swift20:34
*** fandi has joined #openstack-swift20:36
*** NM has quit IRC20:38
*** annegentle has quit IRC20:39
*** annegentle has joined #openstack-swift20:42
*** Masahiro has joined #openstack-swift20:42
*** Masahiro has quit IRC20:47
*** tdasilva has quit IRC21:01
*** itarchitectkev has quit IRC21:01
*** openstackgerrit has quit IRC21:05
*** openstackgerrit has joined #openstack-swift21:06
*** elambert has quit IRC21:11
*** annegentle has quit IRC21:14
*** NM has joined #openstack-swift21:27
*** elambert has joined #openstack-swift21:32
*** NM has quit IRC21:37
*** NM has joined #openstack-swift21:38
*** annegentle has joined #openstack-swift21:40
*** NM has quit IRC21:41
*** elambert has quit IRC21:46
*** annegentle has quit IRC21:48
*** annegentle has joined #openstack-swift21:49
notmynameCFP for the vancouver summit just opened. deadline is Feb 921:52
notmynamehttps://www.openstack.org/summit/vancouver-2015/call-for-speakers21:52
*** chlong has joined #openstack-swift21:56
*** chlong has quit IRC22:03
*** annegentle has quit IRC22:10
openstackgerritSamuel Merritt proposed openstack/swift: Add notion of overload to swift-ring-builder  https://review.openstack.org/14145222:20
openstackgerritSamuel Merritt proposed openstack/swift: Add dispersion command to swift-ring-builder  https://review.openstack.org/14443222:20
*** Masahiro has joined #openstack-swift22:31
*** Masahiro has quit IRC22:36
*** lpabon has quit IRC22:38
lcurtisanother nagging question...if we have multiple proxy servers, how are they kept consistent in a high load  /volume environment? or is there a quorum leader per se?22:43
notmynamelcurtis: what needs to be consistent between them?22:43
lcurtiswell...where to write data22:44
lcurtisor where an object is stored22:44
notmynamethat's determined by the ring file + math. it's deterministic, so there's no need for the proxies to share state22:44
notmynamethat being said, it's fair to ask what happens when you have 2 proxy servers with different versions of the ring22:45
*** annegentle has joined #openstack-swift22:45
*** elambert has joined #openstack-swift22:46
*** annegent_ has joined #openstack-swift22:46
notmynamein which case, assuming you aren't using radically different rings (ie you're using the included tools and pushing ring files with every rebalance), the ring doesn't change too much from one rebalance to another (it's proportional to the amount of capacity changed)22:46
notmynameand therefore the locations are largely stable22:46
notmynamelcurtis: https://swiftstack.com/blog/2013/02/25/data-placement-in-swift/ and https://swiftstack.com/blog/2012/11/21/how-the-ring-works-in-openstack-swift/22:47
lcurtisyes had started reading22:47
lcurtisnotmyname do you work for swiftstack?22:47
notmynamelcurtis: yes, I do22:48
lcurtisyou are the swift-meistro22:48
lcurtisthanks so much for your guidance22:48
notmynameno more than many others here, but I have been around a while :-)22:49
notmynameclayg: peluse: you'll probably enjoy this talk https://www.usenix.org/conference/osdi14/technical-sessions/presentation/muralidhar  <-- facebook's warm storage. cross-DC erasure codes (RS14,4+XOR)22:50
*** annegentle has quit IRC22:50
*** dmsimard is now known as dmsimard_away22:50
claygnotmyname: yeah thanks22:52
notmynamealso I thought that it's cool that the recording of that talk is hosted in Swift (RAX cloud files) ;-)22:53
*** annegent_ has quit IRC22:54
tacticusnotmyname: nice talk.22:56
*** chlong has joined #openstack-swift23:22
*** elambert has quit IRC23:32
*** elambert has joined #openstack-swift23:32
*** lihkin1 has quit IRC23:33
*** elambert has quit IRC23:37
*** kei_yama has joined #openstack-swift23:39
*** lcurtis has quit IRC23:48
*** km has joined #openstack-swift23:51
*** ho has joined #openstack-swift23:54

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