Acronis Acronis Cyber Infrastructure 3.0 User Manual

Acronis Cyber Infrastructure 3.0

Administrator’s Command Line Guide

November 20, 2019

”Acronis” and ”Acronis Secure Zone” are registered trademarks of Acronis International GmbH.

”Acronis Compute with Conﬁdence”, ”Acronis Startup Recovery Manager”, ”Acronis Instant Restore”, and the Acronis logo are trademarks of Acronis

International GmbH.

Linux is a registered trademark of Linus Torvalds.

VMware and VMware Ready are trademarks and/or registered trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Windows and MS-DOS are registered trademarks of Microsoft Corporation.

All other trademarks and copyrights referred to are the property of their respective owners.

Distribution of substantively modiﬁed versions of this document is prohibited without the explicit permission of the copyright holder.

Distribution of this work or derivative work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is

obtained from the copyright holder.

DOCUMENTATION IS PROVIDED ”AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED

WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT

SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Third party code may be provided with the Software and/or Service. The license terms for such third-parties are detailed in the license.txt ﬁle located in

the root installation directory. You can always ﬁnd the latest up-to-date list of the third party code and the associated license terms used with the

Software and/or Service at http://kb.acronis.com/content/7696.

Acronis patented technologies

Technologies, used in this product, are covered and protected by one or more U.S. Patent Numbers: 7,047,380; 7,246,211; 7,275,139; 7,281,104;

7,318,135; 7,353,355; 7,366,859; 7,383,327; 7,475,282; 7,603,533; 7,636,824; 7,650,473; 7,721,138; 7,779,221; 7,831,789; 7,836,053; 7,886,120; 7,895,403;

7,934,064; 7,937,612; 7,941,510; 7,949,635; 7,953,948; 7,979,690; 8,005,797; 8,051,044; 8,069,320; 8,073,815; 8,074,035; 8,074,276; 8,145,607; 8,180,984;

8,225,133; 8,261,035; 8,296,264; 8,312,259; 8,347,137; 8,484,427; 8,645,748; 8,732,121; 8,850,060; 8,856,927; 8,996,830; 9,213,697; 9,400,886; 9,424,678;

9,436,558; 9,471,441; 9,501,234; and patent pending applications.

Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Providing Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.2 Managing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Managing Storage Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1 Managing Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1.1 vinfra node token show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1.2 vinfra node token create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1.3 vinfra node token validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2 Managing Traﬃc Types and Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2.1 vinfra cluster traﬃc-type create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2.2 vinfra cluster traﬃc-type list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2.3 vinfra cluster traﬃc-type show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.4 vinfra cluster traﬃc-type set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.5 vinfra cluster traﬃc-type delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2.6 vinfra cluster network create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2.7 vinfra cluster network list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2.8 vinfra cluster network show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2.9 vinfra cluster network set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.2.10 vinfra cluster network set-bulk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.11 vinfra cluster network delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3 Managing Storage Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.1 vinfra node join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3.2 vinfra node list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3.3 vinfra node show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.4 vinfra node release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.5 vinfra node forget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4 Managing Node Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4.1 vinfra node iface list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4.2 vinfra node iface show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4.3 vinfra node iface up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.4.4 vinfra node iface down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.4.5 vinfra node iface set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.4.6 vinfra node iface create-bond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4.7 vinfra node iface create-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.4.8 vinfra node iface delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.5 Managing Node Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.5.1 vinfra node disk list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.5.2 vinfra node disk show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.5.3 vinfra node disk assign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.5.4 vinfra node disk release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.5.5 vinfra node disk blink on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.5.6 vinfra node disk blink oﬀ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.5.7 vinfra node iscsi target add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.5.8 vinfra node iscsi target delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.6 Creating and Deleting the Storage Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.6.1 vinfra cluster create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.6.2 vinfra cluster delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.7 Showing Storage Cluster Overview and Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.7.1 vinfra cluster overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.7.2 vinfra cluster show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3. Managing Compute Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.1 Creating and Deleting the Compute Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.1.1 vinfra service compute create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.1.2 vinfra service compute delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2 Showing Compute Cluster Details and Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.2.1 vinfra service compute show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.2.2 vinfra service compute stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.3 Changing Compute Cluster Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.4 Managing Compute Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.4.1 vinfra service compute node add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.4.2 vinfra service compute node list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.4.3 vinfra service compute node show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.4.4 vinfra service compute node fence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.4.5 vinfra service compute node unfence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.4.6 vinfra service compute node release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.5 Managing Virtual Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.5.1 vinfra service compute network create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.5.2 vinfra service compute network list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.5.3 vinfra service compute network show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.5.4 vinfra service compute network set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.5.5 vinfra service compute network delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.6 Managing Virtual Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.6.1 vinfra service compute router create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.6.2 vinfra service compute router list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.6.3 vinfra service compute router show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.6.4 vinfra service compute router set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.6.5 vinfra service compute router iface add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.6.6 vinfra service compute router iface list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.6.7 vinfra service compute router iface remove . . . . . . . . . . . . . . . . . . . . . . . . . . 61

3.6.8 vinfra service compute router delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3.7 Managing Floating IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3.7.1 vinfra service compute ﬂoatingip create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3.7.2 vinfra service compute ﬂoatingip list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

3.7.3 vinfra service compute ﬂoatingip show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3.7.4 vinfra service compute ﬂoatingip set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3.7.5 vinfra service compute ﬂoatingip delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3.8 Managing Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3.8.1 vinfra service compute image create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3.8.2 vinfra service compute image list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.8.3 vinfra service compute image show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.8.4 vinfra service compute image set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3.8.5 vinfra service compute image save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3.8.6 vinfra service compute image delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

3.9 Managing Flavors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

3.9.1 vinfra service compute ﬂavor create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

3.9.2 vinfra service compute ﬂavor list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

iii

3.9.3 vinfra service compute ﬂavor show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

3.9.4 vinfra service compute ﬂavor delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.10 Managing Storage Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.10.1 vinfra cluster storage-policy create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.10.2 vinfra cluster storage-policy list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

3.10.3 vinfra cluster storage-policy show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

3.10.4 vinfra cluster storage-policy set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

3.10.5 vinfra cluster storage-policy delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.11 Managing Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.11.1 vinfra service compute volume create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.11.2 vinfra service compute volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

3.11.3 vinfra service compute volume show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

3.11.4 vinfra service compute volume set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

3.11.5 vinfra service compute volume extend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

3.11.6 vinfra service compute volume delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3.12 Managing Volume Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3.12.1 vinfra service compute volume snapshot create . . . . . . . . . . . . . . . . . . . . . . . . 81

3.12.2 vinfra service compute volume snapshot list . . . . . . . . . . . . . . . . . . . . . . . . . . 82

3.12.3 vinfra service compute volume snapshot show . . . . . . . . . . . . . . . . . . . . . . . . 82

3.12.4 vinfra service compute volume snapshot set . . . . . . . . . . . . . . . . . . . . . . . . . . 83

3.12.5 vinfra service compute volume snapshot upload-to-image . . . . . . . . . . . . . . . . . 84

3.12.6 vinfra service compute volume snapshot revert . . . . . . . . . . . . . . . . . . . . . . . . 84

3.12.7 vinfra service compute volume snapshot reset-state . . . . . . . . . . . . . . . . . . . . . 85

3.12.8 vinfra service compute volume snapshot delete . . . . . . . . . . . . . . . . . . . . . . . . 86

3.13 Managing Compute SSH Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

3.13.1 vinfra service compute key create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

3.13.2 vinfra service compute key list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.13.3 vinfra service compute key show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.13.4 vinfra service compute key delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

3.14 Managing Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

3.14.1 vinfra service compute server create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

3.14.2 vinfra service compute server list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3.14.3 vinfra service compute server show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3.14.4 vinfra service compute server stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

3.14.5 vinfra service compute server set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

3.14.6 vinfra service compute server iface attach . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

3.14.7 vinfra service compute server iface list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

3.14.8 vinfra service compute server iface detach . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

3.14.9 vinfra service compute server volume attach . . . . . . . . . . . . . . . . . . . . . . . . . 96

3.14.10 vinfra service compute server volume list . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

3.14.11 vinfra service compute server volume show . . . . . . . . . . . . . . . . . . . . . . . . . . 97

3.14.12 vinfra service compute server volume detach . . . . . . . . . . . . . . . . . . . . . . . . . 97

3.14.13 vinfra service compute server log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

3.14.14 vinfra service compute server migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

3.14.15 vinfra service compute server resize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3.14.16 vinfra service compute server start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

3.14.17 vinfra service compute server pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

3.14.18 vinfra service compute server unpause . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

3.14.19 vinfra service compute server suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

3.14.20 vinfra service compute server resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

3.14.21 vinfra service compute server reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

3.14.22 vinfra service compute server reset-state . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

3.14.23 vinfra service compute server stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

3.14.24 vinfra service compute server shelve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

3.14.25 vinfra service compute server unshelve . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

3.14.26 vinfra service compute server evacuate . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

3.14.27 vinfra service compute server delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

4. Managing General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

4.1 Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

4.1.1 vinfra cluster license load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

4.1.2 vinfra cluster license show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

4.2 Managing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

4.2.1 vinfra domain create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4.2.2 vinfra domain list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

4.2.3 vinfra domain show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

4.2.4 vinfra domain set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

4.2.5 vinfra domain delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

4.3 Managing Domain Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

4.3.1 vinfra domain user create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

4.3.2 vinfra domain user list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

4.3.3 vinfra domain user show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

4.3.4 vinfra domain user set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

4.3.5 vinfra domain user delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

4.4 Managing Domain Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

4.4.1 vinfra domain project create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

4.4.2 vinfra domain project list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

4.4.3 vinfra domain project show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

4.4.4 vinfra domain project set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

4.4.5 vinfra domain project user list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

4.4.6 vinfra domain project user remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

4.4.7 vinfra domain project delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

4.5 Managing SSH Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

4.5.1 vinfra cluster sshkey add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

4.5.2 vinfra cluster sshkey list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

4.5.3 vinfra cluster sshkey delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

4.6 Managing External DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

4.6.1 vinfra cluster settings dns show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

4.6.2 vinfra cluster settings dns set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

4.7 Conﬁguring Management Node High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

4.7.1 vinfra cluster ha create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

4.7.2 vinfra cluster ha update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

4.7.3 vinfra cluster ha show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

4.7.4 vinfra cluster ha delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

4.8 Managing Storage Tier Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

4.8.1 vinfra cluster settings encryption show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

4.8.2 vinfra cluster settings encryption set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

