Reviewed:  https://review.openstack.org/302578
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a8ebbebd4ee0c3bb1452ea32f92e1588a6b35067
Submitter: Jenkins
Branch:    master

commit 7105f888ee1f52d2a462fc0ece3130dc0d3d49f5
Author: OpenStack Proposal Bot <email address hidden>
Date:   Thu Mar 31 06:28:06 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Ibe5d4d38834fbcb99c0332d3375659a21d94154e

commit 5de98cb2de2eca3d061488c55f96e6f7c9bc56a8
Author: OpenStack Proposal Bot <email address hidden>
Date:   Wed Mar 30 06:41:25 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Ia46d661560b1141c1c1522c9477c510d28a0d0e7

commit a9d55427b6e8d2472088e3d40a8a5151ce408283
Author: Moshe Levi <email address hidden>
Date:   Wed Mar 23 10:59:04 2016 +0200

    Fix detach SR-IOV when using LibvirtConfigGuestHostdevPCI
    
    This patch fixes an issue which was introduced by this
    change If3edc1965c01a077eb61984a442e0d778d870d75.
    Usually the vif config is of type LibvirtConfigGuestInterface,
    but some vif use LibvirtConfigGuestHostdevPCI config
    (e.g.  the ib_hostdev). The difference is that
    LibvirtConfigGuestInterface keeps the pci address in source_dev
    while LibvirtConfigGuestHostdevPCI has domain, bus, slot and
    function, instead of relying on the vif config type we can take the
    pci address for the neutron port.
    
    Closes-Bug: #1560860
    
    Change-Id: I62a7ff16f1c9c5da923451520fbeeabb5cc0c5c6
    (cherry picked from commit f15d9a9693b19393fcde84cf4bc6f044d39ffdca)

commit 5b6ee702df7ad901f68bec2ed8d43b66aa6d98c1
Author: OpenStack Proposal Bot <email address hidden>
Date:   Tue Mar 29 06:37:30 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Iad0e42a18bd3a7dcf216b4df17b9893e13382efe

commit 29042e06f7e570bd13607b62b997a6ae21db80c5
Author: OpenStack Proposal Bot <email address hidden>
Date:   Mon Mar 28 06:34:19 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: If159133a2e32c6ef53ba104751a3eb054a95b733

commit 3e9819dab8249ec9993b0b9874e80a78f2ed1754
Author: Matt Riedemann <email address hidden>
Date:   Sun Mar 27 19:31:32 2016 -0400

    Update cells blacklist regex for test_server_basic_ops
    
    Tempest change 9bee3b92f1559cb604c8bd74dcca57805a85a97a
    renamed a test in our blacklist so update the filter to
    handle the old and new name.
    
    The Tempest team is hesitant to revert the change so we
    should handle it ourselves and eventually move to using
    test uuids for our blacklist, but there might need to
    be work in devstack-gate for that first.
    
    Change-Id: Ibab3958044c21568d7fbbe0a298bb40bbbc20df3
    Closes-Bug: #1562323
    (cherry picked from commit e86b7fbb99de0c4cff6a9569f748bae1bde693a6)

commit c71c4e01b21da5b5b7cb262969e30d6a68b3c58a
Author: Sylvain Bauza <email address hidden>
Date:   Thu Mar 24 23:07:54 2016 +0100

    Stop providing force_hosts to the scheduler for move ops
    
    Since now we provide the original RequestSpec for move operations (unshelve,
    live-migrate and evacuate), it can also provide the original force_hosts/nodes
    to the scheduler.
    In that case, it means that if an admin was asking to boot an instance forcing
    to an host, a later move operation could then give again the forced value and
    then wouldn't permit to get a different destination which is an issue.
    
    TBH, that is not a problem for live-migrate and evacuate that do provide an
    optional host value (which bypasses then the scheduler) but since unshelve
    is not having this optional value, it would mean that we could only unshelve
    an forced instance to the same host.
    
    Change-Id: I03c22ff757d0ee1da9d69fa48cc4bdd036e6b13f
    Closes-Bug: #1561357
    (cherry picked from commit 446d15568e00a483d909dc5c565d70baf29179ad)

commit 73e4fb189abe098f0058d173044708119785e494
Author: OpenStack Proposal Bot <email address hidden>
Date:   Thu Mar 24 06:31:09 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Ide680eb6e11506d19cbaa549837a0ea448b9c401

commit ad3c069f69ca1ab2c1d9c6c18d762b7c26c5ad92
Author: Pawel Koniszewski <email address hidden>
Date:   Wed Mar 23 18:44:10 2016 +0100

    Try to repopulate instance_group if it is None
    
    There are cases that we need to create new RequestSpect object and we
    pass None for instance_group argument. It might cause server group
    policies to be omitted during filtering phase. Therefore if
    instance_group is None we should try to repopulate instance_group
    basing on data that is in filter_properties.
    
    Change-Id: Id7e669e0a6db1ff1052c42006f1a141bdb8cdf29
    Closes-Bug: #1561022
    (cherry picked from commit 00efcf3a4171d270fc3a7b9b4a9230332aea81e6)

commit 9b98668465e326cde844a8b012e4a0eec6c2844c
Author: OpenStack Proposal Bot <email address hidden>
Date:   Wed Mar 23 06:29:56 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: I3be6855101c04f36b9c06a69d16876cdf6f00c62

