IBM BigFix: Tiny Core Linux. Virtual Relay Auto-deployment

Size: px

Start display at page:

Download "IBM BigFix: Tiny Core Linux. Virtual Relay Auto-deployment"

Horatio Summers
6 years ago
Views:

1 IBM Security IBM BigFix: Tiny Core Linux Virtual Relay Auto-deployment Document version 1.1 IBM BigFix Team 1

2 Table of Contents Introduction...3 Prerequisites...3 Architectural overview...4 Performing the Auto-Deployment of the virtual relay instances...5 Setting up the environment...5 Customizing the properties files...5 Launching the Virtual Relay Auto-Deployment...6 Troubleshooting...6 Limitations...6 Appendix 1 Samples of customization files...7 2

3 Introduction This guide describes step-by-step the sequence of operations to generate the Virtual Relay instances using the Auto-Deployment feature. Its design is centered on enabling you to automatically deploy a consistent amount of new virtual relays based on the template that you created according to your business needs. To deploy with the Auto-Deployment mode, you must create a script which instantiates automatically the virtual machines and provides the correct configuration files for each virtual machine. In the next sections, more details are provided about the steps to perform the Auto-Deployment of the new Virtual Relay instances. Prerequisites Before starting with the Auto-Deployment, ensure that you have the following prerequisites: The Virtual Relay template: The Virtual Relay template that you created during the template setup, as described in Phase 2 of the Tiny Core Linux-BigFix Virtual Relay document available at: (link) The Windows Power Shell: The power shell is contained in Windows Management Framework 4.0, needed to run the VMWare vsphere PowerCLI. This tool is available at: The VMWare vsphere PowerCLI: Depending on your Virtual Center release, download the VMWare vsphere PowerCLI needed to run VMWare commands. This tool is available at: The dos2unix utility: The dos2unix command is a simple way to ensure that files that were edited and uploaded from a Windows workstation to a Linux workstation work correctly. This tool is available at: 3

PowerCLI to execute specific commands to manage the virtual center.

4 Architectural overview The Virtual Relay Auto-Deployment capability is designed to run from a Windows Power Shell using the VMWare vsphere PowerCLI to execute specific commands to manage the virtual center. The following diagram shows a basic architectural view of the solution: Power Shell 4

5 Performing the Auto-Deployment of the virtual relay instances Before launching the virtual relay Auto-Deployment, you need to satisfy some requirements and perform some customizations as described in the next two sections. Setting up the environment After meeting all the prerequisites and creating the template (as described in the previous section) you can start setting up the environment: Install the Windows Power Shell, depending on your Windows version, following the instructions described at: Install the VMWare vsphere PowerCLI, following the instructions described at: Set up the dos2unix utility which can be copied either into an already existing system variable path or into any other directory. If you copy the utility into an already existing system variable path, no further action is needed. If you copy it into any other directory, ensure that the system variable %PATH% contains the path where you copied the utility. Customizing the properties files To perform the Auto-Deployment, you must create the following two mandatory files: A flat file named machine.list containing the network parameters of the virtual machines that you intend to deploy. A properties file named environment.props containing the properties of your virtual center environment. Optionally, you can define two additional files containing some additional properties for the client and relay configurations: besclient.config which must be copied into the /var/opt/besclient local directory. besrelay.config which must be copied into the /var/opt/besrelay local directory. Refer to Appendix 1 for the samples of these files. 5

Launching the Virtual Relay Auto-Deployment Open the power shell and move to the directory where you downloaded the tool. Run the launchauto-deployment.

6 Launching the Virtual Relay Auto-Deployment Open the power shell and move to the directory where you downloaded the tool. Run the launchauto-deployment.ps1 command as displayed in the following screen capture: The Auto-Deployment process starts. Troubleshooting Starting from the directory where you stored the auto-deployment scripts, all the log files related to the auto-deployment actions are available in the folder named logs. The log files are named auto-deployment_<execution_date>.log. Limitations You can specify only a data store in the environment.props file. In case of a data store cluster, you can specify the data store cluster name. It is not possible to configure and assign specific virtual center resources such as: Resource pools. Specific folders from which to deploy. Permissions. 6