4.9 Managing Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

4.9.1 vinfra cluster alert list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

4.9.2 vinfra cluster alert show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

4.9.3 vinfra cluster alert delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

4.10 Managing Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

4.10.1 vinfra cluster auditlog list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

4.10.2 vinfra cluster auditlog show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

4.11 Sending Problem Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

5. Monitoring Storage Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

5.1 Monitoring General Storage Cluster Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

5.2 Monitoring Metadata Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

5.3 Monitoring Chunk Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

5.3.1 Understanding Disk Space Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

5.3.1.1 Understanding Allocatable Disk Space . . . . . . . . . . . . . . . . . . . . . . .142

5.3.1.2 Viewing Space Occupied by Data Chunks . . . . . . . . . . . . . . . . . . . . . .143

5.3.2 Exploring Chunk States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

5.4 Monitoring Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

5.5 Monitoring Physical Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

5.6 Monitoring Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

5.7 Monitoring Replication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

6. Accessing Storage Clusters via iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

6.1 iSCSI Workﬂow Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

6.1.1 Managing Legacy iSCSI Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

6.2 Conﬁguring CLI Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

6.3 Managing Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

6.3.1 Creating Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

6.3.2 Starting and Stopping Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

6.3.3 Listing Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

6.3.4 Printing Details of Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

6.3.5 Deleting Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

6.4 Managing iSCSI Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

6.4.1 Creating iSCSI Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

6.4.2 Listing and Printing Details of iSCSI Volumes . . . . . . . . . . . . . . . . . . . . . . . . . .161

6.4.3 Attaching iSCSI Volumes to Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . .161

6.4.4 Viewing and Setting iSCSI Volume Parameters . . . . . . . . . . . . . . . . . . . . . . . . .162

6.4.5 Increasing iSCSI Volume Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

6.4.6 Setting iSCSI Volume Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

6.4.7 Detaching iSCSI Volumes from Target Groups . . . . . . . . . . . . . . . . . . . . . . . . .162

6.4.8 Deleting iSCSI Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

6.5 Managing Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

6.5.1 Adding Nodes to Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

6.5.2 Setting Node Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

6.5.3 Deleting Nodes from Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

6.6 Managing Targets and Portals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

vii

6.6.1 Creating Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

6.6.2 Adding and Removing Target Portals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

6.6.3 Deleting Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

6.7 Managing CHAP Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

6.7.1 Creating and Listing CHAP Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

6.7.2 Changing CHAP Account Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

6.7.3 Assigning CHAP Accounts to Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . .167

6.7.4 Deleting CHAP Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

6.8 Managing LUN Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

6.8.1 Creating LUN Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

6.8.2 Listing LUN Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

6.8.3 Changing LUN View Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

6.8.4 Deleting LUN Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

7. Advanced Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

7.1 Updating Kernel with ReadyKernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

7.1.1 Installing ReadyKernel Patches Automatically . . . . . . . . . . . . . . . . . . . . . . . . .171

7.1.2 Managing ReadyKernel Patches Manually . . . . . . . . . . . . . . . . . . . . . . . . . . .171

7.1.2.1 Downloading, Installing, and Loading ReadyKernel Patches . . . . . . . . . . .171

7.1.2.2 Loading and Unloading ReadyKernel Patches . . . . . . . . . . . . . . . . . . .171

7.1.2.3 Installing and Removing ReadyKernel Patches for Speciﬁc Kernels . . . . . . . 172

7.1.2.4 Downgrading ReadyKernel Patches . . . . . . . . . . . . . . . . . . . . . . . . .172

7.1.2.5 Disabling Loading of ReadyKernel Patches on Boot . . . . . . . . . . . . . . . .173

7.1.2.6 Managing ReadyKernel Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

7.2 Managing Guest Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

7.2.1 Installing Guest Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

7.2.1.1 Installing Guest Tools in New VMs . . . . . . . . . . . . . . . . . . . . . . . . . .174

7.2.1.2 Installing Guest Tools in Existing VMs . . . . . . . . . . . . . . . . . . . . . . . .175

7.2.2 Uninstalling Guest Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

7.2.2.1 Uninstalling Guest Tools from Linux VMs . . . . . . . . . . . . . . . . . . . . . .177

7.2.2.2 Uninstalling Guest Tools from Windows VMs . . . . . . . . . . . . . . . . . . . 177

7.3 Running Commands in Virtual Machines without Network Connectivity . . . . . . . . . . . . . . . 178

7.3.1 Running Commands in Linux Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . .178

7.3.2 Running Commands in Windows Virtual Machines . . . . . . . . . . . . . . . . . . . . . .179

7.4 Setting Virtual Machines CPU Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

7.5 Creating Linux Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

viii

7.6 Creating SSH-Enabled Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

7.6.1 Creating SSH-Enabled Linux Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

7.6.2 Creating SSH-Enabled Windows Templates . . . . . . . . . . . . . . . . . . . . . . . . . . .182

7.7 Securing OpenStack API Traﬃc with SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

7.8 Enabling Metering for Compute Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

7.9 Conﬁguring Memory Policy for Storage Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

7.9.1 vinfra memory-policy vstorage-services per-cluster change . . . . . . . . . . . . . . . . .191

7.9.2 vinfra memory-policy vstorage-services per-cluster show . . . . . . . . . . . . . . . . . .192

7.9.3 vinfra memory-policy vstorage-services per-cluster reset . . . . . . . . . . . . . . . . . .192

7.9.4 vinfra memory-policy vstorage-services per-node change . . . . . . . . . . . . . . . . . .193

7.9.5 vinfra memory-policy vstorage-services per-node show . . . . . . . . . . . . . . . . . . . 194

7.9.6 vinfra memory-policy vstorage-services per-node reset . . . . . . . . . . . . . . . . . . .195

CHAPTER 1

Introduction

This guide describes the syntax and parameters of the vinfra command-line tool that can be used to manage

Acronis Cyber Infrastructure from console and automate such management tasks.

Note: While the following chapters provide information on speciﬁc operations that you can perform with

vinfra, you can also run vinfra help to get a list of all supported commands and their descriptions. For help

on a speciﬁc command, either run vinfra help <command> or vinfra <command> --help.

In addition, this guide describes how to use the command line to perform operations unsupported by vinfra

as of now.

Note that the following operations should not be done from the command line:

• setting custom paths for Acronis Cyber Infrastructure services, in particular:

•

creating S3 clusters only in /mnt/vstorage/vols/s3

•

creating iSCSI targets only in /mnt/vstorage/vols/iscsi

• mounting clusters or change cluster mount options

• conﬁguring ﬁrewall with firewall-cmd

• renaming network connections

• managing MDS/CS

• managing partitions, LVMs, or software RAID

• modifying ﬁles in /mnt/vstorage/vols and /mnt/vstorage/webcp/backup directories

Chapter 1. Introduction

• setting encoding or replication of cluster root

1.1 Providing Credentials

The vinfra CLI tool requires the following information:

• IP address or hostname of the management node (set to backend-api.svc.vstoragedomain by default).

• Username (admin by default).

• Password (created during installation of Acronis Cyber Infrastructure).

This information can be supplied via the --vinfra-portal, --vinfra-username, and --vinfra-password

command-line parameters with each command. Alternatively, you can supply it by setting the environment

variables VINFRA_PORTAL, VINFRA_USERNAME, and VINFRA_PASSWORD (e.g., in your ~/.bash_profile). In this case,

you will be able to run the CLI tool without the aforementioned command-line parameters.

As you typically run vinfra from the management node as admin, the only variable you usually need to set is

the password. For example:

# export VINFRA_PASSWORD=12345

If you installed vinfra on a remote machine and/or run it as a diﬀerent user, you will need to set

VINFRA_PORTAL and/or VINFRA_USERNAME on that machine in addition to VINFRA_PASSWORD.

1.2 Managing Tasks

The vinfra CLI tool executes some commands immediately, while for other commands (that may take some

time to complete) it creates system tasks that are queued. Examples of actions performed via tasks are

creating the storage or compute cluster and adding nodes to it.

To keep track of tasks being performed by vinfra, use the vinfra task list and vinfra task show

commands. For example:

Chapter 1. Introduction

+--------------------------------------+---------+-----------------------------------------+ # vinfra task show 8fc27e7a-ba73-471d-9134-e351e1137cf4 +---------+----------------------------------------+ | Field | Value | +---------+----------------------------------------+ | args | - stor1 | | | - 7ffa9540-5a20-41d1-b203-e3f349d62565 | | | - null | | | - null | | kwargs | {} | | name | backend.tasks.cluster.CreateNewCluster | | result | cluster_id: 1 | | state | success | | task_id | 8fc27e7a-ba73-471d-9134-e351e1137cf4 | +---------+----------------------------------------+

CHAPTER 2

Managing Storage Cluster

2.1 Managing Tokens

2.1.1 vinfra node token show

Display the backend token:

usage: vinfra node token show

Example:

# vinfra node token show +-------+---------------+ | Field | Value | +-------+---------------+ | host | 10.37.130.101 | | token | dc56d4d2 | | ttl | 86398 | +-------+---------------+

This command shows the details of the current token.

2.1.2 vinfra node token create

Create the backend token:

usage: vinfra node token create [--ttl <ttl>]

--ttl <ttl>

Token TTL, in seconds

Chapter 2. Managing Storage Cluster

Example:

# vinfra node token create --ttl 86400 +-------+---------------+ | Field | Value | +-------+---------------+ | host | 10.37.130.101 | | token | dc56d4d2 | | ttl | 86398 | +-------+---------------+

This command creates a new token with the time to live (TTL) of 86400 seconds.

2.1.3 vinfra node token validate

Validate the backend token:

usage: vinfra node token validate <token>

<token>

Token value

Example:

This command validates the token dc56d4d2.

2.2 Managing Traﬃc Types and Networks

2.2.1 vinfra cluster traﬃc-type create

Create a new traﬃc type:

usage: vinfra cluster traffic-type create --port <port> <traffic-type-name>

--port <port>

Traﬃc type port

<traffic-type-name>

Traﬃc type name

Example:

This command creates a custom traﬃc type MyTrafficType on port 6900.

2.2.2 vinfra cluster traﬃc-type list

Chapter 2. Managing Storage Cluster

List available traﬃc types:

usage: vinfra cluster traffic-type list

Example:

This command lists all traﬃc types in Acronis Cyber Infrastructure.

2.2.3 vinfra cluster traﬃc-type show

Show details of a traﬃc type:

usage: vinfra cluster traffic-type show <traffic-type>

<traffic-type>

Traﬃc type name

Example:

Chapter 2. Managing Storage Cluster

This command shows the details of the traﬃc type Storage.

