er.
>>>
>>>VM States are different because there can be outside changes (through
>>>other vm managers) that cause vm life cycle to behave differently.
>>>
>>>--Alex
>>>
>>>> -Original Message-
>>>> From: Nitin Mehta
>>>
gt;--Alex
>>
>>> -Original Message-
>>> From: Nitin Mehta
>>> Sent: Saturday, March 9, 2013 2:35 AM
>>> To: cloudstack-dev@incubator.apache.org; Prashant Kumar Mishra;
>>> Abhinandan Prateek; Alex Huang
>>> Cc: Chip Childers
>&g
cubator.apache.org; Prashant Kumar Mishra;
>> Abhinandan Prateek; Alex Huang
>> Cc: Chip Childers
>> Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>>
>> Hi Alex,
>> I had one more question. Say the MS is shut down or restarted, when do
>>w
-Original Message-
> From: Nitin Mehta
> Sent: Saturday, March 9, 2013 2:35 AM
> To: cloudstack-dev@incubator.apache.org; Prashant Kumar Mishra;
> Abhinandan Prateek; Alex Huang
> Cc: Chip Childers
> Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>
> Hi Ale
hta [mailto:nitin.me...@citrix.com]
>>Sent: Tuesday, February 12, 2013 7:15 AM
>>To: Prashant Kumar Mishra; cloudstack-dev@incubator.apache.org;
>>Abhinandan Prateek
>>Cc: Chip Childers
>>Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>>
>>Apol
.me...@citrix.com]
>Sent: Tuesday, February 12, 2013 7:15 AM
>To: Prashant Kumar Mishra; cloudstack-dev@incubator.apache.org;
>Abhinandan Prateek
>Cc: Chip Childers
>Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>
>Apologize for the delayed response. Was involved i
ator.apache.org
>Cc: Nitin Mehta
>Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
>
>Hi Nitin,
>I am planning to take the QA job for this feature. Have reviewed the
>functional spec, gone through community discussion and have the
>following questions
>
gt;Cc: Nitin Mehta
>Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
>
>Hi Nitin,
>I am planning to take the QA job for this feature. Have reviewed the
>functional spec, gone through community discussion and have the
>following questions
>
>1-What is expected beh
To: cloudstack-dev@incubator.apache.org
> Cc: Nitin Mehta
> Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
>
> Need reply to complete my Test cases.
>
> -Original Message-
> From: Prashant Kumar Mishra [mailto:prashantkumar.mis...@citrix.com]
> Sent
-Original Message-
From: Prashant Kumar Mishra [mailto:prashantkumar.mis...@citrix.com]
Sent: Tuesday, February 05, 2013 5:16 PM
To: cloudstack-dev@incubator.apache.org
Cc: Nitin Mehta
Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
Need reply to complete my Test cases
Need reply to complete my Test cases.
-Original Message-
From: Prashant Kumar Mishra [mailto:prashantkumar.mis...@citrix.com]
Sent: Thursday, January 24, 2013 12:26 PM
To: cloudstack-dev@incubator.apache.org
Cc: Nitin Mehta
Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
Hi Nitin,
I am planning to take the QA job for this feature. Have reviewed the functional
spec, gone through community discussion and have the following questions
1-What is expected behavior of CS for Operating systems which do not support
dynamic scaling . ?
2-How much resources can be scale
gt;corrective actions like updating the DB
>
>
>
>>
>>The idea is to not handle every possible scenario, but to ensure that the
>>vm (and system) is in a sane recoverable state after the unexpected
>>interaction.
>>
>>
>>On 1/21/13 10:01 PM, &qu
nteraction.
>
>
>On 1/21/13 10:01 PM, "Koushik Das" wrote:
>
>>See inline for 1.
>>
>>-Original Message-
>>From: Hari Kannan [mailto:hari.kan...@citrix.com]
>>Sent: Tuesday, January 22, 2013 10:51 AM
>>To: cloudstack-dev@incubator.apach
, Dec 20, 2012 at 4:52 AM, Koushik Das
wrote:
See inline
Thanks,
Koushik
-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Wednesday, December 19, 2012 7:55 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] Scaling up CPU and RAM for ru
ix.com]
>Sent: Tuesday, January 22, 2013 10:51 AM
>To: cloudstack-dev@incubator.apache.org
>Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
>
>Hello Nitin, Koushik,
>
>I'm following up on this feature - is the FS located here still
>accurate/up to date?
>
&
See inline for 1.
-Original Message-
From: Hari Kannan [mailto:hari.kan...@citrix.com]
Sent: Tuesday, January 22, 2013 10:51 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [DISCUSS] Scaling up CPU and RAM for running VMs
Hello Nitin, Koushik,
I'm following up on this fe
n [mailto:shadow...@gmail.com]
>Sent: Thursday, December 20, 2012 9:47 AM
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>
>Oh, if it's not already obvious, we're onboard for collaborating on this
>feature and can help
Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Thursday, December 20, 2012 9:47 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
Oh, if it's not already obvious, we're onboard for collaborating on this
fea
inline
>>
>> Thanks,
>> Koushik
>>
>> > -Original Message-
>> > From: Chip Childers [mailto:chip.child...@sungard.com]
>> > Sent: Wednesday, December 19, 2012 7:55 PM
>> > To: cloudstack-dev@incubator.apache.org
>> > Sub
n [mailto:shadow...@gmail.com]
> > >> Sent: Tuesday, December 18, 2012 10:35 PM
> > >> To: cloudstack-dev@incubator.apache.org
> > >> Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
> > >>
> > >> The FS looks good and address
See inline
Thanks,
Koushik
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, December 19, 2012 7:55 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>
> On W
On Wed, Dec 19, 2012 at 3:34 AM, Koushik Das wrote:
> See inline
>
>> -Original Message-
>> From: Marcus Sorensen [mailto:shadow...@gmail.com]
>> Sent: Tuesday, December 18, 2012 10:35 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re:
[David]
I am worried about the effect of this on usage statistics, but still
sounds very useful.
[/David]
Currently EVENT_VM_UPGRADE is already handled in usage server, it
records upgraded service offering into usage DB (though i cant find
any codes that persist this eventType). Maybe this can be
See inline
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Sunday, December 16, 2012 3:56 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>
> On Sat, Dec 15, 2012 at 12:43 PM,
See inline
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Tuesday, December 18, 2012 10:35 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Scaling up CPU and RAM for running VMs
>
> The FS looks good and add
The FS looks good and addresses the things I'd want it to (scaling should
be limited to within cluster, use offerings).
As you mention, there's a real problem surrounding no support for scaling
down CPU, and it's just as much a problem with the guests as it is with
hvms at the moment, it seems. Th
Created first draft of the FS
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+scaling+of+CPU+and+RAM
Also created jira issue https://issues.apache.org/jira/browse/CLOUDSTACK-658
Comments? There is an 'open issue' section where I have mentioned some issues
that needs to be closed
On 18-Dec-2012, at 8:54 AM, Mice Xia wrote:
> Great feature and I believe a lot of customers need it, hope Xenserver will
> support dynamic memory change one day.
>
> [Koushik]
> Assuming that in the updated compute offering only CPU and RAM has changed,
> the deployment planner can either sel
Great feature and I believe a lot of customers need it, hope Xenserver will
support dynamic memory change one day.
[Koushik]
Assuming that in the updated compute offering only CPU and RAM has changed, the
deployment planner can either select the same host in which case the values are
dynamicall
You can scale down memory in KVM, but not CPU without a reboot. I'd like to
see this implemented as the ability to jump between service offerings
without reboot, and perhaps have a custom service offering that allows for
any custom number to be put in. That way people who utilize cloudstack can
cho
On Sat, Dec 15, 2012 at 12:43 PM, Koushik Das wrote:
> Currently CS supports changing CPU and RAM for stopped VM. This is achieved
> by changing compute offering of the VM (with new CPU and RAM values) and then
> starting it. I am planning to extend the same for running VM as well.
> Initially
Koushik
When you have something to test, let me know. We are big vmware shop, I can
test this when needed.
FYI, I wont be able test anything until I get back in the offfice which the
first week of January.
Last thing to note, not all operating systems support online increase of
cpu/mem. Linux
I was planning on looking at the same. With KVM, it requires that you
launch the vm with a max number and a current number. Then you can increase
up to max.
I agree that it will be important to migrate before scaling if necessary.
The scenario would likely be common and make the feature less usefu
34 matches
Mail list logo
