Re: [Cloud-admin] Kubecon 2017 Offsite Outcomes and archiving

Replying to myself to separate out review from new thoughts :) Two things I wanted to comment on. 1) traffic control and thoughts 2) deployment naming 1) I think the conclusion was nftables did not have a TC equivalent and that current techniques were not able to replace our TC usage. We could get more savvy with targeting using nftables (or iptables) and potentially the nftables project would look at a traffic control type mechanism. I talked a little about where I stopped short in the existing implementation (of bastion resource QoS) at building a wrapper for TC and in trying to find all the avenues I went down a few years ago I found https://packages.debian.org/stretch/firehol which appears to be just that. It has the potential to be unwieldy being sprawling bash but super interesting (https://github.com/firehol/firehol/blob/master/sbin/fireqos). I /think/ https://wiki.nftables.org/wiki-nftables/index.php/Rate_limiting_matchings from the meeting doc ( https://office.wikimedia.org/wiki/Wikimedia_Cloud_Services/Offsite_Notes/ku…) would perform similar functions to the limit module in iptables which drops violators instead of managing a queue to ensure both ends are sane consumers within the defined throughput limits. I think this doesn't exactly fit our model. Need to talk to Arturo to confirm I grok this entirely :) Super excited about the possibility of making our TC setup potentially more dynamic and sane, and also moving to something more modern. 2) I think we should sidestep the meaningful names pitfall and go for something distinct but not inherently descriptive. Main will be problematic whenever it becomes not "main" in the implicit sense (see me naming something secondary that then becomes ...primary). Anything we try to brand w/ a relationship to use case has this issue. I have used colors before to this end "blue", "black", "orange" environments. That's just an example, I actually think we should go wholly generic and use numeric identify. depone, deptwo, depthree potentially. phonetic: "dep-one", "dep-two". Contextual "one" "two". We can move the server from "one" to "three". IDK. I hate pure numeric tagging less than other approaches I can think of. Not in love with "dep" as a prefix. Ideas needed. On Mon, Dec 11, 2017 at 9:01 AM, Chase Pettet &lt;cpettet(a)wikimedia.org&gt; wrote: -- Chase Pettet chasemp on phabricator <https://phabricator.wikimedia.org/p/chasemp/> and IRC