2.2.4 vinfra cluster traﬃc-type set

Modify traﬃc type parameters:

usage: vinfra cluster traffic-type set [--name <name>] [--port <port>] <traffic-type>

--name <name>

A new name for the traﬃc type

--port <port>

A new port for the traﬃc type

<traffic-type>

Traﬃc type name

Example:

# vinfra cluster traffic-type set "MyTrafficType" \

Chapter 2. Managing Storage Cluster

This command renames the traﬃc type MyTrafficType to MyOtherTrafficType and changes its port to 6901.

2.2.5 vinfra cluster traﬃc-type delete

Delete a traﬃc type:

usage: vinfra cluster traffic-type delete <traffic-type>

<traffic-type>

Traﬃc type name

Example:

# vinfra cluster traffic-type delete "MyOtherTrafficType" Operation successful

This command deletes the custom traﬃc type MyOtherTrafficType.

2.2.6 vinfra cluster network create

Create a new network:

usage: vinfra cluster network create [--traffic-types <traffic-types>] <network-name>

--traffic-types <traffic-types>

A comma-separated list of traﬃc type IDs or names

<network-name>

Network name

Example:

Chapter 2. Managing Storage Cluster

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

This command creates a custom network MyNet and assigns the traﬃc type SSH to it.

2.2.7 vinfra cluster network list

List available networks:

usage: vinfra cluster network list

Example:

This command lists all networks in Acronis Cyber Infrastructure.

2.2.8 vinfra cluster network show

Show details of a network:

usage: vinfra cluster network show <network>

Network ID or name

Example:

# vinfra cluster network show MyNet +-------+--------------------------------------+ | Field | Value | +-------+--------------------------------------+

This command shows the details of the custom network MyNet.

2.2.9 vinfra cluster network set

Modify network parameters:

usage: vinfra cluster network set [--name <network-name>]

[--traffic-types <traffic-types> |

--add-traffic-types <traffic-types> |

--del-traffic-types <traffic-types>] <network>

Chapter 2. Managing Storage Cluster

--name <network-name>

Network name

--traffic-types <traffic-types>

A comma-separated list of traﬃc type names (overwrites network’s current traﬃc types)

--add-traffic-types <traffic-types>

A comma-separated list of traﬃc type names (adds the speciﬁed traﬃc types to the network)

--del-traffic-types <traffic-types>

A comma-separated list of traﬃc type names (removes the speciﬁed traﬃc types from the network)

Network ID or name

Example:

This command creates a task to rename the network MyNet to MyOtherNet and assign to it the traﬃc types

iSCSI and NFS.

Task outcome:

Chapter 2. Managing Storage Cluster

| type: Custom

2.2.10 vinfra cluster network set-bulk

Modify traﬃc types of multiple networks:

usage: vinfra cluster network set-bulk --network <network>:<traffic-types>

--network <network>:<traffic-types>

Network conﬁguration in the format:

• <network>: network ID or name.

• <traffic-types>: a comma-separated list of traﬃc type names (this option can be used multiple

times).

Example:

This command creates a task to change the traﬃc type set of the network MyNet1 to SNMP and that of MyNet2 to

SSH and SNMP.

Chapter 2. Managing Storage Cluster

Task outcome:

2.2.11 vinfra cluster network delete

Delete a network:

usage: vinfra cluster network delete <network>

Network ID or name

Example:

# vinfra cluster network delete MyOtherNet Operation successful

This command deletes the network MyOtherNet.

2.3 Managing Storage Nodes

2.3.1 vinfra node join

Join a node to the storage cluster:

Chapter 2. Managing Storage Cluster

usage: vinfra node join [--disk <disk>:<role>[:<key=value,...>]] <node>

--disk <disk>:<role> [:<key=value,...>]

Disk conﬁguration in the format:

• <disk>: disk device ID or name

• <role>: disk role (cs, mds, journal, mds-journal, mds-system, cs-system, system)

• comma-separated key=value pairs with keys (optional):

•

tier: disk tier (0, 1, 2 or 3)

•

journal-tier: journal (cache) disk tier (0, 1, 2 or 3)

•

journal-type: journal (cache) disk type (no_cache, inner_cache or external_cache)

•

journal-disk: journal (cache) disk ID or device name

•

journal-size: journal (cache) disk size, in bytes

•

bind-address: bind IP address for the metadata service

E.g., sda:cs:tier=0,journal-type=inner_cache. This option can be used multiple times.

<node>

Node ID or hostname

Example:

# vinfra node join f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 \

--disk sda:mds-system \

--disk sdb:cs \

This command creates a task to add the node with the ID f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 to the

storage cluster and assigns roles to disks: mds-system to sda, cs to sdb and sdc.

Task outcome:

# vinfra task show a2713068-9544-4ea1-8ec8-69a068cf86f2 +---------+--------------------------------------------+ | Field | Value | +---------+--------------------------------------------+

| args | - f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 | | | - 1 | | kwargs | disks: | | | - id: 85F32403-94A9-465A-9E6C-C1A2B41294FC | | | role: mds-system | | | service_params: {} | | | - id: FE0B5876-E054-489B-B0FD-72429BEFD46A | | | role: cs | | | service_params: {} | | | - id: D3BEF4BB-AA3B-4DB6-9376-BC7CDA636700 | | | role: cs | | | service_params: {} | | name | backend.tasks.node.AddNodeInClusterTask | | result | {} | | state | success | | task_id | a2713068-9544-4ea1-8ec8-69a068cf86f2 | +---------+--------------------------------------------+

2.3.2 vinfra node list

Chapter 2. Managing Storage Cluster

List storage nodes:

usage: vinfra node list

Example:

This command lists all nodes registered in Acronis Cyber Infrastructure (both unassigned and used in the

storage cluster).

2.3.3 vinfra node show

Show storage node details:

usage: vinfra node show <node>

<node>

Node ID or hostname

Example:

Chapter 2. Managing Storage Cluster

This command shows the details of the node with the ID 4f96acf5-3bc8-4094-bcb6-4d1953be7b55.

2.3.4 vinfra node release

Release a node from the storage cluster. Start data migration from the node as well as cluster replication and

rebalancing to meet the conﬁgured redundancy level:

usage: vinfra node release [--force] <node>

--force

Release node without data migration

<node>

Node ID or hostname

Chapter 2. Managing Storage Cluster

Example:

This command creates a task to release the node with the ID f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 from the

storage cluster with migration of data to maintain the set redundancy mode.

Task outcome:

# vinfra task show c2a653a2-8991-4b3a-8bdf-5c0872aa75b3 +---------+----------------------------------------+ | Field | Value | +---------+----------------------------------------+ | args | - f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 | | | - false | | kwargs | {} | | name | backend.tasks.node.ReleaseNodeTask | | state | success | | task_id | c2a653a2-8991-4b3a-8bdf-5c0872aa75b3 | +---------+----------------------------------------+

2.3.5 vinfra node forget

Remove a node from the storage cluster:

usage: vinfra node forget <node>

<node>

Node ID or hostname

Example:

This command creates a task to unregister the node with the ID fd1e46de-6e17-4571-bf6b-1ac34ec1c225 from

Acronis Cyber Infrastructure.

Task outcome:

Chapter 2. Managing Storage Cluster

# vinfra task show 0eac3b74-e8f5-4974-9efe-a9070187d83c +---------+----------------------------------------+ | Field | Value | +---------+----------------------------------------+ | args | - fd1e46de-6e17-4571-bf6b-1ac34ec1c225 | | kwargs | {} | name | backend.tasks.node.DeleteNodeTask | | state | success | | task_id | 0eac3b74-e8f5-4974-9efe-a9070187d83c | +---------+----------------------------------------+

2.4 Managing Node Network Interfaces

2.4.1 vinfra node iface list

List node network interfaces:

usage: vinfra node iface list [-a | --node <node>]

-a, --all

List all network interfaces on all nodes

--node <node>

Node ID or hostname to list network interfaces on (default: node001.vstoragedomain)

Example:

This command shows network interfaces of the node with the ID 4f96acf5-3bc8-4094-bcb6-4d1953be7b55.

# vinfra node iface list --node 4f96acf5-3bc8-4094-bcb6-4d1953be7b55 +------+--------------------------------------+--------------------+-------+---------+ | name | node_id | ipv4 | state | network | +------+--------------------------------------+--------------------+-------+---------+ | eth0 | 4f96acf5-3bc8-4094-bcb6-4d1953be7b55 | - 10.94.29.218/16 | up | Public | | eth1 | 4f96acf5-3bc8-4094-bcb6-4d1953be7b55 | - 10.37.130.101/24 | up | Private | +------+--------------------------------------+--------------------+-------+---------+

2.4.2 vinfra node iface show

Show details of a network interface:

usage: vinfra node iface show [--node <node>] <iface>

Chapter 2. Managing Storage Cluster

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

<iface>

Network interface name

Example:

This command shows the details of the network interface eth0 located on the node with the ID

Chapter 2. Managing Storage Cluster

4f96acf5-3bc8-4094-bcb6-4d1953be7b55.

2.4.3 vinfra node iface up

Bring a network interface up:

usage: vinfra node iface up [--node <node>] <iface>

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

<iface>

Network interface name

Example:

Chapter 2. Managing Storage Cluster

This command brings up the network interface eth2 located on the node with the ID

4f96acf5-3bc8-4094-bcb6-4d1953be7b55.

2.4.4 vinfra node iface down

Bring a network interface down:

usage: vinfra node iface down [--node <node>] <iface>

--node <node>

Node ID or hostname

<iface>

Network interface name

Example:

Chapter 2. Managing Storage Cluster

This command brings down the network interface eth2 located on the node with the ID

4f96acf5-3bc8-4094-bcb6-4d1953be7b55.

2.4.5 vinfra node iface set

Modify network interface parameters (overwrite the omitted options with the default values for the interface):

usage: vinfra node iface set [--ipv4 <ipv4>] [--ipv6 <ipv6>] [--gw4 <gw4>] [--gw6 <gw6>]

--ipv4 <ipv4>

A comma-separated list of IPv4 addresses

--ipv6 <ipv6>

A comma-separated list of IPv6 addresses

--gw4 <gw4>

Gateway IPv4 address

--gw6 <gw6>

Gateway IPv6 address

--mtu <mtu>

MTU interface value

--dhcp4

Enable DHCPv4

--no-dhcp4

Disable DHCPv4

--dhcp6

Enable DHCPv6

--no-dhcp6

Disable DHCPv6

Chapter 2. Managing Storage Cluster

