openstack/openstack-manuals
Code Issues Proposed changes

Update the dashboard chapter in the Admin User Guide

Browse Source 
bug: #1218649

Change-Id: I38bd71af696ba75d21ba837d32a6cf6e466db362
author: diane fleming
This commit is contained in:
Diane Fleming 2013-08-29 19:46:26 -05:00
parent 4e505f3554
commit d5baa108c4
20 changed files with 1650 additions and 772 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

103
doc/src/docbkx/common/section_dashboard_access.xml
View File

@ -10,8 +10,8 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:raxm="http://docs.rackspace.com/api/metadata" version="5.0"
xml:id="log_in_dashboard">
<?dbhtml stop-chunking?>
<title>Log in to the dashboard</title>
<?dbhtml-stop-chunking?>
<para>The dashboard is available on the node with the
<literal>nova-dashboard</literal> server role.</para>
<procedure>
@ -38,7 +38,7 @@
</step>
<step>
<para>In the address bar, type the host name or IP address
that you got from the cloud operator:</para>
for the dashboard:</para>
<screen><userinput>https://<replaceable>IP_ADDRESS_OR_HOSTNAME</replaceable>/</userinput></screen>
<note>
<title>Certificate Warning</title>
@ -73,11 +73,11 @@
</procedure>
<section xml:id="dashboard_project_tab">
<title>OpenStack dashboard&mdash;Project tab</title>
<para>Select a project from the drop-down list on the left
side to view and perform tasks for resources created by
users of that project. The <guilabel>Project</guilabel>
tab displays the details of the projects to which you
belong.</para>
<para>Select a project from the <guilabel>CURRENT
PROJECT</guilabel> drop-down list on the left side to
view and manage resources in that project.</para>
<para>The <guilabel>Project</guilabel> tab displays the
details of the selected project.</para>
<informalfigure xml:id="dashboard_project_user">
<mediaobject>
<imageobject>
@ -86,8 +86,7 @@
</imageobject>
</mediaobject>
</informalfigure>
<para>Then, access the following categories to perform the
following tasks:</para>
<para>Access the following categories to complete these tasks:</para>
<variablelist>
<varlistentry>
<term><guilabel>Overview</guilabel></term>
@ -115,38 +114,41 @@
Snapshots</guilabel></term>
<listitem>
<para>View images, instance snapshots, and volume
snapshots created by users of the project,
plus any images that are publicly available.
Create, edit, and delete images, and launch
instances from images and snapshots.</para>
snapshots created project users, plus any
images that are publicly available. Create,
edit, and delete images, and launch instances
from images and snapshots.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Access &amp;
Security</guilabel></term>
<listitem>
<itemizedlist>
<listitem>
<para><guilabel>Security Groups</guilabel>
tab. View, create, edit, and delete
security groups and security group
rules.</para>
</listitem>
<listitem>
<para><guilabel>Keypairs</guilabel> tab.
View, create, edit, and import
keypairs, and delete keypairs.</para>
</listitem>
<listitem>
<para><guilabel>Floating IPs</guilabel>
tab. Allocate an IP address to or
release it from a project.</para>
</listitem>
<listitem>
<para><guilabel>API Access</guilabel> tab.
View API endpoints.</para>
</listitem>
</itemizedlist>
<para>Use these tabs to complete these
tasks:</para>
<formalpara>
<title><guilabel>Security Groups</guilabel>
tab</title>
<para>View, create, edit, and delete security
groups and security group rules.</para>
</formalpara>
<formalpara>
<title><guilabel>Keypairs</guilabel>
tab</title>
<para>View, create, edit, and import keypairs,
and delete keypairs.</para>
</formalpara>
<formalpara>
<title><guilabel>Floating IPs</guilabel>
tab</title>
<para>Allocate an IP address to or release it
from a project.</para>
</formalpara>
<formalpara>
<title><guilabel>API Access</guilabel>
tab</title>
<para>View API endpoints.</para>
</formalpara>
</listitem>
</varlistentry>
</variablelist>
@ -165,9 +167,7 @@
</imageobject>
</mediaobject>
</informalfigure>
<para>On the <guilabel>Admin</guilabel> tab, access the
following categories to perform the following
tasks:</para>
<para>Access the following categories to complete these tasks:</para>
<variablelist>
<varlistentry>
<term><guilabel>Overview</guilabel></term>
@ -224,19 +224,20 @@
<varlistentry>
<term><guilabel>System Info</guilabel></term>
<listitem>
<itemizedlist>
<listitem>
<para><guilabel>Services</guilabel> tab.
View services.</para>
</listitem>
<listitem>
<para><guilabel>Default Quotas</guilabel>
tab. View default quota values. Quotas
are hard-coded in OpenStack Compute
and define the maximum allowable size
and number of resources.</para>
</listitem>
</itemizedlist>
<para>Access the following tabs to complete these tasks:</para>
<formalpara>
<title><guilabel>Services</guilabel>
tab</title>
<para>View services.</para>
</formalpara>
<formalpara>
<title><guilabel>Default Quotas</guilabel>
tab</title>
<para>View default quota values. Quotas are
hard-coded in OpenStack Compute and define
the maximum allowable size and number of
resources.</para>
</formalpara>
</listitem>
</varlistentry>
</variablelist>

90
doc/src/docbkx/common/section_dashboard_manage_images.xml
View File

@ -1,90 +0,0 @@
<?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" version="5.0"
xml:id="dashboard_manage_images">
<title>Upload images</title>
<para>The cloud operator assigns roles to users, which determines
who can upload and manage images. Image upload and management
might be restricted to only cloud administrators or cloud
operators. If the administrator or cloud operator has granted you
permission, you can upload and manage images. You can also use the
glance and nova clients or the Image Service and Compute APIs to
manage images. See <xref linkend="cli_manage_images"/>. For
details about image creation, see the <link
xlink:href="http://docs.openstack.org/trunk/openstack-image/content/"
><citetitle>Virtual Machine Image
Guide</citetitle></link>.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard, choose a project, and
click the <guilabel>Images &amp; Snapshots</guilabel>
category.</para>
</step>
<step>
<para>Click <guibutton>Create Image</guibutton>. The
<guilabel>Create An Image</guilabel> window appears:</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata fileref="figures/user_image_create.png"
format="PNG" width="4in" contentwidth="4in"/>
</imageobject>
</mediaobject>
</informalfigure>
</step>
<step>
<para>In the <guilabel>Create An Image</guilabel> window, enter
or select the following values:</para>
<informaltable rules="all">
<col width="25%"/>
<col width="75%"/>
<tbody>
<tr>
<td><para><guilabel>Name</guilabel></para></td>
<td><para>Enter a name for the image.</para></td>
</tr>
<tr>
<td><para><guilabel>Description</guilabel></para></td>
<td><para>Enter a brief description about the
image.</para></td>
</tr>
<tr>
<td><para><guilabel>Image Location</guilabel></para></td>
<td><para>Include the URL of the image.</para></td>
</tr>
<tr>
<td><para><guilabel>Image File</guilabel></para></td>
<td><para>Alternatively, browse to find the file on your
machine.</para></td>
</tr>
<tr>
<td><para><guilabel>Format</guilabel></para></td>
<td><para>Select the image format.</para></td>
</tr>
<tr>
<td><para><guilabel>Minimum Disk (GB)</guilabel> and
<guilabel>Maximum Disk (GB)</guilabel></para></td>
<td><para>Leave these fields empty.</para>
</td>
</tr>
<tr>
<td><para><guilabel>Public</guilabel></para></td>
<td><para>Select this option to make the image public to
all users.</para></td>
</tr>
<tr>
<td><para><guilabel>Protected</guilabel></para></td>
<td><para>Select this option to ensure only users with
permissions can delete it.</para></td>
</tr>
</tbody>
</informaltable>
</step>
<step>
<para>Click <guibutton>Create Image</guibutton>.</para>
<para>The image is queued to be uploaded. It might take some
time before the status changes from queued to active.</para>
</step>
</procedure>
</section>

9
doc/src/docbkx/openstack-user-admin/src/bk-admin-user-guide.xml
View File

@ -38,9 +38,9 @@
<para>OpenStack is an open source cloud computing platform
for public and private clouds. A series of
interrelated projects deliver a cloud infrastructure
solution. This guide shows OpenStack admin users how to
create and manage resources in an OpenStack cloud with
the OpenStack dashboard or OpenStack client
solution. This guide shows OpenStack admin users how
to create and manage resources in an OpenStack cloud
with the OpenStack dashboard or OpenStack client
commands.</para>
</abstract>
<revhistory>
@ -49,7 +49,8 @@
<revdescription>
<itemizedlist>
<listitem>
<para>First edition of this document.</para>
<para>First edition of this
document.</para>
</listitem>
</itemizedlist>
</revdescription>

