It is possible to deploy an existing Red Hat Enterpise Linux public image and perform a layered install of Red Hat Gluster Storage. This creates an effective "double charge" for each Red Hat Enterpise Linux instance.
Google Compute Engine charges a premium fee for using a public Red Hat Enterpise Linux image for instances in order to cover the expense of the Red Hat subscription.
When deploying a layered install, you must re-register the instances with Red Hat Subscription Manager, thus consuming a Red Hat Enterpise Linux entitlement that you have paid for separately. After registering with Subscription Manager, however, Google Compute Engine will continue to charge the premium fee for the instances.
4.15.1. Installing Red Hat Gluster Storage from the ISO to a RAW Disk Image File
Using your local virtualization manager, create a virtual machine with a RAW format sparse flat-file backing the system disk. The suggested minimum disk size for the Red Hat Gluster Storage 3.1 system disk is 20 GB and the maximum disk size for import into Google Compute Engine is 100 GB. Google Compute Engine additionally requires the disk size be in whole GB increments, that is, 20 GB or 21 GB, but not 20.5 GB. The RAW disk file should have the disk.raw file name. The disk.raw file must include an MS-DOS (MBR) partition table.
For example, run the following
dd command to create a 20 GB sparse file to serve as the RAW disk image:
# dd if=/dev/zero of=disk.raw bs=1 count=0 seek=20G
The steps below assumes KVM/QEMU as your local virtualization platform.
4.15.2. Enabling and Starting the Network Interface
To enable and start the network interface:
Enable the default eth0 network interface at boot time:
# sed -i s/ONBOOT=no/ONBOOT=yes/ /etc/sysconfig/network-scripts/ifcfg-eth0
Start the eth0 network interface:
# ifup eth0
4.15.3. Subscribing to the Red Hat Gluster Storage Server Channels
4.15.4. Updating your System
Update your systems using the following command:
# yum -y update
4.15.5. Tuning and Miscellaneous Configuration
Set the tuned profile to
rhgs-sequential-io using the following command:
# tuned-adm profile rhgs-sequential-io
rhgs-sequential-io profile is appropriate for this environment, but the
rhgs-random-io profile may be more appropriate for different workloads.
# setenforce 0
4.15.6. Customizing the Virtual Machine for Google Compute Engine
The Google Compute Engine's "Build a Compute Engine Image from Scratch" documentation includes specific instructions for configuring the kernel, network, packages, SSH, and security of the virtual machine. It is recommended that you reference this documentation directly for updated information to ensure compatibility of your image with Google Compute Engine.
Power off the instance to apply all changes and prepare the image import:
# init 0