Importing the ZipKit for RHEL 6.3

Once you have downloaded the files for the ZipKit, use the eZDeploy toolkit to import the content and make it available for use by BMC Cloud Lifecycle Management.

• • Before you begin
  • Importing the ZipKit
  • Importing Network Shell scripts in BMC Server Automation
  •  
  • Adding software in BMC Server Automation
  •  
  • Import the TFTP batch file in BMC Server Automation
  • Adding software to a package in BMC Server Automation
  • To configure Network tag for blueprint
  •  
  • Where to go next

Before you begin

Ensure that you have completed the following tasks:

• Downloaded the RHEL 6.3 ZipKit.
• Downloaded the NSH scripts and Batch file for NTP and TFTP post installation options.
• Downloaded TFTP package from Red Hat Enterprise Linux 6.3 64 bit DVD media.
• Ensure that you have an eZDeploy profile. See create an eZDeploy profile.

Importing the ZipKit

To import the ZipKit:

1. Locate the folder to which you downloaded the ZipKit.
2. Open a command prompt window and navigate to the folder to which you downloaded the ZipKit.
3. Execute the eZDeploy toolkit by issuing the following command:

The toolkit extracts the blueprint and the BMC Server Automation objects (packages and scripts) and makes them available for the BMC Cloud Lifecycle Management. See Using the eZDeploy toolkit for more information.

Importing Network Shell scripts in BMC Server Automation

For NTP and TFTP post-deployment options, import the following NSH scripts in your BMC Server Automation console.

• NTPClientInstallationRHEL6.3
• NTPServerInstallationRHEL6.3
• TFTPInstallationRHEL6.3

To import Network Shell (NSH) scripts:

1. Log on as an Administrator in the BMC Server Automation console.
2. Navigate to the Folders > Depot and right-click on CSM_Scripts.
3. Click Import.
4. Browse to the NSH Script repository and select the NSH Script to be imported.
5. Click Next and verify that the path is set to Depot/CSM_scripts.
6. If required, double-click and edit the path to Depot/CSM_Scripts.
7. Click Finish.

Adding software in BMC Server Automation

For TFTP post-deployment options, add the following TFTP software in your BMC Server Automation console.

• xinetd-2.3.14-17.el5.x86_64.rpm
• tftp-server-0.49-2.x86_64.rpm
• tftp-0.49-2.x86_64.rpm

You need to add the software packages to the Depot in BMC Server Automation, which can then be deployed to servers. To add a software package to the Depot :

1. Log on to the BMC Server Automation console as an administrator.
2. In the BMC Server Automation console, navigate to the Folders pane.
3. Right-click on the Depot > CSM_Scripts folder.
4. Select New > Software > Custom Software.
5. Select the software you wish to add as a software package.
6. From the Select Installable Sources window, browse to the location of repository and select the required software package.
7. Click OK. This displays the Add Depot Software window.
8. Click Next and Finish to complete the process of adding a software package.

Import the TFTP batch file in BMC Server Automation

After adding the software and NSH scripts in BMC Server Automation. Import the TFTP batch files.

To import the batch files package: 

1. Log on as an Administrator in the BMC Server Automation console.
2. Navigate to the Folders > Jobs > CSM_Application and right-click on CSM_Application.
   
3. Click Import.
4. In the Import Wizard screen, select the directory containing the batch file package.
   
5. Click Next.
6. The Import Wizard displays a list of all the objects which will be imported using the batch file.
   

7. Click Next.

   

   The content of the batch file is associated to different destination groups of BMC Server Automation. Ensure that you have the correct path specified in the Import wizard, if not you need to edit the destination group path. To edit double-click on destination group.

   The following table lists the content of the batch file and the corresponding destination group folder location:

   Batch file content	Destination group folder location
   Deploy job	Jobs/CSM_applications
   BLPackage	Depot/CSM_scripts
   Template	Component_template/CSM_Application_package
   Batch job	Jobs/CSM_Application
   Component discovery job	Jobs/CSM_Application

8. Click Next.
9. Repeat step 1 to 8 to import all the NTP and TFTP package batch files.

Adding software to a package in BMC Server Automation

 After importing the batch files in BMC Server Automation, you would get BMC Server Automation BLPackages for TFTP post-deployment options. You need to add TFTP software to respective BLPackage for TFTP.

To configure Network tag for blueprint

Once eZDeploy toolkit makes the blueprint available for the BMC Cloud Lifecycle Management. You need to configure Network tags imported with the blueprint as per your environment.

When defining network resources (for example, Network Interface Card details), you can tag the NIC and then use the policies to match tags on networks in the container.

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Service Blueprints.
2. Open the service blueprint you imported in BMC Cloud Lifecycle Management, select the Service Deployment Definition.
3. Select Resource set and click Edit.
4. Click the Network Resources tab.
5. In Network Select Method, select a tag (for example, Blueprint[Web] or Blueprint[DB]). The NIC tag is used to select the network to which the NIC should be attached (or routed).
6. If you select Use Network Policies, the NIC tags are used to place the NIC on the network. The Service Governor selects the network based on a matching tag group and tag. See Tagging recommendations and examples for more details.

Where to go next

Creating-a-RHEL-6-3-service-offering