Tacker WSGI/HTTP API layer =========================== This section will cover the internals of Tacker's HTTP API, and the classes in Tacker that can be used to create Extensions to the Tacker API. Python web applications interface with webservers through the Python Web Server Gateway Interface (WSGI) - defined in `PEP 333 `_ Startup ------- Tackers's WSGI server is started from the `server module `_ and the entry point `serve_wsgi` is called to build an instance of the `TackerApiService`_, which is then returned to the server module, which spawns a `Eventlet`_ `GreenPool`_ that will run the WSGI application and respond to requests from clients. .. _TackerApiService: http://git.openstack.org/cgit/openstack/tacker/tree/tacker/service.py .. _Eventlet: http://eventlet.net/ .. _GreenPool: http://eventlet.net/doc/modules/greenpool.html WSGI Application ---------------- During the building of the TackerApiService, the `_run_wsgi` function creates a WSGI application using the `load_paste_app` function inside `config.py`_ - which parses `api-paste.ini`_ - in order to create a WSGI app using `Paste`_'s `deploy`_. The api-paste.ini file defines the WSGI applications and routes - using the `Paste INI file format`_. The INI file directs paste to instantiate the `APIRouter`_ class of Tacker, which contains several methods that map VNFM resources (such as vnfd, vnf) to URLs, and the controller for each resource. .. _config.py: http://git.openstack.org/cgit/openstack/tacker/tree/tacker/common/config.py .. _api-paste.ini: http://git.openstack.org/cgit/openstack/tacker/tree/etc/tacker/api-paste.ini .. _APIRouter: http://git.openstack.org/cgit/openstack/tacker/tree/tacker/api/v2/router.py .. _Paste: http://pythonpaste.org/ .. _Deploy: http://pythonpaste.org/deploy/ .. _Paste INI file format: http://pythonpaste.org/deploy/#applications Further reading --------------- Tacker wsgi is based on neutron's extension. The following doc is still relevant. `Yong Sheng Gong: Deep Dive into Neutron `_