VMware

VMware vCloudTM Application Director Release Notes

vCloud Application Director 6.0 | 10 December 2013 | Build: 1446071

Last Document Update: 10 December 2013

These release notes cover the following topics:

What's New

VMware vCloud Application Director 6.0 delivers new features that improve the application modeling, deployment, and update lifecycle management of multitier applications in hybrid cloud environments. The release includes the following new features.

  • vCloud Automation Center Integration - After registering vCloud Automation Center to vCloud Application Director using a CLI command, you can model single or multitier application blueprints and publish a deployment profile to the vCloud Automation Center Service Catalog. From the Service Catalog you can request applications and track the status of the requested catalog items.
  • Application Updates - A key aspect of application provisioning is the handling of post-provisioning activities such as applying updates. For this vCloud Application Director release, you can extend the following update capabilities:
    • Rollback a failed update to restore an application to its previously successful deployment settings.
    • Scale in a cluster of one or more nodes to free unused resources and accommodate the changing load in the scalable application.
    • Update the promotion of changes across deployment environments to facilitate release automation.
    • Reuse the update profiles, which contain frequently used update scripts and properties to update a deployed application.
  • External Services Support- vCloud Application Director can now connect to external services such as a provisioned database using Data Director, a load balancer, existing database, and SaaS applications to reduce the time to deliver a workload. Sample external services are available for databases provisioned through Data Director and existing F5 load balancer.
  • Policy-Based Provisioning - Provide the ability to define policies across different deployment environments by blacklisting application services or enforcing mandatory services. You can also set memory limit, CPU limit, or number of total instances limit across all of the nodes in an application deployment to facilitate policy-based provisioning. The Compliance view page in the user interface shows the policy violations against currently active policies on deployments and application updates.
  • REST API Support - REST API support automates the creation of cloud providers, cloud templates, deployment environments, deployment profiles, and update profiles. You can also update the logical templates and deployment profiles in vCloud Application Director. This release extends the existing REST API capabilities of scheduling deployments, modifying configuration updates, and scaling out clustered deployments.
  • Puppet Integration - Reuse Puppet content to model vCloud Application Director application blueprints to perform the following tasks:
    • Create multitier applications using the Puppet modules.
    • Combine Puppet and non-Puppet content in application blueprints.
    • Import both Puppet Open Source and Puppet Enterprise Modules to the vCloud Application Director catalog.
    • Manage the update life cycle while maintaining multi-node dependencies, property bindings, and diverse content types.
    • Leverage the vCloud Automation Center Service Catalog to publish and request Puppet-based applications.
  • Marketplace Integration - A native integration with VMware Solution Exchange that you can enable to import, browse, and search application blueprints and services available in the marketplace from the vCloud Application Director user interface. You can also import the EULA, cloud solution descriptor, and artifact files to the vCloud Application Director appliance.
  • Flexible Disk Layout - Model the disks of a node in an application blueprint to map to a datastore and use different file systems such as, EXT3 or NTFS. You can assign one or more tags to determine the mapping of disks to the right datastore during deployment. The binary, data, log, and archive tags are useful when modeling database nodes. During deployment, a deployer can customize the deployment profile to map each disk to a datastore.

Other vCloud Application Director Documentation

vCloud Application Director 6.0 includes the following product documentation.

Known Issues

Register to the vCloud Automation Center Service Catalog

  • In some cases, when you register and unregister the vCloud Application Director appliance for the same tenant on two different vCloud Automation Center servers, the operation fails.
    Workaround: Restart the vCloud Application Director appliance.
  • When you unregister the vCloud Automation Center server, the operation does not delete the cloud provider created with the registered vCloud Automation Center server. Therefore, attempting to use the deployment environments, deployment profiles, or update profiles associated with this cloud provider fail with the following error message, Error while filtering the templates for the selected Deployment Environment.
    Workaround: Open the vCloud Application Director Web interface, manually delete the cloud provider, and create another one.

Cloud Abstraction

  • If the host IP address changes, you cannot edit the existing vCloud Automation Center 6.0 cloud provider.
    Workaround: Register a new cloud provider with the updated IP address.
  • You cannot update the host IP address of a cloud provider that has the vCloud Automation Center provisioning group and administrator credentials for the provisioning group already configured.
    Workaround: Create another vCloud Automation Center cloud provider and add the new host IP address.
  • Sometimes, when creating a deployment environment for Amazon EC2, us-west-1b might be designated as the Availability Zone. Ignore the option us-west-1b and type the applicable Availability Zone for your Amazon VPC.

vCloud Application Director Catalog

  • Sometimes installation of the vFabric tcServer service might fail when you try to download binaries from the default mirror site because of network connectivity or other intermittent problems.
    Workaround: Repeat the installation process. You can also configure the service INSTALL script to use another mirror site.
  • In the Clustered DotShoppingCart sample application, changing the default Apache load balancer http_proxy_port property value in the blueprint and deploying the sample application, causes the application to become inaccessible from a Web browser.
  • When authoring a new service, you cannot install many applications and RPM packages with SELinux enabled.
    Workaround: Disable SELinux by default when creating new templates. When using a sample template for download, you must disable SELinux as part of the service install script. The following example shows how you can disable SELinux on a CentOS operating system.
    if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then
     if [ -x /usr/sbin/setenforce ]; then
      /usr/sbin/setenforce Permissive
     else
      echo 'SELinux is enabled. This may cause installation to fail.'
     fi
    fi
  • During the installation of the sample RabbitMQ service on Ubuntu, the apt-get command might intermittently fail with incorrect checksums depending on the network connectivity.
    Workaround: Redeploy the application deployment or contact your system administrator if the failure persists.