--auto-routes-v4

Enable automatic IPv4 routes

--ignore-auto-routes-v4

Ignore automatic IPv4 routes

--auto-routes-v6

Enable automatic IPv6 routes

--ignore-auto-routes-v6

Ignore automatic IPv6 routes

--network <network>

Network ID or name

--no-network

Remove a network from the interface

--connected-mode

Enable connected mode (InﬁniBand interfaces only)

--datagram-mode

Enable datagram mode (InﬁniBand interfaces only)

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

Chapter 2. Managing Storage Cluster

<iface>

Network interface name

Example:

# vinfra node iface set eth2 --network Private \

This command creates a task to assign the network interface eth2 located on the node with the ID

4f96acf5-3bc8-4094-bcb6-4d1953be7b55 to the network Private.

Task outcome:

Chapter 2. Managing Storage Cluster

2.4.6 vinfra node iface create-bond

Create a network bonding:

usage: vinfra node iface create-bond [--ipv4 <ipv4>] [--ipv6 <ipv6>] [--gw4 <gw4>]

[--gw6 <gw6>] [--mtu <mtu>] [--dhcp4 | --no-dhcp4] [--dhcp6 | --no-dhcp6] [--network <network>] [--auto-routes-v4 | --ignore-auto-routes-v4] [--auto-routes-v6 | --ignore-auto-routes-v6] [--bonding-opts <bonding_opts>] [--node <node>]

--bond-type <bond-type> --ifaces <ifaces>

--ipv4 <ipv4>

A comma-separated list of IPv4 addresses

--ipv6 <ipv6>

A comma-separated list of IPv6 addresses

--gw4 <gw4>

Gateway IPv4 address

--gw6 <gw6>

Gateway IPv6 address

--mtu <mtu>

MTU interface value

--dhcp4

Enable DHCPv4

--no-dhcp4

Disable DHCPv4

--dhcp6

Enable DHCPv6

--no-dhcp6

Disable DHCPv6

--auto-routes-v4

Enable automatic IPv4 routes

--ignore-auto-routes-v4

Ignore automatic IPv4 routes

--auto-routes-v6

Enable automatic IPv6 routes

Chapter 2. Managing Storage Cluster

--ignore-auto-routes-v6

Ignore automatic IPv6 routes

--network <network>

Network ID or name

--bonding-opts <bonding_opts>

Additional bonding options

--bond-type <bond-type>

Bond type (balance-rr, active-backup, balance-xor, broadcast, 802.3ad, balance-tlb, balance-alb)

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

--ifaces <ifaces>

A comma-separated list of network interface names, e.g., iface1,iface2,...,iface<N>

Example:

# vinfra node iface create-bond --ifaces eth2,eth3 --bond-type balance-xor \

Chapter 2. Managing Storage Cluster

This command creates a task to bond network interfaces eth2 and eth3 into bond0 of the type balance-xor on

the node with the ID fd1e46de-6e17-4571-bf6b-1ac34ec1c225.

Task outcome:

Chapter 2. Managing Storage Cluster

2.4.7 vinfra node iface create-vlan

Create a VLAN:

usage: vinfra node iface create-vlan [--ipv4 <ipv4>] [--ipv6 <ipv6>] [--gw4 <gw4>]

--ipv4 <ipv4>

A comma-separated list of IPv4 addresses

--ipv6 <ipv6>

A comma-separated list of IPv6 addresses

--gw4 <gw4>

Gateway IPv4 address

--gw6 <gw6>

Gateway IPv6 address

--mtu <mtu>

MTU interface value

--dhcp4

Enable DHCPv4

--no-dhcp4

Disable DHCPv4

--dhcp6

Enable DHCPv6

--no-dhcp6

Disable DHCPv6

--auto-routes-v4

Enable automatic IPv4 routes

--ignore-auto-routes-v4

Ignore automatic IPv4 routes

--auto-routes-v6

Enable automatic IPv6 routes

--ignore-auto-routes-v6

Ignore automatic IPv6 routes

--network <network>

Network ID or name

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

--iface <iface>

Interface name

Chapter 2. Managing Storage Cluster

--tag <tag>

VLAN tag number

Example:

# vinfra node iface create-vlan --iface eth2 --tag 100 --dhcp4 \

This command creates a task to create a VLAN with the tag 100 on the network interface eth2 on the node

with the ID fd1e46de-6e17-4571-bf6b-1ac34ec1c225.

Task outcome:

Chapter 2. Managing Storage Cluster

2.4.8 vinfra node iface delete

Delete a network interface:

usage: vinfra node iface delete [--node <node>] <iface>

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

<iface>

Network interface name

Example:

Chapter 2. Managing Storage Cluster

This command creates a task to delete a VLAN interface eth1.100 from the node with the ID

fd1e46de-6e17-4571-bf6b-1ac34ec1c225.

Task outcome:

2.5 Managing Node Disks

2.5.1 vinfra node disk list

List node disks:

usage: vinfra node disk list [-a | --node <node>]

-a, --all

List disks on all nodes

--node <node>

Node ID or hostname to list disks on (default: node001.vstoragedomain)

Example:

# vinfra node disk list --node 94d58604-6f30-4339-8578-adb7903b7277 \

-c id -c node_id -c device -c used -c size -c role +----------------+----------------+--------+--------+-----------+------------+ | id | node_id | device | used | size | role | +----------------+----------------+--------+--------+-----------+------------+ | E0B7CE6F-<...> | 94d58604-<...> | sda | 5.5GiB | 239.1GiB | mds-system | | EAC7DF5D-<...> | 94d58604-<...> | sdb | 2.1GiB | 1007.8GiB | cs |

Chapter 2. Managing Storage Cluster

| 49D792CA-<...> | 94d58604-<...> | sdc | 2.1GiB | 1007.8GiB | cs | +----------------+----------------+--------+--------+-----------+------------+

This command lists disks on the node with the ID 94d58604-6f30-4339-8578-adb7903b7277. (The output is

abridged to ﬁt on page.)

2.5.2 vinfra node disk show

Show details of a disk:

usage: vinfra node disk show [--node <node>] <disk>

--node <node>

Node ID or hostname

<disk>

Disk ID or device name (default: node001.vstoragedomain)

Example:

# vinfra node disk show EAC7DF5D-9E60-4444-85F7-5CA5738399CC \

| 94d58604-6f30-4339-8578-adb7903b7277 |

| tier: 0

Chapter 2. Managing Storage Cluster

This command shows the details of the disk with the ID EAC7DF5D-9E60-4444-85F7-5CA5738399CC attached to

the node with the ID 94d58604-6f30-4339-8578-adb7903b7277.

2.5.3 vinfra node disk assign

Add multiple disks to the storage cluster:

usage: vinfra node disk assign --disk <disk>:<role>[:<key=value,...>]

[--node <node>]

--disk <disk>:<role>[:<key=value,...>]

Disk conﬁguration in the format:

• <disk>: disk device ID or name

• <role>: disk role (cs, mds, journal, mds-journal, mds-system, cs-system, system)

• comma-separated key=value pairs with keys (optional):

•

tier: disk tier (0, 1, 2 or 3)

•

journal-tier: journal (cache) disk tier (0, 1, 2 or 3)

•

journal-type: journal (cache) disk type (no_cache, inner_cache or external_cache)

•

journal-disk: journal (cache) disk ID or device name

•

journal-size: journal (cache) disk size, in bytes

•

bind-address: bind IP address for the metadata service

E.g., sda:cs:tier=0,journal-type=inner_cache. This option can be used multiple times.

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

Example:

# vinfra node disk assign --disk sdc:cs --node f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 +---------+--------------------------------------+

Chapter 2. Managing Storage Cluster

This command creates a task to assign the role cs to the disk sdc on the node with the ID

f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4

Task outcome:

# vinfra task show 080337ba-0508-44a0-9363-eddcd9df9f0d +---------+------------------------------------------------------------------------------+ | Field | Value | +---------+------------------------------------------------------------------------------+ | args | [] | | kwargs | cluster_id: 1 | | | disks: | | | - id: D3BEF4BB-AA3B-4DB6-9376-BC7CDA636700 | | | role: cs | | | service_params: {} | | | logger: | | | __classname: backend.logger.tracer.TracingLogger | | | __dict: | | | prefix: POST /api/v2/1/nodes/f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4/disks/ | | | token: '3215629651314950' | | | node_id: f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4 | | name | backend.tasks.disks.BulkAssignDiskTask | | result | {} | | state | success | | task_id | 080337ba-0508-44a0-9363-eddcd9df9f0d | +---------+------------------------------------------------------------------------------+

2.5.4 vinfra node disk release

Release a disk from the storage cluster. Start data migration from the node as well as cluster replication and

rebalancing to meet the conﬁgured redundancy level:

usage: vinfra node disk release [--force] [--node <node>] <disk>

--force

Release without data migration

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

<disk>

Disk ID or device name

Chapter 2. Managing Storage Cluster

Example:

This command creates a task to release the role cs from the disk sdc on the node with the ID

f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4.

Task outcome:

2.5.5 vinfra node disk blink on

Start blinking the speciﬁed disk bay to identify disk for maintenance purposes:

usage: vinfra node disk blink on [--node <node>] <disk>

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

<disk>

Disk ID or device name

Example:

Chapter 2. Managing Storage Cluster

# vinfra node disk blink on sda --node f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4

This command starts blinking the disk sda on the node with the ID f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4.

2.5.6 vinfra node disk blink oﬀ

Stop blinking the speciﬁed disk bay:

usage: vinfra node disk blink off [--node <node>] <disk>

--node <node>

Node ID or hostname (default: node001.vstoragedomain)

<disk>

Disk ID or device name

Example:

# vinfra node disk blink off sda --node f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4

This command stops blinking the disk sda on the node with the ID f59dabdb-bd1c-4944-8af2-26b8fe9ff8d4.

2.5.7 vinfra node iscsi target add

Add an iSCSI target as a disk to a node:

usage: vinfra node iscsi target add [--auth-username <auth-username>]

[--auth-password <auth-password>]

--portal <portal> --node <node> <target-name>

--auth-username <auth-username>

User name

--auth-password <auth-password>

User password

--portal <portal>

Portal IP address in the format IP:port (this option can be speciﬁed multiple times)

--node <node>

Node ID or hostname

Chapter 2. Managing Storage Cluster

<target-name>

Target name

Example:

# vinfra node iscsi target add iqn.2014-06.com.vstorage:target1 \

This command creates a task to connect a remote iSCSI target iqn.2014-06.com.vstorage:target1 with the IP

