Provider extension API operations

To use the provider extension with the default policy settings, you must have the administrative role.

This list shows example neutron commands that enable you to complete basic provider extension API operations:

Shows all attributes of a network, including provider attributes:
```
$ neutron net-show <name or net-id>
```

Creates a local provider network:

$ neutron net-create <name> --tenant_id <tenant-id> --provider:network_type local

When you create flat networks, <phys-net-name> must be known to the plug-in. See the OpenStack Configuration Reference for details. Creates a flat provider network:
```
$ neutron net-create <name> --tenant_id <tenant-id> --provider:network_type flat --provider:physical_network <phys-net-name>
```
When you create VLAN networks, <phys-net-name> must be known to the plug-in. See the OpenStack Configuration Reference for details on configuring network_vlan_ranges to identify all physical networks. When you create VLAN networks, <VID> can fall either within or outside any configured ranges of VLAN IDs from which tenant networks are allocated. Creates a VLAN provider network:
```
$ neutron net-create <name> --tenant_id <tenant-id> --provider:network_type vlan --provider:physical_network <phys-net-name> --provider:segmentation_id <VID>
```
When you create GRE networks, <tunnel-id> can be either inside or outside any tunnel ID ranges from which tenant networks are allocated.
After you create provider networks, you can allocate subnets, which you can use in the same way as other virtual networks, subject to authorization policy based on the specified <tenant_id>. Creates a GRE provider network:
```
$ neutron net-create <name> --tenant_id <tenant-id> --provider:network_type gre --provider:segmentation_id <tunnel-id>
```