Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Overview of the eZDeploy utility

The following sections provide an overview of the eZDeploy utility:

Key features of the eZDeploy utility

The eZDeploy utility provides the following capabilities:

  • Export or import service blueprints with specific versions
  • Export or import a multitier blueprint created using reused service blueprints
  • Export or import the service catalog along with postdeployment actions with option and option choice
  • Export or import service offerings, services, and software packages
  • Use additional command line parameters to specify whether you want to create duplicate options
  • Create user profiles
  • Set an eZDeploy profile as a Global profile to be used for the import or export command
  • Import the eZDeploy package in an interactive or noninteractive mode
  • Specify a single location for the software to be used during import
  • Apply a custom prefix during import
  • Utilize system validation command
  • Support additional providers like Amazon, OpenStack, and so on

Back to top

Benefits of the eZDeploy utility

Some of the benefits of the eZDeploy utility are as follows:

  • Service blueprints are exported and imported along with all BMC Server Automation artifacts (system packages, software packages, and NSH scripts). Prior to the eZDeploy utility, the service blueprint JSON file and BMC Server Automation artifacts were exported and imported manually.
  • Services, service offerings, and software packages can be exported and imported. Prior to the eZDeploy utility, services and service offerings were created manually, and software packages were exported and imported manually via the BMC Server Automation console.
  • BMC Atrium Orchestrator workflows, if any, can also be exported and imported. Prior to the eZDeploy utility, BMC Atrium Orchestrator workflows were imported and exported manually from the BMC Atrium Orchestrator repository.
  • Product Catalog entries from the Definitive Media Library are linked to the service blueprint during import. Prior to the eZDeploy utility, because BMC Server Automation artifacts could not be imported, no Product Catalog entries were created during import.

Back to top

Product compatibility

The eZDeploy 3.0 utility integrates with BMC Cloud Lifecycle Management 4.5.00 only.

Back to top

Limitations of the eZDeploy utility

  • Only a single session of eZDeploy can be active from a single server.
  • Option included in the exported service must have at least one option choice.
  • The source and the target BMC Cloud Lifecycle Management environment versions for importing an eZDeploy package must be the same. eZDeploy packages exported from earlier versions of BMC Cloud Lifecycle Management cannot be imported in the later versions of BMC Cloud Lifecycle Management.
  • The VGP creation process uses the template reference and licenses, but not other properties, such as timezone. You must update these properties manually after you create the VGP.
  • Ensure that you enable the BMC BladeLogic Sever Automation web services to export BMC Server Automation artifacts successfully.
  • Before performing eZDeploy operations for any third-party provider (for example: OpenStack, or Azure), ensure that the provider is registered and the corresponding Product Catalog entries are onboarded in the target environment.
  • eZDeploy creates request definitions type as Compute only irrespective of the original request definition type of the service imported. For example: OpenStack service has the request definition type as OpenStack, but after importing the OpenStack service, the request definition type is set to Compute by eZDeploy. You must then manually set the correct request definition type for the imported service.
  • For imported option icons to be visible on the GUI, you must restart the Mid Tier service and clear the browser cache.

Back to top

Related topic

Troubleshooting eZDeploy issues

Back to top

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments