Neutron - Create Subnet JSON examples not clear
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-api-site |
Fix Released
|
High
|
Dhriti Shikhar |
Bug Description
According to
https:/
and
http://
there are a bunch of options (tenant_id, gateway_ip, name, etc...) that supposedly could be part of the request, but are not demonstrated in this example.
In addition, options such as dns_nameservers and host_routes do not consistently appear in all different documentation pages.
Also, I am looking at these sources:
[2] https:/
[3] http://
[4] https:/
As a SDK developer I find that the fact these agree only partially very confusing. Can the manual be updated to contain the full list of request and response parameters?
-------
Built: 2014-04-04T15:28:54 00:00
git SHA: 49a00ab38529b20
URL: http://
source File: file:/home/
xml:id: POST_os-
affects: | openstack-manuals → openstack-api-site |
Changed in openstack-api-site: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in openstack-api-site: | |
assignee: | nobody → chandan kumar (chkumar246) |
Changed in openstack-api-site: | |
assignee: | chandan kumar (chkumar246) → Dhriti Shikhar (dhritishikhar) |
Changed in openstack-api-site: | |
status: | Triaged → In Progress |
Changed in openstack-api-site: | |
milestone: | none → kilo |
Here's the full list if it's helpful. I agree it would be good to include those in the docs: 10.4.0. 7:9696/ v2.0/subnets/ cd065bcb- 33aa-4eb2- a15d-4fc11bb5fb 11.json -X GET -H "X-Auth-Token: <snip>" -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python- neutronclient"
REQ: curl -i http://
DEBUG: neutronclient. client RESP:{'status': '200', 'content-length': '431', 'content-location': 'http:// 10.4.0. 7:9696/ v2.0/subnets/ cd065bcb- 33aa-4eb2- a15d-4fc11bb5fb 11.json', 'date': 'Tue, 15 Apr 2014 22:28:13 GMT', 'content-type': 'application/json; charset=UTF-8', 'x-openstack- request- id': 'req-57e0fbed- b6d3-4d2e- abce-7ff59f7afc b7'} {"subnet": {"name": "private-subnet", "enable_dhcp": true, "network_id": "43ecb539- 56c5-46f8- 9548-4f3add9f53 35", "tenant_id": "bed4c647343042 5fa7e794336173b fc2", "dns_nameservers": [], "gateway_ip": "10.0.0.1", "ipv6_ra_mode": null, "allocation_pools": [{"start": "10.0.0.2", "end": "10.0.0.254"}], "host_routes": [], "ip_version": 4, "ipv6_address_ mode": null, "cidr": "10.0.0.0/24", "id": "cd065bcb- 33aa-4eb2- a15d-4fc11bb5fb 11"}}
+------ ------- ------+ ------- ------- ------- ------- ------- ------- --+ ------- ------+ ------- ------- ------- ------- ------- ------- --+ 33aa-4eb2- a15d-4fc11bb5fb 11 | 56c5-46f8- 9548-4f3add9f53 35 | fa7e794336173bf c2 | ------- ------+ ------- ------- ------- ------- ------- ------- --+
| Field | Value |
+------
| allocation_pools | {"start": "10.0.0.2", "end": "10.0.0.254"} |
| cidr | 10.0.0.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.0.0.1 |
| host_routes | |
| id | cd065bcb-
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | private-subnet |
| network_id | 43ecb539-
| tenant_id | bed4c6473430425
+------