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.
Remember that old,old post of mine: HTTP Filtered Value Set Providers and dependent enumerations ? Probably not. It goes into a little feature of Rational Team Concert that makes it easy to avoid having to duplicate data from external systems that RTC might need to integrate with. UrbanCode Deploy can do something similar for value sets for process properties.
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.
Managing database schema changes can be a non-trivial task. Very often the danger associated with potential bad changes being deployed makes DBAs very protective of their territories and resistant to changing tried and true methods.
However, the push towards more Agile development methods, adoption of DevOps practices and Continuous Delivery capabilities is including database development in its embrace; the last 10 years or so has seen a lot of work towards aligning database development with application development best practices. That said, there are probably quite a few organisations out there where the normal practice for deploying database changes is to use some sort of “list of instructions” and various GUI DB tools with maybe some scripts thrown in. Even adopting practices such as SCM and CI can appear daunting.
Strange title. I know. There are probably a few other ways those words could have been combined, but basically this post is about:
Continue reading “Cooking up deployments on stacked clouds”
They say a picture is worth a thousand words and the picture of the High Availability setup for UCD in the UCD Infocenter is no exception, reproduced here .
The text in the Infocenter (in the process of being updated with a more comprehensive guide for a future UCD release) has information scattered around on how to do this. So here’s a quick and dirty guide to how I set this up.
In my last post there’s a tidbit about overcoming an access problem using an agent (or the CLI). That was with UCD 6.0. No need for this with the upcoming release of UCD 6.0.1 : see Eric Minick’s post about Plugins for Artifact Sources.
A quick couple of UrbanCode Deploy tips, one on getting the SSH config right and the other on using the UCD agent and/or CLI provide an access work around.
A mild case of paranoia. Or too many episodes of Breaking Bad and Walter White Syndrome. Whatever it is, I feel like Darrell Schrag’s been peering over my shoulder (across all of 9000+ miles) as I’ve been working on this post, tut-tutting at some of the wrong turns I’ve taken. Though Darrell had no idea I’ve been writing this post, “Getting the Most out of Your UrbanCode Deploy Implementation” might well have been directed at me: this post is a kind of a case in point, at least of his advice on using/creating plug-ins.