commit c7eb823fe73e3db5dca48df5879db18cbab5bd8d
Author: Sean Mooney <email address hidden>
Date:   Fri Jan 22 17:00:36 2016 +0000

    stop setting mtu when plugging vhost-user ports
    
    vhost-user is a userspace protocol to establish connectivity
    between a virto-net frontend typically qemu and a
    userspace virtio backend such as ovs with dpdk.
    
    vhost-user interfaces exist only in userspace from the host perspective
    and are not represented in the linux networking stack as kernel netdevs.
    As a result attempting to set the mtu on a vhost-user interface
    using ifconfig or ip link will fail with a device not found error.
    
    - this change removes a call to _set_device_mtu when plugging
      vhost-user interfaces.
    - this change prevents the device not found error from occurring
      which stopped vms booting with vhost-user interfaces
      due to an uncaught exception resulting in a failure to set the
      interface type in ovs.
    - this change make creating vhost-user interface
      an atomic action.
    
    This latent bug is only triggered when the mtu value is set to a
    value other than 0 which was the default proir to mitaka.
    
    Change-Id: I2e17723d5052d57cd1557bd8a173c06ea0dcb2d4
    Closes-Bug: #1533876
    (cherry picked from commit adf7ba61dd73fe4bfffa20295be9a4b1006a1fe6)

commit a598793ad92057f685100d3b0f30cbc1aa597d38
Author: OpenStack Proposal Bot <email address hidden>
Date:   Tue Mar 22 06:29:59 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Id73392e9f47d7ac891237869979d186386f34bfa

commit 23a202eee87a14b152e25eac1f9b6a0aa14a2bd3
Author: Matthew Booth <email address hidden>
Date:   Fri Mar 18 12:12:51 2016 +0000

    Fix conversion of config disks to qcow2 during resize/migration
    
    finish_migration contains some code which converts raw disks to qcow2
    when moving from a host which uses raw disks to a host which uses
    qcow2 disks. This was erroneously also converted config disks, which
    are hard-coded to be raw even when other disks are qcow2.
    
    This has always been broken, but it wasn't previously exposed because
    a subsequent bug unconditionally overwrote the qcow2 config disk with
    a new, raw one. Change I03e08fae97416ebe5cdedcf238a06d1b90203c5d
    changed the order of these 2 events, so that the erroneously-converted
    config drive was no longer overwritten, resulting in a qcow2 file
    being presented to the instance as raw.
    
    This change explicitly filters out config disks from conversion.
    
    Change-Id: I6bf3cd4f9e0e152bf69732d9a17f93c86dedbd40
    Closes-Bug: #1558343
    (cherry picked from commit 29fb0aca1623eb0c4a565d728501667a4c5e8136)

commit f0dc7dbb6823f15e3bad1e407c498b3ce0248665
Author: Pawel Koniszewski <email address hidden>
Date:   Tue Mar 15 16:13:38 2016 +0100

    xenapi: Fix when auto block_migration in the API
    
    When nova calculates live migration type it stores the calculated
    type in migrate_data.block_migration. Because of that we really should
    not use block_migration, because it might not be accurate in certain
    cases.
    
    Closes-Bug: #1557585
    Change-Id: I0796a4b9bfabb1b2132a8253963528a40b1fb680
    (cherry picked from commit 762605ca4c2ac990b53a50d8f2c52fc793e07c94)

commit adaa9dee27279e6dda5d95750c626e620ce496a8
Author: John Garbutt <email address hidden>
Date:   Tue Mar 15 18:23:36 2016 +0000

    xenapi: Fix up passing of sr_uuid_map
    
    Currently pre_live_migration breaks the chain of passing the migrate
    data between the different driver calls.
    
    Also, the place that was using sr_uuid_map was not looking for it in the
    migrate data object, where it now lives.
    
    Related-Bug: #1557585
    Change-Id: I6f210d876816dc59325f3c36c75c2df5c880c61e
    (cherry picked from commit 8e5188af4c5221faaa60b21fa9c35550a1380e9f)

commit 15372ef7cc42e43185aef3e8ec960436987970cf
Author: Bob Ball <email address hidden>
Date:   Tue Mar 15 16:21:00 2016 +0000

    xenapi: Fix the live-migrate aggregate check
    
    AggregateList now returns [] if the host is not in an
    aggregate.  This was causing an IndexError in XenAPI.
    
    This change also replaces the AggregateHostNotFound exception,
    which is not caught properly further up the stack, with the
    MigrationPreCheckError as this is a suitable substitute since
    the aggregate check is only part of the pre migration check.
    
    Probably introduced by Ibcb896b2eef673bce23491161ff394bcc87aa541
    
    Related-Bug: #1557585
    Change-Id: Icacd3cbe065ee8598e5e5f03bd73463b95ed2f75
    (cherry picked from commit 38738d79e0774cf71dfff8185330b1f45b64d9fc)

commit 61b4dcc18ffe0c2b00ef9984af28b7294bcaf68d
Author: OpenStack Proposal Bot <email address hidden>
Date:   Mon Mar 21 06:29:57 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Ife86c184c2b8971a18a278d68555d6d646792e25

commit e9804f545b97a3e84157a6cf74e8482cd9fafdc3
Author: OpenStack Proposal Bot <email address hidden>
Date:   Fri Mar 18 06:27:59 2016 +0000

    Imported Translations from Zanata
    
    For more information about this automatic import see:
    https://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: I50fa5f8d7efd9ef1638ec1fe31177d6210588638

commit a970127bf7d0de2328f8bdfe1f8201c3938b6d77
Author: Thierry Carrez <email address hidden>
Date:   Wed Mar 16 19:16:46 2016 +0100

    Update .gitreview for stable/mitaka
    
    Change-Id: Ie60313913fdb70d6fbbdcceced621e14d2cf54eb