Open Stack

Hi Simhon,

We are in the process of removing the network-id argument from the tap-service-create API. There is a patch that has been submitted with this change and it is currently under review. We expect it to be merged very soon.

Thanks,
Anil

From: Simhon Doctori שמחון דוקטורי [mailto:simhond at gmail.com]
Sent: Wednesday, April 13, 2016 4:46 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [neutron][taas] service show omits the network id

Hi,
Although the network id is essential argument when creating the service, it is not shown when doing show for the service. Either using cli or rest-api.

{
  "tap_services": [
    {
      "tenant_id": "619ce6d9192c494fbf3dd7947ef78f9f",
      "port_id": "2250affe-6a38-4678-b4ab-969c36cc6f12",
      "description": "",
      "name": "tapServicePort",
      "id": "5afd1d73-0d8c-4931-bc6c-c8388ba6508f"
    }
  ]
}

neutron) tap-service-show 5afd1d73-0d8c-4931-bc6c-c8388ba6508f
+-------------+--------------------------------------+
| Field       | Value                                |
+-------------+--------------------------------------+
| description |                                      |
| id          | 5afd1d73-0d8c-4931-bc6c-c8388ba6508f |
| name        | tapServicePort                       |
| port_id     | 2250affe-6a38-4678-b4ab-969c36cc6f12 |
| tenant_id   | 619ce6d9192c494fbf3dd7947ef78f9f     |
+-------------+--------------------------------------+

Is this in purpose or a bug ?
Simhon Doctori
imVision Technologies.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160413/8d0dca15/attachment.html>