openstack/openstack-ansible
Code Issues Proposed changes

docs: replace "tenant" to "project"

Browse Source 
Change-Id: I6c0d36317ff76f45dfa8f4b380ffa6de2ad54e6a
Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
This commit is contained in:
Ivan Anfimov
2025-11-23 10:56:54 +00:00
parent b62ce91a0f
commit fda1d01b41
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/admin/openstack-operations/verify-deploy.rst
View File

@@ -15,7 +15,7 @@ the OpenStack API and dashboard, as an administrator.
$ lxc-attach -n `lxc-ls -1 | grep utility | head -n 1`
#. Source the ``admin`` tenant credentials:
#. Source the ``admin`` project credentials:
.. code::

4
doc/source/reference/architecture/container-networking.rst
View File

@@ -122,12 +122,12 @@ It will be used to populate ``network_mappings`` for Neutron.
The ``network_interface`` override is used for Open vSwitch and OVN-based deployments,
and requires a physical interface name which will be connected to the provider bridge
(ie. br-ex) for flat and vlan-based provider and tenant network traffic.
(ie. br-ex) for flat and vlan-based provider and project network traffic.
.. note::
Previous versions of OpenStack-Ansible utilized a bridge named ``br-vlan`` for
flat and vlan-based provider and tenant network traffic. The ``br-vlan`` bridge
flat and vlan-based provider and project network traffic. The ``br-vlan`` bridge
is a leftover of containerized Neutron agents and is no longer useful or
recommended.

2
doc/source/reference/architecture/metal-networking.rst
View File

@@ -102,7 +102,7 @@ It will be used to populate ``network_mappings`` for Neutron.
The ``network_interface`` override is used for Open vSwitch and OVN-based deployments,
and requires a physical interface name which will be connected to the provider bridge
(ie. br-ex) for flat and vlan-based provider and tenant network traffic.
(ie. br-ex) for flat and vlan-based provider and project network traffic.
The following diagrams reflect the differences in the virtual network layout for
supported network architectures.