<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cloning RHEL VM or Boot Volume in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/cloning-rhel-vm-or-boot-volume/m-p/6984823#M1490</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One great feature of virtual machines and UCS service profiles is the ability to easily set up a golden image or VM, then clone new instances to rapidly provision.&amp;nbsp; This can make administrative tasks easier, as we do not need to PXE boot or kickstart new images.&amp;nbsp; Additionally, if done using thin provisioning or zero copy clones, the new instance will take up almost 0 space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When cloning an instance of RHEL, or converting to a template, it is important to first remove any old log data and make the instance unique.&amp;nbsp; Also, you will want your network interfaces to actually work when you bring the clone online.&amp;nbsp; One great resource I have found that lays out many steps necessary comes from The Lone Sysadmin:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://lonesysadmin.net/2013/03/26/preparing-linux-template-vms/" title="https://lonesysadmin.net/2013/03/26/preparing-linux-template-vms/"&gt;Preparing Linux Template VMs – The Lone Sysadmin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have taken his steps and simplified them into a simple copy paste of plain text here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/sbin/service rsyslog stop&lt;/P&gt;&lt;P&gt;/sbin/service auditd stop&lt;/P&gt;&lt;P&gt;/bin/package-cleanup --oldkernels --count=1&lt;/P&gt;&lt;P&gt;/usr/bin/yum clean all&lt;/P&gt;&lt;P&gt;/usr/sbin/logrotate -f /etc/logrotate.conf&lt;/P&gt;&lt;P&gt;/bin/rm -f /var/log/*-???????? /var/log/*.gz&lt;/P&gt;&lt;P&gt;/bin/rm -f /var/log/dmesg.old&lt;/P&gt;&lt;P&gt;/bin/rm -rf /var/log/anaconda&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/audit/audit.log&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/wtmp&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/lastlog&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/grubby&lt;/P&gt;&lt;P&gt;/bin/rm -f /etc/udev/rules.d/70*&lt;/P&gt;&lt;P&gt;/bin/sed -i ‘/^(HWADDR|UUID)=/d’ /etc/sysconfig/network-scripts/ifcfg-eth0&lt;/P&gt;&lt;P&gt;/bin/sed -i ‘/^(HWADDR|UUID)=/d’ /etc/sysconfig/network-scripts/ifcfg-eth1&lt;/P&gt;&lt;P&gt;/bin/sed -i ‘/^(HWADDR|UUID)=/d’ /etc/sysconfig/network-scripts/ifcfg-eth2&lt;/P&gt;&lt;P&gt;/bin/rm -rf /tmp/*&lt;/P&gt;&lt;P&gt;/bin/rm -rf /var/tmp/*&lt;/P&gt;&lt;P&gt;/bin/rm -f /etc/ssh/*key*&lt;/P&gt;&lt;P&gt;/bin/rm -f ~root/.bash_history&lt;/P&gt;&lt;P&gt;unset HISTFILE&lt;/P&gt;&lt;P&gt;/bin/rm -rf ~root/.ssh/&lt;/P&gt;&lt;P&gt;/bin/rm -f ~root/anaconda-ks.cfg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Happy Cloning!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;JBell&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Apr 2015 23:19:48 GMT</pubDate>
    <dc:creator>jbell126</dc:creator>
    <dc:date>2015-04-06T23:19:48Z</dc:date>
    <item>
      <title>Cloning RHEL VM or Boot Volume</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/cloning-rhel-vm-or-boot-volume/m-p/6984823#M1490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One great feature of virtual machines and UCS service profiles is the ability to easily set up a golden image or VM, then clone new instances to rapidly provision.&amp;nbsp; This can make administrative tasks easier, as we do not need to PXE boot or kickstart new images.&amp;nbsp; Additionally, if done using thin provisioning or zero copy clones, the new instance will take up almost 0 space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When cloning an instance of RHEL, or converting to a template, it is important to first remove any old log data and make the instance unique.&amp;nbsp; Also, you will want your network interfaces to actually work when you bring the clone online.&amp;nbsp; One great resource I have found that lays out many steps necessary comes from The Lone Sysadmin:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://lonesysadmin.net/2013/03/26/preparing-linux-template-vms/" title="https://lonesysadmin.net/2013/03/26/preparing-linux-template-vms/"&gt;Preparing Linux Template VMs – The Lone Sysadmin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have taken his steps and simplified them into a simple copy paste of plain text here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/sbin/service rsyslog stop&lt;/P&gt;&lt;P&gt;/sbin/service auditd stop&lt;/P&gt;&lt;P&gt;/bin/package-cleanup --oldkernels --count=1&lt;/P&gt;&lt;P&gt;/usr/bin/yum clean all&lt;/P&gt;&lt;P&gt;/usr/sbin/logrotate -f /etc/logrotate.conf&lt;/P&gt;&lt;P&gt;/bin/rm -f /var/log/*-???????? /var/log/*.gz&lt;/P&gt;&lt;P&gt;/bin/rm -f /var/log/dmesg.old&lt;/P&gt;&lt;P&gt;/bin/rm -rf /var/log/anaconda&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/audit/audit.log&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/wtmp&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/lastlog&lt;/P&gt;&lt;P&gt;/bin/cat /dev/null &amp;gt; /var/log/grubby&lt;/P&gt;&lt;P&gt;/bin/rm -f /etc/udev/rules.d/70*&lt;/P&gt;&lt;P&gt;/bin/sed -i ‘/^(HWADDR|UUID)=/d’ /etc/sysconfig/network-scripts/ifcfg-eth0&lt;/P&gt;&lt;P&gt;/bin/sed -i ‘/^(HWADDR|UUID)=/d’ /etc/sysconfig/network-scripts/ifcfg-eth1&lt;/P&gt;&lt;P&gt;/bin/sed -i ‘/^(HWADDR|UUID)=/d’ /etc/sysconfig/network-scripts/ifcfg-eth2&lt;/P&gt;&lt;P&gt;/bin/rm -rf /tmp/*&lt;/P&gt;&lt;P&gt;/bin/rm -rf /var/tmp/*&lt;/P&gt;&lt;P&gt;/bin/rm -f /etc/ssh/*key*&lt;/P&gt;&lt;P&gt;/bin/rm -f ~root/.bash_history&lt;/P&gt;&lt;P&gt;unset HISTFILE&lt;/P&gt;&lt;P&gt;/bin/rm -rf ~root/.ssh/&lt;/P&gt;&lt;P&gt;/bin/rm -f ~root/anaconda-ks.cfg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Happy Cloning!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;JBell&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Apr 2015 23:19:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/cloning-rhel-vm-or-boot-volume/m-p/6984823#M1490</guid>
      <dc:creator>jbell126</dc:creator>
      <dc:date>2015-04-06T23:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Cloning RHEL VM or Boot Volume</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/cloning-rhel-vm-or-boot-volume/m-p/6984824#M1491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the share Mr Bell!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2015 15:20:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/cloning-rhel-vm-or-boot-volume/m-p/6984824#M1491</guid>
      <dc:creator>rugby0134</dc:creator>
      <dc:date>2015-04-16T15:20:02Z</dc:date>
    </item>
  </channel>
</rss>

