← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1298217] Re: Unable to connect VM to a specific subnet

 

On the neutron side - it is possible. You need to specify "fixed_ip" for the port. 
Fixed ip is a list of {ip_address, subnet_id} dicts. Ip address for fixed_ip may be omitted and then subnet_id will be used to allocate ip address from the appropriate subnet.

** Changed in: neutron
       Status: New => Invalid

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

Title:
  Unable to connect VM to a specific subnet

Status in OpenStack Neutron (virtual network service):
  Invalid
Status in OpenStack Compute (Nova):
  New

Bug description:
  VM can only connected (on creation or later) to a network and not to a specific subnet on that network.
  Same goes for port - you cannot create a port on a specific subnet in a network.

  This is inconsistent with router-interface-add which targets a
  specific subnet instead of network.

  It also greatly limits the user's ability to manage VMs in his own
  network

  port and VM creation should allow user to target a specific subnet.

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


References