EMA Blog: Business Intelligence and IT Management

It’s always like that in enterprise IT. There’s this incredible new technology that lets you do things you could never even fathom possible. But then, once the honeymoon is over, the old problems come back to bite you with a vengeance.

At EMA, we constantly receive inquiries regarding what OpenStack means to the VMware portfolio. Is it a competing technology? Are OpenStack and vCloud complementary? Why did VMware join OpenStack? What are the typical use cases for OpenStack as opposed to vCloud? To address these questions, let’s take a step back and take a look at what OpenStack is and, as importantly, what it is not. This post is building on my previous article on the business value of OpenStack.

At EMA, we constantly receive inquiries regarding what OpenStack means to the VMware portfolio. Is it a competing technology? Are OpenStack and vCloud complementary? Why did VMware join OpenStack? What are the typical use cases for OpenStack as opposed to vCloud? To address these questions, let’s take a step back and take a look at what OpenStack is and, as importantly, what it is not. This post is building on my previous article on the business value of OpenStack.

OpenStack’s huge momentum is undeniable. IBM, RedHat, NetApp, Rackspace, HP, Dell, Cisco, Intel and even VMware have committed significant funds and human resources to this project. But why would companies, that are otherwise competing rather fiercely, sit on one table to build an OpenSource cloud platform?

OpenStack’s huge momentum is undeniable. IBM, RedHat, NetApp, Rackspace, HP, Dell, Cisco, Intel and even VMware have committed significant funds and human resources to this project. But why would companies, that are otherwise competing rather fiercely, sit on one table to build an OpenSource cloud platform?

Almost one year into the discussion about the Software Defined Data Center (SDDC), it is time to take inventory of the state of the discipline. As a reminder, the ultimate goal of the SDDC is to abstract and centralize the
management of compute, network, storage, operating systems, middleware and applications in order to dynamically place workloads where they can run in the most cost efficient, secure and compliant manner.

Almost one year into the discussion about the Software Defined Data Center (SDDC), it is time to take inventory of the state of the discipline. As a reminder, the ultimate goal of the SDDC is to abstract and centralize the
management of compute, network, storage, operating systems, middleware and applications in order to dynamically place workloads where they can run in the most cost efficient, secure and compliant manner.

After talking about the “grand vision” of the Software Defined Datacenter (SDD) in part 1 of this series and discussing the individual components required to build out the SDD in part 2, this third part will be all about the three core challenges and controversies:

After talking about the “grand vision” of the Software Defined Datacenter (SDD) in part 1 of this series and discussing the individual components required to build out the SDD in part 2, this third part will be all about the three core challenges and controversies:

In part 1 of this series of four posts, we examined the grand vision of the software-defined datacenter (SDD). In this second post of the series, we will take a look at the core components of the SDD (see Figure 1) and provide a brief evaluation of how mature these components currently are.