Recently, we upgraded our cloud environment. This raises the question, “What is wrong with the environment after an upgrade?” As tools improve, we get new warnings, messages, and analytics. This often leads to a decision to ensure that after the upgrade, all monitoring, alerts, and other diagnostics show green across the board. Is this required, desirable, and even warranted? Wouldn’t it make sense to understand a change between releases first, before blanket acceptance?
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.
The use of the cloud is not governed by technology so much as it is governed by cost: the cost of on-premises management, support, expertise, and environment vs. the cost of cloud services and outsourced expertise, management, etc. The cost differential must be high enough in the short term to allow it to become valid in the long term. There are lots of cloud calculators out there. Since Apple, Dropbox, and others have changed clouds or moved to their own data centers, what does this tell us about the future of cloud?
Building a private cloud was a high priority for a number of organizations in 2014. This priority carried over into 2015 because it is hard to execute. For many organizations, it has carried over again into 2016. Of course, the definition of a private cloud has changed in that time, too. Some organizations are happy simply to have consistent VMs deployed in response to a helpdesk ticket. Other organizations aspire to have the AWS in their own datacenter. One significant trend is the use of public cloud services to manage on-premises private clouds. The other trend is OpenStack in the enterprise, rather than only in academia and hyperscale where it started.
IT as a Service (ITaaS) is changing nearly every day. In the past, it was mainly about automating deployment through the contents of a service catalog. Today, it has grown to include IT operations analytics (ITOA). What matters isn’t whether we can select an application from a service catalog, but rather how we monitor and react to issues during the lifetime of the application. With containers, which are all about automation, ITaaS has to change not only to include ITOA, but also to react to the results of the analytics.
Innovation is the future of IT, but is innovation really happening? Let us look at one segment of IT: security. The RSA Conference hosts an annual Innovation Sandbox. The winner can claim to be the most innovative security company that participated in the contest. This year, there was a wide mix of companies.
Over the last couple of months, there seems to have been a brain drain at VMware; executives are leaving in swarms. (Is that the collective noun for a group of execs? I don’t know.)
The past month has seen the departure of Jonathan Chadwick, the highly respected chief finance officer; Martin Casado, the general manager of the Networking and Security Business Unit and creator of NSX; and finally, last week, longtime Chief Operating Officer Carl Eschenbach.