jayofdoom

I've been in the situation of an interviewer, having to painfully show the skills the recruiter edited into their resume to get them an interview.

I absolutely agree with OP about being worried about edits, except I generally take it to the maximum extreme and don't use dedicated external recruiters at all when looking for work.

A concrete example: a company might offer two ways of doing things:

- an "old way", which is more expensive, but more easily understood by sales and gives them more commission because it's base price is more expensive

- a "new way", which while cheaper and better from a "meta" business standpoint, doesn't bring in as much for an established sales person, because the overall sale would be smaller, and on top of that, they have to make the effort to understand how to sell the new way.

I've seen several higher-quality products get choked out because of this pattern happening, and sales being accidentally-incentivized to keep people in the old, pricier way of doing things.

ConEmu solves this problem really well. I use it on almost every windows machine I have.

If you look at the eclipse at all without glasses, you will cause permanent eye damage. It's worse than looking directly at a sun NOT during an eclipse.

Don't do what you suggest. Seriously.

Actually, archive.org has a copyright exemption from the Library of Congress for certain stuff (of which I think this falls into). http://archive.org/about/dmca.php

Thanks :). Glad to hear you liked the product.

There is a third group -- which I would place myself in. I feel a strong responsibility to an environment I work in; but I also have a need for a disconnect and work/life balance. I absolutely am not ok with people in group #2, but I think group #1 is similarly unhealthy -- being constantly aware of issues can lead rapidly to burnout.

This is why you have to have an on-call rotation, with an SLA (i.e. all pages are ack'd within ten minutes) with enforcement for people who regularly miss pages, and keep the life-disruption to one or two team members. Obviously, anyone who's worked on a large software product knows you might get an escalation even if not on-call, but that's a hugely different workload than being attached to a pager and having to respond to them.

Probably worth noting as well how many software products OpenBSD has contributed back to the overall free software world; things like OpenSSH, (edit: NOT OpenSSL), a more secure ntpd and inetd.

Even if you don't run OpenBSD, you benefit from it.

If it can do it for normal Rackspace Cloud instances, it can do it for OnMetal instances.

The ramdisk stuff is pretty cool. There's a generic howto on how to do this with CoreOS here: https://coreos.com/docs/running-coreos/bare-metal/booting-wi... -- look under "Adding a Custom OEM".

Of course you can also look at the code we used to implement it, which jroll linked above.

For the network, you're getting 2x 10Gbit connections, configured in an HA-Bond, and plugged into a real switch. There's no current dependency on a virtual networking layer.

Honestly? Using 512GB of ram is pretty hard. I learned during some of this that you can actually get tmpfs to be CPU limited if you try to write to it too quickly.

As we talk about here: http://developer.rackspace.com/blog/how-we-run-ironic-and-yo..., each instance is provisioned with redundant 10Gbit network links with minimal network over-provisioning in each cab.

I would say if you're running applications in the cloud, you should ship your logs and forgo logging them on disk. Or setup an awesome ES+Logstash cluster using IO nodes :).

You should've left off the last paragraph; I assumed you knew who I was :).

Here's the blog post, as promised: http://developer.rackspace.com/blog/how-we-run-ironic-and-yo...

1) I don't think prices have been announced yet.

2) They do have 32GB SATADOMs, but these are intended for boot media and configuration only. They are not intended for anything more than boot media. Think something like an SD Card in a solid-state machine.

3) Yes, I want this. No, we don't do it currently.

FWIW, we didn't build all this. Ironic existed long before we came around, we added a deploy driver and set it all up and exposed it for customers. We'll have a blog up shortly with exactly how we're running this in production.

The coolest part of all this is something nobody has mentioned here yet -- this is all on Open Compute hardware. When I managed servers, I always wanted access to the cool hardware and scale that companies like Facebook and Google had. Hopefully with OnMetal, we're going to give our customers the cool hardware I always wanted.

Edit: As a note, I'm a Racker and I work on the team that built this.

I'm using CoreOS to pxe an image to provision bare metal as part of Openstack Ironic. Check it out here: http://git.openstack.org/cgit/openstack/ironic-python-agent/...