Skip to main content

Provisioning For What Purpose? (Part 1)

In the early part of the last decade, I ran a global education program at a mid-sized company called Softwatch.  In this role, my responsibilities required that I provide education to our partners around the world.  One such occasion had me traveling to Paris to teach a class with 20 students from various parts of Europe, and so my partner Matt Grob and I flew out on Saturday to spend the weekend creating a complete education lab from scratch.

Granted, it's not incredibly taxing when you're building a lab in Paris of all places.  The process, which was fairly straightforward, took us both days and then we had the nights to explore the Champs-Élysées, La Concorde, etc. not to mention eat and drink amazing culinary delights.

However, I digress.  The point I am trying to make is that it took us an entire weekend to build 20 computers in an identical manner.  It cost the company several hundred dollars to provide accommodations (hotel and meals) that would have been unnecessary if it were 2012 instead of 2002.

But it must be said that provisioning, for provisioning's sake, is never done - there is always a purpose. This task is performed to provide an environment that can run applications.  Maybe the applications are COTS (Commercial, Off The Shelf) or internally developed, but applications are the raison d'être.  Even in my story, we were building the machines so that my company's software could also be installed and run by the students during the class.

Provisioning, then, should be considered part of application release.

Many companies have missed the boat:  BMC's BladeLogic and CA's Automation Suite for Clouds are provisioning with no purpose.  They require other solutions to consume the produced machine, real or virtual, so that it may be incorporated into a bigger picture.  But customers no longer want building blocks - they want turn-key solutions - so these formerly bedrock solutions are now passé.  This is evidenced by the fact that both of these solutions are now buried deep within the websites of their respective owners.  I suspect similarly deep locations will be found on the websites of other vendors in this space.

Looking at the bigger picture, however, we see that provisioning is simply a sequence of steps to be followed:  
  1. Install the OS
  2. Install the application server, DBMS, or ESB
  3. Configure the application server, DBMS, or ESB
  4. Connect it to the rest of the infrastructure
  5. Deploy the application components on the box.  
The above steps define a process to be automated.

Automation is automation, regardless of how it's being used.  And all automation, regardless of its design, requires core capabilities that have withstood the test of time in terms of stability and scalability.

In part 2 we will look at some of these core capabilities that should be required features of any automation platform.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...
Read more

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...
Read more

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...
Read more