7 Appendix 1 Samples of customization files In this appendix are described the formats of both the mandatory and the optional files. An example of the machine.list flat file, which is a mandatory infrastructure file: virtual-relay1.mydomain.com, N, , , , , , virtual-relay2.mydomain.com, N, , , , , , virtual-relay3.mydomain.com, N, , , , , virtual-relay4.mydomain.com, N, , , , , , virtual-relaydhcp.mydomain..com, Y Where the different columns contain the following information: column 1 : The fully qualified host name of the virtual relay. column 2 : If you intend to use DHCP [Y or N]. column 3: The IP address of the virtual relay. column 4 : The IP address of the subnet mask. column 5 : The IP address of the broadcast column 6 : The IP address of the gateway. column 7 : The IP address of the primary DNS. column 8 : The IP address of the secondary DNS. In this example, five virtual relay instances are created. The first four with a static IP address, the last one with DHCP. Note: Use a comma (,) as field separator. An example of the environment.props properties file, which is a mandatory infrastructure file: # virtual machine properties template=vrautodeployready guestuser=tc guestpassword=myguestpassword # virtual center properties vspherecenter= vspherecenterusername=administrator vspherecenterpassword=myvspherecenterpassword # esx host properties vmhost=myvmhost hostuser=root hostpassword=myhostpassword datastore=mydatastore 7

8 Where the different lines contain the following properties: template: The name of the template to deploy. guestuser: The virtual machine user name. guestpassword: The virtual machine password. VsphereCenter: The virtual center IP address. VsphereCenterUsername: The virtual center user name. VsphereCenterPassword: The virtual center password. VmHost: The host (esxi) IP address. HostUser: The host (esxi) user name. HostPassword: The host (esxi) password. Datastore: The host (esxi) data store. An example of the besclient.config file, which is an optional virtual relay configuration file: [Software\BigFix\EnterpriseClient] EnterpriseClientFolder = /opt/besclient [Software\BigFix\EnterpriseClient\GlobalOptions] StoragePath = /var/opt/besclient LibPath = /opt/besclient/beslib [Software\BigFix\EnterpriseClient\Settings\Client\_BESClient_EMsg_File] value= /var/opt/besclient/besclientdebug.log [Software\BigFix\EnterpriseClient\Settings\Client\_BESClient_EMsg_Detail] value= 0 [Software\BigFix\EnterpriseClient\Settings\Client\_BESClient_Inspector_RPMEmulationEnabled] value=1 [Software\BigFix\EnterpriseClient\Settings\Client\ RelayServer1] value = [Software\BigFix\EnterpriseClient\Settings\Client\ RelayServer2] value = [Software\BigFix\EnterpriseClient\Settings\Client\ RelaySelect_Automatic] value = 0 For the content of this file, refer to the IBM BigFix Platform Knowledge Center. An example of the besrelay.config file, which is an optional virtual relay configuration file: [Software\BigFix\Enterprise Server] EnterpriseServerFolder = /opt/besrelay/ [Software\BigFix\Enterprise Server\GlobalOptions] StoragePath = /var/opt/besrelay 8

9 [Software\BigFix\EnterpriseClient\Settings\Client\_BESRelay_HTTPServer_ServerRootPath] value = /var/opt/besrelay/wwwrootbes [Software\BigFix\EnterpriseClient\Settings\Client\_BESGather_Download_CheckInternetFlag] value = 0 [Software\BigFix\EnterpriseClient\Settings\Client\_BESGather_Comm_UseUrlMoniker] value = 0 [Software\BigFix\EnterpriseClient\Settings\Client\ RelayServer1] value = [Software\BigFix\EnterpriseClient\Settings\Client\ RelayServer2] value = For the content of this file, refer to the IBM BigFix Platform Knowledge Center. 9

Virtual Appliance Installation Guide

Virtual Appliance Installation Guide 2017 RapidFire Tools, Inc. All rights reserved. V20171027 Ver 2M Contents Purpose of this Guide...3 System Requirements...3 Hyper-V installation System Requirements...3