Current Series Release Notes¶

16.0.0.0rc1-13¶

Tacker no longer depends on eventlet. The library has been removed from the requirements, and none of the services monkey patches the standard library anymore. The API runs as a WSGI application under a WSGI server such as uWSGI, and oslo.service uses its threading backend.

The eventlet based standalone API server tacker-server has been removed as part of the eventlet removal. Run the Tacker API with a WSGI server such as uWSGI or mod_wsgi using the tacker.api.wsgi.api:application WSGI application instead, as the devstack plugin does. The configuration options bind_host, bind_port, api_workers and the socket options of the removed server (backlog, tcp_keepidle, retry_until_window, max_header_line, use_ssl, ssl_ca_file, ssl_cert_file and ssl_key_file) have also been removed. The listen address and the number of workers are now configured on the WSGI server side.

Fixed that registering a VIM failed with an internal server error when MySQL 8.0 and PyMySQL 1.2.1 or later were used. Values of JSON columns were sent as bytes, which PyMySQL now sends as binary strings, and MySQL rejects binary strings for JSON columns.

Fixed the Kubernetes infra driver of the v1 VNF LCM API failing to generate the Kubernetes objects from manifests with Kubernetes Python client 37 or later, in which the models are based on pydantic. The objects are generated without validation as with the older clients. The sample MgmtDriver for container update is also fixed not to give a Pod object as the body of the API to delete a Pod, which is rejected by the clients.