24
doc/src/docbkx/openstack-user-admin/src/ch_dashboard.xml
View File

@ -10,15 +10,27 @@
<title>OpenStack dashboard</title>
</info>
<para>As a cloud administrative user, the OpenStack dashboard lets
you create and manage projects and users, images, and flavors,
and set quotas.</para>
you create and manage projects, users, images, and flavors.
You can also set quotas and create and manage services. For
information about using the dashboard to perform end user
tasks, see the
<link xlink:href="http://docs.openstack.org/user-guide/content/"
><citetitle>OpenStack End User
Guide</citetitle></link>.</para>
<xi:include href="../../common/section_dashboard_access.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_manage_projects_users.xml"/>
<xi:include
href="section_dashboard_admin_manage_projects_users.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_manage_images.xml"/>
<xi:include href="section_dashboard_admin_manage_instances.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_manage_flavors.xml"/>
<xi:include href="section_dashboard_admin_manage_volumes.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_set_quotas.xml"/>
<xi:include href="section_dashboard_admin_manage_images.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_admin_manage_flavors.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_admin_set_quotas.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_admin_manage_services.xml"/>
</chapter>

181
doc/src/docbkx/openstack-user-admin/src/section_cinder_cli_manage_volumes.xml Normal file
View File

@ -0,0 +1,181 @@
<?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" version="5.0"
xml:id="cli_manage_volumes">
<title>Manage volumes</title>
<para>A volume is a detachable block storage device, similar to a
USB hard drive. You can attach a volume to only one instance.
To create and manage volumes, you use a combination of nova
and cinder client commands.</para>
<para>This example creates a volume named
<literal>my-new-volume</literal> based on an image.</para>
<section xml:id="cli_list_volumes"><title>Create a volume</title><procedure>
<step>
<para>List images, and note the ID of the image to use for
your volume:</para>
<screen><prompt>$</prompt> <userinput>nova image-list</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+--------------------------------------+---------------------------------+--------+--------------------------------------+
| ID | Name | Status | Server |
+--------------------------------------+---------------------------------+--------+--------------------------------------+
| 397e713c-b95b-4186-ad46-6126863ea0a9 | cirros-0.3.1-x86_64-uec | ACTIVE | |
| df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.1-x86_64-uec-kernel | ACTIVE | |
| 3cf852bd-2332-48f4-9ae4-7d926d50945e | cirros-0.3.1-x86_64-uec-ramdisk | ACTIVE | |
| 7e5142af-1253-4634-bcc6-89482c5f2e8a | myCirrosImage | ACTIVE | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 |
| 89bcd424-9d15-4723-95ec-61540e8a1979 | mysnapshot | ACTIVE | f51ebd07-c33d-4951-8722-1df6aa8afaa4 |
+--------------------------------------+---------------------------------+--------+--------------------------------------+</computeroutput></screen>
</step>
<step>
<para>List the availability zones, and note the ID of the
availability zone in which to create your
volume:</para>
<screen><prompt>$</prompt> <userinput>nova availability-zone-list</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+-----------------------+----------------------------------------+
| Name | Status |
+-----------------------+----------------------------------------+
| internal | available |
| |- devstack-grizzly | |
| | |- nova-conductor | enabled :-) 2013-07-25T16:50:44.000000 |
| | |- nova-consoleauth | enabled :-) 2013-07-25T16:50:44.000000 |
| | |- nova-scheduler | enabled :-) 2013-07-25T16:50:44.000000 |
| | |- nova-cert | enabled :-) 2013-07-25T16:50:44.000000 |
| | |- nova-network | enabled :-) 2013-07-25T16:50:44.000000 |
| nova | available |
| |- devstack-grizzly | |
| | |- nova-compute | enabled :-) 2013-07-25T16:50:39.000000 |
+-----------------------+----------------------------------------+</computeroutput></screen>
</step>
<step>
<para>Create a volume with 8 GBs of space. Specify the
availability zone and image, as follows:</para>
<screen><prompt>$</prompt> <userinput>cinder create 8 --display-name my-new-volume --image-id 397e713c-b95b-4186-ad46-6126863ea0a9 --availability-zone nova</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+---------------------+--------------------------------------+
| Property | Value |
+---------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2013-07-25T17:02:12.472269 |
| display_description | None |
| display_name | my-new-volume |
| id | 573e024d-5235-49ce-8332-be1576d323f8 |
| image_id | 397e713c-b95b-4186-ad46-6126863ea0a9 |
| metadata | {} |
| size | 8 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| volume_type | None |
+---------------------+--------------------------------------+</computeroutput></screen>
</step>
<step>
<para>To verify that your volume was created successfully,
list the available volumes:</para>
<screen><prompt>$</prompt> <userinput>cinder list</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| 573e024d-5235-49ce-8332-be1576d323f8 | available | my-new-volume | 8 | None | true | |
| bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol | 8 | None | true | |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+</computeroutput></screen>
<para>If your volume was created successfully, its status
is <literal>available</literal>. If its status is
<literal>error</literal>, you might have
exceeded your quota.</para>
</step>
</procedure>
</section>
<section xml:id="cli_attach_volume"><title>Attach a volume to an instance</title>
<procedure> <step>
<para>Attach your volume to a server:</para>
<screen><prompt>$</prompt> <userinput>nova volume-attach 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8 /dev/vdb</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/vdb |
| serverId | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 |
| id | 573e024d-5235-49ce-8332-be1576d323f8 |
| volumeId | 573e024d-5235-49ce-8332-be1576d323f8 |
+----------+--------------------------------------+</computeroutput></screen>
<para>Note the ID of your volume.</para>
</step>
<step>
<para>Show information for your volume:</para>
<screen><prompt>$</prompt> <userinput>cinder show 573e024d-5235-49ce-8332-be1576d323f8</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| attachments | [{u'device': u'/dev/vdb', u'server_id': u'84c6e57d-a6b1-44b6-81eb-fcb36afd31b5', u'id': u'573e024d-5235-49ce-8332-be1576d323f8', u'volume_id': u'573e024d-5235-49ce-8332-be1576d323f8'}] |
| availability_zone | nova |
| bootable | true |
| created_at | 2013-07-25T17:02:12.000000 |
| display_description | None |
| display_name | my-new-volume |
| id | 573e024d-5235-49ce-8332-be1576d323f8 |
| metadata | {} |
| os-vol-host-attr:host | devstack-grizzly |
| os-vol-tenant-attr:tenant_id | 66265572db174a7aa66eba661f58eb9e |
| size | 8 |
| snapshot_id | None |
| source_volid | None |
| status | in-use |
| volume_image_metadata | {u'kernel_id': u'df430cc2-3406-4061-b635-a51c16e488ac', u'image_id': u'397e713c-b95b-4186-ad46-6126863ea0a9', u'ramdisk_id': u'3cf852bd-2332-48f4-9ae4-7d926d50945e', u'image_name': u'cirros-0.3.1-x86_64-uec'} |
| volume_type | None |
+------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+</computeroutput></screen>
<para>The output shows that the volume is attached to the
server with ID
<literal>84c6e57d-a6b1-44b6-81eb-fcb36afd31b5</literal>,
is in the nova availability zone, and is
bootable.</para>
</step>
</procedure></section>
<section xml:id="cli_delete_volumes"><title>Delete a volume</title>
<procedure>
<step>
<para>To delete your volume, you must first detach it from
the server.</para>
<para>To detach the volume from your server, pass the
server ID and volume ID to the command, as
follows:</para>
<screen><prompt>$</prompt> <userinput>nova volume-detach 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8</userinput></screen>
<para>The <command>volume-detach</command> command does
not return any output.</para>
</step>
<step>
<para>List volumes:</para>
<screen><prompt>$</prompt> <userinput>cinder list</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| 573e024d-5235-49ce-8332-be1576d323f8 | available | my-new-volume | 8 | None | true | |
| bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol | 8 | None | true | |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+</computeroutput></screen>
<para>Note that the volume is now available.</para>
</step>
<step>
<para>Now you can delete the volume, as follows:</para>
<screen><prompt>$</prompt> <userinput>cinder delete my-new-volume</userinput></screen>
<para>The delete command does not return any
output.</para>
</step>
<step>
<para>List the volumes again, and note that the status of
your volume is <literal>deleting</literal>:</para>
<screen><prompt>$</prompt> <userinput>cinder list</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| 573e024d-5235-49ce-8332-be1576d323f8 | deleting | my-new-volume | 8 | None | true | |
| bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol | 8 | None | true | |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+</computeroutput></screen>
<para>When the volume is fully deleted, it disappears from
the list of volumes:</para>
<screen><prompt>$</prompt> <userinput>cinder list</userinput></screen>
<screen><?db-font-size 65%?><computeroutput>+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
| bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol | 8 | None | true | |
+--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+</computeroutput></screen>
</step>
</procedure></section>
</section>

