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.
- Before you begin to implement Global Namespace in your organization, we strongly recommend reviewing How Portal Relationships between Qumulo Clusters Enable a Global Namespace in Qumulo Core, especially the Known Limitations section.
- For any questions, contact the Qumulo Care team.
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
-
PRIVILEGE_PORTAL_SPOKE_EVICT
: Control automatic cache management for active spoke portals by configuring a free threshold -
PRIVILEGE_PORTAL_SPOKE_READ
: View the status of a single spoke portal -
PRIVILEGE_PORTAL_SPOKE_WRITE
: Create a spoke portal and propose a relationship with a hub portal
-
-
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
-
- If both of the clusters use Active Directory, they must be joined to the same domain or each cluster must be joined to Active Directory domains that have a two-way trust relationship to each other.
- A Qumulo cluster can be a portal host for any number of hub portals or for a single spoke portal. It isn't possible for a Qumulo cluster to be a host for spoke and hub portals simultaneously.
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).
-
On one cluster, choose a location for the spoke portal root directory. For example,
/remote/projects
. -
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 Spoke Root Hub Host Hub Root ID Hub Portal ID == ======= ================ =========== =========== ============= 2 Pending /remote/projects 203.0.113.0 3 4
Hub Portal ID
4
is the ID that the hub portal host cluster allocated for this portal relationship. You can use it to authorize the relationship on the hub portal host cluster as described later.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:
-
To find the spoke portal ID, run the
qq portal_list
command. -
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
Note
- We recommend using floating IP addresses.
- Qumulo Core doesn't support fully qualified domain names (FQDNs) for this operation.
- Portal IDs are unique within each cluster. It isn't possible to use a portal ID from a spoke portal to identify the other side of the relationship, or the other way around.
-
When the portal relationship is established, both spoke portal and hub portal enter the
Pending
state.Note
In this state, the spoke portal root directory is empty and Qumulo Core doesn’t transfer any data until the hub portal authorizes the portal relationship.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.
This action makes both clusters in the portal relationship unavailable for less than 30 seconds while the systems reconfigure.
-
To find the hub portal ID, run the
qq portal_list
command.Tip
To retrieve portal configuration information, run theqq portal_list_spokes
andqq portal_list_hubs
commands. -
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
Note
Portal IDs are unique within each cluster. It isn't possible to use a portal ID from a spoke portal to identify the other side of the relationship, or the other way around.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 Hub Root Spoke Host Spoke 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.
Deleting a Portal Relationship Between Two Qumulo Clusters
When you delete the spoke portal and the hub portal (in any order), the portal relationship is deleted completely. This section explains how to delete a portal relationship between two Qumulo clusters by using the qq
CLI.
This action makes both clusters in the portal relationship unavailable for less than 30 seconds while the systems reconfigure.
Prerequisites
-
A spoke portal or hub portal in any state
-
Privileges
PRIVILEGE_PORTAL_SPOKE_WRITE
: Delete a spoke portalPRIVILEGE_PORTAL_HUB_WRITE
: Delete a hub portal
Step 1: Delete the Spoke Portal
You can delete a spoke portal in any state (Unlinked
, Pending
, Active
, or Ended
) and without connectivity to the hub portal. This section explains how to delete the spoke portal from a portal relationship.
-
To find the spoke portal ID, run the
qq portal_list
command.The following is example output from the command that shows the portal ID, state, role, and root directory.
ID State Role Local Root == ======== ===== ================ 3 Active Spoke /remote/projects
-
To delete the spoke portal run the
qq portal_delete_spoke
command and specify the spoke portal ID. For example:qq portal_delete_spoke --id 3
Qumulo Core deletes the spoke portal and begins to reclaim the spoke portal’s cluster capacity in the background.
If the spoke portal can connect to the hub portal, the hub portal detects the relationship change automatically and enters the
Ended
state without affecting any of the data on the hub portal host cluster.
Step 2: Delete the Hub Portal
You can delete a hub portal in any state (Pending
, Active
, or Ended
) and without connectivity to the spoke portal.
This action makes the spoke portal root directory and all cached data inaccessible.
-
To find the hub portal ID, run the
qq portal_list
command.The following is example output from the command that shows the portal ID, state, role, and root directory.
ID State Role Local Root == ======== ===== ========== 4 Active Hub /projects/
-
To delete the hub portal, run the
qq portal_delete_hub
command and specify the hub portal ID. For example:qq portal_delete_hub --id 4
Qumulo Core deletes the hub portal without affecting any of the data on the hub portal host cluster.
If the hub portal can connect to the spoke portal, the spoke portal detects the relationship change and enters the
Ended
state automatically.