What's new in IBM UrbanCode Deploy, Version 6.2.0.2

IBM® UrbanCode™ Deploy, Version 6.2 includes new features and bug fixes.

New for March 2017: Delivery Insights, a part of IBM Cloud DevOps Insights, provides metrics and other information about your IBM UrbanCode Deploy servers. See Integrating IBM UrbanCode Deploy with Delivery Insights.

What's new in version 6.2.0.2

You can install high-availability cluster servers silently. See Installing the server in silent mode.
You can provision virtual images that use Windows to vCenter. See Configuring VMware vCenter images.
You can pass resource properties from blueprints to the resource tree. See Passing properties from blueprints to the resource tree.
In the blueprint designer, by dragging an IBM UrbanCode Deploy tag to an image, you can add all the components that contain that tag to the image. See Deploying components with blueprints.
In blueprint source code, you can add constraints to parameters, including limiting the length or pattern of a property, or limiting the property to a list of values. See Externalizing properties in blueprints.
On vCenter, you can provision images to specific folders on the cloud. See Modeling environments for VMware vCenter.
On SoftLayer and Amazon EC2, you can assign tags to images that you provision. See Modeling environments for SoftLayer and Modeling environments for Amazon Web Services.
On OpenStack, you can add name and value pairs to the metadata of an image that you provision. See Modeling environments for OpenStack and OpenStack-based clouds.
When using advanced inventory management, you can update snapshot versions in addition to component versions. See Managing environment inventory and compliance.
The cloud discovery service for the blueprint design server is compatible with AIX® and z/OS®.

This version contains important security updates.

You can now create application templates. These templates can specify the environments, resource tree, application properties, application process, and types of components, which are defined by tags, that are assigned to an application during creation. See Application templates.
You can now provision environments on OpenStack Kilo. You must extend a currently existing Kilo engine for use with the blueprint design server; see Extending Heat orchestration engines.
You can now install multiple blueprint design servers and engines for a high-availability setup. See Setting up clusters of blueprint design servers.
If you provision environments that you connect to through OpenStack heat, you can define environment properties from the blueprint designer in the blueprint source code. See Passing properties from blueprints to the resource tree.

Feedback