openstack/openstack-manuals
Code Issues Proposed changes

[install] Replace "tenant" with "project"

Browse Source 
backport: mitaka
Partial-Bug: #1475005
Change-Id: I4b485b6463cdaaf3811abef496e4de3cfb7ff684
This commit is contained in:
qiaomin 2016-08-18 00:59:55 +00:00 committed by Matthew Kassawara
parent 9eef23a4a0
commit a76f8ffee0
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/install-guide/source/keystone-services.rst
View File

@ -105,7 +105,7 @@ Create the service entity and API endpoints
OpenStack uses three API endpoint variants for each service: admin,
internal, and public. The admin API endpoint allows modifying users and
tenants by default, while the public and internal APIs do not allow these
projects by default, while the public and internal APIs do not allow these
operations. In a production environment, the variants might reside on
separate networks that service different types of users for security
reasons. For instance, the public API network might be visible from the

2
doc/install-guide/source/keystone-users.rst
View File

@ -3,7 +3,7 @@ Create a domain, projects, users, and roles
The Identity service provides authentication services for each OpenStack
service. The authentication service uses a combination of :term:`domains
<domain>`, :term:`projects<project>` (tenants), :term:`users<user>`, and
<domain>`, :term:`projects<project>`, :term:`users<user>`, and
:term:`roles<role>`.
#. Create the ``default`` domain:

2
doc/install-guide/source/launch-instance.rst
View File

@ -70,7 +70,7 @@ Most cloud images support :term:`public key authentication` rather than
conventional password authentication. Before launching an instance, you
must add a public key to the Compute service.
#. Source the ``demo`` tenant credentials:
#. Source the ``demo`` project credentials:
.. code-block:: console

2
doc/install-guide/source/neutron-concepts.rst
View File

@ -4,7 +4,7 @@ Networking (neutron) concepts
OpenStack Networking (neutron) manages all networking facets for the
Virtual Networking Infrastructure (VNI) and the access layer aspects
of the Physical Networking Infrastructure (PNI) in your OpenStack
environment. OpenStack Networking enables tenants to create advanced
environment. OpenStack Networking enables projects to create advanced
virtual network topologies which may include services such as a
:term:`firewall`, a :term:`load balancer`, and a
:term:`virtual private network (VPN)`.