| *** amit213 has joined #openstack-swift | 00:30 | |
| *** janonymous has joined #openstack-swift | 00:32 | |
| *** tongli has quit IRC | 00:55 | |
| *** klrmn has quit IRC | 00:56 | |
| *** tqtran has quit IRC | 01:25 | |
| *** jaakkos has quit IRC | 01:43 | |
| *** jaakkos has joined #openstack-swift | 01:43 | |
| *** links has joined #openstack-swift | 01:56 | |
| *** tuan_luong has joined #openstack-swift | 02:10 | |
| *** Jeffrey4l has joined #openstack-swift | 02:39 | |
| *** Jeffrey4l_ has joined #openstack-swift | 02:43 | |
| *** tuan_luong has quit IRC | 02:45 | |
| *** Jeffrey4l_ has quit IRC | 03:45 | |
| *** links has quit IRC | 04:05 | |
| *** dmorita has quit IRC | 04:07 | |
| *** dmorita has joined #openstack-swift | 04:14 | |
| *** tqtran has joined #openstack-swift | 04:24 | |
| *** dmorita_ has joined #openstack-swift | 04:25 | |
| *** dmorita__ has joined #openstack-swift | 04:27 | |
| *** dmorita has quit IRC | 04:29 | |
| *** dmorita_ has quit IRC | 04:29 | |
| *** tqtran has quit IRC | 04:29 | |
| *** dmorita__ has quit IRC | 04:36 | |
| *** dmorita has joined #openstack-swift | 04:38 | |
| *** dmorita has quit IRC | 04:41 | |
| *** dmorita has joined #openstack-swift | 04:41 | |
| *** dmorita has quit IRC | 04:43 | |
| *** links has joined #openstack-swift | 05:14 | |
| *** ChubYann has quit IRC | 05:18 | |
| *** dmorita has joined #openstack-swift | 05:19 | |
| *** dmorita has quit IRC | 05:20 | |
| *** dmorita has joined #openstack-swift | 05:24 | |
| *** ChubYann has joined #openstack-swift | 05:32 | |
| *** dmorita has quit IRC | 05:32 | |
| *** dmorita has joined #openstack-swift | 05:36 | |
| *** dmorita_ has joined #openstack-swift | 05:39 | |
| *** dmorita__ has joined #openstack-swift | 05:41 | |
| *** dmorita has quit IRC | 05:41 | |
| *** dmorita has joined #openstack-swift | 05:44 | |
| *** dmorita_ has quit IRC | 05:45 | |
| *** dmorita has quit IRC | 05:46 | |
| *** dmorita has joined #openstack-swift | 05:46 | |
| *** dmorita__ has quit IRC | 05:47 | |
| *** dmorita has quit IRC | 05:48 | |
| *** dmorita_ has joined #openstack-swift | 05:48 | |
| *** mingyu has joined #openstack-swift | 05:52 | |
| *** klrmn has joined #openstack-swift | 05:53 | |
| *** dmorita_ has quit IRC | 05:54 | |
| *** dmorita has joined #openstack-swift | 05:56 | |
| *** klrmn has quit IRC | 05:56 | |
| *** psachin has joined #openstack-swift | 05:57 | |
| *** dmorita has quit IRC | 05:59 | |
| *** tqtran has joined #openstack-swift | 06:17 | |
| *** dmorita has joined #openstack-swift | 06:24 | |
| *** ukaynar has joined #openstack-swift | 06:25 | |
| *** dmorita has quit IRC | 06:29 | |
| *** tqtran has quit IRC | 06:30 | |
| *** ukaynar has quit IRC | 06:49 | |
| *** tesseract has joined #openstack-swift | 07:00 | |
| *** tesseract is now known as Guest37184 | 07:01 | |
| *** tesseract- has joined #openstack-swift | 07:01 | |
| *** Guest37184 has quit IRC | 07:05 | |
| *** silor has joined #openstack-swift | 08:10 | |
| *** silor has quit IRC | 08:13 | |
| *** silor has joined #openstack-swift | 08:16 | |
| *** silor has quit IRC | 09:07 | |
| *** Trixboxer has quit IRC | 09:34 | |
| *** Trixboxer has joined #openstack-swift | 09:35 | |
| *** links has quit IRC | 10:13 | |
| *** dmorita has joined #openstack-swift | 10:21 | |
| *** dmorita has quit IRC | 10:25 | |
| *** ChubYann has quit IRC | 11:13 | |
| *** ChubYann has joined #openstack-swift | 11:14 | |
| *** silor has joined #openstack-swift | 12:10 | |
| *** mingyu has quit IRC | 12:13 | |
| *** dmorita has joined #openstack-swift | 12:37 | |
| *** dmorita has quit IRC | 12:41 | |
| *** silor has quit IRC | 13:13 | |
| *** mingyu has joined #openstack-swift | 13:47 | |
| *** mingyu has quit IRC | 14:02 | |
| *** mingyu has joined #openstack-swift | 14:03 | |
| *** mingyu has quit IRC | 14:22 | |
| *** SkyRocknRoll has joined #openstack-swift | 14:43 | |
| *** mingyu has joined #openstack-swift | 14:44 | |
| *** mingyu has quit IRC | 14:55 | |
| *** McMurlock1 has joined #openstack-swift | 15:24 | |
| *** tesseract- has quit IRC | 15:50 | |
| cnf | how can I see _every_ bucket that is in swift? | 16:22 |
|---|---|---|
| cnf | I made some before, but the users / project that created them are gone | 16:22 |
| cnf | now I can't see (nor delete) them | 16:22 |
| *** klrmn has joined #openstack-swift | 16:29 | |
| *** McMurlock1 has quit IRC | 16:31 | |
| *** dmorita has joined #openstack-swift | 16:38 | |
| *** dmorita has quit IRC | 16:42 | |
| *** silor has joined #openstack-swift | 16:48 | |
| *** silor has quit IRC | 16:52 | |
| *** psachin has quit IRC | 16:54 | |
| *** SkyRocknRoll has quit IRC | 16:58 | |
| *** mingyu has joined #openstack-swift | 17:25 | |
| *** mingyu has quit IRC | 17:29 | |
| cnf | m00 | 17:41 |
| *** mingyu has joined #openstack-swift | 17:55 | |
| *** mingyu has quit IRC | 18:00 | |
| cnf | so can anyone tell me how to see orphaned buckets? | 18:08 |
| *** ukaynar has joined #openstack-swift | 18:20 | |
| *** ukaynar has quit IRC | 18:45 | |
| *** ukaynar has joined #openstack-swift | 18:48 | |
| cnf | no one here, huh? | 18:52 |
| notmyname | cnf: nope | 18:52 |
| cnf | hmm | 18:52 |
| cnf | can't figure out how to claim orphaned containers | 18:53 |
| notmyname | side effect of most people who work on openstack being paid to do so means less IRC coverage on the weekends | 18:53 |
| cnf | and I can't get swift3 working | 18:53 |
| cnf | yeah, or during the week at times when it is useful to me :/ | 18:53 |
| notmyname | heh, we've got several people in the EU. should be some coverage then | 18:53 |
| notmyname | but in answer to your question (then I need to run errands) is that the way to find the containers is to send a GET to the enclosing account | 18:54 |
| notmyname | you'd have to do that for every account to get a list of every container | 18:54 |
| cnf | well, they don't have an account associated with them | 18:54 |
| cnf | that is why they are orphaned | 18:54 |
| notmyname | ah | 18:54 |
| notmyname | how'd you end up with that? | 18:55 |
| cnf | accidentally wiped my keystone database | 18:55 |
| notmyname | oops | 18:55 |
| cnf | it's not a disaster, it's all testing still, but now I do want to figure out how to recover from it | 18:55 |
| cnf | but I just can't find a way to do it | 18:56 |
| cnf | I have data on disk, and no way to access it | 18:56 |
| cnf | or even delete is | 18:56 |
| notmyname | the answer is relatively straightforward, but definitely more in the "advanced" category | 18:57 |
| notmyname | the simple answer is "walk the drives and see what's there". doing that efficiently and dealing with replicas is what's slightly more complicated | 18:57 |
| notmyname | but there's some good news :-) | 18:57 |
| cnf | but everything on there is hashed? | 18:58 |
| notmyname | if you have a utilization trackign system that is based on logs and walking drives (IMO the right way to do it) instead of polling based on eg keystone data, then you can find what you need | 18:59 |
| cnf | uhm | 18:59 |
| notmyname | and i know of such a system that already exists :-) | 18:59 |
| notmyname | https://github.com/notmyname/slogging | 18:59 |
| notmyname | it used to live in swift, then it was extracted and now it lives in my github repo | 18:59 |
| cnf | why was it extracted? | 19:00 |
| cnf | also, I don't really understand how that is related, tbh | 19:00 |
| notmyname | because a utilization system isn't in scope for a storage engine, and we wanted to be able to release each independently as needed. not sure if we'd make the same decision today, but that's the call we made several years ago | 19:01 |
| notmyname | slogging will help because it crawls all the drives in the cluster and reports what it finds. that's the only way to find orphaned stuff | 19:01 |
| cnf | ok | 19:01 |
| notmyname | it can find accounts and containers | 19:02 |
| cnf | hmm, that kinda sucks | 19:02 |
| cnf | any way to reclaim it? or can you only delete it? | 19:02 |
| notmyname | sure. as long as it's associated with some token int eh auth system, the data is perfectly ok | 19:02 |
| cnf | and how do you associate it? | 19:03 |
| notmyname | TBH, I don't know. it would be different for each auth system. I'd imagine you'd "just" add that account name to some keystone user | 19:03 |
| notmyname | cnf: unfortunately, I need to step away now | 19:03 |
| cnf | ah, sure | 19:03 |
| notmyname | good luck | 19:04 |
| cnf | thanks | 19:04 |
| cnf | i might try my swift3 luck some more | 19:04 |
| cnf | or give up for the day | 19:04 |
| notmyname | (of course, the alternative is delete everythign and start over, but that's not necessary. one of the good things about swift is being able to inspect the on-disk data and do something with it | 19:04 |
| cnf | yeah, I don't know how the "do something with it" bit works :P | 19:05 |
| cnf | right, I deleted everything | 19:38 |
| cnf | i got a bit of an idea looking at the sqlite databases... | 19:38 |
| cnf | I guess I could script some python to find hanging ones, and reattach them | 19:38 |
| cnf | but that is an excersise for later | 19:39 |
| cnf | exersise | 19:39 |
| cnf | thingie | 19:39 |
| *** mingyu has joined #openstack-swift | 19:41 | |
| *** mingyu has quit IRC | 19:45 | |
| *** ndk has quit IRC | 19:59 | |
| *** ndk_ has joined #openstack-swift | 20:00 | |
| ahale | yeah the "do something with it" bit can get terrifying sometimes, sometimes the craziest ideas you end up with are the best. but like notmyname implies, swift at least gives you that chance where you might otherwise be lost or dependant on vendors | 20:11 |
| cnf | uhu | 20:13 |
| cnf | i have put it off for a "learn later" | 20:13 |
| cnf | i need to get more comfortable with the rest of it, first | 20:13 |
| cnf | but I did see it's all just sqlite, so that can't be too hard to script against | 20:13 |
| cnf | ahale: you don't have a working swift3 setup by any chance? :P | 20:14 |
| cnf | timburke: was helping me last time, but he needed to go | 20:14 |
| ahale | afraid not, im rackspace so i only know the old stuff that we support | 20:14 |
| *** nikivi has joined #openstack-swift | 20:14 | |
| cnf | ah, ok | 20:15 |
| cnf | it seems keystone needs some stuff enabled for it to work | 20:15 |
| cnf | but I can not find any references to it | 20:15 |
| ahale | yeah those are both things i now nothing at all about | 20:16 |
| cnf | ^^; | 20:16 |
| ahale | the trawling, inspecting on disk stuff is something im trying to work on at the moment for a problem i have in one of my clusters, not so much orphaned data, but some bad in another similar way | 20:21 |
| cnf | uhu | 20:21 |
| ahale | its hard because it can feel overwhelming, but good because its normally kind of simple to script and deal with stuff programaticallly, and get things to a state where swift can get itself going again | 20:22 |
| *** nikivi has quit IRC | 20:22 | |
| cnf | uhu | 20:22 |
| cnf | openstack in generally is rather overwhelming | 20:22 |
| cnf | been trying to get the hang of it for 3 weeks now | 20:22 |
| cnf | and I still barely know what I am doing :P | 20:22 |
| ahale | hehe yeah i have been doing it for 6 years and still have no idea outside the pure-swift world really | 20:23 |
| cnf | haha | 20:23 |
| *** ukaynar has quit IRC | 20:24 | |
| cnf | eh, $currentemployer is willing to pay me my day rate to let me play with openstack | 20:24 |
| cnf | i'm not complaining :P | 20:24 |
| *** nikivi has joined #openstack-swift | 20:24 | |
| ahale | nice | 20:24 |
| ahale | i kind of wish i had had more exposure to the other parts, but being in a largish cloud, we have a lot of teams with very limited scope | 20:26 |
| cnf | uhu | 20:27 |
| cnf | well, I think Swift is the one component that works stand-alone | 20:27 |
| ahale | absolutely | 20:27 |
| cnf | though it could use a better auth backend apart from keystone for that | 20:27 |
| ahale | yah, we run swauth and a custom kinda keystone thing, but thats somebodyelsesproblem | 20:28 |
| cnf | haha | 20:29 |
| cnf | swauth is just a tad basic | 20:29 |
| cnf | though not too bad | 20:30 |
| cnf | does need moar docs, though :P | 20:30 |
| ahale | yeah , i mean we probably benefited from having the guy who wrote it on our team at the time ;) and only use it for internal stuff, storing logs, processing slogging type stuff | 20:31 |
| cnf | uhu | 20:32 |
| ahale | from being mostly swift - i kinda feel that some of the other openstack projects like keystone are sometimes a little over complicated- lots of moving parts | 20:32 |
| cnf | oh, you are not kidding... | 20:33 |
| cnf | and such a pain to debug, never any useful debug info | 20:33 |
| cnf | though swift has that problem a bit, as well | 20:33 |
| ahale | i've heard that a couple of times about swift from people but havent really felt it myself | 20:34 |
| ahale | have you got any examples of situations that were hard? cos whenever ive had chance to dev input stuff i normally think its ok | 20:34 |
| cnf | probably because you already know it well | 20:35 |
| cnf | but python stack traces don't really help when you don't know how the project works that well | 20:35 |
| ahale | do you think its lack of meaningful error messages, or lack or docs on architecture basics and stuff | 20:36 |
| cnf | well, both really | 20:36 |
| cnf | well, no, lack of docs, is not entirely right | 20:36 |
| cnf | there are SO many docs, they are all over the place | 20:37 |
| ahale | meaningful docs for operators | 20:37 |
| ahale | ahh | 20:37 |
| cnf | and yes, it lacks meaningful error messages | 20:37 |
| cnf | I would like more docs that explain how things work | 20:37 |
| cnf | mind, this really isn't just swift, most other OS projects are much worse | 20:38 |
| ahale | things like how a request flows throuh the different layers and wsgi apps, how things can go wrong? | 20:38 |
| cnf | yeah, that's a good example | 20:38 |
| cnf | when things go wrong, there is little help | 20:38 |
| cnf | and it doesn't have to be holding hands type of docs, but a "this is how the flow is, and this bit you can read up on here, and this here" | 20:39 |
| ahale | yeah , holding your hand through everything would be impossible - but there does feel a lack of things to equip people with knowing where to start, how to break down a problem | 20:40 |
| cnf | like, for example | 20:40 |
| cnf | i have been looking at swift3 for DAYS now | 20:40 |
| ahale | (i have a few newish team members who are starting to take over looking at our prod stuff so this is really interestng to me) | 20:41 |
| cnf | i _think_ the problem might be that swift3 calls v2 of the api | 20:41 |
| cnf | which is depricated, and as such disabled | 20:41 |
| cnf | no idea if this is true, or where to "fix" this, or anything | 20:41 |
| cnf | but that should not take days to figure out ^^; | 20:41 |
| cnf | well, maybe i'm just slow, but still | 20:42 |
| ahale | :) yeah no that shouldnt take days - something in the stack should be emitting a clear error somewhere | 20:42 |
| ahale | should as in ideally should, not should as in "you did configs wrong" | 20:43 |
| cnf | yeah | 20:43 |
| cnf | so yeah, I find the documentation needed for debugging to rather slim | 20:43 |
| ahale | its interesting that you mentioned both swift3 and also swauth as lacking on the docs, as they both used to be core swift code | 20:44 |
| cnf | hmm, so yeah | 20:44 |
| cnf | i'm wrong | 20:44 |
| cnf | it's not the api version | 20:44 |
| cnf | i think? | 20:44 |
| cnf | no occurance of s3token in the keystone code | 20:44 |
| cnf | but it needs to respond to a call to /v2.0/s3token | 20:45 |
| cnf | o,O | 20:45 |
| cnf | i don't understand this | 20:45 |
| ahale | oO that sounds super weird | 20:45 |
| cnf | yeah :/ | 20:45 |
| ahale | like keystone shouldnt need to know anything about anything s3 | 20:45 |
| cnf | well, swift3 is calling keystone on /v2.0/s3token | 20:46 |
| cnf | i dno why | 20:46 |
| cnf | and I found an OLD post that say something about it | 20:46 |
| ahale | i'd have figured the swift3 middlware would handle all that and make keystone reqs back - and that you were probably on the right track assuming it was a version thing - that keystone would move faster than the out-of-tree s3 code | 20:46 |
| ahale | but like i said i know nothing about that stuff :) | 20:46 |
| cnf | damn, I lost the link | 20:46 |
| *** ukaynar has joined #openstack-swift | 20:49 | |
| timburke | cnf: on for a bit -- the keystone side is in https://github.com/openstack/keystone/blob/master/keystone/contrib/s3/core.py which gets exposed as a paste filter_factory named "s3_extension" | 20:50 |
| cnf | hey timburke | 20:50 |
| cnf | and that exposes /v2.0/s3token ? | 20:50 |
| cnf | and I have | 20:50 |
| cnf | sec | 20:50 |
| timburke | so somewhere there should be a paste pipeline definition similar to what's going on in swift's proxy-server.conf | 20:50 |
| cnf | yeah, I do | 20:51 |
| cnf | timburke: http://paste.openstack.org/show/585000/ | 20:51 |
| timburke | yeah; it can actually be exposed as either /v2.0/s3tokens or /v3/s3tokens, but swift3 hardcodes the v2.0 :( | 20:51 |
| cnf | it's not in my domain config files, though, is that needed? | 20:52 |
| *** nikivi has quit IRC | 20:52 | |
| timburke | not sure; i'm not familiar enough with setting up keystone | 20:52 |
| cnf | hmm | 20:53 |
| cnf | I really don't understand this | 20:53 |
| cnf | keystone just gives me a 404 when I hit /v2.0/s3token (or v3/s3token) | 20:53 |
| timburke | "s3token" or "s3tokens"? | 20:53 |
| cnf | neither work | 20:54 |
| timburke | you'll also want to make sure you're doing POST requests; from experimenting, GETs will 404 | 20:54 |
| cnf | ah | 20:54 |
| cnf | ok, a POST gives me a 400 | 20:55 |
| timburke | something like `curl -v http://keystone-server/v2.0/s3tokens -X POST` should respond with a 400 instead | 20:55 |
| timburke | yeah, nice | 20:55 |
| cnf | INFO eventlet.wsgi.server [req-0cf736ea-9537-49f3-8037-64e5cbe81af7 - - - - -] 172.17.0.1,172.17.0.1 - - [08/Oct/2016 20:56:29] "POST /v2.0/s3tokens HTTP/1.1" 404 318 0.023016 | 20:55 |
| cnf | is my keystone log | 20:55 |
| cnf | wt... | 20:56 |
| cnf | now I am really confusef | 20:56 |
| cnf | d | 20:57 |
| timburke | that's...strange... hmm | 20:59 |
| cnf | and it's also not noted in the API docs | 20:59 |
| timburke | did it at least mention your 400? | 20:59 |
| cnf | >,< | 20:59 |
| cnf | yeah, the 400 gives me a nice stack trace | 20:59 |
| cnf | ERROR keystone.common.wsgi TypeError: argument of type 'NoneType' is not iterable | 21:00 |
| cnf | ahale: example of "not useful debug info :P | 21:00 |
| patchbot | Error: No closing quotation | 21:00 |
| ahale | ugh | 21:00 |
| cnf | how the hell can one request give a 404, and the other a 400 on the same bloody path? o,O | 21:01 |
| cnf | pardon me, but i'm a bit frustrated | 21:01 |
| timburke | so, funny story: apparently something like `curl -v http://keystone/v2.0/s3tokens -X POST -H content-type:application/json -d '{"credentials": {"signature": "", "access": "", "token": ""}}'` will 404! with a message like "Could not find credential: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855" | 21:03 |
| timburke | *no idea* where that came from, but w/e | 21:03 |
| cnf | o,O | 21:03 |
| cnf | what... | 21:03 |
| cnf | the... | 21:03 |
| cnf | actual... | 21:03 |
| cnf | ahale: another example of _really_ bad debug info? :P | 21:04 |
| cnf | timburke: ok, so i'm just not using the right credentials? | 21:04 |
| timburke | sending a legit credential (instead of blank) gets me a 401 | 21:04 |
| cnf | ok, then I have no idea how to construct the right credentials for s3 | 21:04 |
| timburke | i think maybe? what's your access_key? is it the keystone user name, or the crazy hex "Access" thing from keystone? | 21:05 |
| *** geaaru has joined #openstack-swift | 21:05 | |
| ahale | wow that 404 is kind of awesome tim | 21:06 |
| cnf | I have no idea... | 21:06 |
| cnf | timburke: i am using the "access" thing from `openstack ec2 credentials show name` | 21:06 |
| cnf | user_id also doesn't work | 21:07 |
| cnf | hmm | 21:08 |
| timburke | yeah, keystone generates some separate id instead of the user_id. i guess so you could have multiple credentials per user? | 21:08 |
| cnf | I think so? | 21:08 |
| cnf | but I can't get any working | 21:08 |
| cnf | I don't know which one I am supposed to use | 21:09 |
| timburke | i'd expect the access to work :-/ mind trying a curl like what i sent above, but pasting in your access id in the appropriate place? | 21:12 |
| cnf | what do I use for signture? | 21:13 |
| timburke | leave it blank; we'll see if it 401s or 404s | 21:14 |
| cnf | 404 | 21:15 |
| cnf | with signature blank | 21:15 |
| cnf | uhm, no | 21:16 |
| cnf | 401 | 21:16 |
| timburke | yay! i like 401s! | 21:16 |
| cnf | HTTP/1.1 401 Unauthorized | 21:16 |
| cnf | hmm, weird | 21:18 |
| cnf | so 1) why is is unauthorized, and 2) why is what swift3 is sending not found? | 21:18 |
| timburke | if you've got debug logging on in the proxy, i think we'll see the access credential that's sent to keystone | 21:20 |
| timburke | the unauthorized is because we provided a blank signature, which can't match | 21:21 |
| timburke | if you wanted to generate a signature to send, you could do something like `python -c "import hmac, hashlib; print hmac.new('<your secret>', '', hashlib.sha1).digest().encode('base64')"` | 21:22 |
| timburke | which should get you a 200 with a blank token | 21:23 |
| cnf | then I have to sign my secret with it, no? | 21:26 |
| cnf | ok, can I just say "wtf" now? | 21:27 |
| cnf | timburke: so when I do a call against swift with an s3 client, I get a log entry saying Connecting to Keystone sending this JSON: | 21:28 |
| cnf | and then the json with all the values | 21:28 |
| cnf | if I send that EXACT json, I get a 200 | 21:28 |
| cnf | swift gets a 404 | 21:28 |
| cnf | o,O | 21:28 |
| timburke | wha-? | 21:28 |
| cnf | uuuuuuhu... | 21:29 |
| timburke | maybe double check the ports? dns resolution? try curling from the proxy? | 21:29 |
| cnf | curl from the proxy gets me a 200 | 21:30 |
| cnf | oh, hmm | 21:30 |
| cnf | wt? | 21:32 |
| cnf | ok, so | 21:32 |
| cnf | if I curl | 21:32 |
| cnf | I see a INFO keystone.common.wsgi [req-37d4d40a-d702-4d50-a7a8-95a8c2eeb7c0 - - - - -] POST http://<dns.entry>:35357/v2.0/s3tokens | 21:33 |
| cnf | and then a NFO eventlet.wsgi.server [req-37d4d40a-d702-4d50-a7a8-95a8c2eeb7c0 - - - - -] 172.17.0.1 - - [08/Oct/2016 21:33:28] "POST /v2.0/s3tokens HTTP/1.1" 200 2111 0.230437 | 21:33 |
| cnf | the one from swift does NOT show the keystone.common.wsgi entry | 21:33 |
| timburke | bbiab, gotta move laundry | 21:36 |
| cnf | ok, and I have found something | 21:37 |
| *** ukaynar has quit IRC | 21:38 | |
| cnf | yeah... that is stupid... | 21:39 |
| *** ukaynar has joined #openstack-swift | 21:43 | |
| *** geaaru has quit IRC | 21:56 | |
| *** tries_ has quit IRC | 22:04 | |
| *** tries_ has joined #openstack-swift | 22:16 | |
| cnf | timburke: got it working | 22:43 |
| cnf | ok, now how do container permissions work... | 22:44 |
| *** Raymii has quit IRC | 23:01 | |
| *** Raymii has joined #openstack-swift | 23:05 | |
| *** Nype has joined #openstack-swift | 23:11 | |
| Nype | Hello, Is it possible to have access logs (with IP etc) files hosted with swift? | 23:12 |
| cnf | Nype you want access logs OF swift, or store access logs of something else IN swift? | 23:12 |
| cnf | Nype: ? | 23:18 |
| Nype | I want access logs of swift | 23:35 |
| Nype | sorry for time answer :s | 23:35 |
| cnf | use the swift-proxy access logs? don't you run it on apache or something? | 23:40 |
| Nype | I use swift throught OVH, should I contact them to know if i can have an acces to these logs ? | 23:42 |
| cnf | oh, it's not your own swift install? | 23:43 |
| Nype | nope, it's like amazon s3 based on openstack swift | 23:44 |
| cnf | and you want access logs from that? | 23:44 |
| Nype | i pay per GB/month and GB out of trafic | 23:45 |
| cnf | you should ask them, I guess | 23:45 |
| notmyname | Nype: yeah. if you aren't running the cluster yourself, you'll have to ask your provider for them. eg rackspace has that feature. not sure if ovh does. | 23:45 |
| *** ukaynar has quit IRC | 23:45 | |
| cnf | ohai notmyname | 23:45 |
| cnf | i got swift3 working | 23:45 |
| * notmyname isn't here ;-) | 23:45 | |
| Nype | i want theses logs to have a lot of stats mainly | 23:45 |
| Nype | ok thank you guys, i'll contact them | 23:45 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!