neutron provider and multi provider extensions not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Network provider and multi-provider extensions aren't supported.
Need to verify, if these make any sense with Contrail implementation.
=======
Provider networks (provider)
The provider extended attributes for networks enable administrative users to specify how network objects map to the underlying networking infrastructure. These extended attributes also appear when administrative users query networks.
To this aim, it extends the network resource by defining a set of attributes prefixed with provider.
These attributes are added to the network resource:
provider:
provider:
provider:
The actual semantics of these attributes depend on the technology back end of the particular plug-in. See the plug-in documentation and the OpenStack Cloud Administrator Guide to understand which values should be specific for each of these attributes when OpenStack Networking is deployed with a particular plug-in. The examples shown in this chapter refer to the Open vSwitch plug-in.
The default policy settings enable only users with administrative rights to specify these parameters in requests and to see their values in responses. By default, the provider network extension attributes are completely hidden from regular tenants. As a rule of thumb, if these attributes are not visible in a GET /networks/
Method URI Description
GET /v2.0/networks
Lists networks that are accessible to the tenant who submits the request.
POST /v2.0/networks
Creates a network.
GET /v2.0/networks/
Shows details for a specified network.
PUT /v2.0/networks/
Updates a specified network.
DELETE /v2.0/networks/
Deletes a specified network.
=======
In conjunction with segments, we need to see if multiple provider has any application for contrail usage.
Create network with multiple segment mappings
Request
Response
Method URI Description
POST /v2.0/networks
Creates a network with multiple segment mappings.
Normal response codes: 201
Request
Example 4.168. Create network with multiple segment mappings: JSON request
{
"network": {
"segments": [
{
},
{
}
],
"name": "net1",
}
}
Response
Example 4.169. Create network with multiple segment mappings: JSON response
{
"network": {
"status": "ACTIVE",
"subnets": [],
"name": "net1",
"segments": [
{
},
{
}
],
"shared": false,
"id": "4e8e5957-
}
}
tags: | added: neutronapi |
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
milestone: | none → r1.10-fcs |