Tuesday, 2019-03-12

notmynametimburke: lol. I didn't actually *run* the patch. but it looks ok and the idea seems sound. and the +1 seems as strong as my previous "hmm... that's odd" when you first showed it to me00:02
zaitcevI didn't land it because I'm actually no sure what is more likely to break. If you monkey-patch something system, it's less likely to change, while internals of eventlet are more fluid. But then monkey-patching has more side effects, if anything goes wrong it's harder to realize it's involved. So it's a bit of a Buridan's Ass dilemma.00:02
notmynamethat was previous versions. current one doesn't rely on eventlet monkeypatching nor stdlib monkeypatching00:04
notmynamealso, TIL https://en.wikipedia.org/wiki/Buridan%27s_ass00:04
notmynamezaitcev: I like the current version of the patch because it also helps with a subsequent timburke patch that helps us parse our headers without having to either monkeypatch stdlib or wait for py3800:10
notmynametimburke: which one was that?00:10
*** gyee has quit IRC00:16
*** itlinux has joined #openstack-swift01:24
*** mvkr has quit IRC01:36
*** mvkr has joined #openstack-swift01:38
*** mvkr has quit IRC01:49
*** itlinux has quit IRC01:51
*** mvkr has joined #openstack-swift01:52
*** openstackstatus has quit IRC02:22
*** openstack has joined #openstack-swift02:24
*** ChanServ sets mode: +o openstack02:24
openstackgerritMichele Valsecchi proposed openstack/swift master: Fix a typo  https://review.openstack.org/64264404:57
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: Change grpcio version in requirements.txt to >=1.11.0  https://review.openstack.org/63936504:59
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: test which gates run in the gerrit  https://review.openstack.org/64264505:09
*** tristanC has quit IRC06:02
*** tristanC2 has joined #openstack-swift06:04
*** mahatic has quit IRC06:07
*** DHE has quit IRC06:07
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264506:11
*** dr_gogeta86 has quit IRC06:16
*** DHE has joined #openstack-swift06:17
*** e0ne has joined #openstack-swift06:18
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264506:46
openstackgerritMerged openstack/swift master: Do not use self in classmethod  https://review.openstack.org/64235906:48
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264506:54
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264507:02
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264507:16
*** pcaruana has joined #openstack-swift07:39
*** hseipp has joined #openstack-swift07:42
*** pcaruana has quit IRC07:43
*** pcaruana has joined #openstack-swift07:43
*** tkajinam has quit IRC08:07
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264508:10
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: test to add override-checkout to pull the master  https://review.openstack.org/64268008:11
*** e0ne has quit IRC08:17
*** ccamacho has joined #openstack-swift08:21
*** e0ne has joined #openstack-swift08:23
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264508:24
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264508:28
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: DNM: trying to set override-checkout  https://review.openstack.org/64264508:30
kota_sorry, the noisy patch stream. I'm trying the black box testing to understand what happens in the zuul.08:31
kota_and it looks like finally I got the dsvm gate in the losf feature branch.08:32
*** e0ne has quit IRC08:39
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/losf: Enable swift-dsvm-functional tests at losf feature branch  https://review.openstack.org/64264508:51
kota_alecuyer, rledisez, notmyname: ^^^08:52
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Stop overwriting reserved term  https://review.openstack.org/63949008:53
*** mikecmpbll has joined #openstack-swift09:05
zigoI'm getting this error in swift-proxy: http://paste.openstack.org/show/747594/09:48
zigoWhat can this be about?09:48
*** hseipp has quit IRC10:01
*** [diablo] has joined #openstack-swift10:07
*** e0ne has joined #openstack-swift10:16
*** ybunker has joined #openstack-swift11:42
ybunkerhi everyone, still battle with the acct cont issue from yesterday :-(11:43
ybunkerthe other thing that im worry about is that besides replication, the nodes can't write acct or container to the actual node, for example:   http://pasted.co/9856ba8e11:58
*** e0ne has quit IRC12:36
*** ybunker has quit IRC12:50
*** ybunker has joined #openstack-swift12:53
*** FlorianFa has quit IRC13:03
*** irclogbot_2 has quit IRC13:26
*** e0ne has joined #openstack-swift13:28
*** irclogbot_2 has joined #openstack-swift13:29
*** openstack has joined #openstack-swift15:39
*** ChanServ sets mode: +o openstack15:39
*** e0ne has quit IRC15:45
timburkezigo, looks like a client disconnect that just happened to be on a chunk boundary? i guess?15:57
*** e0ne has joined #openstack-swift15:58
*** guimaluf has joined #openstack-swift15:59
*** ybunker has quit IRC16:03
*** mikecmpbll has quit IRC16:03
*** mikecmpbll has joined #openstack-swift16:04
*** ybunker has joined #openstack-swift16:20
*** gyee has joined #openstack-swift16:27
*** ccamacho has quit IRC16:29
ybunkerhi, anyone can give me a hand with the acct cont replication issue?16:46
ybunkerat this point i think that any acct container is being replicated at all on the cluster :-(16:53
*** e0ne has quit IRC16:55
ybunkeris there any mailing list that i can send the query? i really need to get this problem solved asap :S17:22
tdasilvaybunker: hi, so where are things at?17:23
tdasilvafrom the chat with zaitcev yesterday it sounded like he was suggesting to merge the two separate configs into one? to simplify things?17:24
ybunkertdasilva: objects are replicating fine.. but accounts and containers not, i already check many things but with no luck at all, also for some reason, besides replication, i think that is not writing container or account info inside the local /srv/node directories17:25
tdasilvaybunker: right, so did you make any changes to your configs yesterday with the suggestion from zaitcev ?17:28
*** hseipp has quit IRC17:28
ybunkertdasilva: yes, and it doesn work :(, let me send you the config files17:28
zaitcevtdasilva: I only meant it long-term. The short-term suggestion was to get rid of extra replicators that did no work anyway, only prompted error messages in logs.17:31
tdasilvazaitcev: yeah, i think those are good suggestions! simplify first to get a good handle on it running! i'd say have just one network for both types of traffic and just one config file17:32
tdasilvaper service per node if possible17:32
tdasilvabut that will require both changes to config files and to ring17:32
ybunkertdasilva: also i think that replication is also not working on existing nodes17:36
*** mikecmpbll has quit IRC17:37
ybunkertdasilva: if you send me a brief of the changes that i need to made to simple use one service per node and the changes that i need to do on the ring i can try that17:40
tdasilvaybunker: honestly i'd start by simplifying your configuration, right now it seems you have one configuration file for each disk. I would change to have just one configuration for a given node/service17:43
ybunkertdasilva: ok, lets go in that direction, for that i guess that i need to change also the rsyncd.conf file right?17:45
*** renich has joined #openstack-swift17:45
renichGood day, swifters! o/17:45
tdasilvaso i'd back up your /etc/swift dir in your node. then you should only have one config for the account server: account-server.conf17:46
renichI am wondering, I have an openstack-swift installation (keystone and swift) and it's on the latest version (Liberty). I was asked to do some bencharking but ssbench doesn't work anymore since it doesn't support v3 auth. How can I do this?17:46
tdasilvadelete the files under /etc/swift/account-server/*17:46
tdasilvarenich: liberty is not latest version17:47
ybunkertdasilva: http://pasted.co/f753363817:47
renichtdasilva: oh, hehee... well, thank you for the reality shot ;D17:47
renichtdasilva: oh, I meant Rocky17:48
renichSorry... ~_~17:48
ybunkertdasilva: bkp -> ok, delete files unders account-server -> ok17:49
tdasilvaybunker: now you need to adjust your account-server.conf to bind the correct ip:port and then change the ring for that node so that all disks have the same ip:port combo17:53
tdasilvafor both data and replication ip:port17:53
ybunkertdasilva: also do i need to change the rsyncd.conf file?17:54
tdasilvarenich: so taking a quick look at the ssbench here: https://github.com/swiftstack/ssbench/blob/master/ssbench/swift_client.py#L23117:54
renichtdasilva: yep17:54
tdasilvarenich: and checking the swift client here: https://github.com/openstack/python-swiftclient/blob/master/swiftclient/client.py#L564,L64817:54
renichtdasilva: ok17:55
tdasilvait doesn't seem like it would be super difficult to patch up a v3 support, but i don't have the time to do that right now17:55
tdasilvarenich: would you be able to send a PR to ssbench?17:55
tdasilvaybunker: pretty sure you will, but let's take one thing at a time, let's first the services running and rings updated17:56
tdasilvathen rsync17:56
renichtdasilva: my python skills don't add up to that much... !17:56
renichtdasilva: but I understand. Any other options other than ssbench that support v3? Or, how can I enable v2 auth in keystone just for that test?17:57
ybunkertdasilva: ok, for the ip:port relationship i need to specify rsync_module ={port} for each of the ports?17:57
ybunkertdasilva: or using vm_test_mode = yes will adapt with the rsync config ?17:59
tdasilvaybunker: i don't think you need vm_test_mode, that's really for a SAIO type of setup IIRC, for your rsync config i think you could have something like here: https://github.com/openstack/swift/blob/master/etc/rsyncd.conf-sample#L6,L1018:00
tdasilvarenich: if you are running liberty swift+keystone, doesn't that support v2 already? you should just be able to use that....OTOH i *think* for latest keystone, they have removed support for v318:01
notmynametdasilva: he's using rocky18:01
renichtdasilva: I was wrong. I am running rocky. The latest one.18:02
*** e0ne has joined #openstack-swift18:02
ybunkertdasilva: ok so account-server.conf file is like this:   http://pasted.co/b886d80a18:02
ybunkertdasilva: and rsync conf:  http://pasted.co/16351cf918:05
tdasilvaybunker: i changed your paste to openstack paste just so i can refer to line numbers: http://paste.openstack.org/show/747633/18:06
*** e0ne has quit IRC18:06
ybunkertdasilva: oh ok, great18:06
notmynamerenich: looking...18:07
tdasilvaybunker: for now commment out line 5 and let's add healthcheck to the pipeline in line 2618:07
tdasilvaybunker: then also add this: https://github.com/openstack/swift/blob/master/etc/account-server.conf-sample#L109,L11018:08
tdasilvaafter line 3218:09
tdasilvaybunker: have you changed your rings yet?18:09
tdasilvaaccount rings only for now18:09
ybunkertdasilva: done18:09
ybunkertdasilva: on the rsync do i leave it like the last one? or just change the account on the old one?18:10
tdasilvaybunker: oh sorry, for the rsync, i meant to change only the account first18:11
tdasilvayou said object servers is working fine, so i'd prefer not to touch it18:11
ybunkertdasilva: ok, no problem18:11
tdasilvaybunker: can you post your latest account-server, account-ring output and rsync.conf file again? also are you making changes to just one node for now?18:15
renichnotmyname: thanks!18:15
ybunkertdasilva: yes, just one node18:15
notmynamerenich: so the good news is that swiftclient supports keystone v3 just fine. the bad news is that at some point in the past ssbench inlined the client code18:15
notmynamerenich: I don't know if there were modifications or if it were just done to avoid dependencies. but if there were modifications, then it might be tricky to update the client. really just depends on what they were, if any18:16
*** hoonetorg has joined #openstack-swift18:17
ybunkertdasilva: account-server.conf (http://paste.openstack.org/show/747634/)18:17
notmynamerenich: for a basic test, maybe changing the `import ssbench.swift_client as client` lines to use swiftclient would be a good start for a test18:18
notmynameie change it to `from swiftclient import client`18:18
ybunkertdasilva: account-ring:  http://paste.openstack.org/show/747635/18:19
notmynamerenich: there are 3 instances of that line in the ssbench code. should be pretty easy to change those and see what breaks18:19
renichnotmyname: OK, I'll try that18:19
ybunkertdasilva: and finally the rsync:  http://paste.openstack.org/show/747636/18:20
*** e0ne_ has joined #openstack-swift18:21
tdasilvaybunker: let's try making changes to rings...do you have a back up of your builder files?18:23
tdasilvaif not, please make one18:23
ybunkertdasilva: yesç18:23
tdasilvaybunker: which node did you make the account-server config changes?18:23
ybunker10.1.1.19 -
*** zaitcev_ has joined #openstack-swift18:24
*** ChanServ sets mode: +v zaitcev_18:24
tdasilvaybunker: ok, so you need to change the ip port for both data and replication to just use
tdasilvayou will stop use for replication for now, ok18:26
renichnotmyname: https://paste.fedoraproject.org/paste/PAlzdapq3nnt9uUmmXKwXQ18:26
ybunkertdasilva: ok, for the 3 disks right? /srv/node/1, /srv/node/2 and /srv/node/318:26
*** gmann is now known as gmann_afk18:26
tdasilvaybunker: correct18:26
tdasilvaybunker: do you know the swift-ring-builder command to change the ip:port ?  the --help flag can be useful....18:27
ybunkertdasilva: if you got the command out there will appreciated :-)18:27
*** zaitcev has quit IRC18:27
renichnotmyname: so, now, to change all instances of client.DEFAULT_NETWORK_TIMEOUT to 20.0?18:28
ybunkertdasilva: do i need to remove it and then add it again? or is there any parameter and action to just change it?18:30
tdasilvaybunker: nope, just change, try this: swift-ring-builder account.builder set_info --ip --change-port 400018:30
tdasilvathen run `swift-ring-builder account.builder` to see if it worked18:30
notmynamerenich: I think there's a better way. it seems the inlined client set up a `network_timeout` but the upstream client now has a `timeout`18:31
renichI was about to edit client.py18:32
tdasilvaybunker: if it does, you can then run: `swift-ring-builder account.builder set_info --ip --change-replication-ip --change-replication-port 4000` to update replication ip:port18:32
notmynamerenich: so the change needs to be changing line 230 in worker.py to pass that in, but also update the references to where it's set18:32
renich<gulp>... OK. Will try that.18:32
renichnotmyname: so change: network_timeout=network_timeout) to network_timeout=timeout?18:33
renichthere is a connect_timeout as well. I saw that constant in ssbench's version as well18:34
ybunkertdasilva: done..  http://paste.openstack.org/show/747638/18:34
*** mikecmpbll has joined #openstack-swift18:36
tdasilvaybunker: just for sanity your drives are mounted as `/srv/node/[1..3]`, correct?18:36
ybunkertdasilva: yes18:36
ybunkertdasilva: for acct cont, and then `/srv/node/[4..12]` for objects18:37
renichnotmyname: not proficient in python so I need a bit more help, if you are willing to... :S18:37
tdasilvaybunker: ok, good, just for clarify, it's probably a good idea to add these two lines to your account-server.conf: https://github.com/openstack/swift/blob/master/etc/account-server.conf-sample#L8,L918:37
notmynamerenich: no, change it to `timeout=network_timeout`18:38
tdasilvaybunker: you ring looks good, now i'd run `swift-ring-builder account.builder write_ring` and distribute the account rings to all your nodes18:38
ybunkertdasilva: done18:38
tdasilvathen i'd try to run a healthcheck on the ip port from all your nodes18:39
tdasilvayou can also check rsync to make sure it's working ok18:39
tdasilvaif it all works, just repeat the process for all nodes18:39
*** pcaruana has quit IRC18:39
renichnotmyname: looks like this: http://paste.openstack.org/show/747640/18:40
*** e0ne_ has quit IRC18:41
renichAnd, when ran, it gives this: http://paste.openstack.org/show/747641/18:41
notmynamerenich: that's good, but above there where network_timeout is set, you'll need to change that too.18:42
notmynameyeah, the upstream version doesn't set a default timout18:42
renichOK, I will change all network_timeout instances to timeout, right?18:43
notmynameso the fastest thing to do is change every instance of `client.THE_TIMEOUT` to the actual default number that's in the ssbench client (either 10 or 20 seconds)18:43
renichit's 20.018:43
ybunkertdasilva: with what command can i run the healthcheck?18:45
tdasilva`curl -i`18:45
tdasilvaybunker: please run that from all your swift nodes to make sure they can all talk to this ip:port18:46
ybunkertdasilva: Ok on all18:48
renichnotmyname: OK, changed all client.DEFAULT*TIMEOUT to 20.0. Now, I get: swiftclient.exceptions.ClientException: Authorization Failure. Authorization Failed: Not Found (HTTP 404) (Request-ID: req-08639d7a-bd13-49b0-8ae2-41c7296a0247)18:48
notmynamethat's good!18:48
tdasilvaybunker: same for rsync?18:49
notmynameat least it's not syntax errors or missing variables18:49
renichnotmyname: yeah! Just FYI, `swift --os-auth-url http://localhost:5000/v3 --os-tenant-name redacted --os-username redacted --os-password redacted stat` works18:49
tdasilvaybunker: i think something like  `rsync rsync://pub@`18:49
notmynamerenich: so same creds with ssbench are getting a 40418:50
ybunkertdasilva: rsync up18:50
renichnotmyname: yep18:50
notmynamerenich: I'd probably look at cluster logs or turn on debug logging in ssbench next. see what's getting sent so I can find why the 404 is happening18:51
renichOK, I'll try that.18:51
ybunkertdasilva: rsync: failed to connect to ( Connection refused (111)18:52
tdasilvaybunker: mmm..and you restarted rsync right? after changes to the config file18:52
ybunkertdasilva: got it, the address was pointing to the replica, instead of the storage ip18:53
notmynamerenich: I need to head to lunch. I won't be on irc for a bit18:53
ybunkertdasilva: http://paste.openstack.org/show/747642/18:53
tdasilvaybunker: same output when running from all other nodes?18:54
ybunkertdasilva: yes18:54
renichnotmyname: man, thanks a ton for the help.18:55
tdasilvaok, how's the logs? do you see any traffic going into that account server?18:55
renichnotmyname: I'll keep at it.18:55
ybunkertdasilva: no, no traffic at all :-(18:55
ybunkerin fact inside the /srv/node/[1...3] there's no `accounts` directory18:56
tdasilvawell, we started from account-server and since nothing is being written to container server, there might be nothing to write to account server18:57
tdasilvaso i'd make the same changes to the container server18:57
ybunkertdasilva: do i need the changes on container also, right¿18:57
tdasilvayou will need to use another port18:57
renichSo, it seems ssbench is still looking for /v3/tokens: http://paste.openstack.org/show/747643/18:59
ybunkertdasilva: http://paste.openstack.org/show/747644/18:59
ybunkerits ok?18:59
renichIt seems it should be /v3/auth/tokes19:00
tdasilvaybunker: looks ok, just comment out line 319:01
ybunkertdasilva: ok19:01
ybunkertdasilva: applying changes on the ring file and replicating config19:04
ybunkertdasilva: ok, well, now im getting on the swift_container_server.log file:    container-replicator: ERROR rsync failed with 1019:07
renichI'll be back in a while. Going to get lunch as well.19:08
tdasilvaybunker: well you changed only one node, is the rsync error for that node? could be for another node19:09
ybunkertdasilva: let me change it on the other new nodes19:11
tdasilvaybunker: make sure that you make the change to the ring and then distribute the copy to all nodes19:12
ybunkertdasilva: ok, and then restart all the services? or no need for that?19:13
tdasilvaybunker: yeah because you changed the config19:13
tdasilvaybunker: just for future reference, when changing just the ring you don't need to restart services19:13
ybunkertdasilva: ok :)19:14
ybunkertdasilva: no accounts replication for the moment.. :(19:18
tdasilvaybunker: just to recap, are you changing all your container server config files/rings/rsync config?19:21
ybunkertdasilva: yes, but just on new nodes, do you want me to change also on the old nodes?19:21
tdasilvaybunker: can you post your latest ring?19:22
tdasilvacontainer ring19:22
ybunkertdasilva:   container ring http://paste.openstack.org/show/747646/19:24
tdasilvaybunker: are those weights representative of your disk sizes?19:25
ybunkertdasilva: yes, but for the new nodes (, and i need to set them to 50% of weight19:25
ybunkerbecause those disks are 400G and the old ones are 200G19:26
tdasilvaybunker: so on nodes like 10.1.1.[11-16] they are 200G ? and 19,20,21 they are 400G?19:27
tdasilvaor vice-versa?19:27
ybunkertdasilva: yes 10.1.1.[11-16] are of 200G19:27
ybunkertdasilva: and 19,20,21 400G19:27
tdasilvaoh wow, so your weights are really messed up too19:28
ybunkertdasilva: yep19:28
tdasilvaybunker: can you change the weight on 200 on 19,20,21 ? but this time instead of write-ring you will need to rebalance19:29
ybunkertdasilva: ok19:29
tdasilvaybunker: was thinking something like: http://paste.openstack.org/show/747648/19:33
tdasilvaafter rebalance, distribute rings to all nodes19:34
ybunkertdasilva: done19:38
notmynametimburke: note the ML message about pike extended maintenance19:38
tdasilvaybunker: can you post output of swift-ring-builder for account and container rings?19:38
ybunkertdasilva: accounts:  http://paste.openstack.org/show/747650/19:40
ybunkertdasilva: containers:   http://paste.openstack.org/show/747651/19:41
tdasilvaybunker: ok, have you done a rebalance and distributed rings to all nodes19:42
tdasilvaybunker: eventually you should adjust weight on 17 and 18 ...19:42
ybunkertdasilva: and then i got another problem... major problem... the objects...take a look in here:    http://paste.openstack.org/show/747652/19:43
ybunkertdasilva: on that19:43
ybunkertdasilva: do i need to change also the account and container on the OLD nodes?19:43
timburkenotmyname, looks fairly clean... what do we want to do about https://review.openstack.org/#/c/629402/ ?19:44
patchbotpatch 629402 - swift (stable/pike) - object-server can 409 in response to x-if-delete-at - 1 patch set19:44
tdasilvaybunker: yeah the weights on the object nodes look wrong too, but let's take one step at a time...19:44
ybunkertdasilva: nodes to are 4TB (and some nodes are at 98% of used disk), and then to are 2TB19:45
ybunkertdasilva: yep19:45
timburkei *guess* maybe there should be a client release for https://review.openstack.org/#/c/505092/ ? i'm kinda inclined to skip it and tell people to just upgrade to latest... python-swiftclient doesn't change much (for better or worse) and it should *always* work on old swift19:45
patchbotpatch 505092 - python-swiftclient (stable/pike) - Add support for versionless endpoints (MERGED) - 1 patch set19:45
tdasilvaybunker: sorry, lost track a bit...let's put object-server to the side for a bit, where are you at with account/container server?19:47
ybunkertdasilva: account/container on new nodes is working! :) thanks!!!! :-), but on old nodes do i also need to change to this new scheme of just one config file for account/container?19:48
tdasilvaybunker: you seeing data go into account/container dirs???19:48
ybunkertdasilva: yes! :)19:49
tdasilvaah cool19:49
notmynametimburke: I agree about swiftclient. I dont' see any need to release old versions19:49
tdasilvayeah, make same change to old nodes now19:49
ybunkertdasilva: ok19:49
tdasilvaybunker: how many proxy nodes do you have?19:49
ybunkertdasilva: 519:49
tdasilvaok, if they are different from any of these nodes, make sure you are copying rings to them too19:50
ybunkertdasilva: the thing is that rsync is using for account container.. but on the object-ring it still using the replication network
tdasilvaybunker: mmm...can you post the configs for the object server?20:04
ybunkertdasilva: sure20:04
ybunkertdasilva:   http://paste.openstack.org/show/747655/20:08
ybunkertdasilva: and object.builder (http://paste.openstack.org/show/747656/)20:09
ybunkertdasilva: i've to go now, can we continue tomorrow? i really appreciate your help with this :-) thanks!! i still cant believe the cluster that the old guy left to me.. he was wise to leave the company hahaha lol20:11
tdasilvaybunker: you are welcome, looks like you are almost ther20:12
*** e0ne has joined #openstack-swift20:20
*** ybunker has quit IRC20:34
notmynametimburke: no, I don't have strong feelings about pavel's old backport to pike. having just done the backports, I didn't particularly enjoy the hoops I had to jump through20:45
*** gmann_afk is now known as gmann20:54
openstackgerritTim Burke proposed openstack/swift master: py3: Stop using stdlib's putrequest(); it only does ASCII  https://review.openstack.org/64289321:19
*** e0ne has quit IRC21:26
openstackgerritMerged openstack/swift master: Stop overwriting reserved term  https://review.openstack.org/63949021:35
*** rcernin has joined #openstack-swift22:01
mattoliveraumorning, wow alot of scrollback lately.22:07
*** hoonetorg has quit IRC22:09
*** hoonetorg has joined #openstack-swift22:10
*** mikecmpb_ has joined #openstack-swift22:15
*** mikecmpbll has quit IRC22:16
*** ianychoi_ is now known as ianychoi22:47
*** tkajinam has joined #openstack-swift22:53
openstackgerritTim Burke proposed openstack/swift master: Fix quoting for large objects  https://review.openstack.org/57190523:11
openstackgerritTim Burke proposed openstack/swift master: py3: alternate approach for DLO  https://review.openstack.org/64292023:11
timburkei really *really* like the progress that p 642520 and p 642893 represent. there's something very reassuring about being able to run both unit and func tests for a middleware that's being ported...23:19
patchbothttps://review.openstack.org/#/c/642520/ - swift - Get functional/tests.py running under py3 - 5 patch sets23:19
patchbothttps://review.openstack.org/#/c/642893/ - swift - py3: Stop using stdlib's putrequest(); it only doe... - 1 patch set23:19
*** tristanC2 is now known as tristanC23:36
*** itlinux has joined #openstack-swift23:37
openstackgerritMerged openstack/swift master: Fix a typo  https://review.openstack.org/64264423:45

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