Understanding the Neutron Server layering model-5 minutes a day to play with OpenStack (69)

This section begins by discussing the various service components of Neutron, first learning Neutron Server.

Is the hierarchical structure of the Neutron Server, which is first and foremost the following:

Core API
Provides a RESTful API for managing network, subnet and ports externally.

Extension API
Provide external management router, load balance, firewall and other resources of RESTful API.

Commnon Service
Authentication and validation of API requests.

Neutron Core
Neutron server's core handler, which processes the request by invoking the appropriate Plugin.

Core Plugin API
Defines the set of abstract functions for core Plgin, Neutron core calls the corresponding core plgin through the API.

Extension Plugin API
Defines the set of abstract functions for service Plgin, Neutron Core calls the appropriate service Plgin through the API.

Core Plugin
The Core Plugin API is implemented to maintain the state of network, subnet, and port in the database, and is responsible for invoking the appropriate agent to perform related operations on the network provider, such as creating a network.

Service Plugin
Implements the Extension Plugin API, maintains the status of router, load balance, security group and other resources in the database, and is responsible for invoking the appropriate agent to perform related operations on network provider, such as creating Built router.

To sum up, Neutron Server consists of two parts: 1. Provides API services. 2. Run Plugin.

That is Neutron Server = API + Plugins

Understanding the layered model of Neutron Server makes it easier to understand how Neutron supports various network provider.
We'll discuss this in more detail in the next section.

Understanding the Neutron Server layering model-5 minutes a day to play with OpenStack (69)