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

Time to Level Up!

With the recent news out of Salesforce and Oracle, it’s easy to understand why folks affected by layoffs might feel discouraged. Not only are they leaving companies they may have called home for years, but they’re also facing the daunting prospect of job hunting while headlines scream about “AI taking over human jobs.” Not long ago, another company I follow - let’s call it Acme  - went through a similar round of layoffs. Two employees in particular (we’ll call them Jim and John) showed how mindset can make all the difference. Jim had been at Acme for over 20 years. He was reliable, steady, and well-liked, but not exactly the standout type. When he was laid off, he decided to take some time off before even thinking about his next move. After all, he had a severance package. Didn’t he deserve a break after two decades of hard work? John’s story was different. Though he hadn’t been at Acme as long, he’d built a strong reputation and had both technical and leadership skills. Instead of...

Finding Clarity in the Chaos of a Job Search

Job searches are humbling. They test your confidence, your patience, and your ability to stay motivated when things don’t move as quickly as you’d like. But they also teach you things about yourself that you might not have learned any other way. For me, the past few months have been a crash course in rediscovering what really matters: not just in a résumé, but in relationships, self-perception, and how we use technology to help tell our stories. Here are three lessons that stood out. Reach Out to Your Network (Long Before You Need It) Your network is a living thing. It requires upkeep, time, and attention, just like a flower garden. You can’t ignore it for years and expect it to bloom the moment you need it. Start planting early. Stay in touch with people whose paths you’ve crossed - colleagues, mentors, partners, even those you only worked with briefly. Drop a note once in a while. Comment on their posts. Share something that made you think of them. These small gestures are the sunl...

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...