I thought I'd perform an installation of 12cR1 to do a little testing. So I launched a new instance in Amazon EC2 and picked an AMI for 64-bit RHEL 6.4.
All started smoothly, but I've got stuck preparing a disk for ASM.
My first plan was to install ASMLIB. I see from the documentation that I need kmod-oracleasm (kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm), and that this is in the RHEL supplementary channel.
$ yum repolist all
Loaded plugins: amazon-id, refresh-packagekit, rhui-lb, security
repo id repo name status
rhel-source Red Hat Enterprise Linux 6Server - x86_64 - Source disabled
rhel-source-beta Red Hat Enterprise Linux 6Server Beta - x86_64 - Source disabled
rhui-REGION-client-config-server-6 Red Hat Update Infrastructure 2.0 Client Configuration Server 6 enabled: 3
rhui-REGION-rhel-server-releases Red Hat Enterprise Linux Server 6 (RPMs) enabled: 10,994
rhui-REGION-rhel-server-releases-optional Red Hat Enterprise Linux Server 6 Optional (RPMs) enabled: 6,250
rhui-REGION-rhel-server-releases-optional-source Red Hat Enterprise Linux Server 6 Optional (SRPMs) disabled
rhui-REGION-rhel-server-releases-source Red Hat Enterprise Linux Server 6 (SRPMs) disabled
repolist: 17,247
$ rhn-channel --add --channel=rhel-x86_64-server-supplementary-6
Username:
^C
Does Amazon EC2 provide the RHEL supplementary channel, and if so what credentials do I need to provide? Otherwise I guess I would need my own RHN subscription, which seems expensive for a self-learning instance.
So my second plan was to avoid ASMLIB and implement udev rules.
I created a 64GiB volume and attached it to the instance as /dev/sdh. On the instance it appears as /dev/xvdl:
$ fdisk -l /dev/xvdl
Disk /dev/xvdl: 68.7 GB, 68719476736 bytes
255 heads, 63 sectors/track, 8354 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf4c9fedb
Device Boot Start End Blocks Id System
/dev/xvdl1 1 8354 67103473+ 83 Linux
$ sudo scsi_id -g -u -d /dev/xvdl
$
So scsi_id doesn't return a value to use in the udev rule. I've found references to this which suggest setting disk.EnableUUID. Is this option available in Amazon EC2 at all? Or is there an alternative way of getting a UUID for the disk?
Any help with these questions, or suggestions for alternative solutions, would be much appreciated.
Thanks
Mike