Skip to end of metadata
Go to start of metadata
MANAGE-INSTANCE(1)     Xandr CLI Documentation v0.486    MANAGE-INSTANCE(1)
NAME
       manage-instance -
       launch/reinstall/list/list-dns/modify-dns/modify/shutdown/bundle/restart/move/enable-lm/lm/disable-lm/list-lm/add-nic/remove-nic/modify-nic/delete
       instances
SYNOPSIS
       manage-instance launch -n name -c cpu_units -s server_id -m memory -d
       disk -S share_name -p image [--root-vg root_vg] [--swap-vg swap_vg]
       [--dns dns_name] [--os operating_system] [--ip address | --vlan-id
       vlan_id | --subnet I <subnet> ] [-U local_path,path[,permissions]] [-k
       authorized_keys] [-N number_of_inodes] [--kernel version]
       [--admin-password password] [--metadata string | --metadata-file path]
       [--async] [--force]
       manage-instance reinstall -i instance_id -S share_name -p image [-U
       local_path,path[,permissions]] [-k authorized_keys] [-N
       number_of_inodes] [--kernel version] [--preserve-ssh-keys] [--preserve
       path] [--async]
       manage-instance list [-s col_name | -b col_name] [-F perl_expression]
       [-f filters] [--metadata] [ --oc col_name ] [-R] [-v]
       manage-instance list-dns [-s col_name | -b col_name] [-F
       perl_expression] [-f filters] [ --oc col_name ] [-R]
       manage-instance modify -i instance_id [-n name] [-c cpu_units] [-m
       memory] [-d disk] [--kernel version] [--metadata string |
       --metadata-file path] [--async]
       manage-instance modify-dns -i instance_id [--ip address] --dns dns_name
       manage-instance shutdown -i instance_id [--hard] [--async] [--force]
       manage-instance bundle -i instance_id -S share_name -p image [-X
       exclude] [--io-priority io_priority] [--async]
       manage-instance restart -i instance_id [--hard] [--async]
       manage-instance move -i instance_id -s server_id [ --vlan-id vlan_id ]
       [--io-priority io_priority] [--mode mode] [--async]
       manage-instance enable-lm -i instance_id -s server_id [--primary-ip
       address] [--secondary-ip address] [--async]
       manage-instance disable-lm -i instance_id [--async]
       manage-instance lm -i instance_id [--async]
       manage-instance list-lm [-s col_name | -b col_name] [-F
       perl_expression] [-f filters] [ --oc col_name ] [-R]
       manage-instance delete -i instance_id [--release-server] [--async]
       [--force]
       manage-instance display-console -i instance_id
       manage-instance add-nic -i instance_id [--ip address | --vlan-id
       vlan_id | --subnet subnet ] [--async] [--force] [--dns dns_name]
       manage-instance remove-nic -i instance_id --ip address [--async]
       manage-instance modify-nic -i instance_id --from-ip address --to-ip
       address [--async] [--force]
       manage-instance history [-i instance_id] [--depth number]
       manage-instance command [--username username] [--password password]
       manage-instance command -h
       manage-instance (help | -h) [command]
       manage-instance -V
DESCRIPTION
       The manage-instance command is used to launch, reinstall, list, modify,
       shutdown, bundle, restart, move, migrate, and delete instances. The
       requirements for an instance are fairly simple: you specify the server
       to launch the instance on, the path to the image you want to use to
       create it, and the resources that you wish to dedicate to the instance.
       You also have options such as assigning a specific IP address to your
       instance, specifying a non-Linux operating system, uploading a file
       upon launch, etc.
       Before you can launch an instance, you must reserve the server you wish
       to launch on with the manage-server command.
       Passing a valid pointer to an image may have multiple components.
       First, specify a share name. This can either be "public" for the
       Xandr globally available base images, or a share name that belongs
       to you.  Next, pass an image path which is the relative path to the
       image after the share name.  For example, if you have mounted the
       "public" share on /mnt/public and wish to launch
       /mnt/public/images/centos5-base/centos-current.fs.tgz then you would
       pass the following arguments to the command: --share-name=public
       --path=images/centos5-base/centos-current.fs.tgz
       If you are using a Windows image, you must use the --os parameter to
       alert the API that you are launching a Windows instance.
       Memory and disk resources cannot be oversubscribed to instances, and
       CPU units must be allocated in whole numbers.  Instances can break out
       of the allocated CPU units if neighboring instances are under-utilizing
       their CPU allocation but oversubscribing CPUs may end up in instances
       competing for the same resources.
