Mark neutron-lbaas as deprecated

This patch marks neutron-lbaas as deprecated in the neutron documentation.

It also removes some legacy LBaaS v1 documentation and neutron-lbaas bug
handling links.

Change-Id: I9824191ec671ba29fe545cc112fb2129405b3b60
This commit is contained in:
Michael Johnson 2018-01-31 16:00:30 -08:00
parent f5e7cff702
commit 1e075f01ee
9 changed files with 24 additions and 73 deletions

View File

@ -398,60 +398,6 @@ basic security group operations:
$ openstack port set --no-security-group PORT_ID $ openstack port set --no-security-group PORT_ID
Basic Load-Balancer-as-a-Service operations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. note::
The Load-Balancer-as-a-Service (LBaaS) API provisions and configures
load balancers. The reference implementation is based on the HAProxy
software load balancer.
This list shows example neutron commands that enable you to complete
basic LBaaS operations:
- Creates a load balancer pool by using specific provider.
``--provider`` is an optional argument. If not used, the pool is
created with default provider for LBaaS service. You should configure
the default provider in the ``[service_providers]`` section of the
``neutron.conf`` file. If no default provider is specified for LBaaS,
the ``--provider`` parameter is required for pool creation.
.. code-block:: console
$ neutron lb-pool-create --lb-method ROUND_ROBIN --name mypool \
--protocol HTTP --subnet-id SUBNET_UUID --provider PROVIDER_NAME
- Associates two web servers with pool.
.. code-block:: console
$ neutron lb-member-create --address WEBSERVER1_IP --protocol-port 80 mypool
$ neutron lb-member-create --address WEBSERVER2_IP --protocol-port 80 mypool
- Creates a health monitor that checks to make sure our instances are
still running on the specified protocol-port.
.. code-block:: console
$ neutron lb-healthmonitor-create --delay 3 --type HTTP --max-retries 3 \
--timeout 3
- Associates a health monitor with pool.
.. code-block:: console
$ neutron lb-healthmonitor-associate HEALTHMONITOR_UUID mypool
- Creates a virtual IP (VIP) address that, when accessed through the
load balancer, directs the requests to one of the pool members.
.. code-block:: console
$ neutron lb-vip-create --name myvip --protocol-port 80 --protocol \
HTTP --subnet-id SUBNET_UUID mypool
Plug-in specific extensions Plug-in specific extensions
~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~

View File

@ -351,6 +351,12 @@ The Neutron Metering agent resides beside neutron-l3-agent.
Configure Load-Balancer-as-a-Service (LBaaS v2) Configure Load-Balancer-as-a-Service (LBaaS v2)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. warning::
Neutron-lbaas is deprecated as of Queens. Load-Balancer-as-a-Service
(LBaaS v2) is now provided by the `Octavia project
<https://docs.openstack.org/octavia/latest/>`_. Please see the FAQ:
https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation
For the back end, use either ``Octavia`` or ``HAProxy``. For the back end, use either ``Octavia`` or ``HAProxy``.
This example uses Octavia. This example uses Octavia.

View File

@ -108,6 +108,12 @@ Set these options to configure SSL:
Load-Balancer-as-a-Service (LBaaS) overview Load-Balancer-as-a-Service (LBaaS) overview
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. warning::
Neutron-lbaas is deprecated as of Queens. Load-Balancer-as-a-Service
(LBaaS v2) is now provided by the `Octavia project
<https://docs.openstack.org/octavia/latest/>`_. Please see the FAQ:
https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation
Load-Balancer-as-a-Service (LBaaS) enables Networking to distribute Load-Balancer-as-a-Service (LBaaS) enables Networking to distribute
incoming requests evenly among designated instances. This distribution incoming requests evenly among designated instances. This distribution
ensures that the workload is shared predictably among instances and ensures that the workload is shared predictably among instances and

View File

@ -399,12 +399,6 @@ configuration. Either or both the ``peer_address`` and the
addressing modes and router modes described above should not impact addressing modes and router modes described above should not impact
support. support.
LBaaS
-----
TODO
FWaaS FWaaS
----- -----

View File

@ -4,6 +4,12 @@
Load Balancer as a Service (LBaaS) Load Balancer as a Service (LBaaS)
================================== ==================================
.. warning::
Neutron-lbaas is deprecated as of Queens. Load-Balancer-as-a-Service
(LBaaS v2) is now provided by the `Octavia project
<https://docs.openstack.org/octavia/latest/>`_. Please see the FAQ:
https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation
The Networking service offers a load balancer feature called "LBaaS v2" The Networking service offers a load balancer feature called "LBaaS v2"
through the ``neutron-lbaas`` service plug-in. through the ``neutron-lbaas`` service plug-in.

View File

@ -368,7 +368,8 @@ LBaaS
The Load-Balancer-as-a-Service (LBaaS) API provisions and configures The Load-Balancer-as-a-Service (LBaaS) API provisions and configures
load balancers. The reference implementation is based on the HAProxy load balancers. The reference implementation is based on the HAProxy
software load balancer. software load balancer. See the `Octavia project
<https://docs.openstack.org/octavia/latest/>`_ for more information.
FWaaS FWaaS
^^^^^ ^^^^^

View File

@ -28,7 +28,8 @@ Historically, Neutron supported the following advanced services:
#. **FWaaS** (*Firewall-as-a-Service*): runs as part of the L3 agent. #. **FWaaS** (*Firewall-as-a-Service*): runs as part of the L3 agent.
#. **LBaaS** (*Load-Balancer-as-a-Service*): implemented purely inside #. **LBaaS** (*Load-Balancer-as-a-Service*): implemented purely inside
neutron-server, does not interact directly with agents. neutron-server, does not interact directly with agents. **Deprecated as of
Queens**.
#. **VPNaaS** (*VPN-as-a-Service*): derives from L3 agent to add #. **VPNaaS** (*VPN-as-a-Service*): derives from L3 agent to add
VPNaaS functionality. VPNaaS functionality.

View File

@ -1,7 +1,7 @@
Neutron Bugs Neutron Bugs
============ ============
Neutron (client, core, FwaaS, LBaaS, VPNaaS) maintains all of its bugs in the following Neutron (client, core, FwaaS, VPNaaS) maintains all of its bugs in the following
Launchpad projects: Launchpad projects:
* `Launchpad Neutron <https://bugs.launchpad.net/neutron>`_ * `Launchpad Neutron <https://bugs.launchpad.net/neutron>`_
@ -604,14 +604,6 @@ L3 IPAM DHCP
* `L3 IPAM DHCP - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp>`_ * `L3 IPAM DHCP - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp>`_
* `L3 IPAM DHCP - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=l3-ipam-dhcp>`_ * `L3 IPAM DHCP - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=l3-ipam-dhcp>`_
.. _lbaas:
LBAAS
+++++
* `LBaaS - All bugs <https://bugs.launchpad.net/neutron/+bugs?field.tag=lbaas>`_
* `LBaaS - In progress <https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=INPROGRESS&field.tag=lbaas>`_
.. _lib: .. _lib:
Lib Lib

View File

@ -26,5 +26,4 @@ Here is a list of tagged documentation and API reference bugs:
IRC Information and Etiquette IRC Information and Etiquette
----------------------------- -----------------------------
The main IRC channel for Neutron is #openstack-neutron. We also utilize #openstack-lbaas The main IRC channel for Neutron is #openstack-neutron.
for LBaaS specific discussions. The weekly meeting is documented in the `list of meetings <https://wiki.openstack.org/wiki/Meetings#OpenStack_Networking_.28Neutron.29>`_ wiki page.