Using the eZDeploy 1.0.00 utility

This topic describes how to use the eZDeploy 1.0.00 utility. For information about the current version of the utility, see Using-the-eZDeploy-1-1-00-utility.

This topic covers the following:

• • Before you begin  
  • Importing the eZDeploy package
  • Post-import actions for eZDeploy
  • Exporting service blueprints as an eZDeploy package

Before you begin  

 The following are additional prerequisites for importing the eZDeploy package:

• BMC Cloud Lifecycle Management is installed and configured.
• The Virtual Center (VC) server name is available.
• Virtual Center templates are available.
• Datastore name is available.
• BMC Server Automation is configured.
  • VC server is added and registered in your BMC Server Automation.
  • Distribute Configuration Object (also known as DCO) job is run.

Importing the eZDeploy package

The import eZDeploy functionality imports the BMC Cloud Lifecycle Management service blueprint as an eZDeploy package.

To import an eZDeploy package, perform the following steps: 

1. Run the command eZDeploy>  import –name  <ezDeploy Package name with Path> -profile <eZDeploy target eZDeployProfile Name>  –file <answer file name path> -prefix BMC

    

    The following table lists the inputs that you must provide to run the command.

    

   Field name	Input	Parameter type
   Name	Full name of the eZDeploy package file	Required
   Profile	Target eZDeploy profile	Required
   File	Answer file name along with the file path	Optional
   Prefix	Custom prefix on blueprint artifacts	Optional

2. Press Enter.

    

   Note

   On pressing Enter, the BMC Server Automation artifacts (system packages, software packages, and NSH scripts, if any) are imported.

3. If eZDeploy cannot locate the software bits, download the software installable and copy it to a common location that is accessible to the BMC Server Automation Server and the Virtual Center (VC) Server; for example, <BladeLogic installed directory>\storage. You can enter the path or URL on eZDeploy as network path.
   • For Network Path—//<host>/<path_including_installer_file>
     eZDeploy checks for an existing installable resource (a Virtual Guest Package, or VGP) available on the BMC Server Automation Server. eZDeploy prompts with the following message:  Do You Want to Select Existing Virtual Guest Package ? [y/n].
     If  you select "y", all VGPs available on the BMC Server Automation Server are listed and you can select an ID assigned to that displayed VGP. In this scenario, you can skip step 4. If you select "n", you must create an installable resource (see step 4).
     
4. To create an installable resource (Virtual Guest Packages), refer to the following points:
5. 
   
   • If eZDeploy detects VC Servers registered on the BMC Server Automation server and lists them on the console, enter the ID assigned to the VC Server and press Enter.
   • If eZDeploy detects VMWare templates available on the VC Server and lists them on the console, enter the ID assigned to the template name that you will use for creating a Virtual Guest and press Enter.
   • If eZDeploy detects datastores available on the VC Server and lists them on the console, enter the ID assigned to the datastore name and press Enter.
   • If your .eZ file is a Windows based service blueprint, enter the Windows license key for creating VGPs and press Enter.
   • If your .eZ file is a Windows based service  blueprint, enter the Administrator password (or, for blueprints on *nix platforms, enter the root password) and press Enter.

The VGP is created and saved on the BMC Server Automation Server with the prefix followed by the VGP name. 

The functional models and deployment models, along with options, if any, are imported.

Post-import actions for eZDeploy

After you have successfully imported the eZDeploy package, perform the following post-import actions:

• To verify if the import was successful, go to the BMC Cloud Lifecycle Management Blueprint console. You will find the blueprint with the prefix followed by the blueprint name. Open the imported blueprint and check for functional and deployment models. Also check for system packages and software packages, and whether or not the installable resources are attached to the models. 
• To change the Network Interface card details as per your requirement, perform the following steps:
  By default, you will find the Network Tags added in the imported blueprint. 

1. Open the imported blueprint and go to Service Deployment Definition.
2. Select Deployment Definition.
3. Edit Resource set.
4. Open the Network Resources tab and make the changes as per your requirement.

• If options are imported, go to the Service Catalog console, open Options Editor, and look up for option and option choices with the prefix followed by the option name. You can now select the imported options or option choices manually while creating a service offering from the eZDeploy imported service blueprint.

Exporting service blueprints as an eZDeploy package

The export service blueprint functionality exports the BMC Cloud Lifecycle Management service blueprint as an eZDeploy package (.eZfile). If you want to import a service blueprint, you must export it first.

To export a BMC Cloud Lifecycle Management service blueprint as an eZDeploy package, perform the following steps: 

1. Run the command eZDeploy> export –name <Service Blueprint Name> -profile <eZDeploy SourceProfileName> –service <service name>

    

   The following table lists the inputs that you must provide to run the command. 

    

   Field name	Input	Parameter type
   Name	Name of the BMC Cloud Lifecycle Management service blueprint	Required
   Profile	Name of the eZDeploy profile that is created	Required
   Service	Name of the Service Catalog	Optional

2. Press Enter.

   If eZDeploy detects any BMC Atrium Orchestrator workflows that are associated with the service blueprint, you must provide the module version.

The BMC Cloud Lifecycle Management service blueprint is exported. A folder with the name export is created under the eZDeploy directory. The export folder contains a .eZ file (zip file) with the BMC Cloud Lifecycle Management service blueprint name.