neutron provider and multi provider extensions not supported

Bug #1351153 reported by Rahul
6
This bug affects 1 person
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:network_type - Specifies the nature of the physical network mapped to this network resource. Examples are flat, vlan, or gre.

provider:physical_network - Identifies the physical network on top of which this network object is being implemented. The OpenStack Networking API does not expose any facility for retrieving the list of available physical networks. As an example, in the Open vSwitch plug-in this is a symbolic name which is then mapped to specific bridges on each compute host through the Open vSwitch plug-in configuration file.

provider:segmentation_id - Identifies an isolated segment on the physical network; the nature of the segment depends on the segmentation model defined by network_type. For instance, if network_type is vlan, then this is a vlan identifier; otherwise, if network_type is gre, then this will be a gre key.

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/<network-id> operation, this implies the user submitting the request is not authorized to view or manipulate provider network attributes.

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/{network_id}
Shows details for a specified network.

PUT /v2.0/networks/{network_id}
Updates a specified network.

DELETE /v2.0/networks/{network_id}
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": [
            {
                "provider:segmentation_id": "2",
                "provider:physical_network": "8bab8453-1bc9-45af-8c70-f83aa9b50453",
                "provider:network_type": "vlan"
            },
            {
                "provider:physical_network": "8bab8453-1bc9-45af-8c70-f83aa9b50453",
                "provider:network_type": "stt"
            }
        ],
        "name": "net1",
        "admin_state_up": true
    }
}

 Response

Example 4.169. Create network with multiple segment mappings: JSON response

{
    "network": {
        "status": "ACTIVE",
        "subnets": [],
        "name": "net1",
        "admin_state_up": true,
        "tenant_id": "9bacb3c5d39d41a79512987f338cf177",
        "segments": [
            {
                "provider:segmentation_id": 2,
                "provider:physical_network": "8bab8453-1bc9-45af-8c70-f83aa9b50453",
                "provider:network_type": "vlan"
            },
            {
                "provider:segmentation_id": null,
                "provider:physical_network": "8bab8453-1bc9-45af-8c70-f83aa9b50453",
                "provider:network_type": "stt"
            }
        ],
        "shared": false,
        "port_security_enabled": true,
        "id": "4e8e5957-649f-477b-9e5b-f1f75b21c03c"
    }
}

tags: added: neutronapi
information type: Proprietary → Public
Changed in juniperopenstack:
status: New → Won't Fix
milestone: none → r1.10-fcs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.