Problems with switching to small small and small instances of EC2

Question

You have several applications where small instances of EC2 are, well, too large. Thus, the announcement of microlevels is what the doctor ordered.

I would like to take a small instance of EBS, disconnect it and associate it with the micro-instance. At some point, it can be great to go the other way and enlarge the micro-instance to a small or more.

In this failed experiment, I tried:

• Create a new small instance with Alestic Ubuntu 10.04 32-bit AMI (ami-1234de7b). Boots like a charm.
• Disconnect my recently released micro-instance, separate the volume that was created for me in the previous step.
• Attach a small copy to the micro copy.
• Power on
• Nada.

What is odd, there is no exit to the console log until I turn off. Then I see everything.

[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
...
[    1.221261] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
[    1.221261] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
[    1.222164] devtmpfs: mounted
[    1.222202] Freeing unused kernel memory: 216k freed
[    1.223409] Write protecting the kernel text: 4328k
[    1.223760] Write protecting the kernel read-only data: 1336k
init: console-setup main process (63) terminated with status 1
%Ginit: plymouth main process (45) killed by SEGV signal
init: plymouth-splash main process (196) terminated with status 2
cloud-init running: Thu, 09 Sep 2010 17:37:54 +0000. up 2.61 seconds
mountall: Disconnected from Plymouth
init: hwclock-save main process (291) terminated with status 1
Checking for running unattended-upgrades:  * Asking all remaining processes to terminate...       
[80G 
[74G[ OK ]
 * All processes ended within 1 seconds....       
[80G 
[74G[ OK ]
 * Deconfiguring network interfaces...       
[80G 
[74G[ OK ]
 * Deactivating swap...       
[80G 
[74G[ OK ]
 * Unmounting local filesystems...       
[80G 
[74G[ OK ]
 * Will now halt
[  185.599636] System halted.

This exchange method worked well between the same sizes as in the past, and this is my first attempt to do this between different sizes. Is this simply impossible or am I missing something fundamental in my knowledge of EC2?

Answer 1

Although this is likely to be ported to Server Fault, I ran into the same issue with this instance earlier today.

It seems that this image suggests that there will be an ephemeral repository when there is not one in the micro level. To get around this, comment out the following line in / etc / fstab:

/dev/sda2   /mnt    auto    defaults,comment=cloudconfig    0   0

, , , ami-1234de7b.

Answer 2

-, ami (ami-2c354b7e). . , .

, . "/dev/sda2/mnt auto defaults, comment = cloudconfig 0 0"

Answer 3

. , . :

$ l="deb http://archive.ubuntu.com/ubuntu lucid-proposed main"
$ echo "$l" | sudo tee -a /etc/apt/sources.list
$ sudo apt-get update && sudo apt-get install cloud-init
$ dpkg-query --show cloud-init

, Ubuntu , , ...

: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/634102

In addition, we have several images based on the official Ubuntu AMI that work for Micro's: http://blog.simpledeployr.com/2010/09/new-ruby-amis-with-latest-ubuntu-lucid.html

Answer 4

I do not see a problem on your side. This could be a problem in Amazon's infrastructure.