** Changed in: eucalyptus
Status: New = Invalid
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member
** Changed in: eucalyptus
Status: New = Invalid
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member
We ran 96 instances in Lucid a few minutes ago. I really believe this
is fix-released in Lucid. Please re-open with detailed information if
anyone reproduces in Lucid.
Please make sure that VNET_ADDRSPERNET is higher than the number of
instances you want to run, plus 3. So if you want to run
We ran 96 instances in Lucid a few minutes ago. I really believe this
is fix-released in Lucid. Please re-open with detailed information if
anyone reproduces in Lucid.
Please make sure that VNET_ADDRSPERNET is higher than the number of
instances you want to run, plus 3. So if you want to run
Unnominating for lucid, can't be reproduced so far...
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Incomplete = Won't Fix
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Unnominating for lucid, can't be reproduced so far...
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Incomplete = Won't Fix
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: lucid-alpha-3 = None
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: lucid-alpha-3 = None
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Medium
Status: Incomplete
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Medium
Status: Incomplete
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Targeting at A3, as we should test this setup in our scalability testing
next week at the Distro Sprint.
** Changed in: eucalyptus (Ubuntu)
Milestone: None = lucid-alpha-3
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Targeting at A3, as we should test this setup in our scalability testing
next week at the Distro Sprint.
** Changed in: eucalyptus (Ubuntu)
Milestone: None = lucid-alpha-3
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Marking incomplete, as we have outstanding requests for information from
both Paul and Dan.
I have loaded up my (much smaller) Lucid cluster here with 56 VMs
without a problem.
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Marking incomplete/medium per last comment
** Changed in: eucalyptus (Ubuntu)
Importance: High = Medium
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Incomplete
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Marking incomplete, as we have outstanding requests for information from
both Paul and Dan.
I have loaded up my (much smaller) Lucid cluster here with 56 VMs
without a problem.
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Marking incomplete/medium per last comment
** Changed in: eucalyptus (Ubuntu)
Importance: High = Medium
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Incomplete
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Paul, upstream says they haven't hit such a limit in their testing, they
think it must come from some configuration issue or status that would be
carried from tests to tests.
Dan: could you please confirm that you don't run into any limit running the
same test that Paul ran in comment 10,
Paul, upstream says they haven't hit such a limit in their testing, they
think it must come from some configuration issue or status that would be
carried from tests to tests.
Dan: could you please confirm that you don't run into any limit running the
same test that Paul ran in comment 10,
** Tags added: uec
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
** Tags added: uec
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
We need some upstream advice on this...
Note that VNET_PUBLICIPS=192.168.3.1-192.168.5.254 is, I think, incorrect.
PUBLICIPS only accepts ranges within a single class C. You should write instead:
VNET_PUBLICIPS=192.168.3.1-192.168.3.255 192.168.4.0-192.168.4.255
192.168.5.0-192.168.5.254
Note
new tests : v27.1 rebooted cluster, creating security groups,
VNET_ADDRSPERNET=512
VNET_PUBLICIPS=192.168.3.1-192.168.5.254
launching vms :
export EMI=emi-4158125D
euca-run-instances $EMI -n 50 -k mykey -t c1.medium --addressing private
--group group2
euca-run-instances $EMI -n 50 -k mykey -t
Thanks a lot for this precious testing on your impressive configuration.
I see the following in cc.log:
running cmd '///usr/lib/eucalyptus/euca_rootwrap ip addr add 172.19.16.1/23
broadcast 172.19.17.255 dev eth0:priv label eth0:priv'
could not bring up new device eth0 with ip 172.19.16.1
** Attachment added: symptom : instances being terminated by security groups
http://launchpadlibrarian.net/34539244/instances.weird
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of
VNET_ADDRSPERNET=32
see logs_3.tar.bz2 ...
result : euca-describe-instances |grep running|wc = 75
export EMI=emi-4158125D
euca-add-group -d Group 10 group10
euca-add-group -d Group 11 group11
euca-add-group -d Group 12 group12
euca-add-group -d Group 13 group13
euca-add-group -d Group 14 group14
new tests : v27.1 rebooted cluster, creating security groups,
VNET_ADDRSPERNET=512
VNET_PUBLICIPS=192.168.3.1-192.168.5.254
launching vms :
export EMI=emi-4158125D
euca-run-instances $EMI -n 50 -k mykey -t c1.medium --addressing private
--group group2
euca-run-instances $EMI -n 50 -k mykey -t
Thanks a lot for this precious testing on your impressive configuration.
I see the following in cc.log:
running cmd '///usr/lib/eucalyptus/euca_rootwrap ip addr add 172.19.16.1/23
broadcast 172.19.17.255 dev eth0:priv label eth0:priv'
could not bring up new device eth0 with ip 172.19.16.1
** Attachment added: symptom : instances being terminated by security groups
http://launchpadlibrarian.net/34539244/instances.weird
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of
VNET_ADDRSPERNET=32
see logs_3.tar.bz2 ...
result : euca-describe-instances |grep running|wc = 75
export EMI=emi-4158125D
euca-add-group -d Group 10 group10
euca-add-group -d Group 11 group11
euca-add-group -d Group 12 group12
euca-add-group -d Group 13 group13
euca-add-group -d Group 14 group14
** Attachment added: logs and config files (together)
http://launchpadlibrarian.net/34495573/log.tar.bz2
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This issue seems similar to what we ran into on the upstream side which
revnos 931 and 933 fixed.
I can attempt to reproduce it from source against the latest upstream.
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Paul,
are these overprovisioned nodes? Or are those 384 real cores?
It looks like the front end is timing out while processing requests
because the nodes may not be responding fast enough.
What about disk? Can you walk us through your hardware config?
thanks
neil
--
maximum 61 running
Neil, we are talking about 384 cores seen by the sum of all OSes (64 per node
OS).
No special trick to overprovisione the nodes.
In the new intel machines Nehalem class, we have a technology called
hyperthreading (remember pentium 4 ? same thing).
There's 192 physical cores, but seen as 384
Nope, hyperthreading should be fine.
I strongly suspect that addresses per subnet in eucalyptus.conf is either set
to 64 (that will give you 61 instances max and is consistent with your
behavior) or you increased the value but didn't restart the CC (it need to
cleanrestart).
Can you post
hello
The conf is in the attached tar file, but i changed the value from 32
(default) to 512 from the beginning of the install (i ran into this
VNET_ADDRPERNET problem yesterday). 64 was never entered.
I've just rebooted the entire cluster and ran more tests. I can have more than
61 instances
** Attachment added: logs and config files (together)
http://launchpadlibrarian.net/34495573/log.tar.bz2
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This issue seems similar to what we ran into on the upstream side which
revnos 931 and 933 fixed.
I can attempt to reproduce it from source against the latest upstream.
--
maximum 61 running instances, others shutting down
https://bugs.launchpad.net/bugs/462140
You received this bug
Paul,
are these overprovisioned nodes? Or are those 384 real cores?
It looks like the front end is timing out while processing requests
because the nodes may not be responding fast enough.
What about disk? Can you walk us through your hardware config?
thanks
neil
--
maximum 61 running
Neil, we are talking about 384 cores seen by the sum of all OSes (64 per node
OS).
No special trick to overprovisione the nodes.
In the new intel machines Nehalem class, we have a technology called
hyperthreading (remember pentium 4 ? same thing).
There's 192 physical cores, but seen as 384
Nope, hyperthreading should be fine.
I strongly suspect that addresses per subnet in eucalyptus.conf is either set
to 64 (that will give you 61 instances max and is consistent with your
behavior) or you increased the value but didn't restart the CC (it need to
cleanrestart).
Can you post
hello
The conf is in the attached tar file, but i changed the value from 32
(default) to 512 from the beginning of the install (i ran into this
VNET_ADDRPERNET problem yesterday). 64 was never entered.
I've just rebooted the entire cluster and ran more tests. I can have more than
61 instances
41 matches
Mail list logo