address 172.16.24.244 and port 3260 to the node with the ID f1931be7-0a01-4977-bfef-51a392adcd94.

Task outcome:

2.5.8 vinfra node iscsi target delete

Delete an iSCSI target from a node:

usage: vinfra node iscsi target delete --node <node> <target-name>

--node <node>

Node ID or hostname

Chapter 2. Managing Storage Cluster

<target-name>

Target name

Example:

# vinfra node iscsi target delete iqn.2014-06.com.vstorage:target1 \

This command creates a task to disconnect a remote iSCSI target iqn.2014-06.com.vstorage:target1 from the

node with the ID f1931be7-0a01-4977-bfef-51a392adcd94.

Task outcome:

2.6 Creating and Deleting the Storage Cluster

2.6.1 vinfra cluster create

Create a storage cluster:

usage: vinfra cluster create [--disk <disk>:<role>[:<key=value,...>]]

[--tier-encryption {0,1,2,3}] --node <node> <cluster-name>

--disk <disk>:<role> [:<key=value,...>]

Disk conﬁguration in the format:

• <disk>: disk device ID or name

• <role>: disk role (cs, mds, journal, mds-journal, mds-system, cs-system, system)

• comma-separated key=value pairs with keys (optional):

Chapter 2. Managing Storage Cluster

•

tier: disk tier (0, 1, 2 or 3)

•

journal-tier: journal (cache) disk tier (0, 1, 2 or 3)

•

journal-type: journal (cache) disk type (no_cache, inner_cache or external_cache)

•

journal-disk: journal (cache) disk ID or device name

•

journal-size: journal (cache) disk size, in bytes

•

bind-address: bind IP address for the metadata service

E.g., sda:cs:tier=0,journal-type=inner_cache. This option can be used multiple times.

--tier-encryption {0,1,2,3}

Enable encryption for storage cluster tiers. Encryption is disabled by default. This option can be used

multiple times.

--node <node>

Node ID or hostname

<cluster-name>

Storage cluster name

Example:

This command creates a task to create the storage cluster stor1 on the node with the ID

94d58604-6f30-4339-8578-adb7903b7277. As disk roles are not explicitly speciﬁed, they are assigned

automatically: mds-system to the system disk, and cs to all other disks.

Task outcome:

| - null

| kwargs | {} |

2.6.2 vinfra cluster delete

Delete the storage cluster:

usage: vinfra cluster delete

Example:

# vinfra cluster delete Operation waiting (timeout=600s) [Elapsed Time: 0:01:09] ... | Operation successful

Chapter 2. Managing Storage Cluster

This command releases all nodes from the storage cluster.

2.7 Showing Storage Cluster Overview and Details

2.7.1 vinfra cluster overview

Show storage cluster overview:

usage: vinfra cluster overview

Example:

Chapter 2. Managing Storage Cluster

This command shows an overview of the cluster.

2.7.2 vinfra cluster show

Show cluster details:

usage: vinfra cluster show

Example:

Chapter 2. Managing Storage Cluster

This command shows cluster details.

CHAPTER 3

Managing Compute Cluster

3.1 Creating and Deleting the Compute Cluster

3.1.1 vinfra service compute create

Create a compute cluster:

usage: vinfra service compute create [--public-network <network>]

[--subnet cidr=CIDR[,key=value,...]] [--cpu-model <cpu-model>] [--force] [--enable-metering] --nodes <nodes>

--public-network <network>

A physical network to connect the public virtual network to. It must include the ‘VM public’ traﬃc type.

--subnet cidr=CIDR[,key=value,...]

Subnet for IP address management in the public virtual network (the --public-network option is

required):

• cidr: subnet range in CIDR notation;

• comma-separated key=value pairs with keys (optional):

•

gateway: gateway IP address.

•

dhcp: enable/disable the virtual DHCP server.

•

allocation-pool: allocation pool of IP addresses from CIDR in the format ip1-ip2, where ip1

and ip2 are starting and ending IP addresses. Specify the key multiple times to create multiple

IP pools.

•

dns-server: DNS server IP address, specify multiple times to set multiple DNS servers.

Example: --subnet cidr=192.168.5.0/24,dhcp=enable.

--cpu-model <cpu-model>

CPU model for virtual machines.

--force

Skip checks for minimal hardware requirements.

--enable-metering

Enable metering services.

--nodes <nodes>

A comma-separated list of node IDs or hostnames.

Example:

# vinfra service compute create --virtual-ip 10.94.50.244 \

--nodes 7ffa9540-5a20-41d1-b203-e3f349d62565,\ 02ff64ae-5800-4090-b958-18b1fe8f5060,\ 6e8afc28-7f71-4848-bdbe-7c5de64c5013,\ 37c70bfb-c289-4794-8be4-b7a40c2b6d95,\ 827a1f4e-56e5-404f-9113-88748c18f0c2 --enable-nested \

--public-network Public --subnet cidr=10.94.0.0/16,dhcp=enable,\ gateway=10.94.0.1,allocation-pool=10.94.129.64-10.94.129.79,\ dns-server=10.30.0.27,dns-server=10.30.0.28 +---------+--------------------------------------+ | Field | Value | +---------+--------------------------------------+ | task_id | be517afa-fae0-457e-819c-f4d6399f3ae2 | +---------+--------------------------------------+

Chapter 3. Managing Compute Cluster

This command creates a task to create the compute cluster from ﬁve nodes speciﬁed by ID. It also speciﬁes

the virtual IP address (must belong to the network with the Compute API traﬃc type), the public network for

VMs, the gateway, the allocation pool of IP addresses to assign to VMs, and the DNS servers to use.

Task outcome:

Chapter 3. Managing Compute Cluster

3.1.2 vinfra service compute delete

Delete all nodes from the compute cluster:

usage: vinfra service compute delete

Example:

This command creates a task to release nodes from the compute cluster.

Task outcome:

# vinfra task show 063e8a15-fcfe-4629-865f-b5e5fa44b38f +---------+--------------------------------------------------------------+ | Field | Value | +---------+--------------------------------------------------------------+ | args | [] | | kwargs | {} | | name | backend.presentation.compute.tasks.DestroyComputeClusterTask | | state | success | | task_id | 063e8a15-fcfe-4629-865f-b5e5fa44b38f | +---------+--------------------------------------------------------------+

Chapter 3. Managing Compute Cluster

3.2 Showing Compute Cluster Details and Overview

3.2.1 vinfra service compute show

Display compute cluster details:

usage: vinfra service compute show

Example:

Chapter 3. Managing Compute Cluster

This command shows the status and capabilities of the compute cluster.

3.2.2 vinfra service compute stat

Display compute cluster statistics:

usage: vinfra service compute stat

Example:

Chapter 3. Managing Compute Cluster

This command shows the overview of the compute cluster.

3.3 Changing Compute Cluster Parameters

Change compute cluster parameters:

usage: vinfra service compute set [--cpu-model <cpu-model>] [--enable-metering]

--cpu-model <cpu-model>

Set the default CPU model for virtual machines (SandyBridge, IvyBridge, Haswell, Haswell-noTSX,

Broadwell, Broadwell-noTSX, Skylake-Client, Skylake-Server, HostPassthrough)

Chapter 3. Managing Compute Cluster

--enable-metering

Enable metering services.

Example:

# vinfra service compute set --cpu-model Haswell

This command sets the default CPU model for VMs to Haswell.

3.4 Managing Compute Nodes

3.4.1 vinfra service compute node add

Add a node to the compute cluster:

usage: vinfra service compute node add [--compute] [--controller] [--force] <node-id>

--compute

Compute node role

--controller

Compute controller node role

--force

Skip checks for minimal hardware requirements

<node-id>

ID or hostname of the compute node

Example:

This command creates a task to add the node with the ID 827a1f4e-56e5-404f-9113-88748c18f0c2 to the

compute cluster.

Task outcome:

Chapter 3. Managing Compute Cluster

3.4.2 vinfra service compute node list

List compute nodes:

usage: vinfra service compute node list

Example:

# vinfra service compute node list +--------------------------------------+-----------------------------------+-------+-----+ | id | hypervisor_hostname | state | vms | +--------------------------------------+-----------------------------------+-------+-----+ | 7ffa9540-5a20-41d1-b203-e3f349d62565 | stor-1.example.com.vstoragedomain | up | 1 | | 6e8afc28-7f71-4848-bdbe-7c5de64c5013 | stor-3.example.com.vstoragedomain | up | 1 | | 02ff64ae-5800-4090-b958-18b1fe8f5060 | stor-2.example.com.vstoragedomain | up | 1 | | 827a1f4e-56e5-404f-9113-88748c18f0c2 | stor-5.example.com.vstoragedomain | up | 0 | | 37c70bfb-c289-4794-8be4-b7a40c2b6d95 | stor-4.example.com.vstoragedomain | up | 1 | +--------------------------------------+-----------------------------------+-------+-----+

This command lists nodes in the compute cluster.

3.4.3 vinfra service compute node show

Display compute node details:

usage: vinfra service compute node show <node>

<node>

Node ID or hostname

Example:

Chapter 3. Managing Compute Cluster

| block_usage: 0

| physical:

| memory: 5773

This command shows the details of the compute node with the ID 7ffa9540-5a20-41d1-b203-e3f349d62565.

3.4.4 vinfra service compute node fence

Fence a compute node:

usage: vinfra service compute node fence <node>

<node>

Node ID or hostname

Example:

# vinfra service compute node fence e6255aed-d6e7-41b2-ba90-86164c1cd9a6 Operation successful

This command fences the node with the ID e6255aed-d6e7-41b2-ba90-86164c1cd9a6.

Chapter 3. Managing Compute Cluster

3.4.5 vinfra service compute node unfence

Unfence a compute node:

usage: vinfra service compute node unfence <node>

<node>

Node ID or hostname

Example:

# vinfra service compute node unfence e6255aed-d6e7-41b2-ba90-86164c1cd9a6 Operation successful

This command unfences the node with the ID e6255aed-d6e7-41b2-ba90-86164c1cd9a6.

3.4.6 vinfra service compute node release

Release a node from the compute cluster:

usage: vinfra service compute node release [--compute] [--controller] <node-id>

--compute

Compute node role

--controller

Compute controller node role

<node-id>

ID or hostname of the compute node

Example:

This command creates a task to release the node with the ID 827a1f4e-56e5-404f-9113-88748c18f0c2 from the

compute cluster.

Task outcome:

Chapter 3. Managing Compute Cluster

