What's New in UrbanCode Deploy with Patterns 184.108.40.206
An Events view that helps users monitor and diagnose provisioning activities. The Events view provides a graphical visualization of events and their timeline. Only events originated in by the HEAT engine are supported in this release. Those events pertain to the start, completion, or failure of stack requests. The view allows users to correlate visually the initial request to start, delete, or update a stack resource, with the successful completion or failure of such request (i.e., correlating a start event with its completion or failure).
The capability pre-requires the administrative configuration of Event Sources, which define the name or IP address of the heat engine (host) from which the event originates, the messaging system used to handle the event (RabbitMQ or Qpid), and the authentication for accessing the host. This pre-required configuration takes place in the administration user interface.
Improved editing experience
Furthermore, when user subsequently adds additional components into an image, they will be given the option of adding it to the same or different application.
Commenting in the diagram editor has been extended to include connections. When a connection is commented out in the diagram editor, the code in the source editor corresponding to the corresponding network connectivity will be commented out (in synchrony with the diagram editor).
Enhanced UrbanCode Deploy agent packaging
In this release enhanced UrbanCode Deploy agent packaging gives customers more visibility and customization of the manner in which the UrbanCode Deploy agent is installed in the target environment. Such agent is utilized to carry out the deployment automation of application components into a provisioned environment. In this release the agent is surfaced in the blueprint itself, allowing customers to fully customize the location, procedure and other parameters involved in the agent installation (e.g., the URL and authentication values of the UrbanCode server with which the agent will be connecting).
Below is the list of defects fixed in this release:
|125199||Auto-scaling updates in stand-alone HEAT engine fails due to user authorization|
|116687||Provisioned blueprint containing another blueprint does not work in the Amazon case|
|125199||Update from blueprint from UrbanCode Deploy failed with port conflict issue|
|125081||AttributeError: ‘Client’ object has no attribute ‘software_configs’UCDP|
|124958||Update udclient path in agent install package|
|123756||UCL: Agent naming schemes are broken for multi-node cases including autoscaling group|
|123617||Parameter validation misses references from other intrinsic functions like get_attr|
|123506||UCL: base_resource_group support is missing|
|123225||NPE when deleting Auth* Realms|
|123180||Create build package for UCDP heat plugins|
|123142||UCL: Provision a blueprint that has two nodes with same component will always fail|
|122918||GVT – Corruption strings in different panel of pseudo translation build|
|122881||CDP heat engine doesn’t authenticate against keystone v3 API|
|122820||Multiple components on node failing to deploy|
|122343||Dojo build minify isn’t handling Orion correctly|
|121534||UCDP: Template verification of get_param indicates failure when using pseudo-parameters “OS::stack_id” and “OS::stack_name”|
|121406||When network connection made to instance in asg, network id parameter not exposed in asg|
|121348||Commenting a server should comment out the related types|
|121347||Server rename fails in some use cases|
|121202||Validation should “ignore” commented sections|
|120544||Include Resource Tree code in blueprint only when it contains components|
|120526||Bueprint only when it contains components
|117022||Extra slash in method /rest/blueprint/outputs|
Below is the list of issues known with this release:
|123130||UCL:Unable to apply a component to an empty ucdp provisioned instance. Whenever you have an empty OS::Nova::Server with no components and you add a component, it will fail on the update because the server must be re-provisioned to add the user_data sections. Port conflict issues may arise.||This is due to the following defects in Openstack Heat
|125199||Autoscaling updates in standalone Heat engines fail due to user authorization.||Workaround is to use a heat engine embedded with the openstack environment.|
|116687||Provision blueprint that contain another blueprint does not work in the Amazon case. Using nested blueprints with non-openstack clouds (Amazon, VMWare) does not work due to limitations in the openstack icehouse release.||Workaround is to use a heat engine embedded with the openstack environment.|
|VMWare provisioning: When deploying a UCD component, the VMWare must have a routable IP address.|