This section explains how to use the Global Namespace functionality in Qumulo Core by creating a spoke portal on one cluster, proposing a portal relationship to another cluster (which creates the hub portal), and authorizing the relationship by using the qq CLI.

Configuring a Portal Relationship Between Two Qumulo Clusters

This section explains how to configure a portal relationship between two Qumulo clusters by using the qq CLI.

Prerequisites

  • Two clusters with the same version of Qumulo Core

  • Network connectivity on TCP port 3713 from the cluster that shares a portion of its file system for the spoke portal root directory to the cluster that will share a portion of its file system for the hub portal root directory

  • PRIVILEGE_PORTAL_GLOBAL_READ for viewing the status for a hub portal or spoke portal and retrieving general portal information

  • Spoke portals

  • Hub portals

    • PRIVILEGE_PORTAL_HUB_READ: View the status of a specific hub portal

    • PRIVILEGE_PORTAL_HUB_WRITE: Authorize a hub portal and confirm a relationship with a spoke portal

Step 1: Create the Spoke Portal

This section explains how to create the spoke portal on one cluster and propose the creation of a portal relationship to another cluster (which creates the hub portal).

  1. On one cluster, choose a location for the spoke portal root directory. For example, /remote/projects.

  2. To propose an initial portal relationship, run the qq portal_create command and specify the spoke portal root directory, the IP address of the proposed hub portal host cluster, and the proposed hub portal root directory on that cluster. For example:

    qq portal_create \
  --spoke-root /remote/projects \
  --hub-address 203.0.113.0 \
  --hub-root /projects

    The spoke portal enters the Pending state. The following is example output from the command.

    ID  State    Hub          Spoke Root        Hub Root ID
==  =======  ===========  ================  ===========
2   Pending  203.0.113.0  /remote/projects  3

    If Qumulo Core can’t establish a connection from the cluster with the spoke portal portion to the cluster with the hub portal portion, it displays an error message and the spoke portal enters the Unlinked state.

    To propose a portal relationship at a later time, do the following:

    1. To find the spoke portal ID, run the qq portal_list command.

    2. Run the qq portal_propose_hub command and specify the spoke ID, the IP address of a prospective Qumulo cluster with the hub portal portion, and the proposed hub portal root directory on that cluster. For example:

      qq portal_propose_hub \
  --spoke-id 2 \
  --hub-address 203.0.113.0 \
  --hub-root /projects

    3. When the portal relationship is established, both spoke portal and hub portal enter the Pending state.

      You can check the status of a cluster by using the qq portal_list command. The following is example output from the command that shows the portal ID, state, role, and root directory.

      • From the spoke portal host cluster

        ID  State     Role   Local Root
==  ========  =====  ================
2   Pending   Spoke  /remote/projects

      • From the hub portal host cluster

        ID  State     Role   Local Root
==  ========  =====  ==========
4   Pending   Hub    /projects/

Step 2: Authorize the Portal Relationship

This section explains how to authorize the portal relationship from the hub portal to the spoke portal.

  1. To find the hub portal ID, run the qq portal_list command.

  2. To authorize the proposed portal relationship, run the qq portal_authorize_hub command and specify the hub portal ID and the IP address that the current cluster can use to contact the cluster that proposed the relationship. For example:

    qq portal_authorize_hub \
  --id 4 \
  --spoke-address 203.0.113.1

    The following is example output from the command that shows that the portal relationship for the hub portal is in the Active state.

    ID  State   Root       Peer Address  Peer Name
==  ======  =========  ============  =========
4   Active  /projects  203.0.113.1   qfsd-edge

    After a few seconds, the spoke portal enters the Active state as well. You can now use the spoke portal root directory.