How does your data center cope with the new demands of digital services? Can it provide on-demand scale, efficient low-cost operations, or consistent service availability? In this blog sponsored by Intel learn how Intel and its partners are working with the industry to re-architect the data center for the digital services economy.
Are Your Applications Ready for an OpenStack Neighborhood?
BrandPosts are written and edited by members of our sponsor community. BrandPosts create an opportunity for an individual sponsor to provide insight and commentary from their point-of-view directly to our audience. The editorial team does not participate in the writing or editing of BrandPosts.
By Billy Cox
The typical enterprise application grew up on its own block. By that I mean the application lived in its own environment served by a dedicated pool of bare-metal servers. For the administrator, there was no question the application would get the resources it needed to meet the appropriate service-level agreements (SLAs). That was all hard wired into the system.
Today, with the advent of cloud computing and the maturation of the supporting technologies, a big change is under way. Enterprise applications are now moving into multi-tenant OpenStack neighborhoods where they have to contend with potentially “noisy neighbors.”
A so-called “noisy neighbor” is a virtual machine that consumes more than its fair share of the shared resources within the system and therefore degrades the performance of the other VMs running on that same system. And this is where things get even trickier: When you move an application into a shared environment, you might encounter performance problems but have no way of knowing they are due to a noisy neighbor.
At Intel, we are addressing this problem with software, called Intel Data Center Manager: Service Assurance Administrator (Intel DCM: SAA). This software plugs into OpenStack to extend its functionality in a natural way. It uses OpenStack methods to determine the best placement for a particular virtual machine and the workload it runs.
Intel DCM: SAA has built-in capabilities that use Service Level Agreement (SLA) specifications as performance targets. The details on these capabilities are beyond the scope of this blog post. For now, let’s just cut to the chase: By assigning a specific SLA to an application, all stakeholders can have the confidence that—regardless of other activities in the neighborhood—the application will get the CPU resources it needs to meet the expected performance criteria.
Your workloads also want to live in a secure and trusted neighborhood. You need the assurance that the neighborhood is in fact the right neighborhood (the right hypervisor) and is running in compliance with required regulations (configured to meet requirements).
What application owners need are assurances about the performance and trust of workloads running in a multi-tenant environment. Service providers, in turn, gain the means to create new offerings with assured performance or to pack workloads more densely into existing server racks—with the confidence that they will meet their SLAs.
Looking ahead, Intel plans to add to the software with quality of service capabilities for storage and networking resources—all in the interest of maintaining good neighborly relations on OpenStack blocks.
For a closer look at the capabilities in the initial release of Intel DCM: SAA, watch this video and take a look under the hood.