281
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_flavors.xml Normal file
View File

@ -0,0 +1,281 @@
<?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" version="5.0"
xml:id="dashboard_manage_flavors">
<?dbhtml stop-chunking?>
<title>Manage flavors</title>
<para>In OpenStack, a flavor defines the compute, memory, and
storage capacity of a virtual server that users can launch. As
an administrative user, you can create, edit, and delete
flavors.</para>
<para>Only administrative users can create and manage
flavors.</para>
<para>A flavor consists of the following parameters:</para>
<table rules="all" width="50%">
<caption>Flavor parameters</caption>
<col width="20%"/>
<col width="80%"/>
<thead>
<tr>
<th>Parameter</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<para>Flavor Name</para>
</td>
<td>
<para>The flavor name.</para>
</td>
</tr>
<tr>
<td>
<para>VCPUs</para>
</td>
<td>
<para>Number of virtual CPUs to use.</para>
</td>
</tr>
<tr>
<td>
<para>RAM</para>
</td>
<td>
<para>Amount of RAM to use, in megabytes.</para>
</td>
</tr>
<tr>
<td>
<para>Root Disk</para>
</td>
<td>
<para>Amount of disk space (in gigabytes) to use
for the root (/) partition.</para>
</td>
</tr>
<tr>
<td>
<para>Ephemeral Disk</para>
</td>
<td>
<para>Amount of disk space (in gigabytes) to use
for the ephemeral partition. If unspecified,
the value is 0 by default.</para>
<para>Ephemeral disks offer machine local disk
storage linked to the life cycle of a VM
instance. When a VM is terminated, all data on
the ephemeral disk is lost. Ephemeral disks
are not included in any snapshots.</para>
</td>
</tr>
<tr>
<td>
<para>Swap Disk</para>
</td>
<td>
<para>Amount of swap space (in megabytes) to use.
If unspecified, the default is 0.</para>
</td>
</tr>
<tr>
<td>
<para>ID</para>
</td>
<td>
<para>The flavor ID, generated by
OpenStack.</para>
</td>
</tr>
</tbody>
</table>
<para>The default flavors are:</para>
<itemizedlist>
<title>Default Flavors</title>
<listitem>
<para>m1.nano (1 VCPU/0 GB Disk/64 MB RAM)</para>
</listitem>
<listitem>
<para>m1.micro (1 VCPU/0 GB Disk/128 MB RAM)</para>
</listitem>
<listitem>
<para>m1.tiny (1 VCPU/0 GB Disk/512 MB RAM)</para>
</listitem>
<listitem>
<para>m1.small (1 VCPU/20 GB Disk/2048 MB RAM)</para>
</listitem>
<listitem>
<para>m1.medium (2 VCPU/40 GB Disk/4096 MB RAM)</para>
</listitem>
<listitem>
<para>m1.large (4 VCPU/80 GB Disk/8192 MB RAM)</para>
</listitem>
<listitem>
<para>m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM)</para>
</listitem>
</itemizedlist>
<section xml:id="dashboard_create_flavors">
<title>Create flavors</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project
from the <guilabel>CURRENT PROJECT</guilabel>
drop-down list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Flavors</guilabel> category.</para>
</step>
<step>
<para>Click <guibutton>Create
Flavor</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Create Flavor</guilabel>
window, enter or select the following
values:</para>
<informaltable rules="all" width="75%">
<col width="25%"/>
<col width="75%"/>
<tbody>
<tr>
<td>
<para><guilabel>Name</guilabel></para>
</td>
<td>
<para>Enter the flavor name.</para>
</td>
</tr>
<tr>
<td>
<para><guilabel>VCPUs</guilabel></para>
</td>
<td>
<para>Enter the number of virtual CPUs
to use.</para>
</td>
</tr>
<tr>
<td>
<para><guilabel>RAM
MB</guilabel></para>
</td>
<td>
<para>Enter the amount of RAM to use,
in megabytes.</para>
</td>
</tr>
<tr>
<td>
<para><guilabel>Root Disk
GB</guilabel></para>
</td>
<td>
<para>Enter the mount of disk space in
gigabytes to use for the root (/)
partition.</para>
</td>
</tr>
<tr>
<td>
<para><guilabel>Ephemeral Disk
GB</guilabel></para>
</td>
<td>
<para>Enter the amount of disk space
in gigabytes to use for the
ephemeral partition. If
unspecified, the value is 0 by
default.</para>
<para>Ephemeral disks offer machine
local disk storage linked to the
life cycle of a VM instance. When a
VM is terminated, all data on the
ephemeral disk is lost. Ephemeral
disks are not included in any
snapshots.</para>
</td>
</tr>
<tr>
<td>
<para><guilabel>Swap Disk
GB</guilabel></para>
</td>
<td>
<para>Enter the amount of swap space
(in megabytes) to use. If
unspecified, the default is 0.
</para>
</td>
</tr>
</tbody>
</informaltable>
</step>
<step>
<para>Click <guibutton>Create
Flavor</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_update_flavors">
<title>Update flavors</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project
from the <guilabel>CURRENT PROJECT</guilabel>
drop-down list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Flavors</guilabel> category.</para>
</step>
<step>
<para>Select the flavor that you want to edit. Click
<guibutton>Edit Flavor</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Edit Flavor</guilabel> window,
you can change the flavor name, VCPUs, RAM, root
dish, ephemeral disk, and swap disk
values..</para>
</step>
<step>
<para>Click <guibutton>Save</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_flavors">
<title>Delete flavors</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project
from the <guilabel>CURRENT PROJECT</guilabel>
drop-down list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Flavors</guilabel> category.</para>
</step>
<step>
<para>Select the flavors that you want to
delete.</para>
</step>
<step>
<para>Click <guibutton>Delete
Flavors</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Confirm Delete
Flavors</guilabel> window, click
<guibutton>Delete Flavors</guibutton> to
confirm the deletion. You cannot undo this
action.</para>
</step>
</procedure>
</section>
</section>

148
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_images.xml Normal file
View File

@ -0,0 +1,148 @@
<?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" version="5.0"
xml:id="dashboard_manage_images">
<?dbhtml stop-chunking?>
<title>Create and manage images</title>
<para>As an administrative user, you can create and manage images
for the projects to which you belong. You can also create and
manage images for users in all projects to which you have
access.</para>
<para>To create and manage images in specified projects as an end
user, see the <link
xlink:href="http://docs.openstack.org/user-guide/content/"
><citetitle>OpenStack End User
Guide</citetitle></link>.</para>
<para>To create and manage images as an administrator for other
users, use the following procedures.</para>
<section xml:id="dashboard_create_images">
<title>Create images</title>
<para>For details about image creation, see the <link
xlink:href="http://docs.openstack.org/trunk/openstack-image/content/"
><citetitle>Virtual Machine Image
Guide</citetitle></link>.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Images</guilabel> category. The images that you
can administer for cloud users appear on this page.</para>
</step>
<step>
<para>Click <guibutton>Create Image</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Create An Image</guilabel> window,
enter or select the following values:</para>
<informaltable rules="all" width="50%">
<col width="25%"/>
<col width="75%"/>
<tbody>
<tr>
<td><para><guilabel>Name</guilabel></para></td>
<td><para>Enter a name for the image.</para></td>
</tr>
<tr>
<td><para><guilabel>Description</guilabel></para></td>
<td><para>Enter a brief description about the
image.</para></td>
</tr>
<tr>
<td><para><guilabel>Image
Location</guilabel></para></td>
<td><para>Include the URL of the image.</para></td>
</tr>
<tr>
<td><para><guilabel>Image File</guilabel></para></td>
<td><para>Alternatively, browse to find the image file
on your machine.</para></td>
</tr>
<tr>
<td><para><guilabel>Format</guilabel></para></td>
<td><para>Select the image format.</para></td>
</tr>
<tr>
<td><para><guilabel>Minimum Disk (GB)</guilabel> and
<guilabel>Maximum Disk (GB)</guilabel></para></td>
<td><para>Leave these fields empty.</para>
</td>
</tr>
<tr>
<td><para><guilabel>Public</guilabel></para></td>
<td><para>Select this option to make the image public to
all users.</para></td>
</tr>
</tbody>
</informaltable>
</step>
<step>
<para>Click <guibutton>Create Image</guibutton>.</para>
<para>The image is queued to be uploaded. It might take some
time before the status changes from queued to active.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_update_images">
<title>Update images</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Images</guilabel> category.</para>
</step>
<step>
<para>Select the image that you want to edit. Click
<guilabel>Edit</guilabel>.</para>
</step>
<step>
<para>In the <guilabel>Update Image</guilabel> window, you can
change the name for the image. Select the
<guilabel>Public</guilabel> check box to make the image
public. Clear this check box to make the image private. You
cannot change the kernel ID, RAM disk ID, or architecture
attributes for an image.</para>
</step>
<step>
<para>Click <guibutton>Update Image</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_images">
<title>Delete images</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Images</guilabel> category.</para>
</step>
<step>
<para>Select the images that you want to delete.</para>
</step>
<step>
<para>Click <guibutton>Delete Images</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Confirm Delete Image</guilabel> window,
click <guibutton>Delete Images</guibutton> to confirm the
deletion. </para>
<para>You cannot undo this action.</para>
</step>
</procedure>
</section>
</section>

