Wednesday, 2014-06-25

*** mwstorer has quit IRC00:09
*** annegent_ has joined #openstack-swift00:15
*** kota_ has joined #openstack-swift00:16
*** kevinc_ has quit IRC00:20
*** annegent_ has quit IRC00:20
*** dmorita has joined #openstack-swift00:32
*** matsuhashi has joined #openstack-swift00:35
*** pconstantine_ has quit IRC00:35
openstackgerritSteven Lang proposed a change to openstack/swift: Modify the object services to report their full service name.  https://review.openstack.org/10240100:47
*** shri has quit IRC00:49
openstackgerritSteven Lang proposed a change to openstack/swift: Modify the object services to report their full service name.  https://review.openstack.org/10240101:08
*** annegent_ has joined #openstack-swift01:16
openstackgerritSteven Lang proposed a change to openstack/swift: Modify the object services to report their full service name.  https://review.openstack.org/10240101:20
*** annegent_ has quit IRC01:21
*** nosnos has joined #openstack-swift01:51
*** nosnos has quit IRC01:56
*** nosnos has joined #openstack-swift01:57
openstackgerritKota Tsuyuzaki proposed a change to openstack/swift: Efficient Replication for Distributed Regions  https://review.openstack.org/9982401:59
mlannerpeluse_: notmyname: 5 are up and running. there are some "interesting" problems that we have discovered and are trying to work through, but it's not stopping us from using the systems right now.02:02
*** kota_ has quit IRC02:10
*** cm2 has quit IRC02:14
*** nsquare has quit IRC02:30
*** openstackgerrit has quit IRC02:31
*** baojg has joined #openstack-swift02:33
*** kota_ has joined #openstack-swift02:35
*** mitz_ has joined #openstack-swift02:36
*** kota_ has quit IRC02:39
*** kota_ has joined #openstack-swift02:39
*** annegent_ has joined #openstack-swift02:42
*** annegent_ has quit IRC02:46
*** fifieldt_ is now known as fifieldt02:47
*** baojg has quit IRC02:56
*** haomaiwa_ has joined #openstack-swift02:56
*** baojg has joined #openstack-swift02:56
mlannerpeluse_: who knows most about those avoton boxes? the BIOS kinda acts a bit wacky for some things. there are settings that just seem to be missing. do you know who i can contact to check for the latest BIOS version?02:59
*** jyoti_ranjan has joined #openstack-swift03:28
*** matsuhashi has quit IRC03:42
*** zaitcev has quit IRC03:43
*** matsuhashi has joined #openstack-swift03:43
*** matsuhashi has quit IRC03:47
*** zhiyan_ is now known as zhiyan03:49
*** nosnos has quit IRC03:51
*** Anticimex has quit IRC03:57
*** Kbee has joined #openstack-swift03:58
*** baojg has quit IRC04:04
*** annegent_ has joined #openstack-swift04:16
*** annegent_ has quit IRC04:21
*** baojg has joined #openstack-swift04:22
*** matsuhashi has joined #openstack-swift04:31
*** nosnos has joined #openstack-swift04:37
*** ppai has joined #openstack-swift04:40
*** kopparam has joined #openstack-swift04:46
*** judd7 has quit IRC04:49
*** judd7_ has quit IRC04:49
*** judd7 has joined #openstack-swift04:50
*** judd7_ has joined #openstack-swift04:51
*** mmcardle has joined #openstack-swift04:51
*** bkopilov has joined #openstack-swift04:56
*** ajc_ has joined #openstack-swift04:59
*** mmcardle has quit IRC05:01
*** gyee has quit IRC05:02
*** baojg has quit IRC05:02
*** baojg has joined #openstack-swift05:02
*** mmcardle has joined #openstack-swift05:03
*** baojg has quit IRC05:04
*** baojg has joined #openstack-swift05:04
*** kota_ has quit IRC05:08
*** mmcardle has quit IRC05:13
KbeeHello,  is there a way to choose handoff nodes, or is it upto swift-ring-builder to automagically choose handoff node depending on nodes and devices and replica count?05:14
*** annegent_ has joined #openstack-swift05:16
*** psharma has joined #openstack-swift05:16
*** annegent_ has quit IRC05:21
*** ppai has quit IRC05:24
*** ppai has joined #openstack-swift05:24
*** nsquare has joined #openstack-swift05:26
Kbeenotmyname, is there a way to choose handoff nodes, or is it upto swift-ring-builder to automagically choose handoff node depending on nodes and devices and replica count?05:27
mattoliverauHey Kbee, that is done by the ring, though you do have some say, when you add a device to the ring you can specify a weight, when you define regions you can also define a weight.05:30
mattoliverauKbee: the hand off nodes are determined by the hash and part power, this devided in to partitions and partitions are placed on different devices.05:32
mattoliverauKbee: you can have a little more control by using storage policies as you can create a new object ring that only uses a particular set of devices.05:33
Kbeemattoliverau, Thanks. so if there are 3 storage nodes and 3 replicas,  single zone, there wont be any handoff nodes right.. since the uniquely as possible algo uses three nodes to place data05:35
mattoliverauKbee: yes, if there only 2 storage nodes and 3 replicas all in one zone, then the hand off nodes would be all of them :)05:36
Kbeemattoliverau, Awww.. :) .. i need to dig into code i believe to get this :)05:37
mattoliverauKbee: there is a list-endpoints middleware you can add to your proxy server which will tell you which nodes an object is stored on.05:38
Kbeemattoliverau, if there are 5 servers and 3 replicas and 1 zone does ring leave the 2 object servers untouched and distribute partitions only on 3 servers.. and use the rest 2 only when something breaks on other 3 ?05:41
mattoliverauKbee: nope.. and kinda :P05:42
mattoliverauKbee: swift will use all 5 nodes for storage05:42
mattoliverauKbee: with 3 replica's each file written will be written to 3 of the nodes05:42
mattoliverauKbee: So here is a very high overview of the ring.. I'll find you the docs on it in a sec, so you can proove me wrong :P05:43
*** kota_ has joined #openstack-swift05:43
mattoliverauKbee: swift does and md5sum of the requrested filename 'account/container/object'05:44
mattoliverauKbee: when you define a part power, this determines how much of the md5sum to use as a mask to now where to look in the ring.05:45
Kbeemattoliverau, correct.. thats evident05:45
mattoliverauKbee: this points to partition number. so there are 2^part_power partitions.05:46
mattoliverauKbee: when the ring is build these partitions are assigned to 3 nodes.05:47
mattoliverauKbee: or should I say replacount number of nodes.05:47
Kbeemattoliverau, OK.. .. replica-count nodes..05:47
mattoliverauKbee: because it is based off the hash the objects should be neatly, or hopefully balanced across all 5 nodes (in your example above).05:48
mattoliverauKbee: but each object is on a <replica count> number of servers, but different objects could be on any of the 505:49
mattoliverauKbee: does that make sense or have I talked nonsesnse :P I'll find the documentation hold on :)05:50
Kbeemattoliverau,  hmmm.. then hows hand-off calculated.. so its more of hand-off node for each object deployed rather than hand-off node.. :) rit ? Yes pls.. could not find something on net digging on this05:53
*** ktsuyuzaki has joined #openstack-swift05:54
mattoliverauKbee: I haven't watched this, but quickly skimmed it so this might help: https://swiftstack.com/blog/2012/11/21/how-the-ring-works-in-openstack-swift/05:55
*** ktsuyuzaki is now known as kota__05:55
mattoliverauthere is the swift documentation: http://docs.openstack.org/developer/swift/ring.html05:55
*** kota_ has quit IRC05:56
mattoliverauKbee: this might be somewhat useful as well: https://swiftstack.com/blog/2013/02/25/data-placement-in-swift/05:57
Kbeemattoliverau, i have gone through all :).. in the last one-data placement swift - the diagram shows that if there are 4 serves , data is always placed on 3 and the rest is not used at all and this may be used for handoff.. this was the question..05:59
*** chandan_kumar has quit IRC06:00
*** kota_ has joined #openstack-swift06:02
*** kota__ has quit IRC06:04
*** ktsuyuzaki has joined #openstack-swift06:09
mattoliverauKbee: oh sorry, I must have miss understood. If there is a failure then the it will move the partition (or partitions) on the broken device and move data, it will choose using the same algorithm it  initially uses (to keep it distributed).06:11
*** kota_ has quit IRC06:11
mattoliverauKbee: this might be of more use then: http://mirror.linux.org.au/linux.conf.au/2013/mp4/Playing_with_OpenStack_Swift.mp406:11
mattoliverauKbee: here notmyname goes over swift automotic revovery.06:12
mattoliverauKbee: There was a blueprint around being able to specify hand off nodes. But not sure where that is at, or if it's even going forward.06:13
*** ktsuyuzaki has quit IRC06:13
*** kota_ has joined #openstack-swift06:15
Kbeemattoliverau, i did some digging now using swift-get-nodes and by it, handoff nodes are pre decided .. and if there are number of drives > number of replicas, rest are used as hand offs.. here's o/p -> http://paste.openstack.org/show/84853/06:15
*** annegent_ has joined #openstack-swift06:16
Kbeemattoliverau, i.e it always stores on 3 nodes, and rest are not used :)06:17
Kbeemattoliverau, or stores on replica-count nodes and rest are handoff06:17
Kbeemattoliverau, i had checked that bluprint.. thats abandoned - https://review.openstack.org/#/c/5609/06:19
*** annegent_ has quit IRC06:21
*** pconstantine_ has joined #openstack-swift06:22
Kbeemattoliverau, now i get.. for each partition, you have handoff nodes assigned on disks spanning the entire nodes .. and this is predecided during ring creation and cant be specified manually :)06:24
mattoliverauKbee: cool, nice work, now we have both learnt something! I should thank you :)06:25
Kbeemattoliverau, Thank you.. should have got hold of that command bfor asking here :)06:26
*** nsquare has quit IRC06:28
mattoliverauKbee: lol, no it benefitted me as much as you, so I'm glad you didn't :)06:28
Kbeemattoliverau, no definitely i did.. Thanks..06:29
*** nsquare has joined #openstack-swift06:30
Kbeemattoliverau, no definitely it did benefit.. Thanks..06:30
*** nsquare has quit IRC06:31
*** nsquare has joined #openstack-swift06:37
*** psharma_ has joined #openstack-swift06:42
*** psharma__ has joined #openstack-swift06:45
*** psharma has quit IRC06:45
*** psharma_ has quit IRC06:49
*** psharma_ has joined #openstack-swift06:52
*** psharma__ has quit IRC06:55
*** ppai has quit IRC06:57
*** ktsuyuzaki has joined #openstack-swift06:58
*** kota_ has quit IRC07:00
*** kota_ has joined #openstack-swift07:03
*** judd7_ has quit IRC07:03
*** judd7 has quit IRC07:03
*** judd7 has joined #openstack-swift07:05
*** judd7_ has joined #openstack-swift07:05
*** ktsuyuzaki has quit IRC07:05
*** judd7 has quit IRC07:05
*** judd7_ has quit IRC07:05
*** kopparam has quit IRC07:07
*** kopparam has joined #openstack-swift07:08
*** shausy has joined #openstack-swift07:10
*** ktsuyuzaki has joined #openstack-swift07:12
*** kopparam has quit IRC07:12
*** ppai has joined #openstack-swift07:12
*** judd7 has joined #openstack-swift07:12
*** judd7_ has joined #openstack-swift07:12
*** kota_ has quit IRC07:13
*** kota_ has joined #openstack-swift07:16
*** nsquare has quit IRC07:16
*** annegent_ has joined #openstack-swift07:16
*** ktsuyuzaki has quit IRC07:18
*** ktsuyuzaki has joined #openstack-swift07:19
*** ktsuyuzaki has quit IRC07:19
*** kota_ has quit IRC07:20
*** mmcardle has joined #openstack-swift07:22
*** joeljwright has joined #openstack-swift07:22
*** annegent_ has quit IRC07:23
*** ppai has quit IRC07:30
*** dANOKELOFF has joined #openstack-swift07:42
*** ppai has joined #openstack-swift07:47
*** kopparam has joined #openstack-swift07:47
*** baojg has quit IRC07:48
*** baojg has joined #openstack-swift07:49
*** baojg has quit IRC07:49
*** baojg has joined #openstack-swift07:49
*** kopparam has quit IRC07:52
*** judd7 has quit IRC07:52
*** judd7_ has quit IRC07:52
*** judd7 has joined #openstack-swift07:54
*** judd7_ has joined #openstack-swift07:54
*** matsuhashi has quit IRC07:57
*** matsuhashi has joined #openstack-swift07:58
*** baojg has quit IRC08:04
*** kopparam has joined #openstack-swift08:05
*** jyoti_ranjan has quit IRC08:05
*** matsuhashi has quit IRC08:05
*** kopparam has quit IRC08:08
*** kopparam has joined #openstack-swift08:09
*** matsuhashi has joined #openstack-swift08:10
*** baojg has joined #openstack-swift08:14
*** annegent_ has joined #openstack-swift08:16
*** matsuhashi has quit IRC08:17
*** matsuhashi has joined #openstack-swift08:18
*** pconstantine_ has quit IRC08:20
*** annegent_ has quit IRC08:21
*** matsuhashi has quit IRC08:31
*** Ju_ has quit IRC08:34
dANOKELOFFHi, anyone can help me with this error please ? https://gist.github.com/anonymous/eb6880e973b2baf1206608:40
*** mkollaro has joined #openstack-swift08:45
*** nosnos has quit IRC08:45
*** openstackgerrit has joined #openstack-swift08:52
*** dmorita has quit IRC09:02
*** annegent_ has joined #openstack-swift09:16
*** annegent_ has quit IRC09:21
*** haomaiwa_ has quit IRC09:22
*** jyoti_ranjan has joined #openstack-swift09:25
*** nosnos has joined #openstack-swift09:36
*** matsuhashi has joined #openstack-swift09:36
KbeedANOKELOFF, I see two things wrong.. the URl and the creds..09:41
KbeedANOKELOFF, probably you should use - swift -A http://94.23.34.79:8080/v1.0/system -U root -K testpass stat .. system is account here..09:42
dANOKELOFFKbee: Hum, ok09:43
dANOKELOFFKbee: i will try09:44
dANOKELOFFKbee: With this command i have the same error.09:44
Kbeei might have typed wrong.. try with this  -swift -A  http://94.23.34.79:8080/v1/AUTH_system -U root -K testpass stat09:45
Kbee401 means creds incorrect09:45
dANOKELOFFSame problem :(09:47
dANOKELOFFand same error09:47
dANOKELOFFoh wait09:48
KbeeIn your proxy-server.conf you have an extra |m| @ end of user_system_root -> user_system_root = testpass .adminm09:48
Kbeeremove that and try09:48
Kbeeadminm is altogether a new role09:49
*** judd7__ has joined #openstack-swift09:50
*** judd7___ has joined #openstack-swift09:50
*** dANOKELO_ has joined #openstack-swift09:52
*** judd7_ has quit IRC09:53
*** judd7 has quit IRC09:53
*** dANOKELOFF has quit IRC09:53
*** matsuhashi has quit IRC09:54
dANOKELO_Kbee: Ok i try , but again 401 Unauthorized09:55
*** matsuhashi has joined #openstack-swift09:55
dANOKELO_Auth GET failed @ip 401 Unauthorized09:55
KbeedANOKELO_, did you remove extra |m| in proxy-server.conf ?09:56
dANOKELO_yes09:56
Kbeerestart proxy ??09:56
dANOKELO_yes09:56
Kbeewaht command did you try ?09:57
*** matsuhas_ has joined #openstack-swift09:57
*** matsuhashi has quit IRC09:57
dANOKELO_http://94.23.34.79:8080/v1/AUTH_system -U root -K09:58
dANOKELO_testpass stat09:58
dANOKELO_swift -A  http://94.23.34.79:8080/v1/AUTH_system -U root -K09:58
dANOKELO_testpass stat09:58
dANOKELO_this command : swift -A http://94.23.34.79:8080/v1/AUTH_system -U root -K testpass stat09:59
dANOKELO_but if i try this command :10:01
dANOKELO_curl -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass:10:01
dANOKELO_ testpass' http://94.23.34.79:8080/auth/v1.010:01
dANOKELO_i have a message who give me my token, but if i write the token the response is 401 Unauthorized.10:01
dANOKELO_I go to gist you this example too.10:01
dANOKELO_THIS COMMAND :10:03
dANOKELO_curl -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass: testpass' http://94.23.34.79:8080/auth/v1.010:03
dANOKELO_RETURN :10:03
dANOKELO_* Hostname was NOT found in DNS cache10:04
dANOKELO_*   Trying 94.23.34.79...10:04
dANOKELO_* Connected to 94.23.34.79 (94.23.34.79) port 8080 (#0)10:04
dANOKELO_> GET /auth/v1.0 HTTP/1.110:04
dANOKELO_> User-Agent: curl/7.35.010:04
dANOKELO_> Host: 94.23.34.79:808010:04
dANOKELO_> Accept: */*10:04
dANOKELO_> X-Storage-User: system:root10:04
dANOKELO_> X-Storage-Pass: testpass10:04
dANOKELO_>10:04
dANOKELO_< HTTP/1.1 200 OK10:04
dANOKELO_< X-Storage-Url: http://94.23.34.79:8080/v1/AUTH_system10:04
dANOKELO_< X-Auth-Token: AUTH_tkbef158f2830747a7a482f803decacfbc10:04
dANOKELO_< Content-Type: text/html; charset=UTF-810:04
dANOKELO_< X-Storage-Token: AUTH_tkbef158f2830747a7a482f803decacfbc10:04
dANOKELO_< Content-Length: 010:04
dANOKELO_< X-Trans-Id: tx6a640152b58b43feb0c4b-0053aa9dc110:04
dANOKELO_< Date: Wed, 25 Jun 2014 10:00:33 GMT10:04
dANOKELO_<10:04
dANOKELO_* Connection #0 to host 94.23.34.79 left intact10:04
dANOKELO_THIS COMMAND :10:04
dANOKELO_curl -v -H ‘X-Auth-Token: AUTH_tkbef158f2830747a7a482f803decacfbc’ http://94.23.34.79:8080/v1/AUTH_system10:04
dANOKELO_RETURN :10:04
dANOKELO_* Hostname was NOT found in DNS cache10:04
dANOKELO_*   Trying 94.23.34.79...10:04
dANOKELO_* Connected to 94.23.34.79 (94.23.34.79) port 8080 (#0)10:04
dANOKELO_> GET /v1/AUTH_system HTTP/1.110:04
dANOKELO_> User-Agent: curl/7.35.010:04
dANOKELO_> Host: 94.23.34.79:808010:04
dANOKELO_> Accept: */*10:04
dANOKELO_> X-Auth-Token: AUTH_tk0966b8c1c29340fba36e8b90dcfb3a9410:05
dANOKELO_>10:05
dANOKELO_< HTTP/1.1 401 Unauthorized10:05
dANOKELO_< Content-Length: 13110:05
dANOKELO_< Content-Type: text/html; charset=UTF-810:05
dANOKELO_< Www-Authenticate: Swift realm="AUTH_system"10:05
dANOKELO_< X-Trans-Id: txf7d41f871b724c59ab313-0053aa9e7110:05
dANOKELO_< Date: Wed, 25 Jun 2014 10:03:29 GMT10:05
dANOKELO_<10:05
dANOKELO_* Connection #0 to host 94.23.34.79 left intact10:05
dANOKELO_<html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>10:05
dANOKELO_my god sorry !10:05
hugokuodANOKELO_: please paste in somewhere else next time. e.g. pastebin    Thanks10:06
dANOKELO_THis gist https://gist.github.com/anonymous/a07ae42317eb7350cf8a10:06
dANOKELO_hugokuo: yeah i paste in my gist, but i wrong paste , i dont paste the url sorry10:07
*** mkerrin has quit IRC10:12
*** jyoti_ranjan has quit IRC10:13
*** annegent_ has joined #openstack-swift10:16
*** jasond has quit IRC10:16
*** IRTermite has quit IRC10:20
*** annegent_ has quit IRC10:21
*** joeljwright has quit IRC10:22
*** jyoti_ranjan has joined #openstack-swift10:24
*** matsuhas_ has quit IRC10:28
*** matsuhashi has joined #openstack-swift10:28
mattoliveraudANOKELO_: you haven't specified the method in the 2nd command, ie -X GET10:29
dANOKELO_mattoliverau: sorry ? the command who i get the token ?10:30
mattoliverauNo the one afterwards, where you used the token10:36
mattoliverauThe 2nd one10:36
mattoliverauThe first command was successful :)10:37
dANOKELO_yeah, i try but again error 40110:37
*** matsuhashi has quit IRC10:37
*** matsuhashi has joined #openstack-swift10:37
mattoliverauSorry chatting from my phone so a bit slow :)10:37
dANOKELO_no problem , thank's for your help : when i run the 2nd one : the error message is " This server could not verify that you are authorized to access the document you requested"10:38
*** IRTermite has joined #openstack-swift10:42
dANOKELO_i put the gist of my swift error here, if anyone can help and solve my problem :) , thank's : https://gist.github.com/fclement21/13aadbf13ee45ad5854c10:52
*** Kbee has quit IRC10:52
mattoliverauYeah, it's like the token is incorrect or it can't find the account10:53
*** tdasilva has joined #openstack-swift10:54
dANOKELO_yeah, but i dont understand why, because the server give me the token.10:55
*** ppai has quit IRC11:02
acolesdANOKELO_: i'm making a guess here, based on trying to reproduce your error...have you setup memcached default interface to match what you have in you proxy-server.conf, as described in the multi node install doc, step 3 & 4?11:04
*** tdasilva_ has joined #openstack-swift11:05
*** tdasilva has quit IRC11:06
acolesdANOKELO_: 'Configure the Proxy node' section http://docs.openstack.org/developer/swift/howto_installmultinode.html11:07
dANOKELO_acoles: I update my gist with my memcached.conf and my proxy-server.conf : https://gist.github.com/fclement21/13aadbf13ee45ad5854c, i go eat , i continu when i back11:07
*** foexle has joined #openstack-swift11:08
*** baojg has quit IRC11:10
*** baojg has joined #openstack-swift11:11
*** baojg has quit IRC11:11
*** baojg has joined #openstack-swift11:12
mattoliverauSo it looks like your specifying the memcache server in the cache section of the proxy conf.11:13
mattoliverau*your not11:13
mattoliverauWell according to acoles link11:14
*** baojg has quit IRC11:16
*** annegent_ has joined #openstack-swift11:16
*** ppai has joined #openstack-swift11:17
*** dANOKELO_ has quit IRC11:18
acolesdANOKELO_: the proxy server conf in that last gist is different to the one you posted a while back https://gist.github.com/anonymous/eb6880e973b2baf1206611:19
*** nshaikh has joined #openstack-swift11:20
acolesdANOKELO_: and as mattoliverau spotted, you don't have the memcache_servers line in the most recent one11:20
*** annegent_ has quit IRC11:21
mattoliverauAnyway I'm going to call it a night, it's almost bed time and I need to spend some time with the wife, before she decides to devorse or worse kill me :p night all11:26
acolesmattoliverau: yeah, i thought it was late for you :)11:27
*** kopparam has quit IRC11:30
*** kopparam has joined #openstack-swift11:30
mattoliverauPerils of working from home and having phone connected to irc :p11:30
*** kopparam has quit IRC11:35
*** mmcardle has quit IRC11:36
*** Anticimex has joined #openstack-swift11:36
*** jyoti_ranjan is now known as jyoti-ranjan11:48
*** cm2 has joined #openstack-swift11:49
*** dmsimard_away is now known as dmsimard11:49
*** jyoti-ranjan has left #openstack-swift11:51
*** jyoti-ranjan has joined #openstack-swift11:51
*** tdasilva_ has quit IRC11:57
*** tdasilva has joined #openstack-swift12:08
*** mmcardle has joined #openstack-swift12:13
*** annegent_ has joined #openstack-swift12:16
*** kopparam has joined #openstack-swift12:19
*** annegent_ has quit IRC12:21
*** ajc_ has quit IRC12:23
*** shausy has quit IRC12:24
*** shausy has joined #openstack-swift12:25
*** shausy has quit IRC12:25
*** shausy has joined #openstack-swift12:34
openstackgerritMark Seger proposed a change to openstack/python-swiftclient: Add context sensitive help  https://review.openstack.org/10251012:36
*** kopparam has quit IRC12:38
*** ppai has quit IRC12:40
*** dANOKELOFF has joined #openstack-swift12:42
*** annegent_ has joined #openstack-swift12:45
dANOKELOFFmattoliverau and acoles I update my gist : https://gist.github.com/fclement21/13aadbf13ee45ad5854c12:53
*** annegent_ has quit IRC12:54
acolesdANOKELOFF: and you restarted memcached and swift proxy servers?12:56
dANOKELOFFacoles: I restarted but now I have 503 error12:57
dANOKELOFFwith the 2nd command12:57
*** joeljwright has joined #openstack-swift12:58
*** matsuhashi has quit IRC12:59
*** matsuhashi has joined #openstack-swift12:59
acolesdANOKELOFF: oh man :( can you gist tail of /var/log/swift/proxy.error13:00
dANOKELOFFacoles: sure.13:00
dANOKELOFFI havent got the proxy.error file13:01
*** lpabon has joined #openstack-swift13:03
*** matsuhashi has quit IRC13:04
acolesanything relevant in var/log/syslog?13:06
dANOKELOFFacoles: yes, i have so much lines13:06
acolesany near tail with 'proxy-server' in line13:08
acoles?13:08
*** joeljwright1 has joined #openstack-swift13:09
dANOKELOFFyes ; this : Jun 25 15:04:41 ns368471 proxy-server: 94.23.34.79 94.23.34.79 25/Jun/2014/13/04/41 GET /v1/AUTH_system HTTP/1.0 503 - curl/7.35.0 AUTH_tk447816efc3fa49f78f37ca2f8ce6cd26 - 118 - tx6033472498864a5994183-0053aac8e9 - 0.0016 - - 1403701481.163990021 1403701481.16561794313:10
*** matsuhashi has joined #openstack-swift13:10
dANOKELOFFacoles: ok , i update the gist 2sec please13:11
*** joeljwright has quit IRC13:11
dANOKELOFFhttps://gist.github.com/fclement21/13aadbf13ee45ad5854c13:11
*** zz_wasmum is now known as wasmum13:19
*** mkerrin has joined #openstack-swift13:20
*** tdasilva has quit IRC13:24
*** annegent_ has joined #openstack-swift13:26
dANOKELOFFIt's ok !13:27
dANOKELOFFI havent error13:27
dANOKELOFFacoles: Thank's for your help !13:27
acolesdANOKELOFF: oh? so what did you fix?13:27
dANOKELOFFI modify my container , my object and my account, and i had mount_check = false13:28
dANOKELOFFI follow this issue : https://answers.launchpad.net/swift/+question/16179613:28
*** miqui has joined #openstack-swift13:29
acolesdANOKELOFF: cool, i was just heading down the mount_check path after seeing that 507 in your logs13:30
dANOKELOFFacoles: thanks a lot for your help !13:30
*** mmcardle has quit IRC13:31
*** baojg has joined #openstack-swift13:31
acolesdANOKELOFF: so, FWIW, the memcached config is important because tempauth caches tokens it has issued, which *may* explain why your tokens were failing, IF tempauth was failing to cache them.13:31
acolesdANOKELOFF: glad you're fixed though :)13:32
*** mmcardle has joined #openstack-swift13:32
dANOKELOFFsure , thanks :)13:32
*** matsuhashi has quit IRC13:33
acolesdANOKELOFF: also, http://docs.openstack.org/developer/swift/development_saio.html#optional-setting-up-rsyslog-for-individual-logging may be useful13:33
*** matsuhashi has joined #openstack-swift13:33
dANOKELOFFok13:34
*** matsuhashi has quit IRC13:38
*** AbyssOne is now known as JelleB13:39
dmsimardUsing keystone auth with Swift - If I create a new user, a new tenant with that user in it, it works well with that user. If I create a second user and add it to the same tenant, that second user gets 403 on API calls. The logs don't seem to tell me why ?13:41
dmsimardBoth users have the _member_ role13:43
*** psharma_ has quit IRC13:43
*** nosnos has quit IRC13:43
chmoueldmsimard: this should work, you have nothing in the logs?13:43
dmsimardchmouel: I see the 403 in the swift logs, it looks like it might be keystone and not swift related..13:44
*** nshaikh has quit IRC13:44
*** matsuhashi has joined #openstack-swift13:44
*** matsuhashi has quit IRC13:44
chmoueldmsimard: it should give you detialled logs by default if you are running with DEBUG13:44
chmoueli.e: tenant mismatch or such13:44
chmouelor if it's keystone13:44
dmsimardYeah I'll turn up the verbosity see what happens13:45
*** matsuhashi has joined #openstack-swift13:45
*** matsuhashi has quit IRC13:49
*** lpabon has quit IRC13:50
*** nshaikh has joined #openstack-swift13:52
*** kopparam has joined #openstack-swift13:53
dmsimardNothing special with debug verbosity - I get an additional line with the user/tenant/role info and then the same 403 error - I'll check keystone :/13:55
*** kopparam has quit IRC13:57
*** kopparam has joined #openstack-swift13:57
openstackgerritMark Seger proposed a change to openstack/python-swiftclient: Add context sensitive help  https://review.openstack.org/10251013:59
*** CaioBrentano has joined #openstack-swift13:59
dmsimardNothing special in keystone either. This is weird.14:02
chmouelhumm weird yeah14:05
*** jyoti-ranjan has quit IRC14:06
openstackgerritChristian Schwede proposed a change to openstack/swift: Fix swift-recon --auditor bug  https://review.openstack.org/10019214:08
openstackgerritChristian Schwede proposed a change to openstack/swift: Add test for swift-recon --auditor  https://review.openstack.org/10005814:08
*** mmcardle has quit IRC14:09
dmsimardchmouel: Any idea who would return the 403 for this particular error ? "ClientException: Account GET failed: https://api.tld/v1/AUTH_e8217e83ef32427bb4e4d217f1390ab4?format=json 403 Forbidden  [first 60 chars of response] <html><h1>Forbidden</h1><p>Access was denied to this resourc"14:10
dmsimardI don't think it's necessarily keystone since the authentication is successful and I get a token (and I can do other stuff like nova calls)14:10
dmsimardIt's not the load balancers since otherwise the problem would extend to any/all users14:11
joeljwright1dmsimard: does the user have the appropriate role?14:11
dmsimardThat really leaves the swift proxy itself ?14:11
chmoueldmsimard: yeah the only thing i see is because the role is not set to that user14:11
joeljwright1I've seen these accessing swift with new users when the user didn't have the appropriate role to access swift14:11
dmsimardjoeljwright1: There's two users in a tenant, both with only the _member_ role. One works, the other get 403's14:11
chmouelthe swift_operator14:11
dmsimardIf I *have* to set swift_operator, I'll do it14:12
dmsimardbut that doesn't explain why the first user works14:12
dmsimardwithout that role14:12
chmouelyeah i am not sure14:12
chmouelit should work if __member_ is in swift_operator14:13
chmouelwhich i think is the default but i am not sure these days14:13
dmsimardswift_operator grants admin privileges for the tenant the user is in, correct ?14:14
dmsimardno more, no less ?14:14
dmsimardAs in, if it's configured as such in the swift proxy keystone middleware parameters14:14
*** mwstorer has joined #openstack-swift14:14
acolesclayg: gholt: notmyname: i updated fast-post wiki with a section discussing container sync https://wiki.openstack.org/wiki/Swift/FastPost14:14
acolesit ain't pretty, no surprise14:15
*** mmcardle has joined #openstack-swift14:16
*** mjseger has quit IRC14:16
dmsimardchmouel: So I should add _member_ to the list of operator_roles - then ?14:17
chmoueldmsimard: if the first one works, i don't think you should14:18
chmouelit's maybe a configuration issue in keystone with the second14:18
chmoueltry to auth with both users with curl14:18
chmoueland see the output of both if there is things is missing14:18
*** grapsus_ has quit IRC14:19
*** sileht has quit IRC14:20
*** grapsus_ has joined #openstack-swift14:21
*** annegent_ has quit IRC14:21
*** annegent_ has joined #openstack-swift14:21
*** sileht has joined #openstack-swift14:23
*** kenhui has joined #openstack-swift14:24
*** jasond has joined #openstack-swift14:27
*** pberis has joined #openstack-swift14:35
openstackgerritMark Seger proposed a change to openstack/python-swiftclient: Add context sensitive help  https://review.openstack.org/10251014:36
*** zhiyan is now known as zhiyan_14:43
*** kopparam_ has joined #openstack-swift14:45
*** eglynn has joined #openstack-swift14:47
*** mmcardle has quit IRC14:47
*** kopparam has quit IRC14:48
dmsimardLooking at the differences, aside from timestamps or tenant/user/token credentials, there isn't anything different.. One does a call to "/v1/AUTH_e8217e83ef32427bb4e4d217f1390ab4?format=json" and gets a 200, the other a 403. This is driving me nuts.14:49
dmsimardAdding the 403 user to swift_operator or adding _member_ to operator_roles solves the issue14:49
eglynndumb question about swift eventual versus strong consistency?14:50
eglynnsay datapoints {p1, p2, ..., p_i} are stored in a swift object14:50
eglynn(presumably replicated in an eventually consistent way)14:50
eglynnsay I want to read this blob and update with a further datapoint {p_(i+1)}14:51
dmsimardI do have a stacktrace for the 403, though. Looked at the code but it's just reacting to the 403: http://paste.openstack.org/show/84885/14:51
*** CaioBrentano has quit IRC14:51
eglynnbut evential consistency tells me that I may end up folding my new datapoint into the an older version of the object {p1, p2, ..., p_(i-1)} instead of {p1, p2, ..., p_i}14:51
eglynnso the $64k question ...14:51
*** mmcardle has joined #openstack-swift14:51
eglynnis read-then-update an acknowledged *anti*-pattern for swift?14:52
wasmumanyone have some keystone swift3 time?14:53
jasondi'm using bin/swift-temp-url to generate a temp URL, but when I try to access it, I get "401 Unauthorized: Temp URL invalid".  can someone help me troubleshoot what's wrong?14:54
*** kevinc_ has joined #openstack-swift14:57
openstackgerritDonagh McCabe proposed a change to openstack/swift: Add swift-checker utility for use by monitoring tools  https://review.openstack.org/9996114:59
*** swat30 has quit IRC15:03
*** jokke_ has quit IRC15:03
*** zaitcev has joined #openstack-swift15:04
*** ChanServ sets mode: +v zaitcev15:04
*** kopparam_ has quit IRC15:08
*** judd7__ has quit IRC15:08
*** kopparam has joined #openstack-swift15:09
*** swat30 has joined #openstack-swift15:10
dmsimardoh chmouel15:11
dmsimardIt's right there, on your blog15:11
*** jokke_ has joined #openstack-swift15:11
dmsimardhttp://blog.chmouel.com/2011/11/24/swift-and-keystone-middleware-part1/ "So let’s say we have a user called demo2 which is part of the demo account and have only the role Member to it and not SwiftOperator by default as we say before he will not be able to do much."15:11
dmsimard:D15:12
claygacoles: don't we have a spec repo for this sort of stuff now?15:12
*** kopparam has quit IRC15:13
*** lpabon has joined #openstack-swift15:16
*** wasmum is now known as zz_wasmum15:19
*** kevinc_ has quit IRC15:20
notmynamegood morning world15:24
*** kevinc_ has joined #openstack-swift15:24
*** zz_wasmum is now known as wasmum15:25
dmsimardnotmyname: o/15:28
*** gyee has joined #openstack-swift15:31
*** byeager has joined #openstack-swift15:34
*** annegent_ has quit IRC15:40
notmynameclayg: almost on the -specs repo15:40
notmynamecreiht: acoles: portante: how's getting 2.0 into the lab and testing it going?15:41
creihtnotmyname: it is in progress, but I'm also on vacation for the rest of the week :)15:42
notmynamecreiht: no vacation, just testing!15:42
notmyname;-)15:42
notmynamecreiht: I hear it's raining a lot in TX (Karen was in DFW this weekend). did it make it down to SA?15:42
creihtyeah15:42
creihtit is also raining a lot at the beach, but that is ok with me :)15:43
notmynamedoh15:43
*** annegent_ has joined #openstack-swift15:43
*** annegent_ has quit IRC15:43
notmynameour "rain" never gets to the ground https://twitter.com/CarMarConroy/status/481820593163993089 (this morning in the middle part of SF)15:44
notmynameoh. middle-west part. (west portal, not western addition which is in the north central part--of course)15:45
notmynamecreiht: enjoy your vacation (why are you on IRC?). one last work question, please, before you go: based on what you know when you left, does it look like the testing of 2.0 will be done at rax by next wednesday?15:46
creihtlol15:47
creihtnot sure15:47
creihtnotmyname: and because it is raining outside :)15:48
notmynameheh15:48
creihtnotmyname: but it is in process15:49
notmynamegood15:50
creihtif we don't get distracted by other thing, it might be a possibility15:50
notmynamegreat15:50
creihtbut you know how things go :)15:50
notmynameright15:50
notmynamein this case, though, because it is a big release, there are some non-dev people getting involved. so I'm trying to do some date coordination15:50
creihthah15:51
notmynameie the foundation and I hope some of the companies here, including RAX, will do some marketing press releases about it15:51
*** shausy has quit IRC15:53
*** wasmum is now known as zz_wasmum15:53
*** shausy has joined #openstack-swift15:54
cschwedenotmyname: i might write a blogpost about SP and publish it on our blog15:54
*** zz_wasmum is now known as wasmum15:55
notmynamecschwede: great. I hope you do :-)15:55
notmynameI'll be doing the same15:55
cschwedenotmyname: great :)15:55
creihtnotmyname: I was thinking we could get glange to do a comic about it ;)15:55
notmynameperfect :-)15:55
*** wasmum is now known as zz_wasmum15:56
glangeswift isn't funny15:56
creihtglange: neither are your comics :)15:56
cschwedenotmyname: i’m thinking about doing something like a „how do i use SP“ post, more from a technical/user/ops site15:56
glangeboo!15:56
glangemy comics are hillarious15:56
glangethey hit those 2 or 3 people that understand them really hard :)15:57
creihtyes you have a very targeted audience :)15:57
notmynamecschwede: yes, that would be good. let's try to coordinate (ie talk over email as we write it) so we don't have too much overlap15:58
cschwedenotmyname: good idea, i was thinking the same15:59
*** joeljwright1 has quit IRC15:59
*** dANOKELOFF has quit IRC15:59
*** CaioBrentano has joined #openstack-swift16:01
openstackgerritEamonn O'Toole proposed a change to openstack/swift: Parallel object auditor  https://review.openstack.org/5977816:06
*** joeljwright has joined #openstack-swift16:07
*** nshaikh has quit IRC16:08
*** GeorgesLeYeti has joined #openstack-swift16:27
* notmyname is out for post-op visit. I get my bandage off today!!!!!16:27
GeorgesLeYetiHello there16:27
*** joeljwright1 has joined #openstack-swift16:31
*** joeljwright has quit IRC16:34
acolesnotmyname: in progress16:36
acolesclayg: we do, i'll move it there16:36
*** orzel has joined #openstack-swift16:36
*** shausy has quit IRC16:37
orzelHello. there's no admin interface in horizon for swift, right ? As a user i can see my containers, but the admin can't see anything, or can it ?16:37
*** byeager has quit IRC16:38
clayg+1 glange's comics are funny (most of the time)16:39
goodesclayg: is sent a PR with the two changes for vsaio16:40
*** joeljwright has joined #openstack-swift16:40
claygvsaio i like it16:40
clayggoodes: do i have to run it/look at it - or can i just merge it?16:41
goodesclayg: 8 lines of change - visual review then merge16:42
*** joeljwright1 has quit IRC16:44
orzelwhat's 'PR' for ? I guess r is 'review' .. ?16:49
*** joeljwright1 has joined #openstack-swift16:50
goodesPR is a github Pull Request16:50
*** joeljwright has quit IRC16:52
*** joeljwright has joined #openstack-swift16:56
*** joeljwright1 has quit IRC16:58
*** joeljwright2 has joined #openstack-swift16:58
*** joeljwright has quit IRC17:02
*** joeljwright2 has quit IRC17:02
claygorzel: probably almost no one in here knows anything about horizon - do they have like an #openstack-horizon or something maybe?17:05
*** eglynn has quit IRC17:07
*** zz_wasmum is now known as wasmum17:12
*** GeorgesLeYeti has quit IRC17:15
*** mkollaro has quit IRC17:19
*** jamiehannaford has joined #openstack-swift17:20
openstackgerritA change was merged to openstack/swift: Don't count 412 or 416 as errors in stats  https://review.openstack.org/9853017:21
orzelclayg: this chan exists, yes. You're kinda saying that the "swift" community doesn't really care about the web gui, right ?17:23
*** mkollaro has joined #openstack-swift17:25
*** baojg has quit IRC17:26
creihtorzel: The swift community cares very much about the user interfaces to swift, of which many are available, and horizon is just one17:26
creihtwe can't be experts in all of them17:26
creiht:)17:26
creihtthat's why you will likely get a much better answer from the horizon folks17:27
orzelmy question is quite high level (anything there?). i would not qualify it as 'expert' !17:30
orzelbut ok, i'll see with them17:30
creihthah17:30
creihtlast I saw that wasn't there, but I don't know if they have been working on that top of stuff lately17:30
creihts/top/type17:31
orzellet's see17:32
*** shri has joined #openstack-swift17:32
orzelcompletely unrelated, but i'm trying to switch from fs to swift as glance backend17:32
*** nsquare has joined #openstack-swift17:34
*** jasond` has joined #openstack-swift17:35
*** mmcardle has quit IRC17:35
orzelcreiht: speaking of user interface. from cli, 'glance stat' is very useful, but is it possible to get the same info for every user as an admin ?17:40
orzeli can't find anything in various docs17:40
orzelswift stat, sorry :)17:40
creihtorzel: not really, since there isn't anything built into swift that keeps track of all accounts17:41
*** jamiehannaford has quit IRC17:41
creihtthat's usually left up to the auth system17:41
claygcreiht: os.walk() on the account nodes ;)17:41
*** jamiehannaford has joined #openstack-swift17:41
creihtthere are tools that can collect the info for billing purposes17:42
creihtclayg: lol17:42
*** eglynn has joined #openstack-swift17:46
jasond`does anybody know why i might be getting "401 Unauthorized: Temp URL invalid" when i generate a tempurl with bin/swift-temp-url?  are there special permissions needed to use tempurls?17:47
*** kopparam has joined #openstack-swift17:47
orzelcreiht: so, basically, i need ceilometer17:47
torgomaticjasond`: probably you're calling it wrong? If you see "Temp URL invalid" in the response, you know that the tempurl middleware is installed17:48
torgomatichave you set up a key and all that?17:48
creihtorzel: that's one option I guess17:49
jasond`torgomatic: i'm calling it with:  curl 'http://localhost:8080/v1/AUTH_demo/a/b?temp_url_sig=7396ed6d6b6e5a5cb8b020c4494cf2a6a9f1e325&temp_url_expires=1403713581'17:49
*** wasmum is now known as zz_wasmum17:49
torgomaticjasond`: your expires is in the past17:50
jasond`there is a key.  i'm not sure it's being accepted as valid17:50
jasond`torgomatic: that was from a little bit ago17:50
torgomaticjasond`: if X-Account-Meta-Temp-Url-Key is set on the account, it's valid17:51
torgomaticit's just an opaque string to tempurl; there's no restrictions other than length > 017:51
jasond`torgomatic: just regenerated one:  curl 'http://localhost:8080/v1/AUTH_demo/a/b?temp_url_sig=51b16c4f35f1a781f4d0b9039f23145072e69455&temp_url_expires=1403719664'17:51
*** jyoti-ranjan has joined #openstack-swift17:52
jasond`torgomatic: good to know17:52
torgomaticjasond`: can you share how you're calling bin/swift-temp-url? maybe something's wonky there17:53
notmyname /back17:53
jasond`torgomatic: /opt/stack/swift/bin/swift-temp-url GET 1000 /v1/AUTH_demo/a/b 72930a7927a4fa7f8cab54e59f4aa1b317:53
*** kopparam has quit IRC17:54
torgomaticjasond`: well, I can generate that same URL when I get the expires timing right... can you run 'swift stat' (or otherwise HEAD the account) and link to a paste of the result please?17:55
openstackgerritAlistair Coles proposed a change to openstack/swift-specs: Updating containers on object fast-POST  https://review.openstack.org/10259217:56
torgomaticswift-specs? who in the what now?17:57
acolesclayg: ^^17:57
acolestorgomatic: clayg shoved me there :)17:58
claygwhat now?17:59
notmynamedid mordred get the boilerplate proposed there?17:59
acolesnotmyname: yes, its there18:00
jasond`torgomatic: here's the output http://paste.openstack.org/show/84905/18:00
notmynameah cool18:00
glangeclayg: thanks :)18:01
acolesnotmyname: wasn't sure if i was supposed to create specs/juno - projects vary18:01
notmynameacoles: I'm not sure if any of us know yet ;-)18:01
notmynameostly it's up to us to decide what to do18:01
torgomaticjasond`: your account doesn't match; the paste says AUGH_6e8blahblahblah, but your temp url has AUTH_demo in it18:02
torgomaticuse the one from the paste18:02
* creiht sneaks back into vacation mode18:02
claygare my timezones off or is there a meeting nowish?18:02
notmynameclayg: in an hour18:02
*** jokke__ has joined #openstack-swift18:02
jasond`torgomatic: that may have done it.  i don't see the error message.  thank you!18:03
torgomaticjasond`: np18:03
acolesnotmyname: yeah, so i was lazy and stuck it in specs to avoid a 'no toc entry' warning...so i can go home :)18:03
notmynameacoles: :-)18:04
*** jokke__ has quit IRC18:05
mordrednotmyname: yah - a working structure is there- please edit/change to suit what you want to do18:05
notmynamemordred: thanks.18:05
mordrednotmyname: also, I do not believe I can do anything sane to mark the other patches as landed - at least not without way more testing than I think we have time for - so I recommend just marking them as abandoned as per the original plan18:06
notmynamemordred: ok. I did that yesterday afternoon18:07
mordrednotmyname: I'll spend some time poking at options for the next time we do this - and maybe at some point we'll actually have a non-painful process18:07
mordrednotmyname: great18:07
notmynamemordred: great. we're using a feature branch again for the (real) EC work. while I think we can avoid the force push this time (probably), it's still good to know how to do it sanely18:07
claygdoes anyone else have a strong preference in tests of resp = req.get_response(app) over resp = controller.METHOD(req)?18:09
*** jokke_ has quit IRC18:09
claygI always think the second one feels like cheating, but most of the time it just doesn't matter if you call PUT with a GET req or if you're controllers .container_name property doesn't match what should have got parsed out of the req's PATH_INFO18:09
notmynameclayg: doesn't the first still work with responses-as-exceptions where the second doesn't?18:10
notmynametorgomatic: ^18:10
claygnotmyname: ANOTHER GOOD POINT!18:10
notmynamespeaking of swift team meeting, do we need to meet this week? nothing's on the agenda https://wiki.openstack.org/wiki/Meetings/Swift18:11
*** jokke_ has joined #openstack-swift18:11
claygso If I submit a bug fix, s'ok to "clean up" some tests while I'm writing new ones?  Cause otherwise I sorta have to pop a whole new testcase with a different setup (as opposed to just fixing the existing test case's setup - it's like 10 existing tests in test/unit/proxy/controllers/test_obj)18:12
torgomaticclayg: what notmyname said; there's stuff in __call__ you want18:13
claygsweet that's at least two folks that would find the clean up favorable - i'll throw it up and see if it sticks18:13
claygat least two *other* - i already greatly prefer the first form, just wasn't sure if I could really tease out why it was objectively better18:14
notmynameya, I'd actually lean towards calling controller.METHOD wrong (instead of less preferable)18:15
notmynameportante: peluse_: clayg: torgomatic: acoles: cschwede: others? any compelling need to have a meeting today? anything to bring up?18:15
torgomaticnotmyname: all I've got is stuff that'll be in Gerrit shortly18:17
*** jasond` has left #openstack-swift18:22
openstackgerritgholt proposed a change to openstack/swift: SimpleClient http proxying  https://review.openstack.org/10259818:26
cschwedenotmyname: the only thing from my side would be the mid-sprint next week in Paris - anyone interested? https://wiki.openstack.org/wiki/Sprints/ParisJuno2014#Swift18:27
cschwedenotmyname: but no need to have a meeting for that ;)18:29
notmynamecschwede: ok, thanks18:29
*** zz_wasmum is now known as wasmum18:29
*** pberis has quit IRC18:29
torgomaticnotmyname: maybe just have the "open discussion" section of the meeting? that should take all of 5 minutes if nobody's got anything to say18:30
torgomaticor not; up to you18:31
notmynamecschwede: https://twitter.com/notmyname/status/48186719412538573018:31
cschwedenotmyname: great :D18:32
*** kenhui has quit IRC18:33
*** gvernik has joined #openstack-swift18:37
*** tsg has joined #openstack-swift18:45
notmynametorgomatic: ya, that's a good idea18:45
notmynamemeeting today will be "open discussion" and may or may not take exactly 5 minutes18:46
*** wasmum is now known as zz_wasmum18:49
*** kopparam has joined #openstack-swift18:51
*** kopparam has quit IRC18:56
anticwtrivia question for today: if you have 3 replicas you have how many hand-off locations?18:58
anticwwhat if you have 2 ... or 1 ?18:58
anticwswift-get-nodes ...18:58
torgomaticswift-get-nodes -a18:58
torgomatic:)18:58
torgomaticin an N-disk system, you'll have somewhere in the vicinity of N-3 handoffs (most of the other disks in the cluster)18:59
*** zz_wasmum is now known as wasmum18:59
torgomaticswift-get-nodes only prints the first 3 because printing 1000+ handoffs is not particularly helpful18:59
notmyname"helpful"18:59
*** cutforth has joined #openstack-swift19:00
anticwtry with replicas=119:00
notmynamevideo of PTL webinar I did yesterday has been uploaded https://www.youtube.com/watch?v=skNooBXIKqc19:00
notmynameok, swift team meeting of "open discussion" starts now in #openstack-meeting19:01
openstackgerritSamuel Merritt proposed a change to openstack/swift: Zero-copy object-server GET responses with splice()  https://review.openstack.org/10260919:03
*** openstackgerrit has quit IRC19:04
*** openstackgerrit has joined #openstack-swift19:04
*** jamiehannaford has quit IRC19:06
*** jamiehannaford has joined #openstack-swift19:09
*** kevinc_ has quit IRC19:10
*** jyoti-ranjan has quit IRC19:11
*** wasmum is now known as zz_wasmum19:12
*** angelastreeter has joined #openstack-swift19:16
*** gvernik has quit IRC19:20
*** mlipchuk has joined #openstack-swift19:26
*** zz_wasmum is now known as wasmum19:28
*** lpabon_ has joined #openstack-swift19:28
*** lpabon_ has quit IRC19:31
*** wasmum is now known as zz_wasmum19:41
mattoliverauCool and on that note I'm going back to bed! See you all in the few hours :)19:42
*** jokke_ has quit IRC19:45
*** tdasilva has joined #openstack-swift19:50
*** jokke_ has joined #openstack-swift19:52
*** zz_wasmum is now known as wasmum19:53
*** kevinc_ has joined #openstack-swift19:55
*** jamiehannaford has quit IRC20:00
*** openstackgerrit has quit IRC20:05
*** openstackgerrit has joined #openstack-swift20:05
*** jokke_ has quit IRC20:10
*** joeljwright has joined #openstack-swift20:13
*** joeljwright has quit IRC20:13
*** cutforth has quit IRC20:14
openstackgerritA change was merged to openstack/swift: Fix swift-recon --auditor bug  https://review.openstack.org/10019220:15
*** orzel has left #openstack-swift20:21
openstackgerritSamuel Merritt proposed a change to openstack/swift: Zero-copy object-server GET responses with splice()  https://review.openstack.org/10260920:22
*** wasmum is now known as zz_wasmum20:23
*** pconstantine_ has joined #openstack-swift20:25
*** lpabon has quit IRC20:25
torgomatic^^ just a changed commit message; I completely forgot to mention benchmark results20:27
portante37% reduction in CPU, cool20:29
portantetorgomatic: did it improve bandwidth utilization for large objects?20:30
torgomaticyeah, turned out it was actually worth doing :)20:30
portante:)20:30
portantego figure20:30
torgomaticportante: I didn't get into testing that; in my tests, stuff was going over the 10G LAN as fast as the disk could spew it out20:30
*** shri1 has joined #openstack-swift20:30
*** shri1 has quit IRC20:30
portantenice20:30
torgomaticboth with splice and with read/write20:30
openstackgerritJosh Gachnang proposed a change to openstack/python-swiftclient: Adding Swift Temporary URL support  https://review.openstack.org/10263220:31
*** zz_wasmum is now known as wasmum20:31
*** shri has quit IRC20:31
torgomaticI tried installing the patch cluster-wide to do some real benchmarks, and that's when I found out that RHEL/CentOS 6's kernels don't support AF_ALG sockets :|20:32
portanteugh20:32
portantemight be worth a backport patch!20:32
torgomaticI think so, but I'm biased ;)20:33
torgomaticI also have no idea what the scope of that would be, so...20:33
torgomaticthe good news is it made me catch EAFNOSUPPORT and turn that into a useful warning in the logs, so there's your silver lining :)20:35
portanteso that means we should just take the patch no matter what!20:35
torgomaticclearly ;)20:35
*** CaioBrentano has quit IRC20:41
*** jokke_ has joined #openstack-swift20:41
*** kenhui has joined #openstack-swift20:44
*** angelastreeter has quit IRC20:47
goodesis feature/ec just profiles or does it also include object ec code?20:49
torgomaticannegentle: ping20:57
notmynamegoodes: feature/ec used to have the storage policy work on it (it was poorly named)20:59
notmynamegoodes: but it's been reset and now it is being used for the ec storage policy work21:00
*** tdasilva has quit IRC21:00
*** kenhui has quit IRC21:00
*** kenhui has joined #openstack-swift21:01
goodesnotmyname: i'm interested to learn how meta data will be stored with ec'd objects - where is the best place to look?21:02
*** wasmum is now known as zz_wasmum21:02
openstackgerritA change was merged to openstack/swift: Fix some spelling in comments  https://review.openstack.org/10229721:03
clayggoodes: try asking peluse_ - i'm not sure where the ec design docs are published - i suppose we'll be moving them into the specs repo21:13
*** mmcardle has joined #openstack-swift21:14
*** foexle has quit IRC21:24
goodesclayg: thanks I'll look for him tomorrow, time to call it a night21:27
claygg'night21:31
*** mmcardle has quit IRC21:39
*** miqui has quit IRC21:40
*** orzel has joined #openstack-swift21:48
orzeli keep on having no object reported by 'swift stat', despite them working perfectly (~200 objects in one container, i can add/see/remove/whatever). Any idea why ?21:49
*** jamiehannaford has joined #openstack-swift21:54
claygoh gawd the rabbit hole keeps going :'(22:04
*** judd7___ has quit IRC22:08
mattoliverauMorning everyone.. again :P22:11
*** dmsimard is now known as dmsimard_away22:15
*** kenhui has quit IRC22:16
notmynameportante: may be too late for you, but I'm starting to look at the swift-specs repo right now22:21
notmyname*sigh* clayg: what's the solution for "dist must be a Distribution instance"?22:26
notmynamemordred: ^^ isn't there a recent patch to pbr to fix that22:27
*** acole_ has joined #openstack-swift22:32
acole_hey'all22:33
notmynameacole_: hello22:33
acole_notmyname: hey!22:33
acole_so googling "openstack swift chargeback" didn't work out for me :)22:33
acole_how do y'all deal with events for bandwidth/requests/storage over time?22:34
notmynameacole_ == acoles? if not, this will get _really_ confusing22:34
acole_nope22:34
acole_adrian cole22:34
notmynamehmm22:34
notmynameok22:34
acole_nova is more SEO friendly in this regard :)22:34
notmynameacole_: what are you looking for in the way of chargebacks?22:34
*** openstackgerrit has quit IRC22:35
*** openstackgerrit has joined #openstack-swift22:35
acole_so basically, I'm looking at how various projects address this for some research I need to make22:35
acole_it isn't a swift-specific thing, just I figured it might exist here and is a close match to what I need to do22:36
notmynameacole_: so strategies as opposed to "I have a prod cluster and need to bill my customers"22:36
acole_right22:36
acole_this is internal so more accounting/optimization vs billing22:36
notmynameright22:36
notmynameacole_: ok. basically there are 2 different ways people have done this for swift22:37
notmynameone is the ceilometer approach: have middleware to intercept requests and track bandwidth and then poll the cluster about account stats. this requires a list external to swift of what accounts are in the system22:38
notmynamethe other way is like this: parse the logs after the fact for bandwidth usage and crawl the drives in the cluster for the storage usage (account stats)22:38
acole_gotit22:39
acole_is there any project that would address this inside swift or are ^^ pretty much fine for now for most folks?22:39
notmynameacole_: what do you mean by "inside swift"?22:40
acole_like this https://wiki.openstack.org/wiki/SystemUsageData22:40
notmynameacole_: note that this information is end-user info. not operator info like "how full are my drives"22:40
acole_as opposed to parsing logs, firing events basically22:40
acole_^^ right22:40
acole_I can imagine that the granularity of change makes something like SystemUsageDAta trickier in swift vs nova22:41
notmynamea bit. there's also often a few orders of magnitude more entities in an swift cluster than a nova cluster :-)22:41
acole_yeap22:42
notmynameacole_: I'd say that swift does provide a lot of this info via logs and the account stats (eg some sort of mashup of the 2 strategies above)22:42
notmynameand swift already has some event emitting info for operator things (so there is somewhat of a framework for emitting info to a listner)22:43
acole_ic cool22:43
notmynamethis is actually one of the reasons that I think a good durable queue service (maybe marconi someday?) would be awesome for swift22:43
notmynameit seems like swift's statsd info is similar to that nova notification system22:45
notmynameexcept that the statsd info isn't end-user utilization info. it's more like "how many GETs respond with 404s"22:45
*** kopparam has joined #openstack-swift22:45
*** goodes has quit IRC22:46
*** kenhui has joined #openstack-swift22:47
acole_notmyname: thanks for the brain dump!22:47
*** serverascode has quit IRC22:47
notmynameacole_: does it answer your question?22:47
acole_yep sure did22:47
notmynameacole_: what will you do with it?22:47
acole_well, tbh it is like some other practices I've seen22:48
acole_so sort of affirms that at least in swift (another leveraged cloud system), this sort of approach much be working :)22:49
*** goodes has joined #openstack-swift22:49
*** orzel has left #openstack-swift22:49
acole_so I've been basically trying to catch up with how various cloud systems address things, and the topic du'jour is utilization as I'm tasked with helping work on that.22:49
notmynameleveraged cloud system?22:49
*** kopparam has quit IRC22:50
acole_so for example, I don't want to NIH a chargeback design, if there was one embedded in swift.22:50
acole_so basically this is just me and how I research stuff :) irc, code search, wiki, etc22:51
notmynameacole_: FWIW, I wrote a project a while back that does this (haven't looked at it in a while so it probably doesn't work anymore) called slogging, and SwiftStack uses a similar method (parse logs and crawl drives)22:51
*** serverascode has joined #openstack-swift22:51
notmynameacole_: with zero current support or promises of actually working (although it used to): https://github.com/notmyname/slogging22:52
acole_bbiab need to switch rooms22:52
*** acole_ has quit IRC22:52
*** shri has joined #openstack-swift22:53
*** kenhui has quit IRC22:55
*** tdasilva has joined #openstack-swift22:57
*** acole has joined #openstack-swift22:57
acolenotmyname: thanks, I'll have a look. the short of this project is that we need to make something not too dissimilar to ICE https://github.com/Netflix/ice22:58
acoleand I'm looking around to see how folks are plumbing their cloud tenants/regions into usage reporting22:59
acoleseems that part must be moreso special sauce than open source projects at least so far as I've found22:59
notmynamewell sorta. I mean, if each cloud tool has their own concept of those things the way to track it will be "custom" compared to another cloud tool23:00
acolefair point23:01
notmynameacole: for swift, if you think about the entities as a tree (account->container->object), then it makes sense to track just that. and map to an actual user or tenant external to the swift usage reporting system23:02
*** jamiehannaford has quit IRC23:02
*** kevinc_ has quit IRC23:05
*** kevinc_ has joined #openstack-swift23:06
*** jkelly has joined #openstack-swift23:12
*** lpabon has joined #openstack-swift23:17
*** jkelly has quit IRC23:17
*** lpabon has quit IRC23:18
*** lpabon has joined #openstack-swift23:19
*** jamiehannaford has joined #openstack-swift23:23
*** acole has quit IRC23:26
*** tdasilva has quit IRC23:35
*** pconstantine_ has quit IRC23:53

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