Carl Baldwin c7d0d2e569 Add address scope to ports in RPC response to L3 agent

The L3 agent needs to know the address scope of each port of each
router it sets up in order to enforce isolation between scopes.

This commit adds a devref for the address scopes and subnet pools
features.

Change-Id: I6a7b3708fadefff1919d70ab1b8bc345b3fbe81c
Partially-Implements: blueprint address-scopes

2015-12-07 21:57:41 +00:00

2.3 KiB

Raw Blame History

Developer Guide

In the Developer Guide, you will find information on Neutron's lower level programming APIs. There are sections that cover the core pieces of Neutron, including its database, message queue, and scheduler components. There are also subsections that describe specific plugins inside Neutron. Finally, the developer guide includes information about Neutron testing infrastructure.

Programming HowTos and Tutorials

effective_neutron development.environment contribute neutron_api client_command_extensions alembic_migrations

Neutron Internals

services_and_agents api_layer quota api_extensions plugin-api db_layer policy rpc_api rpc_callbacks layer3 l2_agents ovs_vhostuser quality_of_service advanced_services oslo-incubator callbacks dns_order upgrade i18n instrumentation address_scopes

Testing

fullstack_testing testing_coverage template_model_sync_test

Module Reference

Add in all the big modules as automodule indexes.

Indices and tables

genindex
modindex
search

2.3 KiB Raw Blame History