yahoo-eng-team team mailing list archive

[OpenStack Infra <1616745@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

https://review.openstack.org/350613
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 de3a3cda740dfa22152c8224c39aeb9e51642d93
Author: John Davidge <john.davidge@xxxxxxxxxxxxx>
Date:   Mon Aug 1 14:04:08 2016 +0100

    IP allocation with Service Subnets
    
    This changes the way that IPAM decides which subnets to use when
    assigning IPs to newly created ports. If the port has a defined
    device_owner, this is used to filter available subnets to choose
    from only those with a matching service_type or no service_type
    at all.
    
    If the given network has no service subnets, then the existing
    behaviour is used.
    
    A new IPAM exception is introduced to handle the following scenarios:
    1. A port is created with a device_owner and only non-matching service
       subnets exist.
    2. A port is created without a device owner, and no subnets exist
       without a service_type.
    
    With this patch, service subnets are now usable.
    
    Implements: blueprint service-subnets
    APIImpact: subnet-create and subnet-update with service_types
    DocImpact: IPs assigned to new ports will now come from a service subnet
    matching the port device_owner, if one exists.
    
    Closes-Bug: 1544768
    Change-Id: If3dd94a46bdee24c13d1f17c4f2e69af0cb8af63

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

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

Title:
      IP allocation with Service Subnets

Status in neutron:
  New

Bug description:
  https://review.openstack.org/350613
  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 de3a3cda740dfa22152c8224c39aeb9e51642d93
  Author: John Davidge <john.davidge@xxxxxxxxxxxxx>
  Date:   Mon Aug 1 14:04:08 2016 +0100

      IP allocation with Service Subnets
      
      This changes the way that IPAM decides which subnets to use when
      assigning IPs to newly created ports. If the port has a defined
      device_owner, this is used to filter available subnets to choose
      from only those with a matching service_type or no service_type
      at all.
      
      If the given network has no service subnets, then the existing
      behaviour is used.
      
      A new IPAM exception is introduced to handle the following scenarios:
      1. A port is created with a device_owner and only non-matching service
         subnets exist.
      2. A port is created without a device owner, and no subnets exist
         without a service_type.
      
      With this patch, service subnets are now usable.
      
      Implements: blueprint service-subnets
      APIImpact: subnet-create and subnet-update with service_types
      DocImpact: IPs assigned to new ports will now come from a service subnet
      matching the port device_owner, if one exists.
      
      Closes-Bug: 1544768
      Change-Id: If3dd94a46bdee24c13d1f17c4f2e69af0cb8af63

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