On April second, Cisco introduced something that seems to make a lot of sense in its new declarative-based, ACI-led world of software-defined networking: a policy mechanism. The blog post about it was pretty straightforward: it included the obligatory nods toward the Internet Engineering Task Force (IETF) and open-source communities, defined the differences between the traditional imperative and the newer Cisco declarative models, and had snazzy graphics. Cisco laid out the core challenge clearly:
For this declarative model to work across a multi-vendor environment, to translate and map policy definition into the infrastructure, there has hitherto been no standard protocol to do that across physical/virtual switches, routers and L4-L7 network services. This vacuum has led to the development of OpFlex, a new open standard recently submitted to the IETF.
Red Hat has released a 2.0 version of OpenShift, its on-premises (private) PaaS. OpenShift seems to build on real customer experience to address a range of issues that come up in real deployments, providing an out-of-the-box solution that is likely to appeal to enterprises seeking to offer a consistent development/deployment option to reduce complexity and cost.
It has been around a decade since Dell and Red Hat’s collaboration, when they helped launch Red Hat Linux into the mainstream. Now, they have gotten back together to collaborate on an enterprise-grade version of OpenStack, based on the Havana version. This announcement recently followed another announcement from Red Hat that they would be bundling OpenStack with the Red Hat Enterprise Linux 6.5.
In my last couple of posts, I wanted to express my thoughts about the future of cloud computing. In the first post, I shared what appears to be a bright outlook for the future for people working in the cloud space, given the soaring demand for skilled engineers and not enough quality people to fill those roles. In my second post, I presented a couple of key skill areas that currently seem to have the most demand. I want to share my thoughts, or more to the point, concern, that this “gap” of skilled engineers is only going to increase unless we can help guide people off the hypervisor and into the cloud.