Increase m1.small memory to 192 MB

see bug 529056 comment 7 (https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/529056/comments/7) for some discussion on this.

Note, 192M was chosen, as it is believed we can boot without any OOM. if that assertion is not true, then we'd bump it up. The real request is that m1.small run lucid image well.

I'd prefer m1.small to keep being clearly distinct from c1.medium so as to make sense in the global scale of VM types offered by default... but if that is the only way to make our default image work with the default vmtype, then so be it.

Why not 256MB? 192MB just seems ... terribly odd.

CPU cores are usually the limiting factor anyway. Someone with limited memory on node controllers and/or specific requirements can always change the value in the web UI, if need be.

@Etienne: I think 256 Mb would just make c1.medium =~ m1.small...

This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu20

---------------
eucalyptus (1.6.2-0ubuntu20) lucid; urgency=low

  [ Dustin Kirkland ]
  * Continue fixing karmic -> lucid upgrades, LP: #519513
  * debian/eucalyptus-java-common.postinst: ensure that the db dir exists
    before running euca_upgrade
  * debian/eucalyptus-common.preinst: ensure that the local conf exists
  * tools/euca_upgrade:
    - on upgrade, migrate eucalyptus.conf settings to eucalyptus.local.conf
    - on upgrade, migrated $NODES to nodes.list
  * clc/modules/msgs/conf/scripts/startup.groovy: change m1.small to 192M
    such that we can actually boot the lucid uec image, LP: #544292

  [ Scott Moser ]
  * debian/source_eucalyptus.py: fix AttributeError, LP: #520775
 -- Dustin Kirkland <email address hidden> Mon, 22 Mar 2010 17:22:48 -0700