Application Modeling

  • Sometimes when you attempt to drag and drop a VM template to the blueprint canvas, the VM template might not appear in the application blueprint.
    Workaround: Refresh the Web browser. You can also return to the previous page and reopen the blueprint canvas and add the VM template to the application blueprint.
  • When you specify a host name for an application blueprint with Puppet content, the host name is assigned to the Puppet node name. If the application is deployed several times, multiple node entries are not created in the Puppet master.
    Workaround: Append ${random} to the host name to create multiple node entries in the Puppet master.
  • Attempting to delete a logical template version referenced by a basic external service or a provider specification for an advanced external service displays the following misleading error message, An unexpected error occurred. Please contact your system administrator.
  • vCloud Application Director assigns the appropriate memory values for an Amazon EC2 instance. Manually configuring the memory settings might cause a failure in deployment.

Application Deployment and Update Process

  • When deploying an application blueprint with an external service to the vCloud Automation Center cloud environment, a deployer must select a cloud template with one NIC.
  • In the deployment profile, when you select a deployment environment with an external service instance and click Map Details, the information from the external service instance might not be populated.
    Workaround: Select another deployment environment, reselect the previous deployment environment, click Map Details to map the external service instance information, and proceed to the next tab.
  • Deploying a vfabric_tc_server sample service fails with the following error message, Property 'external_template' in vFabric_tc_Server_v2.7.1 is required and cannot be blank for deployment.
    Workaround: You must override the external_template property value with https://${darwin.server.ip}:8443/darwin/conf/darwin_global.conf & and redeploy the application.
  • If you use the SSH client to log in to an application deployed to vSphere using vCloud Automation Center, power off a virtual machine in that application from the vCloud Automation Center or vCenter Server user interface, and initiate an update process, the process remains in progress indefinitely.
    Workaround: Cancel the update process, power on the virtual machine in the application, and initiate another update process in vCloud Application Director.
  • Sometimes when a deployment task fails, tasks that are running in other nodes display an In progress status infinitely even though the tasks have completed successfully.
  • If you shut down the vCloud Application Director appliance while application deployments are in progress and restart later, the interruption might not allow the deployment status details to be updated properly.
  • In some instances, when the vCloud Application Director server times out, the Web interface shows the error message, Unable to communicate with server. Please contact the administrator.
    Workaround: Reopen the application or deployment.

Rollback an Update

  • Reverting the external service instance profile properties to the catalog values in the update profile might cause the rollback process to fail.
    Workaround: Define the catalog values for the external service instance profile properties in the deployment environment and initiate a rollback process.
  • You cannot rollback a node component property if you update both the external service instance profile property and the node component property in the update profile and initiate a rollback process.
    Workaround: Update the external service instance profile property and initiate a rollback process. Initiate another rollback process after you update the node component property.
  • You cannot use the rollback feature on the vFabric_SQLFire_Server service. The update and rollback features are not supported on the vFabric_SQLFire_Locator service, and SC_ZIP property and DotShoppingCart_App component in the Clustered DotShoppingCart sample application.
  • Applying the rollback feature on a deployment scaled for clustered nodes is not supported.
    Workaround: If an update process to scale clustered nodes fails, open the update script, diagnose and fix the problem in the script, and initiate another update process.

Update Profile

  • When you a deploy an application using CLI, if you select an update profile the auto complete option for the update profile name is not displayed.
    Workaround: List the available update profiles for the deployment and note the name of update profile you plan to use.
  • While an update process is in progress, you cannot access the list on the update profile page.

External Services

  • Deleting an external service after you remove the application in which it was used fails with an error message.

CLI and CLI Import and Export

  • Using CLI to update the current group name of the logged in user does not update the group name and the previous name appears in the CLI prompt.
    Workaround: Log out of the vCloud Application Director CLI and log in.
  • Using an external API service to import an application version, service version, or script task version to a vCloud Application Director instance does not work.
    Workaround: You can use the CLI import functionality instead to import the components in the package.

User Interface

  • Adding a custom task to an application, modifying the value of a property, and publishing the deployment profile of the application to the vCloud Automation Center service catalog without saving the deployment profile causes the user interface to become unresponsive.
    Workaround: Save the deployment profile and publish it to the vCloud Automation Center service catalog.
  • Frequently expanding and minimizing the information in the Task Details status window of the deployment summary page might cause rendering problems.
    Workaround: Refresh your Web browser.
  • If you create an application using non-ASCII characters and deploy this application to vCloud Director or if an organization VDC network name is using non-ASCII characters in vCloud Director, the application name and organization VDC network name do not render properly in the user interface.
    Workaround: Rename the application or organization VDC network using ASCII characters.
  • Using the reserved keyword, host for properties or names of services, external service components, and application components cause the keyword to disappear from the user interface.
  • In the Execution Plan tab of the Deployment Profile wizard, the user interface incorrectly indicates that the custom task properties are not overridable.
  • The external service properties of an application are incorrectly marked as overridable in the blueprint canvas.
  • The VM Details status window on the deployment summary page might render blank without an error message.
    Workaround: Refresh your Web browser.
  • If an application has more than 12 application versions, you might experience problems when navigating between the application versions.

Top of Page