3.5 Managing Virtual Networks

3.5.1 vinfra service compute network create

Create a compute network:

usage: vinfra service compute network create [--dhcp | --no-dhcp]

[--dns-nameserver <dns-nameserver>] [--allocation-pool <allocation-pool>] [--gateway <gateway> | --no-gateway] [--ip-version <ip-version>] [--physical-network <physical-network>] [--cidr <cidr>] <network-name>

--dhcp

Enable DHCP

--no-dhcp

Disable DHCP

--dns-nameserver <dns-nameserver>

DNS server IP address. This option can be used multiple times.

--allocation-pool <allocation-pool>

Allocation pool to create inside the network in the format: ip_addr_start-ip_addr_end. This option can

be used multiple times.

--gateway <gateway>

Gateway IP address

--no-gateway

Do not conﬁgure a gateway for this network

--ip-version <ip-version>

Network IP version

--physical-network <physical-network>

A physical network to link to a public network

--cidr <cidr>

Subnet range in CIDR notation

<network-name>

Network name

Example:

# vinfra service compute network create myprivnet --type vxlan \

Chapter 3. Managing Compute Cluster

This command creates a private network myprivnet with the speciﬁc CIDR and gateway.

3.5.2 vinfra service compute network list

List compute networks:

usage: vinfra service compute network list

Example:

Chapter 3. Managing Compute Cluster

+----------------+-----------+-------+------------------+------------------------+ | 1bf2c9da-<...> | private | vxlan | 192.168.128.0/24 | - end: 192.168.128.254 | | | | | | start: 192.168.128.2 | | 3848fb5d-<...> | myprivnet | vxlan | 192.128.128.0/24 | - end: 192.128.128.254 | | | | | | start: 192.128.128.2 | | 417606ac-<...> | public | flat | 10.94.0.0/16 | - end: 10.94.129.79 | | | | | | start: 10.94.129.64 | +----------------+-----------+-------+------------------+------------------------+

This command lists networks used in the compute cluster. (The output is abridged to ﬁt on page.)

3.5.3 vinfra service compute network show

Display compute network details:

usage: vinfra service compute network show <network>

Network ID or name

Example:

This command shows the details of the network with the ID 417606ac-1dbe-426a-844d-e047831ddce9.

3.5.4 vinfra service compute network set

Modify compute network parameters:

Chapter 3. Managing Compute Cluster

usage: vinfra service compute network set [--dhcp | --no-dhcp]

[--dns-nameserver <dns-nameserver>] [--allocation-pool <allocation-pool>] [--gateway <gateway> | --no-gateway] [--name <name>] <network>

--dhcp

Enable DHCP

--no-dhcp

Disable DHCP

--dns-nameserver <dns-nameserver>

DNS server IP address. This option can be used multiple times.

--allocation-pool <allocation-pool>

Allocation pool to create inside the network in the format: ip_addr_start-ip_addr_end. This option can

be used multiple times.

--gateway <gateway>

Gateway IP address

--no-gateway

Do not conﬁgure a gateway for this network

--name <name>

A new name for the network

Network ID or name

Example:

This command disables DHCP for the private network myprivnet.

3.5.5 vinfra service compute network delete

Delete a compute network:

usage: vinfra service compute network delete <network>

Network ID or name

Chapter 3. Managing Compute Cluster

Example:

# vinfra service compute network delete myprivnet Operation successful

This command deletes the private network myprivnet.

3.6 Managing Virtual Routers

3.6.1 vinfra service compute router create

Create a virtual router:

usage: vinfra service compute router create [--external-gateway <network>]

[--enable-snat | --disable-snat] [--fixed-ip <fixid-ip>] [--internal-interface <network=network, ip-addr=ip-addr>|<network>] <router-name>

--external-gateway <network>

Specify a public network to be used as the router’s external gateway (name or ID)

--enable-snat

Enable source NAT on the external gateway

--disable-snat

Disable source NAT on the external gateway

--fixed-ip <fixid-ip>

Desired IP on the external gateway

--internal-interface <network=network,ip-addr=ip-addr>|<network>

Specify an internal interface. This option can be used multiple times.

• network: name of a private virtual network.

• ip-addr: an unused IP address from the selected private network to assign to the interface; specify

if the default gateway of the selected private network is in use.

<router-name>

Virtual router name

Example:

Chapter 3. Managing Compute Cluster

# vinfra service compute router create myrouter --external-gateway public \

This command creates a router myrouter between the public network public and the private network private

with enabled SNAT on the external gateway.

3.6.2 vinfra service compute router list

List virtual routers:

usage: vinfra service compute router list

Example:

Chapter 3. Managing Compute Cluster

This command lists virtual routers used in the compute cluster. (The output is abridged to ﬁt on page.)

| ip_addresses:

3.6.3 vinfra service compute router show

Display information about a virtual router:

usage: vinfra service compute router show <router>

Virtual router name

Example:

This command shows the details of the virtual router myrouter.

3.6.4 vinfra service compute router set

Modify virtual router parameters:

usage: vinfra service compute router set [--name <name>] [--external-gateway <network> |

--no-external-gateway] [--fixed-ip <fixed-ip>]

Chapter 3. Managing Compute Cluster

[--enable-snat | --disable-snat] [--route <destination=destination,nexthop=nexthop> |

--no-route] <router>

--name <name>

Virtual router name

--external-gateway <network>

Specify a public network to be used as the router’s external gateway (name or ID)

--no-external-gateway

Remove the external gateway from the router

--enable-snat

Enable source NAT on the external gateway

--disable-snat

Disable source NAT on the external gateway

--fixed-ip <fixed-ip>

Desired IP on the external gateway

--route <destination=destination,nexthop=nexthop>

A static route for the router. This option can be used multiple times.

• destination: destination subnet range in CIDR notation.

• nexthop: next hop IP address from one of the networks that the router is connected to.

--no-route

Clear routes associated with the router

Virtual router name or ID

Example:

Chapter 3. Managing Compute Cluster

This command disables SNAT on the external gateway of the virtual router myrouter.

3.6.5 vinfra service compute router iface add

Add an interface to a virtual router:

usage: vinfra service compute router iface add [--ip-address <ip-address>]

--interface <network> router

--ip-address <ip-address>

IP address

--interface <network>

Network name or ID

router

Virtual router name or ID

Example:

# vinfra service compute router iface add myrouter --interface private2 \

This command adds an interface from the virtual network private2 to the virtual router myrouter with the IP

address 192.168.30.3.

| - 10.94.129.76 | ACTIVE |

3.6.6 vinfra service compute router iface list

List router interfaces:

usage: vinfra service compute router iface list router

Chapter 3. Managing Compute Cluster

router

Virtual router name or ID

Example:

This command lists interfaces of the virtual router myrouter.

3.6.7 vinfra service compute router iface remove

Remove an interface from a virtual router:

usage: vinfra service compute router iface remove --interface <network> router

--interface <network>

Network name or ID

router

Virtual router name or ID

Example:

This command removes the interface from the virtual network private2 from the virtual router myrouter.

Chapter 3. Managing Compute Cluster

3.6.8 vinfra service compute router delete

Delete a virtual router:

usage: vinfra service compute router delete <router>

Virtual router ID or name

Example:

# vinfra service compute router delete myrouter Operation successful

This command deletes the virtual router myrouter.

3.7 Managing Floating IP Addresses

3.7.1 vinfra service compute ﬂoatingip create

Create a ﬂoating IP address:

usage: vinfra service compute floatingip create [--floating-ip-address <floating-ip-address>]

[--port-id <port-id>] [--fixed-ip-address <fixed-ip-address>] [--description description] --network <network>

--floating-ip-address <floating-ip-address>

Floating IP address

--port-id <port-id>

ID of the port to be associated with the ﬂoating IP address. To learn the port ID of the selected server,

use the command vinfra service compute server iface list (page 95).

--fixed-ip-address <fixed-ip-address>

Port IP address (required only if the port has multiple IP addresses)

--description description

Description of the ﬂoating IP address

--network <network>

ID or name of the network from which to allocate the ﬂoating IP

Chapter 3. Managing Compute Cluster

Example:

# vinfra service compute floatingip create 720e45bc-4225-49de-9346-26513d8d1262 \

This command creates a ﬂoating IP address from the public network with the ID

720e45bc-4225-49de-9346-26513d8d1262 and assigns it to a server on port with the ID

418c8c9e-aaa5-42f2-8da7-24bfead6f28b and the private IP address 192.168.128.5.

3.7.2 vinfra service compute ﬂoatingip list

List ﬂoating IP addresses:

usage: vinfra service compute floatingip list

Example:

# vinfra service compute floatingip list -c id -c fixed_ip_address -c port_id \

-c floating_ip_address -c floating_network_id +----------------+------------------+----------------+---------------------+---------------------+ | id | fixed_ip_address | port_id | floating_ip_address | floating_network_id | +----------------+------------------+----------------+---------------------+---------------------+ | a709f884-<...> | 192.168.128.5 | 418c8c9e-<...> | 10.94.129.72 | 720e45bc-<...> | +----------------+------------------+----------------+---------------------+---------------------+

This command lists ﬂoating IP addresses used in the compute cluster. (The output is abridged to ﬁt on page.)

Chapter 3. Managing Compute Cluster

3.7.3 vinfra service compute ﬂoatingip show

Display information about a ﬂoating IP address:

usage: vinfra service compute floatingip show <floatingip>

ID of the ﬂoating IP address

Example:

This command shows the details of the ﬂoating IP address with the ID a709f884-c43f-4a9a-a243-a340d7682ef8.

3.7.4 vinfra service compute ﬂoatingip set

Modify parameters of a ﬂoating IP address:

usage: vinfra service compute floatingip set [--port-id <port-id>]

[--fixed-ip-address <fixed-ip-address>] [--description <description>] <floatingip>

--port-id <port-id>

ID of the port to be associated with the ﬂoating IP address

--fixed-ip-address <fixed-ip-address>

Port IP address (required only if the port has multiple IP addresses)

--description <description>

Description of the ﬂoating IP address

Chapter 3. Managing Compute Cluster

ID of the ﬂoating IP address

Example:

# vinfra service compute floatingip set a709f884-c43f-4a9a-a243-a340d7682ef8 \

This command adds a description for the ﬂoating IP address with the ID

a709f884-c43f-4a9a-a243-a340d7682ef8.

3.7.5 vinfra service compute ﬂoatingip delete

Delete a ﬂoating IP address:

usage: vinfra service compute floatingip delete <floatingip>

ID of the ﬂoating IP address

