Unixchips : openstack command line administration PART-2 (glance/cinder/manila)

Manage Images (Glance)

cloud operator assigns the roles to users and determines who can upload and manage the images .Only cloud operators or administrators can upload and manage images.
We can upload the images through glance client or image service API

To list the available images

$ glance image-list
************************************
+--------------------------------------+---------------------------------
+-------------+------------------+----------+--------+
| ID
| Name
|
Disk Format | Container Format | Size Status |
+--------------------------------------+---------------------------------
+-------------+------------------+----------+--------+
| 397e713c-b95b-4186-ad46-6126863ea0a9 | cirros-0.3.1-x86_64-uecami
| ami 25165824 | active |
| df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.1-x86_64-uec-kernel |
aki
| aki
| 4955792 | active |
| 3cf852bd-2332-48f4-9ae4-7d926d50945e | cirros-0.3.1-x86_64-uec-ramdisk |
ari
| ari
| 3714968 | active |
| 7e5142af-1253-4634-bcc6-89482c5f2e8a | myCirrosImage
|
ami
| ami
| 14221312 | active |
+--------------------------------------+---------------------------------

To filter only the cirrors image

$ glance image-list | grep 'cirros'
*********************************
| 397e713c-b95b-4186-ad46-6126863ea0a9 | cirros-0.3.1-x86_64-uec
|
ami
| ami
| 25165824 | active |
| df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.1-x86_64-uec-kernel |
aki
| aki
| 4955792 | active |
| 3cf852bd-2332-48f4-9ae4-7d926d50945e | cirros-0.3.1-x86_64-uec-ramdisk |
ari
| ari
| 3714968 | active |

To get the image details by name or id

$ glance image-show myCirrosImage

+---------------------------------------+---------------------------------

-----+

| Property

| Value

+---------------------------------------+---------------------------------

-----+

| Property 'base_image_ref'

| 397e713c-b95b-4186-ad46-

6126863ea0a9 |

| Property 'image_location'

| snapshot

| Property 'image_state'

| available

| Property 'image_type'

| snapshot

| Property 'instance_type_ephemeral_gb' | 0

| Property 'instance_type_flavorid'

| 2

| Property 'instance_type_id'

| 5

| Property 'instance_type_memory_mb'

| 2048

| Property 'instance_type_name'

| m1.small

| Property 'instance_type_root_gb'

| 20

| Property 'instance_type_rxtx_factor' | 1

| Property 'instance_type_swap'

| 0

| Property 'instance_type_vcpu_weight' | None

| Property 'instance_type_vcpus'

| 1

| Property 'instance_uuid'

| 84c6e57d-a6b1-44b6-81eb-

fcb36afd31b5 |

| Property 'kernel_id'

| df430cc2-3406-4061-b635-

a51c16e488ac |

| Property 'owner_id'

| 66265572db174a7aa66eba661f58eb9e

| Property 'ramdisk_id'

| 3cf852bd-2332-48f4-9ae4-

7d926d50945e |

| Property 'user_id'

| 376744b5910b4b4da7d8e6cb483b06a8

| checksum

| 8e4838effa1969ad591655d6485c7ba8

| container_format

| ami

| created_at

| 2013-07-22T19:45:58

| deleted

| False

| disk_format

| ami

| id

| 7e5142af-1253-4634-bcc6-

89482c5f2e8a |

| is_public

| False

min_ram

| 0

| name

| myCirrosImage

| owner

| 66265572db174a7aa66eba661f58eb9e

| protected

| False

| size

| 14221312

| status

| active

| updated_at

| 2013-07-22T19:46:42

+---------------------------------------+---------------------------------

The location metadata of the images can be defined in following method

edit the /etc/glance/glance.conf as below

show_multiple_locations = True

filesystem_store_metadata_file = filePath, where filePath points to a JSON

file that defines the mount point for OpenStack images on your system and a unique ID.

For example:

[{

"id": "b9d69795-5951-4cb0-bb5c-29491e1e2daf",

"mountpoint": "/var/lib/glance/images/"

}]

After you restart the Image Service, you can use the following syntax to view the image's

location information:

$ glance --os-image-api-version=2 image-show 2d9bb53f-70ea-4066-

a68b-67960eaae673

To upload a cent Os 6.3 image in qcow format and configure the public access

$ glance image-create --name centos63-image --disk-format=qcow2 \ --

