API Extensions¶

API extensions provide a standardized way of introducing new API functionality. While the neutron-lib project itself does not serve an API, the neutron project does and leverages the API extension framework from neutron-lib.

API extensions consist of the following high-level constructs:

• API definitions that specify the extension’s static metadata. This metadata includes basic details about the extension such as its name, description, alias, etc. as well as its extended resources/sub-resources and required/optional extensions. These definitions live in the neutron_lib.api.definitions package.
• API reference documenting the APIs/resources added/modified by the extension. This documentation is in rst format and is used to generate the openstack API reference. The API reference lives under the api-ref/source/v2 directory of the neutron-lib project repository.
• An extension descriptor class that must be defined in an extension directory for neutron or other sub-project that supports extensions. This concrete class provides the extension’s metadata to the API server. These extension classes reside outside of neutron-lib, but leverage the base classes from neutron_lib.api.extensions. For more details see the section below on using neutron-lib’s extension classes.
• The API extension plugin implementation itself. This is the code that implements the extension’s behavior and should carry out the operations defined by the extension. This code resides under its respective project repository, not in neutron-lib. For more details see the neutron api extension dev-ref.

from neutron_lib.api.definitions import provider_net
from neutron_lib.api import extensions


class Providernet(extensions.APIExtensionDescriptor):
    api_definition = provider_net
    # nothing else needed if default behavior is acceptable