127
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_instances.xml Normal file
View File

@ -0,0 +1,127 @@
<?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" version="5.0"
xml:id="dashboard_manage_instances">
<?dbhtml stop-chunking?>
<title>Manage instances</title>
<para>As an administrative user, you can manage instances for
users in various projects. You can view, terminate, edit,
perform a soft or hard reboot, create a snapshot from, and
migrate instances. You can also view the logs for instances or
launch a VNC console for an instance.</para>
<para>For information about using the dashboard to launch
instances as an end user, see the <link
xlink:href="http://docs.openstack.org/user-guide/content/"
><citetitle>OpenStack End User
Guide</citetitle></link>.</para>
<section xml:id="dashboard_instance_snapshots">
<title>Create instance snapshots</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Instances</guilabel>
category.</para>
</step>
<step>
<para>Select an instance to create a snapshot from it.
From the <guilabel>Actions</guilabel> drop-down
list, select <guilabel>Create
Snapshot</guilabel>.</para>
</step>
<step>
<para>In the <guilabel>Create Snapshot</guilabel>
window, enter a name for the snapshot. Click
<guibutton>Create Snapshot</guibutton>. The
dashboard shows the instance snapshot in the
<guilabel>Images &amp; Snapshots</guilabel>
category.</para>
</step>
<step>
<para>To launch an instance from the snapshot, select
the snapshot and click
<guibutton>Launch</guibutton>. For information
about launching instances, see the <link
xlink:href="http://docs.openstack.org/user-guide/content/"
><citetitle>OpenStack End User
Guide</citetitle></link>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_control_instance_states">
<title>Control the state of an instance</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Instances</guilabel>
category.</para>
</step>
<step>
<para>Select the instance for which you want to change
the state.</para>
</step>
<step>
<para>In the <guilabel>More</guilabel> drop-down list
in the <guilabel>Actions</guilabel> column, select
the state.</para>
<para>Depending on the current state of the instance,
you can choose to pause, un-pause, suspend,
resume, soft or hard reboot, or terminate an
instance. <figure>
<title>OpenStack dashboard: Actions</title>
<mediaobject>
<imageobject>
<imagedata
fileref="../../common/figures/change_instance_state.png"
format="PNG" contentwidth="4in"/>
</imageobject>
</mediaobject>
</figure>
</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_track_usage">
<title>Track usage</title>
<para>Use the <guilabel>Overview</guilabel> category to track
usage of instances for each project.</para>
<para>You can track costs per month by showing metrics like
number of VCPUs, disks, RAM, and uptime of all your
instances.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Instances</guilabel>
category.</para>
</step>
<step>
<para>Select a month and click
<guibutton>Submit</guibutton> to query the
instance usage for that month.</para>
</step>
<step>
<para>Click <guibutton>Download CSV
Summary</guibutton> to download a CSV
summary.</para>
</step>
</procedure>
</section>
</section>

297
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_projects_users.xml Normal file
View File

@ -0,0 +1,297 @@
<?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" version="5.0"
xml:id="dashboard_manage_projects_users">
<?dbhtml stop-chunking?>
<title>Manage projects and users</title>
<para>As a cloud administrator, you manage both projects and
users. Projects are organizational units in the cloud to which
you can assign users. Projects are also known as <emphasis
role="italic">tenants</emphasis> or <emphasis
role="italic">accounts</emphasis>.You can manage projects
and users independently from each other.</para>
<para>Users are members of one or more projects.</para>
<para>During cloud set up, the operator defines at least one
project, user, and role. The operator links the role to the
user and the user to the project. Roles define the actions
that users can perform. As an administrator, you can create
additional projects and users as needed.</para>
<para>Learn how to add, update, and delete projects and users,
assign users to one or more projects, and change or remove the
assignment. To enable or temporarily disable a project or
user, update that project or user. You can also change quotas
at the project level. For information, see <xref
linkend="dashboard_set_quotas"/>.</para>
<para>When you create a user account, you must assign the account
to a primary project. Optionally, you can assign the account
to additional projects. Before you can delete a user account,
you must remove the user account from its primary
project.</para>
<section xml:id="disable_project">
<title>Consequences of disabling projects and users</title>
<para>When you disable a project, it has the following
consequences:</para>
<itemizedlist>
<listitem>
<para>In the dashboard, users can no longer access the
project from the <guilabel>CURRENT
PROJECT</guilabel> drop-down list on the
<guilabel>Project</guilabel> tab.</para>
</listitem>
<listitem>
<para>Users who are members of only the disabled
project can no longer log in.</para>
</listitem>
<listitem>
<para>You cannot launch instances for a disabled
project. Instances that are already running are
not automatically terminated though—you must stop
them manually.</para>
</listitem>
<listitem>
<para>The data for a disabled project is maintained so
that you can enable the project again at any
time.</para>
</listitem>
</itemizedlist>
<para>When you disable a user account, the user can no longer
log in, but the data for the user is maintained so that
you can enable the user again at any time.</para>
</section>
<section xml:id="dashboard_create_project">
<title>Create a project</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Projects</guilabel> category.</para>
</step>
<step>
<para>Click <guibutton>Create
Project</guibutton>.</para>
</step>
<step>
<para>On the <guilabel>Project Info</guilabel> tab in
the <guilabel>Create Project</guilabel> window,
enter a name and description for the project. By
default, the project is enabled. See <xref
linkend="disable_project"/>.</para>
</step>
<step>
<para>On the <guilabel>Project Members</guilabel> tab,
add members to the project.</para>
</step>
<step>
<para>On the <guilabel>Quota</guilabel> tab, edit
quota values. For information about quotas, see
<xref linkend="quotas"/>.</para>
</step>
<step>
<para>Click <guibutton>Create
Project</guibutton>.</para>
<para>The <guilabel>Projects</guilabel> category shows
the project, including its assigned ID.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_update_project">
<title>Update a project</title>
<para>You can update a project to change its name or
description, and enable or temporarily disable it.</para>
<procedure>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Projects</guilabel> category.</para>
</step>
<step>
<para>Select the project that you want to update.
</para>
</step>
<step>
<para>In the <guilabel>More</guilabel> drop-down list,
click <guilabel>Edit Project</guilabel>.</para>
</step>
<step>
<para>In the <guilabel>Edit Project</guilabel> window,
you can update a project to change its name or
description, and enable or temporarily disable
it.</para>
<para>By default, the project is enabled. To
temporarily disable it, clear the
<guilabel>Enabled</guilabel> check box. To
enable a disabled project, select the
<guilabel>Enabled</guilabel> check box.</para>
</step>
<step>
<para>Click <guibutton>Save</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_user_assignments">
<title>Modify user assignments for a project</title>
<para>When you create users, you must assign them to a primary
project as described in <xref
linkend="dashboard_create_user"/>. You can assign
users to additional projects or update and remove
assignments.</para>
<procedure>
<step>
<para>On the <guilabel>Admin</guilabel> tab, select
the <guilabel>Projects</guilabel> category.</para>
</step>
<step>
<para>Select a project to modify its user
assignments.</para>
</step>
<step>
<para>Select <guibutton>Modify
Users</guibutton>.</para>
<para>The <guilabel>Edit Project</guilabel> window
shows the following lists of users:</para>
<itemizedlist>
<listitem>
<para><guilabel>All Users</guilabel>. Users
that are available to be assigned to the
current project.</para>
</listitem>
<listitem>
<para><guilabel>Project Members</guilabel>.
Users that are assigned to the current
project, </para>
</listitem>
</itemizedlist>
<mediaobject>
<imageobject>
<imagedata
fileref="./figures/cloud_dash_users_list.png"
/>
</imageobject>
</mediaobject>
</step>
<step>
<para>To assign a user to the current project, click
<guibutton>+</guibutton> for the user.</para>
<para>The user moves from the <guilabel>All
Users</guilabel> list to the <guilabel>Project
Members</guilabel> list.</para>
</step>
<step>
<para>To remove a user from the current project, click
the <guibutton>-</guibutton> button for the
user.</para>
<para>The user moves from the <guilabel>Project
Members</guilabel> list to the <guilabel>All
Users</guilabel> list.</para>
</step>
<step>
<para>Click <guibutton>Save</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_project">
<title>Delete projects</title>
<procedure>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Projects</guilabel> category.</para>
</step>
<step>
<para>Select the projects that you want to delete.
</para>
</step>
<step>
<para>Click <guibutton>Delete Projects</guibutton> to
confirm the deletion.</para>
<note>
<para>You cannot undo the delete action.</para>
</note>
</step>
</procedure>
</section>
<section xml:id="dashboard_create_user">
<title>Create a user account</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, select
the <guilabel>Users</guilabel> category.</para>
</step>
<step>
<para>Click <guibutton>Create User</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Create User</guilabel> window,
enter a user name, email, and preliminary password
for the user. Confirm the password.</para>
<para>Select a project from the <guilabel>Primary
Project</guilabel> drop-down list.</para>
<para>Choose a role for the user from the
<guilabel>Role</guilabel> drop-down list.
Default is <literal>Member</literal>.</para>
</step>
<step>
<para>Click <guibutton>Create User</guibutton> to
confirm your changes.</para>
<para>Respond to the prompt to remember the password
for the user.</para>
<para>The dashboard assigns an ID to the user, and the
user appears in the <guilabel>Users</guilabel>
category. </para>
</step>
</procedure>
</section>
<section xml:id="dashboard_disable_user">
<title>Disable or enable a user</title>
<procedure>
<step>
<para>On the <guilabel>Admin</guilabel> tab, select
the <guilabel>Users</guilabel> category.</para>
</step>
<step>
<para>Select the user that you want to disable or
enable. You can disable or enable only one user at
a time.</para>
</step>
<step>
<para>In the <guilabel>Actions</guilabel> drop-down
list, select <guilabel>Disable User</guilabel> or
<guilabel>Enable User</guilabel>.</para>
<para>In the <guilabel>Enabled</guilabel> column, the
enabled value updates to either
<literal>True</literal> or
<literal>False</literal>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_user">
<title>Delete users</title>
<procedure>
<step>
<para>On the <guilabel>Admin</guilabel> tab, select
the <guilabel>Users</guilabel> category.</para>
</step>
<step>
<para>Select the users that you want to delete.</para>
</step>
<step>
<para>Click <guilabel>Delete Users</guilabel>.</para>
</step>
<step>
<para>In the <guilabel>Confirm Delete Users</guilabel>
window, click <guibutton>Delete Users</guibutton>
to confirm the deletion.</para>
</step>
</procedure>
</section>
</section>

