According to a blog post on blogs.sun.com, the capacity limit for OpenSolaris 2008.05 on EC2 has been removed.
The blog entry makes it sound like you no longer need to register with Sun to use OpenSolaris on EC2, but that doesn’t appear to be the case - I only see the AMI in my private instances, and the details on the image seem to confirm this.
I’m running an instance right now; it did seem to take an extra long time for the image to come up, even by EC2 standards, and ec2-describe-instances showed the instance as “running” for a long time before I could connect using SSH. But it’s up now, ZFS root and all:
-bash-3.2# uname -a
SunOS domU-12-31-38-00-28-35 5.11 snv_91 i86pc i386 i86xpv
-bash-3.2# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mnt 106K 147G 18K /mnt
rpool 2.74G 6.86G 59K /rpool
rpool/ROOT 2.73G 6.86G 18K /rpool/ROOT
rpool/ROOT/opensolaris-1 2.73G 6.86G 2.72G legacy
rpool/ROOT/opensolaris-1/opt 12.9M 6.86G 12.9M /opt
rpool/export 37K 6.86G 19K /export
rpool/export/home 18K 6.86G 18K /export/home
swap 450M 9.89M 18K /swap
swap/swapfile 450M 460M 16K -
One curiosity:
-bash-3.2# pkg image-update
pkg: "image-update" option currently not supported on Amazon EC2. Please check out http://blogs.sun.com/ec2 for more details.
I must have missed those details…
Update: Here’s the reason why you can’t run “pkg image-update” from the Getting Started Guide for Amazon EC2: “pkg image-update - This command is currently not supported on Amazon EC2 since it modifies the kernel and ramdisk files resulting in non-bootable AMI. As we know, in the EC2 environment modifying the kernel and ramdisk is not permitted. In certain cases, if the user wants to enable this command, then the user can edit the /usr/bin/pkg file appropriately.” (Which makes sense.)
Post a Comment