OpenStack Shared File Systems Service (Manila)

server migration across physical networks

Bug #2002019 reported by chuan137
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Medium
chuan137
OpenStack Shared File Systems Service (Manila) dalmatian-rc1

Bug Description

Hi,

I am using the server migration feature to migrate share servers from one host to another keeping the same share network. Current implementation assumes that the network on source and target host are in the same network segment, i.e. segmentation id is not changed. However, in our environments, the backend hosts may be connected to different physical networks. So the neutron networks consist of multiple segments, with different segmentation ids. Thus migration fails.

Steps to reproduce
==================

1. manila share-server-migration-check --preserve-snapshots True --writable True --nondisruptive True a85f022b-cddd-40bf-b95f-bfa84d64868c manila-share-netapp-ma01-md004@ma01-md004

Expected result
===============
compatible: True

Actual result
=============
compatible: False

Environment
===========
Manila: Xena
Storage: NetApp (dhss=True)
Neutron:
   type_drivers = vlan,vxlan
   tenant_network_types = vxlan,vlan

Best regards,
Chuan

See original description
chuan137 (chuan137)
description: updated
Changed in manila:
assignee: nobody → chuan137 (chuan137)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/manila/+/869720

Changed in manila:
status: New → In Progress
Revision history for this message
Maurice Escher (maurice-escher) wrote :

The required neutron enhancement is in https://bugs.launchpad.net/neutron/+bug/2003095

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on manila (master)

Change abandoned by "Chuan Miao <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/manila/+/922959

Revision history for this message
Vida Haririan (vhariria) wrote :

See related comments in manila-dalmatian-m2-bugsquash ethercal https://ethercalc.net/o2qsmjpagsfb

Carlos Eduardo (silvacarlose)
Changed in manila:
importance: Undecided → Medium
Goutham Pacha Ravi (gouthamr)
Changed in manila:
milestone: none → dalmatian-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.opendev.org/c/openstack/manila/+/869720
Committed: https://opendev.org/openstack/manila/commit/7085a3eaf10fdb15b850204e721f2f58a443699d
Submitter: "Zuul (22348)"
Branch: master

commit 7085a3eaf10fdb15b850204e721f2f58a443699d
Author: Chuan Miao <email address hidden>
Date: Mon Jul 1 13:02:56 2024 +0200

    svm migration across physical networks with multiple port bindings

    This patch provides the support for share server migrations between
    different physical networks. It is achieved by creating an inactive port
    binding on the target host during share server migration, and then cut
    it over to target host when migration completes. The implementation is
    driver agnostic, so this feature should be not limited to specific
    driver, although it is only tested against NetApp driver. The feature is
    enabled by a new share service option
    'server_migration_extend_neutron_network'. The support for multiple
    binding Manila ports is added in Neutron's 2023.1 release.

    Closes-Bug: #2002019
    Change-Id: I18d0dd1847a09f28989b1a2b62fc6ff8f8155def

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 19.0.0.0rc1

This issue was fixed in the openstack/manila 19.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.