34
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_services.xml Normal file
View File

@ -0,0 +1,34 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities bortred from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY plusmn "&#xB1;">
]>
<section xmlns="http://docbook.org/ns/docbook" version="5.0"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
xml:id="dashboard_view_services">
<title>View services information</title>
<para>As an administrative user, you can view information for
OpenStack services.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>System Info</guilabel> category.</para>
</step>
<step>
<para>Click the <guilabel>Services</guilabel> tab to view
services information. </para>
<para>The page shows the internal name and the public OpenStack
name for the service, the host where the service runs, and
whether the service is or is not enabled.</para>
</step>
</procedure>
</section>

123
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_volumes.xml Normal file
View File

@ -0,0 +1,123 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY plusmn "&#xB1;">
]>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="dashboard_manage_volumes">
<?dbhtml stop-chunking?>
<title>Manage volumes and volume types</title>
<para>Volumes are block storage devices that you attach to
instances to enable persistent storage. Users can attach a
volume to a running instance or detach a volume and attach it
to another instance at any time. For information about using
the dashboard to create and manage volumes as an end user, see
the <link
xlink:href="http://docs.openstack.org/user-guide/content/"
><citetitle>OpenStack End User
Guide</citetitle></link>.</para>
<para>As an administrative user, you can manage volumes and volume
types for users in various projects. You can create and delete
volumes types, and you can view and delete volumes. </para>
<section xml:id="dashboard_create_volume_types">
<title>Create a volume type</title>
<procedure>
<!-- <title>To create or delete a volume</title> -->
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Volumes</guilabel> category.</para>
</step>
<step>
<para>Click <guibutton>Create Volume
Type</guibutton>.</para>
<para>In the <guilabel>Create Volume Type</guilabel>
window, enter a name for the volume type.</para>
</step>
<step>
<para>Click <guibutton>Create Volume Type</guibutton>
to confirm your changes.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_volume_types">
<title>Delete volume types</title>
<para>When you delete a volume type, volumes of that type are
not deleted.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Volumes</guilabel> category.</para>
</step>
<step>
<para>Select the volume type or types that you want to
delete.</para>
</step>
<step>
<para>Click <guibutton>Delete Volume
Types</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Confirm Delete Volume
Types</guilabel> window, click
<guibutton>Delete Volume Types</guibutton> to
confirm the action.</para>
</step>
<step>
<para>A message indicates whether the action
succeeded.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_volume">
<title>Delete volumes</title>
<para>When you delete an instance, the data of its attached
volumes is not destroyed.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Volumes</guilabel> category.</para>
</step>
<step>
<para>Select the volume or volumes that you want to
delete.</para>
</step>
<step>
<para>Click <guibutton>Delete
Volumes</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Confirm Delete
Volumes</guilabel> window, click
<guibutton>Delete Volumes</guibutton> to
confirm the action.</para>
</step>
<step>
<para>A message indicates whether the action
succeeded.</para>
</step>
</procedure>
</section>
</section>

197
doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_set_quotas.xml Normal file
View File

