Public bug reported:

https://review.openstack.org/245005
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/nova" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

commit af41accff9456748a3106bc1206cfc22d10a8cf4
Author: Kevin_Zheng <zhengzhe...@huawei.com>
Date:   Fri Nov 13 14:14:28 2015 +0800

    Split-network-plane-for-live-migration
    
    When we do live migration with QEMU/KVM driver,
    we use hostname of target compute node as the
    target of live migration. So the RPC call and live
    migration traffic will be in same network plane.
    
    This patch adds a new option live_migration_inbound_addr
    in configuration file, set None as default value.
    When pre_live_migration() executes on destination host, set
    the option into pre_migration_data, if it's not None.
    When driver.live_migration() executes on source host,
    if this option is present in pre_migration_data, the ip/hostname
    address is used instead of CONF.libvirt.live_migration_uri
    as the uri for live migration, if it's None, then the
    mechanism remains as it is now.
    
    This patch (BP) focuses only on the QEMU/KVM driver,
    the implementations for other drivers should be done
    in a separate blueprint.
    
    DocImpact:new config option "live_migration_inbound_addr" will be added.
    
    Change-Id: I81c783886497a844fb4b38d0f2a3d6c18a99831c
    Co-Authored-By: Rui Chen <chenrui.m...@gmail.com>
    Implements: blueprint split-network-plane-for-live-migration

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: doc nova

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1542421

Title:
      Split-network-plane-for-live-migration

Status in OpenStack Compute (nova):
  New

Bug description:
  https://review.openstack.org/245005
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/nova" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit af41accff9456748a3106bc1206cfc22d10a8cf4
  Author: Kevin_Zheng <zhengzhe...@huawei.com>
  Date:   Fri Nov 13 14:14:28 2015 +0800

      Split-network-plane-for-live-migration
      
      When we do live migration with QEMU/KVM driver,
      we use hostname of target compute node as the
      target of live migration. So the RPC call and live
      migration traffic will be in same network plane.
      
      This patch adds a new option live_migration_inbound_addr
      in configuration file, set None as default value.
      When pre_live_migration() executes on destination host, set
      the option into pre_migration_data, if it's not None.
      When driver.live_migration() executes on source host,
      if this option is present in pre_migration_data, the ip/hostname
      address is used instead of CONF.libvirt.live_migration_uri
      as the uri for live migration, if it's None, then the
      mechanism remains as it is now.
      
      This patch (BP) focuses only on the QEMU/KVM driver,
      the implementations for other drivers should be done
      in a separate blueprint.
      
      DocImpact:new config option "live_migration_inbound_addr" will be added.
      
      Change-Id: I81c783886497a844fb4b38d0f2a3d6c18a99831c
      Co-Authored-By: Rui Chen <chenrui.m...@gmail.com>
      Implements: blueprint split-network-plane-for-live-migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1542421/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to