Example:

# vinfra service compute floatingip delete a709f884-c43f-4a9a-a243-a340d7682ef8 Operation successful

This command deletes the ﬂoating IP address with the ID a709f884-c43f-4a9a-a243-a340d7682ef8.

Chapter 3. Managing Compute Cluster

3.8 Managing Images

3.8.1 vinfra service compute image create

Create a new compute image:

usage: vinfra service compute image create [--min-disk <size-gb>] [--min-ram <size-mb>]

[--os-distro <os-distro>] [--protected] [--disk-format <disk_format>] [--container-format <format>]

--file <file> <image-name>

--min-disk <size-gb>

Minimum disk size required to boot from image, in gigabytes

--min-ram <size-mb>

Minimum RAM size required to boot from image, in megabytes

--os-distro <os-distro>

OS distribution. To list available distributions, run service compute cluster show.

--protected

Protect image from deletion

--disk-format <disk_format>

Disk format aki, ami, ari, detect, iso, ploop, qcow2, raw, vdi, vhd, vhdx, vmdk (default: detect)

--container-format <format>

Container format: aki, ami, ari, bare, docker, ovf, ova (default: bare)

--file <file>

Create image from a local ﬁle

<image-name>

Image name

Example:

# vinfra service compute image create mycirrosimg \

--file /distr/cirros-0.4.0-x86_64-disk.img Uploading image to server [elapsed time: 0:00:04]... | +---------+--------------------------------------+ | Field | Value | +---------+--------------------------------------+

Chapter 3. Managing Compute Cluster

| task_id | 03874663-d03f-4891-a10b-64837e7faf43 | +---------+--------------------------------------+

This command creates a task to create a Cirros image from the local ﬁle and upload it to Acronis Cyber

Infrastructure.

Task outcome:

3.8.2 vinfra service compute image list

List compute images:

usage: vinfra service compute image list

Example:

This command lists images available to the compute cluster.

3.8.3 vinfra service compute image show

Display compute image details:

usage: vinfra service compute image show <image>

<image>

Image ID or name

Chapter 3. Managing Compute Cluster

Example:

| 0

| 12716032

This command shows the details of the default Cirros image.

3.8.4 vinfra service compute image set

Modify compute image parameters:

usage: vinfra service compute image set [--min-disk <size-gb>] [--min-ram <size-mb>]

[--os-distro <os-distro>] [--protected] [--name <name>] <image>

--min-disk <size-gb>

Minimum disk size required to boot from image, in gigabytes

--min-ram <size-mb>

Minimum RAM size required to boot from image, in megabytes

--os-distro <os-distro>

OS distribution. To list available distributions, run service compute cluster show.

--protected

Protect image from deletion

Chapter 3. Managing Compute Cluster

--name <name>

Image name

<image>

Image ID or name

Example:

This command protects the default Cirros image and sets the minimum RAM size for it to 1 GB.

3.8.5 vinfra service compute image save

Download a compute image:

usage: vinfra service compute image save [--file <filename>] <image>

--file <filename>

File to save the image to (default: stdout)

<image>

Image ID or name

Example:

Chapter 3. Managing Compute Cluster

# vinfra service compute image save 4741274f-5cca-4205-8f66-a2e89fb346cc --file cirros.qcow2 Operation successful

This command downloads the default Cirros image to the local disk as cirros.qcow2.

3.8.6 vinfra service compute image delete

Delete a compute image:

usage: vinfra service compute image delete <image>

<image>

Image ID or name

Example:

# vinfra service compute image delete 179f45ef-c5d6-4270-b0c0-085b542544c5 Operation successful

This command deletes the image with the ID 179f45ef-c5d6-4270-b0c0-085b542544c5.

3.9 Managing Flavors

3.9.1 vinfra service compute ﬂavor create

Create a new compute ﬂavor:

usage: vinfra service compute flavor create [--swap <size-mb>] --vcpus <vcpus>

--ram <size-mb> <flavor-name>

--swap <size-mb>

Swap space size, in megabytes

--vcpus <vcpus>

Number of virtual CPUs

--ram <size-mb>

Memory size, in megabytes

<flavor-name>

Flavor name

Example:

# vinfra service compute flavor create myflavor --vcpus 1 --ram 3072 +-------+--------------------------------------+ | Field | Value | +-------+--------------------------------------+ | id | 561a48ea-0c1c-4152-8b7d-e4b4af276c2d | | name | myflavor | | ram | 3072 | | swap | 0 | | vcpus | 1 | +-------+--------------------------------------+

This command creates a ﬂavor myflavor with 1 vCPU and 3 GB RAM.

3.9.2 vinfra service compute ﬂavor list

List compute ﬂavors:

Chapter 3. Managing Compute Cluster

usage: vinfra service compute flavor list

Example:

# vinfra service compute flavor list +--------------------------------------+----------+-------+------+-------+ | id | name | ram | swap | vcpus | +--------------------------------------+----------+-------+------+-------+ | 100 | tiny | 512 | 0 | 1 | | 101 | small | 2048 | 0 | 1 | | 102 | medium | 4096 | 0 | 2 | | 103 | large | 8192 | 0 | 4 | | 104 | xlarge | 16384 | 0 | 8 | | 561a48ea-0c1c-4152-8b7d-e4b4af276c2d | myflavor | 3072 | 0 | 1 | +--------------------------------------+----------+-------+------+-------+

This command lists all ﬂavors.

3.9.3 vinfra service compute ﬂavor show

Display compute ﬂavor details:

usage: vinfra service compute flavor show <flavor>

Flavor ID or name

Example:

# vinfra service compute flavor show myflavor +-------+--------------------------------------+ | Field | Value | +-------+--------------------------------------+ | id | 561a48ea-0c1c-4152-8b7d-e4b4af276c2d | | name | myflavor | ram | 3072 | | swap | 0 | | vcpus | 1 | +-------+--------------------------------------+

This command shows the details of the ﬂavor myflavor.

3.9.4 vinfra service compute ﬂavor delete

Delete a compute ﬂavor:

usage: vinfra service compute flavor delete <flavor>

Chapter 3. Managing Compute Cluster

Flavor ID or name

Example:

# vinfra service compute flavor delete myflavor Operation successful

This command deletes the ﬂavor myflavor.

3.10 Managing Storage Policies

You can manage storage policies only after creating the compute cluster.

3.10.1 vinfra cluster storage-policy create

Create a new storage policy:

usage: vinfra cluster storage-policy create --tier {0,1,2,3}

(--replicas <norm>[:<min>] |

--encoding <M>+<N>) --failure-domain {disk,host,rack,row,room} <name>

--tier {0,1,2,3}

Storage tier

--replicas <norm>[:<min>]

Storage replication mapping in the format:

• norm: the number of replicas to maintain

• min: the minimum required number of replicas (optional)

--encoding <M>+<N>

Storage erasure encoding mapping in the format:

• M: the number of data blocks

• N: the number of parity blocks

--failure-domain {disk,host,rack,row,room}

Chapter 3. Managing Compute Cluster

Storage failure domain

<name>

Storage policy name

Example:

# vinfra cluster storage-policy create mystorpolicy --tier 3 \

This command creates a storage policy mystorpolicy with the tier set to 3, redundancy scheme to erasure

coding 3+2, and failure domain set to host.

3.10.2 vinfra cluster storage-policy list

List existing storage policies:

usage: vinfra cluster storage-policy list

Chapter 3. Managing Compute Cluster

Example:

This command lists storage policies available to the compute cluster.

3.10.3 vinfra cluster storage-policy show

Show details of a storage policy:

usage: vinfra cluster storage-policy show <storage-policy>

<storage-policy>

Storage policy ID or name

Example:

This command shows the details of the storage policy mystorpolicy.

3.10.4 vinfra cluster storage-policy set

Modify storage policy parameters:

usage: vinfra cluster storage-policy set [--name <name>] [--tier {0,1,2,3}]

[--replicas <norm>[:<min>] |

--encoding <M>+<N>] [--failure-domain {disk,host,rack,row,room}] <storage-policy>

--name <name>

A new name for the storage policy

--tier {0,1,2,3}

Storage tier

--replicas <norm>[:<min>]

Storage replication mapping in the format:

• norm: the number of replicas to maintain

• min: the minimum required number of replicas (optional)

--encoding <M>+<N>

Storage erasure encoding mapping in the format:

• M: the number of data blocks

Chapter 3. Managing Compute Cluster

• N: the number of parity blocks

--failure-domain {disk,host,rack,row,room}

Storage failure domain

<storage-policy>

Storage policy ID or name

Example:

This command changes the redundancy type for the storage policy mystorpolicy from erasure coding 3+2 to

5+2.

3.10.5 vinfra cluster storage-policy delete

The default policy cannot be deleted.

Remove an existing storage policy:

usage: vinfra cluster storage-policy delete <storage-policy>

<storage-policy>

Storage policy ID or name

Example:

# vinfra cluster storage-policy delete mystorpolicy Operation successful

This command deletes the storage policy mystorpolicy.

Chapter 3. Managing Compute Cluster

3.11 Managing Volumes

3.11.1 vinfra service compute volume create

Create a new compute volume:

usage: vinfra service compute volume create [--description <description>]

[--network-install <network_install>] [--image <image>] [--snapshot <snapshot>]

--storage-policy <storage_policy>

--size <size-gb> <volume-name>

--description <description>

Volume description

--network-install <network_install>

Perform network installation (true or false).

--image <image>

Source compute image ID or name

--snapshot <snapshot>

Source compute volume snapshot ID or name

Chapter 3. Managing Compute Cluster

--storage-policy <storage_policy>

Storage policy ID or name

--size <size-gb>

Volume size, in gigabytes

<volume-name>

Volume name

Example:

This command creates a volume myvolume sized 8 GB and chooses the default storage policy for it.

Chapter 3. Managing Compute Cluster

3.11.2 vinfra service compute volume list

List compute volumes:

usage: vinfra service compute volume list

Example:

This command lists volumes available to the compute cluster. (The output is abridged to ﬁt on page.)

3.11.3 vinfra service compute volume show

Display compute volume details:

usage: vinfra service compute volume show <volume>

Volume ID or name

Example:

Chapter 3. Managing Compute Cluster

This command shows the details for the volume myvolume.

3.11.4 vinfra service compute volume set

Modify volume parameters:

usage: vinfra service compute volume set [--description <description>]

[--network-install <network_install>] [--storage-policy <storage_policy>] [--bootable <bootable>] [--name <name>] <volume>

--description <description>

Volume description

