From d5baa108c40bcbf84c30603c900c71e2b1816d14 Mon Sep 17 00:00:00 2001 From: Diane Fleming Date: Thu, 29 Aug 2013 19:46:26 -0500 Subject: [PATCH] Update the dashboard chapter in the Admin User Guide bug: #1218649 Change-Id: I38bd71af696ba75d21ba837d32a6cf6e466db362 author: diane fleming --- .../common/section_dashboard_access.xml | 103 +++--- .../section_dashboard_manage_images.xml | 90 ----- .../src/bk-admin-user-guide.xml | 9 +- .../openstack-user-admin/src/ch_dashboard.xml | 24 +- .../src/section_cinder_cli_manage_volumes.xml | 181 ++++++++++ ...section_dashboard_admin_manage_flavors.xml | 281 +++++++++++++++ .../section_dashboard_admin_manage_images.xml | 148 ++++++++ ...ction_dashboard_admin_manage_instances.xml | 127 +++++++ ..._dashboard_admin_manage_projects_users.xml | 297 ++++++++++++++++ ...ection_dashboard_admin_manage_services.xml | 34 ++ ...section_dashboard_admin_manage_volumes.xml | 123 +++++++ .../section_dashboard_admin_set_quotas.xml | 197 +++++++++++ .../src/section_dashboard_manage_flavors.xml | 10 - .../src/section_dashboard_manage_images.xml | 18 - ...ection_dashboard_manage_projects_users.xml | 319 ------------------ .../src/section_dashboard_set_quotas.xml | 217 ------------ .../openstack-user/src/ch_dashboard.xml | 2 +- .../src/section_dashboard_manage_images.xml | 160 +++++++++ .../section_dashboard_manage_instances.xml | 44 +-- .../src/section_dashboard_manage_volumes.xml | 38 +-- 20 files changed, 1650 insertions(+), 772 deletions(-) delete mode 100644 doc/src/docbkx/common/section_dashboard_manage_images.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_cinder_cli_manage_volumes.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_flavors.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_images.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_instances.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_projects_users.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_services.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_volumes.xml create mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_set_quotas.xml delete mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_flavors.xml delete mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_images.xml delete mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_projects_users.xml delete mode 100644 doc/src/docbkx/openstack-user-admin/src/section_dashboard_set_quotas.xml create mode 100644 doc/src/docbkx/openstack-user/src/section_dashboard_manage_images.xml diff --git a/doc/src/docbkx/common/section_dashboard_access.xml b/doc/src/docbkx/common/section_dashboard_access.xml index c18ae94776..ab5eade57d 100644 --- a/doc/src/docbkx/common/section_dashboard_access.xml +++ b/doc/src/docbkx/common/section_dashboard_access.xml @@ -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"> + Log in to the dashboard - The dashboard is available on the node with the nova-dashboard server role. @@ -38,7 +38,7 @@ In the address bar, type the host name or IP address - that you got from the cloud operator: + for the dashboard: https://IP_ADDRESS_OR_HOSTNAME/ Certificate Warning @@ -73,11 +73,11 @@
OpenStack dashboard—Project tab - 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 Project - tab displays the details of the projects to which you - belong. + Select a project from the CURRENT + PROJECT drop-down list on the left side to + view and manage resources in that project. + The Project tab displays the + details of the selected project. @@ -86,8 +86,7 @@ - Then, access the following categories to perform the - following tasks: + Access the following categories to complete these tasks: Overview @@ -115,38 +114,41 @@ Snapshots 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. + snapshots created project users, plus any + images that are publicly available. Create, + edit, and delete images, and launch instances + from images and snapshots. Access & Security - - - Security Groups - tab. View, create, edit, and delete - security groups and security group - rules. - - - Keypairs tab. - View, create, edit, and import - keypairs, and delete keypairs. - - - Floating IPs - tab. Allocate an IP address to or - release it from a project. - - - API Access tab. - View API endpoints. - - + Use these tabs to complete these + tasks: + + <guilabel>Security Groups</guilabel> + tab + View, create, edit, and delete security + groups and security group rules. + + + <guilabel>Keypairs</guilabel> + tab + View, create, edit, and import keypairs, + and delete keypairs. + + + <guilabel>Floating IPs</guilabel> + tab + Allocate an IP address to or release it + from a project. + + + <guilabel>API Access</guilabel> + tab + View API endpoints. + @@ -165,9 +167,7 @@ - On the Admin tab, access the - following categories to perform the following - tasks: + Access the following categories to complete these tasks: Overview @@ -224,19 +224,20 @@ System Info - - - Services tab. - View services. - - - Default Quotas - tab. View default quota values. Quotas - are hard-coded in OpenStack Compute - and define the maximum allowable size - and number of resources. - - + Access the following tabs to complete these tasks: + + <guilabel>Services</guilabel> + tab + View services. + + + <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. + diff --git a/doc/src/docbkx/common/section_dashboard_manage_images.xml b/doc/src/docbkx/common/section_dashboard_manage_images.xml deleted file mode 100644 index 2de00c4176..0000000000 --- a/doc/src/docbkx/common/section_dashboard_manage_images.xml +++ /dev/null @@ -1,90 +0,0 @@ - -
- Upload images - 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 . For - details about image creation, see the Virtual Machine Image - Guide. - - - Log in to the OpenStack dashboard, choose a project, and - click the Images & Snapshots - category. - - - Click Create Image. The - Create An Image window appears: - - - - - - - - - - In the Create An Image window, enter - or select the following values: - - - - - - Name - Enter a name for the image. - - - Description - Enter a brief description about the - image. - - - Image Location - Include the URL of the image. - - - Image File - Alternatively, browse to find the file on your - machine. - - - Format - Select the image format. - - - Minimum Disk (GB) and - Maximum Disk (GB) - Leave these fields empty. - - - - Public - Select this option to make the image public to - all users. - - - Protected - Select this option to ensure only users with - permissions can delete it. - - - - - - Click Create Image. - The image is queued to be uploaded. It might take some - time before the status changes from queued to active. - - -
diff --git a/doc/src/docbkx/openstack-user-admin/src/bk-admin-user-guide.xml b/doc/src/docbkx/openstack-user-admin/src/bk-admin-user-guide.xml index bf24794d88..a6ed1ee4eb 100644 --- a/doc/src/docbkx/openstack-user-admin/src/bk-admin-user-guide.xml +++ b/doc/src/docbkx/openstack-user-admin/src/bk-admin-user-guide.xml @@ -38,9 +38,9 @@ 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. @@ -49,7 +49,8 @@ - First edition of this document. + First edition of this + document. diff --git a/doc/src/docbkx/openstack-user-admin/src/ch_dashboard.xml b/doc/src/docbkx/openstack-user-admin/src/ch_dashboard.xml index 29dc2356cc..9d82f60857 100644 --- a/doc/src/docbkx/openstack-user-admin/src/ch_dashboard.xml +++ b/doc/src/docbkx/openstack-user-admin/src/ch_dashboard.xml @@ -10,15 +10,27 @@ OpenStack dashboard As a cloud administrative user, the OpenStack dashboard lets - you create and manage projects and users, images, and flavors, - and set quotas. + 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 + OpenStack End User + Guide. - + - + - + - + + + + + + + diff --git a/doc/src/docbkx/openstack-user-admin/src/section_cinder_cli_manage_volumes.xml b/doc/src/docbkx/openstack-user-admin/src/section_cinder_cli_manage_volumes.xml new file mode 100644 index 0000000000..c831d03896 --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_cinder_cli_manage_volumes.xml @@ -0,0 +1,181 @@ + +
+ Manage volumes + 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. + This example creates a volume named + my-new-volume based on an image. +
Create a volume + + List images, and note the ID of the image to use for + your volume: + $ nova image-list + +--------------------------------------+---------------------------------+--------+--------------------------------------+ +| 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 | ++--------------------------------------+---------------------------------+--------+--------------------------------------+ + + + List the availability zones, and note the ID of the + availability zone in which to create your + volume: + $ nova availability-zone-list + +-----------------------+----------------------------------------+ +| 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 | ++-----------------------+----------------------------------------+ + + + Create a volume with 8 GBs of space. Specify the + availability zone and image, as follows: + $ cinder create 8 --display-name my-new-volume --image-id 397e713c-b95b-4186-ad46-6126863ea0a9 --availability-zone nova + +---------------------+--------------------------------------+ +| 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 | ++---------------------+--------------------------------------+ + + + To verify that your volume was created successfully, + list the available volumes: + $ cinder list + +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ +| 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 | | ++--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ + If your volume was created successfully, its status + is available. If its status is + error, you might have + exceeded your quota. + + +
+
Attach a volume to an instance + + Attach your volume to a server: + $ nova volume-attach 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8 /dev/vdb + +----------+--------------------------------------+ +| Property | Value | ++----------+--------------------------------------+ +| device | /dev/vdb | +| serverId | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | +| id | 573e024d-5235-49ce-8332-be1576d323f8 | +| volumeId | 573e024d-5235-49ce-8332-be1576d323f8 | ++----------+--------------------------------------+ + Note the ID of your volume. + + + Show information for your volume: + $ cinder show 573e024d-5235-49ce-8332-be1576d323f8 + +------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 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 | ++------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + The output shows that the volume is attached to the + server with ID + 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5, + is in the nova availability zone, and is + bootable. + +
+
Delete a volume + + + To delete your volume, you must first detach it from + the server. + To detach the volume from your server, pass the + server ID and volume ID to the command, as + follows: + $ nova volume-detach 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8 + The volume-detach command does + not return any output. + + + List volumes: + $ cinder list + +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ +| 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 | | ++--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ + Note that the volume is now available. + + + Now you can delete the volume, as follows: + $ cinder delete my-new-volume + The delete command does not return any + output. + + + List the volumes again, and note that the status of + your volume is deleting: + $ cinder list + +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ +| 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 | | ++--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ + When the volume is fully deleted, it disappears from + the list of volumes: + $ cinder list + +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ +| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | ++--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ +| bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol | 8 | None | true | | ++--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+ + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_flavors.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_flavors.xml new file mode 100644 index 0000000000..d370d74687 --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_flavors.xml @@ -0,0 +1,281 @@ + +
+ + Manage flavors + 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. + Only administrative users can create and manage + flavors. + A flavor consists of the following parameters: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Flavor parameters
ParameterDescription
+ Flavor Name + + The flavor name. +
+ VCPUs + + Number of virtual CPUs to use. +
+ RAM + + Amount of RAM to use, in megabytes. +
+ Root Disk + + Amount of disk space (in gigabytes) to use + for the root (/) partition. +
+ Ephemeral Disk + + Amount of disk space (in gigabytes) to use + for the ephemeral partition. If unspecified, + the value is 0 by default. + 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. +
+ Swap Disk + + Amount of swap space (in megabytes) to use. + If unspecified, the default is 0. +
+ ID + + The flavor ID, generated by + OpenStack. +
+ The default flavors are: + + Default Flavors + + m1.nano (1 VCPU/0 GB Disk/64 MB RAM) + + + m1.micro (1 VCPU/0 GB Disk/128 MB RAM) + + + m1.tiny (1 VCPU/0 GB Disk/512 MB RAM) + + + m1.small (1 VCPU/20 GB Disk/2048 MB RAM) + + + m1.medium (2 VCPU/40 GB Disk/4096 MB RAM) + + + m1.large (4 VCPU/80 GB Disk/8192 MB RAM) + + + m1.xlarge (8 VCPU/160 GB Disk/16384 MB RAM) + + +
+ Create flavors + + + Log in to the OpenStack dashboard. + Choose the admin project + from the CURRENT PROJECT + drop-down list. + + + On the Admin tab, click the + Flavors category. + + + Click Create + Flavor. + + + In the Create Flavor + window, enter or select the following + values: + + + + + + + Name + + + Enter the flavor name. + + + + + VCPUs + + + Enter the number of virtual CPUs + to use. + + + + + RAM + MB + + + Enter the amount of RAM to use, + in megabytes. + + + + + Root Disk + GB + + + Enter the mount of disk space in + gigabytes to use for the root (/) + partition. + + + + + Ephemeral Disk + GB + + + Enter the amount of disk space + in gigabytes to use for the + ephemeral partition. If + unspecified, the value is 0 by + default. + 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. + + + + + Swap Disk + GB + + + Enter the amount of swap space + (in megabytes) to use. If + unspecified, the default is 0. + + + + + + + + Click Create + Flavor. + + +
+
+ Update flavors + + + Log in to the OpenStack dashboard. + Choose the admin project + from the CURRENT PROJECT + drop-down list. + + + On the Admin tab, click the + Flavors category. + + + Select the flavor that you want to edit. Click + Edit Flavor. + + + In the Edit Flavor window, + you can change the flavor name, VCPUs, RAM, root + dish, ephemeral disk, and swap disk + values.. + + + Click Save. + + +
+
+ Delete flavors + + + Log in to the OpenStack dashboard. + Choose the admin project + from the CURRENT PROJECT + drop-down list. + + + On the Admin tab, click the + Flavors category. + + + Select the flavors that you want to + delete. + + + Click Delete + Flavors. + + + In the Confirm Delete + Flavors window, click + Delete Flavors to + confirm the deletion. You cannot undo this + action. + + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_images.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_images.xml new file mode 100644 index 0000000000..6118239b9b --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_images.xml @@ -0,0 +1,148 @@ + +
+ + Create and manage images + 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. + To create and manage images in specified projects as an end + user, see the OpenStack End User + Guide. + To create and manage images as an administrator for other + users, use the following procedures. +
+ Create images + For details about image creation, see the Virtual Machine Image + Guide. + + + Log in to the OpenStack dashboard. + Choose the admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Images category. The images that you + can administer for cloud users appear on this page. + + + Click Create Image. + + + In the Create An Image window, + enter or select the following values: + + + + + + Name + Enter a name for the image. + + + Description + Enter a brief description about the + image. + + + Image + Location + Include the URL of the image. + + + Image File + Alternatively, browse to find the image file + on your machine. + + + Format + Select the image format. + + + Minimum Disk (GB) and + Maximum Disk (GB) + Leave these fields empty. + + + + Public + Select this option to make the image public to + all users. + + + + + + Click Create Image. + The image is queued to be uploaded. It might take some + time before the status changes from queued to active. + + +
+
+ Update images + + + Log in to the OpenStack dashboard. + Choose the admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Images category. + + + Select the image that you want to edit. Click + Edit. + + + In the Update Image window, you can + change the name for the image. Select the + Public 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. + + + Click Update Image. + + +
+
+ Delete images + + + Log in to the OpenStack dashboard. + Choose the admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Images category. + + + Select the images that you want to delete. + + + Click Delete Images. + + + In the Confirm Delete Image window, + click Delete Images to confirm the + deletion. + You cannot undo this action. + + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_instances.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_instances.xml new file mode 100644 index 0000000000..e013b725c8 --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_instances.xml @@ -0,0 +1,127 @@ + +
+ + Manage instances + 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. + For information about using the dashboard to launch + instances as an end user, see the OpenStack End User + Guide. +
+ Create instance snapshots + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Instances + category. + + + Select an instance to create a snapshot from it. + From the Actions drop-down + list, select Create + Snapshot. + + + In the Create Snapshot + window, enter a name for the snapshot. Click + Create Snapshot. The + dashboard shows the instance snapshot in the + Images & Snapshots + category. + + + To launch an instance from the snapshot, select + the snapshot and click + Launch. For information + about launching instances, see the OpenStack End User + Guide. + + +
+
+ Control the state of an instance + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Instances + category. + + + Select the instance for which you want to change + the state. + + + In the More drop-down list + in the Actions column, select + the state. + 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.
+ OpenStack dashboard: Actions + + + + + +
+ + + +
+
+ Track usage + Use the Overview category to track + usage of instances for each project. + You can track costs per month by showing metrics like + number of VCPUs, disks, RAM, and uptime of all your + instances. + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Instances + category. + + + Select a month and click + Submit to query the + instance usage for that month. + + + Click Download CSV + Summary to download a CSV + summary. + + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_projects_users.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_projects_users.xml new file mode 100644 index 0000000000..0f58cc7309 --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_projects_users.xml @@ -0,0 +1,297 @@ + +
+ + Manage projects and users + 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 tenants or accounts.You can manage projects + and users independently from each other. + Users are members of one or more projects. + 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. + 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 . + 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. +
+ Consequences of disabling projects and users + When you disable a project, it has the following + consequences: + + + In the dashboard, users can no longer access the + project from the CURRENT + PROJECT drop-down list on the + Project tab. + + + Users who are members of only the disabled + project can no longer log in. + + + You cannot launch instances for a disabled + project. Instances that are already running are + not automatically terminated though—you must stop + them manually. + + + The data for a disabled project is maintained so + that you can enable the project again at any + time. + + + 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. +
+
+ Create a project + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Projects category. + + + Click Create + Project. + + + On the Project Info tab in + the Create Project window, + enter a name and description for the project. By + default, the project is enabled. See . + + + On the Project Members tab, + add members to the project. + + + On the Quota tab, edit + quota values. For information about quotas, see + . + + + Click Create + Project. + The Projects category shows + the project, including its assigned ID. + + +
+
+ Update a project + You can update a project to change its name or + description, and enable or temporarily disable it. + + + On the Admin tab, click the + Projects category. + + + Select the project that you want to update. + + + + In the More drop-down list, + click Edit Project. + + + In the Edit Project window, + you can update a project to change its name or + description, and enable or temporarily disable + it. + By default, the project is enabled. To + temporarily disable it, clear the + Enabled check box. To + enable a disabled project, select the + Enabled check box. + + + Click Save. + + +
+
+ Modify user assignments for a project + When you create users, you must assign them to a primary + project as described in . You can assign + users to additional projects or update and remove + assignments. + + + On the Admin tab, select + the Projects category. + + + Select a project to modify its user + assignments. + + + Select Modify + Users. + The Edit Project window + shows the following lists of users: + + + All Users. Users + that are available to be assigned to the + current project. + + + Project Members. + Users that are assigned to the current + project, + + + + + + + + + + To assign a user to the current project, click + + for the user. + The user moves from the All + Users list to the Project + Members list. + + + To remove a user from the current project, click + the - button for the + user. + The user moves from the Project + Members list to the All + Users list. + + + Click Save. + + +
+
+ Delete projects + + + On the Admin tab, click the + Projects category. + + + Select the projects that you want to delete. + + + + Click Delete Projects to + confirm the deletion. + + You cannot undo the delete action. + + + +
+
+ Create a user account + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, select + the Users category. + + + Click Create User. + + + In the Create User window, + enter a user name, email, and preliminary password + for the user. Confirm the password. + Select a project from the Primary + Project drop-down list. + Choose a role for the user from the + Role drop-down list. + Default is Member. + + + Click Create User to + confirm your changes. + Respond to the prompt to remember the password + for the user. + The dashboard assigns an ID to the user, and the + user appears in the Users + category. + + +
+
+ Disable or enable a user + + + On the Admin tab, select + the Users category. + + + Select the user that you want to disable or + enable. You can disable or enable only one user at + a time. + + + In the Actions drop-down + list, select Disable User or + Enable User. + In the Enabled column, the + enabled value updates to either + True or + False. + + +
+
+ Delete users + + + On the Admin tab, select + the Users category. + + + Select the users that you want to delete. + + + Click Delete Users. + + + In the Confirm Delete Users + window, click Delete Users + to confirm the deletion. + + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_services.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_services.xml new file mode 100644 index 0000000000..9725c8eda4 --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_services.xml @@ -0,0 +1,34 @@ + + + + + + +]> +
+ View services information + As an administrative user, you can view information for + OpenStack services. + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down list. + + + On the Admin tab, click the + System Info category. + + + Click the Services tab to view + services information. + 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. + + +
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_volumes.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_volumes.xml new file mode 100644 index 0000000000..5fe003c077 --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_manage_volumes.xml @@ -0,0 +1,123 @@ + + + + + + +]> +
+ + Manage volumes and volume types + 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 OpenStack End User + Guide. + 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. +
+ Create a volume type + + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Volumes category. + + + Click Create Volume + Type. + In the Create Volume Type + window, enter a name for the volume type. + + + Click Create Volume Type + to confirm your changes. + + +
+
+ Delete volume types + When you delete a volume type, volumes of that type are + not deleted. + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Volumes category. + + + Select the volume type or types that you want to + delete. + + + Click Delete Volume + Types. + + + In the Confirm Delete Volume + Types window, click + Delete Volume Types to + confirm the action. + + + A message indicates whether the action + succeeded. + + +
+
+ Delete volumes + When you delete an instance, the data of its attached + volumes is not destroyed. + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + Volumes category. + + + Select the volume or volumes that you want to + delete. + + + Click Delete + Volumes. + + + In the Confirm Delete + Volumes window, click + Delete Volumes to + confirm the action. + + + A message indicates whether the action + succeeded. + + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_set_quotas.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_set_quotas.xml new file mode 100644 index 0000000000..27ce31eaed --- /dev/null +++ b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_admin_set_quotas.xml @@ -0,0 +1,197 @@ + + + + + + +]> +
+ + View and manage quotas + As an administrative user, you can set quotas when you 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. + Typically, you change quotas when a project needs more than 10 + volumes or 1 TB on a Compute node. + The following tables describe the Compute and Block Storage + service quotas: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Compute quotas
QuotaDefines the number of
+ Metadata Items + + Metadata items allowed for each instance. +
+ VCPUs + + Instance cores allowed for each project. +
+ Instances + + Instances allowed for each project. +
+ Injected Files + + Injected files allowed for each project. +
+ Injected File Content Bytes + + Content bytes allowed for each injected file. +
+ RAM (MB) + + RAM megabytes allowed for each instance. +
+ Floating IPs + + Floating IP addresses allowed for each project. +
+ Fixed IPs + + Fixed IP addresses allowed for each project. Must be + equal to or greater than the number of allowed + instances. +
+ Security Groups + + Security groups allowed for each project. +
+ Security Group Rules + + Rules allowed for each security group. +
+ + + + + + + + + + + + + + + + + + + + +
Block Storage quotas
QuotaDefines the number of
+ Volumes + + Volumes allowed for each project. +
+ Gigabytes + + Volume gigabytes allowed for each project. +
+
+ View default project quotas + + + Log in to the OpenStack dashboard and choose the + admin project from the + CURRENT PROJECT drop-down + list. + + + On the Admin tab, click the + System Info category. + + + Click the Default Quotas tab to + view the default quotas for the Compute and Block Storage + services. + + +
+
+ Update project quotas + + + On the Admin tab, click the + Projects category. + + + Select a project to change its quota values. + + + In the More drop-down list, click + Modify Quotas. + + + On the Quota tab in the + Edit Project window, edit quota + values. Then, click Save. + + + + 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 . + +
+
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_flavors.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_flavors.xml deleted file mode 100644 index 736f836922..0000000000 --- a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_flavors.xml +++ /dev/null @@ -1,10 +0,0 @@ - -
- Manage flavors - - -
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_images.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_images.xml deleted file mode 100644 index a6f9fe4a85..0000000000 --- a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_images.xml +++ /dev/null @@ -1,18 +0,0 @@ - -
- Manage images - 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 . - For details about image creation, see the Virtual Machine Image - Guide. -
\ No newline at end of file diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_projects_users.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_projects_users.xml deleted file mode 100644 index a26f096b2f..0000000000 --- a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_manage_projects_users.xml +++ /dev/null @@ -1,319 +0,0 @@ - -
- Projects and users - - In an OpenStack cloud, you can manage projects and users - independently from each other. - Projects represent different organizational units in the - cloud to which you can assign users. - Cloud admin users perform both project and user management - tasks. - 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. - As an admin user, you can create additional projects and - users as needed. - 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. -
- Create and manage projects - You can create, temporarily disable, enable, and delete - projects. -
- Create a project - - - Log in to the OpenStack dashboard. - - - In the CURRENT PROJECT - drop-down list on the - Project tab, select - the admin project. - - - On the Admin tab, click - the Projects - category. - - - Click Create - Project. - - - In the Create Project - window, enter a name and description for the - project. By default, the project is enabled. - See . Click - Create - Project. - The dashboard assigns an ID and shows the - project in the Projects - category. - - -
-
- Update a project - - - You can update a project to change its name or - description, and to enable or temporarily disable - it. - Disabling a project has the following - consequences: - - Consequences of disabling a project - - In the dashboard, the project can no - longer be accessed from the - CURRENT PROJECT - drop-down list on the - Project - tab. - - - Users that are only members of the - disabled project can no longer log - in. - - - It is impossible to launch new instances - for a disabled project. Instances already - running are not automatically terminated - though—you must stop them manually. - - - All data for a disabled project is kept - so that you can enable the project again - at any time. - - - - Select the project that you want to update. - - - - From the More drop-down - list, click Edit - Project. - - - Optionally, change the following attributes - for the project: - - Name. - - - Description. - - - To disable the project, clear - the Enabled - check box. - To enable the project, select - the Enabled - check box. - - - - - Click Save. - - -
-
- Delete one or more projects - - - Select the projects that you want to delete. - - - - Click Delete Projects - and confirm your choice in the pop-up that - appears. - - You cannot undo the delete - action. - - - -
-
-
- Create and manage user accounts - Users are members of one or multiple projects. - You can add, update, and delete users. To enable or - temporarily disable a user, update that user. - When you create a user account, you must assign the - account to a primary project. Optionally, you can assign - the account to additional projects. - 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. - Before you can delete a user account, you must remove - the user account from its primary project. -
- Create a user account - - - Log in to the OpenStack dashboard. - - - In the CURRENT PROJECT - drop-down list on the - Project tab, select - the admin project. - - - Click the Users - category. - - - On the Admin tab, - select the Users - category. - - - - Click Create - User. - - - In the Create User - window, enter a user name, email, and - preliminary password for the user. - Select a project from the Primary - Project drop-down list. - Choose a role for the user from the - Role drop-down list. - Default is Member. - - - Click Create User to - confirm your changes. - The dashboard assigns an ID and shows the - user account in the Users - category. - - -
-
- Disable or delete user accounts - - - - To temporarily deactivate a user account, - select the user, and from the Actions - drop-down list, select Disable. - - - To delete one or more users accounts, - activate the check boxes in front of the user - accounts that you want to delete. - - - Click Delete Users and confirm your choice - in the pop-up that appears. - A message on the Web page shows if the - action has been successful. - NOTE: Remove User - from Primary Project - If a user account cannot be deleted, it is - because it is still assigned to its primary - project. - - - To delete a user from a project, edit the - user data to view to which Primary Project the - user is assigned. - - - Remove the user from his primary project as - described in Modifying User Assignments for a - Project, to . - - -
-
- Modify user assignments for a project - When creating new users, you must assign them to a - primary project as described in Creating Or Deleting Users Accounts. To - assign users to additional projects or to modify and - remove assignments, proceed as follows: - - To modify user assignments for a - project - - On the Admin tab, select the Projects - category. - - - Select the project for which to modify user - assignments. - - - From the Actions drop-down list for the - project, select Modify Users. - The Dashboard shows two lists of users: - Project Members shows - the users assigned to the current project, - All Users shows other - existing users, which can be assigned to the - current project. - - - - - - - - To remove a user from the current project, - click the - button - associated with the entry for the user. - - - - To assign a user to the current project - - Click the + button - associated with the entry for the user. - - - 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 http://docs.openstack.org/essex/openstack-compute/install/content/keystone-concepts.html. - - - -
-
-
diff --git a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_set_quotas.xml b/doc/src/docbkx/openstack-user-admin/src/section_dashboard_set_quotas.xml deleted file mode 100644 index 2426c2baac..0000000000 --- a/doc/src/docbkx/openstack-user-admin/src/section_dashboard_set_quotas.xml +++ /dev/null @@ -1,217 +0,0 @@ - - - - - - -]> -
- Set quotas - - 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. - Typically, you change default values because a project requires - more than 10 volumes, or more than 1 TB on a Compute node. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Compute and Block Storage quotas
QuotaDescriptionService
- Metadata Items - - Number of metadata items allowed per instance. - - Compute -
- VCPUs - - Number of instance cores allowed per tenant. - - Compute -
- Instances - - Number of instances allowed per tenant. - - Compute -
- Injected Files - - Number of injected files allowed per tenant. - - Compute -
- Injected File Content Bytes - - Number of content bytes allowed per injected file. - - Compute -
- Volumes - - Number of volumes allowed per tenant. - - Block Storage -
- Gigabytes - - Number of volume gigabtyes allowed per tenant. - - Block Storage -
- RAM (MB) - - Megabytes of ram allowed per instance. - - Compute -
- Floating IPs - - Number of floating IP addresses allowed per tenant. - - Compute -
- Fixed IPs - - Number of fixed IP addresses allowed per tenant. - This number must be equal to or greater than the number - of allowed instances. - - Compute -
- Security Groups - - Number of security groups allowed per tenant. - - Compute -
- Security Group Rules - - Number of rules per security group. - - Compute -
- -
- Project quotas - As an administrative user in the dashboard, you can set - quotas when you or update quotas for an - existing project. - - To view default quotas - - On the Admin tab in the navigation - sidebar, click the System Info - category. - - - Click the Default Quotas tab in the - main page. - - - - To update project quotas - - On the Admin tab in the navigation - sidebar, click the Projects category. - - - Select the project for which to change quota values. - - - From the More drop-down list, click - Modify Quotas. - - - On the Quota tab in the - Edit Project window, edit quota - values. Then, click Save. - - - - 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 . - -
-
\ No newline at end of file diff --git a/doc/src/docbkx/openstack-user/src/ch_dashboard.xml b/doc/src/docbkx/openstack-user/src/ch_dashboard.xml index 6ed0ba9640..7096904fd8 100644 --- a/doc/src/docbkx/openstack-user/src/ch_dashboard.xml +++ b/doc/src/docbkx/openstack-user/src/ch_dashboard.xml @@ -17,7 +17,7 @@ + href="section_dashboard_manage_images.xml"/> diff --git a/doc/src/docbkx/openstack-user/src/section_dashboard_manage_images.xml b/doc/src/docbkx/openstack-user/src/section_dashboard_manage_images.xml new file mode 100644 index 0000000000..ba1ea96d7b --- /dev/null +++ b/doc/src/docbkx/openstack-user/src/section_dashboard_manage_images.xml @@ -0,0 +1,160 @@ + +
+ Create and manage images + 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 . +
+ Create images + For details about image creation, see the Virtual Machine Image + Guide. + + + Log in to the OpenStack dashboard. + Choose the admin project from the + CURRENT PROJECT drop-down + list. + + + On the Project tab, click the + Images & Snapshots + category. + + + Click Create Image. The + Create An Image window + appears: + + + + + + + + + + In the Create An Image window, + enter or select the following values: + + + + + + Name + Enter a name for the image. + + + Description + Enter a brief description about the + image. + + + Image + Location + Include the URL of the image. + + + Image File + Alternatively, browse to find the file on your + machine. + + + Format + Select the image format. + + + Minimum Disk (GB) and + Maximum Disk (GB) + Leave these fields empty. + + + + Public + Select this option to make the image public to + all users. + + + Protected + Select this option to ensure that only users + with permissions can delete it. + + + + + + Click Create Image. + The image is queued to be uploaded. It might take some + time before the status changes from queued to active. + + +
+
+ Update images + + + Log in to the OpenStack dashboard. + Choose the admin project from the + CURRENT PROJECT drop-down + list. + + + On the Project tab, click the + Images & Snapshots + category. + + + Select the image that you want to edit. In the + More drop-down list, click + Edit. + + + In the Update Image window, you can + change the name for the image. Select the + Public check box to make the image + public. Clear this check box to make the image + private. + + + Click Update Image. + + +
+
+ Delete images + + + Log in to the OpenStack dashboard. + Choose the admin project from the + CURRENT PROJECT drop-down + list. + + + On the Project tab, click the + Images & Snapshots + category. + + + Select the images that you want to delete. + + + Click Delete Images. + + + In the Confirm Delete Image window, + click Delete Images to confirm the + deletion. You cannot undo this action. + + +
+
diff --git a/doc/src/docbkx/openstack-user/src/section_dashboard_manage_instances.xml b/doc/src/docbkx/openstack-user/src/section_dashboard_manage_instances.xml index 34745a42ea..b3e757186b 100644 --- a/doc/src/docbkx/openstack-user/src/section_dashboard_manage_instances.xml +++ b/doc/src/docbkx/openstack-user/src/section_dashboard_manage_instances.xml @@ -1,25 +1,17 @@
- Create instance snapshots + Manage instances
Create instance snapshots - To create instance snapshots - Log in to the OpenStack dashboard. - - - If you are a member of multiple projects, select - a project from the drop-down list at the top of - the Project tab. - - - Click the Instances + Log in to the OpenStack dashboard, choose a + project, and click the + Instances category. The dashboard lists the instances that are available for this project. @@ -51,17 +43,10 @@
Control the state of an instance - To control the state of an instance - Log in to the OpenStack dashboard. - - - If you are a member of multiple projects, select - a project from the drop-down list at the top of - the Project tab. - - - Click the Instances + Log in to the OpenStack dashboard, choose a + project, and click the + Instances category. The dashboard lists the instances that are available for this project. @@ -93,21 +78,12 @@
Track usage - Use the dashboard's Overview - category to track usage of instances for each + You can track usage of instances for each project. - - - - - You can track costs per month by showing metrics like number of VCPUs, disks, RAM, and uptime of all your instances. - To track usage If you are a member of multiple projects, select a project from the drop-down list at the top of @@ -120,7 +96,7 @@ Click Download CSV - Summary to download a CVS + Summary to download a CSV summary. diff --git a/doc/src/docbkx/openstack-user/src/section_dashboard_manage_volumes.xml b/doc/src/docbkx/openstack-user/src/section_dashboard_manage_volumes.xml index 75ff4bfb63..8814d77f1a 100644 --- a/doc/src/docbkx/openstack-user/src/section_dashboard_manage_volumes.xml +++ b/doc/src/docbkx/openstack-user/src/section_dashboard_manage_volumes.xml @@ -12,10 +12,12 @@ xml:id="dashboard_manage_volumes"> Manage volumes - 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. + 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.
Create a volume @@ -29,12 +31,13 @@ Click Create Volume. - In the window that opens, enter a name to assign - to a volume, a description (optional), and define - the size in GBs. + In the window that opens, enter a name, an + optional description, and the size in GBs for the + volume. - Confirm your changes. + Click Create Volume to + confirm your changes. The dashboard shows the volume in the @@ -112,25 +115,16 @@
- +
Delete volumes When you delete an instance, the data of its attached