@ -0,0 +1,197 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities bortred from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY plusmn "&#xB1;">
]>
<section xmlns="http://docbook.org/ns/docbook" version="5.0"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
xml:id="dashboard_set_quotas">
<?dbhtml stop-chunking?>
<title>View and manage quotas</title>
<para>As an administrative user, you can set quotas when you <xref
linkend="dashboard_create_project"/> or update quotas for an
existing project. Quotas are operational limits that prevent
system capacities from being exhausted without notification. For
example, to optimize cloud resources, you can control the number
of gigabytes allowed for each project. You enforce quotas at the
project, or tenant, level rather than at the user level.</para>
<para>Typically, you change quotas when a project needs more than 10
volumes or 1 TB on a Compute node.</para>
<para>The following tables describe the Compute and Block Storage
service quotas:</para>
<table rules="all" width="50%" xml:id="compute_quotas">
<caption>Compute quotas</caption>
<col width="30%"/>
<col width="70%"/>
<thead>
<tr>
<th>Quota</th>
<th>Defines the number of</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<para>Metadata Items</para>
</td>
<td>
<para>Metadata items allowed for each instance.</para>
</td>
</tr>
<tr>
<td>
<para>VCPUs</para>
</td>
<td>
<para>Instance cores allowed for each project.</para>
</td>
</tr>
<tr>
<td>
<para>Instances</para>
</td>
<td>
<para>Instances allowed for each project.</para>
</td>
</tr>
<tr>
<td>
<para>Injected Files</para>
</td>
<td>
<para>Injected files allowed for each project.</para>
</td>
</tr>
<tr>
<td>
<para>Injected File Content Bytes</para>
</td>
<td>
<para>Content bytes allowed for each injected file.</para>
</td>
</tr>
<tr>
<td>
<para>RAM (MB)</para>
</td>
<td>
<para>RAM megabytes allowed for each instance.</para>
</td>
</tr>
<tr>
<td>
<para>Floating IPs</para>
</td>
<td>
<para>Floating IP addresses allowed for each project.</para>
</td>
</tr>
<tr>
<td>
<para>Fixed IPs</para>
</td>
<td>
<para>Fixed IP addresses allowed for each project. Must be
equal to or greater than the number of allowed
instances.</para>
</td>
</tr>
<tr>
<td>
<para>Security Groups</para>
</td>
<td>
<para>Security groups allowed for each project.</para>
</td>
</tr>
<tr>
<td>
<para>Security Group Rules</para>
</td>
<td>
<para>Rules allowed for each security group.</para>
</td>
</tr>
</tbody>
</table>
<table rules="all" width="50%" xml:id="block_storage_quotas">
<caption>Block Storage quotas</caption>
<col width="30%"/>
<col width="70%"/>
<thead>
<tr>
<th>Quota</th>
<th>Defines the number of</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<para>Volumes</para>
</td>
<td>
<para>Volumes allowed for each project.</para>
</td>
</tr>
<tr>
<td>
<para>Gigabytes</para>
</td>
<td>
<para>Volume gigabytes allowed for each project.</para>
</td>
</tr>
</tbody>
</table>
<section xml:id="dashboard_set_quotas_procedure">
<title>View default project quotas</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard and choose the
<guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>System Info</guilabel> category.</para>
</step>
<step>
<para>Click the <guilabel>Default Quotas</guilabel> tab to
view the default quotas for the Compute and Block Storage
services.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_project_quotas">
<title>Update project quotas</title>
<procedure>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click the
<guilabel>Projects</guilabel> category.</para>
</step>
<step>
<para>Select a project to change its quota values.</para>
</step>
<step>
<para>In the <guilabel>More</guilabel> drop-down list, click
<guilabel>Modify Quotas</guilabel>.</para>
</step>
<step>
<para>On the <guilabel>Quota</guilabel> tab in the
<guilabel>Edit Project</guilabel> window, edit quota
values. Then, click <guibutton>Save</guibutton>.</para>
</step>
</procedure>
<note>
<para>The dashboard does not show all possible project quotas.
To view and update the quotas for a service, use the keystone
command-line client. See <xref linkend="cli_set_quotas"
/>.</para>
</note>
</section>
</section>

10
doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_flavors.xml
View File

@ -1,10 +0,0 @@
<?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"
version="5.0"
xml:id="dashboard_manage_flavors">
<title>Manage flavors</title>
<?dbhtml stop-chunking?>
<para></para>
</section>

18
doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_images.xml
View File

@ -1,18 +0,0 @@
<?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" version="5.0"
xml:id="admin_dashboard_manage_images">
<title>Manage images</title>
<para>During setup of OpenStack cloud, the cloud operator sets
user permissions to manage images. Image upload and management
might be restricted to only cloud administrators or cloud
operators. Though you can complete most tasks with the
OpenStack dashboard, you can manage images through only the
glance and nova clients or the Image Service and Compute APIs.
See <xref linkend="cli_manage_images"/>.</para>
<para>For details about image creation, see the <link
xlink:href="http://docs.openstack.org/trunk/openstack-image/content/"
><citetitle>Virtual Machine Image
Guide</citetitle></link>.</para>
</section>

319
doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_projects_users.xml
View File

@ -1,319 +0,0 @@
<?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" version="5.0"
xml:id="dashboard_manage_projects_users">
<title>Projects and users</title>
<?dbhtml stop-chunking?>
<para>In an OpenStack cloud, you can manage projects and users
independently from each other.</para>
<para>Projects represent different organizational units in the
cloud to which you can assign users.</para>
<para>Cloud admin users perform both project and user management
tasks.</para>
<para>During the basic system set up, the cloud operator must
define at least one project, user, and role. The operator
links the role to the user and the user to the project. Roles
define which actions users can perform.</para>
<para>As an admin user, you can create additional projects and
users as needed.</para>
<para>Learn how to add, update, and delete projects and users,
assign users to one or more projects, and change or remove the
assignment. To enable or temporarily disable a project or
user, update that project or user.</para>
<section xml:id="dashboard_projects">
<title>Create and manage projects</title>
<para>You can create, temporarily disable, enable, and delete
projects.</para>
<section xml:id="dashboard_create_project">
<title>Create a project</title>
<procedure>
<step
xmlns:raxm="http://docs.rackspace.com/api/metadata">
<para>Log in to the OpenStack dashboard.</para>
</step>
<step>
<para>In the <guilabel>CURRENT PROJECT</guilabel>
drop-down list on the
<guilabel>Project</guilabel> tab, select
the <literal>admin</literal> project.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab, click
the <guilabel>Projects</guilabel>
category.</para>
</step>
<step>
<para>Click <guibutton>Create
Project</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Create Project</guilabel>
window, enter a name and description for the
project. By default, the project is enabled.
See <xref linkend="disable_project"/>. Click
<guibutton>Create
Project</guibutton>.</para>
<para>The dashboard assigns an ID and shows the
project in the <guilabel>Projects</guilabel>
category.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_update_project">
<title>Update a project</title>
<procedure>
<para>You can update a project to change its name or
description, and to enable or temporarily disable
it.</para>
<para>Disabling a project has the following
consequences:</para>
<itemizedlist xml:id="disable_project">
<title>Consequences of disabling a project</title>
<listitem>
<para>In the dashboard, the project can no
longer be accessed from the
<guilabel>CURRENT PROJECT</guilabel>
drop-down list on the
<guilabel>Project</guilabel>
tab.</para>
</listitem>
<listitem>
<para>Users that are only members of the
disabled project can no longer log
in.</para>
</listitem>
<listitem>
<para>It is impossible to launch new instances
for a disabled project. Instances already
running are not automatically terminated
though—you must stop them manually.</para>
</listitem>
<listitem>
<para>All data for a disabled project is kept
so that you can enable the project again
at any time.</para>
</listitem>
</itemizedlist>
<step>
<para>Select the project that you want to update.
</para>
</step>
<step>
<para>From the <guilabel>More</guilabel> drop-down
list, click <guilabel>Edit
Project</guilabel>.</para>
</step>
<step>
<para>Optionally, change the following attributes
for the project: <itemizedlist>
<listitem>
<para>Name.</para>
</listitem>
<listitem>
<para>Description.</para>
</listitem>
<listitem>
<para>To disable the project, clear
the <guilabel>Enabled</guilabel>
check box.</para>
<para>To enable the project, select
the <guilabel>Enabled</guilabel>
check box.</para>
</listitem>
</itemizedlist></para>
</step>
<step>
<para>Click <guibutton>Save</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_project">
<title>Delete one or more projects</title>
<procedure>
<step>
<para>Select the projects that you want to delete.
</para>
</step>
<step>
<para>Click <guibutton>Delete Projects</guibutton>
and confirm your choice in the pop-up that
appears.</para>
<note>
<para>You cannot undo the delete
action.</para>
</note>
</step>
</procedure>
</section>
</section>
<section xml:id="dashboard_users">
<title>Create and manage user accounts</title>
<para>Users are members of one or multiple projects.</para>
<para>You can add, update, and delete users. To enable or
temporarily disable a user, update that user.</para>
<para>When you create a user account, you must assign the
account to a primary project. Optionally, you can assign
the account to additional projects.</para>
<para>When you disable a user account, the user can no longer
log in, but the data is kept so that you can enable the
account again at any time.</para>
<para>Before you can delete a user account, you must remove
the user account from its primary project.</para>
<section xml:id="dashboard_create_user">
<title>Create a user account</title>
<procedure>
<step
xmlns:raxm="http://docs.rackspace.com/api/metadata">
<para>Log in to the OpenStack dashboard.</para>
</step>
<step>
<para>In the <guilabel>CURRENT PROJECT</guilabel>
drop-down list on the
<guilabel>Project</guilabel> tab, select
the <literal>admin</literal> project.</para>
</step>
<step>
<para>Click the <guilabel>Users</guilabel>
category.</para>
</step>
<step>
<para>On the <guilabel>Admin</guilabel> tab,
select the <guilabel>Users</guilabel>
category.</para>
</step>
<step>
<para>Click <guibutton>Create
User</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Create User</guilabel>
window, enter a user name, email, and
preliminary password for the user.</para>
<para>Select a project from the <guilabel>Primary
Project</guilabel> drop-down list.</para>
<para>Choose a role for the user from the
<guilabel>Role</guilabel> drop-down list.
Default is <literal>Member</literal>.</para>
</step>
<step>
<para>Click <guibutton>Create User</guibutton> to
confirm your changes.</para>
<para>The dashboard assigns an ID and shows the
user account in the <guilabel>Users</guilabel>
category.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_deactivate_delete_user">
<title>Disable or delete user accounts</title>
<procedure>
<step>
<para>To temporarily deactivate a user account,
select the user, and from the Actions
drop-down list, select Disable.</para>
</step>
<step>
<para>To delete one or more users accounts,
activate the check boxes in front of the user
accounts that you want to delete.</para>
</step>
<step>
<para>Click Delete Users and confirm your choice
in the pop-up that appears.</para>
<para>A message on the Web page shows if the
action has been successful.</para>
<para><emphasis role="italic">NOTE: Remove User
from Primary Project</emphasis></para>
<para>If a user account cannot be deleted, it is
because it is still assigned to its primary
project.</para>
</step>
<step>
<para>To delete a user from a project, edit the
user data to view to which Primary Project the
user is assigned.</para>
</step>
<step>
<para>Remove the user from his primary project as
described in <link
xlink:href="https://www.suse.com/documentation/suse_cloud10/book_cloud_admin/data/sec_adm_dash_projects_users.html#pro_adm_dash_user_assign"
>Modifying User Assignments for a
Project</link>, <link
xlink:href="https://www.suse.com/documentation/suse_cloud10/book_cloud_admin/data/sec_adm_dash_projects_users.html#step_adm_dash_user_remove_start"
/> to <link
xlink:href="https://www.suse.com/documentation/suse_cloud10/book_cloud_admin/data/sec_adm_dash_projects_users.html#step_adm_dash_user_remove_end"
/>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_user_assignments">
<title>Modify user assignments for a project</title>
<para>When creating new users, you must assign them to a
primary project as described in <link
xlink:href="https://www.suse.com/documentation/suse_cloud10/book_cloud_admin/data/sec_adm_dash_projects_users.html#pro_adm_dash_user_create"
>Creating Or Deleting Users Accounts</link>. To
assign users to additional projects or to modify and
remove assignments, proceed as follows:</para>
<procedure>
<title>To modify user assignments for a
project</title>
<step>
<para>On the Admin tab, select the Projects
category.</para>
</step>
<step>
<para>Select the project for which to modify user
assignments.</para>
</step>
<step>
<para>From the Actions drop-down list for the
project, select Modify Users.</para>
<para>The Dashboard shows two lists of users:
<guilabel>Project Members</guilabel> shows
the users assigned to the current project,
<guilabel>All Users</guilabel> shows other
existing users, which can be assigned to the
current project.</para>
<mediaobject>
<imageobject>
<imagedata
fileref="./figures/cloud_dash_users_list.png"
/>
</imageobject>
</mediaobject>
</step>
<step>
<para>To remove a user from the current project,
click the <guibutton>-</guibutton> button
associated with the entry for the user.</para>
</step>
</procedure>
<procedure>
<title>To assign a user to the current project</title>
<step>
<para>Click the <guibutton>+</guibutton> button
associated with the entry for the user.</para>
</step>
<step>
<para>In the window that appears, set the user's
role with which to add him to the project and
click Add. Roles define the actions that the
user is allowed to perform. Roles are
configured by the cloud operator in OpenStack
Identity (Keystone). Actions are defined per
OpenStack service in the respective
/etc/[SERVICE_CODENAME]/policy.json file, for
example in /etc/nova/policy.json for the
Compute (Nova) service. For details, see <link
xlink:href="http://docs.openstack.org/essex/openstack-compute/install/content/keystone-concepts.html"
>http://docs.openstack.org/essex/openstack-compute/install/content/keystone-concepts.html</link>.
</para>
</step>
</procedure>
</section>
</section>
</section>

