907 karma · joined July 27, 2015
Actually, since you're queuing up all the tweets to post them in one go, it should be feasible to add the out-of count to every tweet in the storm! That would be neat. But the last tweet should have it by convention.
Data Transfer OUT From Amazon RDS To Internet
First 1 GB / month $0.000 per GB
Up to 10 TB / month $0.090 per GB
Next 40 TB / month $0.085 per GBGenerally true, but "strategery" was actually coined by SNL writers for Will Ferrell, although it is frequently misattributed to Bush. The Bush administration did start using it internally tongue-in-cheek.
You point to imgadm and vmadm as superior solutions, but these appear to be "proprietary" (to use your own word) to SmartOS. Why not add SmartOS to your list of unnecessarily technologies and apply the same critical thinking? Triton appears to occupy the same space as OpenStack (Triton DataCenter), Kubernetes (Triton ContainerPilot), CoreOS (Triton SmartOS), and possibly other components, and it appears to use the same kernel-level containerization facilities as Docker and runC. You're using a competitor's vertically-integrated solution, so no, you don't need another stack. If you weren't using Triton you would be researching these alternatives. Your argument is akin to saying you don't need a car because you have a Buick, people who drive cars are using an unnecessary, proprietary mode of transport, and they should all just drive Buicks instead.
That brings us back to configuration management tools. You keep calling them proprietary, but the cores of all these products are open source! And while I agree with you that the client/server model used by Puppet, Chef, and SaltStack is unnecessary—although it does have benefits at scale—it's worth noting that Chef Zero and Ansible just use ssh-sshd. These tools are making the same system calls as your shell scripts, they're just doing them from Ruby or Python instead. So just to recap:
> I don't have to use proprietary, discrete systems;
They're not proprietary, they're open source, and you only need one of the four.
> I can leverage technology already built into the operating system;
They do: Ruby or Python and system calls.
> I don't need a client-server architecture like Chef or Puppet, ever (ssh-sshd is just fine, thank you!)
Okay, so use Chef Zero or Ansible.
Finally, your other main argument, against abstraction, does not hold water. Everything we do is an abstraction. Shell scripts are an abstraction. Why aren't you writing your configuration management in C? (Wait, why are you writing it in C instead of assembler?) On one hand, you have a portable, open source tool with a domain-specific language. On the other hand, you have each company creating their own proprietary (this is the correct use of "proprietary," by the way) tooling, and an engineer has to learn it from scratch every time they change jobs. You may think any engineer can walk in off the street and instantly grok your homegrown shell- and AWK-based big ball of mud, but you are probably wrong. If your solution is as good as you think it is—if it's portable, extensible, and easy to maintain—you should release it and we can add it to the list of available CM tools. If it's not, why are you reinventing the wheel?
Vagrant allows you to create reproducible development environments using shell scripts (by default), so it should be right up your ally. Docker is used to containerize applications. runC is the container runtime used by Docker. Kubernetes orchestrates containerized applications across a fleet of CoreOS (a minimal "Docker host" Linux) machines. OpenStack orchestrates your data center. They are discrete solutions because they do different things. Each piece of the puzzle does one thing and (hopefully) does it well. That philosophy should sound familiar to you!
Back to "writing shell scripts and encapsulating them in OS packaging": have you tried a configuration management tool? I used to be old school like you; specifically, maintaining a fleet of AIX instances using a healthy mix of Perl, ksh, and RPM. I too was resistant to the tide of new, quickly-evolving technologies. I started using Ansible about a year ago and it's changed my life. Don't be so quick to pooh pooh the idea that there just might be a better way to do things.
Once you start breaking your stack apart to 1) add redundancy, 2) isolate hardware for different workloads, and 3) scale the components independently of each other, the situation gets a little more interesting. Sure, you could run different clusters of Nginx for each of SSL termination, static content, cache and compress, etc. and have them reverse proxy to each other (and some people probably do this), but when you get to this evolution of your architecture, it's worth evaluating the different options for each layer of the stack. There's an argument to be made that e.g. HAProxy is a better load balancer, Nginx is a better static content server, Pound is a better SSL terminator, Varnish is a better caching and compressing reverse proxy, etc. (N.B. that I am not saying these things, I am just saying that they can be said.) If you're not serving static content at all—let's say you're presenting an API written in Elixir/Phoenix—it may not make sense to go with Nginx in the first place!
Regarding Varnish, specifically, I've found that it offers unparalleled power and flexibility when it comes to caching and compression. Yes, that power and flexibility comes at the cost of more complexity, but it's there when you need it. It offers different storage backends, including a pure memory backend; the ability to serve gzipped content directly from cache (for supported clients); PURGE and BAN HTTP verbs; synthetic responses; query string sorting; the ability to serve stale content while updating; ESI; and probably a whole bunch of other stuff I'm forgetting and/or have never used. Nginx and Nginx Plus may support some or all of these things, built-in or as modules... I'm not sure.
ENUM = [0, 1, 2].freeze
LOOKUP = {
:A => [1, 2, 3].freeze,
:B => [4, 5, 6].freeze
}.freeze
# or:
LOOKUP = {
:A => [1, 2, 3],
:B => [4, 5, 6]
}.tap { |s| s.values.each(&:freeze) }.freezeThis is a bit more Perlish (not that I'm an authority):
sub is_prime {
(1x$_[0]) !~ /^(?:.?|(.{2,}?)\1+)$/;
}
But perhaps less clear to a novice reader. You can also leave off the semicolon.* Thunderbolt 3 (from 1)
* USB 3.1 (from 3.0)
* NVMe (from SATA)
* LPDDR4 (from DDR3)
* An integrated GPU with sufficient power so as to eliminate the need for a dedicated GPU for my typical usage (from a 650M)
* More battery life / power efficiency
The specs for the MBPs that came out in late-2012 through mid-2015 weren't significant enough to justify an upgrade. It's not that I'm "desperate," and I can't speak for the GP, but this machine is starting to show its age (battery life, fan noise, etc.) and I really don't want to drop $2-3K for a new unit with mid-2015 specs.
$ whois theonion.com | grep -i 'name server'
Name Server: NS1.LINODE.COM
Name Server: NS2.LINODE.COM
Name Server: NS3.LINODE.COM
Name Server: NS4.LINODE.COM
Name Server: NS5.LINODE.COM
$ dig @ns1.linode.com theonion.com ns +short
$ dig @ns1.linode.com theonion.com a +shortI hope there's some wiggle room in there for folks who may know more but cater their resumes to what they want to do and/or the buzzwords recruiters are filtering by.