container-format=bare --is-public=True --file=./centos63.qcow2

To update the image using name or ID

Below are the parameters which we can update on images

--name NAME The name of the image.

--disk-format DISK_FORMAT The disk format of the image. Acceptable formats are

ami, ari, aki, vhd, vmdk, raw, qcow2, vdi, and iso.

--container-format

CONTAINER_FORMAT The container format of the image. Acceptable formats

are ami, ari, aki, bare, and ovf.

--owner TENANT_ID The tenant who should own the image.

--size SIZE The size of image data, in bytes.

--min-disk DISK_GB The minimum size of disk needed to boot image, in

gigabytes.

--min-ram DISK_RAM The minimum amount of ram needed to boot image, in

megabytes.

--location IMAGE_URL The URL where the data for this image resides. For

example, if the image data is stored in swift, you could

specify

swift://account:key@example.com/container/ob

--file FILE Local file that contains disk image to be uploaded during

update. Alternatively, you can pass images to the client

through stdin.

--checksum CHECKSUM Hash of image data to use for verification.

--copy-from IMAGE_URL Similar to --location in usage, but indicates that the

Glance server should immediately copy the data and

store it in its configured image store.

--is-public [True|False] Makes an image accessible to the public.

--is-protected [True|False] Prevents an image from being deleted.

--property KEY=VALUE Arbitrary property to associate with image. Can be used

multiple times.

--purge-props Deletes all image properties that are not explicitly set in

the update request. Otherwise, those properties not

referenced are preserved.

--human-readable Prints image size in a human-friendly format.

$ glance image-update \ --property hw_vif_model=e1000 f16-x86_64-

openstack-sda

Below are the valid vif models

libvirt_type setting | Supported model values

qemu or kvm virtio , ne2k_pci, pcnet, rtl8139, e1000

Create images using nova

To create an image first we need to list out the instances

$ nova list

+--------------------------------------+----------------------+--------+--

----------+-------------+------------------+

| ID

| Name

| Status |

Task State | Power State | Networks

+--------------------------------------+----------------------+--------+--

----------+-------------+------------------+

| 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | myCirrosServer

| ACTIVE |

None

| Running

| private=10.0.0.3 |

+--------------------------------------+----------------------+--------+--

To create a snapshot of the instance

$ nova image-create myCirrosServer myCirrosImage

We can check the details of the image created using below command

$ nova image-show myCirrosImage

+-------------------------------------+-----------------------------------

---+

| Property

| Value

+-------------------------------------+-----------------------------------

---+

| metadata owner_id

| 66265572db174a7aa66eba661f58eb9e

| minDisk

| 0

| metadata instance_type_name

| m1.small

| metadata instance_type_id

| 5

| metadata instance_type_memory_mb

| 2048

| id

| 7e5142af-1253-4634-bcc6-

89482c5f2e8a |

| metadata instance_type_root_gb

| 20

| metadata instance_type_rxtx_factor | 1

| metadata ramdisk_id

| 3cf852bd-2332-48f4-9ae4-

7d926d50945e |

| metadata image_state

| available

| metadata image_location

| snapshot

| minRam

| 0

| metadata instance_type_vcpus

| 1

| status

| ACTIVE

| updated

| 2013-07-22T19:46:42Z

| metadata instance_type_swap

| 0

| metadata instance_type_vcpu_weight | None

| metadata base_image_ref

| 397e713c-b95b-4186-ad46-

6126863ea0a9 |

| progress

| 100

| metadata instance_type_flavorid

| 2

| OS-EXT-IMG-SIZE:size

| 14221312

| metadata image_type

| snapshot

| metadata user_id

| 376744b5910b4b4da7d8e6cb483b06a8

| name

| myCirrosImage

| created

| 2013-07-22T19:45:58Z

| metadata instance_uuid

| 84c6e57d-a6b1-44b6-81eb-

fcb36afd31b5 |

| server

| 84c6e57d-a6b1-44b6-81eb-

To launch an instance from the image

$ nova boot newServer --image 7e5142af-1253-4634-bcc6-89482c5f2e8a \ --

flavor 3

+-------------------------------------+-----------------------------------

---+

| Property

| Value

+-------------------------------------+-----------------------------------

---+

| OS-EXT-STS:task_state

| scheduling

| image

| myCirrosImage

| OS-EXT-STS:vm_state

| building

| OS-EXT-SRV-ATTR:instance_name

