Reviewed: https://review.openstack.org/510689 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2ac329b90274ecbf7dd3234b39c74dc974658c30 Submitter: Jenkins Branch: master
commit 2ac329b90274ecbf7dd3234b39c74dc974658c30 Author: Boden R <[email protected]> Date: Mon Oct 9 14:49:49 2017 -0600 clarify deferred fixed IP assignment for ports on routed networks This patch clarifies the routed network configuration doc with respect to when a fixed IP is assigned to a port on a routed network. For more details see related bug. Change-Id: Id8e97afdfc488069ac3a910e017c34b085b4eb36 Closes-Bug: #1718320 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1718320 Title: Do not defer allocation if fixed-ips is in the port create request. Status in neutron: Fix Released Bug description: https://review.openstack.org/499954 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 630b2d1a5e8b8c6926a590eb87fedde12624c3da Author: Harald Jensas <[email protected]> Date: Sun Jun 4 23:41:19 2017 +0200 Do not defer allocation if fixed-ips is in the port create request. Fix a usage regression, use case #2 in Nova Neutron Routed Networks spec https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/neutron-routed-networks.html Currently ip allocation is always deferred if binding:host_id is not specified when routed networks are used. This causes initial fixed-ips data provided by the user to be _lost_ unless the user also specify the host. Since the user specified the IP or Subnet to allocate in, there is no reason to defer the allocation. a) It is a common pattern, especially in Heat templates to: 1. Create a port with fixed-ips specifying a subnet. 2. Create a server and associate the existing port. b) It is also common to use Neutron IPAM as a source to get VIP addresses for clusters on provider networks. This change enables these use cases with routed networks. DocImpact: "The Networking service defers assignment of IP addresses to the port until the particular compute node becomes apparent." This is no longer true if fixed-ips is used in the port create request. Change-Id: I86d4aafa1f8cd425cb1eeecfeaf95226d6d248b4 Closes-Bug: #1695740 (cherry picked from commit 33e48cf84db0f6b51a0f981499bbd341860b6c1c) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1718320/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
