Fix spec lint as surfaced by re-runs of tox -e py27
Change-Id: I0fdf69e4a2f611394174e07aea54d2fac9c2f420
This commit is contained in:
parent
a0cda74430
commit
8c1df93d54
@ -33,9 +33,9 @@ software should be set up is determined by a set of information sources.
|
||||
|
||||
- Cross-model relations
|
||||
|
||||
In its simplest form a charm’s sole goal is to as quickly as possible install a
|
||||
piece of software, write its configuration and fire it up enabling the end user
|
||||
to make use of the software.
|
||||
In its simplest form a charm’s sole goal is to as quickly as possible install
|
||||
a piece of software, write its configuration and fire it up enabling the end
|
||||
user to make use of the software.
|
||||
|
||||
Problem Description
|
||||
===================
|
||||
|
@ -16,6 +16,9 @@
|
||||
Octavia Charm
|
||||
=============
|
||||
|
||||
Problem Description
|
||||
===================
|
||||
|
||||
At present our support for LBaaS makes use of the ``neutron-lbaas``
|
||||
*service_plugin* and *service_provider* drivers. In the existing
|
||||
implementation the load balancer code, which is a part of the datapath, is run
|
||||
|
@ -55,6 +55,11 @@ After the 18.11 Charm release we evaluate and decide on further adoption.
|
||||
|
||||
0: https://docs.openstack.org/reno/latest/
|
||||
|
||||
Alternatives
|
||||
------------
|
||||
|
||||
None defined.
|
||||
|
||||
Implementation
|
||||
==============
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user