[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu30.2 --- eucalyptus (1.6.2-0ubuntu30.2) lucid-proposed; urgency=low * Revert: node/handlers_kvm.c: fix console bug (was only showing first 64K), LP: #566793 *

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-15 Thread Martin Pitt
Please upload the lucid fix to maverick as soon as possible (SRU policy). Bumping priority. ** Changed in: eucalyptus (Ubuntu Maverick) Milestone: lucid-updates = maverick-alpha-2 -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package eucalyptus - 1.6.2+bzr1230-0ubuntu1 --- eucalyptus (1.6.2+bzr1230-0ubuntu1) maverick; urgency=low [ Colin Watson ] * debian/eucalyptus-cloud.eucalyptus-cloud-publication.upstart: Only start after avahi-daemon has started. [ Dave Walker

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-14 Thread Launchpad Bug Tracker
** Branch linked: lp:~davewalker/eucalyptus/maverick_to_quilt -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. --

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-10 Thread C de-Avillez
Both Chris and I tested this. I run 2 loops: * allocating and deallocating 200 devices; * allocating and deallocating 513 devices. Both worked as expected. We *did* see errors, but they are unrelated to this bug (see bug 590929). As such, I consider this bug fixed. ** Tags added:

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-08 Thread Steve Langasek
Accepted into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: eucalyptus (Ubuntu Lucid)

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-08 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/lucid-proposed/eucalyptus -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. --

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
** Description changed: Eucalyptus versions: ii eucalyptus-common 1.6.2-0ubuntu30.1 ii eucalyptus-java-common1.6.2-0ubuntu30.1 ii eucalyptus-sc 1.6.2-0ubuntu30.1 Bug 430846 and bug 498174 partially dealt with this issue. But, on an SC

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
This appears to have worked for me up to 50 1GB volumes (actually allocated 52) then it started failing giving me the error in the log file: Your proposed upload exceeds the maximum allowed object size. (edu.ucsb.eucalyptus.cloud.EntityTooLargeException) I have plenty of space on my physical

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
The above issue was caused by having my UEC set to 50GB limit for volumes. I changed it to 200GB under Configuration - Clusters - Disk space reserved for volumes and it allowed me to create 194 of them. It then started having problems from what appears to be a different but related bug of not

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
My removal errors are probably related to 517086, but the creation error appears to be new according to C de-Avillez, it is failing at vgcreate, example follows: 12:32:54 DEBUG [SystemUtil:pool-10-thread-4] Running command: ///usr/lib/eucalyptus/euca_rootwrap dd if=/dev/zero

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
I manually ran: # /usr/lib/eucalyptus/euca_rootwrap vgcreate vg-6E6tMQ.. /dev/loop93 Volume group vg-6E6tMQ.. successfully created So I am not sure what is going on. -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
Actually my volume removal errors seem to be different than the other bug at least in several of the cases I have looked at. They are also lvremove issues like the vgcreate ones. --- 12:53:57 DEBUG [SystemUtil:pool-10-thread-5] Running command: ///usr/lib/eucalyptus/euca_rootwrap lvremove -f

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-07 Thread Chris Cheney
So this bug regarding loop devices seems to be fixed but there is a new bug 590929 opened about the problems with creating/deleting volumes having problems with lvm. -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ccheney/ubuntu/lucid/eucalyptus/lucid-sru -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. --

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-02 Thread Dustin Kirkland
** Changed in: eucalyptus (Ubuntu Lucid) Assignee: (unassigned) = Chris Cheney (ccheney) ** Changed in: eucalyptus (Ubuntu Lucid) Status: New = Triaged ** Changed in: eucalyptus (Ubuntu Lucid) Importance: Undecided = High -- SC: Maximum number of loop devices should be

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-06-01 Thread Dustin Kirkland
** Changed in: eucalyptus (Ubuntu) Assignee: (unassigned) = Chris Cheney (ccheney) ** Also affects: eucalyptus (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: eucalyptus (Ubuntu Maverick) Importance: High Assignee: Chris Cheney (ccheney) Status:

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-05-28 Thread C de-Avillez
new test, using resources provided by Etienne Goyer (et merci beaucoup Etienne!): I successfully allocated 257 volumes. This is interesting, in one aspect: I understood we could have a max of 256 volumes and 256 snapshots. It seems that the real maximum is 512 (to be tested); but we may end up

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-05-27 Thread C de-Avillez
proposing for lucid-updates. Changes will be made to /etc/init /eucalyptus-sc.conf (and, perhaps, to /etc/eucalyptus/eucalyptus.conf?) raising the loopback devices to 512 (256 max volumes, plus one snapshot per volume). ** Changed in: eucalyptus (Ubuntu) Importance: Undecided = High **

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-05-27 Thread C de-Avillez
*Note* per Dan, the NCs use one loopback device per VM *startup*. Currently we are defaulting to 32 loopback in the upstart script, so we should be good to up-to 32 *simultaneous* instances startups. -- SC: Maximum number of loop devices should be configurable

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-05-27 Thread C de-Avillez
Marking Triaged, given the results of the teleconference. ** Changed in: eucalyptus (Ubuntu) Status: New = Triaged -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification because you are a member of Ubuntu

[Bug 586134] Re: SC: Maximum number of loop devices should be configurable

2010-05-27 Thread C de-Avillez
I have tested it on the test rig: updated the upstart script to allocate 512 /dev/loopnnn, and successfully created 50 volumes (the max we can create right now). -- SC: Maximum number of loop devices should be configurable https://bugs.launchpad.net/bugs/586134 You received this bug notification