217
doc/src/docbkx/openstack-user-admin/src/section_dashboard_set_quotas.xml
View File

@ -1,217 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities bortred from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
<!ENTITY plusmn "&#xB1;">
]>
<section xmlns="http://docbook.org/ns/docbook" version="5.0"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
xml:id="dashboard_set_quotas">
<title>Set quotas</title>
<?dbhtml stop-chunking?>
<para>To prevent system capacities from being exhausted without
notification, you can set up quotas. Quotas are operational
limits. For example, to optimize cloud resources, you can control
the number of gigabytes allowed for each project, also known as a tenant. Quotas are
currently enforced at the project level rather than
at the user level.</para>
<para>Typically, you change default values because a project requires
more than 10 volumes, or more than 1 TB on a Compute node.</para>
<para>
<table rules="all" width="624">
<caption>Compute and Block Storage quotas</caption>
<col width="20%"/>
<col width="60%"/>
<col width="20%"/>
<thead>
<tr>
<th>Quota</th>
<th>Description</th>
<th>Service</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<para>Metadata Items</para>
</td>
<td>
<para>Number of metadata items allowed per instance.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>VCPUs</para>
</td>
<td>
<para>Number of instance cores allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Instances</para>
</td>
<td>
<para>Number of instances allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Injected Files</para>
</td>
<td>
<para>Number of injected files allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Injected File Content Bytes</para>
</td>
<td>
<para>Number of content bytes allowed per injected file.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Volumes</para>
</td>
<td>
<para>Number of volumes allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Block Storage</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Gigabytes</para>
</td>
<td>
<para>Number of volume gigabtyes allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Block Storage</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>RAM (MB)</para>
</td>
<td>
<para>Megabytes of ram allowed per instance.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Floating IPs</para>
</td>
<td>
<para>Number of floating IP addresses allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Fixed IPs</para>
</td>
<td>
<para>Number of fixed IP addresses allowed per tenant.
This number must be equal to or greater than the number
of allowed instances.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Security Groups</para>
</td>
<td>
<para>Number of security groups allowed per tenant.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
<tr>
<td>
<para>Security Group Rules</para>
</td>
<td>
<para>Number of rules per security group.</para>
</td>
<td>
<para><systemitem class="service">Compute</systemitem></para>
</td>
</tr>
</tbody>
</table>
</para>
<section xml:id="dashboard_set_quotas_procedure">
<title>Project quotas</title>
<para>As an administrative user in the dashboard, you can set
quotas when you <xref linkend="dashboard_create_project"/> or update quotas for an
existing project.</para>
<procedure>
<title>To view default quotas</title>
<step>
<para>On the <guilabel>Admin</guilabel> tab in the navigation
sidebar, click the <guilabel>System Info</guilabel>
category.</para>
</step>
<step>
<para>Click the <guilabel>Default Quotas</guilabel> tab in the
main page.</para>
</step>
</procedure>
<procedure>
<title>To update project quotas</title>
<step>
<para>On the <guilabel>Admin</guilabel> tab in the navigation
sidebar, click the <guilabel>Projects</guilabel> category.</para>
</step>
<step>
<para>Select the project for which to change quota values.</para>
</step>
<step>
<para>From the <guilabel>More</guilabel> drop-down list, click
<guilabel>Modify Quotas</guilabel>.</para>
</step>
<step>
<para>On the <guilabel>Quota</guilabel> tab in the
<guilabel>Edit Project</guilabel> window, edit quota
values. Then, click <guibutton>Save</guibutton>.</para>
</step>
</procedure>
<note>
<para>Not all possible project quotas are displayed in the
dashboard. To obtain and update the complete list for a
service, use the keystone command-line client. See <xref
linkend="cli_set_quotas"/>.</para>
</note>
</section>
</section>

2
doc/src/docbkx/openstack-user/src/ch_dashboard.xml
View File

@ -17,7 +17,7 @@
<xi:include href="../../common/section_dashboard_access.xml"/>
<?hard-pagebreak?>
<xi:include
href="../../common/section_dashboard_manage_images.xml"/>
href="section_dashboard_manage_images.xml"/>
<?hard-pagebreak?>
<!-- end user guide -->
<xi:include href="section_dashboard_access_and_security.xml"/>

160
doc/src/docbkx/openstack-user/src/section_dashboard_manage_images.xml Normal file
View File

