cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiroaki Kawai (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1638) Network plugins won't be notified VM migration.
Date Wed, 13 Mar 2013 06:24:12 GMT


Hiroaki Kawai commented on CLOUDSTACK-1638:

Yes. As far as a plugin that handles migration wants to be run on, all the versions of cloudstack
will be affected. I shall update affected versions.
> Network plugins won't be notified VM migration.
> -----------------------------------------------
>                 Key: CLOUDSTACK-1638
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Hiroaki Kawai
>            Assignee: Hiroaki Kawai
>              Labels: patch
> The location of the virtual machine is provided by DeployDestination, which will be passed
in NetworkGuru#reserve and NetworkElement#prepare.
> During the virtual machine migration, it actually changes DeployDestination and it looks
like that it will tell that event to network components as it has NetworkManager#prepareNicForMigration.
The problem is that althogh the interface has that method, NetworkManagerImpl does not tell
the DeployDestination changes to network components.
> So IMHO, we need to add calls of NetworkGuru#reserve and NetworkElement#prepare in NetworkManagerImpl#prepareNicForMigration
. And then, we also need to add calls NetworkGuru#release and NetworkElement#release after
the migration, otherwise the network resources that plugin reserved will be kept even when
the vm leaves off.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message