OPTIONS
       -n, --name
           Instance name. May not contain symbols or spaces, but only dashes,
           underscores, and alphanumeric characters. When used with "manage-
           instance modify", it is used to rename an instance. Note that if
           both --name and --dns are used, the setting from --dns will
           override the --name setting.
       -i, --instance-id
           ID of instance. Must be a composite string
           ’<datacenter_id>:<instance_id>’, e.g. ’NYM1:1’, ’LAX1:210’. You can
           specify a comma-separated list of instance IDs for ’shutdown’,
           ’restart’, and ’delete’ commands. For example,
               manage-instance shutdown -i NYM1:1,NYM1:12,NYM1:32,NYM1:55
       -s, --server-id
           ID of the server upon which you wish to launch this instance. Must
           be a composite string ’<datacenter_id>:<server_id>’, e.g. ’NYM1:1’,
           ’LAX1:210’. You can use the "manage-server list" command to find
           available reserved servers.
       -S, --share-name
           Name of the storage share where you can find the operating system
           image.  Valid values are either "public" or the name of a share
           attached to your account.
       -p, --path
           Path to image (relative to the shared storage). For example, if the
           share is "public" and there is an image centos-current.fs.tgz
           located in a subdirectory images/centos5-base/ you would pass
           images/centos5-base/centos-current.fs.tgz as an image path.
       -c, --cpu-units
           Number of cores to reserve for the instance. If other instances on
           a server are under-utilizing their allocated CPU units then the
           instance can "burst out" and use up to 2x the reserved number of
           CPU units. Fractional units are not currently allowed but will be
           shortly.
       -m, --memory
           Memory size and units (mb, gb) to allocate to instance, e.g. 512mb
           or 2gb.  Memory is a fixed reservation and you cannot overallocate
           a server’s total available memory.
       -d, --disk
           Disk size and units (mb, gb or tb) to allocate to instance, e.g.
           100gb or 0.5tb.
       --root-vg
           Volume group on which to create the instance’s root volume. See
           manage-volume list-vgs for available volume groups. The default is
           xen_vg, which is typically the only volume group that will be
           available.
       --swap-vg
           Volume group on which to create the instance’s swap volume. See
           manage-volume list-vgs for available volume groups. The default is
           xen_vg, which is typically the only volume group that will be
           available.
       --os
           Operating system name; required for Windows instances. Default is
           Linux. For possible values, please see
           http://wiki.Xandr.com/display/documentation/Available+Operating+Systems.
       --ip
           IP address of starting instance. The IP should belong to the
           customer’s range and be unoccupied. When used with "manage-instance
           add-nic/remove-nic", it specifys the network interface card to be
           added/removed.
       --vlan-id
           ID of VLAN in which you wish to start the instance. When used with
           the add-nic command it specifies the VLAN from which you wish to
           obtain the IP for the new NIC. Must be a composite string
           ’<datacenter_id>:<vlan_id>’, e.g. ’NYM1:2085’, ’LAX1:2070’.
       --subnet
           Subnet in which you wish to start the instance. When used with the
           add-nic command it specifies the subnet from which you wish to
           obtain the IP for the new NIC. Must be specified in CIDR notation,
           e.g. ’8.12.238.64/26’.
       -U, --upload
           Upload a file or suite of files into an instance at launch or
           reinstall time. Should be in the form: <path to file>,<destination
           path>,<permissions (this is optional; must be octal; the default
           value is 0644)>. For example,
           --upload=./files/passwd.orig,/root/passwd,0600. Available only for
           Linux.
       --preserve
           This option allows you to specify a full path to a file or a
           directory which should be preserved during instance reinstall. You
           can specify this option multiple times.
       --preserve-ssh-keys
           When this option is used, the host SSH keys will be preserved
           during instance reinstall.
       -N, --number-of-inodes
           Number of inodes that should be allocated for the filesystem.
           Default value is calculated in the following way: disk size (in
           kilobytes) is divided by 32 (kilobytes/inode ratio). (If calculated
           value is less than one million the number of inodes will be set to
           ~one million.) The number of inodes cannot be changed after the
           filesystem is created. Available only for Linux.
       -k, --authorized-keys
           Path to file whose content should be placed in
           ’/root/.ssh/authorized_keys’ when the instance is launched or
           reinstalled. Note that the size of a file is limited to 1 mb.
           Available only for Linux.
       --admin-password
           Microsoft’s Remote Desktop Protocol (RDP) requires an
           administrator’s password. This option allows you to set a custom
           password at launch time. The password should contain at least three
           out of four character classes: uppercase letters, lowercase
           letters, numbers, special symbols (characters not defined as
           letters or numbers). If this option isn’t specified, a password
           will be generated automatically.
       --kernel
           Linux kernel version. You can also specify the value "image" to
           alert the API that you will be using a custom kernel that exists
           inside the image or existing instance. If this parameter is not
           specified, the default Xandr kernel will be used. (For more
           information, see
           http://wiki.Xandr.com/display/documentation/Available+and+Custom+Kernels).
       --io-priority
           I/O priority of the bundling/moving process relative to other
           instances that are in running state on the same server. Here are
           currently supported values.
               ’default’ - normal I/O priority - running instances and the
               bundling/moving process receive equal I/O priority.
               ’min’ - idle I/O priority - the bundling/moving processes disk
               I/O only runs when running processes are idle.
       --mode
           Mode of disk data copying in the move command. Here are currently
           supported values.
               ’data-only’ - copy only disk space that is already allocated
               for files and directories.
               ’raw’ - copy the instance’s disk bit by bit including disk
               space that is not being used.
           Default is ’data-only’.
       -X, --exclude
           Exclude files or directories whose names match the specified
           pattern or suite of patterns. Available only for Linux. For
           example, exclude=’/var/backups’. A pattern may contain standard
           wildcard characters like, ’*’ or ’?’. The character ’\’ says to
           take the following character of the pattern literally. The
           characters ’[’ and ’]’ introduce a character class. If the first
           character of the class after the opening ’[’ is ’!’ or ’^’, then
           the class will NOT be included. Characters are case sensitive. Here
           are examples of typical patterns.
               ’/var/log’ (not ’/var/log/’, with trailing slash) excludes the
               whole directory and all the files/subdirectories beneath it.
               ’*.bak’ excludes all files whose names end in ’.bak’.
               ’*.s?f’ excludes ’*.saf’, ’*.sbf’, ’*.scf’, etc.
               ’*.s\?f’ excludes ’*.s?f’ literally.
               ’*.s[b-d]f’ excludes ’*.sbf’, ’*.scf’, ’*.sdf’ only.
               ’*.s[^w]f’ excludes ’*.saf’, ’*.sbf’, etc. but not ’*.swf’.
           Notes:
               A few tips: Enclosing patterns in quotes is highly recommended
               to avoid ambiguity of pattern interpretation. Be careful when
               using wildcard characters. For example, if the ’*.bak’ pattern
               is specified then any directory that ends in the same pattern
               (e.g. ’dir.bak/foo’) will be excluded also. All patterns that
               start with a leading slash are treated as absolute paths. You
               can exclude multiple files by repeating the --exclude parameter
               multiple times in the same command.
       --from-ip
           The former IP address of a network interface card for ’modify-nic’
           command.
       --to-ip
           The new IP address of a network interface card for ’modify-nic’
           command.
       --primary-ip
           When you execute the enable-lm command and the server where the
           instance currently resides has more than one IP address assigned,
           you will need to use this option to specify which one of the server
           addresses you want to use for the instance data synchronization.
       --secondary-ip
           When you execute the enable-lm command and the destination server
           where you want to migrate the instance to has more than one IP
           address assigned, you will need to use this option to specify which
           one of the server addresses you want to use for the instance data
           synchronization.
       --metadata
           An arbitrary string that should be set as instance’s metadata. Also
           you can use the --metadata optional parameter for including
           instance’s metadata into output of the list command. Please note,
           the --raw optional parameter will be enabled in this case
           implicitly.
       --metadata-file
           Path to file whose content should be uploaded as instance’s
           metadata.
       --hard
           Restart or shutdown an instance forcefully without waiting for
           processes to shut down gracefully.
       --force
           If user attempts to launch an instance with a reserved IP address,
           or delete an instance in running state, or shut down or delete
           their last running instance, they will be prompted to enter
           "--force" as a precaution. Also you must use --force if you need to
           use a reserved IP address or an IP address used by instance in
           "manage-instance add-nic/modify-nic" commands.
       --release-server
           This option allows you to auto-release the server if you are
           deleting the last instance on the server.
       --depth
           Number of most recent operations to show in history. Default is 20.
       --dns
           The desired DNS name for the instance or NIC. See the section DNS
           NAMES below for more details. Note that if both --name and --dns
           are used, the setting from --dns will override the --name setting.
       --async
           Execute command in asynchronous mode. This means that the CLI will
           not wait to apprise you of your command’s status before being
           available for the next command.  =item -v, --verbose
           Verbose output (incl. rack name, operating system name, Linux
           kernel version, and password for Windows Administrator).
       -s, --sort
           Column name(s) for sorting (id, name, server_hostname, server_id,
           rack, ip_address, state, cpu_units, memory, disk, os, kernel,
           admin_password, metadata). Use --sort
           <column_name1>{,<column_nameN>}.
       -b, --rsort
           Column name(s) for reverse sorting.
       -f, --filter
           Filter results by column name (id, name, server_hostname,
           server_id, rack, ip_address, state, cpu_units, memory, disk, os,
           kernel, admin_password, metadata). Use --filter
           <column_name1>=<pattern1>{,<patternN>}
           {<column_name2>=<pattern2>{,<patternN>} where {} indicates an
           optional parameter. Do not use a space between multiple patterns.
           For example, --filter state=running,offline.
       -F, --server-side-filter
           Filters results on the server side before they are passed to the
           client. The value for this option is a perl expression which
           controls whether rows are included in the result set returned to
           the client. Server and client side filtering can be freely
           combined. See the section SERVER SIDE FILTERING for more details.
       --oc
           Specify a comma separated list of data columns to return in list
           output.
       -R, --raw
           Output results in tab-delimited form.
       --username
           Username for API, same as for Customer Portal. Could be specified
           in CLI config file "rpc.cfg" (expected locations: /etc/Xandr,
           ~/.Xandr, or the current working directory).
       --password
           Password for API, same as for Customer Portal. If password isn’t
           specified, you’ll be asked to enter it. Note that specifying a
           password on the command line should be considered insecure.
           Password could be specified in CLI config file, but to keep the
           password safe, the file should not be accessible to anyone but
           yourself. To ensure this, set the file access mode to 400 or 600.
       -V, --version
           Version of the command-line interface you are currently using.
       -h, --help
           Display help.
COMMANDS
   launch
           Launch new instance. If user attempts to specify a reserved IP
           address, they will be prompted to enter "--force" as a precaution.
           If the user has any DNS domains configured, a new A record for the
           instance will be added to DNS. The DNS name can be specified using
           the --dns option. If the --dns option is not used, the name of the
           instance will be used as the default. Please see the section DNS
           NAMES for more details. Note that if both --name and --dns are
           used, the setting from --dns will override the --name setting.
           Required Parameters: -n/--name, -c/--cpu-units, -s/--server-id,
           -m/--memory, -d/--disk, -S/--share-name, -p/--path
           Optional Parameters: --root-vg, --swap-vg, --os, (--ip | --vlan-id
           | --subnet), -U/--upload, -k/--authorized-keys,
           -N/--number-of-inodes, --dns, --kernel, --admin-password,
           (--metadata | --metadata-file), --async, --force
   reinstall
           Reinstall an existing instance. A new empty root filesystem will be
           created for the instance, and the filesystem will be populated from
           the specified image. The instance IP address and DNS records will
           remain unchanged. Optionally you can preserve the host SSH keys and
           any other file or directory using the options --preserve-ssh-keys
           and --preserve. Options -k, -U, -N, and --kernel have the same
           effect as they do for the launch command.
           Required Parameters: -i/--instance-id, -S/--share-name, -p/--path
           Optional Parameters: -U/--upload, -k/--authorized-keys,
           -N/--number-of-inodes, --kernel, --async, --preserve,
           --preserve-ssh-keys
   list
           Show list of instances.
           Required Parameters: none
           Optional Parameters: --metadata, (-s/--sort | -b/--rsort),
           -F/--server-side-filter, -f/--filter, --oc, -R/--raw, -v/--verbose
   list-dns
           Show list of instances with their DNS names.
           Required Parameters: none
           Optional Parameters: --metadata, (-s/--sort | -b/--rsort),
           -F/--server-side-filter, -f/--filter, --oc, -R/--raw
   modify
           Modify instance with specified instance ID.
           Required Parameters: -i/--instance-id
           Optional Parameters: -n/--name, -c/--cpu-units, -m/--memory,
           -d/--disk, --kernel, (--metadata | --metadata-file), --async
   modify-dns
           Modify the DNS name of the specified instance. If multiple IP
           addresses are assigned to the instance, you will need to use the
           --ip option to specify which IP address you want to modify the DNS
           name for.
           Required Parameters: -i/--instance-id  --dns
           Optional Parameters: --ip, --force
   shutdown
           Shut down (put into offline state) instance with specified instance
           ID. If user attempts to shut down their last running instance, they
           will be prompted to enter "--force" as a precaution. Multiple
           instance IDs are allowed.
           Required Parameters: -i/--instance-id
           Optional Parameters: --hard, --async, --force
   bundle
           Bundle (create image from) instance with specified instance ID.
           This is an easy way to migrate an instance or make duplicates.
           Currently an instance must be offline before bundling.
           Required Parameters: -i/--instance-id, -S/--share-name, -p/--path
           Optional Parameters: -X/--exclude, --io-priority, --async
   restart
           Restart (take out of offline state) instance with specified
           instance ID. Multiple instance IDs are allowed.
           Required Parameters: -i/--instance-id
           Optional Parameters: --hard, --async
   move
           Move instance with specified instance ID to server with specified
           server ID.  This will result in the specified instance being marked
           as "moved" and a new instance being created.
           For intradatacenter moves, IP and MAC addresses will move to the
           new instance. --vlan-id cannot be specified for an intradatacenter
           move.
           For interdatacenter moves, one IP will be allocated in the remote
           datacenter on the specified --vlan-id for each IP assigned to the
           moving instance. --vlan-id must be specified for an interdatacenter
           move. If the existing instance has multiple IPs on different VLANs,
           there is no attempt to mirror the VLAN heterogeneity on the new
           instance. VIPs pointed at the moving instance will break once the
           instance is moved to the remote datacenter, and this must be fixed
           manually.
           Required Parameters: -i/--instance-id, -s/--server-id
           Optional Parameters: --io-priority, --mode, --async, --vlan-id
   enable-lm
           Start the synchronization of instance disk data of the specified
           instance to the specified server. This is the first step required
           for live migration of the instance. See the section LIVE MIGRATION
           below for more details.
           Required Parameters: -i/--instance-id, -s/--server-id
           Optional Parameters: --async, --primary-ip, --secondary-ip
   lm
           Migrate the specified instance live to the destination server where
           the instance disk data is synchronized to. See the section LIVE
           MIGRATION below for more details.
           Required Parameters: -i/--instance-id
           Optional Parameters: --async
   disable-lm
           Stop the synchronization of instance disk data started with the
           enable-lm command. See the section LIVE MIGRATION below for more
           details.
           Required Parameters: -i/--instance-id
           Optional Parameters: --async
   list-lm
           Show list of instances whose disks are being synchronized to other
           servers in preparation for live migration and the status of the
           synchronization process. See the section LIVE MIGRATION below for
           more details.
           Required Parameters: none
           Optional Parameters: (-s/--sort | -b/--rsort),
           -F/--server-side-filter, -f/--filter,  --oc, -R/--raw
   delete
           Delete instance with specified instance ID. Please be aware: this
           command totally destroys instances in the running, offline, and
           failed states; it also erases all data including all attached
           volumes (see manage-volume). If user attempts to delete their last
           running instance, they will be prompted to enter "--force" as a
           precaution. Multiple instance IDs are allowed.
           Please note that deleting instances that was moved to a new server
           intradatacenter using the move command will result on the original
           instance getting its original IP and mac addresses back. If there
           are any A records for the instance in DNS, they will be removed.
           Please note that deleting instances that was moved to a new server
           interdatacenter using the move command will result on the original
           instance getting its original DNS entries back.
           Required Parameters: -i/--instance-id
           Optional Parameters: --release-server, --async, --force
   display-console
           Show console output for instance with specified instance ID. Not
           available for Windows.
           Required Parameters: -i/--instance-id
           Optional Parameters: none
   add-nic
           Add network interface card with specified IP address to instance
           with specified instance ID. Instead of the IP address is also
           possible to specify the subnet or the VLAN from which the IP
           address should be allocated. If the user has any DNS domains
           configured, a new A record for the new NIC will be added to DNS.
           The DNS name can be specified using the --dns option. If the --dns
           option is not used, a number will be appended to the part of the
           instance name before the first dot, and this variant of the
           instance name will be used as the default. Please see the section
           DNS NAMES for more details.
           Required Parameters: -i/--instance-id
           Optional Parameters: --ip, --vlan-id, --subnet, --async, --force,
           --dns
   remove-nic
           Remove network interface card with specified IP address from
           instance with specified instance ID. If there is an A record for
           the NIC in DNS, it will be removed.
           Required Parameters: -i/--instance-id, --ip
           Optional Parameters: --async
   modify-nic
           Change IP address of network interface card for instance with
           specified instance ID. If there is an A record for the NIC in DNS,
           the record will be modified accordingly.
           Required Parameters: -i/--instance-id, --from-ip, --to-ip
           Optional Parameters: --async, --force
   history
           Show history of operations on instances. If no particular instance
           is specified then operations on all instances will be displayed.
           Required Parameters: none
           Optional Parameters: -i/--instance-id, --depth
   help
           Show help.
           Required Parameters: none
           Optional Parameters: launch, list, modify, shutdown, bundle,
           restart, move, delete, display-console, add-nic, modify-nic,
           remove-nic, history
DNS NAMES
       Please note that fully qualified DNS names must end with a dot ’.’. DNS
       names without the terminating dot will have the default DNS domain
       appended to them. You can list your DNS domains, determine which domain
       is the default domain, and change the default DNS domain with the
       command manage-dns-domain.
LIVE MIGRATION
       It is possible to migrate instances "live" from one server to another.
       First, you have to start the synchronization of instance disk data from
       the server where the instance presently resides to the server where you
       want to migrate the instance to. This is achieved with the enable-lm
       command. The destination server must be on the same subnet as the
       source server. The intance will be restarted during this step. The
       synchronization of the disk data can take considerable time depending
       on the size of the instance. You can check the status of the
       synchronization process with the list-lm command. You will see that the
       status is either "syncing", with a progress indicator next to it, or
       it’s "up-to-date". Any time when the synchronization status is "up-to-
       date", you can use the lm command to migrate the instance to the
       destination server. The instance will become unresponsive for 30 - 60
       seconds during the migration, but it will be migrated live (existing
       TCP connections will remain established). After a successful migration
       the source and destination servers will swap roles. If you use the
       command lm again, the instance will migrate back to the original source
       server. In this way you can use the lm command multiple times and the
       instance will migrate back and forth between the two servers. The
       synchronization of the instance disk data can be stopped at any time
       regardless of whether you migrated the instance or not with the
       disable-lm command. The instance is restarted during the disable-lm
       command. It is generally recommended to keep the time when
       synchronization of instance disk data is enabled to minimum.
SERVER SIDE FILTERING
       You can use the -F option to filter the result set on the server side
       before the results are passed to the client. The value for the -F
       option is a perl expression which, when evaluates to true, causes the
       row to be included in the result set, and when false, it causes this
       row to be excluded from the result set passed to the client. You can
       further refine the displayed results using client side filtering and
       ordering options -f, -s, and -b. The perl expression is limited to
       using variables, comparison operators, regular expressions,
       parentheses, and a few other operations. Function calls and loops are
       not allowed. Variable names match column names with the dollar sign
       prepended to them as is customary in perl.
   Examples:
       manage-instance list -F ’$id eq "NYM2:11399"’
           List only the instance NYM2:11399
       manage-instance list -F ’$name =~ /cronbox/’
           List instances whose name matches the perl regular expression
           ’cronbox’.
       manage-instance list -F ’$state eq "running" && cpu_units == 4’
           List running instances with 4 CPUs.
DEPRECATED
       We have replaced underscores ’_’ with dashes ’-’ in all CLI parameter
       names to be more compliant with standard syntax. The following manage-
       instance options are affected.
       Deprecated Parameters: --server_id, --cpu_units, --instance_id,
       --authorized_keys, --share_name
SEE ALSO
       manage-server, manage-lb-ip, manage-lb-pool, manage-vlan, manage-gslb-
       zone, manage-gslb-domain, manage-gslb-group, manage-storage, manage-
       dns-domain
0.486                             2018-02-13                MANAGE-INSTANCE(1)