openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00163
Re: Some insight into the number of instances Nova needs to spin up...
-
To:
"openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
-
From:
Erik Carlin <erik.carlin@xxxxxxxxxxxxx>
-
Date:
Wed, 29 Dec 2010 19:27:09 +0000
-
Accept-language:
en-US
-
In-reply-to:
<AANLkTinD0sbq5h1CDCAByRLgP65WT_=U+zJLzbF=UHG8@mail.gmail.com>
-
Thread-index:
AQHLp45iJZqn0I6GF0u6N3+b4zQVyA==
-
Thread-topic:
[Openstack] Some insight into the number of instances Nova needs to spin up...
-
User-agent:
Microsoft-MacOutlook/14.2.0.101115
We know Amazon is highly, highly elastic. While the instances launched
per day is impressive, we know that many of those instances have a short
life. I see Guy is now teaming up with CloudKick on this report. The EC2
instance ID enables precise measurement of instances launched, and
CloudKick provides some quantitative measure of lifetime of instances.
Last time I checked, those numbers we're something like 3% of EC2
instances launched via CK were still running (as a point of reference,
something like 80% of Rackspace cloud servers were still running).
To meet the elasticity demands of EC2, nova would need to support a high
change rate of adds/deletes (not to mention state polling, resizes, etc).
Is there a nova change rate target as well or just a physical host limit?
The 1M host limit still seems reasonable to me. Large scale deployments
will break into regions where each region is an independent nova
deployment that each has a 1M host limit.
Erik
On 12/29/10 10:47 AM, "Jay Pipes" <jaypipes@xxxxxxxxx> wrote:
>Some insight into the number of instances being spun up *per day* on
>AWS, *just in the US-East-1 region*:
>
>http://www.jackofallclouds.com/2010/12/recounting-ec2/
>
>Avg in 2010: 70,528 instances spun up each day
>Max: 150,800 instances in a single day
>
>Food for thought.
>
>What do we think Nova could/can support? I know we are aiming at
>supporting clouds of 1M physical hosts. Perhaps we need to re-assess?
>:)
>
>/me urges more prioritization of the openstack-ci (continuous
>integration and performance/stress testing) project in Cactus...
>
>-jay
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to : openstack@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack
>More help : https://help.launchpad.net/ListHelp
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.
Follow ups
References