Hello all,
I have been trying some new ideas on scheduler and I think I'm reaching a
resource issue. I'm running 6 compute service right on my 4 CPU 4 Gig VM, and I
started to get some memory allocation issues. Keystone and Nova are already
complaining there is not enough memory. The obvious so
On 24 February 2014 16:24, David Peraza wrote:
> Hello all,
>
> I have been trying some new ideas on scheduler and I think I'm reaching a
> resource issue. I'm running 6 compute service right on my 4 CPU 4 Gig VM,
> and I started to get some memory allocation issues. Keystone and Nova are
> alread
ginal Message-
From: John Garbutt [mailto:j...@johngarbutt.com]
Sent: Monday, February 24, 2014 11:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Simulating many fake nova compute nodes for
scheduler testing
On 24 February 2014 16:24,
g script.)
Best regards,
Toan
> -Message d'origine-
> De : David Peraza [mailto:david_per...@persistentsys.com]
> Envoyé : lundi 24 février 2014 21:13
> À : OpenStack Development Mailing List (not for usage questions)
> Objet : Re: [openstack-dev] [nova] Simulatin
Garbutt [mailto:j...@johngarbutt.com]
> Sent: Monday, February 24, 2014 11:51 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] Simulating many fake nova compute nodes
> for scheduler testing
>
> On 24 February 2014 16:24,
On Tue, 2014-02-25 at 10:45 +, John Garbutt wrote:
>
> As a heads up, the overheads of DB calls turned out to dwarf any
> algorithmic improvements I managed. There will clearly be some RPC
> overhead, but it didn't stand out as much as the DB issue.
>
> The move to conductor work should certa
threads talking
> to
each
> other over rabbit or qpid. I'm trying to test out performance as well.
>
> Regards,
> David Peraza
>
> -Original Message-
> From: John Garbutt [mailto:j...@johngarbutt.com]
> Sent: Monday, February 24, 2014 11:51 AM
> To: OpenSta
rbutt [mailto:j...@johngarbutt.com]
Sent: Tuesday, February 25, 2014 5:45 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Simulating many fake nova compute nodes for
scheduler testing
On 24 February 2014 20:13, David Peraza wrote:
> Tha
David Peraza писал(а) в своём письме Mon,
03 Mar 2014 21:27:01 +0200:
Using compute inside LXC, I created 100 computes per physical host. Here
is what I did, it's very simple:
- Creating a LXC with logical volume
- Installing a fake nova-compute inside the LXC
- Make a booting scrip
@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Simulating many fake nova compute nodes for
scheduler testing
David Peraza писал(а) в своём письме Mon,
03 Mar 2014 21:27:01 +0200:
>
> Using compute inside LXC, I created 100 computes per physical host. Here
> is what I did,
David Peraza писал(а) в своём письме Mon,
03 Mar 2014 23:52:12 +0200:
Thanks Sergey,
Will look into this, but still have the same question, would introducing
containers increase my footprint per fake compute service?
Yes. There is more then one processes running in the container.
I can
On Mon, Mar 3, 2014 at 3:10 PM, Sergey Skripnick wrote:
>
>
>
> I can run multiple compute service in same hosts without containers.
>> Containers give you a nice isolation and another way to try a more
>> realistic scenario, but my initial goal now is to be able to simulate many
>> fake compute
gt; À : OpenStack Development Mailing List (not for usage questions)
> Objet : Re: [openstack-dev] [nova] Simulating many fake nova compute
nodes
> for scheduler testing
>
> Thanks Khanh,
>
> I see the potential issue with using threads. Thanks for pointing out.
On using
&g
sage-
> From: John Garbutt [mailto:j...@johngarbutt.com]
> Sent: Tuesday, February 25, 2014 5:45 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] Simulating many fake nova compute nodes
> for scheduler testing
>
>
14 matches
Mail list logo
