justinhensley

tldr has been my daily driver for 1-2 years now, almost replacing man entirely. The community has contributed very useful examples.

I go to man once or twice for tools that are entirely new to me. Then, I use tldr until I have muscle memory or using a feature that is new to me.

I did not intend it that way. They handle something on the order of thousands of packages per shift. They aren't putting in extra work to be rough with even most of them.

I edited my comment because "gleeful" was misleading. All of them said that the primary reason for the rough treatment of packages was because they're trying to keep up with production and that they're incentives (bonuses) are volume base. It's a demanding job in a very fast paced environment. The people also have their managers coming by to periodically yell at them to "pick up the pace" or other more colorful language.

The guy who said he purposely damages things was burnt out from working there for 5+ years. It brought out a side in him that I didn't know existed honestly. I was pretty shocked when he told me about it. Outside of work, he was extremely chill and fun to be around.

Is there anything more here than a couple of scripts that start and stop ec2 instances when you manually provide an instance id?

Maybe I'm missing the point by viewing this repo on mobile.

That very well may happen. But in the article posted, it specifically mentions Miami asking for federal money to buyout areas at risk for flooding. The federal government said no.

It is a lot to ingest. Can you elaborate on the OpenStack development you are doing?

OpenStack refers to a number of different projects (Nova, Neutron, Horizon, etc). I would advise getting a high level understanding of how Nova, Neutron, and Cinder/Swift interoperate. Then drill in to Neutron. As with every other cloud platform I've worked with, most of the IaaS complexity lies in Networking, in my opinion. Neutron, and SDN in general, is a fairly complex topic depending on your experience with network architecture and administration.

I said elsewhere in the thread. If there is a better IaaS solution than OpenStack, then I would love to know about it.

I disagree with you that you need an IaaS solution to run containers on-prem, but realistically, yes you do need an IaaS solution

Are you using TripleO/Red Hat Platform Director? Can you share the size of your OpenStack environment?

When you say VMware 6.5, are you referring to ESXi aka vSphere Hypervisor? That is not a 1 for 1 replacement of OpenStack.

I have seen several successful implementations in the 18 months I've been working with OpenStack. There are definitely gotchas and low level (driver, hardware)issues you have to deal with. I never thought I would be so familiar with IPMI.

That said, OpenStack is an ambitious product. It essentially seeks to give you a lot of the functionality of AWS, except with on-premise infrastructure. That is a tall order. AWS is a multi-billion dollar effort that I assume has has far more engineers than the OpenStack project.

OpenStack is a complex solution to a very complex problem. Having worked with other commercial IaaS solutions, I will say I hands down prefer OpenStack to the others I've worked with.

If there is a private cloud solution that delivers the same/similar functionality of OpenStack with less admin overhead and more simplicity, then I want to hear about it.

Greg Brockman. It's in the second sentence of the post.

The goal of this project is to be able to check it from the command line. So while you're at the computer, you can check it via CLI rather than opening a browser.

I think the authors intent was just for his own use and some fun.

Just saw this. Nashville, TN.

I think it's especially true here though due to HN's crowd sourced quality control. The rules are largely adhered to by the user base as well, and it's not just an agree/disagree button.