I recently spent four months mired knee-deep in a large enterprise transformation project, analyzing and working directly with the customer on a bloated application portfolio rationalization. This isn’t easy, especially with a very large, diverse enterprise. Companies of this type have multiple business areas, some of which in turn have multiple business units, each with its own complexities and quirks. These areas and units each have their own versions of shadow IT. Further, in the name of being more productive, they may choose to use applications that aren’t known or supported by the central IT organization.
Transformation & Agility
Transformation & Agility concerns the utilization of the technical agility derived from the benefits delivered by virtualization and cloud computing, coupled with Agile Development practices that improve business agility, performance, and results. This includes the agility derived from: (Read More)
- The implementation of Agile and DevOps methodologies
- The application and system architectures
- The implementation of IaaS, PaaS, and SaaS clouds
- Monitoring of the environment, coupled with processes for resolving problems quickly
- Having continuous availability through the use of high-availability and disaster recovery products and procedures
Transformation covers the journey from A to Z and all points between: how you get there and the roads you will travel; how decisions made on day zero or one, or even day three, will affect later decisions; and what technical, operational, and organizational pitfalls can be associated with an implementation. We examine what tool sets are required for Agile Cloud Development, and it delves into other aspects of Agile Development that integrate with cloud computing, SaaS, and PaaS environments, including DevOps, Scrum, XP, and Kanban.
Puppet recently published its annual State of DevOps report. Previously, its 2014 report revealed that DevOps was becoming widely accepted in the enterprise. The 2015 report explained that as enterprises become more mature with DevOps, they become higher performing and release software more frequently with better quality. This year’s report has expanded the research to include employee loyalty, security, and lean product management.
In order for new or smaller public clouds to be competitive with the big kids (Amazon and Azure), these vendors must either adopt the same practices or be unique in what they do. However, if they have a unique value, is it possible to see it, or are all public clouds painted with the same brush as Amazon? Is the key to public cloud to be like Amazon?
Will containers change the shoe size (footprint) of the physical servers in the data center? Recently, I was talking with peers about what containers can bring to the environment. “What changes are needed in the environment,” we asked, “to achieve the greatest success when offering containers as an option to customers?” To truly understand the change in thinking about the physical server’s footprint, we first need a basic understanding of the differences between virtualization in general and container virtualization.
I just returned from two days in Seattle at DockerCon 2016. What I learned at DockerCon this year can be summed up in four categories:
- Container adoption is on the rise
- Docker is winning by making containers simpler
- Docker is forging a path to win enterprise workloads
- The battle for orchestration just became more interesting
Have you heard about unikernels? A unikernel, or cloud operating system, as it has also been called, is a specialized lightweight operating system intended to be used within a virtual machine. Unikernels have the potential to become the core of a new form of cloud computing in which a single hypervisor instance can support hundreds or even thousands of virtual machines. A rethinking of how we populate the cloud infrastructure, the unikernel is a specialized, single-address-space virtual machine image constructed by using a virtual library operating system.