Moving to Containers

In this ever-changing world of IT, the legacy of today was once the future of yesterday: namely, hypervisors. Hypervisors are now considered legacy, even though they are seriously underutilized due to issues with fear, uncertainty, and doubt around using these resources to their fullest. The new technology is containers. However, where are the operational tools to …

Yesterday Is Here to Stay

Docker, Kubernetes, and Mesos are generating a lot of discussion as the future of application development. We are seeing significant progress towards having these methodologies adopted by enterprises for application development. We have even been hearing that VMware is the new legacy, since containerised applications don’t always need a hypervisor. These “modern application” methods are replacing …

In the Age of Cloud, You Still Need an Enterprise Architecture

I’ve been speaking a lot lately about the importance of IT governance, especially as it relates to driving cloud (public, private, hybrid) adoption in the enterprise. Although IT governance is critical to the success of having a flexible and agile enterprise, having an overarching enterprise architecture to show how all the components of the enterprise …

VMware’s NSX Has a Problem

One of the things that seemed clear to me over the last couple of VMworld conferences is that VMware is very committed to NSX. In addition to having NSX as the core of its Software-Defined Data Center (SDDC), VMware is also placing NSX in the core of its End User Compute (EUC) offering. I also expect VMware to make …

Strategy for Cloud Automation

Strategy for Cloud Automation. There is a lot of post about the Cloud and Cloud Computing but have not seen to many post or articles that discusses different strategy to consider when it comes to the automation in your environment. I did comes across a nice post called Legacy Job Schedulers: 3 Effective Exit Strategies to Consider by Jim Manias from Advanced Systems Concepts, Inc. that had some interesting points and thought it would be a great topic for discussion. In this post, Jim Manias, starts old school with a reminder that the early stages of automation were managed via schedulers from the host system to kick off the scripts when triggered either manually or from an event. Actually in all practical purposes if you use PowerShell for any of your automation needs, chances are you have used the Windows Scheduler in one form or another.