Jump to: navigation, search


  • Launchpad Entry: NovaSpec:bexar-migration-live
  • Created: 2010-10-20
  • Contributors: Kei Masumoto, Muneyuki Noguchi, Masanori Itoh, Tushar Patil


  • On the 2nd Design Summit, please see: http://etherpad.openstack.org/LiveMigration
  • Please see attached PPT presented at the Bexar Design Summit and the above etherpad note.
  • Please see notes in the Dependency section.


Add a capability for migrating a running VM from one host to another host transparently to applications and any external entity interacting with such applications on the cloud server without taking down the cloud server and with a very negligible downtime.


A Special Note:

This blueprint, bexar-migration-live, depends on bexar-network-service in the following sense.

  • After we have bexar-migration-live, we can attach multiple NICs to a VM. Live Migration feature should support migrating network connectivity together with the VM. In this sense, this blueprint depends on bexar-network-service blueprint.
  • We are planning 2 phase step development.
    • Step 1) Implement live migration feature using austin release code base.
    • Step 2) Implement live migration feature using bexar-network-service API calls.
  • Thus, even if bexar-migration-live was deferred, still we can support under austin release network model(Step 1). In this sense, I think the dependency is a bit weak one. But, anyway I know that I have to follow the procedure changing specification after the Submission Deadline.