If you're always using `become_user: root` in your playbooks, maybe think about writing them differently! I have experience with Tower, and have never configured users to have any level of access beyond very, very basic SSH access.
1,215 karma · joined June 16, 2015
You _should_ be able to pass in a vault password as well, as part of any job? Are you doing something with vault in your inventory?
Only use io2 if you have a latency sensitive application or need more than 10,000 iops. Even then you can RAID10 some gp2 volumes together and with enhanced networking get I believe 30k iops out of one instance.
Firewalld on the other hand, I'm still figuring out (firewall-cmd is useful, but trying to translate iptables rules -> firewalld is proving harder than I expected)
CockroachDB heavily utilizes RocksDB.
I spent a total of $500 to have a .75ct diamond set in a ring this way.
I try to live on the CLI though so I've kinda forced myself to learn more about Git and the myriad of commands, but Tower was most certainly the best set of training wheels I could ask for.
Guides to doing auto failover and recovery:
https://dev.mysql.com/doc/mysql-utilities/1.5/en/utils-task-...
https://dev.mysql.com/doc/mysql-utilities/1.5/en/utils-task-...
Sometimes that involves using one container that you tightly control to do a bunch of different things -- e.g.: "fedora".
You may use a base (fully loaded) fedora container to run apache in one container, (fedora:httpd), mysql in another (fedora:mysql), and something like tomcat (fedora:tomcat).
The alternative, preferred in some (most?) instances, is to use something like Alpine and bake in the bare minimum of everything for every process.
When folks run a bunch of stuff in one container it's typically using something like circus or supervisord running at pid 1.
It's really interesting to hear that they could be tied so closely to Disney though.
That last sentence is important.
Interesting, I was looking into running single daemons (e.g.: nginx) as a unikernel (through rump kernels). This is certainly something different!
Edit: doing some research it simply seems that Hyperkit/MirageOS are supplementing docker (via Alpine Linux). I may still be missing something just by looking at the slides.
I asked a ton of times about their cloud stuff and just got re-directed back to dedicated servers. I got tired of it, went to AWS, and haven't looked back. Using reserved instances and scaling groups we're paying about 10% less per month for 8x the number of servers, and slightly more cpu/memory/disk overall (we had some pretty beefy stuff at Rackspace).
It's more akin to the iPhone 1 not including a jack then adding one later than the iPhone 7 removing it.
Another note: Original Gameboy games stuck way out the back. The GBA SP sure made a lot of sacrifices, and odd design choices but the fact that it fixed the biggest issue means a lot for it.
While Facebook is now completely unusable on my phone, and Reddit is very close (an example of too-much-JS-gone-wrong), going on Twitter is a blast of minty fresh air at my fingertips.
https://github.com/kimchi-project/kimchi/wiki/Communications
With pgsql, I can get a clear concise explain and if I disagree with what's happening (because I know exactly what my hardware is capable of) I can tune any query to be decently performant.
With mysql, you get... I mean explain is ok, but I wouldn't put it above that. "EXPLAIN ANALYZE" is my gold standard forever and ever. I even liked it more than SQL Server's equivalent; which is also fantastic.
Still cool that OpenBSD runs on one of those little tablets though!
Could you just use something like a health-check on a cluster system like zookeeper/etcd/consul/keepalived/... to simply peek at the lag time, and then mark a replica as unhealthy and regenerate your HAProxy config?
Just curious as I have very little experience with HAProxy. I do everything with consul right now and it works very well (previously I used keepalived + vrrp, or pacemaker/corosync but no multicast "in the cloud.").
I feel strongly about two things:
1) I screwed up at the beginning so hard (there were _no_ best practices to be found so it was a bit wild west) that I've come to the point where I need to use something else, or rewrite everything.
2) Terraform is best when you are in a silo by yourself, or you're using something to do the state applies for you (Atlas, or DIY through Jenkins and friends).
It does a lot right that other tools don't do (stringing together resources is a cinch), but it also behaves in strange things and the statefile is both a huge positive, and a huge negative.
If you need to move fast it's not a bad tool to choose at all.
The BIG caveat here is as follows -- If you have a mixed-cloud setup and use AWS, GCE, Azure, DigitalOcean, etc.. at the same time; It's probably hands down the best tool for managing everything.
Notes:
- I only use AWS. I use some of the other TF providers mixed in with it. (Consul, Datadog)
- I started from scratch (no AWS resources -> 100% Terraform), the general opinion seems to be this is the better place to start from.
- I use a majority of Hashicorp's stuff and am quite partial to liking their products. Terraform is something I have the most opinions on. I have no problems strongly suggesting Packer, Consul, Vagrant, and Vault to anyone.
- One of the main reasons I'm considering alternatives is that, at my current position, I'm having trouble getting folks to wrap their heads around Terraform.
This is my favorite part of the Linux community. Ask something that you aren't sure of, and if it's wrong, you'll get quite some volume of responses correcting you!