| instance-00000007

| flavor

| m1.medium

| id

| d7efd3e4-d375-46d1-9d57-

372b6e4bdb7f |

| security_groups

| [{u'name': u'default'}]

| user_id

| 376744b5910b4b4da7d8e6cb483b06a8

| OS-DCF:diskConfig

| MANUAL

| accessIPv4

| accessIPv6

| progress

| 0

| OS-EXT-STS:power_state

| 0

| OS-EXT-AZ:availability_zone

| nova

| config_drive

| status

| BUILD

| updated

| 2013-07-22T19:58:33Z

| hostId

| OS-EXT-SRV-ATTR:host

| None

| key_name

| None

| OS-EXT-SRV-ATTR:hypervisor_hostname | None

| name

| newServer

| adminPass

| jis88nN46RGP

| tenant_id

| 66265572db174a7aa66eba661f58eb9e

| created

| 2013-07-22T19:58:33Z

| metadata

| {}

(important we cannot create a snapshot form an instance which has an attached volume. We need to detach the volume first and create the snapshot)

Below is the procedure for snapshot creation of an instance

Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk. If necessary, list the instances to view the instance name:

$ nova list

+--------------------------------------+------------+--------+------------------------------+

+--------------------------------------+------------+--------+------------------------------+

+--------------------------------------+------------+--------+------------------------------+

Use the nova stop command to shut down the instance:

$ nova stop myInstance

Use the nova list command to confirm that the instance shows a SHUTOFF status:

$ nova list

+--------------------------------------+------------+---------+------------------+

+--------------------------------------+------------+---------+------------------+

+--------------------------------------+------------+---------+------------------+

Use the nova image-create command to take a snapshot:

$ nova image-create --poll myInstance myInstanceSnapshot
Instance snapshotting... 50% complete

Use the nova image-list command to check the status until the status is ACTIVE:

$ nova image-list

+--------------------------------------+---------------------------------+--------+--------+

+--------------------------------------+---------------------------------+--------+--------+

+--------------------------------------+---------------------------------+--------+--------+

Download the snapshot as an image

$ glance image-download --file snapshot.raw f30b204e-1ce6-40e7-b8d9-b353d4d84e7d

Copy the image to the new machine/environment using scp or http method and import the snapshot

$ glance --os-image-api-version 1 image-create \

--container-format bare --disk-format qcow2 --copy-from IMAGE_URL

Boot a new instance from the snapshot

$nova boot --flavor m1.tiny --image myInstanceSnapshot myNewInstance

Manage volumes (cinder)

Migrate a volume

According to the below cases we can migrate a volume

Bring down a physical storage device for maintenance without disrupting workloads.
Modify the properties of a volume.
Free up space in a thinly-provisioned back end.

$ cinder migrate volumeID destinationHost --force-host-copy True|False

To create a volume

List the images and note the id of the imagesfrom which we are creating the volume

$nova image-list

+-----------------------+---------------------------------+--------+--------------------------+
| ID | Name | Status | Server |
+-----------------------+---------------------------------+--------+--------------------------+
| 397e713c-b95b-4186... | cirros-0.3.2-x86_64-uec | ACTIVE | |
| df430cc2-3406-4061... | cirros-0.3.2-x86_64-uec-kernel | ACTIVE | |
| 3cf852bd-2332-48f4... | cirros-0.3.2-x86_64-uec-ramdisk | ACTIVE | |
| 7e5142af-1253-4634... | myCirrosImage | ACTIVE | 84c6e57d-a6b1-44b6-81... |
| 89bcd424-9d15-4723... | mysnapshot | ACTIVE | f51ebd07-c33d-4951-87... |
+-----------------------+---------------------------------+--------+--------------------------+

List the availability zones and note the id of the AZ

$ cinder availability-zone-list

+------+-----------+
| Name | Status |
+------+-----------+
| nova | available |
+------+-----------+

Now create a volume with 8GB size

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 |
+---------------------+--------------------------------------+

Verify that cinder volume is created successfully

(if the status of the volume is error, we need to check the quota details we may exceeded the quota)

To attach a volume to an instance

$ 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 |
+----------+--------------------------------------+

To get the information about the attached volume

