Add a prelude to the Stein release notes

This patch adds a prelude to the stein release notes and fixes some
formatting issues in previous Stein release notes.

Change-Id: Ic0e8d9e70eb61ef471304ecfd9985c8da0725b3d
This commit is contained in:
Michael Johnson 2019-03-08 15:23:27 -08:00
parent ff1a4761be
commit 4c0fd91dcc
3 changed files with 35 additions and 12 deletions

View File

@ -0,0 +1,23 @@
---
prelude: |
For the OpenStack Stein release, the Octavia team is excited to announce
support for: Octavia flavors, TLS client authentication, backend
re-encryption, and object tags.
* Octavia flavors allow an operator to define "flavors" of load balancers,
such as "active-standby" or "single" using the amphora driver, that
configure the load balancer topology. The Amphora driver also supports
specifying the nova compute flavor to use for the load balancer amphora.
* TLS client authentication allows the listener to request a client
certificate from users connecting to the load balancer. This certificate
can then be checked against a CA certificate and optionally a certificate
revocation list. New HTTP header insertions allow passing client
certificate information to the backend members, while new L7 rules
allow you to take custom actions based on the content of the client
certificate.
* Backend re-encryption allows users to configure pools to initiate TLS
connections to the backend member servers. This enables load balancers
to authenticate and encrypt connections from the load balancer to the
backend member server.
* Object tags allow users to assign a list of strings to the load balancer
objects that can then be used for advanced API list filtering.

View File

@ -3,10 +3,10 @@ features:
- |
Added tags property for Octavia resources. It includes:
* Load balancer
* Listener
* Member
* Pool
* L7rule
* L7policy
* Health Monitor
* Load balancer
* Listener
* Member
* Pool
* L7rule
* L7policy
* Health Monitor

View File

@ -3,9 +3,9 @@ features:
- |
Listeners default timeouts can be set by config in section haproxy_amphora:
* `timeout_client_data`: Frontend client inactivity timeout
* `timeout_member_connect`: Backend member connection timeout
* `timeout_member_data`: Backend member inactivity timeout
* `timeout_tcp_inspect`: Time to wait for TCP packets for content inspection
* `timeout_client_data`: Frontend client inactivity timeout
* `timeout_member_connect`: Backend member connection timeout
* `timeout_member_data`: Backend member inactivity timeout
* `timeout_tcp_inspect`: Time to wait for TCP packets for content inspection
The value for all of these options is expected to be in milliseconds.
The value for all of these options is expected to be in milliseconds.