Having hooked up UrbanCode Deploy with Patterns (UCDP) to OpenStack and UrbanCode Deploy (UCD), it’s time to take a look at a “HelloWorld”-style example. I’ll work through a single-server UCDP blueprint, deploying a single UCD component to it.
UrbanCode Deploy with Patterns (UCDP): a mouthful right? A pretty neat and powerful mouthful though. Consider theses two posts: Cooking up deployments on stacked clouds and UrbanCode Deploy with vSphere and Chef. UCDP makes it simpler and easier to carry out a bunch of steps detailed in those posts. Before I get into the details, let me first quickly go through how to install UCDP and connect it to an OpenStack setup.
In a previous post (Cooking up deployments on stacked clouds) I looked at using UrbanCode Deploy with OpenStack and Chef. I showed one way of creating a stack from a Heat template, injecting the UCD agent and Chef into one of the newly provisioned servers, cooking a Chef recipe and deploying an application on it. This time round I look at how to do almost the same thing with VMware vSphere.
Calling Rational Team Concert an old dog isn’t fair – it’s only just over 5 years old – and I mean it in the nicest possible way in the context of the Jazz Jumpstart team being “old”, and the Rational Emerging Technologies Team, well, “emerging”.
Anywho, as is my wont, I was going through what could be in the next CLM release, noticed the bit about Rational Team Concert Build and IBM UrbanCode Deploy and decided to try out this “emerging” feature with Rational Team Concert 4.0.5 RC1.
Having successfully gone through installing WebSphere and creating Base WepSphere profiles using Urbancode Deploy (UCD), the next logical step is to use the profile in some way. Here’s where the Application Deployment for WebSphere plug-in comes in. There are a bunch of steps in this plug-in that help with a whole range of WebSphere tasks.
After creating generic UCD processes to first install WebSphere and then create standalone (Base) WebSphere profiles, I wanted to turn my attention to applying the second process to WebSphere ND. I’d already written about creating a clustered CLM setup using the command line in my old post Clusters of CLM applications without a GUI so this should have been pretty simple. It occurred to me that the steps in both the processes from the last two posts could actually be steps in a UCD plug-in, just like the Application Deployment for WebSphere plug-in. Of course I’ve never written an UCD plug-in before and my experiences with writing RTC extensions had left me with the distinct feeling that this kind of thing was not for mere mortals like me. This was the domain of gurus and gods like Ralph Schoon. However, the thought had been planted in my head and, like in Inception, I could not help but follow it through.
Following up my last post, I describe a simple sample UCD process that helps with automating the creation of Base WebSphere profiles. I hope to attack setting up WebSphere ND infrastructure at some later time. As with the previous post the intent is not to create a “perfect” process but one that gets the job done while exploring some other aspects of UCD.