Today at Microsoft's Ignite conference in Chicago, the company's executives will make a set of major announcements about its server, management, and cloud offerings. At the top of the list is Azure Stack, a cloud infrastructure platform that packages the capabilities of Microsoft's public Azure cloud for use by customers in private data centers and public hosting services. Microsoft also announced Microsoft Operations Management Suite, a set of Azure-based management tools that will help companies manage public and private cloud infrastructure as well as virtual and physical Windows and Linux servers. Lastly, there's a new preview of Windows Server 2016 and the Systems Center 2016 systems management platform. The new Server 2016 preview includes the first release of Nano Server, a minimal Windows Server environment designed for "headless" cloud and virtual server applications that greatly reduces the server operating system footprint.
Additionally, Microsoft executives announced that a preview of Windows Server 2016 scheduled for release this summer would include the first public release of Windows Server Containers (a new isolated operating environment for server applications) and Hyper-V Containers (an isolated version of the Hyper-V environment for cloud deployment of both Windows and Linux applications). The next Server 2016 preview will also include Azure Service Fabric—a self-scaling, self-healing environment for running services in public, private, or hybrid clouds environments.
Stacking Azure
Azure Stack takes a page from the Open Stack cloud management platform in that it provides a way to manage the provisioning and deployment of virtual servers and platform services within a data center's physical infrastructure. But Azure Stack is also optimized for deployment of enterprise applications such as SQL Server, Exchange, and SharePoint and will allow companies to provide self-service application provisioning in the same way that Microsoft currently does within the Azure public cloud while maintaining control over what can be deployed and integration with internal billing or charge-back systems.
Read 5 remaining paragraphs | Comments
No comments:
Post a Comment