News for hackers. Stuff that matters.
Re:We're moving. Goodbye Rackspace. by MichaelGG on Monday November 08, 2010 @09:23PM (#1885032)
Have you looked at just buying the hardware and colocating it? $400 should get you half a cabinet. Bandwidth can be found for a few dollars a meg. As you're buying redundant servers, you can get refurb/ebay stuff and save on the upfront costs (who cares about next business day service replacemnt if you have spare parts?).
Re:We're moving. Goodbye Rackspace. by lsc on Monday November 08, 2010 @09:42PM (#1885072)
I wrote a thing about the pros and cons of doing that, but instead I thought it would be better to give you some objective numbers.

1 full rack with 15a of 120v power (remember, don't exceed 75% of a circuts rated potential, so that's really 11.25a) at he.net in freemont is going to set you back $400/month. $500/month with 100Mbps bandwidth. (more than you will need for now)

Now, you are talking between 5-7 low-power servers there.

You want to buy a metered/switched PDU ($400 or so new, $150 used)

one of my 8 core, 32GiB ram opterons with 4 disks is about $2500 in parts, new. I can't imagine anyone charging more than $500 to put the thing together.

Note, unless you have really cheap hardware guys and downtime costs you little, I'd avoid used hardware. I started on used servers, and I no longer buy used hardware that is user-serviceable. (I avoid used servers. But I may buy used switches.)

If you need racker/stackers I can point you at experienced guys who will be happy to work for $50-$60/hr, and people who can get the job done at half that. If you want more advanced hardware troubleshooting, double that for someone really good. but for that kind of money they should be able to set you up with an automated provisioning system. for comparison, I'll work for $100/hr if you are willing to deal with my inconsistent schedule.

Setting up a server should not take more than a few hours, including hooking up the serial console, etc... And hardware problems? figure on once every two years per server.

a lot depends on the quality of your provisioning setup (something like cobbler is good) and your serial console/rebooter setup. But it /can/ be a lot cheaper than 'the cloud' in many instances.

edit: added the bit about used hardware.

Re:We're moving. Goodbye Rackspace. by MichaelGG on Tuesday November 09, 2010 @01:48AM (#1885637)
Right, so, if they were quoted $3K a month, in a couple of months of self hosting, they'd have definitely recovered their investment, and then start saving a few K a month.

Your point about onsite hands is something I forgot. In the companies I've had, I've always had offices adjoining the datacenter. (I've been lucky to end up with such great spaces.)

If you don't have onsite hands, then fixing even minor hardware issues can be a major pain. If you do, then cheap users servers are fine, if your software is fault tolerant. If a machine goes down, others takeover in a minute and you have slightly less capacity. No big deal.

I just see these crazy high numbers for hosting, especially "cloud" stuff and don't get it. Cloud in particular seems to only make sense if you're actually elastic, or scaling up very fast. Amazon and so on's pricing, for "always on" servers, does not look that appealing.

Re:We're moving. Goodbye Rackspace. by lsc on Tuesday November 09, 2010 @04:39AM (#1885928)
Personally, I think the very best use case for "cloud" is backup servers. Think of it, run a 'small' instance to slave your database and other stuff to EBS storage, and once a month practice bringing up production on "the cloud" - cheapest and most complete backup system I can think of.
Re:We're moving. Goodbye Rackspace. by lsc on Tuesday November 09, 2010 @04:44AM (#1885940)
As for onsite hands, 95% of what you would go to the co-lo for can be done from your comfy chair if you have a good serial console/rebooter setup. Also, the he.net price includes "remote hands" service. Note, don't expect more than "remote hands" and make sure you clearly label everything... but you can usually avoid leaving the office.
Re:We're moving. Goodbye Rackspace. by adriand on Tuesday November 09, 2010 @09:16AM (#1886448)
I really appreciate your insight on this. I'm going to take this back to my team and discuss. Thanks.
Re:We're moving. Goodbye Rackspace. by 3pt14159 on Monday November 08, 2010 @09:33PM (#1885060)
Don't. It isn't worth it. Just use AWS or Rackspace or Linode. Outsource hardware management to people that do it for a living.
Re:We're moving. Goodbye Rackspace. by lsc on Monday November 08, 2010 @09:57PM (#1885099)
why not outsource your OS management and use shared hosting, engine yard or appengine? hardware guys willing to do the work of amazon can be had for very little money, even on a short-term contract basis.

there are situations where different levels of outsourcing are appropriate. And certainly, if your cost per compute node doesn't matter, few will fault you for going with amazon. But you should be aware that you are paying for that, and in some situations, having a high cost per compute unit will kill you.

Re:We're moving. Goodbye Rackspace. by 3pt14159 on Monday November 08, 2010 @10:15PM (#1885142)
This is a fair question, so I don't see why it should be downvoted.

The reason outsourcing hardware to AWS or Rackspace makes sense versus hiring hardware guys (usually) doesn't is that you introduce one more link in your failure chain. In My opinion it is far, far more likely that you and your hardware guy are going to mess up ZFS configuration somehow and have it fail when your app gets black swan traffic than Amazon going down. When it comes to Engine Yard, I'm all for that too, in the right circumstances, but you get fairly high lock in. I agree that you get that with AWS too, it just seems more likely that AWS will be around 10 years than it does Engine Yard. But sure, Engine Yard and Heroku are great.

Re:We're moving. Goodbye Rackspace. by lsc on Monday November 08, 2010 @11:08PM (#1885279)
filesystem user error can be just as deadly on aws as it can on your own hardware. either way, you need good backups.

While I agree that amazon itself is unlikely enough to go down that you can pretty much bet the company on it, any one server at amazon may go down at any time. Now, amazon has the huge advantage of being able to give you another server at any time, but you need to be prepared for that. any data on your local disk would be gone, and you need to be able to re-connect to your EBS store from only one instance. (many, many of the 'admin error' cases of data loss i've seen stemmed from mounting a network block device read/write on two different servers without a clustered file system.)

My point is just that amazon doesn't free you from the need for (and mistakes of) *NIX admins (like heroku, app engine and engine yard should.)

Re:We're moving. Goodbye Rackspace. by count on Tuesday November 09, 2010 @08:06AM (#1886273)
That's a good point - you could argue it doesn't free you from the need of a good admin, and it actually makes it more difficult to hire someone who knows what they are doing; good cloud SA skills are much more rare than good traditional SA skills.

When you can just drive to the datacenter and toss in some more disks or drop your new F5 on there (or hack it together with CARP), but instead have to be familiar with exactly what the restrictions and use cases around the cloud providers offerings are; the field of candidates just got painfully smaller, and probably more expensive.

Re:We're moving. Goodbye Rackspace. by jfine on Tuesday November 09, 2010 @03:38PM (#1887817)
Heroku and Engine Yard (for their cloud service) are just front ends to AWS anyway. Your basically paying them for the luxury of not having to deal with AWS. So as long as they don't get undercut by a competitor and all their customers flee, they should be around for a while. That or their owners get greedy, sell the companies, and the new owners move to "more economical hosting". Na, that never happens. ;-)
Re:We're moving. Goodbye Rackspace. by lsc on Thursday November 11, 2010 @01:40AM (#1893110)
right. Just like you are paying AWS for the luxury of not having to deal with hardware.

Both can be rational decisions (or not, depending on many factors) I'm just pointing out that the people who deal with racking and stacking (the sort that amazon allows you to fire) are rather a lot less expensive than Linux SysAdmins, the sort who app engine, heroku and engine yard allow you to fire.