Adds glossary file
* Adds a common/glossary.xml file * Not yet published anywhere, but want to add to the Compute Admin manual for starters. * Commented out some definitions, removed Rackspace-specific content. Change-Id: Iaadfd9cb56123805972d1e28aa41dbab354428d8
This commit is contained in:
annegentle
parent
2db72768e3
commit
82ad24079e
@ -0,0 +1,177 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<section xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||||
xml:id="Compute_API_Quick_Start" version="5.0">
|
||||
<title>OpenStack API Quick Start</title>
|
||||
<para>The OpenStack system has several key projects that are
|
||||
separate installations but can work together depending on your
|
||||
cloud needs: OpenStack Compute, OpenStack Object Storage,
|
||||
OpenStack Identity Service, and OpenStack Image Store. With
|
||||
the TryStack OpenStack installation, the OpenStack Compute,
|
||||
OpenStack Identity, and OpenStack Image Store projects are all
|
||||
working together in the background of the installation. </para>
|
||||
<section xml:id="Openstack-API-Concepts-a09234">
|
||||
|
||||
<title>OpenStack API Introduction</title>
|
||||
<para>This page covers the basics for talking to your
|
||||
OpenStack cloud through the Compute API after authorizing
|
||||
with the Identity Service API. You can then build a cloud
|
||||
by launching images and assigning metadata to instances,
|
||||
all through the API. For an API reference of all the
|
||||
possible commands, see the <link
|
||||
xlink:href="http://docs.openstack.org/api/openstack-compute/1.1/content/"
|
||||
>OpenStack Compute API 1.1 specification</link> and
|
||||
the <link
|
||||
xlink:href="http://docs.openstack.org/api/openstack-identity-service/2.0/content/"
|
||||
>Identity Service 2.0 specification</link> published
|
||||
at <link xlink:href="http://docs.openstack.org/api"
|
||||
>docs.openstack.org/api</link>. </para>
|
||||
</section>
|
||||
<section xml:id="Getting-Credentials-a00665">
|
||||
<title>Getting Credentials</title>
|
||||
<para>Credentials are a combination of your username,
|
||||
password, and what tenant (or project) your cloud is
|
||||
running under. You only need to generate an additional
|
||||
token if you are interacting with your cloud directly with
|
||||
API endpoints, and not with a client. Your cloud
|
||||
administrator can give you a username and a password as
|
||||
well as your tenant identifier so you can generate
|
||||
authorization tokens. You can also get the tenant ID from
|
||||
the Dashboard URLs, for example
|
||||
https://trystack.org/dash/296/images/ indicates a tenant
|
||||
ID of 296. </para>
|
||||
<para>These tokens are typically good for 24 hours, and when
|
||||
the token expires, you will find out with a 401
|
||||
(Unauthorized) error and can request another token
|
||||
programmatically. The general workflow goes something like
|
||||
this: </para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Begin API requests by asking for an
|
||||
authorization token from the endpoint your cloud
|
||||
administrator gave you, typically
|
||||
http://hostname:port/v2.0/tokens. You send your
|
||||
username, password, and what group or account you
|
||||
are with (the "tenant" in auth-speak). </para>
|
||||
<para><programlisting>curl -k -X 'POST' -v https://nova-api.trystack.org:5443/v2.0/tokens -d '{"auth":{"passwordCredentials":{"username": "joecool", "password":"coolword"}, "tenantId":"5"}}' -H 'Content-type: application/json'</programlisting></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>The server returns a response in which the
|
||||
24-hours token is contained. Use that token to
|
||||
send API requests with the X-Auth-Token included
|
||||
as an header field.</para>
|
||||
<para><programlisting>curl -k -D - -H "X-Auth-Token: 7d2f63fd-4dcc-4752-8e9b-1d08f989cc00" -X 'GET' -v https://nova-api.trystack.org:9774/v1.1/296/extensions -H 'Content-type: application/json' </programlisting></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Repeatedly send API requests with that token in
|
||||
the x-auth-token header until either: 1) the job's
|
||||
done or 2) you get a 401 (Unauthorized) code in
|
||||
return. </para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Request a token again when you get a 401
|
||||
response until the script's job is done.</para>
|
||||
</listitem>
|
||||
|
||||
</orderedlist>
|
||||
<para>For a typical OpenStack deployment running the Identity
|
||||
Service you can request a token with this command in
|
||||
cURL:<programlisting>
|
||||
$ curl -X 'POST' -v https://nova-api.trystack.org:5443/v2.0/tokens -d '{"auth":{"passwordCredentials":{"username": "joecool", "password":"coolword"}, "tenantId":"5"}}' -H 'Content-type: application/json'
|
||||
</programlisting></para>
|
||||
<para>In return, you should get a 200 OK response with a token
|
||||
in the form of "id":
|
||||
"cd427a33-bb4a-4079-a6d7-0ae148bdeda9" and an expiration
|
||||
date 24 hours from now. Here's what it looks like:</para>
|
||||
<para>
|
||||
<programlisting>
|
||||
{
|
||||
"access": {
|
||||
"serviceCatalog": [
|
||||
{
|
||||
"endpoints": [
|
||||
{
|
||||
"adminURL": "https://nova-api.trystack.org:9774/v1.1/1",
|
||||
"internalURL": "https://nova-api.trystack.org:9774/v1.1/1",
|
||||
"publicURL": "https://nova-api.trystack.org:9774/v1.1/1",
|
||||
"region": "RegionOne"
|
||||
}
|
||||
],
|
||||
"name": "nova",
|
||||
"type": "compute"
|
||||
},
|
||||
{
|
||||
"endpoints": [
|
||||
{
|
||||
"adminURL": "https://GLANCE_API_IS_NOT_DISCLOSED/v1.1/1",
|
||||
"internalURL": "https://GLANCE_API_IS_NOT_DISCLOSED/v1.1/1",
|
||||
"publicURL": "https://GLANCE_API_IS_NOT_DISCLOSED/v1.1/1",
|
||||
"region": "RegionOne"
|
||||
}
|
||||
],
|
||||
"name": "glance",
|
||||
"type": "image"
|
||||
},
|
||||
{
|
||||
"endpoints": [
|
||||
{
|
||||
"adminURL": "https://nova-api.trystack.org:5443/v2.0",
|
||||
"internalURL": "https://keystone.trystack.org:5000/v2.0",
|
||||
"publicURL": "https://keystone.trystack.org:5000/v2.0",
|
||||
"region": "RegionOne"
|
||||
}
|
||||
],
|
||||
"name": "keystone",
|
||||
"type": "identity"
|
||||
}
|
||||
],
|
||||
"token": {
|
||||
"expires": "2012-02-15T19:32:21",
|
||||
"id": "5df9d45d-d198-4222-9b4c-7a280aa35666",
|
||||
"tenant": {
|
||||
"id": "1",
|
||||
"name": "admin"
|
||||
}
|
||||
},
|
||||
"user": {
|
||||
"id": "14",
|
||||
"name": "annegentle",
|
||||
"roles": [
|
||||
{
|
||||
"id": "2",
|
||||
"name": "Member",
|
||||
"tenantId": "1"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
</programlisting></para>
|
||||
</section>
|
||||
<section xml:id="Sending-Requests-to-API-a09879">
|
||||
<title>Sending Requests to the API</title>
|
||||
<para>You have a couple of options for sending requests to
|
||||
OpenStack through an API. Developers and testers may
|
||||
prefer to use cURL, the command-line tool from <link
|
||||
xlink:href="http://curl.haxx.se/"
|
||||
>http://curl.haxx.se/</link>. With cURL you can send
|
||||
HTTP requests and receive responses back from the command
|
||||
line. </para>
|
||||
<para>If you like to use a more graphical interface, the REST
|
||||
client for Firefox also works well for testing and trying
|
||||
out commands, see <link
|
||||
xlink:href="https://addons.mozilla.org/en-US/firefox/addon/restclient/"
|
||||
>https://addons.mozilla.org/en-US/firefox/addon/restclient/</link>.
|
||||
You can also download and install rest-client, a Java
|
||||
application to test RESTful web services, from <link
|
||||
xlink:href="http://code.google.com/p/rest-client/"
|
||||
>http://code.google.com/p/rest-client/</link>. </para>
|
||||
<para>You need to generate a token as shown above if you use
|
||||
cURL or a REST client. </para>
|
||||
</section>
|
||||
|
||||
|
||||
</section>
|
||||
913
doc/src/docbkx/common/glossary.xml
Normal file
913
doc/src/docbkx/common/glossary.xml
Normal file
@ -0,0 +1,913 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<glossary xmlns="http://docbook.org/ns/docbook"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="rs_glossary"
|
||||
version="5.0" role="auto">
|
||||
<title>Glossary</title>
|
||||
<info>
|
||||
<legalnotice>
|
||||
<para> Licensed under the Apache License, Version 2.0 (the
|
||||
"License"); you may not use this file except in
|
||||
compliance with the License. You may obtain a copy of
|
||||
the License at </para>
|
||||
<para>
|
||||
<link
|
||||
xlink:href="http://www.apache.org/licenses/LICENSE-2.0"
|
||||
>http://www.apache.org/licenses/LICENSE-2.0</link>
|
||||
</para>
|
||||
<para> Unless required by applicable law or agreed to in
|
||||
writing, software distributed under the License is
|
||||
distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
|
||||
CONDITIONS OF ANY KIND, either express or implied. See
|
||||
the License for the specific language governing
|
||||
permissions and limitations under the License. </para>
|
||||
</legalnotice>
|
||||
</info>
|
||||
<glossdiv>
|
||||
<title>A</title>
|
||||
<glossentry>
|
||||
<glossterm>API</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for Application Programming Interface. An
|
||||
API allows independent programmers to develop
|
||||
newly created application services, using an open
|
||||
application.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Apache</glossterm>
|
||||
<glossdef>
|
||||
<para>The most common web server software presently
|
||||
being used on the Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Applet</glossterm>
|
||||
<glossdef>
|
||||
<para>A Java program that can be embedded into a web
|
||||
page.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Application Server</glossterm>
|
||||
<glossdef>
|
||||
<para>A piece of software that makes available another
|
||||
piece of software over a network.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>ASPs</glossterm>
|
||||
<glossdef>
|
||||
<para>An abbreviation for Application Service
|
||||
Providers. These are companies that rent
|
||||
specialized applications that help businesses and
|
||||
organizations provide additional services with
|
||||
less cost.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>attachment (network)</glossterm>
|
||||
<glossdef><para>Association of an interface identifier to a logical
|
||||
port, which represent 'plugging' an interface into
|
||||
a port.</para></glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>B</title>
|
||||
<!--<glossentry>
|
||||
<glossterm>Backup Schedule</glossterm>
|
||||
<glossdef>
|
||||
<para> A backup schedule can be defined to create
|
||||
server images at regular intervals (daily and
|
||||
weekly). Backup schedules are configurable per
|
||||
server. </para>
|
||||
</glossdef>
|
||||
</glossentry>-->
|
||||
<glossentry>
|
||||
<glossterm>Bandwidth</glossterm>
|
||||
<glossdef>
|
||||
<para>The amount of available data used by
|
||||
communication resources such as the Internet. It
|
||||
refers the amount of data that is used to download
|
||||
things or the amount of data available to
|
||||
download.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Binary</glossterm>
|
||||
<glossdef>
|
||||
<para>Information that consists solely of ones and
|
||||
zeroes, which is the language of computers.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Bit</glossterm>
|
||||
<glossdef>
|
||||
<para>Is a single digit number that’s in base of 2
|
||||
(either a zero or one). Bandwidth usage is
|
||||
measured in bits-per-second.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Bit Torrent</glossterm>
|
||||
<glossdef>
|
||||
<para>A peer-to-peer system that legally shares files
|
||||
such as legal software updates, movies and other
|
||||
resources.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Blog</glossterm>
|
||||
<glossdef>
|
||||
<para>Refers to an online journal. Blogs can be either
|
||||
personal or professional in tone.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>BPS</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for bit-per-second, the most universal
|
||||
measurement of how quickly data is transferred
|
||||
from place to place.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Browser</glossterm>
|
||||
<glossdef>
|
||||
<para>Any client software that allows a computer or
|
||||
device to access the Internet (Microsoft Internet
|
||||
Explorer, Mozilla Firefox, Google Chrome,
|
||||
etc…).</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Byte</glossterm>
|
||||
<glossdef>
|
||||
<para>Set of bits that make up a single character
|
||||
there are usually 8 bits to a byte.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>C</title>
|
||||
<glossentry>
|
||||
<glossterm>Certificate Authority</glossterm>
|
||||
<glossdef>
|
||||
<para>Issuer of online security certificates that
|
||||
shows if a web site is verified as safe.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Cloud Computing</glossterm>
|
||||
<glossdef>
|
||||
<para>Cloud computing is a model for enabling
|
||||
access to a shared pool of configurable computing
|
||||
resources (such as networks, servers, storage,
|
||||
applications, and services) that can be rapidly
|
||||
provisioned and released with minimal management
|
||||
effort or service provider interaction. The acronym OSSM
|
||||
stands for on-demand, self-service, scalable, and measurable</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Cloudware</glossterm>
|
||||
<glossdef>
|
||||
<para>Refers to software that only exists on the
|
||||
Internet. There is no material product that
|
||||
resides on your computer or disks.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Connection Logging</glossterm>
|
||||
<glossdef>
|
||||
<para>The connection logging feature allows logs to be
|
||||
delivered to a Cloud Files account every hour. For
|
||||
HTTP-based protocol traffic, these are
|
||||
Apache-style access logs. For all other traffic,
|
||||
this is connection and transfer logging.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Cookie</glossterm>
|
||||
<glossdef>
|
||||
<para>Information that web pages save and send back as
|
||||
a way to recognize a user so that on succeeding
|
||||
visits, the users are easily recognized.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<!--<glossentry>
|
||||
<glossterm>Cyberspace</glossterm>
|
||||
<glossdef>
|
||||
<para>Refers to the Internet and all the information
|
||||
stored on it.</para>
|
||||
</glossdef>
|
||||
</glossentry>-->
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>D</title>
|
||||
<glossentry>
|
||||
<glossterm>DHTML</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for Dynamic HyperText Markup Language.
|
||||
Used to refer to pages that use HTML, JavaScript.
|
||||
and CCS to allow users to interact with a web page
|
||||
or show simple animation.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Download</glossterm>
|
||||
<glossdef>
|
||||
<para>The transfer of data – usually in the form of
|
||||
files – from one computer to another.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>DNS</glossterm>
|
||||
<glossdef>
|
||||
<para> The Domain Name System (DNS) is a system by
|
||||
which Internet domain name-to-address and
|
||||
address-to-name resolutions are determined. All
|
||||
domains and their components, such as mail
|
||||
servers, utilize DNS to resolve to the appropriate
|
||||
locations. DNS servers are usually set up in a
|
||||
master-slave relationship such that failure of the
|
||||
master invokes the slave. DNS servers may also be
|
||||
clustered or replicated such that changes made to
|
||||
one DNS server are automatically propagated to
|
||||
other active servers. </para>
|
||||
<para>A system by which Internet domain
|
||||
name-to-address and address-to-name resolutions
|
||||
are determined. Stands for Domain Name System. DNS
|
||||
helps navigate the Internet by translating the IP
|
||||
address into an address that is easier to remember
|
||||
(for example, translating 111.111.111.1 into
|
||||
www.yahoo.com).</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>DNS Record</glossterm>
|
||||
<glossdef>
|
||||
<para>A record that specifies information about a
|
||||
particular domain and belongs to the
|
||||
domain.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Domain</glossterm>
|
||||
<glossdef>
|
||||
<para>Is a name that identifies a web site and
|
||||
separates it from other sites. Often, the domain
|
||||
name will have 2 or more parts that are separated
|
||||
by dots (i.e. yahoo.com, usa.gov, Harvard.edu or
|
||||
mail.yahoo.com).</para>
|
||||
<para> A domain is an entity/container of all
|
||||
DNS-related information containing one or more
|
||||
records. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry>
|
||||
<glossterm>Domain Name System</glossterm>
|
||||
<glossdef>
|
||||
<para>A system by which Internet domain
|
||||
name-to-address and address-to-name resolutions
|
||||
are determined.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<!--<glossentry>
|
||||
<glossterm>Domain Owner</glossterm>
|
||||
<glossdef>
|
||||
<para> Within Rackspace DNS, the account which creates
|
||||
the domain is the domain owner.</para>
|
||||
</glossdef>
|
||||
</glossentry>-->
|
||||
|
||||
<!--<glossentry>
|
||||
<glossterm>Duck</glossterm>
|
||||
<glossdef>
|
||||
<para>An aquatic bird.</para>
|
||||
</glossdef>
|
||||
</glossentry>-->
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>E</title>
|
||||
<glossentry>
|
||||
<glossterm>Email</glossterm>
|
||||
<glossdef>
|
||||
<para>Messages either text or graphical that are sent
|
||||
from one server to another via the
|
||||
Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>entity</glossterm>
|
||||
<glossdef>
|
||||
<para>A generic term for any piece of hardware or
|
||||
software desiring to connect to the network
|
||||
services provided by Quantum, the Network Connectivity service. An entity may
|
||||
make use of Quantum by implementing a VIF.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>F</title>
|
||||
<glossentry>
|
||||
<glossterm>Firewall</glossterm>
|
||||
<glossdef>
|
||||
<para>Software and hardware that communicate with each
|
||||
other to help protect a computer by separating it
|
||||
into two or more parts on a network, making it
|
||||
more difficult to be hacked.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Fixed IP address</glossterm>
|
||||
<glossdef>
|
||||
<para>A fixed IP address can be set and the purpose of
|
||||
the server assigned to the IP address can remain
|
||||
the same even if the server assigned to that IP
|
||||
address changes. This feature lets you swap out
|
||||
virtual machines and the DHCP server re-assigns
|
||||
the same IP address to the swapped-in
|
||||
server.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Flash</glossterm>
|
||||
<glossdef>
|
||||
<para>Technology that is used for Internet animation,
|
||||
originated by Macromedia, now maintained by Adobe.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Flavor</glossterm>
|
||||
<glossdef>
|
||||
<para> A flavor is an available hardware configuration
|
||||
for a server. Each flavor has a unique combination
|
||||
of disk space, memory capacity and priority for
|
||||
CPU time. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>FTP</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for File Transfer Protocol which is a
|
||||
method of moving files between two separate sites
|
||||
on the Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>G</title>
|
||||
<glossentry>
|
||||
<glossterm>Gateway</glossterm>
|
||||
<glossdef>
|
||||
<para>Hardware or software that translates between two
|
||||
different protocols.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>GIF</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for Graphic Interchange Format, a type of
|
||||
image file that is commonly used for animated
|
||||
images on web pages.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>glance</glossterm>
|
||||
<glossdef>
|
||||
<para>The name of the project that provides the OpenStack Image Service.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>H</title>
|
||||
<glossentry>
|
||||
<glossterm>Hacker</glossterm>
|
||||
<glossdef>
|
||||
<para>An intruder who attempts to enter a site for the
|
||||
purpose of causing intentional damage.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<!--<glossentry>
|
||||
<glossterm>Health Monitor</glossterm>
|
||||
<glossdef>
|
||||
<para>A health monitor is a feature of each load
|
||||
balancer. It is used to determine whether or not a
|
||||
back-end node is usable for processing a request.
|
||||
The load balancing service supports two types of
|
||||
health monitors: passive and active. </para>
|
||||
</glossdef>
|
||||
</glossentry>-->
|
||||
<glossentry>
|
||||
<glossterm>horizon</glossterm>
|
||||
<glossdef>
|
||||
<para>The project that provides the OpenStack Dashboard.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Host</glossterm>
|
||||
<glossdef>
|
||||
<para>A computer and/or network facility that stores
|
||||
data that is available to be accessed by other
|
||||
computers.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>HTML</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for HyperText Markup Language, the coding
|
||||
that creates documents for use on the
|
||||
Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>HTTP</glossterm>
|
||||
<glossdef>
|
||||
<para>Stands for HyperText Transfer Protocol, the
|
||||
protocol that tells browsers where to go to find
|
||||
information.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Hypertext</glossterm>
|
||||
<glossdef>
|
||||
<para>Any kind of text that contains a link to some
|
||||
other site, commonly found in documents where
|
||||
clicking on a word or words opens up a different
|
||||
web site.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>I</title>
|
||||
<glossentry>
|
||||
<glossterm>Image</glossterm>
|
||||
<glossdef>
|
||||
<para> An image is a collection of files used to
|
||||
create or rebuild a server. Cloud providers can provide a
|
||||
number of pre-built OS images by default. You may
|
||||
also create custom images from cloud servers you
|
||||
have launched. These custom images are useful for
|
||||
backup purposes or for producing “gold” server
|
||||
images if you plan to deploy a particular server
|
||||
configuration frequently. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Instance</glossterm>
|
||||
<glossdef>
|
||||
<para> An instance is a virtual machine running or in a known
|
||||
state such as "suspended" that can be used like a hardware server. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>IP Address</glossterm>
|
||||
<glossdef>
|
||||
<para>Number that’s unique to every computer system on
|
||||
the Internet.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>ISP</glossterm>
|
||||
<glossdef>
|
||||
<para>Refers to Internet Service Provider, which is
|
||||
any business that provides Internet access to
|
||||
individuals or businesses.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>J</title>
|
||||
|
||||
<glossentry>
|
||||
<glossterm>Java</glossterm>
|
||||
<glossdef>
|
||||
<para>A programming language that is used to create
|
||||
systems that involve more than one computer by way
|
||||
of a network.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Javascript</glossterm>
|
||||
<glossdef>
|
||||
<para>A programming language used in web pages.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>K</title>
|
||||
<glossentry>
|
||||
<glossterm>keystone</glossterm>
|
||||
<glossdef>
|
||||
<para>The name of the project that provides OpenStack Identity services.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>L</title>
|
||||
<glossentry>
|
||||
<glossterm>Layer-2 network</glossterm>
|
||||
<glossdef><para>A virtual Ethernet network managed by the Quantum
|
||||
service. For the time being, Quantum will manage
|
||||
only Ethernet networks.</para></glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Load Balancer</glossterm>
|
||||
<glossdef>
|
||||
<para>A load balancer is a logical device which
|
||||
belongs to a cloud account. It is used to
|
||||
distribute workloads between multiple back-end
|
||||
systems or services, based on the criteria defined
|
||||
as part of its configuration. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>M</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>N</title>
|
||||
<glossentry>
|
||||
<glossterm>network</glossterm>
|
||||
<glossdef><para>A virtual network providing connectivity
|
||||
between entities, i.e.: collection of virtual
|
||||
ports sharing network connectivity. In the
|
||||
Network Connectivity (Quantum) terminology, a network is always a Layer-2
|
||||
network.</para></glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Node</glossterm>
|
||||
<glossdef>
|
||||
<para>A node is a back-end device providing a service
|
||||
on a specified IP and port.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>nova</glossterm>
|
||||
<glossdef>
|
||||
<para>The name of the project that provides OpenStack Compute.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>O</title>
|
||||
<glossentry>
|
||||
<glossterm>Object storage</glossterm>
|
||||
<glossdef>
|
||||
<para>Provides eventually consistent and redundant storage and retrieval of fixed digital content.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>P</title>
|
||||
<glossentry>
|
||||
<glossterm>plugin</glossterm>
|
||||
<glossdef><para>Software component providing the actual
|
||||
implementation for Quantum APIs, or for Compute APIs, depending on the context.</para></glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>port</glossterm>
|
||||
<glossdef>
|
||||
<para>A port on the virtual network switch represented
|
||||
by a Quantum virtual Layer-2 network.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>Q</title>
|
||||
<glossentry>
|
||||
<glossterm>quantum</glossterm>
|
||||
<glossdef>
|
||||
<para>The project that provides a network connectivity abstraction layer to OpenStack Compute.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>R</title>
|
||||
<glossentry>
|
||||
<glossterm>Rackspace Cloud DNS</glossterm>
|
||||
<glossdef>
|
||||
<para>A Domain Name System (DNS) available to
|
||||
Rackspace Cloud customers. Interactions with
|
||||
Rackspace Cloud DNS occur programmatically via the
|
||||
Rackspace Cloud DNS API as described in this Cloud
|
||||
DNS Developer Guide.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Reboot</glossterm>
|
||||
<glossdef>
|
||||
<para> The reboot function allows for either a soft or
|
||||
hard reboot of a server. With a soft reboot, the
|
||||
operating system is signaled to restart, which
|
||||
allows for a graceful shutdown of all processes. A
|
||||
hard reboot is the equivalent of power cycling the
|
||||
server. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Rebuild</glossterm>
|
||||
<glossdef>
|
||||
<para> The rebuild function removes all data on the
|
||||
server and replaces it with the specified image.
|
||||
Server ID and IP addresses remain the same.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Record</glossterm>
|
||||
<glossdef>
|
||||
<para> A DNS record belongs to a particular domain and
|
||||
is used to specify information about the domain.
|
||||
There are several types of DNS records. Each
|
||||
record type contains particular information used
|
||||
to describe that record's purpose. Examples
|
||||
include mail exchange (MX) records, which specify
|
||||
the mail server for a particular domain, and name
|
||||
server (NS) records, which specify the
|
||||
authoritative name servers for a domain. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Resize</glossterm>
|
||||
<glossdef>
|
||||
<para> The resize function converts an existing server
|
||||
to a different flavor, in essence, scaling the
|
||||
server up or down. The original server is saved
|
||||
for a period of time to allow rollback if there is
|
||||
a problem. All resizes should be tested and
|
||||
explicitly confirmed, at which time the original
|
||||
server is removed. All resizes are automatically
|
||||
confirmed after 24 hours if they are not confirmed
|
||||
or reverted. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry>
|
||||
<glossterm>RESTful</glossterm>
|
||||
<glossdef>
|
||||
<para>A kind of web service API that uses REST, or
|
||||
Representational State Transfer. REST is the style
|
||||
of architecture for hypermedia systems that is
|
||||
used for the World Wide Web.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>S</title>
|
||||
<glossentry>
|
||||
<glossterm>Server</glossterm>
|
||||
<glossdef>
|
||||
<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 virtual machine instance in the
|
||||
Cloud Servers system. Flavor and image are
|
||||
requisite elements when creating a server. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Session Persistence</glossterm>
|
||||
<glossdef>
|
||||
<para>Session persistence is 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>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Shared IP Address</glossterm>
|
||||
<glossdef>
|
||||
<para> Public IP addresses can be shared across
|
||||
multiple servers for use in various high
|
||||
availability scenarios. When an IP address is
|
||||
shared to another server, the cloud network
|
||||
restrictions are modified to allow each server to
|
||||
listen to and respond on that IP address (you may
|
||||
optionally specify that the target server network
|
||||
configuration be modified). Shared IP addresses
|
||||
can be used with many standard heartbeat
|
||||
facilities (e.g. keepalived) that monitor for
|
||||
failure and manage IP failover. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Shared IP Group</glossterm>
|
||||
<glossdef>
|
||||
<para> A shared IP group is a collection of servers
|
||||
that can share IPs with other members of the
|
||||
group. Any server in a group 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>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry>
|
||||
<glossterm>Social Networking</glossterm>
|
||||
<glossdef>
|
||||
<para>The act of joining groups and websites where you will find
|
||||
people with similar interests. Individuals and
|
||||
businesses use social networking sites such as Facebook,
|
||||
LinkedIn and Twitter to share experiences
|
||||
with others online.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>swift</glossterm>
|
||||
<glossdef>
|
||||
<para>The project that provides OpenStack Object Storage services.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>subdomain</glossterm>
|
||||
<glossdef>
|
||||
<para>A domain within a parent domain. Subdomains
|
||||
cannot be registered. Subdomains allow you to
|
||||
delegate domains. Subdomains can themselves have
|
||||
subdomains, so third-level, fourth-level,
|
||||
fifth-level, and deeper levels of nesting are
|
||||
possible. </para>
|
||||
<para>Subdomains are domains within a parent domain,
|
||||
and subdomains cannot be registered. Subdomains
|
||||
allow you to delegate domains. Subdomains can
|
||||
themselves have subdomains, so third-level,
|
||||
fourth-level, fifth-level, and deeper levels of
|
||||
nesting are possible. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>T</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>U</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>V</title>
|
||||
<glossentry>
|
||||
<glossterm>VIF</glossterm>
|
||||
<glossdef><para>A Virtual network InterFace plugged into a port of a Quantum
|
||||
network; typically a virtual network interface
|
||||
belonging to a VM</para></glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Virtual IP</glossterm>
|
||||
<glossdef>
|
||||
<para>A virtual IP is an Internet Protocol (IP)
|
||||
address configured on the load balancer for use by
|
||||
clients connecting to a service that is load
|
||||
balanced. Incoming connections are distributed to
|
||||
back-end nodes based on the configuration of the
|
||||
load balancer. </para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm>Virus</glossterm>
|
||||
<glossdef>
|
||||
<para>Harmful piece of computer programming that
|
||||
interferes with normal computer and Internet
|
||||
operations.</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>W</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>X</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>Y</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
<glossdiv>
|
||||
<title>Z</title>
|
||||
<glossentry>
|
||||
<glossterm/>
|
||||
<glossdef>
|
||||
<para/>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
</glossdiv>
|
||||
<!-- ... -->
|
||||
</glossary>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user