Active System Manager Release 8.2 Installation Guide

Ensure all instructions have been completed for VMware or Hyper-V virtual machines as noted in the previous section.

Install VMware tools (VMware only)
Install puppet agent and ensure it is configured to run on startup
Make sure ASM appliance and virtual machine time are synchronized by NTP.
Make sure DNS is configured for “dellasm” to resolve.
Make sure puppet.conf file has updated configuration to point to “ dellasm” as server.

Copy puppet certname scripts puppet_certname.sh and puppet_certname.rb to the virtual machine.

You can find the puppet certificate name scripts for Linux (puppet_certname.sh and ppet_certname.rb) in /opt/asm-deployer/scripts on ASM appliance. You can move these files to /var/lib/razor/repo-store. The following command needs to be run from the /var/lib/razor/repo-store directory or will fail.
sudo find win2012 -print0 | sudo xargs -0 chown razor:razor
- NOTE: The version of the INI file in puppet certificate script should be specified as 2.0.2. To verify this, open the puppet_certname.sh file and check that the INI file version is specified as 2.0.2 or not.
On a Linux virtual machine, you must copy these scripts to /usr/local/bin. Make sure the permissions are set on these scripts to at least read and execute. To do this, run the following commands:
```
chmod 755 /usr/local/bin/puppet_certname.sh 
                                          chmod 755 /usr/local/bin/puppet_certname.rb
                                       
```

Make sure the virtual machine has access to the internet, as this will be required to download and install the necessary ruby gem files. If your virtual machine will not have access to the internet, then download the ruby gem files for “inifile” and “hashie” and place them in the /usr/local/bin directory where you copied the puppet certname scripts.

NOTE: The puppet_certname.sh script that runs on startup of the VM clone attempts to install the ruby “inifile” and “hashie” gems from the internet. In case of no internet connection, it generates error messages to communicate with rubygems.org.

It would be less error-prone to require the user to install the gems in the source VM rather than having them installed when the clone VM starts up. To do this you need to:

Remove the gem install lines from puppet_certname.sh

Manually run the gem installs either with the instructions on how to set a proxy or how to install the gems by downloading them directly.

You must update the Network Interfaces so that it will not be associated with the base virtual machine MAC address (varies based on OS, examples below). To update it, run the following: RHEL/CentOS:

rm /etc/udev/rules.d/70-persistent-net.rules
                                    rm/lib/udev/rules.d/75-persistent-net-generator.rules
                                    sed -i "/^HWADDR/d" /etc/sysconfig/network-scripts/ifcfg-eth0

RHEL 7

Remove MAC Address from the interface configuration file. For example,

sed -i "/^HWADDR/d" /etc/sysconfig/network-scripts/ifcfg-ens192

NOTE: Interface naming on RHEL 7 VM depends on the various factors provided at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy

Debian/Ubuntu:

rm /lib/udev/rules.d/75-persistent-net-generator.rules

Configure cronjob to execute the puppet_certname.sh script and restart or start the puppet service. Type the following commands:

crontab –e

Add the following line to this file and then save and exit the file.
```
@reboot /usr/local/bin/puppet_certname.sh; /etc/init.d/puppet restart
```
RHEL 7
```
@reboot /usr/local/bin/puppet_certname.sh
```
Run the following command, and ensure that you see the above line, to verify the crontab is updated as expected or not,
```
crontab -l
```

After completing customization, turn off the virtual machine. To create a virtual machine template, follow the appropriate steps for virtualization environment.

NOTE: After preparing the base virtual machine, in case the virtual machine is restarted, the puppet verification file will need to be deleted from system. This file can be found in Windows at C:\ProgramData\puppet_verification_run.txt or in Linux at /var/lib/puppet_verification_run.txt.

Active System Manager Release 8.2 Installation Guide

Customizing Linux Template

對此內容評分

歡迎

歡迎來到 Dell

Active System Manager Release 8.2 Installation Guide

Customizing Linux Template

對此內容評分