Killing it softly

A question came up on how to end an UrbanCode Deploy application process quickly when any one of many component processes executing in parallel fails.


What’s in a name?

“O! be some other name:

What’s in a name? that which we call a rose

by any other name would smell as sweet”

From one of my favourite plays, rendered in somewhat recent times in superb fashion IMHO, by one of my favourite directors (a fellow Aussie and New South Welshman by the way:-).

The naming gods must have finally read “Connecting UrbanCode Deploy with Patterns to OpenStack” and decided the UrbanCode Deploy with Paterns (UCDP/UCDwP/UCD+P..) name is indeed a mouthful.  Mouthful or not, Eric Minick provides a bit more detail on  UCDwP becoming part of UrbanCode Deploy with the 6.1.2 version in his post . Problem solved indeed and does make perfect sense as I’ve been finding when showing UCDwP to customers moving into the cloud over the past year or so. For simplicity I’m just going to call the cloud blueprint capability the “Designer”.


UrbanCode Deploy with Patterns is out

UrbanCode Deploy with Patterns is out. A whole lot of fixes and some new stuff. Take a look at

What’s New in UrbanCode Deploy with Patterns

OpenStack AutoScaling in UrbanCode Deploy with Patterns

The first Fix Pack released for UCD+P added initial support for provisioning to VMware vSphere infrastructure along with support for auto-scaling groups in OpenStack. The UCD+P Knowledge Centre topic describes what is currently supported and this YouTube video shows this in action. This post works through an example of creating and provisioning a UCD+P blueprint with an auto-scaling policy on OpenStack.


What’s up Doc(ker)?

A recent post from Doug Davis “Docker: Managing the excitement” has some nice insights on Docker as a “relatively new” technology. Among the other Docker niceties that Doug points out, one that resonated with me is, and I quote “it takes seconds (if not less than a second, after the first time since things are cached) for it to complete”. Reading between the lines in some of my other posts, I’ve often battled the dark forces of virtual machine world, usually trying to squeeze every bit of extra juice out of my poor laptop. Then I tried Docker and well, suffice to say I need fewer coffee breaks.

My long-time colleague and friend Takehiko Amano has a post on “Immutable Infrastructure” where he talks about Docker in the context of OpenStack and with a bunch of my earlier posts focused on OpenStack, I decided to figure out how the three – OpenStack, Docker, and UCD+P might work together.


UrbanCode Deploy with Patterns: Hello World, the vSphere edition

In the concluding paragraphs of my last post, UrbanCode Deploy with Patterns: Hello World ,I briefly compared the UrbanCode Deploy with Patterns (UCD+P) use of OpenStack HEAT Templates (HOT) for blueprints with my own simple XML blueprint for vSphere compute resources.  In the past week a Fix Pack was released for UCD+P which adds initial support for provisioning to VMware vSphere infrastructure. So in this post I’ll do a “Hello World” -style example of connecting UCD+P to a vCenter 5.5 server, provisioning a VM on it and deploying multiple UrbanCode Deploy (UCD) components to the VM.