*** gyee_ has quit IRC | 00:21 | |
*** dmorita has joined #openstack-swift | 00:32 | |
openstackgerrit | Samuel Merritt proposed a change to openstack/swift: Refactor object PUT to make EC easier to add https://review.openstack.org/114084 | 00:36 |
---|---|---|
*** Midnightmyth has quit IRC | 01:00 | |
*** tgohad has joined #openstack-swift | 01:09 | |
*** tsg has quit IRC | 01:10 | |
*** bill_az_ has quit IRC | 01:14 | |
*** sungju has joined #openstack-swift | 01:15 | |
*** shakamunyi has joined #openstack-swift | 01:17 | |
*** nosnos has joined #openstack-swift | 01:44 | |
openstackgerrit | Zhang Hua proposed a change to openstack/swift: Add distributed tracing capablities in logging. https://review.openstack.org/93677 | 01:46 |
*** haomaiw__ has quit IRC | 02:12 | |
*** tongli has quit IRC | 02:12 | |
*** haomaiwang has joined #openstack-swift | 02:13 | |
*** addnull has joined #openstack-swift | 02:15 | |
*** tgohad has quit IRC | 02:16 | |
*** addnull_ has joined #openstack-swift | 02:16 | |
*** addnull has quit IRC | 02:19 | |
*** addnull_ has quit IRC | 02:19 | |
*** addnull has joined #openstack-swift | 02:20 | |
*** atan8 has quit IRC | 02:20 | |
*** addnull has quit IRC | 02:20 | |
*** addnull has joined #openstack-swift | 02:20 | |
*** addnull has joined #openstack-swift | 02:21 | |
*** addnull has quit IRC | 02:21 | |
*** addnull has joined #openstack-swift | 02:21 | |
*** addnull has quit IRC | 02:22 | |
*** addnull has joined #openstack-swift | 02:22 | |
*** shakayumi has joined #openstack-swift | 02:24 | |
thurloat | good day / evening to sirs / ladies | 02:26 |
thurloat | our swift server appears to be running out of ephemeral ports for replication tasks | 02:27 |
thurloat | getting: object-replicator: Error syncing with node: .... EADDRNOTAVAIL | 02:27 |
*** shakamunyi has quit IRC | 02:28 | |
thurloat | netstat -napt | wc -l is outputting ~28k, mostly in TIME_WAIT | 02:29 |
thurloat | when they finally clear up, it looks like it starts ploughing through again until it runs out of ports and starts spewing the same errors | 02:29 |
*** alexiz has joined #openstack-swift | 02:30 | |
thurloat | two questions out of this: is it okay for these replication requests to get delayed like this?, and if I were to start tuning, would it be swift config to throttle the replicators or try massaging the system to time out requests quicker / increase the ephemeral ports count | 02:31 |
*** shakayumi has quit IRC | 02:34 | |
*** tsg has joined #openstack-swift | 02:41 | |
*** addnull has quit IRC | 02:52 | |
*** liuxf has joined #openstack-swift | 02:55 | |
*** liuxf has quit IRC | 02:55 | |
openstackgerrit | Takashi Kajinami proposed a change to openstack/swift: Ensure update of the container by object-updater https://review.openstack.org/99598 | 02:58 |
*** haomai___ has joined #openstack-swift | 03:03 | |
*** haomaiwang has quit IRC | 03:06 | |
*** chandankumar has joined #openstack-swift | 03:27 | |
*** chandankumar has quit IRC | 03:44 | |
*** gvernik has joined #openstack-swift | 03:49 | |
*** stevemac has joined #openstack-swift | 03:50 | |
*** tgohad has joined #openstack-swift | 03:51 | |
*** tsg has quit IRC | 03:54 | |
*** shakamunyi has joined #openstack-swift | 03:54 | |
*** stevemac has quit IRC | 03:55 | |
*** alexiz has quit IRC | 03:57 | |
*** gvernik has quit IRC | 03:58 | |
*** elambert has joined #openstack-swift | 04:03 | |
openstackgerrit | Takashi Kajinami proposed a change to openstack/swift: Ensure update of the container by object-updater https://review.openstack.org/99598 | 04:14 |
*** nexusz99 has joined #openstack-swift | 04:14 | |
*** ZBhatti has quit IRC | 04:26 | |
*** atan8 has joined #openstack-swift | 04:28 | |
*** nexusz99 has quit IRC | 04:32 | |
*** nexusz99 has joined #openstack-swift | 04:32 | |
*** nexusz99 has quit IRC | 04:34 | |
*** nexusz99 has joined #openstack-swift | 04:35 | |
*** nexusz99 has quit IRC | 04:41 | |
*** nexusz99 has joined #openstack-swift | 04:41 | |
*** nexusz99_ has joined #openstack-swift | 04:43 | |
*** nexusz99 has quit IRC | 04:43 | |
*** tgohad has quit IRC | 04:43 | |
*** nexusz99_ has quit IRC | 04:48 | |
*** nexusz99 has joined #openstack-swift | 04:49 | |
*** nexusz99 has quit IRC | 04:53 | |
*** tsg has joined #openstack-swift | 05:09 | |
*** joeljwright has joined #openstack-swift | 05:21 | |
openstackgerrit | OpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements https://review.openstack.org/88736 | 05:22 |
*** infotection has joined #openstack-swift | 05:22 | |
*** chandankumar has joined #openstack-swift | 05:25 | |
*** nshaikh has joined #openstack-swift | 05:26 | |
*** addnull has joined #openstack-swift | 05:27 | |
*** shakamunyi has quit IRC | 05:37 | |
*** elambert has quit IRC | 05:57 | |
*** gvernik has joined #openstack-swift | 06:17 | |
*** gvernik has quit IRC | 06:17 | |
*** k4n0 has joined #openstack-swift | 06:25 | |
*** nshaikh has quit IRC | 06:28 | |
*** ppai has joined #openstack-swift | 06:30 | |
*** atan8 has quit IRC | 06:55 | |
*** shakamunyi has joined #openstack-swift | 07:03 | |
*** nshaikh has joined #openstack-swift | 07:03 | |
*** shakamunyi has quit IRC | 07:08 | |
*** thurloat has quit IRC | 07:14 | |
*** thurloat has joined #openstack-swift | 07:15 | |
*** sungju has quit IRC | 07:32 | |
*** infotection has quit IRC | 07:41 | |
*** infotection has joined #openstack-swift | 07:41 | |
*** aix has joined #openstack-swift | 07:53 | |
*** shakamunyi has joined #openstack-swift | 08:04 | |
*** shakamunyi has quit IRC | 08:09 | |
*** geaaru has joined #openstack-swift | 08:21 | |
*** kragniz has quit IRC | 08:27 | |
*** kragniz has joined #openstack-swift | 08:29 | |
*** aix has quit IRC | 08:46 | |
*** ByteSore has joined #openstack-swift | 08:47 | |
ByteSore | morning all | 08:47 |
*** nexusz99 has joined #openstack-swift | 08:49 | |
ByteSore | I just installed openstack on Rhel7 and swift on another Rhel7 machine. following the installation manual on access.redhat.com. It said i need to run swift list to see if there is a connection to the proxy but all i get is bash: swift: command not found. is this changed? | 08:50 |
*** nexusz99 has quit IRC | 08:53 | |
*** mrmoje has joined #openstack-swift | 08:55 | |
*** shakamunyi has joined #openstack-swift | 09:05 | |
*** sungju has joined #openstack-swift | 09:06 | |
*** homegrown has joined #openstack-swift | 09:07 | |
*** shakamunyi has quit IRC | 09:09 | |
*** bkopilov has quit IRC | 09:17 | |
*** aix has joined #openstack-swift | 09:24 | |
*** tsg has quit IRC | 09:34 | |
*** sungju has quit IRC | 09:39 | |
*** sungju has joined #openstack-swift | 09:47 | |
*** mrmoje_ has joined #openstack-swift | 09:54 | |
*** dmorita has quit IRC | 09:55 | |
*** mrmoje has quit IRC | 09:56 | |
*** Midnightmyth has joined #openstack-swift | 10:02 | |
*** shakamunyi has joined #openstack-swift | 10:06 | |
*** shakamunyi has quit IRC | 10:10 | |
*** aswadr has quit IRC | 10:12 | |
*** mkollaro has joined #openstack-swift | 10:19 | |
*** bkopilov has joined #openstack-swift | 10:28 | |
*** addnull has quit IRC | 10:41 | |
*** haomai___ has quit IRC | 10:50 | |
*** shakamunyi has joined #openstack-swift | 11:07 | |
*** shakamunyi has quit IRC | 11:11 | |
*** nexusz99 has joined #openstack-swift | 11:26 | |
*** ppai has quit IRC | 11:29 | |
*** mkerrin1 has quit IRC | 11:38 | |
*** zul has joined #openstack-swift | 11:57 | |
*** shakamunyi has joined #openstack-swift | 12:07 | |
*** sungju has quit IRC | 12:08 | |
*** shakamunyi has quit IRC | 12:11 | |
*** nosnos has quit IRC | 12:13 | |
*** Midnightmyth has quit IRC | 12:19 | |
*** traz_ has quit IRC | 12:30 | |
*** zul has quit IRC | 12:44 | |
*** zul has joined #openstack-swift | 12:50 | |
*** bnelson has joined #openstack-swift | 12:54 | |
*** aix has quit IRC | 12:57 | |
*** bill_az_ has joined #openstack-swift | 12:57 | |
*** shakamunyi has joined #openstack-swift | 13:03 | |
*** xianghuihui has joined #openstack-swift | 13:06 | |
*** xianghui has quit IRC | 13:09 | |
*** pberis has quit IRC | 13:11 | |
*** pberis has joined #openstack-swift | 13:12 | |
*** xianghuihui has quit IRC | 13:13 | |
*** shakamunyi has quit IRC | 13:19 | |
*** openstackgerrit has quit IRC | 13:21 | |
*** sas has joined #openstack-swift | 13:33 | |
*** shakamunyi has joined #openstack-swift | 13:36 | |
*** zul has quit IRC | 13:39 | |
*** Midnightmyth has joined #openstack-swift | 13:42 | |
*** nexusz99 has quit IRC | 13:42 | |
*** zul has joined #openstack-swift | 13:49 | |
*** k4n0 has quit IRC | 13:55 | |
*** openstackgerrit has joined #openstack-swift | 14:00 | |
*** tongli has joined #openstack-swift | 14:11 | |
*** dmsimard_away is now known as dmsimard | 14:11 | |
*** mrmoje_ has quit IRC | 14:17 | |
*** mrmoje has joined #openstack-swift | 14:19 | |
*** aix has joined #openstack-swift | 14:20 | |
*** tdasilva has joined #openstack-swift | 14:22 | |
ByteSore | that one is fixed.. | 14:25 |
ByteSore | does someone know how to fix this? swift: ERROR Insufficient Storage 192.168.0.102:6002/accounts | 14:25 |
ByteSore | i get it when i run swift list | 14:25 |
*** mrmoje has quit IRC | 14:29 | |
*** tsg has joined #openstack-swift | 14:30 | |
openstackgerrit | Thiago da Silva proposed a change to openstack/swift: moving object validation checks to top of PUT method https://review.openstack.org/115995 | 14:35 |
openstackgerrit | Thiago da Silva proposed a change to openstack/swift: code shuffle post expired headers refactor https://review.openstack.org/112804 | 14:45 |
openstackgerrit | Thiago da Silva proposed a change to openstack/swift: moving object validation checks to top of PUT method https://review.openstack.org/115995 | 14:45 |
*** mwstorer has joined #openstack-swift | 14:50 | |
*** nshaikh has quit IRC | 14:55 | |
*** goodes has quit IRC | 14:56 | |
*** goodes has joined #openstack-swift | 14:57 | |
*** astellwag has quit IRC | 14:58 | |
*** mjseger has quit IRC | 15:02 | |
*** astellwag has joined #openstack-swift | 15:05 | |
*** zul has quit IRC | 15:16 | |
*** mkollaro has quit IRC | 15:19 | |
notmyname | ByteSore: I'm assuming that you're getting that message when you actually think you have plenty of space available? | 15:30 |
*** occupant has quit IRC | 15:31 | |
notmyname | thurloat: look at setting tcp_tw_recycle and/or tcp_tw_reuse | 15:33 |
notmyname | thurloat: eg http://www.fromdual.com/huge-amount-of-time-wait-connections | 15:33 |
notmyname | thurloat: (dated, but still generally good info) http://docs.openstack.org/developer/swift/deployment_guide.html#general-system-tuning | 15:33 |
*** infotection has quit IRC | 15:34 | |
openstackgerrit | Thiago da Silva proposed a change to openstack/swift: Storage Policy defined constraints middleware https://review.openstack.org/113325 | 15:34 |
*** cebruns has quit IRC | 15:34 | |
thurloat | thanks notmyname, I see that it's an RTFM that we missed setting it up. | 15:35 |
thurloat | will apply asap | 15:36 |
*** chandankumar has quit IRC | 15:36 | |
*** infotection has joined #openstack-swift | 15:37 | |
notmyname | thurloat: one other thing to consider is that it may be rsync chewing through the ports too. check what's goin on there, and see if you may need to limit how many rsync connections are allowed at once | 15:37 |
thurloat | That change dropped the connection count to a much more reasonable ~8k | 15:38 |
thurloat | currently not seeing many rsync connections open, will keep my eye out for it. | 15:39 |
notmyname | cool | 15:39 |
*** annegentle has joined #openstack-swift | 15:40 | |
thurloat | notmyname: would there have been any replication failures because of those errors? or does it pick up where it leaves off on failure? | 15:40 |
notmyname | thurloat: it picks up where it leaves off (sortof. the answer to the spirit of your question is "yes") | 15:40 |
thurloat | i.e. some objects not 3x replicated | 15:40 |
notmyname | thurloat: that being said, you can run the replicator in a "once" mode and even give it a specific drive or partition to replicate. | 15:41 |
*** zul has joined #openstack-swift | 15:42 | |
notmyname | thurloat: swift-dispersion-report is good for letting you know what's going on there (if you need to worry about some partition). also, you can use swift-ring-builder to find common partitions eg if you have multiple failed devices in the cluster | 15:42 |
*** mwstorer has quit IRC | 15:44 | |
notmyname | ok, I'm out for a bit. time to get ready to go in to the office and do the meetings | 15:46 |
*** zslot has joined #openstack-swift | 15:51 | |
thurloat | thanks again for the guidance notmyname! | 15:51 |
*** DisneyRicky has quit IRC | 15:55 | |
*** infotection has quit IRC | 15:56 | |
*** gyee_ has joined #openstack-swift | 15:59 | |
*** DisneyRicky has joined #openstack-swift | 15:59 | |
*** aix has quit IRC | 16:00 | |
openstackgerrit | Samuel Merritt proposed a change to openstack/swift: Let admins add a region without melting their cluster https://review.openstack.org/115441 | 16:00 |
*** infotection has joined #openstack-swift | 16:01 | |
*** DisneyRicky has quit IRC | 16:03 | |
*** mwstorer has joined #openstack-swift | 16:04 | |
*** aix has joined #openstack-swift | 16:13 | |
*** homegrown has quit IRC | 16:13 | |
*** DisneyRicky has joined #openstack-swift | 16:18 | |
*** mwstorer has quit IRC | 16:20 | |
*** elambert has joined #openstack-swift | 16:21 | |
*** aix has quit IRC | 16:21 | |
*** infotection has quit IRC | 16:30 | |
*** mwstorer has joined #openstack-swift | 16:33 | |
*** zul has quit IRC | 16:34 | |
bnelson | I had a question about how to prevent unauthenticated connections to the swift services. The proxy server has authentication checking in the pipeline, but the object, container and account servers don't. | 16:35 |
*** infotection has joined #openstack-swift | 16:35 | |
bnelson | Is there a way to enforce authenticated connections to those servers? If I add auth checking to their pipelines, will that cause problems when the swift services themselves (reaper, replicator, etc) need to contact the object, container and account servers? | 16:36 |
peluse | bnelson: that's because, by design, those should be on a protected network (they don't communicate with clients directly) | 16:36 |
peluse | bnelson: see http://docs.openstack.org/security-guide/content/object-storage.html | 16:37 |
peluse | bnelson: wrt your question on securing the back-end servers, will let someone else field that one, never thought about it before :) | 16:38 |
bnelson | Thanks. I'll look into that link. I think I should be able to structure my setup so that the backend servers only listen on private networks. But I would be interested in any approaches which could secure those backend servers when they are on the external network. | 16:39 |
*** mwstorer has quit IRC | 16:44 | |
*** zul has joined #openstack-swift | 17:00 | |
*** mwstorer has joined #openstack-swift | 17:07 | |
notmyname | bnelson: peluse just gave you excellent advice. some other things you could do would be to keep the IP manifest of the other swift servers (you've actually already got this in the ring) and then set up firewall rules so only those IPs can connect | 17:12 |
notmyname | bnelson: we've talked about adding tls to the proxy->storage connections. it's certainly good in some deployments, but it's also pretty expensive (cpu/throughput) | 17:13 |
notmyname | bnelson: there is another option. /me goes to look for link | 17:13 |
notmyname | bnelson: peluse: see https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests | 17:13 |
notmyname | old idea, but nobody has actually prioritized it enough to work on it | 17:14 |
notmyname | basically, hmac sign the requests and reject bad sigs | 17:14 |
notmyname | doesn't encrypt data, but would prevent malicious messages | 17:14 |
bnelson | notmyname: thanks. that's a good idea, too. So it looks like the securing the backend services is accomplished by limiting network access. Thanks for clarifying that | 17:15 |
notmyname | yup | 17:15 |
notmyname | and I'd love to see that blueprint implemented | 17:15 |
wer | I just generate an rsync config every few minutes from the ring. Cause sad or migrating hardware with incorrect ring info can be problematic. | 17:15 |
wer | I think it happened to me first time I removed a node and built a new cluster..... | 17:16 |
wer | It's lame but it works. | 17:16 |
notmyname | wer: "problematic" == data moved needlessly or otherwise to the "wrong" place? | 17:16 |
openstackgerrit | paul luse proposed a change to openstack/swift: Make some sqlite UPDATE calls only to records that have changed https://review.openstack.org/115775 | 17:17 |
wer | problematic mean.... it died... or someone did something. | 17:17 |
notmyname | wer: hmm...that does sound "problematic" ;-) | 17:17 |
wer | If a machine comes up with old ring info for example. | 17:17 |
wer | Or if you forget to removed from a cluster.... or rings are not fully distributed yet. | 17:18 |
notmyname | wer: but we expect different versions of the ring to be in the cluster at the same time. ie you can't atomically deploy a new ring to 100+ servers at the exact same time. so if you found an issue, I'd like to work through it to see i there are things we can do to make your life easier | 17:18 |
wer | So, I just deleted a node in a cluster. And was standing up a new cluster..... The new node was on the same ip. The cluster started dumping into it.... the new cluster (which had other nodes) began to replicate it :) | 17:19 |
*** cebruns has joined #openstack-swift | 17:21 | |
*** tong_ has joined #openstack-swift | 17:23 | |
notmyname | wer: yes, I could imagine that would cause problems. essentially you're telling your 2 independent swift clusters that they overlap. and that will, in almost all cases, probably not turn out well | 17:24 |
*** annegentle has quit IRC | 17:24 | |
wer | My solution was to have each node generate an rsync config from it's point of view every few minutes and that stopped that behavior.... However I am using a pretty simple ring. All 3 rings are the same. | 17:24 |
wer | yeah it was fun. I had made the assumption that the ring hashes prevented that.... But no, it's just rsync... and I still don't know how I would clean up a scenario like that. But I can tell you it totally happens. And in a large system, it could go unnoticed. | 17:25 |
*** tongli has quit IRC | 17:26 | |
wer | so why wouldn't you use the swift_hash_path_suffix/prefix for this? I guess I need to go remember what those are supposed to do again. But I agree tls would be too expensive. Another auth would be a pain. But with a more complex ring structure one or both might need to be used. | 17:29 |
wer | derp. placement is what they are used for :) yeah, cleanup could be a pain. | 17:31 |
wer | with an overlap like that. | 17:31 |
*** joeljwright has quit IRC | 17:31 | |
notmyname | ya, just hash salts | 17:33 |
*** chandankumar has joined #openstack-swift | 17:34 | |
*** zul has quit IRC | 17:34 | |
wer | maybe you oculd use them with rsync.secrets or something. And call it done. /etc/rsyncd.secrets prefix:suffix | 17:35 |
*** chandankumar has quit IRC | 17:37 | |
*** cebruns has quit IRC | 17:41 | |
*** cebruns has joined #openstack-swift | 17:46 | |
*** sas has quit IRC | 17:48 | |
*** tongli has joined #openstack-swift | 17:48 | |
*** cebruns has quit IRC | 17:51 | |
*** tong_ has quit IRC | 17:52 | |
*** cebruns has joined #openstack-swift | 17:53 | |
*** geaaru has quit IRC | 17:53 | |
*** pberis has quit IRC | 17:57 | |
*** Midnightmyth has quit IRC | 17:59 | |
*** annegentle has joined #openstack-swift | 18:00 | |
*** annegentle has quit IRC | 18:06 | |
*** annegentle has joined #openstack-swift | 18:11 | |
*** morganfainberg is now known as morganfainberg_Z | 18:13 | |
*** mrmoje has joined #openstack-swift | 18:26 | |
*** shakamunyi has quit IRC | 18:27 | |
*** occupant has joined #openstack-swift | 18:30 | |
*** zul has joined #openstack-swift | 18:35 | |
*** gyee_ has quit IRC | 18:36 | |
*** zul has quit IRC | 18:37 | |
*** zul has joined #openstack-swift | 18:46 | |
*** morganfainberg_Z is now known as morganfainberg | 18:47 | |
openstackgerrit | Jesse J. Cook proposed a change to openstack/python-swiftclient: Python sessions, streaming, and increased pool https://review.openstack.org/116065 | 18:48 |
*** Midnightmyth has joined #openstack-swift | 18:50 | |
*** tsg has quit IRC | 19:01 | |
*** zul has quit IRC | 19:03 | |
tdasilva | clayg: thanks for the review on 115995 | 19:07 |
*** tongli has quit IRC | 19:10 | |
clayg | tdasilva: I think it's a great cleanup; I'm going try and figure out what it is I think I should know about the content-length/transfer-encoding thing | 19:11 |
tdasilva | ok...i was trying to maintain the same functionality | 19:12 |
clayg | tdasilva: acctually; any isnight you have might be helpful | 19:12 |
tdasilva | in that case, the check_object_creation had a check to make sure content-length or transfer-encoding was provided | 19:12 |
clayg | tdasilva: well it seemed like the KeyError was trying to drive at a subtle distinction between some variation in how the client presents the Content-Length header? | 19:12 |
clayg | tdasilva: yeah I thought maybe somehow the existing checks in the controller were already making that distinction; or at least enough of one to decide if the request was deemed "valid" | 19:13 |
*** mwstorer has quit IRC | 19:13 | |
tdasilva | right..so i removed the check in check_object_creation | 19:13 |
clayg | I see no harm in moving that logic into the check function - but I wasn't sure if the result was exactly the same? maybe it worked out the same in practice | 19:13 |
tdasilva | and added to swob | 19:14 |
clayg | oh; is that all that happened? | 19:14 |
tdasilva | it's what i tried to do :-) | 19:14 |
tdasilva | but i'm glad you are double-checking | 19:14 |
tdasilva | clayg: and the ml not being none was a copy-paste from the PUT | 19:15 |
tdasilva | in controllers/obj.py | 19:16 |
*** zul has joined #openstack-swift | 19:16 | |
tdasilva | so the issue is that we had a call in controllers/obj.py to message_length which was ok if there was no content-length or transfer-encoding | 19:17 |
clayg | bah; i can't see it :'( | 19:17 |
tdasilva | it was ok, because later on in the PUT function we added content-length right before calling check_object_creation | 19:17 |
clayg | I'm going to just test it; if it works it's fine :D | 19:18 |
tdasilva | hehehe...sorry if i'm confusing | 19:18 |
clayg | no no that's not it - I think the code was confusing to begin with because we were checking basically the same stuff in different places different ways | 19:19 |
clayg | which is why it's so good to get it consolidated - we'll acctually have a chance at understand what all that crap is trying validate and what our rules acctually ARE | 19:19 |
tdasilva | clayg: https://github.com/openstack/swift/blob/master/swift/proxy/controllers/obj.py, look at lines 495, 502, 543, 550 | 19:19 |
tdasilva | exactly...that's what i was trying to do | 19:20 |
tdasilva | just to simplify that code | 19:20 |
*** mwstorer has joined #openstack-swift | 19:21 | |
*** zul has quit IRC | 19:21 | |
tdasilva | clayg: what I'm going to try to do is write up a gist of the code flow before and after, and maybe that will help in finding any issues | 19:23 |
*** morganfainberg has quit IRC | 19:25 | |
*** morganfainberg has joined #openstack-swift | 19:27 | |
clayg | did anyone else have any issues with the new futures depends on the SwiftServices change for python-swiftclient? https://review.openstack.org/#/c/85453/ | 19:33 |
*** zul has joined #openstack-swift | 19:36 | |
*** bobby2_ is now known as bobby2 | 19:39 | |
*** joeljwright has joined #openstack-swift | 19:56 | |
joeljwright | clayg: thanks for taking a look at python-swiftclient patch 85453 | 19:59 |
joeljwright | clayg: are you still having issues importing/using the futures? | 20:00 |
joeljwright | clayg: I'm completely baffled by the behaviour you're seeing | 20:00 |
*** mrmoje has quit IRC | 20:03 | |
*** Midnightmyth has quit IRC | 20:08 | |
*** marcusvrn has quit IRC | 20:11 | |
*** morganfainberg is now known as morganfainberg_Z | 20:31 | |
openstackgerrit | A change was merged to openstack/python-swiftclient: fixed unit tests when env vars are set https://review.openstack.org/115131 | 20:34 |
*** bsdkurt has quit IRC | 20:45 | |
*** morganfainberg_Z is now known as morganfainberg | 20:47 | |
*** zul has quit IRC | 21:00 | |
*** joeljwright has left #openstack-swift | 21:02 | |
clayg | what version of setuptools is everyone on these days? pip freeze | grep -i setuptools is not showing me anything (!?) | 21:06 |
clayg | I had python-setuptools installed on my precise which never gave me issue before (the system packaged setuptools with lucid was a disaster of course) - but when trying to get the futures depends installed for the swiftclient change I saw my old friend TypeError dist must be a Distribution | 21:07 |
goodes | has anyone had luck using the code 'Red Hat Hackathon' to book the room at the group rate? | 21:13 |
openstackgerrit | A change was merged to openstack/swift: Fix sporadic false failure in xprofile unit test code (master) https://review.openstack.org/115292 | 21:20 |
*** tsg has joined #openstack-swift | 21:32 | |
*** pberis has joined #openstack-swift | 21:36 | |
peluse | goodes: I picked a Marriott that's somewhere close by I think (I hope) | 21:37 |
goodes | peluse: did not work on the website, so ended up calling them, that worked | 21:39 |
*** annegentle has quit IRC | 22:04 | |
*** bill_az_ has quit IRC | 22:08 | |
clayg | has anyone tried to build python-swiftclient docs like... ever? | 22:16 |
clayg | I *think* they're a thing? http://docs.openstack.org/developer/python-swiftclient/ | 22:16 |
clayg | there's a tox command for "docs"? | 22:16 |
*** erlon has quit IRC | 22:20 | |
*** dmsimard is now known as dmsimard_away | 22:29 | |
*** annegentle has joined #openstack-swift | 22:34 | |
mattoliverau | Morning all | 22:35 |
*** mrmoje has joined #openstack-swift | 22:37 | |
*** shakamunyi has joined #openstack-swift | 22:37 | |
clayg | joelwright: where'd you go!? | 22:38 |
*** sungju has joined #openstack-swift | 22:38 | |
*** annegentle has quit IRC | 22:39 | |
openstackgerrit | Clay Gerrard proposed a change to openstack/python-swiftclient: add some autodoc on swiftclient.service https://review.openstack.org/116120 | 22:40 |
*** shakamunyi has quit IRC | 22:41 | |
clayg | notmyname: do you or anyone you care about have a process around alerting for new depends (e.g. swiftclient post services patch will depend on futures 2.1.3, which may not have system packages on some distros e.g. precise has 2.1.2) | 22:44 |
mattoliverau | Should we rely on pip rather than system packages then? | 22:46 |
mattoliverau | Cause isn't that what requirements.text is all about | 22:46 |
mattoliverau | *Txt (damn auto complete) | 22:47 |
*** shakamunyi has joined #openstack-swift | 22:51 | |
*** annegentle has joined #openstack-swift | 22:52 | |
*** zul has joined #openstack-swift | 22:55 | |
*** pberis has quit IRC | 22:59 | |
*** annegentle has quit IRC | 23:05 | |
clayg | mattoliverau: where "we" is people who develop on these code bases or people managing deployments of these services? | 23:05 |
*** annegentle has joined #openstack-swift | 23:05 | |
*** mrmoje has quit IRC | 23:05 | |
*** pberis has joined #openstack-swift | 23:08 | |
*** zul has quit IRC | 23:17 | |
*** annegentle has quit IRC | 23:22 | |
mattoliverau | clayg: good point, Dev, testing and in ci testing where I guess can get away with with pip. I work with one of the PyPi core Dev/maintainers (Richard Jones) so I'm probably just biased :) | 23:27 |
*** acoles has quit IRC | 23:33 | |
*** tsg has quit IRC | 23:51 | |
*** annegentle has joined #openstack-swift | 23:52 | |
*** annegentle has quit IRC | 23:57 | |
*** tsg has joined #openstack-swift | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!