O'Reilly Edits for the glossary
Edits done for the Operations Guide, will be copied over after review. This uses now "back-end" as adjective and "back end" as noun. Change-Id: I2b8384a80fdd17e88f214bdf0ac47d42264bf19f
This commit is contained in:
Andreas Jaeger
parent
af5f054a1b
commit
6917e73990
@ -1,4 +1,9 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE chapter [
|
||||
<!-- Some useful entities borrowed from HTML -->
|
||||
<!ENTITY mdash "—">
|
||||
]>
|
||||
|
||||
<glossary xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="rs_glossary"
|
||||
version="5.0" role="auto">
|
||||
@ -36,16 +41,23 @@
|
||||
<glossentry>
|
||||
<glossterm>access control list</glossterm>
|
||||
<glossdef>
|
||||
<para>A list of permissions attached to an object. An ACL specifies which users or system processes have access to objects. It also
|
||||
defines which operations can be performed on specified objects.
|
||||
Each entry in a typical ACL specifies a subject and an operation. For instance, ACL entry, <code>(Alice, delete)</code>, for a file gives Alice permission to delete the file.</para>
|
||||
<para>
|
||||
A list of permissions attached to an object. An ACL
|
||||
specifies which users or system processes have
|
||||
access to objects. It also defines which operations
|
||||
can be performed on specified objects. Each entry
|
||||
in a typical ACL specifies a subject and an
|
||||
operation. For instance, the ACL entry <code>(Alice,
|
||||
delete)</code> for a file gives Alice permission to
|
||||
delete the file.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>access key</glossterm>
|
||||
<glossdef>
|
||||
<para>Alternative term for an Amazon EC2 access key.
|
||||
See EC2 Access key.</para>
|
||||
See EC2 access key.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -126,7 +138,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>Active Directory</glossterm>
|
||||
<glossdef>
|
||||
<para>Authentication and Identity Service by
|
||||
<para>Authentication and identity service by
|
||||
Microsoft, based on LDAP. Supported in
|
||||
OpenStack.</para>
|
||||
</glossdef>
|
||||
@ -134,7 +146,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>active/passive configuration</glossterm>
|
||||
<glossdef>
|
||||
<para>In a high availability setup with an
|
||||
<para>In a high-availability setup with an
|
||||
active/passive configuration, systems are set up to
|
||||
bring additional resources online to replace those that
|
||||
have failed.
|
||||
@ -155,7 +167,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>A subset of API calls that are accessible to
|
||||
authorized administrators and are generally not
|
||||
accessible to end users or the public internet,
|
||||
accessible to end users or the public Internet. They
|
||||
can exist as a separate service (keystone) or can
|
||||
be a subset of another API (nova).</para>
|
||||
</glossdef>
|
||||
@ -197,7 +209,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>allocate</glossterm>
|
||||
<glossdef>
|
||||
<para>The process of taking floating IP address from
|
||||
<para>The process of taking a floating IP address from
|
||||
the address pool so it can be associated with a
|
||||
fixed IP on a guest VM instance.</para>
|
||||
</glossdef>
|
||||
@ -223,20 +235,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
Supported by Image Service.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>AMQP</glossterm>
|
||||
<glossdef>
|
||||
<para>Advanced Message Queue Protocol. An open
|
||||
Internet protocol for reliably sending and
|
||||
receiving messages. It enables building a diverse,
|
||||
coherent messaging ecosystem.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Anvil</glossterm>
|
||||
<glossdef>
|
||||
<para>A project that ports the shell script-based
|
||||
project named devstack to Python.</para>
|
||||
project named DevStack to Python.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -274,7 +277,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>The daemon, worker, or service that a client
|
||||
communicates with to access an API. API endpoints
|
||||
can provide any number of services such as
|
||||
can provide any number of services, such as
|
||||
authentication, sales data, performance
|
||||
metrics, Compute VM commands, census data, and so
|
||||
on.</para>
|
||||
@ -493,7 +496,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>auto declare</glossterm>
|
||||
<glossdef>
|
||||
<para>A Compute RabbitMQ setting that determines if a
|
||||
<para>A Compute RabbitMQ setting that determines whether a
|
||||
message exchange is automatically created when the
|
||||
program starts.</para>
|
||||
</glossdef>
|
||||
@ -517,11 +520,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdiv>
|
||||
<title>B</title>
|
||||
<glossentry>
|
||||
<glossterm>back-end</glossterm>
|
||||
<glossterm>back end</glossterm>
|
||||
<glossdef>
|
||||
<para>Interactions and processes that are obfuscated
|
||||
from the user, such as Compute volume mount, data
|
||||
transmission to an isCSI target by a daemon, or
|
||||
transmission to an iSCSI target by a daemon, or
|
||||
Object Storage object integrity checks.
|
||||
</para>
|
||||
</glossdef>
|
||||
@ -540,7 +543,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>back-end store</glossterm>
|
||||
<glossdef>
|
||||
<para>The persistent data store used to save and
|
||||
retrieve a information for a service, such as lists of
|
||||
retrieve information for a service, such as lists of
|
||||
Object Storage objects, current state of guest VMs, lists
|
||||
of user names, and so on. Also, the method that the
|
||||
Image Service uses to get and store VM images.
|
||||
@ -596,7 +599,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>bit-per-second (BPS)</glossterm>
|
||||
<glossterm>bits-per-second (BPS)</glossterm>
|
||||
<glossdef>
|
||||
<para>The universal measurement of how quickly data is
|
||||
transferred from place to place.</para>
|
||||
@ -669,7 +672,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>builder file</glossterm>
|
||||
<glossdef>
|
||||
<para>Contains configuration information that Object
|
||||
Storage uses to reconfigure a ring or recreate it from
|
||||
Storage uses to reconfigure a ring or to re-create it from
|
||||
scratch after a serious failure.
|
||||
</para>
|
||||
</glossdef>
|
||||
@ -726,7 +729,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<para>An OpenStack grouped release of projects that
|
||||
came out in the spring of 2011. It included
|
||||
Compute (nova), Object Storage (swift), and the
|
||||
Image service (glance).</para>
|
||||
Image Service (glance).</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -748,8 +751,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>capacity cache</glossterm>
|
||||
<glossdef>
|
||||
<para>A Compute back end database table that contains
|
||||
the current workload, amount of free RAM,
|
||||
<para>A Compute back-end database table that contains
|
||||
the current workload, amount of free RAM, and
|
||||
number of VMs running on each host. Used to
|
||||
determine on which VM a host starts.</para>
|
||||
</glossdef>
|
||||
@ -939,7 +942,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>cloud controller node</glossterm>
|
||||
<glossdef>
|
||||
<para>A node that runs network, volume, API, scheduler
|
||||
<para>A node that runs network, volume, API, scheduler,
|
||||
and image services. Each service may be broken out
|
||||
into separate nodes for scalability or
|
||||
availability.</para>
|
||||
@ -969,7 +972,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<para>A package commonly installed in VM images that
|
||||
performs initialization of an instance after boot
|
||||
using information that it retrieves from the
|
||||
metadata service such as the SSH public key and
|
||||
metadata service, such as the SSH public key and
|
||||
user data.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1103,7 +1106,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>In Compute, conductor is the process that proxies
|
||||
database requests from the compute process. Using
|
||||
conductor improves security as compute nodes do not
|
||||
conductor improves security because compute nodes do not
|
||||
need direct access to the database.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1216,12 +1219,13 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>credentials</glossterm>
|
||||
<glossdef>
|
||||
<para>Data that is only known to or accessible by a
|
||||
user that is used to verify the user is who they
|
||||
say they are and presented to the server during
|
||||
authentication. Examples include a password,
|
||||
secret key, digital certificate, fingerprint, and
|
||||
so on.</para>
|
||||
<para>
|
||||
Data that is only known to or accessible by a user
|
||||
and used to verify that the user is who they say
|
||||
they are. Credentials are presented to the server
|
||||
during authentication. Examples include a password,
|
||||
secret key, digital certificate, fingerprint, and so
|
||||
on.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -1334,7 +1338,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>The process of finding duplicate data at the
|
||||
disk block, file, and/or object level to minimize
|
||||
storage use, currently unsupported within
|
||||
storage use—currently unsupported within
|
||||
OpenStack.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1364,16 +1368,18 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>delayed delete</glossterm>
|
||||
<glossdef>
|
||||
<para>An option within Image Service so that rather than
|
||||
immediately delete an image, it is deleted after a
|
||||
pre-defined number of seconds.</para>
|
||||
<para>
|
||||
An option within Image Service so that an image is
|
||||
deleted after a predefined number of seconds instead
|
||||
of immediately.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>delivery mode</glossterm>
|
||||
<glossdef>
|
||||
<para>Setting for the Compute RabbitMQ message delivery
|
||||
mode, can be set to either transient or
|
||||
mode; can be set to either transient or
|
||||
persistent.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1422,15 +1428,16 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>DHCP</glossterm>
|
||||
<glossdef>
|
||||
<para>Dynamic Host Configuration Protocol. A network
|
||||
protocol that configures devices that are
|
||||
connected to a network so 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.</para>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -1440,7 +1447,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
OpenStack that came out in the fall of 2011, the
|
||||
fourth release of OpenStack. It included Compute
|
||||
(nova 2011.3), Object Storage (swift 1.4.3), and
|
||||
the Image service (glance).</para>
|
||||
the Image Service (glance).</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -1480,7 +1487,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>disk encryption</glossterm>
|
||||
<glossdef>
|
||||
<para>The ability to encrypt data at the file system,
|
||||
disk partition or whole disk level. Supported
|
||||
disk partition, or whole-disk level. Supported
|
||||
within Compute VMs.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1550,7 +1557,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>In Compute, the support that enables associating
|
||||
DNS entries with floating IP addresses, nodes, or
|
||||
cells so host names are consistent across
|
||||
cells so that hostnames are consistent across
|
||||
reboots.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1614,9 +1621,9 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>Dynamic HyperText Markup Language
|
||||
(DHTML)</glossterm>
|
||||
<glossdef>
|
||||
<para>Pages that use HTML,
|
||||
JavaScript, and CCS to enable users to interact
|
||||
with a web page or show simple animation.</para>
|
||||
<para>Pages that use HTML, JavaScript, and Cascading
|
||||
Style Sheets to enable users to interact with a web
|
||||
page or show simple animation.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
@ -1671,7 +1678,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>EC2 secret key</glossterm>
|
||||
<glossdef>
|
||||
<para>Used along with an EC2 access key when
|
||||
communicating with the Compute EC2 API, is used to
|
||||
communicating with the Compute EC2 API; used to
|
||||
digitally sign each request.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1706,8 +1713,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>endpoint template</glossterm>
|
||||
<glossdef>
|
||||
<para>A list of URL and port number endpoints that
|
||||
indicate where a service, such as object storage,
|
||||
compute, identity, and so on, can be
|
||||
indicate where a service, such as Object Storage,
|
||||
Compute, Identity, and so on, can be
|
||||
accessed.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -1716,7 +1723,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>Any piece of hardware or software that wants to
|
||||
connect to the network services provided by
|
||||
Networking, the Network Connectivity service. An
|
||||
Networking, the network connectivity service. An
|
||||
entity can make use of Networking by implementing a
|
||||
VIF.</para>
|
||||
</glossdef>
|
||||
@ -1829,9 +1836,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>exclusive queue</glossterm>
|
||||
<glossdef>
|
||||
<para>Connected to by a direct consumer in RabbitMQ /
|
||||
Compute, the message can only be consumed by the
|
||||
current connection.</para>
|
||||
<para>
|
||||
Connected to by a direct consumer in
|
||||
RabbitMQ—Compute, the message can be consumed
|
||||
only by the current connection.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -1847,10 +1856,12 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>extension</glossterm>
|
||||
<glossdef>
|
||||
<para>Alternative term for a Compute API extension or
|
||||
plug-in. In the context of Identity Service this is a call
|
||||
that is specific to the implementation, such as
|
||||
adding support for OpenID.</para>
|
||||
<para>
|
||||
Alternative term for an API extension or
|
||||
plug-in. In the context of Identity Service, this is
|
||||
a call that is specific to the implementation, such
|
||||
as adding support for OpenID.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -1925,7 +1936,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>Used to restrict communications between hosts
|
||||
and/or nodes, implemented in Compute using iptables,
|
||||
arptables, ip6tables and etables.</para>
|
||||
arptables, ip6tables, and etables.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -1941,9 +1952,9 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>fixed IP address</glossterm>
|
||||
<glossdef>
|
||||
<para>An IP address that is associated with the same
|
||||
instance each time that instance boots, generally
|
||||
instance each time that instance boots, is generally
|
||||
not accessible to end users or the public
|
||||
internet, used for management of the
|
||||
Internet, and used for management of the
|
||||
instance.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -2001,7 +2012,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>floating IP address</glossterm>
|
||||
<glossdef>
|
||||
<para>An IP address that a project can associate
|
||||
with a VM so the instance has the same public IP
|
||||
with a VM so that the instance has the same public IP
|
||||
address each time that it boots. You create a pool
|
||||
of floating IP addresses and assign them to
|
||||
instances as they are launched to maintain a
|
||||
@ -2016,8 +2027,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
OpenStack that came out in the fall of 2012, the
|
||||
sixth release of OpenStack. It includes Compute
|
||||
(nova), Object Storage (swift), Identity
|
||||
(keystone), Networking (neutron), Image service
|
||||
(glance) and Volumes or Block Storage
|
||||
(keystone), Networking (neutron), Image Service
|
||||
(glance), and Volumes or Block Storage
|
||||
(cinder).</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -2030,9 +2041,9 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>front-end</glossterm>
|
||||
<glossterm>frontend</glossterm>
|
||||
<glossdef>
|
||||
<para>The point where a user interacts with a service,
|
||||
<para>The point where a user interacts with a service;
|
||||
can be an API endpoint, the horizon dashboard, or
|
||||
a command-line tool.</para>
|
||||
</glossdef>
|
||||
@ -2110,8 +2121,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>Green Threads</glossterm>
|
||||
<glossdef>
|
||||
<para>The cooperative threading model used by Python,
|
||||
reduces race conditions, and only context switches
|
||||
<para>The cooperative threading model used by Python;
|
||||
reduces race conditions and only context switches
|
||||
when specific library calls are made. Each
|
||||
OpenStack service is its own thread.</para>
|
||||
</glossdef>
|
||||
@ -2253,7 +2264,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>HyperText Transfer Protocol (HTTP)</glossterm>
|
||||
<glossterm>Hypertext Transfer Protocol (HTTP)</glossterm>
|
||||
<glossdef>
|
||||
<para>The protocol that tells browsers where to go to
|
||||
find information.</para>
|
||||
@ -2263,7 +2274,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>Hypertext Transfer Protocol Secure
|
||||
(HTTPS)</glossterm>
|
||||
<glossdef>
|
||||
<para>Encrypted HTTP communications using SSL or TLS,
|
||||
<para>Encrypted HTTP communications using SSL or TLS;
|
||||
most OpenStack API endpoints and many
|
||||
inter-component communications support HTTPS
|
||||
communication.</para>
|
||||
@ -2324,10 +2335,10 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Identity back-end</glossterm>
|
||||
<glossterm>Identity back end</glossterm>
|
||||
<glossdef>
|
||||
<para>The source used by Identity Service to retrieve user
|
||||
information an OpenLDAP server for example.</para>
|
||||
information; an OpenLDAP server for example.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -2386,7 +2397,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>image ID</glossterm>
|
||||
<glossdef>
|
||||
<para>Combination of URI and UUID used to access
|
||||
<para>Combination of a URI and UUID used to access
|
||||
Image Service VM images through the image API.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -2477,7 +2488,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>instance</glossterm>
|
||||
<glossdef>
|
||||
<para>A running VM, or a VM in a known state such as
|
||||
suspended that can be used like a hardware server.
|
||||
suspended, that can be used like a hardware server.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -2592,7 +2603,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
as different Netfilter modules) and the chains and
|
||||
rules it stores. Different kernel modules and
|
||||
programs are currently used for different
|
||||
protocols; iptables applies to IPv4, ip6tables to
|
||||
protocols: iptables applies to IPv4, ip6tables to
|
||||
IPv6, arptables to ARP, and ebtables to Ethernet
|
||||
frames. Requires root privilege to
|
||||
manipulate.</para>
|
||||
@ -2750,7 +2761,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>load balancer</glossterm>
|
||||
<glossdef>
|
||||
<para>A load balancer is a logical device which
|
||||
<para>A load balancer is a logical device that
|
||||
belongs to a cloud account. It is used to
|
||||
distribute workloads between multiple back-end
|
||||
systems or services, based on the criteria defined
|
||||
@ -2786,7 +2797,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>management network</glossterm>
|
||||
<glossdef>
|
||||
<para>A network segment used for administration, not
|
||||
accessible to the public internet.</para>
|
||||
accessible to the public Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -2905,7 +2916,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>Modular Layer 2 (ML2) neutron plug-in</glossterm>
|
||||
<glossdef>
|
||||
<para>Can concurrently use multiple
|
||||
layer 2 networking technologies, such as 802.1Q and
|
||||
layer-2 networking technologies, such as 802.1Q and
|
||||
VXLAN, in Networking.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -2990,10 +3001,12 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>network controller</glossterm>
|
||||
<glossdef>
|
||||
<para>A Compute daemon that orchestrates the network
|
||||
configuration of nodes including includes IP
|
||||
addresses, VLANs, bridging, and manages routing
|
||||
for both public and private networks.</para>
|
||||
<para>
|
||||
A Compute daemon that orchestrates the network
|
||||
configuration of nodes, including IP addresses,
|
||||
VLANs, and bridging. Also manages routing for both
|
||||
public and private networks.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -3028,7 +3041,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>network segment</glossterm>
|
||||
<glossdef>
|
||||
<para>Represents a virtual, isolated OSI layer 2
|
||||
<para>Represents a virtual, isolated OSI layer-2
|
||||
subnet in Networking.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3176,7 +3189,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>object</glossterm>
|
||||
<glossdef>
|
||||
<para>A BLOB of data held by Object Storage, can be in any
|
||||
<para>A BLOB of data held by Object Storage; can be in any
|
||||
format.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3251,9 +3264,10 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>object versioning</glossterm>
|
||||
<glossdef>
|
||||
<para>Allows a user to set a flag on an Object Storage container
|
||||
so all objects within the container are
|
||||
versioned.</para>
|
||||
<para>
|
||||
Allows a user to set a flag on an Object Storage
|
||||
container so that all objects within the container
|
||||
are versioned.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -3300,10 +3314,10 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<para>
|
||||
OpenStack is a cloud operating system that controls
|
||||
large pools of compute, storage, and networking
|
||||
resources throughout a datacenter, all managed through
|
||||
resources throughout a data center, all managed through
|
||||
a dashboard that gives administrators control while
|
||||
empowering their users to provision resources through
|
||||
a web interface. OpenStack is an Open Source project licensed
|
||||
a web interface. OpenStack is an open source project licensed
|
||||
under the Apache License 2.0.
|
||||
</para>
|
||||
</glossdef>
|
||||
@ -3334,9 +3348,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>orphan</glossterm>
|
||||
<glossdef>
|
||||
<para>In the context of Object Storage this is a process that
|
||||
is not terminated after an upgrade, restart, or
|
||||
reload of the service.</para>
|
||||
<para>
|
||||
In the context of Object Storage, this is a process
|
||||
that is not terminated after an upgrade, restart, or
|
||||
reload of the service.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
@ -3355,9 +3371,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>partition</glossterm>
|
||||
<glossdef>
|
||||
<para>A unit of storage within Object Storage used to store
|
||||
objects, exists on top of devices, replicated for
|
||||
fault tolerance.</para>
|
||||
<para>
|
||||
A unit of storage within Object Storage used to
|
||||
store objects. It exists on top of devices and is,
|
||||
replicated for fault tolerance.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -3378,7 +3396,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>pause</glossterm>
|
||||
<glossdef>
|
||||
<para>A VM state where no changes occur (no changes in
|
||||
memory, network communications stop, etc), the VM
|
||||
memory, network communications stop, etc); the VM
|
||||
is frozen but not shut down.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3394,7 +3412,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>persistent message</glossterm>
|
||||
<glossdef>
|
||||
<para>A message that is stored both in memory and on
|
||||
disk, the message is not lost after a failure or
|
||||
disk. The message is not lost after a failure or
|
||||
restart.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3408,9 +3426,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>personality file</glossterm>
|
||||
<glossdef>
|
||||
<para>A file used to customize a Compute instance, can be
|
||||
used to inject SSH keys or a specific network
|
||||
configuration.</para>
|
||||
<para>
|
||||
A file used to customize a Compute instance. It can
|
||||
be used to inject SSH keys or a specific network
|
||||
configuration.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -3437,15 +3457,17 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>policy service</glossterm>
|
||||
<glossdef>
|
||||
<para>Component of Identity Service that provides a rule
|
||||
management interface and a rule based
|
||||
authorization engine.</para>
|
||||
<para>
|
||||
Component of Identity Service that provides a
|
||||
rule-management interface and a rule-based
|
||||
authorization engine.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>port</glossterm>
|
||||
<glossdef>
|
||||
<para>A virtual network port within Networking, VIFs /
|
||||
<para>A virtual network port within Networking; VIFs /
|
||||
vNICs are connected to a port.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3475,7 +3497,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>An IP address used for management and
|
||||
administration, not available to the public
|
||||
internet.</para>
|
||||
Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -3503,7 +3525,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>project ID</glossterm>
|
||||
<glossdef>
|
||||
<para>User defined alpha-numeric string in Compute, the
|
||||
<para>User-defined alpha-numeric string in Compute; the
|
||||
name of a project.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3531,7 +3553,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>proxy server</glossterm>
|
||||
<glossdef>
|
||||
<para>Users of Object Storage interact with the service through
|
||||
the proxy server which in-turn looks up the
|
||||
the proxy server, which in-turn looks up the
|
||||
location of the requested data within the ring and
|
||||
returns the results to the user.</para>
|
||||
</glossdef>
|
||||
@ -3539,8 +3561,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>public API</glossterm>
|
||||
<glossdef>
|
||||
<para>An API endpoint used for both service to service
|
||||
communication and end user interactions.</para>
|
||||
<para>An API endpoint used for both service-to-service
|
||||
communication and end-user interactions.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -3571,7 +3593,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>Puppet</glossterm>
|
||||
<glossdef>
|
||||
<para>An operating system configuration management
|
||||
<para>An operating system configuration-management
|
||||
tool supported by OpenStack.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3596,7 +3618,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>Qpid</glossterm>
|
||||
<glossdef>
|
||||
<para>Message queue software supported by OpenStack,
|
||||
<para>Message queue software supported by OpenStack;
|
||||
an alternative to RabbitMQ.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3604,7 +3626,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>quarantine</glossterm>
|
||||
<glossdef>
|
||||
<para>If Object Storage finds objects, containers, or accounts
|
||||
that are corrupt they are placed in this state,
|
||||
that are corrupt, they are placed in this state,
|
||||
are not replicated, cannot be read by clients, and
|
||||
a correct copy is re-replicated.</para>
|
||||
</glossdef>
|
||||
@ -3689,14 +3711,14 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>raw</glossterm>
|
||||
<glossdef>
|
||||
<para>One of the VM image disk formats supported by
|
||||
Image Service, an unstructured disk image.</para>
|
||||
Image Service; an unstructured disk image.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>rebalance</glossterm>
|
||||
<glossdef>
|
||||
<para>The process of distributing Object Storage partitions
|
||||
across all drives in the ring, used during initial
|
||||
across all drives in the ring; used during initial
|
||||
ring creation and after ring
|
||||
reconfiguration.</para>
|
||||
</glossdef>
|
||||
@ -3711,7 +3733,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
power cycling the server. The virtualization
|
||||
platform should ensure that the reboot action has
|
||||
completed successfully even in cases in which the
|
||||
underlying domain/vm is paused or halted/stopped.
|
||||
underlying domain/VM is paused or halted/stopped.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3768,7 +3790,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>region</glossterm>
|
||||
<glossdef>
|
||||
<para>A Discrete OpenStack environment with dedicated API
|
||||
<para>A discrete OpenStack environment with dedicated API
|
||||
endpoints that typically shares only the Identity
|
||||
Service (keystone) with other regions.</para>
|
||||
</glossdef>
|
||||
@ -3808,7 +3830,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>Provides data redundancy and fault tolerance by
|
||||
creating copies of Object Storage objects, accounts, and
|
||||
containers so they are not lost when the
|
||||
containers so that they are not lost when the
|
||||
underlying storage fails.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3890,7 +3912,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>Role Based Access Control (RBAC)</glossterm>
|
||||
<glossdef>
|
||||
<para>Provides a predefined list of actions that the
|
||||
user can perform such as start or stop VMs, reset
|
||||
user can perform, such as start or stop VMs, reset
|
||||
passwords, and so on. Supported in both Identity Service
|
||||
and Compute and can be configured using the horizon
|
||||
dashboard.</para>
|
||||
@ -3932,8 +3954,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>routing key</glossterm>
|
||||
<glossdef>
|
||||
<para>The Compute direct exchanges, fanout exchanges, and
|
||||
topic exchanges use this to determine how to
|
||||
process a message, processing varies depending on
|
||||
topic exchanges use this key to determine how to
|
||||
process a message; processing varies depending on
|
||||
exchange type.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -3980,17 +4002,21 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>S3</glossterm>
|
||||
<glossdef>
|
||||
<para>Object storage service by Amazon, similar in
|
||||
function to Object Storage, can act as a back-end store for
|
||||
Image Service VM images.</para>
|
||||
<para>
|
||||
Object storage service by Amazon; similar in
|
||||
function to Object Storage, it can act as a back-end
|
||||
store for Image Service VM images.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>sahara</glossterm>
|
||||
<glossdef>
|
||||
<para>OpenStack project that provides a scalable data
|
||||
processing stack and associated management interfaces.
|
||||
</para>
|
||||
<para>
|
||||
OpenStack project that provides a scalable
|
||||
data-processing stack and associated management
|
||||
interfaces.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -4011,14 +4037,14 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>scrubber</glossterm>
|
||||
<glossdef>
|
||||
<para>Checks for and deletes unused VM, the component
|
||||
<para>Checks for and deletes unused VMs; the component
|
||||
of Image Service that implements delayed delete.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>secret key</glossterm>
|
||||
<glossdef>
|
||||
<para>String of text only known by the user, used
|
||||
<para>String of text known only by the user; used
|
||||
along with an access key to make requests to the
|
||||
Compute API.</para>
|
||||
</glossdef>
|
||||
@ -4042,7 +4068,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>segmented object</glossterm>
|
||||
<glossdef>
|
||||
<para>An Object Storage large object that has been broken up
|
||||
into pieces, the re-assembled object is called a
|
||||
into pieces. The re-assembled object is called a
|
||||
concatenated object.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4052,7 +4078,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<para>Computer that provides explicit services to the
|
||||
client software running on that system, often
|
||||
managing a variety of computer operations.</para>
|
||||
<para>A server is a VM instance in the compute system.
|
||||
<para>A server is a VM instance in the Compute system.
|
||||
Flavor and image are requisite elements when
|
||||
creating a server.</para>
|
||||
</glossdef>
|
||||
@ -4129,7 +4155,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>session persistence</glossterm>
|
||||
<glossdef>
|
||||
<para>A feature of the load balancing service. It
|
||||
<para>A feature of the load-balancing service. It
|
||||
attempts to force subsequent connections to a
|
||||
service to be redirected to the same node as long
|
||||
as it is online.</para>
|
||||
@ -4169,15 +4195,15 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
can share one or more public IPs with any other
|
||||
server in the group. With the exception of the
|
||||
first server in a shared IP group, servers must be
|
||||
launched into shared IP groups. A server may only
|
||||
be a member of one shared IP group.</para>
|
||||
launched into shared IP groups. A server may
|
||||
be a member of only one shared IP group.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>shared storage</glossterm>
|
||||
<glossdef>
|
||||
<para>Block storage that is simultaneously accessible
|
||||
by multiple clients. For example, NFS.</para>
|
||||
by multiple clients, for example, NFS.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -4212,7 +4238,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>SmokeStack</glossterm>
|
||||
<glossdef>
|
||||
<para>Runs automated tests against the core OpenStack
|
||||
API, written in Rails.</para>
|
||||
API; written in Rails.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -4255,7 +4281,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>spread-first scheduler</glossterm>
|
||||
<glossdef>
|
||||
<para>The Compute VM scheduling algorithm that attempts
|
||||
to start new VM on the host with the least amount
|
||||
to start a new VM on the host with the least amount
|
||||
of load.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4295,17 +4321,17 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>storage back-end</glossterm>
|
||||
<glossterm>storage back end</glossterm>
|
||||
<glossdef>
|
||||
<para>The method that a service uses for persistent
|
||||
storage such as iSCSI, NFS, or local disk.</para>
|
||||
storage, such as iSCSI, NFS, or local disk.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>storage node</glossterm>
|
||||
<glossdef>
|
||||
<para>An Object Storage node that provides container services,
|
||||
account services, and object services, controls
|
||||
account services, and object services; controls
|
||||
the account databases, container databases, and
|
||||
object storage.</para>
|
||||
</glossdef>
|
||||
@ -4315,13 +4341,13 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>A XenAPI component that provides a pluggable
|
||||
interface to support a wide variety of persistent
|
||||
storage back-ends.</para>
|
||||
storage back ends.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>storage manager back-end</glossterm>
|
||||
<glossterm>storage manager back end</glossterm>
|
||||
<glossdef>
|
||||
<para>A persistent storage method supported by XenAPI
|
||||
<para>A persistent storage method supported by XenAPI,
|
||||
such as iSCSI or NFS.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4376,7 +4402,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>swawth</glossterm>
|
||||
<glossdef>
|
||||
<para>An authentication and authorization service for
|
||||
Object Storage, implemented through WSGI middleware, uses
|
||||
Object Storage, implemented through WSGI middleware; uses
|
||||
Object Storage itself as the persistent backing
|
||||
store.</para>
|
||||
</glossdef>
|
||||
@ -4503,7 +4529,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>tenant ID</glossterm>
|
||||
<glossdef>
|
||||
<para>Unique ID assigned to each tenant within
|
||||
the Identity Service, the project IDs map to the
|
||||
the Identity Service. The project IDs map to the
|
||||
tenant IDs.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4526,7 +4552,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>tombstone</glossterm>
|
||||
<glossdef>
|
||||
<para>Used to mark Object Storage objects that have been
|
||||
deleted, ensures the object is not updated on
|
||||
deleted; ensures that the object is not updated on
|
||||
another node after it has been deleted.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4534,7 +4560,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossterm>topic publisher</glossterm>
|
||||
<glossdef>
|
||||
<para>A process that is created when a RPC call is
|
||||
executed, used to push the message to the topic
|
||||
executed; used to push the message to the topic
|
||||
exchange.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4548,7 +4574,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>transaction ID</glossterm>
|
||||
<glossdef>
|
||||
<para>Unique ID assigned to each Object Storage request, used
|
||||
<para>Unique ID assigned to each Object Storage request; used
|
||||
for debugging and tracing.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4613,8 +4639,8 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>user</glossterm>
|
||||
<glossdef>
|
||||
<para>In Identity Service each user is associated with one or
|
||||
more tenants, and in Compute they can be associated
|
||||
<para>In Identity Service, each user is associated with one or
|
||||
more tenants, and in Compute can be associated
|
||||
with roles, projects, or both.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@ -4731,9 +4757,11 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>virtual switch (vSwitch)</glossterm>
|
||||
<glossdef>
|
||||
<para>Software that runs on a host or node and
|
||||
provides the features and functions of a hardware
|
||||
based network switch.</para>
|
||||
<para>
|
||||
Software that runs on a host or node and provides
|
||||
the features and functions of a hardware-based
|
||||
network switch.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
@ -4751,7 +4779,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossentry>
|
||||
<glossterm>VLAN manager</glossterm>
|
||||
<glossdef>
|
||||
<para>A Compute component that provides dnsmasq, radvd,
|
||||
<para>A Compute component that provides dnsmasq and radvd
|
||||
and sets up forwarding to and from cloudpipe
|
||||
instances.</para>
|
||||
</glossdef>
|
||||
@ -4814,7 +4842,7 @@ Each entry in a typical ACL specifies a subject and an operation. For instance,
|
||||
<glossdef>
|
||||
<para>Disk-based data storage generally represented as
|
||||
an iSCSI target with a file system that supports
|
||||
extended attributes, can be persistent or
|
||||
extended attributes; can be persistent or
|
||||
ephemeral.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user