yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1861529@xxxxxxxxxxxxxxxxxx>]

During our last drivers meeting on 28.02.2020 we were discussing this
rfe and we agreed that for now we are not going to accept it as this
would require big changes in both: neutron basic concepts and code and
it's only to support some very old, legacy guest operating systems.

But if You will have better use cases for this RFE, feel free to reopen
this RFE and propose spec with detailed use cases and rationale for it.

** Tags removed: rfe-triaged
** Tags added: rfe

** Changed in: neutron
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1861529

Title:
  [RFE] A port's network should be changable

Status in neutron:
  Won't Fix

Bug description:
  We want a way to change a VM port’s network when the VM’s operating
  system does not support online removal and addition of devices.

  These are the steps to accomplish this:
  Given a running VM. We want to change the network of <vm-port-id>.  No floating IP is associated with the VM.

  # openstack port set –no-fixed-ip <vm-port-id>
  # openstack port set –network-id <new-net-id> <vm-port-id>
  # openstack port set –fixed-ip subnet=<new-subnet> <vm-port-id>

  Neutron-server succeeds  with changing the port’s network-id if:

      1. The new network belongs to the same project as the original network.
      2. The port has no fixed-ip addresses on it.
      3. The port’s mac address is unused on the new network.
      4. The new network’s MTU is greater than or equal to the old network’s.

  Some operating systems may be unable to handle online addition and
  deletion of devices.  We want a way of changing a VM’s port’s network
  that does not rely on the guest operating system supporting these
  capabilities.

  The change is done by making the port’s network-id attribute to allow
  PUT requests. Neutron api server checks whether the 4 criteria are
  met.  Then it will proceed with updating the port. When the new fixed-
  ip is set, the user will have to login to the VM’s console and
  manually change the guest OS’s configuration to make use of the new IP
  address.

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