@ -0,0 +1,160 @@
<?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" version="5.0"
xml:id="dashboard_manage_images">
<title>Create and manage images</title>
<para>The cloud operator assigns roles to users, which determines
who can upload and manage images. Image upload and management
might be restricted to only cloud administrators or cloud
operators. If you have admin privileges, you can create and manage
images in the admin project. You can also use the glance and nova
clients or the Image Service and Compute APIs to manage images.
See <xref linkend="cli_manage_images"/>.</para>
<section xml:id="dashboard_create_images">
<title>Create images</title>
<para>For details about image creation, see the <link
xlink:href="http://docs.openstack.org/trunk/openstack-image/content/"
><citetitle>Virtual Machine Image
Guide</citetitle></link>.</para>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Project</guilabel> tab, click the
<guilabel>Images &amp; Snapshots</guilabel>
category.</para>
</step>
<step>
<para>Click <guibutton>Create Image</guibutton>. The
<guilabel>Create An Image</guilabel> window
appears:</para>
<informalfigure>
<mediaobject>
<imageobject>
<imagedata
fileref="../../common/figures/user_image_create.png"
format="PNG" width="4in" contentwidth="4in"/>
</imageobject>
</mediaobject>
</informalfigure>
</step>
<step>
<para>In the <guilabel>Create An Image</guilabel> window,
enter or select the following values:</para>
<informaltable rules="all" width="75%">
<col width="25%"/>
<col width="75%"/>
<tbody>
<tr>
<td><para><guilabel>Name</guilabel></para></td>
<td><para>Enter a name for the image.</para></td>
</tr>
<tr>
<td><para><guilabel>Description</guilabel></para></td>
<td><para>Enter a brief description about the
image.</para></td>
</tr>
<tr>
<td><para><guilabel>Image
Location</guilabel></para></td>
<td><para>Include the URL of the image.</para></td>
</tr>
<tr>
<td><para><guilabel>Image File</guilabel></para></td>
<td><para>Alternatively, browse to find the file on your
machine.</para></td>
</tr>
<tr>
<td><para><guilabel>Format</guilabel></para></td>
<td><para>Select the image format.</para></td>
</tr>
<tr>
<td><para><guilabel>Minimum Disk (GB)</guilabel> and
<guilabel>Maximum Disk (GB)</guilabel></para></td>
<td><para>Leave these fields empty.</para>
</td>
</tr>
<tr>
<td><para><guilabel>Public</guilabel></para></td>
<td><para>Select this option to make the image public to
all users.</para></td>
</tr>
<tr>
<td><para><guilabel>Protected</guilabel></para></td>
<td><para>Select this option to ensure that only users
with permissions can delete it.</para></td>
</tr>
</tbody>
</informaltable>
</step>
<step>
<para>Click <guibutton>Create Image</guibutton>.</para>
<para>The image is queued to be uploaded. It might take some
time before the status changes from queued to active.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_update_images">
<title>Update images</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Project</guilabel> tab, click the
<guilabel>Images &amp; Snapshots</guilabel>
category.</para>
</step>
<step>
<para>Select the image that you want to edit. In the
<guilabel>More</guilabel> drop-down list, click
<guilabel>Edit</guilabel>.</para>
</step>
<step>
<para>In the <guilabel>Update Image</guilabel> window, you can
change the name for the image. Select the
<guilabel>Public</guilabel> check box to make the image
public. Clear this check box to make the image
private.</para>
</step>
<step>
<para>Click <guibutton>Update Image</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="dashboard_delete_images">
<title>Delete images</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard.</para>
<para>Choose the <guilabel>admin</guilabel> project from the
<guilabel>CURRENT PROJECT</guilabel> drop-down
list.</para>
</step>
<step>
<para>On the <guilabel>Project</guilabel> tab, click the
<guilabel>Images &amp; Snapshots</guilabel>
category.</para>
</step>
<step>
<para>Select the images that you want to delete.</para>
</step>
<step>
<para>Click <guibutton>Delete Images</guibutton>.</para>
</step>
<step>
<para>In the <guilabel>Confirm Delete Image</guilabel> window,
click <guibutton>Delete Images</guibutton> to confirm the
deletion. You cannot undo this action.</para>
</step>
</procedure>
</section>
</section>

44
doc/src/docbkx/openstack-user/src/section_dashboard_manage_instances.xml
View File

@ -1,25 +1,17 @@
<?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"
version="5.0"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="dashboard_manage_instances">
<title>Create instance snapshots</title>
<title>Manage instances</title>
<?dbhtml stop-chunking?>
<section xml:id="instance_snapshots">
<title>Create instance snapshots</title>
<procedure>
<title>To create instance snapshots</title>
<step>
<para>Log in to the OpenStack dashboard.</para>
</step>
<step>
<para>If you are a member of multiple projects, select
a project from the drop-down list at the top of
the <guilabel>Project</guilabel> tab.</para>
</step>
<step>
<para>Click the <guilabel>Instances</guilabel>
<para>Log in to the OpenStack dashboard, choose a
project, and click the
<guilabel>Instances</guilabel>
category.</para>
<para>The dashboard lists the instances that are
available for this project.</para>
@ -51,17 +43,10 @@
<section xml:id="control_instance_states">
<title>Control the state of an instance</title>
<procedure>
<title>To control the state of an instance</title>
<step>
<para>Log in to the OpenStack dashboard.</para>
</step>
<step>
<para>If you are a member of multiple projects, select
a project from the drop-down list at the top of
the <guilabel>Project</guilabel> tab.</para>
</step>
<step>
<para>Click the <guilabel>Instances</guilabel>
<para>Log in to the OpenStack dashboard, choose a
project, and click the
<guilabel>Instances</guilabel>
category.</para>
<para>The dashboard lists the instances that are
available for this project.</para>
@ -93,21 +78,12 @@
</section>
<section xml:id="track_usage">
<title>Track usage</title>
<para>Use the dashboard's <guilabel>Overview</guilabel>
category to track usage of instances for each
<para>You can track usage of instances for each
project.</para>
<mediaobject>
<imageobject>
<imagedata
fileref="../../common/figures/dashboard_quota.png"
format="PNG" contentwidth="4in"/>
</imageobject>
</mediaobject>
<para>You can track costs per month by showing metrics like
number of VCPUs, disks, RAM, and uptime of all your
instances.</para>
<procedure>
<title>To track usage</title>
<step>
<para>If you are a member of multiple projects, select
a project from the drop-down list at the top of
@ -120,7 +96,7 @@
</step>
<step>
<para>Click <guibutton>Download CSV
Summary</guibutton> to download a CVS
Summary</guibutton> to download a CSV
summary.</para>
</step>
</procedure>

38
doc/src/docbkx/openstack-user/src/section_dashboard_manage_volumes.xml
View File

@ -12,10 +12,12 @@
xml:id="dashboard_manage_volumes">
<title>Manage volumes</title>
<?dbhtml stop-chunking?>
<para>Volumes are block storage devices that you can attach to
instances. They allow for persistent storage. You can attach a
volume to a running instance, or detach a volume and attach it
to another instance at any time.</para>
<para>Volumes are block storage devices that you attach to
instances to enable persistent storage. You can attach a
volume to a running instance or detach a volume and attach it
to another instance at any time. You can also create a
snapshot from or delete a volume. Only administrative users
can create volume types. </para>
<section xml:id="dashboard_create_volumes">
<title>Create a volume</title>
<procedure>
@ -29,12 +31,13 @@
<step>
<para>Click <guibutton>Create
Volume</guibutton>.</para>
<para>In the window that opens, enter a name to assign
to a volume, a description (optional), and define
the size in GBs.</para>
<para>In the window that opens, enter a name, an
optional description, and the size in GBs for the
volume.</para>
</step>
<step>
<para>Confirm your changes.</para>
<para>Click <guibutton>Create Volume</guibutton> to
confirm your changes.</para>
</step>
<step>
<para>The dashboard shows the volume in the
@ -112,25 +115,16 @@
</step>
</procedure>
</section>
<!-- <section xml:id="create_volume_snapsnots">
<section xml:id="create_volume_snapsnots">
<title>Create volume snapshots</title>
<procedure>
<title>To create volume snapshots:</title>
<step>
<para>Log in to the OpenStack dashboard.</para>
</step>
<step>
<para>If you are a member of multiple projects, select
a project from the drop-down
list at the top of the <guilabel>Project</guilabel> tab.</para>
</step>
<step>
<para>Click the <guilabel>Instances &amp;
<para>Log in to the OpenStack dashboard, choose a
project, and click the <guilabel>Instances &amp;
Volumes</guilabel> category.</para>
</step>
<step>
<para>Select the volume of which to create a snapshot.
<para>Select a volume from which to create a snapshot.
</para>
</step>
<step>
@ -149,7 +143,7 @@
category.</para>
</step>
</procedure>
</section>-->
</section>
<section xml:id="dashboard_delete_volume">
<title>Delete volumes</title>
<para>When you delete an instance, the data of its attached