Uploaded image for project: 'neutron'
  1. neutron
  2. NEUTRON-126

vnic_type of port missing in the model

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • None
    • Multiple
    • General
    • None
    • Operating System: All
      Platform: All

    • 5833
    • Normal

      It would be great to have binding:vnic_type of a port referenced in the model.

      Based on neutron's output it is being sent to ODL.

      {"port": {"status": "DOWN", "binding:host_id": "", "allowed_address_pairs": [], "device_owner": "", "binding:profile": {}, "fixed_ips": [

      {"subnet_id": "8e061929-d306-4215-93e6-9b6e3c31ee43", "ip_address": "10.0.0.3"}

      ], "id": "c1c7b704-a66f-49e4-b7a8-096dbbf317fb", "security_groups": ["762d1182-0a27-4362-b70f-d1d07528c408"], "device_id": "", "name": "", "admin_state_up": true, "network_id": "8933f2c2-c09a-4f6d-8738-905a41b64f82", "tenant_id": "e347f5302c974d449a7413db66360fea", "binding:vif_details": {}, "binding:vnic_type": "normal", "binding:vif_type": "unbound", "mac_address": "fa:16:3e:eb:4c:4d"}}

      ------------------------------------------------------------- +

      Field Value

      ------------------------------------------------------------- +

      admin_state_up True
      allowed_address_pairs  
      binding:host_id  
      binding:profile {}
      binding:vif_details {}
      binding:vif_type unbound
      binding:vnic_type normal
      device_id  
      device_owner  
      fixed_ips {"subnet_id": "8e061929-d306-4215-93e6...
      id c1c7b704-a66f-49e4-b7a8-096dbbf317fb
      mac_address fa:16:3e:eb:4c:4d
      name  
      network_id 8933f2c2-c09a-4f6d-8738-905a41b64f82
      security_groups 762d1182-0a27-4362-b70f-d1d07528c408
      status DOWN
      tenant_id e347f5302c974d449a7413db66360fea

      ------------------------------------------------------------- +

            Unassigned Unassigned
            tcechval Tomas Cechvala
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: