Hey Kelven - This topic was discussed briefly in the past [1]. Are you able to provide any thoughts on Alex's ideas below?
-chip [1] http://markmail.org/message/fznrszaswruvlmuy On Tue, Sep 24, 2013 at 10:53:04AM -0500, Alex Ough wrote: > For a resolution without breaking possible flows, I'd like to add the value > of 'executeInSequence' to the global setting. > Is there any reason not to do this? > > Thanks > Alex Ough > > > On Mon, Sep 23, 2013 at 12:57 PM, Alex Ough <alex.o...@sungard.com> wrote: > > > All, > > > > After a little more investigation, I found that the 'MigrateCommand' > > defined its 'executeInSequence' method to return 'FALSE', which seems to > > make the vm migrations as serial even if the migration requests are > > dispatched to ha_worker in parallel. > > You can confirm this in line 56 of > > '/cloudstack/core/src/com/cloud/agent/api/MigrateCommand.java' > > > > So my question is if there is any reason why the method have been > > defined to return 'FALSE' always? > > And do we expect any side effects and/or malfunctioning if we change it to > > returning 'TRUE'? > > > > Any answers/comments will be very appreciated. > > Thanks > > Alex Ough > > > > > > On Wed, Sep 18, 2013 at 10:22 AM, Alex Ough <alex.o...@sungard.com> wrote: > > > >> I checked the vm migration when their host is set to a maintenance mode > >> and found that even if the orchestration layer fires the each vm migration > >> at the same time using a ha_worker thread, the actual migration seems to be > >> executed serially. > >> > >> Is this what we expect? And if so, any chance to make the actual > >> migrations in parallel? > >> > >> Thanks > >> Alex Ough > >> > > > >
