Slashdot Mirror
Microsoft Joins Open Compute Project, Will Share Server Designs
1sockchuck writes "Microsoft has joined the Open Compute Project and will be contributing specs and designs for the cloud servers that power Bing, Windows Azure and Office 365. "We came to the conclusion that sharing these hardware innovations will help us accelerate the growth of cloud computing," said Kushagra Vaid, Microsoft's General Manager of Cloud Server Engineering. The company is also releasing its Chassis Manager software that manages its servers, fans and power, which which is now available on GitHub. "We would like to help build an open source software community within OCP as well," said Microsoft's Bill Laing. Microsoft's cloud server hardware is built around a 12U chassis that can house up to 24 server and storage blades, offering a different approach from the current Open Compute server and storage designs."
"We came to the conclusion that sharing these hardware innovations will help us accelerate the growth of cloud computing,"
I really don't get this so perhaps someone can explain: What benefit does this have for anybody?
Embrace, extend or extinguish? Which part are we on now?
I'm surprised to actually find that they chose Apache License for the project instead of their GPL-incompatible MS-PL. I have no idea what Chassis Manager is actually useful for (and a skeptic inside of me tells me that probably nothing unless you pay for their other products), but it's interesting to see that they actually released 36k lines of code as free software.
So many to choose from. On the hardware side, they didn't like the current hardware design that Facebook liked (with good reason) and so provided an entirely different set of design sensibilities. This isn't about enhanced standardization, this is about a nice-sounding venue by which to deliver requirements to bidders for MS datacenter equipment. I will say at first glance, I like MS's requirements better than Facebook requirements. The points that I'd worry about would be firmware requirements (MS tends to get insane with network protocols) and the unique IO design which limits the market of compliant equipment (basically, the same that can be said of IBM bladecenter, flex, Dell M1000, etc etc).
On the software side, you'll note that it's in .Net. It's very much not in the realm of typical open source datacenter operations projects. MS once again is stuck having to build the infrastructure themselves for lack of a wider community using their tooling for the purposes MS needs. Of course, MS has historically impressed me with how well they manage to do while being a 'lone wolf'.
XML is like violence. If it doesn't solve the problem, use more.
MS sees an overwhelming trend of Linux oriented software for operations management. They don't have the same mountain of people working to do similar stuff but with .Net. They want that mountain of companies and people building an ecosystem around .Net, but it's not happening naturally. MS has only the hope of putting out there and hoping to prime the pump.
The world has moved on. Sorry MS.
It looks like the skeleton of code to put into 'firmware' of the chassis manager. This suggests they believe the chassis manager should be running Windows as the embedded solution... Holy shit what a terrible idea for a standard, the cost of the module would increase to start with (a hardware design for that role runs 40-50 bucks, moving to atom doubles that) and the cost of the OS to run on top of it would be more than the hardware cost total.
this isn't your father's Microsoft.
never bring a twinkie to a food fight.
Azure is the bluish color #007FFF.
An Azure Cloud is the suffocating bluish smoke belched out by an engine that is reaching the end of it's useful life.
Microsoft is courting Linux workloads to run on their bluish smoke servers. Why would someone who has a business application that runs on Linux want to trust that to a company that has tried to destroy Linux and open source and is actively continuing to do so to this very day?
I'll see your senator, and I'll raise you two judges.
Ah, I remember when Microsoft did the same thing with the OpenGL ARB and more or less poisoned it, leaving OpenGL for dead once they had completed their mission. Also, W3C, Java and pretty much every other standard group they've sabotaged^H joined usually end up the same way.
So forgive me if I see this as yet another attempt at killing off open standards.
More reading
systemd is not an init system. It's a GNU replacement.
Microsoft isn't giving their server designs away out of the goodness of their hearts. They have a huge interest in getting people to move their workloads to Azure. The first step for most places has to be getting them off of VMWare or KVM onto Hyper-V/Windows Server. Next step is convincing enterprises to buy these whitebox server designs to save money on their on-premises stuff. Finally they'll make Azure too good a deal to pass up for the CIO crowd with the usual argument that you can fire most of your IT department. It's already super-easy to publish your applications right from Visual Studio to Azure...again, not an accident.
I actually think the whitebox design method is a good thing...IF...you have a dedicated staff working 24/7 to repair/replace sickly boxes, and the workload is such that a box is a box is a box. This works perfectly for large scale web apps backed by a SAN, or hypervisor hosts. It doesn't work as well for standalone application stacks that have semi-permanent physical server dependencies. Renting 3 servers in the cloud doesn't make as much sense as renting 3,000.
My company does a lot of standalone deployments of applications around the world, in places where network connectivity doesn't permit easy cloud access. It's getting harder to find vendors who aren't trying to steer us to the cloud. Microsoft is making it very difficult to purchase perpetual licenses of software, with the price of a negotiated Software Assurance deal being set less than the equivalent one time license fee [1]. Now that IBM just bailed out of the x86 server market, HP is pretty much the only vendor left making decent hardware for non-cloud applications.
I totally get why AWS, Azure and public clouds make sense. When you're running the back-end for an iPhone app, and need 40,000 web servers all cranking out the same content, it makes sense to rent that. But a lot of companies don't seem to get that it's more expensive to do the cloud thing if the servers are going to be permanent and you're hosting one of those boring line-of-business apps. Hopefully people will realize this before the last decent x86 server vendor quits selling non-cloud-optimized servers.
[1] Licensing SQL Server on multi-socket physical boxes is insanely expensive now compared to VMs. I had to add ESXi to our solution for a recent deployment just to save thousands of dollars on the database license for a low-powered app.
I dont know if anyones used Azure but my boss made me find a reason to shoehorn it into the infrastructure because microsoft swore our 25k in free credit for it was tied neatly to our license discount for Windows. it is a clusterfuck of unworkable web 2.0 line and symbol bullshit that is easily outranked and outclassed by even the most entry-level hosting providers in ease of use. heres a rundown of my experience:
1. signup. microsoft juggles you between 3 different portals, all of which basically mandate internet explorer, and a username with a microsoft TLD. now that im boatanchored to the rest of the redmond world, we can continue to provisioning?
2. no. now you have to apply for a service and confirm the subscription in email. what this means, i mean on a technical level, god only knows. its some ephemeral obfuscation imbued in the product to impart a sense of legitimacy in the process of your virtual cloud experience no doubt.
3. we have a subscription and now we can start provisioning images. you have about 10 different microsoft images and 2 linux images sanctioned by some third party entity no ones ever heard of. Linux VM's require a goofy disclaimer but come with a package selection feature, so i guess thats useful.
4. Windows or Linux, youve made your choice, and youre provisioning nicely but beware: navigating away from the provisioning page will cause the process to stop.
5. Whatever lofty dreams you had about microsofts commitment to cloud and scaleable architecture as a departure from their haggared burro of licensed OS and direct attached storage becomes an afterthought. Microsoft (as they did me) emails you stating they improperly provisioned your VM in the wrong datacenter and that you, not them, are now responsible for the fix. this requires you delete your entire VM and start over again.
6. you stare into the internet, your limit break clearly reached, and observe an ocean of other more capable and well established providers and players in this world of virualized SaaS and PaaS. the interface is clean, the support is in plain fucking english, and if you arent hounded to tie your active directory to it. the thought that anyone, or any group for that matter, would stop to give two shits in an open consortium of existing sucessful and dedicated players to consider an offering from a software company that for its entire existence has sought nothing but ruthless destruction of every other open standard in the world, is bad comedy.
to microsoft: no one cares, and I mean this in all sincerity. its not a troll or a flame its just a sad fact. your designs, your servers and your processes and procedures contextualized historically in their offering to the open anything community have been a complete farce. this isnt your cup of tea and it never has been. You're completely outnumbered, hopelessly outgunned, and the best you can do is peddle lock-in to traditionalist business models sadly manacled in mediocrity. Look at your phones, tablets, zunes, and everything youve fought so hard to make a part of the world thats forsaken you and just stop shoveling time and money into strategies you're laughably unqualified to adopt.
Good people go to bed earlier.