Setting up Administrator Guide Dashboard Chapter
Introducing Admin User Guide dashboard content to
the Cloud Admin Guide as a part of the reorganisation
goal. This patch is the first step in creating a new
Dashboard section for Admin Users in the Cloud Admin Guide,
as disucssed in the User Guide Specialty team meetings.
1.) Moving:
dashboard_manage_host_aggregates.rst
dashboard_manage_flavors.rst
dashboard_admin_manage_stacks.rst
dashboard_manage_instances.rst
dashboard_manage_images.rst
shared_file_systems_manage_shares_dashboard.rst
2). Remove the Images and Instances content from the compute-images-instances.rst
3.) Move the Shared file system dashboard content out of
shared_file_system.rst, and into the Dashboard.rst chapter.
Change-Id: I1e3c122e58349853b61be4ba514e469da407c1c9
Implements: blueprint user-guides-reorganised
This commit is contained in:
Joseph Robinson
parent
134cce6475
commit
5fc76a1af1
@ -121,136 +121,6 @@ process.
|
|||||||
|
|
||||||
|
|
|
|
||||||
|
|
||||||
Manage instances
|
|
||||||
~~~~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
Administrative users can manage instances for users in various projects. As
|
|
||||||
an administrative user, you can view, terminate, edit, perform, or migrate
|
|
||||||
an instance. You can perform a soft or hard reboot if needed. You can also
|
|
||||||
view instance logs, 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
|
|
||||||
<http://docs.openstack.org/user-guide/dashboard_launch_instances.html>`__.
|
|
||||||
|
|
||||||
Create instance snapshots
|
|
||||||
-------------------------
|
|
||||||
|
|
||||||
#. Log in to the Dashboard and choose the admin project from the
|
|
||||||
drop-down list at the top of the page.
|
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
|
||||||
and click the :guilabel:`Instances` category.
|
|
||||||
|
|
||||||
#. Select an instance to create a snapshot from it. From the
|
|
||||||
:guilabel:`Actions` drop-down list, select :guilabel:`Create Snapshot`.
|
|
||||||
|
|
||||||
#. In the :guilabel:`Create Snapshot` window, enter a name for the snapshot.
|
|
||||||
|
|
||||||
#. Click :guilabel:`Create Snapshot`. The Dashboard shows the instance snapshot
|
|
||||||
in the :guilabel:`Images` category.
|
|
||||||
|
|
||||||
#. To launch an instance from the snapshot, select the snapshot and
|
|
||||||
click :guilabel:`Launch Instance`. For information about launching
|
|
||||||
instances, see the
|
|
||||||
`OpenStack End User Guide
|
|
||||||
<http://docs.openstack.org/user-guide/dashboard_launch_instances.html>`__.
|
|
||||||
|
|
||||||
Control the state of an instance
|
|
||||||
--------------------------------
|
|
||||||
|
|
||||||
#. Log in to the Dashboard and choose the admin project from the
|
|
||||||
drop-down list at the top of the page.
|
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
|
||||||
and click the :guilabel:`Instances` category.
|
|
||||||
|
|
||||||
#. Select the instance for which you want to change the state.
|
|
||||||
|
|
||||||
#. From the drop-down list in the :guilabel:`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 (actions in red color are dangerous).
|
|
||||||
|
|
||||||
Track usage
|
|
||||||
-----------
|
|
||||||
|
|
||||||
Use the :guilabel:`Overview` category to track usage of instances
|
|
||||||
for each project.
|
|
||||||
|
|
||||||
You can track costs per month by showing meters like number of VCPUs,
|
|
||||||
disks, RAM, and uptime of all your instances.
|
|
||||||
|
|
||||||
#. Log in to the Dashboard and choose the admin project from the
|
|
||||||
drop-down list at the top of the page.
|
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, click the :guilabel:`Instances` category.
|
|
||||||
|
|
||||||
#. Select a month and click :guilabel:`Submit` to query the instance usage for
|
|
||||||
that month.
|
|
||||||
|
|
||||||
#. Click :guilabel:`Download CSV Summary` to download a CSV summary.
|
|
||||||
|
|
||||||
Image management
|
|
||||||
~~~~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
The OpenStack Image service discovers, registers, and retrieves virtual
|
|
||||||
machine images. The service also includes a RESTful API that allows you
|
|
||||||
to query VM image metadata and retrieve the actual image with HTTP
|
|
||||||
requests. For more information about the API, see the `OpenStack API
|
|
||||||
Complete Reference <http://developer.openstack.org/api-ref.html>`__ and
|
|
||||||
the `Python
|
|
||||||
API <http://docs.openstack.org/developer/python-glanceclient/>`__.
|
|
||||||
|
|
||||||
The OpenStack Image service can be controlled using a command-line tool.
|
|
||||||
For more information about using the OpenStack Image command-line tool,
|
|
||||||
see the `Manage
|
|
||||||
Images <http://docs.openstack.org/user-guide/common/cli_manage_images.html>`__
|
|
||||||
section in the OpenStack End User Guide.
|
|
||||||
|
|
||||||
You can store virtual images made available through the Image service
|
|
||||||
in a variety of ways. In order to use these services, you
|
|
||||||
must have a working installation of the Image service, with a working
|
|
||||||
endpoint, and users that have been created in OpenStack Identity.
|
|
||||||
Additionally, you must meet the environment variables required by the
|
|
||||||
Compute and Image service clients.
|
|
||||||
|
|
||||||
The Image service supports these back-end stores:
|
|
||||||
|
|
||||||
File system
|
|
||||||
The OpenStack Image service stores virtual machine images in the
|
|
||||||
file system back end by default. This simple back end writes image
|
|
||||||
files to the local file system.
|
|
||||||
|
|
||||||
Object Storage
|
|
||||||
The OpenStack highly available service for storing objects.
|
|
||||||
|
|
||||||
Block Storage
|
|
||||||
The OpenStack highly available service for storing blocks.
|
|
||||||
|
|
||||||
VMware
|
|
||||||
ESX/ESXi or vCenter Server target system.
|
|
||||||
|
|
||||||
S3
|
|
||||||
The Amazon S3 service.
|
|
||||||
|
|
||||||
HTTP
|
|
||||||
OpenStack Image service can read virtual machine images that are
|
|
||||||
available on the Internet using HTTP. This store is read only.
|
|
||||||
|
|
||||||
RADOS Block Device (RBD)
|
|
||||||
Stores images inside of a Ceph storage cluster using Ceph's RBD
|
|
||||||
interface.
|
|
||||||
|
|
||||||
Sheepdog
|
|
||||||
A distributed storage system for QEMU/KVM.
|
|
||||||
|
|
||||||
GridFS
|
|
||||||
Stores images using MongoDB. This store driver will be removed in Mitaka.
|
|
||||||
|
|
||||||
|
|
||||||
Image properties and property protection
|
Image properties and property protection
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
@ -554,126 +424,6 @@ Administrative users can specify which compute node their instances
|
|||||||
run on. To do this, specify the ``--availability-zone
|
run on. To do this, specify the ``--availability-zone
|
||||||
AVAILABILITY_ZONE:COMPUTE_HOST`` parameter.
|
AVAILABILITY_ZONE:COMPUTE_HOST`` parameter.
|
||||||
|
|
||||||
Create and manage images
|
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
Administrative users can create and manage images for the projects to
|
|
||||||
which you belong. You can create and manage images for users in all
|
|
||||||
projects to which you have administative access.
|
|
||||||
|
|
||||||
To create and manage images in specified projects as an end
|
|
||||||
user, see the `OpenStack End User Guide
|
|
||||||
<http://docs.openstack.org/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 <http://docs.openstack.org/image-guide/>`_.
|
|
||||||
|
|
||||||
#. Log in to the dashboard.
|
|
||||||
|
|
||||||
Choose the :guilabel:`admin` project from the drop-down list
|
|
||||||
at the top of the page.
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
|
||||||
and click the :guilabel:`Images` category. The images that you
|
|
||||||
can administer for cloud users appear on this page.
|
|
||||||
#. Click :guilabel:`Create Image`, which opens the
|
|
||||||
:guilabel:`Create An Image` window.
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
||||||
.. _Figure Dashboard — Create images:
|
|
||||||
|
|
||||||
**Create images**
|
|
||||||
|
|
||||||
.. figure:: figures/create_image.png
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
||||||
#. In the :guilabel:`Create An Image` window, enter or select the
|
|
||||||
following values:
|
|
||||||
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Name` | Enter a name for the image. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Description` | Enter a brief description of |
|
|
||||||
| | the image. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Image Source` | Choose the image source from |
|
|
||||||
| | the dropdown list. Your choices |
|
|
||||||
| | are :guilabel:`Image Location` |
|
|
||||||
| | and :guilabel:`Image File`. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Image File` or | Based on your selection, there |
|
|
||||||
| :guilabel:`Image Location` | is an :guilabel:`Image File` or |
|
|
||||||
| | :guilabel:`Image Location` |
|
|
||||||
| | field. You can include the |
|
|
||||||
| | location URL or browse for the |
|
|
||||||
| | image file on your file system |
|
|
||||||
| | and add it. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Format` | Select the image format. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Architecture` | Specify the architecture. For |
|
|
||||||
| | example, ``i386`` for a 32-bit |
|
|
||||||
| | architecture or ``x86_64`` for |
|
|
||||||
| | a 64-bit architecture. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Minimum Disk (GB)` | Leave this field empty. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Minimum RAM (MB)` | Leave this field empty. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Copy Data` | Specify this option to copy |
|
|
||||||
| | image data to the Image service.|
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Public` | Select this option to make the |
|
|
||||||
| | image public to all users. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
| :guilabel:`Protected` | Select this option to ensure |
|
|
||||||
| | that only users with |
|
|
||||||
| | permissions can delete it. |
|
|
||||||
+-------------------------------+---------------------------------+
|
|
||||||
|
|
||||||
#. Click :guilabel:`Create Image`.
|
|
||||||
|
|
||||||
The image is queued to be uploaded. It might take several minutes
|
|
||||||
before the status changes from ``Queued`` to ``Active``.
|
|
||||||
|
|
||||||
Update images
|
|
||||||
-------------
|
|
||||||
|
|
||||||
#. Log in to the Dashboard.
|
|
||||||
Choose the :guilabel:`admin` project from the drop-down list
|
|
||||||
at the top of the page.
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
|
||||||
and click the :guilabel:`Images` category.
|
|
||||||
#. Select the images that you want to edit. Click :guilabel:`Edit Image`.
|
|
||||||
#. In the :guilabel:`Update Image` window, you can change the image name.
|
|
||||||
|
|
||||||
Select the :guilabel:`Public` check box to make the image public.
|
|
||||||
Clear this check box to make the image private. You cannot change
|
|
||||||
the :guilabel:`Kernel ID`, :guilabel:`Ramdisk ID`, or
|
|
||||||
:guilabel:`Architecture` attributes for an image.
|
|
||||||
#. Click :guilabel:`Update Image`.
|
|
||||||
|
|
||||||
Delete images
|
|
||||||
-------------
|
|
||||||
|
|
||||||
#. Log in to the Dashboard.
|
|
||||||
Choose the :guilabel:`admin` project from the drop-down list
|
|
||||||
at the top of the page.
|
|
||||||
#. On the :guilabel:`Admin tab`, open the :guilabel:`System` tab
|
|
||||||
and click the :guilabel:`Images` category.
|
|
||||||
#. Select the images that you want to delete.
|
|
||||||
#. Click :guilabel:`Delete Images`.
|
|
||||||
#. In the :guilabel:`Confirm Delete Images` window, click :guilabel:`Delete
|
|
||||||
Images` to confirm the deletion.
|
|
||||||
|
|
||||||
You cannot undo this action.
|
|
||||||
|
|
||||||
Launch instances with UEFI
|
Launch instances with UEFI
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|||||||
@ -2,11 +2,11 @@
|
|||||||
Dashboard
|
Dashboard
|
||||||
=========
|
=========
|
||||||
|
|
||||||
The OpenStack dashboard is a web-based interface that allows you to
|
The OpenStack Dashboard is a web-based interface that allows you to
|
||||||
manage OpenStack resources and services. The dashboard allows you to
|
manage OpenStack resources and services. The Dashboard allows you to
|
||||||
interact with the OpenStack Compute cloud controller using the OpenStack
|
interact with the OpenStack Compute cloud controller using the OpenStack
|
||||||
APIs. For more information about installing and configuring the
|
APIs. For more information about installing and configuring the
|
||||||
dashboard, see the `OpenStack Installation Guide
|
Dashboard, see the `OpenStack Installation Guide
|
||||||
<http://docs.openstack.org/index.html#install-guides>`__
|
<http://docs.openstack.org/index.html#install-guides>`__
|
||||||
for your operating system.
|
for your operating system.
|
||||||
|
|
||||||
@ -15,9 +15,28 @@ for your operating system.
|
|||||||
|
|
||||||
common/dashboard_customizing.rst
|
common/dashboard_customizing.rst
|
||||||
dashboard_sessions.rst
|
dashboard_sessions.rst
|
||||||
|
dashboard_manage_images.rst
|
||||||
|
dashboard_manage_instances.rst
|
||||||
|
dashboard_manage_flavors.rst
|
||||||
|
dashboard_manage_shares.rst
|
||||||
|
dashboard_manage_host_aggregates.rst
|
||||||
|
dashboard_admin_manage_stacks.rst
|
||||||
|
|
||||||
|
|
||||||
- To deploy the dashboard, see the `OpenStack dashboard documentation
|
- To deploy the Dashboard, see the `OpenStack dashboard documentation
|
||||||
<http://docs.openstack.org/developer/horizon/topics/deployment.html>`__.
|
<http://docs.openstack.org/developer/horizon/topics/deployment.html>`__.
|
||||||
- To launch instances with the dashboard, see the `OpenStack End User
|
- To launch instances with the Dashboard, see the `OpenStack End User
|
||||||
Guide <http://docs.openstack.org/user-guide/dashboard_launch_instances.html>`__.
|
Guide <http://docs.openstack.org/user-guide/dashboard_launch_instances.html>`__.
|
||||||
|
|
||||||
|
.. Additional Documents to add-the final toctree should resemble this- <JR>
|
||||||
|
|
||||||
|
.. dashboard_manage_images.rst
|
||||||
|
.. *dashboard_admin_manage_roles.rst
|
||||||
|
.. dashboard_manage_instances.rst
|
||||||
|
.. dashboard_manage_flavors.rst
|
||||||
|
.. *dashboard_manage_volumes.rst
|
||||||
|
.. *dashboard_manage_shares.rst
|
||||||
|
.. *dashboard_set_quotas
|
||||||
|
.. *dashboard_manage_resources.rst
|
||||||
|
.. dashboard_manage_host_aggregates.rst
|
||||||
|
.. dashboard_admin_manage_stacks.rst
|
||||||
|
|||||||
@ -0,0 +1,33 @@
|
|||||||
|
============================================
|
||||||
|
Launch and manage stacks using the Dashboard
|
||||||
|
============================================
|
||||||
|
|
||||||
|
The Orchestration service provides a template-based
|
||||||
|
orchestration engine for the OpenStack cloud. Orchestration
|
||||||
|
services create and manage cloud infrastructure
|
||||||
|
resources such as storage, networking, instances, and
|
||||||
|
applications as a repeatable running environment.
|
||||||
|
|
||||||
|
Administrators use templates to create stacks, which are
|
||||||
|
collections of resources. For example, a stack might
|
||||||
|
include instances, floating IPs, volumes,
|
||||||
|
security groups, or users. The Orchestration service
|
||||||
|
offers access to all OpenStack
|
||||||
|
core services via a single modular template, with additional
|
||||||
|
orchestration capabilities such as auto-scaling and basic
|
||||||
|
high availability.
|
||||||
|
|
||||||
|
For information about:
|
||||||
|
|
||||||
|
* administrative tasks on the command-line, see
|
||||||
|
:doc:`cli_admin_manage_stacks`.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
There are no administration-specific tasks that can be done through
|
||||||
|
the Dashboard.
|
||||||
|
|
||||||
|
* the basic creation and deletion of Orchestration stacks, refer to
|
||||||
|
the `OpenStack End User Guide
|
||||||
|
<http://docs.openstack.org/user-guide/dashboard_stacks.html>`__.
|
||||||
|
|
||||||
163
doc/admin-guide-cloud/source/dashboard_manage_flavors.rst
Normal file
163
doc/admin-guide-cloud/source/dashboard_manage_flavors.rst
Normal file
@ -0,0 +1,163 @@
|
|||||||
|
==============
|
||||||
|
Manage flavors
|
||||||
|
==============
|
||||||
|
|
||||||
|
In OpenStack, a flavor defines the compute, memory, and storage
|
||||||
|
capacity of a virtual server, also known as an instance. As an
|
||||||
|
administrative user, you can create, edit, and delete flavors.
|
||||||
|
|
||||||
|
The following table lists the default flavors.
|
||||||
|
|
||||||
|
============ ========= =============== =============
|
||||||
|
Flavor VCPUs Disk (in GB) RAM (in MB)
|
||||||
|
============ ========= =============== =============
|
||||||
|
m1.tiny 1 1 512
|
||||||
|
m1.small 1 20 2048
|
||||||
|
m1.medium 2 40 4096
|
||||||
|
m1.large 4 80 8192
|
||||||
|
m1.xlarge 8 160 16384
|
||||||
|
============ ========= =============== =============
|
||||||
|
|
||||||
|
Create flavors
|
||||||
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
|
||||||
|
Choose the :guilabel:`admin` project from the drop-down
|
||||||
|
list at the top of the page.
|
||||||
|
#. In the :guilabel:`Admin` tab, open the :guilabel:`System`
|
||||||
|
tab and click the :guilabel:`Flavors` category.
|
||||||
|
#. Click :guilabel:`Create Flavor`.
|
||||||
|
#. In the :guilabel:`Create Flavor` window, enter or select the
|
||||||
|
parameters for the flavor in the :guilabel:`Flavor Information` tab.
|
||||||
|
|
||||||
|
========================= =======================================
|
||||||
|
**Name** Enter the flavor name.
|
||||||
|
**ID** Unique ID (integer or UUID) for the
|
||||||
|
new flavor. If specifying 'auto', a
|
||||||
|
UUID will be automatically generated.
|
||||||
|
**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 amount 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 lifecycle
|
||||||
|
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 (MB)** Enter the amount of swap space (in
|
||||||
|
megabytes) to use. If unspecified,
|
||||||
|
the default is 0.
|
||||||
|
========================= =======================================
|
||||||
|
|
||||||
|
#. In the :guilabel:`Flavor Access` tab, you can control access to
|
||||||
|
the flavor by moving projects from the :guilabel:`All Projects`
|
||||||
|
column to the :guilabel:`Selected Projects` column.
|
||||||
|
|
||||||
|
Only projects in the :guilabel:`Selected Projects` column can
|
||||||
|
use the flavor. If there are no projects in the right column,
|
||||||
|
all projects can use the flavor.
|
||||||
|
#. Click :guilabel:`Create Flavor`.
|
||||||
|
|
||||||
|
Update flavors
|
||||||
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
#. Choose the :guilabel:`admin` project from the drop-down list at
|
||||||
|
the top of the page.
|
||||||
|
#. In the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Flavors` category.
|
||||||
|
#. Select the flavor that you want to edit. Click :guilabel:`Edit
|
||||||
|
Flavor`.
|
||||||
|
#. In the :guilabel:`Edit Flavor` window, you can change the flavor
|
||||||
|
name, VCPUs, RAM, root disk, ephemeral disk, and swap disk values.
|
||||||
|
#. Click :guilabel:`Save`.
|
||||||
|
|
||||||
|
Update Metadata
|
||||||
|
~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
|
||||||
|
Choose the :guilabel:`admin` project from the drop-down list at
|
||||||
|
the top of the page.
|
||||||
|
#. In the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Flavors` category.
|
||||||
|
#. Select the flavor that you want to update. In the drop-down
|
||||||
|
list, click :guilabel:`Update Metadata` or click :guilabel:`No` or
|
||||||
|
:guilabel:`Yes` in the :guilabel:`Metadata` column.
|
||||||
|
#. In the :guilabel:`Update Flavor Metadata` window, you can customize
|
||||||
|
some metadata keys, then add it to this flavor and set them values.
|
||||||
|
#. Click :guilabel:`Save`.
|
||||||
|
|
||||||
|
**Optional metadata keys**
|
||||||
|
|
||||||
|
+-------------------------------+-------------------------------+
|
||||||
|
| | quota:cpu_shares |
|
||||||
|
| +-------------------------------+
|
||||||
|
| **CPU limits** | quota:cpu_period |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:cpu_limit |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:cpu_reservation |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:cpu_quota |
|
||||||
|
+-------------------------------+-------------------------------+
|
||||||
|
| | quota:disk_read_bytes_sec |
|
||||||
|
| +-------------------------------+
|
||||||
|
| **Disk tuning** | quota:disk_read_iops_sec |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:disk_write_bytes_sec |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:disk_write_iops_sec |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:disk_total_bytes_sec |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:disk_total_iops_sec |
|
||||||
|
+-------------------------------+-------------------------------+
|
||||||
|
| | quota:vif_inbound_average |
|
||||||
|
| +-------------------------------+
|
||||||
|
| **Bandwidth I/O** | quota:vif_inbound_burst |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:vif_inbound_peak |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:vif_outbound_average |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:vif_outbound_burst |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | quota:vif_outbound_peak |
|
||||||
|
+-------------------------------+-------------------------------+
|
||||||
|
| **Watchdog behavior** | hw:watchdog_action |
|
||||||
|
+-------------------------------+-------------------------------+
|
||||||
|
| | hw_rng:allowed |
|
||||||
|
| +-------------------------------+
|
||||||
|
| **Random-number generator** | hw_rng:rate_bytes |
|
||||||
|
| +-------------------------------+
|
||||||
|
| | hw_rng:rate_period |
|
||||||
|
+-------------------------------+-------------------------------+
|
||||||
|
|
||||||
|
For information about supporting metadata keys, see the
|
||||||
|
`OpenStack Cloud Administrator Guide
|
||||||
|
<http://docs.openstack.org/admin-guide-cloud/compute-flavors.html>`__.
|
||||||
|
|
||||||
|
Delete flavors
|
||||||
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
#. Choose the :guilabel:`admin` project from the drop-down list at
|
||||||
|
the top of the page.
|
||||||
|
#. In the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Flavors` category.
|
||||||
|
#. Select the flavors that you want to delete.
|
||||||
|
#. Click :guilabel:`Delete Flavors`.
|
||||||
|
#. In the :guilabel:`Confirm Delete Flavors` window, click
|
||||||
|
:guilabel:`Delete Flavors` to confirm the deletion. You cannot
|
||||||
|
undo this action.
|
||||||
@ -0,0 +1,79 @@
|
|||||||
|
=================================
|
||||||
|
Create and manage host aggregates
|
||||||
|
=================================
|
||||||
|
|
||||||
|
Host aggregates enable administrative users to assign key-value pairs to
|
||||||
|
groups of machines.
|
||||||
|
|
||||||
|
Each node can have multiple aggregates and each aggregate can have
|
||||||
|
multiple key-value pairs. You can assign the same key-value pair to
|
||||||
|
multiple aggregates.
|
||||||
|
|
||||||
|
The scheduler uses this information to make scheduling decisions.
|
||||||
|
For information, see
|
||||||
|
`Scheduling <http://docs.openstack.org/liberty/config-reference/content/section_compute-scheduler.html>`__.
|
||||||
|
|
||||||
|
To create a host aggregate
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
|
||||||
|
Choose the :guilabel:`admin` project from the drop-down list at the top
|
||||||
|
of the page.
|
||||||
|
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click
|
||||||
|
the :guilabel:`Host Aggregates` category.
|
||||||
|
|
||||||
|
#. Click :guilabel:`Create Host Aggregate`.
|
||||||
|
|
||||||
|
#. In the :guilabel:`Create Host Aggregate` dialog box, enter or select the
|
||||||
|
following values on the :guilabel:`Host Aggregate Information` tab:
|
||||||
|
|
||||||
|
- :guilabel:`Name`: The host aggregate name.
|
||||||
|
|
||||||
|
- :guilabel:`Availability Zone`: The cloud provider defines the default
|
||||||
|
availability zone, such as ``us-west``, ``apac-south``, or
|
||||||
|
``nova``. You can target the host aggregate, as follows:
|
||||||
|
|
||||||
|
- When the host aggregate is exposed as an availability zone,
|
||||||
|
select the availability zone when you launch an instance.
|
||||||
|
|
||||||
|
- When the host aggregate is not exposed as an availability zone,
|
||||||
|
select a flavor and its extra specs to target the host
|
||||||
|
aggregate.
|
||||||
|
|
||||||
|
#. Assign hosts to the aggregate using the :guilabel:`Manage Hosts within
|
||||||
|
Aggregate` tab in the same dialog box.
|
||||||
|
|
||||||
|
To assign a host to the aggregate, click **+** for the host. The host
|
||||||
|
moves from the :guilabel:`All available hosts` list to the
|
||||||
|
:guilabel:`Selected hosts` list.
|
||||||
|
|
||||||
|
You can add one host to one or more aggregates. To add a host to an
|
||||||
|
existing aggregate, edit the aggregate.
|
||||||
|
|
||||||
|
To manage host aggregates
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Choose the :guilabel:`admin` project from the drop-down list at the top
|
||||||
|
of the page.
|
||||||
|
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab and click
|
||||||
|
the :guilabel:`Host Aggregates` category.
|
||||||
|
|
||||||
|
- To edit host aggregates, select the host aggregate that you want
|
||||||
|
to edit. Click :guilabel:`Edit Host Aggregate`.
|
||||||
|
|
||||||
|
In the :guilabel:`Edit Host Aggregate` dialog box, you can change the
|
||||||
|
name and availability zone for the aggregate.
|
||||||
|
|
||||||
|
- To manage hosts, locate the host aggregate that you want to edit
|
||||||
|
in the table. Click :guilabel:`More` and select :guilabel:`Manage Hosts`.
|
||||||
|
|
||||||
|
In the :guilabel:`Add/Remove Hosts to Aggregate` dialog box,
|
||||||
|
click **+** to assign a host to an aggregate. Click **-** to
|
||||||
|
remove a host that is assigned to an aggregate.
|
||||||
|
|
||||||
|
- To delete host aggregates, locate the host aggregate that you want
|
||||||
|
to edit in the table. Click :guilabel:`More` and select
|
||||||
|
:guilabel:`Delete Host Aggregate`.
|
||||||
122
doc/admin-guide-cloud/source/dashboard_manage_images.rst
Normal file
122
doc/admin-guide-cloud/source/dashboard_manage_images.rst
Normal file
@ -0,0 +1,122 @@
|
|||||||
|
========================
|
||||||
|
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
|
||||||
|
<http://docs.openstack.org/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 <http://docs.openstack.org/image-guide/>`_.
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
|
||||||
|
Choose the :guilabel:`admin` project from the drop-down list
|
||||||
|
at the top of the page.
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Images` category. The images that you
|
||||||
|
can administer for cloud users appear on this page.
|
||||||
|
#. Click :guilabel:`Create Image`, which opens the
|
||||||
|
:guilabel:`Create An Image` window.
|
||||||
|
|
||||||
|
.. figure:: figures/create_image.png
|
||||||
|
|
||||||
|
**Figure Dashboard — Create Image**
|
||||||
|
|
||||||
|
#. In the :guilabel:`Create An Image` window, enter or select the
|
||||||
|
following values:
|
||||||
|
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Name` | Enter a name for the image. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Description` | Enter a brief description of |
|
||||||
|
| | the image. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Image Source` | Choose the image source from |
|
||||||
|
| | the dropdown list. Your choices |
|
||||||
|
| | are :guilabel:`Image Location` |
|
||||||
|
| | and :guilabel:`Image File`. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Image File` or | Based on your selection, there |
|
||||||
|
| :guilabel:`Image Location` | is an :guilabel:`Image File` or |
|
||||||
|
| | :guilabel:`Image Location` |
|
||||||
|
| | field. You can include the |
|
||||||
|
| | location URL or browse for the |
|
||||||
|
| | image file on your file system |
|
||||||
|
| | and add it. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Kernel` | Select the kernel to boot an |
|
||||||
|
| | AMI-style image. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Ramdisk` | Select the ramdisk to boot an |
|
||||||
|
| | AMI-style image. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Format` | Select the image format. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Architecture` | Specify the architecture. For |
|
||||||
|
| | example, ``i386`` for a 32-bit |
|
||||||
|
| | architecture or ``x86_64`` for |
|
||||||
|
| | a 64-bit architecture. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Minimum Disk (GB)` | Leave this field empty. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Minimum RAM (MB)` | Leave this field empty. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Copy Data` | Specify this option to copy |
|
||||||
|
| | image data to the Image service.|
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Public` | Select this option to make the |
|
||||||
|
| | image public to all users. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
| :guilabel:`Protected` | Select this option to ensure |
|
||||||
|
| | that only users with |
|
||||||
|
| | permissions can delete it. |
|
||||||
|
+-------------------------------+---------------------------------+
|
||||||
|
|
||||||
|
#. Click :guilabel:`Create Image`.
|
||||||
|
|
||||||
|
The image is queued to be uploaded. It might take several minutes
|
||||||
|
before the status changes from ``Queued`` to ``Active``.
|
||||||
|
|
||||||
|
Update images
|
||||||
|
~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
Choose the :guilabel:`admin` project from the drop-down list
|
||||||
|
at the top of the page.
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Images` category.
|
||||||
|
#. Select the images that you want to edit. Click :guilabel:`Edit Image`.
|
||||||
|
#. In the :guilabel:`Update Image` window, you can change the image name.
|
||||||
|
|
||||||
|
Select the :guilabel:`Public` check box to make the image public.
|
||||||
|
Clear this check box to make the image private. You cannot change
|
||||||
|
the :guilabel:`Kernel ID`, :guilabel:`Ramdisk ID`, or
|
||||||
|
:guilabel:`Architecture` attributes for an image.
|
||||||
|
#. Click :guilabel:`Update Image`.
|
||||||
|
|
||||||
|
Delete images
|
||||||
|
~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard.
|
||||||
|
Choose the :guilabel:`admin` project from the drop-down list
|
||||||
|
at the top of the page.
|
||||||
|
#. On the :guilabel:`Admin tab`, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Images` category.
|
||||||
|
#. Select the images that you want to delete.
|
||||||
|
#. Click :guilabel:`Delete Images`.
|
||||||
|
#. In the :guilabel:`Confirm Delete Images` window, click :guilabel:`Delete
|
||||||
|
Images` to confirm the deletion.
|
||||||
|
|
||||||
|
You cannot undo this action.
|
||||||
77
doc/admin-guide-cloud/source/dashboard_manage_instances.rst
Normal file
77
doc/admin-guide-cloud/source/dashboard_manage_instances.rst
Normal file
@ -0,0 +1,77 @@
|
|||||||
|
================
|
||||||
|
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 <http://docs.openstack.org/user-guide/dashboard_launch_instances.html>`__.
|
||||||
|
|
||||||
|
Create instance snapshots
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project from the
|
||||||
|
drop-down list at the top of the page.
|
||||||
|
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Instances` category.
|
||||||
|
|
||||||
|
#. Select an instance to create a snapshot from it. From the
|
||||||
|
:guilabel:`Actions` drop-down list, select :guilabel:`Create Snapshot`.
|
||||||
|
|
||||||
|
#. In the :guilabel:`Create Snapshot` window, enter a name for the snapshot.
|
||||||
|
|
||||||
|
#. Click :guilabel:`Create Snapshot`. The Dashboard shows the instance snapshot
|
||||||
|
in the :guilabel:`Images` category.
|
||||||
|
|
||||||
|
#. To launch an instance from the snapshot, select the snapshot and
|
||||||
|
click :guilabel:`Launch Instance`. For information about launching
|
||||||
|
instances, see the
|
||||||
|
`OpenStack End User Guide <http://docs.openstack.org/user-guide/dashboard_launch_instances.html>`__.
|
||||||
|
|
||||||
|
Control the state of an instance
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project from the
|
||||||
|
drop-down list at the top of the page.
|
||||||
|
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Instances` category.
|
||||||
|
|
||||||
|
#. Select the instance for which you want to change the state.
|
||||||
|
|
||||||
|
#. From the drop-down list in the :guilabel:`Actions` column,
|
||||||
|
select the state.
|
||||||
|
|
||||||
|
Depending on the current state of the instance, you can perform various
|
||||||
|
actions on the instance. For example, pause, un-pause, suspend, resume,
|
||||||
|
soft or hard reboot, or terminate (actions in red are dangerous).
|
||||||
|
|
||||||
|
.. figure:: figures/change_instance_state.png
|
||||||
|
:width: 100%
|
||||||
|
|
||||||
|
**Figure Dashboard — Instance Actions**
|
||||||
|
|
||||||
|
|
||||||
|
Track usage
|
||||||
|
~~~~~~~~~~~
|
||||||
|
|
||||||
|
Use the :guilabel:`Overview` category to track usage of instances
|
||||||
|
for each project.
|
||||||
|
|
||||||
|
You can track costs per month by showing meters like number of VCPUs,
|
||||||
|
disks, RAM, and uptime of all your instances.
|
||||||
|
|
||||||
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project from the
|
||||||
|
drop-down list at the top of the page.
|
||||||
|
|
||||||
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
|
and click the :guilabel:`Overview` category.
|
||||||
|
|
||||||
|
#. Select a month and click :guilabel:`Submit` to query the instance usage for
|
||||||
|
that month.
|
||||||
|
|
||||||
|
#. Click :guilabel:`Download CSV Summary` to download a CSV summary.
|
||||||
@ -4,7 +4,7 @@ Manage shares and share types
|
|||||||
|
|
||||||
Shares are file storage that instances can access. Users can
|
Shares are file storage that instances can access. Users can
|
||||||
allow or deny a running instance to have access to a share at any time.
|
allow or deny a running instance to have access to a share at any time.
|
||||||
For information about using the dashboard to create and manage shares as
|
For information about using the Dashboard to create and manage shares as
|
||||||
an end user, see the
|
an end user, see the
|
||||||
`OpenStack End User Guide <http://docs.openstack.org/user-guide/dashboard_manage_shares.html>`_.
|
`OpenStack End User Guide <http://docs.openstack.org/user-guide/dashboard_manage_shares.html>`_.
|
||||||
|
|
||||||
@ -17,7 +17,7 @@ or delete shares.
|
|||||||
Create a share type
|
Create a share type
|
||||||
~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
#. Log in to the dashboard and choose the :guilabel:`admin`
|
#. Log in to the Dashboard and choose the :guilabel:`admin`
|
||||||
project from the drop-down list at the top of the page.
|
project from the drop-down list at the top of the page.
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
@ -43,7 +43,7 @@ Create a share type
|
|||||||
Update share type
|
Update share type
|
||||||
~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
#. Log in to the dashboard and choose the :guilabel:`admin` project from
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project from
|
||||||
the drop-down list at the top of the page.
|
the drop-down list at the top of the page.
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
@ -70,7 +70,7 @@ Delete share types
|
|||||||
|
|
||||||
When you delete a share type, shares of that type are not deleted.
|
When you delete a share type, shares of that type are not deleted.
|
||||||
|
|
||||||
#. Log in to the dashboard and choose the :guilabel:`admin` project from
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project from
|
||||||
the drop-down list at the top of the page.
|
the drop-down list at the top of the page.
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
@ -91,7 +91,7 @@ When you delete a share type, shares of that type are not deleted.
|
|||||||
Delete shares
|
Delete shares
|
||||||
~~~~~~~~~~~~~
|
~~~~~~~~~~~~~
|
||||||
|
|
||||||
#. Log in to the dashboard and choose the :guilabel:`admin` project
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project
|
||||||
from the drop-down list at the top of the page.
|
from the drop-down list at the top of the page.
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
@ -111,7 +111,7 @@ Delete shares
|
|||||||
Delete share server
|
Delete share server
|
||||||
~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
#. Log in to the dashboard and choose the :guilabel:`admin` project
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project
|
||||||
from the drop-down list at the top of the page.
|
from the drop-down list at the top of the page.
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
@ -131,7 +131,7 @@ Delete share server
|
|||||||
Delete share networks
|
Delete share networks
|
||||||
~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
#. Log in to the dashboard and choose the :guilabel:`admin` project
|
#. Log in to the Dashboard and choose the :guilabel:`admin` project
|
||||||
from the drop-down list at the top of the page.
|
from the drop-down list at the top of the page.
|
||||||
|
|
||||||
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
#. On the :guilabel:`Admin` tab, open the :guilabel:`System` tab
|
||||||
@ -2,7 +2,7 @@
|
|||||||
Set up session storage for the Dashboard
|
Set up session storage for the Dashboard
|
||||||
========================================
|
========================================
|
||||||
|
|
||||||
The dashboard uses `Django sessions
|
The Dashboard uses `Django sessions
|
||||||
framework <https://docs.djangoproject.com/en/dev/topics/http/sessions/>`__
|
framework <https://docs.djangoproject.com/en/dev/topics/http/sessions/>`__
|
||||||
to handle user session data. However, you can use any available session
|
to handle user session data. However, you can use any available session
|
||||||
back end. You customize the session back end through the
|
back end. You customize the session back end through the
|
||||||
|
|||||||
BIN
doc/admin-guide-cloud/source/figures/change_instance_state.png
Normal file
BIN
doc/admin-guide-cloud/source/figures/change_instance_state.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 96 KiB |
@ -22,7 +22,6 @@ System (EFS) does.
|
|||||||
shared_file_systems_share_management.rst
|
shared_file_systems_share_management.rst
|
||||||
shared_file_systems_manage_shares_cli.rst
|
shared_file_systems_manage_shares_cli.rst
|
||||||
shared_file_systems_share_types.rst
|
shared_file_systems_share_types.rst
|
||||||
shared_file_systems_manage_shares_dashboard.rst
|
|
||||||
shared_file_systems_snapshots.rst
|
shared_file_systems_snapshots.rst
|
||||||
shared_file_systems_security_services.rst
|
shared_file_systems_security_services.rst
|
||||||
shared_file_systems_cgroups.rst
|
shared_file_systems_cgroups.rst
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user