DevOps, it seems, is popping up everywhere. Sometimes it isn't called out as DevOps, but when you read the details, it certainly sounds like DevOps. The drivers of software-defined data center (SDDC) was clearly one of those "DevOps by any other name" moments, as was a recent KPMG report on cloud in which "successful cloud" strategies included the avoidance of silos:

"Avoid silos. Cloud transformations succeed when organizations are able to embed change into every aspect of the business. As such, silos hamper transformation. In contrast, collaboration powers it. For example, business and IT professionals should work side by side as cloud is adopted into the enterprise."

Silos hamper transformation. Collaboration powers IT. Huh. Sounds a lot like the mantras of DevOps, doesn't it?

That shouldn't be a surprise, as DevOps is often discussion in the context of cloud computing — both on-premise and off. But what is surprising is that this isn't a discussion regarding the merits of automation and orchestration and the ways in which cloud and its API-driven paradigm is eminently well-suited to a DevOps approach to continuous integration and delivery. What's surprising is this is purely about the organizational (cultural) change required to effect transformation via cloud computing. It's not just about dev and ops, or net and ops, or sec and ops, but about IT and the business. Biz and Ops (where ops is defined as all four ops in IT). BizOps.

Click here for Talkin' Cloud's Top 100 CSP list

Okay, that doesn't really have the same ring to it as DevOps or even NetOps, but the concept behind is definitely DevOps all the way.

And if surveys and research are to be believed, it's definitely needed to head off potential problems now, particularly with respect to security.

The State of Public Cloud Security (Forrester) found that "security is not heavily involved in crafting security policies for public cloud. Only 43 percent of organizations reported that their IT security team was heavily involved in crafting security policies for the public cloud."

What that means is that the majority of public cloud usage is not governed by a security-driven policy.

It's driven by users. If that doesn't bother you, consider that the report also found that "64 percent of organizations report developers/non-IT professionals are responsible for selecting public cloud vendors."

Sure, you're saying, but that's security. Security is always clashing with, well, everyone.

Okay, let's take a look at something a bit closer to home, then and consider the aforementioned KPMG report in which 74 percent of organizations cited "ease of integration into existing environments" as a top criterion for choosing a cloud computing environment. Ease of integration includes security, of course, but it also includes automation, orchestration, provisioning, measurement and management. It's the ability to integrate remote cloudy infrastructure into an existing data center environment.

Which is not about security, but about operations — both operations focused on the network and the application infrastructure.

Which means decisions regarding cloud should be made, as KPMG suggests, within a collaborative approach. One that looks and tastes a lot like DevOps.

Do you believe DevOps drives the success of cloud? How so? What examples can you provide other IT administrators?