Verified this is present in 20100210 build.
$ ls -l /etc/init/ureadahead*
-rw-r--r-- 1 root root 889 2009-12-21 23:27 /etc/init/ureadahead.conf.disabled
-rw-r--r-- 1 root root 683 2009-12-21 23:27 /etc/init/ureadahead-other.conf
$ dpkg-divert --listpackage /etc/init/ureadahead.conf
cloud-init
$ dp
This bug was fixed in the package cloud-init - 0.5.3-0ubuntu2
---
cloud-init (0.5.3-0ubuntu2) lucid; urgency=low
* divert ureadahead.conf in postinst (LP: #499520)
* lintian cleanups
-- Scott MoserFri, 05 Feb 2010 15:48:21 -0500
** Changed in: cloud-init (Ubuntu Lucid)
This is being fixed by diverting the /etc/init/ureadahead.conf conffile
in a postinst script for cloud-init.
** Changed in: ureadahead (Ubuntu Lucid)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu Lucid)
Status: Confirmed => Fix Committed
--
default uec-image requires at
** Package changed: vm-builder (Ubuntu Lucid) => cloud-init (Ubuntu
Lucid)
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not needed by default
https://bugs.launchpad.net/bugs/499520
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:~cloud-init-dev/cloud-init/lucid
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not needed by default
https://bugs.launchpad.net/bugs/499520
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Fixed images are running fine with 128Mb RAM, nothing should be changed in
Eucalyptus ?
I think we should disable ureadahead in cloud images, doesn't make much sense
in a system that will rarely be booted twice ?
Opening a ureadahead task, maybe it shouldn't better adapt to the amount of RAM
ava
To be clear, the issue here is more than just accounting. When we boot
an instance in UEC with 256M or less of memory, the OOM kicks in and the
system is generally not in good shape.
looking into this further, the big difference between karmic and lucid
/proc/meminfo was 'LowFree'. On an ec2 in
** Attachment added: "ps output on lucid"
http://launchpadlibrarian.net/38635331/lucid-ps-mem.txt
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not needed by default
https://bugs.launchpad.net/bugs/499520
You received this bug notification because you ar
** Attachment added: "ps output on karmic"
http://launchpadlibrarian.net/38635326/karmic-ps-mem.txt
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not needed by default
https://bugs.launchpad.net/bugs/499520
You received this bug notification because you
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: High
Status: Triaged
** Also affects: vm-builder (Ubuntu Lucid)
Importance: High
Assignee: Scott Moser (smoser)
Status: New
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not nee
I'm elevating the eucalyptus task here to "High" (which might be a bit
ambitious), but I'm also targeting at A3.
I've been doing some scalability testing on my 5-node cluster, each node
having 4GB of memory. I'm able to run up to 14 x 256MB guests per node.
It would be nice to get a few more on t
$ free
total used free sharedbuffers cached
Mem: 1759664 2511921508472 0 3460 41492
-/+ buffers/cache: 2062401553424
** Attachment added: "ps -eFl on i386 alpha 2 instance (ec2)"
http://launchpadlibrarian.net/379762
On Fri, Jan 15, 2010 at 04:37:38PM -, Mathias Gug wrote:
> On Fri, Jan 15, 2010 at 12:38:43PM -, Soren Hansen wrote:
> > Mathias, how have you determined this 300 MB requirement?
> IIRC, I've booted a default UEC image and then looked at top just
> after boot. Swap space was used. And ther
On Fri, Jan 15, 2010 at 12:38:43PM -, Soren Hansen wrote:
> Mathias, how have you determined this 300 MB requirement?
>
IIRC, I've booted a default UEC image and then looked at top just after boot.
Swap space was used. And there was around 30-40 M of free RAM. Not very
scientific though.
--
300 is high, but this bug is made worse by bug 499522 which will be
fixed soon (fixed in my developement ec2-init).
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not needed by default
https://bugs.launchpad.net/bugs/499520
You received this bug notification
Mathias, how have you determined this 300 MB requirement?
--
default uec-image requires at least 300 M of RAM to run - m1.small and
c1.medium not needed by default
https://bugs.launchpad.net/bugs/499520
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Two different issues here: the inflation of the minimal RAM amount
needed to run a lucid cloud image, and a redefinition of the default VM
types to better reflect the default use case. I think it's important to
keep the memory usage in our cloud images to a minimum if possible and
300Mb sounds quit
17 matches
Mail list logo