--network-install <network_install>

Perform network install (true or false)

--storage-policy <storage_policy>

Storage policy ID or name

--bootable <bootable>

Make bootable (true or false)

--name <name>

A new name for the volume

Volume ID or name

Example:

Chapter 3. Managing Compute Cluster

| nova

| c9c0e9e7-ce7a-4566-99d5-d7e40f2987ab

| stor-1.example.com.vstoragedomain@vstorage#vstorage |

This command changes the storage policy of the volume myvolume to mystorpolicy.

3.11.5 vinfra service compute volume extend

Extend a compute volume:

usage: vinfra service compute volume extend --size <size_gb> <volume>

Volume ID or name

Example:

# vinfra service compute volume extend myvolume --size 16 Operation successful

This command extends the volume myvolume to 16 GB.

3.11.6 vinfra service compute volume delete

Delete a compute volume:

usage: vinfra service compute volume delete <volume>

Volume ID or name

Example:

# vinfra service compute volume delete myvolume2 Operation successful

This command deletes the volume myvolume2.

Chapter 3. Managing Compute Cluster

3.12 Managing Volume Snapshots

3.12.1 vinfra service compute volume snapshot create

Create a snapshot of a volume:

usage: vinfra service compute volume snapshot create [--description <description>]

--volume <volume> <volume-snapshot-name>

--description <description>

Volume snapshot description

--volume <volume>

Volume ID or name

<volume-snapshot-name>

Volume snapshot name

Example:

Chapter 3. Managing Compute Cluster

| id | 3fdfe5d6-8bd2-4bf5-8599-a9cef50e5b71 | | metadata | {} | | name | mysnapshot | | project_id | fd0ae61496d04ef6bb637bc3167b7eaf | | size | 8 | | status | creating | | volume_id | 92dc3bd7-713d-42bf-83cd-4de40c24fed9 | +-------------+--------------------------------------+

This command initiates creation of a snapshot mysnapshot of the volume myvolume.

3.12.2 vinfra service compute volume snapshot list

List volume snapshots:

usage: vinfra service compute volume snapshot list

Example:

This command lists volume snapshots available to the compute cluster. (The output is abridged to ﬁt on

page.)

3.12.3 vinfra service compute volume snapshot show

Display details of a volume snapshot:

usage: vinfra service compute volume snapshot show <volume-snapshot>

<volume-snapshot>

Volume snapshot ID or name

Example:

Chapter 3. Managing Compute Cluster

| description | | | id | 3fdfe5d6-8bd2-4bf5-8599-a9cef50e5b71 | | metadata | {} | | name | mysnapshot | | project_id | fd0ae61496d04ef6bb637bc3167b7eaf | | size | 8 | | status | available | | volume_id | 92dc3bd7-713d-42bf-83cd-4de40c24fed9 | +-------------+--------------------------------------+

This command shows the details for the volume snapshot mysnapshot.

3.12.4 vinfra service compute volume snapshot set

Modify volume snapshot parameters:

usage: vinfra service compute volume snapshot set [--description <description>]

[--name <name>] <volume-snapshot>

--description <description>

Volume snapshot description

--name <name>

A new name for the volume snapshot

<volume-snapshot>

Volume snapshot ID or name

Example:

# vinfra service compute volume snapshot set mysnapshot --name mynewsnapshot +-------------+--------------------------------------+ | Field | Value | +-------------+--------------------------------------+ | created_at | 2019-04-30T13:12:54.297629+00:00 | | description | | | id | 3fdfe5d6-8bd2-4bf5-8599-a9cef50e5b71 | | metadata | {} | | name | mynewsnapshot | | project_id | fd0ae61496d04ef6bb637bc3167b7eaf | | size | 8 | | status | available | | volume_id | 92dc3bd7-713d-42bf-83cd-4de40c24fed9 | +-------------+--------------------------------------+

This command changes the name of the volume snapshot mysnapshot to mynewsnapshot.

Chapter 3. Managing Compute Cluster

3.12.5 vinfra service compute volume snapshot upload-to-image

Create a compute image from a compute volume snapshot:

usage: vinfra service compute volume snapshot upload-to-image [--name <name>]

<volume-snapshot>

--name <name>

Image name

<volume-snapshot>

Volume snapshot ID or name

Example:

This command creates the compute image myvm-image from the volume snapshot mynewsnapshot.

3.12.6 vinfra service compute volume snapshot revert

Revert a volume to the speciﬁed snapshot:

Chapter 3. Managing Compute Cluster

usage: vinfra service compute volume snapshot revert <volume-snapshot>

<volume-snapshot>

Volume snapshot ID or name

Example:

# vinfra service compute volume snapshot revert mynewsnapshot +-------------+--------------------------------------+ | Field | Value | +-------------+--------------------------------------+ | created_at | 2019-04-30T13:12:54.297629+00:00 | | description | | id | 3fdfe5d6-8bd2-4bf5-8599-a9cef50e5b71 | | metadata | {} | | name | mynewsnapshot | | project_id | fd0ae61496d04ef6bb637bc3167b7eaf | | size | 8 | | status | volume_id | 92dc3bd7-713d-42bf-83cd-4de40c24fed9 | +-------------+--------------------------------------+

| available

This command reverts the volume to its snapshot mynewsnapshot.

3.12.7 vinfra service compute volume snapshot reset-state

Reset a volume snapshot stuck in the “Error” state or one of transitional states to the “Available” state:

usage: vinfra service compute volume snapshot reset-state <volume-snapshot>

<volume-snapshot>

Volume snapshot ID or name

Example:

# vinfra service compute volume snapshot reset-state mynewsnapshot +-------------+--------------------------------------+ | Field | Value | +-------------+--------------------------------------+ | created_at | 2019-04-30T13:12:54.297629+00:00 | | description | | | id | 3fdfe5d6-8bd2-4bf5-8599-a9cef50e5b71 | | metadata | {} | | name | mynewsnapshot | | project_id | fd0ae61496d04ef6bb637bc3167b7eaf | | size | 8 | | status | available | | volume_id | 92dc3bd7-713d-42bf-83cd-4de40c24fed9 |

Chapter 3. Managing Compute Cluster

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

This command resets the state of the volume snapshot mynewsnapshot.

3.12.8 vinfra service compute volume snapshot delete

Delete a volume snapshot:

usage: vinfra service compute volume snapshot delete <volume-snapshot>

<volume-snapshot>

Volume snapshot ID or name

Example:

# vinfra service compute volume snapshot delete mynewsnapshot Operation successful

This command deletes the volume snapshot mynewsnapshot.

3.13 Managing Compute SSH Keys

3.13.1 vinfra service compute key create

Create a new compute SSH key:

usage: vinfra service compute key create --public-key <public-key>

[--description <description>] <ssh-key>

---public-key <public-key>

Filename for a public key to upload

--description <description>

SSH key description

<ssh-key>

SSH key name

Example:

# vinfra service compute key create publickey --public-key /root/.ssh/id_rsa.pub \

--description 'public key'

This command creates a public SSH key publickey.

3.13.2 vinfra service compute key list

List compute SSH keys:

usage: vinfra service compute key list

Example:

Chapter 3. Managing Compute Cluster

This command lists all SSH keys.

3.13.3 vinfra service compute key show

Display compute SSH key details:

usage: vinfra service compute key show <ssh-key>

<ssh-key>

SSH key name

Example:

Chapter 3. Managing Compute Cluster

| public_key_fingerprint | 1a:fb:de:d8:1e:0a:84:30:fc:ff:e4:fd:89:e7:96:a9 | +------------------------+-------------------------------------------------+

This command shows the details of the SSH key publickey.

3.13.4 vinfra service compute key delete

Delete a compute SSH key:

usage: vinfra service compute key delete <ssh-key>

<ssh-key>

SSH key name

Example:

# vinfra service compute key delete publickey Operation successful

This command deletes the SSH key publickey.

3.14 Managing Virtual Machines

3.14.1 vinfra service compute server create

Create a new compute server:

usage: vinfra service compute server create [--description <description>]

[--metadata <metadata>] [--user-data <user-data>] [--key-name <key-name>] [--config-drive] [--count <count>] [--ha-enabled {true,false}]

--network <id=id[,key=value,...]>

--volume <source=source[,key=value,...]>

--flavor <flavor> <server-name>

--description <description>

Server description

--metadata <metadata>

Server metadata

Chapter 3. Managing Compute Cluster

--user-data <user-data>

User data ﬁle

--key-name <key-name>

Key pair to inject

--config-drive

Use an ephemeral drive

--count <count>

If count is speciﬁed and greater than 1, the name argument is treated as a naming pattern.

--ha-enabled {true,false}

Enable or disable HA for the compute server

--network <id=id[,key=value,...]>

Create a compute server with a speciﬁed network. Specify this option multiple times to create multiple

networks.

• id: attach network interface to a speciﬁed network (ID or name)

• comma-separated key=value pairs with keys (optional):

•

mac: MAC address for network interface

•

fixed-ip: ﬁxed IP address for network interface

•

spoofing-protection: enable or disable spooﬁng protection for network interface (on or off)

--volume <source=source[,key=value,...]>

Create a compute server with a speciﬁed volume. Specify this option multiple times to create multiple

volumes.

• source: source type (volume, image, snapshot, or blank)

• comma-separated key=value pairs with keys (optional):

•

id: resource ID or name for the speciﬁed source type (required for source types volume, image,

and snapshot)

•

size: block device size, in gigabytes (required for source types image and blank)

•

boot-index: block device boot index (required for multiple volumes with source type volume)

•

bus: block device controller type (scsi)

Acronis Acronis Cyber Infrastructure 3.0 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Introduction

1.1 Providing Credentials

1.2 Managing Tasks

Managing Storage Cluster

2.1 Managing Tokens

2.3 Managing Storage Nodes

2.4 Managing Node Network Interfaces

2.5 Managing Node Disks

2.6 Creating and Deleting the Storage Cluster

2.7 Showing Storage Cluster Overview and Details

Managing Compute Cluster

3.1 Creating and Deleting the Compute Cluster

3.2 Showing Compute Cluster Details and Overview

3.3 Changing Compute Cluster Parameters

3.4 Managing Compute Nodes

3.5 Managing Virtual Networks

3.6 Managing Virtual Routers

3.7 Managing Floating IP Addresses

3.8 Managing Images

3.9 Managing Flavors

3.10 Managing Storage Policies

3.11 Managing Volumes

3.12 Managing Volume Snapshots

3.13 Managing Compute SSH Keys

3.14 Managing Virtual Machines