I plan to spend an afternoon getting an ISV application to run on the public PaaS version of OpenShift—to allow direct comparison with a fruitless afternoon spent on the public PaaS version of Cloud Foundry. In this post, I explain the radical difference in approaches I am taking in the two environments to deal with real-world issues in the application lifecycle.
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. Continue reading Dell and Red Hat Collaboration, Part 2
When to implement security and data protection practices, or even change existing ones, is all about timing, knowledge, and scope. Deciding what to implement at any particular time requires knowledge of what needs to be fixed, and also of what the future could hold. To do this properly, you need to pay close attention to the threats within your industry, understand their impact, and evaluate them based on risk. Where to obtain such knowledge is always changing, but the scope we apply the knowledge to seems to be static and not changing with the times.
When people hear the word agile, they usually think of words like scrum, kanban, and velocity. Agile methodologies are geared toward churning out faster iterations of software, but the speed of software development does not always correlate to an organization being agile. What makes an organization agile is when the software that is being delivered is producing enough value to meet the business demand. In order to increase the value of our releases, we need to stop spending so much precious time racking and stacking infrastructure and managing application servers and databases, and spend more time adding valuable features for our business partners and customers. In other words, we need to embrace the cloud.
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.