You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Никита Миронов <n....@me.com> on 2012/11/25 17:25:16 UTC
Create instance
Hello.
Is it possible to create an instance with high settings? For example, 20 Ghz CPU and 16GB Memory.
Instantses standard characteristics is created without problems.
Re: Create instance
Posted by Nitin Mehta <Ni...@citrix.com>.
Yeah - thats correct. Its based on service offering.
One small point to make on cluster.cpu.allocated.capacity.disablethreshold is that it is the maximum capacity you want to allocate in the "cluster".
So if it is set to 90% then new vms won't be allocated to any cluster which is 90% allocated for cpu already.
On 27-Nov-2012, at 3:45 PM, Marc Cirauqui wrote:
> I think it's service offering of deployed vms
>
> thx
>
>
> On Tue, Nov 27, 2012 at 11:05 AM, Donal Lafferty
> <do...@citrix.com>wrote:
>
>> Is cluster.cpu.allocated.capacity.disablethreshold calculated using
>> current Host usage states or the service offering of the deployed VMs?
>>
>> -----Original Message-----
>> From: Marc Cirauqui [mailto:mcirauqui@gmail.com]
>> Sent: 27 November 2012 7:49 AM
>> To: cloudstack-users
>> Subject: Re: Create instance
>>
>> Hello,
>>
>> cpu.overprovisioning.factor is a multiplier on your actual CPU capacity.
>> Say you have 4 physical cores at 2 GHz each, you have a total capacity of
>> 8 GHz. An overprovisioning factor of 2 will make cloudstack to count as if
>> there were 16 GHz and allocate up to that.
>>
>> cluster.cpu.allocated.capacity.disablethreshold is the maximum capacity
>> you want to allocate. Based on the above example, you can set it to stop
>> allocating vms once you've reach 90% capacity (over overprovisioned cpu,
>> this is th 16 GHz).
>>
>> thx
>>
>>
>> On Mon, Nov 26, 2012 at 7:01 PM, Donal Lafferty
>> <do...@citrix.com>wrote:
>>
>>> I was thinking of
>>>
>>> cpu.overprovisioning.factor
>>>
>>> and
>>>
>>> cluster.cpu.allocated.capacity.disablethreshold
>>>
>>>
>>> DL
>>>
>>> -----Original Message-----
>>> From: Nitin Mehta [mailto:Nitin.Mehta@citrix.com]
>>> Sent: 26 November 2012 5:03 PM
>>> To: cloudstack-users@incubator.apache.org
>>> Subject: Re: Create instance
>>>
>>>
>>>
>>> On 26-Nov-2012, at 3:34 PM, Donal Lafferty wrote:
>>>
>>>> One thing to watch out for is that CloudStack caps the CPU and RAM
>>> allocated for a host. Unless you tweak/remove these limits, the
>>> allocator will fail to find you a host. Unless, that is, you actually
>>> have a server capable of allocating a VM 20Ghz and 16GB RAM.
>>>>
>>>>
>>>
>>> I am not sure I quite understand where CS caps the compute allocated
>>> for a host. Can you please site an example here ?
>>>
>>>
>>>> DL
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Никита Миронов [mailto:n.mironov@me.com]
>>>> Sent: 25 November 2012 4:25 PM
>>>> To: cloudstack-users@incubator.apache.org
>>>> Subject: Create instance
>>>>
>>>> Hello.
>>>> Is it possible to create an instance with high settings? For
>>>> example, 20
>>> Ghz CPU and 16GB Memory.
>>>> Instantses standard characteristics is created without problems.
>>>
>>>
>>
Re: Create instance
Posted by Marc Cirauqui <mc...@gmail.com>.
I think it's service offering of deployed vms
thx
On Tue, Nov 27, 2012 at 11:05 AM, Donal Lafferty
<do...@citrix.com>wrote:
> Is cluster.cpu.allocated.capacity.disablethreshold calculated using
> current Host usage states or the service offering of the deployed VMs?
>
> -----Original Message-----
> From: Marc Cirauqui [mailto:mcirauqui@gmail.com]
> Sent: 27 November 2012 7:49 AM
> To: cloudstack-users
> Subject: Re: Create instance
>
> Hello,
>
> cpu.overprovisioning.factor is a multiplier on your actual CPU capacity.
> Say you have 4 physical cores at 2 GHz each, you have a total capacity of
> 8 GHz. An overprovisioning factor of 2 will make cloudstack to count as if
> there were 16 GHz and allocate up to that.
>
> cluster.cpu.allocated.capacity.disablethreshold is the maximum capacity
> you want to allocate. Based on the above example, you can set it to stop
> allocating vms once you've reach 90% capacity (over overprovisioned cpu,
> this is th 16 GHz).
>
> thx
>
>
> On Mon, Nov 26, 2012 at 7:01 PM, Donal Lafferty
> <do...@citrix.com>wrote:
>
> > I was thinking of
> >
> > cpu.overprovisioning.factor
> >
> > and
> >
> > cluster.cpu.allocated.capacity.disablethreshold
> >
> >
> > DL
> >
> > -----Original Message-----
> > From: Nitin Mehta [mailto:Nitin.Mehta@citrix.com]
> > Sent: 26 November 2012 5:03 PM
> > To: cloudstack-users@incubator.apache.org
> > Subject: Re: Create instance
> >
> >
> >
> > On 26-Nov-2012, at 3:34 PM, Donal Lafferty wrote:
> >
> > > One thing to watch out for is that CloudStack caps the CPU and RAM
> > allocated for a host. Unless you tweak/remove these limits, the
> > allocator will fail to find you a host. Unless, that is, you actually
> > have a server capable of allocating a VM 20Ghz and 16GB RAM.
> > >
> > >
> >
> > I am not sure I quite understand where CS caps the compute allocated
> > for a host. Can you please site an example here ?
> >
> >
> > > DL
> > >
> > >
> > > -----Original Message-----
> > > From: Никита Миронов [mailto:n.mironov@me.com]
> > > Sent: 25 November 2012 4:25 PM
> > > To: cloudstack-users@incubator.apache.org
> > > Subject: Create instance
> > >
> > > Hello.
> > > Is it possible to create an instance with high settings? For
> > > example, 20
> > Ghz CPU and 16GB Memory.
> > > Instantses standard characteristics is created without problems.
> >
> >
>
RE: Create instance
Posted by Donal Lafferty <do...@citrix.com>.
Is cluster.cpu.allocated.capacity.disablethreshold calculated using current Host usage states or the service offering of the deployed VMs?
-----Original Message-----
From: Marc Cirauqui [mailto:mcirauqui@gmail.com]
Sent: 27 November 2012 7:49 AM
To: cloudstack-users
Subject: Re: Create instance
Hello,
cpu.overprovisioning.factor is a multiplier on your actual CPU capacity.
Say you have 4 physical cores at 2 GHz each, you have a total capacity of 8 GHz. An overprovisioning factor of 2 will make cloudstack to count as if there were 16 GHz and allocate up to that.
cluster.cpu.allocated.capacity.disablethreshold is the maximum capacity you want to allocate. Based on the above example, you can set it to stop allocating vms once you've reach 90% capacity (over overprovisioned cpu, this is th 16 GHz).
thx
On Mon, Nov 26, 2012 at 7:01 PM, Donal Lafferty
<do...@citrix.com>wrote:
> I was thinking of
>
> cpu.overprovisioning.factor
>
> and
>
> cluster.cpu.allocated.capacity.disablethreshold
>
>
> DL
>
> -----Original Message-----
> From: Nitin Mehta [mailto:Nitin.Mehta@citrix.com]
> Sent: 26 November 2012 5:03 PM
> To: cloudstack-users@incubator.apache.org
> Subject: Re: Create instance
>
>
>
> On 26-Nov-2012, at 3:34 PM, Donal Lafferty wrote:
>
> > One thing to watch out for is that CloudStack caps the CPU and RAM
> allocated for a host. Unless you tweak/remove these limits, the
> allocator will fail to find you a host. Unless, that is, you actually
> have a server capable of allocating a VM 20Ghz and 16GB RAM.
> >
> >
>
> I am not sure I quite understand where CS caps the compute allocated
> for a host. Can you please site an example here ?
>
>
> > DL
> >
> >
> > -----Original Message-----
> > From: Никита Миронов [mailto:n.mironov@me.com]
> > Sent: 25 November 2012 4:25 PM
> > To: cloudstack-users@incubator.apache.org
> > Subject: Create instance
> >
> > Hello.
> > Is it possible to create an instance with high settings? For
> > example, 20
> Ghz CPU and 16GB Memory.
> > Instantses standard characteristics is created without problems.
>
>
Re: Create instance
Posted by Marc Cirauqui <mc...@gmail.com>.
Hello,
cpu.overprovisioning.factor is a multiplier on your actual CPU capacity.
Say you have 4 physical cores at 2 GHz each, you have a total capacity of 8
GHz. An overprovisioning factor of 2 will make cloudstack to count as if
there were 16 GHz and allocate up to that.
cluster.cpu.allocated.capacity.disablethreshold is the maximum capacity you
want to allocate. Based on the above example, you can set it to stop
allocating vms once you've reach 90% capacity (over overprovisioned cpu,
this is th 16 GHz).
thx
On Mon, Nov 26, 2012 at 7:01 PM, Donal Lafferty
<do...@citrix.com>wrote:
> I was thinking of
>
> cpu.overprovisioning.factor
>
> and
>
> cluster.cpu.allocated.capacity.disablethreshold
>
>
> DL
>
> -----Original Message-----
> From: Nitin Mehta [mailto:Nitin.Mehta@citrix.com]
> Sent: 26 November 2012 5:03 PM
> To: cloudstack-users@incubator.apache.org
> Subject: Re: Create instance
>
>
>
> On 26-Nov-2012, at 3:34 PM, Donal Lafferty wrote:
>
> > One thing to watch out for is that CloudStack caps the CPU and RAM
> allocated for a host. Unless you tweak/remove these limits, the allocator
> will fail to find you a host. Unless, that is, you actually have a server
> capable of allocating a VM 20Ghz and 16GB RAM.
> >
> >
>
> I am not sure I quite understand where CS caps the compute allocated for a
> host. Can you please site an example here ?
>
>
> > DL
> >
> >
> > -----Original Message-----
> > From: Никита Миронов [mailto:n.mironov@me.com]
> > Sent: 25 November 2012 4:25 PM
> > To: cloudstack-users@incubator.apache.org
> > Subject: Create instance
> >
> > Hello.
> > Is it possible to create an instance with high settings? For example, 20
> Ghz CPU and 16GB Memory.
> > Instantses standard characteristics is created without problems.
>
>
RE: Create instance
Posted by Donal Lafferty <do...@citrix.com>.
I was thinking of
cpu.overprovisioning.factor
and
cluster.cpu.allocated.capacity.disablethreshold
DL
-----Original Message-----
From: Nitin Mehta [mailto:Nitin.Mehta@citrix.com]
Sent: 26 November 2012 5:03 PM
To: cloudstack-users@incubator.apache.org
Subject: Re: Create instance
On 26-Nov-2012, at 3:34 PM, Donal Lafferty wrote:
> One thing to watch out for is that CloudStack caps the CPU and RAM allocated for a host. Unless you tweak/remove these limits, the allocator will fail to find you a host. Unless, that is, you actually have a server capable of allocating a VM 20Ghz and 16GB RAM.
>
>
I am not sure I quite understand where CS caps the compute allocated for a host. Can you please site an example here ?
> DL
>
>
> -----Original Message-----
> From: Никита Миронов [mailto:n.mironov@me.com]
> Sent: 25 November 2012 4:25 PM
> To: cloudstack-users@incubator.apache.org
> Subject: Create instance
>
> Hello.
> Is it possible to create an instance with high settings? For example, 20 Ghz CPU and 16GB Memory.
> Instantses standard characteristics is created without problems.
Re: Create instance
Posted by Nitin Mehta <Ni...@citrix.com>.
On 26-Nov-2012, at 3:34 PM, Donal Lafferty wrote:
> One thing to watch out for is that CloudStack caps the CPU and RAM allocated for a host. Unless you tweak/remove these limits, the allocator will fail to find you a host. Unless, that is, you actually have a server capable of allocating a VM 20Ghz and 16GB RAM.
>
>
I am not sure I quite understand where CS caps the compute allocated for a host. Can you please site an example here ?
> DL
>
>
> -----Original Message-----
> From: Никита Миронов [mailto:n.mironov@me.com]
> Sent: 25 November 2012 4:25 PM
> To: cloudstack-users@incubator.apache.org
> Subject: Create instance
>
> Hello.
> Is it possible to create an instance with high settings? For example, 20 Ghz CPU and 16GB Memory.
> Instantses standard characteristics is created without problems.
RE: Create instance
Posted by Donal Lafferty <do...@citrix.com>.
One thing to watch out for is that CloudStack caps the CPU and RAM allocated for a host. Unless you tweak/remove these limits, the allocator will fail to find you a host. Unless, that is, you actually have a server capable of allocating a VM 20Ghz and 16GB RAM.
DL
-----Original Message-----
From: Никита Миронов [mailto:n.mironov@me.com]
Sent: 25 November 2012 4:25 PM
To: cloudstack-users@incubator.apache.org
Subject: Create instance
Hello.
Is it possible to create an instance with high settings? For example, 20 Ghz CPU and 16GB Memory.
Instantses standard characteristics is created without problems.
Re: Create instance
Posted by Matty Courtney <ma...@citrix.com>.
You can create instances as large as your hardware allows.
Note that the CPU speed is per vCPU, not a cumulative total, and your
underlying hardware must have physical cores large enough to accommodate a
vCPU. To get a VM that has 20GHz total you might create a service offering
with 8 vCPUs that are 2.5GHz each, unless you have a CPU with a 20GHz core
;-)
On 26/11/12 3:25 AM, "Никита Миронов" <n....@me.com> wrote:
>Hello.
>Is it possible to create an instance with high settings? For example, 20
>Ghz CPU and 16GB Memory.
>Instantses standard characteristics is created without problems.