23david

9 ms·

31.
by 23david 10y ago
Mini Cooper S
32.
by 23david 11y ago
I've advocated for and implemented several InfluxDB installations in production over the last year+, and one of the considerations was always that non-alpha (prod-ready) clustering was always promised in the 'next version' th
33.
by 23david 11y ago
Agreed... why not find a way to allow employees to get liquidity by selling their equity as part of funding rounds? The fact that founders sometimes are able to participate seems to imply that it's a possibility for regular employees t
34.
by 23david 11y ago
Looking at the datacenter locations for AWS, Azure, GCE, Linode, softlayer and DO, it'd be challenging to develop reliable multi-cloud datacenter agnostic apps with any consistent backend datastore requirements. In the end, you may get
35.
by 23david 11y ago
Systemd-approved, nonetheless? “I believe in the rkt model,” said Lennart Poettering, systemd lead developer. “Integrating container and service management, so that there’s a 1:1 mapping between containers and host services is an excellent
36.
by 23david 11y ago
What derivative are you using?
37.
by 23david 11y ago
Providing open-source clients does not make AWS an open ecosystem. If anything, my sense is that the overall direction of the AWS platform has been to get more and more proprietary and closed with initiatives like Lambda and Redshift that c
38.
by 23david 11y ago
Wow didn't realize they'd deprecated lxc. Thx for pointing that out.. that seems to leave all the projects relying on libvirt for container support in an odd spot? I thought that Openstack for example used libvirt-lxc for their co
39.
by 23david 11y ago
Solomon Hykes @solomonstre @kelseyhightower TLDR "no actual downside for Docker users, but it makes it hard to for us to embrace-extend-extinguish" Today at 3:08 PM
40.
by 23david 11y ago
I've been using the latest Grafana release as an alternative to Kibana for visualizations. It now supports Elasticsearch as a db backend. Seems much faster and more stable than Kibana 4.
41.
by 23david 11y ago
Call and/or email Amazon support to fix ES issues?
42.
CS Docker Engine: Non-Free Commercialized Docker(docs.docker.com)
2 points by 23david 11y ago|0 comments
43.
Container Monitoring with Scope(weave.works)
1 points by 23david 11y ago|0 comments
44.
by 23david 11y ago
Based on what you've said about your current situation, I definitely think that you'd be better off staying on AWS. Have you looked into using reserved instances?
45.
by 23david 11y ago
Moving from AWS to DO will force you to handle a lot more devops/IT stuff to work around network and api reliability issues. So to make that worth it, it'd really depend on how much money you are looking to save and on the IT&#x2F
46.
by 23david 11y ago
In my experience, a bad manager can be far worse than having no managers. A management-less company may end up being adrift at sea, but that's a far better alternative than running into an iceberg or sailing into pirate-infested waters
47.
by 23david 11y ago
Ever try porting a customer using cloudformation templates and autoscaling groups over to another cloud service? Or reimplementing s3 or EBS semantics? It can be done, but definitely non-trivial... lockin++
48.
by 23david 11y ago
Very strange. I've never encountered something like that with any database or cache. Wonder if it's somehow related to the way that your cluster is setup? How big is this cluster? Are you writing and reading to the entire cluster,
49.
by 23david 11y ago
I agree that disk space has gotten a lot cheaper, but bandwidth speed hasn't increased tremendously. Binary sizes definitely are an issue. And re:memory, it's pretty tight on most end-user machines. By default, most laptops only c
50.
Do the Simplest Thing That Could Possibly Work(c2.com)
2 points by 23david 11y ago|0 comments
51.
by 23david 11y ago
On health: Even though you're young, try and still go to the doctor every once in a while for checkups. But even if you don't like going to doctors, don't just ignore pain in your body. For example, ignoring a sore wrist or b
52.
by 23david 11y ago
In my experience, this is mainly describing the sad state of sysadmin work at tech startups. Larger and profitable tech companies tend to take sysadmin work a bit more seriously and give more resources and authority (and pay...) to their Te
53.
by 23david 11y ago
This is known as the PID-1 issue, and ever since Docker first came out it's been a major source of frustration for many users who want to use Docker containers to run their existing workloads. It's not possible to run a Docker con
54.
by 23david 11y ago
LXD sounds like another (rkt also...) promising alternative to Docker for running containerized workflows. A few major differences that I can see between LXD and Docker are: a) the security model and focus, where LXD uses LXC natively for s
55.
by 23david 11y ago
Not sure if you're trolling, but I really hope you are...
56.
by 23david 11y ago
Not sure if it's a good idea for me to wade into that particular religious war... :-) Some good comments on both sides here: http://www.quora.com/Python-Web-Frameworks/What-are-the-adva... http://www.re
57.
by 23david 11y ago
If we're discussing templating languages, I definitely prefer Mako over Jinja2 and think it's much more appropriate for devops templating. But Jinja2 is the default in a lot of projects, including Saltstack and Ansible, and it&#x2
58.
by 23david 11y ago
Ansible is a good simple tool with a small learning curve so it's not very intimidating for developers. But it has its strengths and weaknesses just like everything else. Puppet, Chef and Saltstack are all fantastic tools. It all depen
59.
by 23david 11y ago
Is there a reason why Ansible fans feel it's important to hijack unrelated DevOps tooling articles on HN and chime in about how awesome they think Ansible is? It just seems rude, and reinforces the image that the Ansible community is e
60.
by 23david 12y ago
What's your experience been running it in production? Any gotchas?

More ›