Open source standards created by Microsoft in collaboration with chipmakers establishes a foundation for future cloud services development.
During the first week of March 2017, in a series of announcements that likely flew under the radar of most people, Microsoft announced collaborative efforts with several semiconductor chipmakers, including Intel, NVIDIA, AMD, Qualcomm, and Cavium. The announcements came out of a fairly obscure conference called the 2017 Open Compute Project (OCP) U.S. Summit.
The primary takeaway from this flurry of activity is that Microsoft, in the guise of its Project Olympus initiative, and with the help of alliances, partnerships, and more than a little cajoling, has developed a de facto standard model for hardware development and community based open collaboration. So even though your enterprise may not house the hardware that runs your cloud services, the hardware that does is likely a byproduct of Microsoft's Project Olympus.
Climbing the mountain
Project Olympus establishes an open source cooperative standard for server hardware tasked with providing cloud and enterprise services. Developing the standard with the open source model has accomplished two things. First, the hardware is robust yet flexible, which means future scaling of capability and capacity should not be a problem.
Second, the CPU and the subsystems that support it can be just about anything—the standard is CPU independent. This is why Microsoft was able to announce collaborative agreements with so many different chipmakers on the same day. The OCP Summit was just the perfect place to release the shared announcements.
The Project Olympus standard will support the next generation Intel Zeon processors (Skylake) and AMD's next-generation processor, which it has dubbed "Naples." There was also an announcement about NVIDIA and support for GPU-based processing, which is most often associated with artificial intelligence computations.
While the Project Olympus-inspired announcements regarding the big players like Intel, NVIDIA, and AMD were to be expected, some heads were probably turned by a release that said the new hardware standard would also support ARM processors produced by Qualcomm and Cavium. ARM-based processors are not generally associated with Microsoft software like Azure and Windows 10.
The numerous cooperative announcements flowing out of the OCP Summit are just another indication of Microsoft's commitment to cloud-based computing. By getting the vast majority of datacenter engineers to agree upon an open source hardware standard for servers, Microsoft has provided a known and quantifiable foundation for software development. In other words, Microsoft has streamlined and simplified its future.
This is important because Microsoft knows that the overarching future of computing rests in the cloud. It's important to establish Windows 10 on as many devices as possible—potentially billions. And it's even more vital to get as many of those devices as possible, plus IoT devices coming online soon, to use Azure services. The quality of Microsoft's future depends on it.
With a more universal standard, developers of Azure services can focus on features and scalability and much less on hardware drivers and CPU-specific tweaks. As long as customers building datacenters follow the open source standard, engineers at Microsoft can fulfill specific requirements and specifications quickly and efficiently—saving time, money, and headaches.
A notable accomplishment, coming from an obscure conference called the 2017 Open Compute Project (OCP) U.S. Summit—don't you think?
- Azure: How Microsoft plans to boost cloud speeds with an FPGA injection
- Windows Server on ARM: Microsoft moves beyond Intel in its Azure cloud
- AWS and Microsoft Azure at the center of IT's most exciting change in decades
- How Microsoft is differentiating Azure as the "business cloud" for the enterprise
What cloud services does your enterprise currently use? What services are you looking to deploy? Share your thoughts and opinions with your peers at TechRepublic in the discussion thread below.