Happened to take a look at virtualmachinemanagerimpl on master, during reviewing storage migration code. Just want to know, what's the difference between migrate and migrateforscale in VirtualmachineManagerImpl? Is it necessary to duplicate code?
> -----Original Message----- > From: Nitin Mehta [mailto:nitin.me...@citrix.com] > Sent: Monday, March 18, 2013 9:10 AM > To: cloudstack-...@incubator.apache.org > Subject: [MERGE] scaleupvm functionality branch to master > > I would like to merge scale up vm functionality branch to master > > Spec : > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+scaling > +of+CPU+and+RAM > > JIRA ticket : > https://issues.apache.org/jira/browse/CLOUDSTACK-658 > > Branch: > Scaleupvm > > Notes:- > > 1. I have removed the vm state change in the code and so there is no vm > state machine change. I am planning to achieve the synchronization using > async job framework. I will make this change once I get a reply from Kelvn > (minor change) > 2. With the changes in #1 this feature is independent and should not be > intrusive to any functionality. > > Thanks, > -Nitin
