| *** manous has quit IRC | 00:05 | |
| *** zul has quit IRC | 00:22 | |
| *** zul has joined #openstack-swift | 00:29 | |
| *** zul has quit IRC | 00:33 | |
| *** zul has joined #openstack-swift | 00:38 | |
| *** mingyu has joined #openstack-swift | 01:11 | |
| *** mingyu has quit IRC | 01:16 | |
| *** mingyu has joined #openstack-swift | 01:23 | |
| *** david-lyle has quit IRC | 03:04 | |
| *** nadeem has joined #openstack-swift | 03:30 | |
| *** klrmn has quit IRC | 04:15 | |
| *** abhitechie has joined #openstack-swift | 04:19 | |
| *** mingyu has quit IRC | 04:21 | |
| *** nadeem has quit IRC | 04:32 | |
| *** zhengyin has joined #openstack-swift | 04:37 | |
| *** bjolo has joined #openstack-swift | 04:49 | |
| *** nadeem has joined #openstack-swift | 04:51 | |
| *** bjolo has quit IRC | 05:46 | |
| openstackgerrit | zheng yin proposed openstack/swift: Use more specific asserts in test/unit/common/middleware https://review.openstack.org/342770 | 05:48 |
|---|---|---|
| *** manous has joined #openstack-swift | 05:53 | |
| *** tqtran has joined #openstack-swift | 05:55 | |
| *** tqtran has quit IRC | 05:59 | |
| *** mingyu has joined #openstack-swift | 06:08 | |
| *** mingyu has quit IRC | 06:13 | |
| *** abhinavtechie has joined #openstack-swift | 06:52 | |
| *** abhitechie has quit IRC | 06:55 | |
| *** pcaruana has joined #openstack-swift | 07:01 | |
| openstackgerrit | zheng yin proposed openstack/swift: add test_init case in cli/recon https://review.openstack.org/380813 | 07:19 |
| *** zhengyin has quit IRC | 07:32 | |
| *** manous has quit IRC | 07:45 | |
| *** nadeem has quit IRC | 08:17 | |
| *** abhinavtechie has quit IRC | 08:50 | |
| *** mingyu has joined #openstack-swift | 08:58 | |
| *** mingyu has quit IRC | 09:03 | |
| *** kong has quit IRC | 09:41 | |
| *** mingyu has joined #openstack-swift | 09:55 | |
| *** tqtran has joined #openstack-swift | 09:56 | |
| *** tqtran has quit IRC | 10:01 | |
| *** zhengyin has joined #openstack-swift | 10:10 | |
| *** geaaru has joined #openstack-swift | 10:37 | |
| *** mingyu has quit IRC | 11:16 | |
| *** mingyu has joined #openstack-swift | 11:17 | |
| *** mingyu has quit IRC | 11:22 | |
| *** cnf has joined #openstack-swift | 11:59 | |
| *** mingyu has joined #openstack-swift | 12:02 | |
| cnf | hi, is there any good documentation on running a single node swift instance? | 12:08 |
| cnf | SAIO seems to simulate a 4 node cluster, I just want a single node instance | 12:08 |
| *** zul has quit IRC | 12:24 | |
| *** zul has joined #openstack-swift | 12:27 | |
| *** nikivi has joined #openstack-swift | 12:35 | |
| *** Jeffrey4l_ has quit IRC | 12:38 | |
| *** nikivi has quit IRC | 12:50 | |
| *** david-lyle has joined #openstack-swift | 12:56 | |
| *** Jeffrey4l has joined #openstack-swift | 13:16 | |
| cnf | hmm, I just can't get this thing working :/ | 13:29 |
| cnf | argl, stupid swift >,< I followed the install doc, but I just get a 500 error on port 8080 | 13:39 |
| cnf | no idea why | 13:39 |
| *** tqtran has joined #openstack-swift | 13:58 | |
| *** tqtran has quit IRC | 14:02 | |
| *** zhengyin has quit IRC | 14:30 | |
| *** david-lyle has quit IRC | 14:54 | |
| *** pcaruana has quit IRC | 14:56 | |
| *** oak has joined #openstack-swift | 15:49 | |
| *** david-lyle has joined #openstack-swift | 16:18 | |
| *** david-lyle has quit IRC | 16:23 | |
| *** silor has joined #openstack-swift | 17:47 | |
| *** silor1 has joined #openstack-swift | 17:52 | |
| *** silor has quit IRC | 17:54 | |
| *** silor1 is now known as silor | 17:54 | |
| *** tqtran has joined #openstack-swift | 17:59 | |
| *** tqtran has quit IRC | 18:04 | |
| *** silor has quit IRC | 18:10 | |
| cnf | is it possible to run swift behind an ssl terminating reverse proxy? | 18:31 |
| *** nikivi has joined #openstack-swift | 19:45 | |
| notmyname | cnf: yes. it's common (and strongly recommend) to offload tls termination to some other process | 19:55 |
| cnf | well, i'm not having much luck atm, but I think i'm gonna call it a night | 20:01 |
| *** kong has joined #openstack-swift | 20:04 | |
| *** nikivi has quit IRC | 20:04 | |
| notmyname | cnf: sorry about that. where are you stuck? | 20:06 |
| cnf | I had swift3 working with swauth, mostly | 20:06 |
| notmyname | sorry i didn't catch you earlier. it's sunday in my time zone, and I'm normally not too active in IRC on the weekends (relatively) | 20:06 |
| notmyname | that's cool | 20:07 |
| cnf | no idea how to actually connect to swift itself, though | 20:07 |
| notmyname | you were looking for a single-node setup? | 20:07 |
| notmyname | oh | 20:07 |
| cnf | and I can't get keystone working, at all | 20:07 |
| cnf | yeah, I need a single machine object store | 20:07 |
| notmyname | one machine with a bunch of drives? | 20:07 |
| cnf | one ZFS pool | 20:07 |
| notmyname | ah | 20:07 |
| notmyname | TBH, I wouldn't recommend that. (just as I wound't recommend RAID volumes in swift) | 20:08 |
| cnf | well, the ZFS raid is already there, not much choice in that | 20:08 |
| notmyname | it's generally not a good idea to hide the physical failure domains from swift. means that swift can't make placement and recovery decisions based on that | 20:08 |
| cnf | but as a matter of interest, why not? | 20:08 |
| notmyname | if you've got one machine with ZFS already, why do you need swift? why not stick with zfs? | 20:09 |
| cnf | well, there is only one node, anyway | 20:09 |
| cnf | oh, i'm sticking with ZFS | 20:09 |
| notmyname | swift does data placement across drives, servers, racks, and DCs | 20:09 |
| cnf | I just want to expose an object store to share ome space on it | 20:09 |
| cnf | been looking around like mad finding something that's workable | 20:09 |
| cnf | basically, I just want to expose the ZFS space as some sort of object store API, preferably S3 compatible | 20:10 |
| notmyname | kindof a silly example, but https://github.com/notmyname/swift_on_pi is something I put together a while back to run swift on a raspberry pi. it might give you some hints on the single-server setup (note: in no way do I recommned running swift in prod on a raspberry pi ;-) | 20:11 |
| cnf | I understand it's not really what Swift is made for, but I can't really find anything else, so i'm trying to find out if I can make it work | 20:11 |
| cnf | haha | 20:11 |
| cnf | this is a C2750 8 core avaton with 32G of ECC ram | 20:11 |
| cnf | it's a home setup, but it's not crap :P | 20:11 |
| notmyname | interesting. I've had some coworkers deploy on that before | 20:12 |
| notmyname | you can get some interesting supermicro mini-itx boards with it and have a nice small form factor storage box | 20:12 |
| notmyname | I was looking into it, but currently my eye is on the xeon-d. haven't actually spent the money yet, though ;-) | 20:13 |
| cnf | it's a mini-itx board in a NODE 304 case | 20:13 |
| cnf | oh, the xeon-d is my next home lab purchase | 20:13 |
| cnf | as ESXi node | 20:13 |
| notmyname | cool | 20:13 |
| cnf | to replace / suplement the NUC | 20:13 |
| cnf | you know, I would just run minio, if only minio was multi tenant :/ | 20:14 |
| cnf | or multi-user at least | 20:14 |
| cnf | notmyname: i'm finding openstack in general quite frustrating to work with | 20:15 |
| notmyname | yeah, swift's a pretty nice storage system :-) | 20:15 |
| notmyname | oh, yeah. me too ;-) | 20:15 |
| cnf | finding out what is wrong is just... | 20:15 |
| cnf | idno, like looking for a needle while swimming in pudding | 20:15 |
| notmyname | so back up to what you're looking for. are you just looking for storage you can put on your box to give an s3 api? or do you need other stuff too, like Vm provisioning | 20:16 |
| cnf | oh, atm just an API to my storage | 20:16 |
| notmyname | ok, cool. so no need to look beyond swift for now | 20:17 |
| cnf | the VM's are ESX, so i don't think that'd wok anyway | 20:17 |
| cnf | work* | 20:17 |
| notmyname | are you struggling finding docs/guides or debugging help or just general "what is this and how does it work" info? | 20:17 |
| cnf | a little of all of the above :P | 20:18 |
| cnf | the guides make a lot of assumptions that don't quite fis that I want to do | 20:18 |
| cnf | and then finding the missing info is a nightmare | 20:18 |
| cnf | and when things go wrong, openstack in general isn't good at communicating what is actually wrong | 20:19 |
| cnf | add to that I don't know how half of it is _supposed_ to work :P | 20:19 |
| notmyname | did you see swift.openstack.org? the good news is that theres a good bit of info there. the bad news (spoken as one of the people responsible for writing it) is that it's kinda confused as to the audience. sometimes to end-users (like yourself) and sometimes to contributors (like me) | 20:19 |
| cnf | yeah, I have looked through it | 20:20 |
| notmyname | so you got to the point where you had the code installed, right? just not configured and running successfully? | 20:20 |
| cnf | well, swauth + swift3 was working | 20:21 |
| cnf | in some client | 20:21 |
| cnf | without ssl | 20:21 |
| notmyname | ok | 20:21 |
| notmyname | that's somethign | 20:21 |
| cnf | swauth is rather limiting though | 20:21 |
| cnf | limitED | 20:21 |
| notmyname | ok, we can get to that :-) | 20:21 |
| cnf | also, the S3 api was working, but I have no idea how to talk swift API to it | 20:22 |
| notmyname | you remember the `swift-init` command? | 20:22 |
| cnf | i'm running swift-init all start -v -n | 20:22 |
| cnf | atm | 20:22 |
| notmyname | ok | 20:22 |
| notmyname | that's the thing that starts up all of the swift processes (there's a lot). but the basic idea is that it will start everything that there's a config file for. so if you've got 2 object server configs, it will start 2 object servers. etc | 20:23 |
| cnf | right | 20:23 |
| notmyname | but the basic things you'd need are `swift-init main start` and `swift-init rest start` | 20:23 |
| notmyname | the "main" ones are proxy, account, container, and object server | 20:23 |
| cnf | i have account, container, object and proxy | 20:23 |
| notmyname | that's what handles the API | 20:24 |
| notmyname | the "rest" ones are the background daemons that do consistency checks and handles failures | 20:24 |
| notmyname | and you run that on every server in your cluster (in your case, all one of them) | 20:24 |
| cnf | ^^; | 20:24 |
| notmyname | all your configs are in /etc/swift/* | 20:25 |
| notmyname | so you'll probably have swift.conf and {proxy,account,container,object}-server.conf | 20:25 |
| cnf | indeed | 20:25 |
| notmyname | there's some more complicated stuff it can do, eg having a subfolder with more than one config file in it, but in your case, just one of each should be fine | 20:26 |
| notmyname | all the sample configs are very well commented with sane defaults. they're in the source tree and viewable at https://github.com/openstack/swift/tree/master/etc | 20:27 |
| notmyname | basically, if something's commented out, the default value is given and it's probably ok for you. if it's not commented out, you need to set it to something yourself (eg see the "changeme" values in swift.conf) | 20:28 |
| cnf | uhu | 20:28 |
| notmyname | do you have it up and running and not responding to API requests right now? | 20:29 |
| cnf | I have it in an unknown state | 20:29 |
| notmyname | processes at least running? | 20:30 |
| cnf | oh, yeah | 20:30 |
| cnf | escept for it not finding libshss.so.1 and libisal.so.2, but that doesn't seem to stop it? | 20:31 |
| notmyname | nope. that's fine | 20:31 |
| notmyname | IIRC those warnings were removed if you don't have them installed | 20:31 |
| cnf | ok | 20:31 |
| notmyname | ok, just some basic sanity check, on the server run `swift-recon --validate object` | 20:33 |
| notmyname | also, s/object/container/ and s/object/account/ | 20:34 |
| cnf | 1/1 hosts ok, 0 error[s] while checking hosts. | 20:34 |
| *** Jeffrey4l_ has joined #openstack-swift | 20:34 | |
| notmyname | yay | 20:34 |
| cnf | same for the other 2 | 20:34 |
| notmyname | perfect | 20:34 |
| notmyname | what bind_port are you using in the proxy server? | 20:35 |
| cnf | well ,it's a bit of a special setup, and I'm only using it because some clients I was trying insist on ssl | 20:35 |
| *** Jeffrey4l has quit IRC | 20:36 | |
| cnf | well, only using it now before the rest is working | 20:36 |
| notmyname | ? | 20:36 |
| cnf | I run swift in docker, with the reverse proxy also in docker | 20:36 |
| cnf | but that should not batter | 20:36 |
| cnf | matter | 20:36 |
| notmyname | ok | 20:36 |
| *** ajiang has quit IRC | 20:37 | |
| *** bhakta has quit IRC | 20:37 | |
| notmyname | I was going to walk through getting some basic API stuff working | 20:37 |
| cnf | that could work | 20:37 |
| notmyname | just need to know the port and if you're using auth | 20:37 |
| cnf | it is on port 1237 locally | 20:38 |
| cnf | and the proxy on 443 | 20:38 |
| notmyname | ok | 20:38 |
| *** klrmn has joined #openstack-swift | 20:38 | |
| notmyname | any restrictions on 1237? can we talk to that one before adding in tls? | 20:38 |
| cnf | oh, no atm it's all open | 20:38 |
| notmyname | cool | 20:38 |
| *** ajiang has joined #openstack-swift | 20:39 | |
| notmyname | ok. auth? you're using swauth? | 20:39 |
| *** bhakta has joined #openstack-swift | 20:39 | |
| cnf | I was just trying to use cyberduck to check my sanity | 20:39 |
| cnf | but cyberduck insists on ssl | 20:39 |
| notmyname | ya | 20:39 |
| cnf | yeah, swauth i can get working | 20:40 |
| notmyname | cyberduck insists on some very specific things ;-) | 20:40 |
| notmyname | if so, do you have the default test/tester/testing account set up? | 20:40 |
| cnf | yep | 20:40 |
| notmyname | ok, cool | 20:40 |
| notmyname | now, your call here. want to do it low-level with curl and understand what's going on? or do you want to do slightly higher-level with a CLI? | 20:41 |
| cnf | understanding is good | 20:41 |
| notmyname | yay | 20:41 |
| notmyname | ok, this https://gist.github.com/notmyname/b0678451006086951e75ba47d9749772 | 20:42 |
| notmyname | curl request to get an auth token and storage url | 20:42 |
| notmyname | I give it the username ("test:tester") and the password ("testing") | 20:43 |
| notmyname | and the -i shows the headers on the response | 20:43 |
| *** hoonetorg has quit IRC | 20:43 | |
| notmyname | oh, I'm using 8080. you'll switch to 1237 and whatever ip/host you have | 20:43 |
| cnf | hmm, that gives me internal server error | 20:44 |
| notmyname | ah, ok | 20:44 |
| notmyname | no worries | 20:44 |
| notmyname | see the line 9 on my output? | 20:44 |
| notmyname | the x-trans-id header? | 20:44 |
| cnf | uhu | 20:45 |
| notmyname | grab the value of that ("txace85f6f75c343e196e86-0057f1712asaio" in my case) and grep /var/log/syslog for it. pastebin the result | 20:45 |
| cnf | yeah, no syslog ^^; | 20:45 |
| notmyname | rhel variant? /var/log/messages | 20:46 |
| notmyname | the general answer is "wherever you have the syslog output pointed" | 20:46 |
| cnf | no, no syslog at all | 20:47 |
| cnf | it's not running | 20:47 |
| cnf | but I fixed it | 20:47 |
| notmyname | ok | 20:47 |
| cnf | I had changed the storage paramaters in the swauth web admin thing | 20:47 |
| cnf | i put them back | 20:47 |
| notmyname | ok, then back up and let me know where it breaks or if it's working | 20:48 |
| cnf | the curl command is working now | 20:49 |
| notmyname | oh, cool | 20:49 |
| notmyname | ok, next step then | 20:49 |
| notmyname | two things that are important to pull out of the response | 20:49 |
| cnf | {"storage": {"default": "local", "local": "http://127.0.0.1:1237/v1/AUTH_b4450a14-c618-4a84-83aa-195c68b4e42e"}} | 20:49 |
| cnf | that is actually the thing I had changed | 20:49 |
| cnf | and then put back now | 20:49 |
| cnf | right | 20:49 |
| notmyname | ok | 20:50 |
| notmyname | the other is the auth token | 20:50 |
| cnf | ok | 20:50 |
| notmyname | so this first request was the auth step. we sent the request to the auth system (swuath happens to be running in the same process as the swift proxy, so same ip/port combo, but it could be a totally different system) | 20:50 |
| cnf | right | 20:51 |
| notmyname | ...and the auth system responded with a storage url and a token that's good to talk to that url | 20:51 |
| cnf | so if i want to use keystone auth, I need to proxy keystone as well? | 20:51 |
| notmyname | if you want to use keystone auth, you'll have a keystone instance that you'll talk to separately to get a token. | 20:52 |
| cnf | hmm, ok | 20:52 |
| notmyname | ok, I updated https://gist.github.com/notmyname/b0678451006086951e75ba47d9749772 | 20:52 |
| cnf | so it needs to be reachable from any client? | 20:52 |
| notmyname | ya | 20:52 |
| cnf | right | 20:52 |
| cnf | also, the storage url | 20:52 |
| cnf | mine has a 127.0.0.1 ip | 20:52 |
| notmyname | second file added to the gist shows curl sending the token to the storage url | 20:52 |
| cnf | is that relevant to whetevr client you use? | 20:53 |
| notmyname | sounds like a configuration issue in swauth. but if you fix by hand for the moment, it shoudl still work | 20:53 |
| cnf | ok, I get access denied | 20:55 |
| notmyname | ah, ok. | 20:55 |
| notmyname | somethign with your swauth config is not right | 20:56 |
| cnf | ok | 20:56 |
| notmyname | so eith swift can't talk to swauth or swauth is denying access | 20:57 |
| notmyname | in the proxy-server.conf, what's the pipeline line you have? | 20:57 |
| cnf | pipeline = catch_errors cache swift3 swauth slo dlo proxy-server | 20:58 |
| *** nikivi has joined #openstack-swift | 20:58 | |
| notmyname | where'd you get that from? | 20:58 |
| notmyname | you'll notice that it's *very* different from the sample config | 20:59 |
| cnf | uhm, swift3 and swauth docks | 20:59 |
| notmyname | ah | 20:59 |
| cnf | I only added slo and dlo | 20:59 |
| notmyname | ya | 20:59 |
| cnf | I have no idea what all the plugins do, so i just followed that swauth and swift3 said | 20:59 |
| notmyname | :-) | 20:59 |
| notmyname | trying to think of what's simplest | 21:01 |
| notmyname | the end result I want you to be at is basically using the sample config file | 21:01 |
| notmyname | except with the swauth stuff | 21:01 |
| notmyname | so the structure of the config file is ini-style | 21:02 |
| notmyname | in your config file now, you've got a [filter:swauth] section | 21:02 |
| notmyname | you want to keep that | 21:03 |
| notmyname | and I'm not sure what if any other changes you've made | 21:03 |
| cnf | ha, I kind of lost track :P | 21:03 |
| cnf | it's been a long day | 21:03 |
| notmyname | ok. so make a .bak of your exisitng one, use the sample config file, and add in the sawuth filter section | 21:04 |
| cnf | the one from https://github.com/openstack/swift/tree/master/etc ? | 21:04 |
| notmyname | what version of swift are you using? | 21:06 |
| cnf | mikita | 21:07 |
| * notmyname goes to look at https://wiki.openstack.org/wiki/Swift/version_map | 21:08 | |
| cnf | hmm, so that's not working | 21:08 |
| notmyname | ok, cool. 2.7.0 | 21:08 |
| cnf | what did i do wrong... | 21:08 |
| notmyname | you're using a newer confi file that probably references some recent stuff. like crypto. what did the error message say | 21:08 |
| cnf | LookupError: Entry point 'copy' not found in egg 'swift' (dir: /usr/lib/python2.7/dist-packages; protocols: paste.filter_factory, paste.filter_app_factory; entry_points: ) | 21:08 |
| notmyname | ah ok. so find the "copy" string in the pipeline and delete it | 21:09 |
| notmyname | also, swap tempauth for swauth | 21:09 |
| cnf | ok | 21:10 |
| notmyname | swift-init proxy restart | 21:11 |
| cnf | still get access denied | 21:11 |
| cnf | well, 403 forbidden to be precise | 21:11 |
| notmyname | ok | 21:11 |
| notmyname | set this value to "true" https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L146 | 21:12 |
| cnf | same | 21:13 |
| notmyname | ok, grep the logs for the x-trans-id value | 21:14 |
| * notmyname is hoping swauth may have logged a reason | 21:14 | |
| cnf | nothing specific | 21:14 |
| notmyname | isn't there a swauth cli to add/remove accounts? I havne't looked at swauth in a long time | 21:15 |
| notmyname | check that the user you're using is "admin" (IIRC) | 21:15 |
| notmyname | err...has an admin role or group or something | 21:15 |
| notmyname | don't care what it's named | 21:15 |
| cnf | .admin | 21:16 |
| notmyname | was already there? | 21:17 |
| cnf | yeah | 21:18 |
| notmyname | ok, just for fun, in your proxy pipeline, pull out swauth and add tempauth | 21:18 |
| notmyname | since you're using the sample config, everything should still work just fine. even with test/tester testing | 21:19 |
| cnf | https://gist.github.com/cnf/a5483647af068bef532890ae037ce688 | 21:19 |
| notmyname | yeah. nothing there | 21:20 |
| notmyname | FWIW, log formats are descibed at http://docs.openstack.org/developer/swift/logs.html | 21:20 |
| cnf | ok, now I get a 404 | 21:21 |
| cnf | the first curl query works | 21:22 |
| cnf | the 2nd one gives me a 404 | 21:22 |
| notmyname | I'm trying to remember what that is. | 21:24 |
| *** nikivi has quit IRC | 21:24 | |
| notmyname | what does `swift-ring-builder /etc/swift/account.builder` show you? | 21:25 |
| notmyname | should have some mount points in it that match where your drives are in the system | 21:25 |
| cnf | https://gist.github.com/cnf/a5483647af068bef532890ae037ce688 | 21:26 |
| *** david-lyle has joined #openstack-swift | 21:27 | |
| notmyname | "zfs" is the mountpoint? | 21:27 |
| cnf | yep | 21:27 |
| notmyname | compare with the contianer.builder and object.builder | 21:28 |
| notmyname | the port numbers should all be different (and match the bind_port in the respective config file in /etc/swift) | 21:28 |
| cnf | looks good | 21:29 |
| notmyname | hmm | 21:30 |
| *** david-lyle has quit IRC | 21:31 | |
| cnf | hmz | 21:31 |
| cnf | frustrating | 21:31 |
| notmyname | ya, especially remotely :-) | 21:32 |
| notmyname | permissions in the mountpoint? | 21:32 |
| cnf | swift:swift on all of it | 21:33 |
| notmyname | ok, so swauth gives 403 and tempauth gives 404 | 21:33 |
| cnf | yeah | 21:33 |
| notmyname | double check account_autocreate | 21:34 |
| notmyname | should be true (and uncommented) | 21:34 |
| cnf | yeah... adding doesn't help of you set it to false ^^; | 21:35 |
| cnf | oops | 21:35 |
| cnf | (i has been a long day) | 21:35 |
| cnf | ok, got a 200 now | 21:36 |
| notmyname | yay! | 21:36 |
| notmyname | ok, so more API stuff | 21:38 |
| cnf | :P | 21:38 |
| notmyname | ok, so same token and url: curl -i -H "X-Auth-Token: AUTH_tkee9998acb0b741e7864825bde70faa7c" http://saio:8080/v1/AUTH_test/c -XPUT | 21:38 |
| notmyname | but I acced /c and -XPUT | 21:38 |
| notmyname | to PUT to a new container | 21:38 |
| notmyname | tada | 21:38 |
| notmyname | you now created a container | 21:39 |
| cnf | oh, wait | 21:39 |
| cnf | i spoke too soon | 21:39 |
| notmyname | oh | 21:39 |
| cnf | ok, 204 no content | 21:39 |
| cnf | that's good | 21:39 |
| notmyname | ya | 21:39 |
| notmyname | empty account = 204 | 21:40 |
| cnf | HTTP/1.1 201 Created | 21:40 |
| cnf | so, where does the test in AUTH_test come from? | 21:40 |
| notmyname | curl -i -H "X-Auth-Token: AUTH_tkee9998acb0b741e7864825bde70faa7c" http://saio:8080/v1/AUTH_test/c/foo --data-binary 1234 -XPUT | 21:41 |
| notmyname | to create an object in the container "c" called "foo". the contents are "1234" | 21:41 |
| notmyname | AUTH_test comes from the tempauth (or swauth) config | 21:41 |
| cnf | ok, 201 created | 21:41 |
| notmyname | that's your account in swift. like a bank account, not a use account. it's a place where you put stuff | 21:41 |
| cnf | ok | 21:41 |
| notmyname | and now "curl -i -H "X-Auth-Token: AUTH_tkee9998acb0b741e7864825bde70faa7c" http://saio:8080/v1/AUTH_test/c/foo" | 21:41 |
| notmyname | and you'll download (GET) the object | 21:42 |
| notmyname | you should see 1234 | 21:42 |
| cnf | 200 \o/ | 21:42 |
| notmyname | yay | 21:42 |
| cnf | nice | 21:42 |
| notmyname | ok, the swauth problem was also probably because of the autocreate setting | 21:42 |
| cnf | i think i had that set corrcyly | 21:43 |
| cnf | let me check | 21:43 |
| patchbot | (let <variable> = <value> in <command>) -- Defines <variable> to be equal to <value> in the <command> and runs the <command>. '=' and 'in' can be omitted. | 21:43 |
| cnf | yeah it was account_autocreate = True in the old config | 21:44 |
| cnf | ok, so now tempauth works | 21:45 |
| notmyname | https://bugs.launchpad.net/swift/+bug/1629711 | 21:45 |
| openstack | Launchpad bug 1629711 in OpenStack Object Storage (swift) "change account_autocreate to default to true" [Wishlist,Confirmed] | 21:45 |
| cnf | which is a bit basic :P | 21:45 |
| notmyname | there | 21:45 |
| notmyname | cool, so the basics are working | 21:45 |
| cnf | hehe, nice | 21:45 |
| notmyname | my kid is asking to play rocket league, so I've got to get offline for now | 21:49 |
| notmyname | but definitely feel free to drop by with more questions | 21:49 |
| notmyname | we're pretty well covered in most time zones during the business week | 21:49 |
| cnf | ok, I got swauth workin notmyname | 21:49 |
| notmyname | yay | 21:49 |
| cnf | it was the AUTH_ | 21:49 |
| notmyname | (eg australia and japan are about to come online for their monday) | 21:49 |
| cnf | swauth doesn't use AUTH_TEST | 21:49 |
| cnf | it was AUTH_b4450a14-c618-4a84-83aa-195c68b4e42e | 21:49 |
| notmyname | ah, right | 21:49 |
| cnf | well, it's midnight here | 21:49 |
| cnf | and I have $dayjob tomorrow | 21:50 |
| notmyname | glad it's working for you now | 21:50 |
| cnf | (working with _actual_ openstack, trying to get a bloody compute node to come online | 21:50 |
| notmyname | sorry for the difficulty | 21:50 |
| cnf | well, part one is working | 21:50 |
| cnf | nono, thanks for giving me some insight | 21:50 |
| notmyname | but I want swift to get better. please let me know how | 21:50 |
| cnf | sane debugging! :P | 21:50 |
| cnf | python stack traces aren't useful if you don't know the code | 21:51 |
| cnf | anyway, go play with your kid, thanks for your time | 21:51 |
| notmyname | happy to help | 21:52 |
| *** tqtran has joined #openstack-swift | 22:01 | |
| *** tqtran has quit IRC | 22:05 | |
| *** mingyu_ has joined #openstack-swift | 22:09 | |
| *** mingyu has quit IRC | 22:09 | |
| *** geaaru has quit IRC | 22:34 | |
| *** vint_bra has joined #openstack-swift | 22:40 | |
| *** hoonetorg has joined #openstack-swift | 22:57 | |
| *** kei_yama has joined #openstack-swift | 23:31 | |
| *** zul has quit IRC | 23:42 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!