cinder show 573e024d-5235-49ce-8332-be1576d323f8
+------------------------------+------------------------------------------+
| Property | Value |
+------------------------------+------------------------------------------+
| attachments | [{u'device': u'/dev/vdb', |
| | u'server_id': u'84c6e57d-a |
| | u'id': u'573e024d-... |
| | u'volume_id': u'573e024d... |
| 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 |
| 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..., |
| | u'image_id': u'397e713c..., |
| | u'ramdisk_id': u'3cf852bd..., |
| |u'image_name': u'cirros-0.3.2-x86_64-uec'}|
| volume_type | None |
+------------------------------+------------------------------------------+

To resize the volume we need to follow the below steps

First detach the volume using below command

To delete a volume

To delete a volume we need to detach the volume from the instance first as explained above then delete the volume using below command

To transfer a volume

Accept a volume transfer

Create and manage file shares using manila client

To create a share network (We need to pass nutron id and subnet id along with this to configure the network properties of the share)

3. To create a share

$ manila create NFS 1 \

--name myshare \

--description "My Manila share" \

--share-network mysharenetwork \

--share-type default

+-----------------------------+--------------------------------------+

| Property | Value |

+-----------------------------+--------------------------------------+

| status | creating |

| share_type_name | default |

| description | My Manila share |

| availability_zone | None |

| share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |

| share_server_id | None |

| host | |

| access_rules_status | active |

| snapshot_id | None |

| is_public | False |

| task_state | None |

| snapshot_support | True |

| id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |

| size | 1 |

| name | myshare |

| share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |

| has_replicas | False |

| replication_type | None |

| created_at | 2016-03-24T14:15:34.000000 |

| share_proto | NFS |

| consistency_group_id | None |

| source_cgsnapshot_member_id | None |

source_cgsnapshot_member_id | None |
project_id | 907004508ef4447397ce6741a8f037c1 |
| metadata | {} |
+-----------------------------+--------------------------------------+

4. To show the share

$ manila show myshare
+-----------------------------+---------------------------------------------------------------+
| Property | Value |
+-----------------------------+---------------------------------------------------------------+
| status | available |
| share_type_name | default |
| description | My Manila share |
| availability_zone | nova |
| share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
| export_locations | |
| | path = 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
| | preferred = False |
| | is_admin_only = False |
| | id = b6bd76ce-12a2-42a9-a30a-8a43b503867d |
| | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
| | path = 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d |
| | preferred = False |
| | is_admin_only = True |
| | id = 6921e862-88bc-49a5-a2df-efeed9acd583 |
| | share_instance_id = e1c2d35e-fe67-4028-ad7a-45f668732b1d |
| share_server_id | 2e9d2d02-883f-47b5-bb98-e053b8d1e683 |
| host | nosb-devstack@london#LONDON |
| access_rules_status | active |
| snapshot_id | None |
| is_public | False |
| task_state | None |
| snapshot_support | True |
| id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
| size | 1 |
| name | myshare |
| share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
| has_replicas | False |
| replication_type | None |
| created_at | 2016-03-24T14:15:34.000000 |
| share_proto | NFS |
| consistency_group_id | None |
| source_cgsnapshot_member_id | None |
| project_id | 907004508ef4447397ce6741a8f037c1 |
| metadata | {}

5. To list the share

$ manila list
+--------------------------------------+---------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
| ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
+--------------------------------------+---------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
| 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | myshare | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
+--------------------------------------+---------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------

6. To list the export locations

$ manila share-export-location-list myshare
+--------------------------------------+--------------------------------------------------------+-----------+
| ID | Path | Preferred |
+--------------------------------------+--------------------------------------------------------+-----------+
| 6921e862-88bc-49a5-a2df-efeed9acd583 | 10.0.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d | False |
| b6bd76ce-12a2-42a9-a30a-8a43b503867d | 10.254.0.3:/share-e1c2d35e-fe67-4028-ad7a-45f668732b1d | False |
+--------------------------------------+--------------------------------------------------------+-----------+

7. Allow read write access to the share

$ manila access-allow myshare ip 10.0.0.0/24
+--------------+--------------------------------------+
| Property | Value |
+--------------+--------------------------------------+
| share_id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
| access_type | ip |
| access_to | 10.0.0.0/24 |
| access_level | rw |
| state | new |
| id | 0c8470ca-0d77-490c-9e71-29e1f453bf97 |
+--------------+--------------------------------------+

We can check the access details by using below command

$ manila access-list myshare
+--------------------------------------+-------------+-------------+--------------+--------+
| id | access_type | access_to | access_level | state |
+--------------------------------------+-------------+-------------+--------------+--------+
| 0c8470ca-0d77-490c-9e71-29e1f453bf97 | ip | 10.0.0.0/24 | rw | active |
+--------------------------------------+-------------+-------------+--------------+--------+

8. To give read only access to the share

$ manila access-allow myshare ip 20.0.0.0/24 --access-level ro
+--------------+--------------------------------------+
| Property | Value |
+--------------+--------------------------------------+
| share_id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
| access_type | ip |
| access_to | 20.0.0.0/24 |
| access_level | ro |
| state | new |
| id | f151ad17-654d-40ce-ba5d-98a5df67aadc |
+--------------+--------------------------------------+

We can check the access list using below command

$ manila access-list myshare
+--------------------------------------+-------------+-------------+--------------+--------+
| id | access_type | access_to | access_level | state |
+--------------------------------------+-------------+-------------+--------------+--------+
| 0c8470ca-0d77-490c-9e71-29e1f453bf97 | ip | 10.0.0.0/24 | rw | active |
| f151ad17-654d-40ce-ba5d-98a5df67aadc | ip | 20.0.0.0/24 | ro | active |
+--------------------------------------+-------------+-------------+--------------+--------+

9. To create a snapshot of a share

$ manila snapshot-create --name mysnapshot --description "My Manila snapshot" myshare
+-------------------+--------------------------------------+
| Property | Value |
+-------------------+--------------------------------------+
| status | creating |
| share_id | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 |
| description | My Manila snapshot |
| created_at | 2016-03-24T14:39:58.232844 |
| share_proto | NFS |
| provider_location | None |
| id | e744ca47-0931-4e81-9d9f-2ead7d7c1640 |
| size | 1 |
| share_size | 1 |
| name | mysnapshot |
+-------------------+--------------------------------------+

We can check the snapshot details from list snapshot command

$ manila snapshot-list
+--------------------------------------+--------------------------------------+-----------+------------+------------+
| ID | Share ID | Status | Name | Share Size |
+--------------------------------------+--------------------------------------+-----------+------------+------------+
| e744ca47-0931-4e81-9d9f-2ead7d7c1640 | 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | available | mysnapshot | 1 |
+--------------------------------------+--------------------------------------+-----------+------------+------------+

10. To create a share from the snapshot

$ manila create NFS 1 \
--snapshot-id e744ca47-0931-4e81-9d9f-2ead7d7c1640 \
--share-network mysharenetwork \
--name mysharefromsnap
+-----------------------------+--------------------------------------+
| Property | Value |
+-----------------------------+--------------------------------------+
| status | creating |
| share_type_name | default |
| description | None |
| availability_zone | nova |
| share_network_id | c895fe26-92be-4152-9e6c-f2ad230efb13 |
| share_server_id | None |
| host | nosb-devstack@london#LONDON |
| access_rules_status | active |
| snapshot_id | e744ca47-0931-4e81-9d9f-2ead7d7c1640 |
| is_public | False |
| task_state | None |
| snapshot_support | True |
| id | e73ebcd3-4764-44f0-9b42-fab5cf34a58b |
| size | 1 |
| name | mysharefromsnap |
| share_type | bf6ada49-990a-47c3-88bc-c0cb31d5c9bf |
| has_replicas | False |
| replication_type | None |
| created_at | 2016-03-24T14:41:36.000000 |
| share_proto | NFS |
| consistency_group_id | None |
| source_cgsnapshot_member_id | None |
| project_id | 907004508ef4447397ce6741a8f037c1 |
| metadata | {} |
+-----------------------------+--------------------------------------+

List shares

$ manila list
+--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
| ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
+--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------+-------------------+
| 8d8b854b-ec32-43f1-acc0-1b2efa7c3400 | myshare | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
| e73ebcd3-4764-44f0-9b42-fab5cf34a58b | mysharefromsnap | 1 | NFS | available | False | default | nosb-devstack@london#LONDON | nova |
+--------------------------------------+-----------------+------+-------------+-----------+-----------+-----------------+-----------------------------

More commands will be provided on next session

Thank you for reading

Unixchips

Thursday, October 11, 2018

openstack command line administration PART-2 (glance/cinder/manila)

Manage Images (Glance)

Create images using nova

Below is the procedure for snapshot creation of an instance

Manage volumes (cinder)

Create and manage file shares using manila client

No comments:

Post a Comment