yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on.

In case you want to work on that, consider writing a blueprints [1] and
spec [2]. I'll recommend to read [3] if not yet done. The effort to
implement the requested feature is then driven only by the blueprint
(and spec).

References:
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints

** Changed in: nova
       Status: Confirmed => Opinion

-- 
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/1298217

Title:
  Unable to connect VM to a specific subnet

Status in OpenStack Compute (nova):
  Opinion

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/nova/+bug/1298217/+subscriptions