This section explains how to use the qq portal_create command.

Example

To Propose an Initial Portal Relationship

Run the qq portal_create command and specify the spoke portal root directory, the proposed hub portal root directory on that cluster, and the IP addresses of the nodes in the remote cluster.

For example:

qq portal_create \
  --spoke-root /remote/projects \
  --hub-address 203.0.113.0 \
  --hub-root /projects
  --hub-root /projects \
  --hub-hosts 203.0.113.1,203.0.113.2,203.0.113.3,203.0.113.4

Description

Create a spoke portal on the current cluster and propose a hub portal on another cluster

Usage

qq portal_create [-h] [--spoke-root SPOKE_ROOT] [--hub-root HUB_ROOT] [-j] [-n] [-r] (-m HUB_HOSTS | -a HUB_ADDRESS) [-p HUB_PORT]

Flags

Flag Name Required Description
--spoke-root No The full path to the directory that serves as the spoke portal root directory. Qumulo Core creates this directory for you automatically. If this directory exists already, the system outputs an error.
--hub-root No The full path to the prospective directory that will serve as the hub portal root directory
-j No Pretty-print JSON
-n No Do not attempt to resolve file IDs present on the local cluster to paths.
-r No Create a read-only spoke portal. Read-only spoke portals prevent users from creating or modifying files or directories under the hub portal root directory. To make the spoke portal writable later, run `portal_modify_hub --type read-write` on the hub cluster.
-m No The IP addresses and TCP ports of the remote cluster. Use a comma-delimited list to specify multiple hosts. Use colon as a separator after each IP address to provide custom TCP port (3713 is used by default). Ports specified this way override other --port arguments. Put brackets around an IPv6 address, such as [2001:db8::1] or [2001:db8::1]:4000. Use a dash to specify a range of IPv4 addresses that share their first three octets, such as 10.220.1.70-73 or 10.220.1.70-10.220.1.73. A port applies to the whole range.
-a No The IP address of a node in the remote cluster
-p No The TCP port for portal activity on the remote cluster. The default port 3713 is used if this field is not provided.