yahoo-eng-team team mailing list archive

[OpenStack Infra <1971646@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/840565
Committed: https://opendev.org/openstack/neutron/commit/b534de966ba8f0b9362a77d1024cf7ef230c9ff1
Submitter: "Zuul (22348)"
Branch:    master

commit b534de966ba8f0b9362a77d1024cf7ef230c9ff1
Author: zhouhenglc <zhouhenglc@xxxxxxxxxx>
Date:   Thu May 5 11:18:07 2022 +0800

    [api]adds port_forwarding id when list floatingip
    
    if we list floating ip and want to operate a port forwarding, we cannot
    call the update 'port forwarding' api, because we don't know the port
    forwarding id.
    this patch adds the port forwarding returned contents: 'id' and
    'internal_port_id' when list floatingip.
    
    Closes-bug: #1971646
    Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/840584
    
    Change-Id: Ie1d9169cd07547491144776311d77d49b483d5ae


** 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/1971646

Title:
  [api]add port_forwarding_id when list floatingip

Status in neutron:
  Fix Released

Bug description:
  when we enable "port_forwarding" plugin and list floating ip, we can get like:
  {
      "floatingips": [
          {
              "router_id": "0303bf18-2c52-479c-bd68-e0ad712a1639",
              "description": "for test with port forwarding",
              "dns_domain": "my-domain.org.",
              "dns_name": "myfip3",
              "created_at": "2018-06-15T02:12:48Z",
              "updated_at": "2018-06-15T02:12:57Z",
              "revision_number": 1,
              "project_id": "4969c491a3c74ee4af974e6d800c62de",
              "tenant_id": "4969c491a3c74ee4af974e6d800c62de",
              "floating_network_id": "376da547-b977-4cfe-9cba-275c80debf57",
              "fixed_ip_address": null,
              "floating_ip_address": "172.24.4.42",
              "port_id": null,
              "id": "898b198e-49f7-47d6-a7e1-53f626a548e6",
              "status": "ACTIVE",
              "tags": [],
              "port_forwardings": [
                  {
                      "protocol": "tcp",
                      "internal_ip_address": "10.0.0.19",
                      "internal_port": 25,
                      "external_port": 2225
                  },
                  {
                      "protocol": "tcp",
                      "internal_ip_address": "10.0.0.18",
                      "internal_port": 16666,
                      "external_port": 8786
                  }
              ],
              "qos_network_policy_id": "174dd0c1-a4eb-49d4-a807-ae80246d82f4",
              "qos_policy_id": "29d5e02e-d5ab-4929-bee4-4a9fc12e22ae"
          }
      ]
  }

  if we list floating ip and want to operate a port forwarding, we still need call "/v2.0/floatingips/{floatingip_id}/port_forwardings" and get port_forwarding "id".
  this is inefficient.

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