diff --git a/doc/common/glossary.rst b/doc/common/glossary.rst index b81ca08ea3..e5f7765057 100644 --- a/doc/common/glossary.rst +++ b/doc/common/glossary.rst @@ -973,14 +973,6 @@ D May or may not listen on a TCP or UDP port. Do not confuse with a worker. - DAC - - Discretionary access control. Governs the ability of subjects to - access objects, while enabling users to make policy decisions and - assign security attributes. The traditional UNIX system of users, - groups, and read-write-execute permissions is an example of - DAC. - Dashboard The web-based management interface for OpenStack. An alternative @@ -1111,15 +1103,6 @@ D Community project that uses shell scripts to quickly build complete OpenStack development environments. - DHCP - - Dynamic Host Configuration Protocol. A network protocol that - configures devices that are connected to a network so that they can - communicate on that network by using the Internet Protocol (IP). The - protocol is implemented in a client-server model where DHCP clients - request configuration data, such as an IP address, a default route, - and one or more DNS server addresses from a DHCP server. - DHCP agent OpenStack Networking agent that provides DHCP services @@ -1159,6 +1142,13 @@ D address and fixed IP and thus returning the floating IP address to the address pool. + Discretionary Access Control (DAC) + + Governs the ability of subjects to access objects, while enabling + users to make policy decisions and assign security attributes. + The traditional UNIX system of users, groups, and read-write-execute + permissions is an example of DAC. + disk encryption The ability to encrypt data at the file system, disk partition, @@ -1184,13 +1174,6 @@ D A web framework used extensively in horizon. - DNS - - Domain Name System. A hierarchical and distributed naming system - for computers, services, and resources connected to the Internet or a - private network. Associates human-friendly, domain names to IP - addresses. - DNS record A record that specifies information about a particular domain @@ -1242,10 +1225,6 @@ D The transfer of data, usually in the form of files, from one computer to another. - DRTM - - Dynamic root of trust measurement. - durable exchange The Compute RabbitMQ message exchange that remains active when @@ -1258,6 +1237,12 @@ D Dynamic Host Configuration Protocol (DHCP) + A network protocol that configures devices that are connected to a + network so that they can communicate on that network by using the + Internet Protocol (IP). The protocol is implemented in a client-server + model where DHCP clients request configuration data, such as an IP + address, a default route, and one or more DNS server addresses from a + DHCP server. A method to automatically configure networking for a host at boot time. Provided by both Networking and Compute. diff --git a/doc/install-guide/source/environment-networking.rst b/doc/install-guide/source/environment-networking.rst index 0c71c77aec..7e73934759 100644 --- a/doc/install-guide/source/environment-networking.rst +++ b/doc/install-guide/source/environment-networking.rst @@ -40,8 +40,9 @@ Host networking distribution, see the `SLES 12 `__ or `openSUSE `__ documentation. All nodes require Internet access for administrative purposes such as package -installation, security updates, :term:`DNS`, and :term:`NTP`. In most cases, -nodes should obtain internet access through the management network interface. +installation, security updates, :term:`DNS `, and +:term:`NTP`. In most cases, nodes should obtain internet access through the +management network interface. To highlight the importance of network separation, the example architectures use `private address space `__ for the management network and assume that the physical network infrastructure @@ -67,7 +68,8 @@ The example architectures assume use of the following networks: This network requires a gateway to provide Internet access to all nodes for administrative purposes such as package installation, - security updates, :term:`DNS`, and :term:`NTP`. + security updates, :term:`DNS `, and + :term:`NTP`. * Provider on 203.0.113.0/24 with gateway 203.0.113.1 diff --git a/doc/install-guide/source/overview.rst b/doc/install-guide/source/overview.rst index 1eb561fee5..bb6d6175db 100644 --- a/doc/install-guide/source/overview.rst +++ b/doc/install-guide/source/overview.rst @@ -200,8 +200,9 @@ The provider networks option deploys the OpenStack Networking service in the simplest way possible with primarily layer-2 (bridging/switching) services and VLAN segmentation of networks. Essentially, it bridges virtual networks to physical networks and relies on physical network infrastructure -for layer-3 (routing) services. Additionally, a :term:`DHCP` service provides -IP address information to instances. +for layer-3 (routing) services. Additionally, a :term:`DHCP` service provides IP address information to +instances. .. note:: diff --git a/doc/networking-guide/source/config-ml2.rst b/doc/networking-guide/source/config-ml2.rst index 2abaf328b7..fba51331f8 100644 --- a/doc/networking-guide/source/config-ml2.rst +++ b/doc/networking-guide/source/config-ml2.rst @@ -338,9 +338,9 @@ For a detailed list of configuration options, see the related section in the DHCP agent ^^^^^^^^^^ -The DHCP agent is responsible for :term:`DHCP` (Dynamic Host Configuration -Protocol) and RADVD (Router Advertisement Daemon) services. It requires a -running L2 agent on the same node. +The DHCP agent is responsible for :term:`DHCP ` and RADVD (Router Advertisement Daemon) services. +It requires a running L2 agent on the same node. Configuration for the DHCP agent is typically done in the ``dhcp_agent.ini`` configuration file. Make sure that on agent start diff --git a/doc/networking-guide/source/intro-basic-networking.rst b/doc/networking-guide/source/intro-basic-networking.rst index 249d709c79..fab780e2eb 100644 --- a/doc/networking-guide/source/intro-basic-networking.rst +++ b/doc/networking-guide/source/intro-basic-networking.rst @@ -234,8 +234,8 @@ command: DHCP ~~~~ -Hosts connected to a network use the Dynamic Host Configuration -Protocol (:term:`DHCP`) to dynamically obtain IP addresses. A DHCP +Hosts connected to a network use the :term:`Dynamic Host Configuration +Protocol (DHCP)` to dynamically obtain IP addresses. A DHCP server hands out the IP addresses to network hosts, which are the DHCP clients. diff --git a/doc/ops-guide/source/arch-example-nova-network.rst b/doc/ops-guide/source/arch-example-nova-network.rst index b11d7da7f6..864e8d70f6 100644 --- a/doc/ops-guide/source/arch-example-nova-network.rst +++ b/doc/ops-guide/source/arch-example-nova-network.rst @@ -184,12 +184,13 @@ Why use multi-host networking? In a default OpenStack deployment, there is a single ``nova-network`` service that runs within the cloud (usually on the cloud controller) that provides services such as -:term:`network address translation ` (NAT), :term:`DHCP`, -and :term:`DNS` to the guest instances. If the single node that runs the -``nova-network`` service goes down, you cannot access your instances, -and the instances cannot access the Internet. The single node that runs -the ``nova-network`` service can become a bottleneck if excessive -network traffic comes in and goes out of the cloud. +:term:`network address translation ` (NAT), :term:`DHCP `, and :term:`DNS ` +to the guest instances. If the single node that runs the ``nova-network`` +service goes down, you cannot access your instances, and the instances +cannot access the Internet. The single node that runs the ``nova-network`` +service can become a bottleneck if excessive network traffic comes in and +goes out of the cloud. .. tip:: diff --git a/doc/ops-guide/source/arch-network-design.rst b/doc/ops-guide/source/arch-network-design.rst index b5eb74b193..059e7a3eae 100644 --- a/doc/ops-guide/source/arch-network-design.rst +++ b/doc/ops-guide/source/arch-network-design.rst @@ -149,7 +149,8 @@ For OpenStack Networking with the neutron project, typical configurations are documented with the idea that any setup you can configure with real hardware you can re-create with a software-defined equivalent. Each tenant can contain typical network elements such as -routers, and services such as :term:`DHCP`. +routers, and services such as :term:`DHCP `. :ref:`table_networking_deployment` describes the networking deployment options for both legacy ``nova-network`` options and an equivalent