From 78f6a5eaa7c505dac8f0583f1a84c28c5f777502 Mon Sep 17 00:00:00 2001 From: "Michael G. Khmelnitsky, Ph.D" Date: Fri, 8 Mar 2024 00:17:55 -0800 Subject: [PATCH] [DOCS-2055] (#333) --- .../sidebars/administrator_guide_sidebar.yml | 4 +- .../configuring-saml-single-sign-on-sso.md | 24 ++++---- .../external-services/using-access-tokens.md | 2 +- .../creating-directory-quotas.md | 6 +- .../kerberos-configuring-active-directory.md | 2 +- ...eshooting-host-access-rules-nfs-exports.md | 4 +- .../admin-guides/nfs/creating-nfs-export.md | 6 +- ...ing-continuous-replication-relationship.md | 10 ++-- .../replicating-data/shift-from-s3.md | 2 +- .../replicating-data/shift-to-s3.md | 2 +- .../s3-api/configuring-using-s3-api.md | 2 +- .../creating-managing-s3-access-keys.md | 2 +- .../admin-guides/smb/creating-smb-share.md | 6 +- .../snapshots/managing-snapshots.md | 6 +- ...on-requirements-upgrade-recommendations.md | 4 +- .../admin-guides/web-ui/inactivity-timeout.md | 6 +- .../admin-guides/web-ui/login-banner.md | 6 +- .../content-reuse/kerberos-ntp-server.md | 4 +- ...data-protection-reconfiguration-process.md | 6 +- .../installing-vpn-keys-on-cluster.md | 2 +- .../managing-encryption-at-rest.md | 6 +- administrator-guide/index.md | 2 +- .../kerberos-configuring-active-directory.md | 2 +- ...g-cloud-based-monitoring-remote-support.md | 10 ++-- .../configuring-management-protocols.md | 2 +- .../partitioning-cluster-into-tenants.md | 2 +- .../adding-nodes-existing-cluster.md | 10 ++-- ...cing-nodes-transparent-platform-refresh.md | 6 +- .../snapshots/managing-snapshots.md | 2 +- .../upgrading-qumulo-core/feature-log.md | 56 +++++++++---------- ...are-platform.md => performing-upgrades.md} | 46 +++++++++++++-- .../web-ui/inactivity-timeout.md | 2 +- administrator-guide/web-ui/login-banner.md | 2 +- .../deploying-instance-azure-native-qumulo.md | 6 +- .../kerberos-configuring-active-directory.md | 2 +- .../snapshots/managing-snapshots.md | 2 +- .../web-ui/inactivity-timeout.md | 2 +- .../web-ui/login-banner.md | 2 +- .../cluster/cluster_create.md | 2 +- .../saml/saml_modify_settings.md | 2 +- .../ssl/ssl_modify_certificate.md | 2 +- .../web/web_ui_get_settings.md | 2 +- .../web/web_ui_modify_settings.md | 2 +- .../installing-configuring-qumulo-alerts.md | 2 +- 44 files changed, 159 insertions(+), 121 deletions(-) rename administrator-guide/upgrading-qumulo-core/{instant-software-platform.md => performing-upgrades.md} (62%) diff --git a/_data/sidebars/administrator_guide_sidebar.yml b/_data/sidebars/administrator_guide_sidebar.yml index c34876bd3..47dd00438 100644 --- a/_data/sidebars/administrator_guide_sidebar.yml +++ b/_data/sidebars/administrator_guide_sidebar.yml @@ -65,8 +65,8 @@ entries: url: /administrator-guide/upgrading-qumulo-core/mode-reference.html output: web, pdf - - title: Instant Software and Platform Upgrades - url: /administrator-guide/upgrading-qumulo-core/instant-software-platform.html + - title: Performing Upgrades + url: /administrator-guide/upgrading-qumulo-core/performing-upgrades.html output: web, pdf - title: Replication Version Requirements and Upgrade Recommendations diff --git a/_includes/content-reuse/admin-guides/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md b/_includes/content-reuse/admin-guides/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md index 85cf62443..8b727cd29 100644 --- a/_includes/content-reuse/admin-guides/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md +++ b/_includes/content-reuse/admin-guides/authentication-qumulo-core/configuring-saml-single-sign-on-sso.md @@ -95,7 +95,7 @@ This process requires coordination between the cluster administrator and SSO adm
  • To view the current SAML configuration, the cluster administrator can use the qq saml_get_settings command.
  • To allow specific changes (for example, correct a typo, update a DNS name or an expired certificate, or temporarily disable SAML SSO without losing any of the other settings), the cluster administrator can use the qq saml_modify_settings command to change individual SAML settings independently.
  • For first-time SAML configurations, the cluster administrator must provide all of the required settings.
    • -
  • Aside from a basic check of the IdP certificate, Qumulo Core doesn't verify the configuration parameters. It is the cluster administrator's responsibility to ensure that IdP-initiated SAML login works correctly. (This login type initiates when the user clicks Continue to SSO login in the Web UI or selects the Qumulo cluster on the SSO portal.)
    • +
  • Aside from a basic check of the IdP certificate, Qumulo Core doesn't verify the configuration parameters. It is the cluster administrator's responsibility to ensure that IdP-initiated SAML login works correctly. (This login type initiates when the user clicks Continue to SSO login in the Qumulo Core Web UI or selects the Qumulo cluster on the SSO portal.)
    • {{site.data.alerts.end}} @@ -108,10 +108,10 @@ Qumulo Core supports three SAML SSO workflows: {{site.data.alerts.note}} {{site.data.alerts.end}} @@ -120,15 +120,15 @@ Qumulo Core supports three SAML SSO workflows: 1. The SSO portal redirects the user to the cluster's endpoint. - If the user has sufficient privileges, the Web UI logs the user in. Otherwise, the Web UI displays an error message. + If the user has sufficient privileges, the Qumulo Core Web UI logs the user in. Otherwise, the Qumulo Core Web UI displays an error message. ### SP-Initiated SSO Workflow 1. A user navigates to the Qumulo cluster's Web UI endpoint in a browser. -1. If the Qumulo cluster has SAML SSO configured, the user can click **Continue to SSO login** on the Web UI login page. +1. If the Qumulo cluster has SAML SSO configured, the user can click **Continue to SSO login** on the Qumulo Core Web UI login page. - The Web UI redirects the user to the configured SSO portal. Because the authentication request uses HTTP-Redirect Binding, the login URL appears. + the Qumulo Core Web UI redirects the user to the configured SSO portal. Because the authentication request uses HTTP-Redirect Binding, the login URL appears. ``` https://..com/abc12de34fgAB5CDh6i7/saml?SAMLRequest=abcdefgh1234567890... @@ -186,18 +186,18 @@ In Qumulo Core 5.3.0 (and higher), you can use the `qq saml_modify_settings` CLI qq saml_modify_settings --require-sso true ``` -When the cluster requires SSO authentication, your cluster rejects password-based authentication from AD users in the Web UI, the `qq` CLI, and the REST API. +When the cluster requires SSO authentication, your cluster rejects password-based authentication from AD users in the Qumulo Core Web UI, the `qq` CLI, and the REST API. ## Known Issues and Limitations -* Local users (the built-in `admin` user and any additional users) can always use their passwords to authenticate to the Web UI and the `qq` CLI. +* Local users (the built-in `admin` user and any additional users) can always use their passwords to authenticate to the Qumulo Core Web UI and the `qq` CLI. {% include important.html content="We recommend setting a strong password for the built-in `admin` user and using this account only for emergencies." %} -* If SSO is required for a Qumulo cluster, it isn't possible to log in to the **Interactive API documentation** section of the **APIs & Tools** page in the Web UI. +* If SSO is required for a Qumulo cluster, it isn't possible to log in to the **Interactive API documentation** section of the **APIs & Tools** page in the Qumulo Core Web UI. * Qumulo Core doesn't support: - * **SAML Single Logout (SLO):** We recommend clicking **Sign out** in the Web UI. + * **SAML Single Logout (SLO):** We recommend clicking **Sign out** in the Qumulo Core Web UI. * **Automatic Configuration from Metadata XML:** You must specify each parameter by using the `qq` CLI. * **Returning to Previous Web UI Page:** You can't return to a previous page after re-authenticating (for example, after a timeout). * **Azure AD SAML Toolkit:** Currently, due to a configuration deficiency in the toolkit, IdP-initiated SSO isn't operational for Qumulo as a Service. Use the [SP-initiated SSO workflow](#sp-inititated-sso-workflow). @@ -215,7 +215,7 @@ Typically, if SAML authentication fails, Qumulo Core's in-browser error message * The `cluster-dns-name` or `idp-entity-id` on the Qumulo cluster aren't configured correctly. -* A user isn't a member of the Observers role that Qumulo Core requires for granting access to the Web UI. +* A user isn't a member of the Observers role that Qumulo Core requires for granting access to the Qumulo Core Web UI. ### Uncommon Issues In more complex cases, the in-browser errors are less informative for security reasons. For example, if you configure an incorrect IdP certificate on your cluster, the **Signature validation failed. SAML Response rejected.** error appears. diff --git a/_includes/content-reuse/admin-guides/external-services/using-access-tokens.md b/_includes/content-reuse/admin-guides/external-services/using-access-tokens.md index e2460d775..f4f1d024c 100644 --- a/_includes/content-reuse/admin-guides/external-services/using-access-tokens.md +++ b/_includes/content-reuse/admin-guides/external-services/using-access-tokens.md @@ -2,7 +2,7 @@ In Qumulo Core 5.3.0 (and higher), you can use _access tokens_ to let a user authenticate to the Qumulo REST API without having to complete repetitive login procedures. -Access tokens are long-lived. They provide an alternative to session-based authentication that the `qq login` command and the Web UI use. They also support support authentication for services, long-lived automation processes, and programmatic REST API access that doesn't require user input. +Access tokens are long-lived. They provide an alternative to session-based authentication that the `qq login` command and the Qumulo Core Web UI use. They also support support authentication for services, long-lived automation processes, and programmatic REST API access that doesn't require user input. {{site.data.alerts.important}}
      diff --git a/_includes/content-reuse/admin-guides/getting-started/creating-directory-quotas.md b/_includes/content-reuse/admin-guides/getting-started/creating-directory-quotas.md index f13761945..abdbaaa0d 100644 --- a/_includes/content-reuse/admin-guides/getting-started/creating-directory-quotas.md +++ b/_includes/content-reuse/admin-guides/getting-started/creating-directory-quotas.md @@ -1,6 +1,6 @@ ## To Create a Directory Quota -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > Quotas**. @@ -17,7 +17,7 @@ ## To Modify a Directory Quota -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > Quotas**. @@ -28,7 +28,7 @@ ## To Delete a Directory Quota -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > Quotas**. diff --git a/_includes/content-reuse/admin-guides/kerberos/kerberos-configuring-active-directory.md b/_includes/content-reuse/admin-guides/kerberos/kerberos-configuring-active-directory.md index 739d076f6..fc0a9ef8f 100644 --- a/_includes/content-reuse/admin-guides/kerberos/kerberos-configuring-active-directory.md +++ b/_includes/content-reuse/admin-guides/kerberos/kerberos-configuring-active-directory.md @@ -34,7 +34,7 @@ Unless you need direct access to a specific node through a DNS fully qualified d 1. Update the list of IP addresses for this host record. Include the IP addresses for all nodes. - To find the IP addresses in the Web UI, click **Cluster > Network Configuration**. + To find the IP addresses in the Qumulo Core Web UI, click **Cluster > Network Configuration**. 1. Configure the DNS resolver to point to the DNS server. diff --git a/_includes/content-reuse/admin-guides/nfs/configuring-troubleshooting-host-access-rules-nfs-exports.md b/_includes/content-reuse/admin-guides/nfs/configuring-troubleshooting-host-access-rules-nfs-exports.md index 7ef6b9a59..605c2d285 100644 --- a/_includes/content-reuse/admin-guides/nfs/configuring-troubleshooting-host-access-rules-nfs-exports.md +++ b/_includes/content-reuse/admin-guides/nfs/configuring-troubleshooting-host-access-rules-nfs-exports.md @@ -46,9 +46,9 @@ To be able to use hostnames, you must: ## Adding a Host Access Rule to an Existing NFS Export -This section explains how you can add a host access rule to an existing NFS export by using the Web UI or the `qq` CLI. +This section explains how you can add a host access rule to an existing NFS export by using the Qumulo Core Web UI or the `qq` CLI. -### To Add a Host Access Rule by Using the Web UI +### To Add a Host Access Rule by Using the Qumulo Core Web UI 1. Log in to Qumulo Core. diff --git a/_includes/content-reuse/admin-guides/nfs/creating-nfs-export.md b/_includes/content-reuse/admin-guides/nfs/creating-nfs-export.md index 444bebc34..4bc35dfd6 100644 --- a/_includes/content-reuse/admin-guides/nfs/creating-nfs-export.md +++ b/_includes/content-reuse/admin-guides/nfs/creating-nfs-export.md @@ -1,7 +1,7 @@ ## To Create an NFS Export -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > NFS Exports**. @@ -34,7 +34,7 @@ ## To Modify an NFS Export -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > NFS Exports**. @@ -45,7 +45,7 @@ ## To Delete an NFS Export -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > NFS Exports**. diff --git a/_includes/content-reuse/admin-guides/replicating-data/creating-managing-continuous-replication-relationship.md b/_includes/content-reuse/admin-guides/replicating-data/creating-managing-continuous-replication-relationship.md index 07d72b876..368976c5b 100644 --- a/_includes/content-reuse/admin-guides/replicating-data/creating-managing-continuous-replication-relationship.md +++ b/_includes/content-reuse/admin-guides/replicating-data/creating-managing-continuous-replication-relationship.md @@ -39,7 +39,7 @@ The following privileges are required for continuous replication. ## To Create a Replication Relationship {% include important.html content="A replication job doesn't begin until you authorize the relationship on the target cluster." %} -1. Log in to the Web UI on the source cluster. +1. Log in to the Qumulo Core Web UI on the source cluster. 1. Click **Cluster > Replication**. @@ -77,7 +77,7 @@ The following privileges are required for continuous replication. ## To Authorize a Replication Relationship {% include note.html content="If your cluster is currently in a blackout window or if continuous replication for the replication relationship is disabled, replication doesn't begin. For more information, see [Replication: Blackout Windows](https://care.qumulo.com/hc/en-us/articles/360019101513) on Qumulo Care." %} -1. Log in to the Web UI on the target cluster. +1. Log in to the Qumulo Core Web UI on the target cluster. A notification banner informing you of a new relationship authorization request appears. @@ -88,7 +88,7 @@ The following privileges are required for continuous replication. ## To View the Status of a Replication Relationship -1. Log in to the Web UI on the source cluster. +1. Log in to the Qumulo Core Web UI on the source cluster. 1. Click **Cluster > Replication**. @@ -139,7 +139,7 @@ The following privileges are required for continuous replication. ## To Modify a Replication Relationship {% include note.html content="It isn't possible to edit the source and target directory paths. To make these changes, you must create a new replication relationship." %} -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Cluster > Replication**. @@ -150,7 +150,7 @@ The following privileges are required for continuous replication. ## To Delete a Replication Relationship -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Cluster > Replication**. diff --git a/_includes/content-reuse/admin-guides/replicating-data/shift-from-s3.md b/_includes/content-reuse/admin-guides/replicating-data/shift-from-s3.md index 73ab7879f..277972545 100644 --- a/_includes/content-reuse/admin-guides/replicating-data/shift-from-s3.md +++ b/_includes/content-reuse/admin-guides/replicating-data/shift-from-s3.md @@ -130,7 +130,7 @@ This section describes how to use the Qumulo Core Web UI 4.2.5 (and higher) to c 1. In the **Create Copy from S3?** dialog box, review the Shift relationship and then click **Yes, Create**. - The copy job begins and Qumulo Core estimates the work to be performed. When the estimation is complete, the Web UI displays a progress bar with a percentage for a relationship on the **Replication Relationships** page. The page also displays the estimated total work, the remaining bytes and files, and the estimated time to completion for a running copy job. + The copy job begins and Qumulo Core estimates the work to be performed. When the estimation is complete, the Qumulo Core Web UI displays a progress bar with a percentage for a relationship on the **Replication Relationships** page. The page also displays the estimated total work, the remaining bytes and files, and the estimated time to completion for a running copy job. {% include note.html content="For work estimates, Shift-From jobs calculate the total number of files and bytes in a job's bucket prefix. This requires the job to use the [`ListObjectV2` S3 action](https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html) once for every 5,000 objects (or 200 times for every 1 million objects)." %} diff --git a/_includes/content-reuse/admin-guides/replicating-data/shift-to-s3.md b/_includes/content-reuse/admin-guides/replicating-data/shift-to-s3.md index 163b3e9fe..bea1426fe 100644 --- a/_includes/content-reuse/admin-guides/replicating-data/shift-to-s3.md +++ b/_includes/content-reuse/admin-guides/replicating-data/shift-to-s3.md @@ -3,7 +3,7 @@ For more information about copying objects from S3 to Qumulo, see [Using Qumulo ## Prerequisites * A Qumulo cluster with: - * Qumulo Core 3.2.1 (and higher) for the CLI and 3.2.5 (and higher) for the Web UI + * Qumulo Core 3.2.1 (and higher) for the CLI and 3.2.5 (and higher) for the Qumulo Core Web UI * HTTPS connectivity to `s3..amazonaws.com` though one of the following means: diff --git a/_includes/content-reuse/admin-guides/s3-api/configuring-using-s3-api.md b/_includes/content-reuse/admin-guides/s3-api/configuring-using-s3-api.md index d26dd657d..d7a2be02d 100644 --- a/_includes/content-reuse/admin-guides/s3-api/configuring-using-s3-api.md +++ b/_includes/content-reuse/admin-guides/s3-api/configuring-using-s3-api.md @@ -9,7 +9,7 @@ The Qumulo Core S3 API accepts only HTTPS requests by default. To enable HTTPS s Every Qumulo cluster is preconfigured with a self-signed SSL certificate. However, because certain applications don't accept the default certificate, we recommend installing your own. -For information about configuring HTTPS for your cluster, see [Installing the Web UI SSL Certificate](https://care.qumulo.com/hc/en-us/articles/17652500917779) on Qumulo Care. +For information about configuring HTTPS for your cluster, see [Installing the Qumulo Core Web UI SSL Certificate](https://care.qumulo.com/hc/en-us/articles/17652500917779) on Qumulo Care. ### Enabling and Disabling Plaintext HTTP Connections {% include important.html content="If you configure the S3 API service to accept only plaintext HTTP connections, no requests made through the S3 API are encrypted." %} diff --git a/_includes/content-reuse/admin-guides/s3-api/creating-managing-s3-access-keys.md b/_includes/content-reuse/admin-guides/s3-api/creating-managing-s3-access-keys.md index 62aea096b..41eda9b95 100644 --- a/_includes/content-reuse/admin-guides/s3-api/creating-managing-s3-access-keys.md +++ b/_includes/content-reuse/admin-guides/s3-api/creating-managing-s3-access-keys.md @@ -231,7 +231,7 @@ Send a `DELETE` request to the `/v1/s3/access-keys/` Qumulo REST For users that exist in an AD domain that has a trust relationship with the joined domain, you must append that domain's base DN to the base DN in your Qumulo cluster's AD configuration. -To append the trusted base DN to the base DN in use—with a semicolon (`;`) separating the two—use the Web UI or the `qq ad_reconfigure` command. For example: +To append the trusted base DN to the base DN in use—with a semicolon (`;`) separating the two—use the Qumulo Core Web UI or the `qq ad_reconfigure` command. For example: ```bash $ qq ad_reconfigure \ diff --git a/_includes/content-reuse/admin-guides/smb/creating-smb-share.md b/_includes/content-reuse/admin-guides/smb/creating-smb-share.md index a8733bb6e..b8ef08f68 100644 --- a/_includes/content-reuse/admin-guides/smb/creating-smb-share.md +++ b/_includes/content-reuse/admin-guides/smb/creating-smb-share.md @@ -1,7 +1,7 @@ ## To Create an SMB Share -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > SMB Shares**. @@ -42,7 +42,7 @@ ## To Modify an SMB Share -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > SMB Shares**. @@ -53,7 +53,7 @@ ## To Delete an SMB Share -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Sharing > SMB Shares**. diff --git a/_includes/content-reuse/admin-guides/snapshots/managing-snapshots.md b/_includes/content-reuse/admin-guides/snapshots/managing-snapshots.md index d2958a753..4ed716847 100644 --- a/_includes/content-reuse/admin-guides/snapshots/managing-snapshots.md +++ b/_includes/content-reuse/admin-guides/snapshots/managing-snapshots.md @@ -1,5 +1,5 @@ -## Managing Snapshots by Using the Web UI -This section explains how to create on-demand snapshots and snapshot policies, view and search for existing snapshots, and delete snapshots by using the Web UI. +## Managing Snapshots by Using the Qumulo Core Web UI +This section explains how to create on-demand snapshots and snapshot policies, view and search for existing snapshots, and delete snapshots by using the Qumulo Core Web UI. ### To Create an On-Demand Snapshot {{page.varLogin}} @@ -146,7 +146,7 @@ qq snapshot_create_snapshot \ ``` ### Modifying a Snapshot's Expiration Time -Use the `qq snapshot_modify_snapshot` command and specify the snapshot ID from the **Saved Snapshots** page in the Web UI (for example, for the `1234567_replication_from_prod` snapshot, the ID is `1234567`). +Use the `qq snapshot_modify_snapshot` command and specify the snapshot ID from the **Saved Snapshots** page in the Qumulo Core Web UI (for example, for the `1234567_replication_from_prod` snapshot, the ID is `1234567`). In the following example, the snapshot with ID `1234567` never expires. diff --git a/_includes/content-reuse/admin-guides/upgrading-qumulo-core/replication-version-requirements-upgrade-recommendations.md b/_includes/content-reuse/admin-guides/upgrading-qumulo-core/replication-version-requirements-upgrade-recommendations.md index c3325515f..89c2d4260 100644 --- a/_includes/content-reuse/admin-guides/upgrading-qumulo-core/replication-version-requirements-upgrade-recommendations.md +++ b/_includes/content-reuse/admin-guides/upgrading-qumulo-core/replication-version-requirements-upgrade-recommendations.md @@ -214,9 +214,9 @@ To avoid having to resynchronize your clusters after you reconnect the replicati On clusters that run Qumulo Core 2.12.5 (and lower), this process requires additional time to resynchronize the clusters by running a full-tree scan after you reconnect the replication relationship. -1. To temporarily make the target relationship writable for the duration of the upgrade, use the **Make Target Writable** action in the Web UI. +1. To temporarily make the target relationship writable for the duration of the upgrade, use the **Make Target Writable** action in the Qumulo Core Web UI. 1. Wait for the upgrade to complete. -1. Use the **Reconnect Relationship** action in the Web UI. +1. Use the **Reconnect Relationship** action in the Qumulo Core Web UI. {% endif %} diff --git a/_includes/content-reuse/admin-guides/web-ui/inactivity-timeout.md b/_includes/content-reuse/admin-guides/web-ui/inactivity-timeout.md index 33e1137a8..05c11362f 100644 --- a/_includes/content-reuse/admin-guides/web-ui/inactivity-timeout.md +++ b/_includes/content-reuse/admin-guides/web-ui/inactivity-timeout.md @@ -1,15 +1,15 @@ -In Qumulo Core 5.1.0 (and higher), clusters have an optional _inactivity timeout_ that logs users out of the Web UI if they don't interact with it for a specified amount of time. +In Qumulo Core 5.1.0 (and higher), clusters have an optional _inactivity timeout_ that logs users out of the Qumulo Core Web UI if they don't interact with it for a specified amount of time. {% include note.html content="During the final minute of the timeout period, the **Your Session is About to Expire** dialog box appears. The dialog box shows a countdown and lets the user renew the session or log out immediately. When deciding on the timeout length, take your users' needs into consideration." %} -## To Set the Web UI Inactivity Timeout +## To Set the Qumulo Core Web UI Inactivity Timeout To set an inactivity timeout, use the `web_ui_modify_settings` command. Specify the timeout in minutes by using the `--inactivity-timeout` flag. For example: ```bash qq web_ui_modify_settings --inactivity-timeout 15 ``` -## To Clear the Web UI Inactivity Timeout +## To Clear the Qumulo Core Web UI Inactivity Timeout To clear an inactivity timeout, use the `web_ui_modify_settings` command with the `--disable-inactivity-timeout` flag. ```bash diff --git a/_includes/content-reuse/admin-guides/web-ui/login-banner.md b/_includes/content-reuse/admin-guides/web-ui/login-banner.md index c2ed1ffcf..ec2266a7e 100644 --- a/_includes/content-reuse/admin-guides/web-ui/login-banner.md +++ b/_includes/content-reuse/admin-guides/web-ui/login-banner.md @@ -1,13 +1,13 @@ -In Qumulo Core 5.2.1 (and higher), clusters have an optional login banner that users must acknowledge before being they can log in to the Web UI. +In Qumulo Core 5.2.1 (and higher), clusters have an optional login banner that users must acknowledge before being they can log in to the Qumulo Core Web UI. -## To Set the Web UI Login Banner +## To Set the Qumulo Core Web UI Login Banner To set the login banner, use the `web_ui_modify_settings` command. To specify the Markdown file to use for the banner, use the `--login-banner` flag. For example: ```bash qq web_ui_modify_settings --login-banner my-banner.html ``` -## To Clear the Web UI Login Banner +## To Clear the Qumulo Core Web UI Login Banner To clear the login banner, use the `web_ui_modify_settings` command with the `--disable-login-banner` flag. ```bash diff --git a/_includes/content-reuse/kerberos-ntp-server.md b/_includes/content-reuse/kerberos-ntp-server.md index efc192a29..363637a89 100644 --- a/_includes/content-reuse/kerberos-ntp-server.md +++ b/_includes/content-reuse/kerberos-ntp-server.md @@ -1,5 +1,5 @@ Kerberos is very sensitive to clock skew. It is important for all systems involved in a Kerberos relationship—the KDC, your Qumulo cluster, and any Linux clients—to have as little clock skew as possible. We recommend using the same NTP server for all three components. -* You can use your AD domain controller as an NTP server. In the Web UI, on the **Active Directory** page, for **Use Active Directory as your primary time server**, click **Yes**. +* You can use your AD domain controller as an NTP server. In the Qumulo Core Web UI, on the **Active Directory** page, for **Use Active Directory as your primary time server**, click **Yes**. -* To configure any other NTP server in the Web UI, click **Cluster > Date & Time**. +* To configure any other NTP server in the Qumulo Core Web UI, click **Cluster > Date & Time**. diff --git a/_includes/content-reuse/monitoring-data-protection-reconfiguration-process.md b/_includes/content-reuse/monitoring-data-protection-reconfiguration-process.md index ab409b334..cd22385c1 100644 --- a/_includes/content-reuse/monitoring-data-protection-reconfiguration-process.md +++ b/_includes/content-reuse/monitoring-data-protection-reconfiguration-process.md @@ -1,15 +1,15 @@ ## Monitoring the Data Protection Reconfiguration Process To view the progress of the three stages of the data protection reconfiguration process, log in to the Qumulo Core Web UI and click **Cluster**. -1. Qumulo Core begins to move data to new nodes in the cluster and the Web UI displays the message **Rebalancing for data protection reconfiguration**. +1. Qumulo Core begins to move data to new nodes in the cluster and the Qumulo Core Web UI displays the message **Rebalancing for data protection reconfiguration**. -1. Qumulo Core reencodes all data on your cluster and the Web UI displays the message **Reconfiguring data protection**. +1. Qumulo Core reencodes all data on your cluster and the Qumulo Core Web UI displays the message **Reconfiguring data protection**. {% include note.html content="In certain scenarios, this stage might appear to pause while the system performs preparatory work on the cluster." %} When this stage is complete, your data is protected according to the cluster's new configuration and the system begins to use the new drive and node fault tolerance levels. -1. Qumulo Core adds new capacity to your cluster and the Web UI displays the message **Rabalancing**. +1. Qumulo Core adds new capacity to your cluster and the Qumulo Core Web UI displays the message **Rabalancing**. If you initiated the reconfiguration process as part of a node replacement step, the system migrates data from the existing nodes in the cluster. diff --git a/administrator-guide/authentication-qumulo-core/installing-vpn-keys-on-cluster.md b/administrator-guide/authentication-qumulo-core/installing-vpn-keys-on-cluster.md index b4926d433..dfcc85871 100644 --- a/administrator-guide/authentication-qumulo-core/installing-vpn-keys-on-cluster.md +++ b/administrator-guide/authentication-qumulo-core/installing-vpn-keys-on-cluster.md @@ -103,7 +103,7 @@ Before you begin, make sure that you have done the following. 1. Send the output of the command to Qumulo Care. -1. Use the Web UI to enable Qumulo Care Remote Support. +1. Use the Qumulo Core Web UI to enable Qumulo Care Remote Support. 1. Notify Qumulo Care when this process is complete. diff --git a/administrator-guide/encryption-data-security/managing-encryption-at-rest.md b/administrator-guide/encryption-data-security/managing-encryption-at-rest.md index f490b62a8..b5d939d8e 100644 --- a/administrator-guide/encryption-data-security/managing-encryption-at-rest.md +++ b/administrator-guide/encryption-data-security/managing-encryption-at-rest.md @@ -117,7 +117,7 @@ This section explains how to configure Qumulo Core to use a master key stored lo {{site.data.alerts.caution}}
      • If the master key is deleted from the KMS, and all nodes in the cluster are rebooted, all data on the cluster becomes permanently unrecoverable.
        • -
      • If you allow the certificates to expire, or the master key is deleted accidentally, you must create a new, valid configuration as soon as possible. To warn you of this scenario, the Web UI indicates if any of your certificates are about to expire, or if the configured master key becomes unavailable.
        • +
      • If you allow the certificates to expire, or the master key is deleted accidentally, you must create a new, valid configuration as soon as possible. To warn you of this scenario, the Qumulo Core Web UI indicates if any of your certificates are about to expire, or if the configured master key becomes unavailable.
      {{site.data.alerts.end}} @@ -139,7 +139,7 @@ This section explains how to configure Qumulo Core to use a master key stored lo ## Rotating the Master Key -This section explains how to rotate the master key and check the encryption status for your cluster by using the `qq` CLI and how to check the encryption status by using the Web UI. +This section explains how to rotate the master key and check the encryption status for your cluster by using the `qq` CLI and how to check the encryption status by using the Qumulo Core Web UI. {% include caution.html content="[Qumulo Care](https://docs.qumulo.com/contacting-qumulo-care-team.html) team members can help you [rotate your master keys](#rotate-master-key). However, they don't have access to your encryption keys and can't retrieve them for you." %} @@ -163,7 +163,7 @@ This section explains how to rotate the master key and check the encryption stat In the output, ensure that the `key_id` field lists the new key ID. -### To Check the Encryption Status of a Qumulo Cluster by Using the Web UI +### To Check the Encryption Status of a Qumulo Cluster by Using the Qumulo Core Web UI 1. Log in to Qumulo Core. 1. On the **Dashboard** page, in the **Cluster Overview** section, click **More details**. diff --git a/administrator-guide/index.md b/administrator-guide/index.md index fc3d1ec9b..1cf57262f 100644 --- a/administrator-guide/index.md +++ b/administrator-guide/index.md @@ -1,6 +1,6 @@ --- title: "Qumulo On-Premises Administrator Guide" -summary: "The Qumulo On-Premises Administrator Guide contains information about getting started with, upgrading, and configuring Qumulo Core, and working with it by using the Web UI, qq CLI, and REST API." +summary: "The Qumulo On-Premises Administrator Guide contains information about getting started with, upgrading, and configuring Qumulo Core, and working with it by using the Qumulo Core Web UI, qq CLI, and REST API." layout: parent_landing_page permalink: /administrator-guide/ redirect_from: diff --git a/administrator-guide/kerberos/kerberos-configuring-active-directory.md b/administrator-guide/kerberos/kerberos-configuring-active-directory.md index 61bc26ee5..765acdb32 100644 --- a/administrator-guide/kerberos/kerberos-configuring-active-directory.md +++ b/administrator-guide/kerberos/kerberos-configuring-active-directory.md @@ -3,7 +3,7 @@ title: "Configuring Active Directory for Use With Kerberos" summary: "This section describes the Active Directory Domain Controller (DC) configuration changes necessary for enabling NFSv4.1 with Kerberos." permalink: /administrator-guide/kerberos/kerberos-configuring-active-directory.html sidebar: administrator_guide_sidebar -varMachineAccount: To find the machine account name in the Web UI, click **Cluster > Active Directory** and write down the name under **Machine Account**. +varMachineAccount: To find the machine account name in the Qumulo Core Web UI, click **Cluster > Active Directory** and write down the name under **Machine Account**. varLowercase: To maximize compatibility with Linux, we recommend formatting SPN entries in lowercase. include_content: content-reuse/admin-guides/kerberos/kerberos-configuring-active-directory.md --- diff --git a/administrator-guide/monitoring-and-metrics/enabling-cloud-based-monitoring-remote-support.md b/administrator-guide/monitoring-and-metrics/enabling-cloud-based-monitoring-remote-support.md index 89b3664e3..0fac24605 100644 --- a/administrator-guide/monitoring-and-metrics/enabling-cloud-based-monitoring-remote-support.md +++ b/administrator-guide/monitoring-and-metrics/enabling-cloud-based-monitoring-remote-support.md @@ -116,11 +116,11 @@ Before you can use Cloud-Based monitoring and Remote Support, you must: ## Enabling Cloud-Based Monitoring -You can enable Cloud-Based Monitoring by using the Web UI or `qq` CLI. +You can enable Cloud-Based Monitoring by using the Qumulo Core Web UI or `qq` CLI. -### To Enable Cloud-Based Monitoring by Using the Web UI +### To Enable Cloud-Based Monitoring by Using the Qumulo Core Web UI -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Support > Qumulo Care**. @@ -143,9 +143,9 @@ You can enable Cloud-Based Monitoring by using the Web UI or `qq` CLI. ## Enabling Remote Support -You can enable Remote Support by using the Web UI or `qq` CLI. +You can enable Remote Support by using the Qumulo Core Web UI or `qq` CLI. -### To Enable Remote Support by Using the Web UI +### To Enable Remote Support by Using the Qumulo Core Web UI 1. Log in to he Web UI. diff --git a/administrator-guide/network-multitenancy/configuring-management-protocols.md b/administrator-guide/network-multitenancy/configuring-management-protocols.md index 54871f532..fd5408245 100644 --- a/administrator-guide/network-multitenancy/configuring-management-protocols.md +++ b/administrator-guide/network-multitenancy/configuring-management-protocols.md @@ -50,7 +50,7 @@ The Qumulo Core Web UI lets you manage clusters from a browser. * To disable access, use the `--disable-web-ui` flag. -In the following example, the cluster begins to serve the Web UI on TCP ports 80 and 433 on all networks assigned to the tenant. +In the following example, the cluster begins to serve the Qumulo Core Web UI on TCP ports 80 and 433 on all networks assigned to the tenant. ```bash $ qq multitenancy_modify_tenant \ diff --git a/administrator-guide/network-multitenancy/partitioning-cluster-into-tenants.md b/administrator-guide/network-multitenancy/partitioning-cluster-into-tenants.md index f5b9bc18b..18bc8b535 100644 --- a/administrator-guide/network-multitenancy/partitioning-cluster-into-tenants.md +++ b/administrator-guide/network-multitenancy/partitioning-cluster-into-tenants.md @@ -133,7 +133,7 @@ $ qq multitenancy_get_tenant \ ``` #### Viewing Information for All Tenants -* In the Web UI, log in to Qumulo Core and then click **Cluster > Network Multitenancy**. +* In the Qumulo Core Web UI, log in to Qumulo Core and then click **Cluster > Network Multitenancy**. * In the `qq` CLI, use the `multitenancy_list_tenants` command. diff --git a/administrator-guide/node-addition-replacement/adding-nodes-existing-cluster.md b/administrator-guide/node-addition-replacement/adding-nodes-existing-cluster.md index f53ee75af..f3b09c6a6 100644 --- a/administrator-guide/node-addition-replacement/adding-nodes-existing-cluster.md +++ b/administrator-guide/node-addition-replacement/adding-nodes-existing-cluster.md @@ -5,7 +5,7 @@ permalink: /administrator-guide/node-addition-replacement/adding-nodes-existing- sidebar: administrator_guide_sidebar --- -After you connect and power on your new nodes, Qumulo Core discovers any unconfigured nodes automatically and prompts you to add nodes in the Web UI. +After you connect and power on your new nodes, Qumulo Core discovers any unconfigured nodes automatically and prompts you to add nodes in the Qumulo Core Web UI. If Qumulo Core doesn't discover any unconfigured nodes, it displays the message **No unconfigured nodes found**. If you expect to see nodes, {{site.contactQumuloCare}}. @@ -20,7 +20,7 @@ If Qumulo Core doesn't discover any unconfigured nodes, it displays the message ## Prerequisites * **Sufficient Static IP Addresses:** The number of static IP addresses must be equal to or greater than the number of nodes in your cluster. For more information, see [IP Failover with Qumulo Core](https://care.qumulo.com/hc/en-us/articles/115007075107) on Qumulo Care. -* **Same Qumulo Core Version on All Nodes:** For information about upgrading Qumulo Core, see [Performing a Clean Installation of Qumulo Core](https://care.qumulo.com/hc/en-us/articles/360011477954) and [Performing Qumulo Core Upgrades by Using the Web UI](https://care.qumulo.com/hc/en-us/articles/115007247168) on Qumulo Care. +* **Same Qumulo Core Version on All Nodes:** For information about upgrading Qumulo Core, see [Performing a Clean Installation of Qumulo Core](https://care.qumulo.com/hc/en-us/articles/360011477954) and [Performing Qumulo Core Upgrades](https://docs.qumulo.com/administrator-guide/upgrading-qumulo-core/performing-upgrades.html). ## Step 1: Resolve Drive Compatibility Issues @@ -28,13 +28,13 @@ If Qumulo Core doesn't discover any unconfigured nodes, it displays the message To receive support for new, Qumulo-certified drives, do one of the following: -* Upgrade your existing cluster to the latest version of Qumulo Core and then install the same version of Qumulo Core on your new node. For more information, see [Performing Qumulo Core Upgrades by Using the Web UI](https://care.qumulo.com/hc/en-us/articles/115007247168) on Qumulo Care. +* Upgrade your existing cluster to the latest version of Qumulo Core and then install the same version of Qumulo Core on your new node. For more information, see [Performing Qumulo Core Upgrades by Using the Qumulo Core Web UI](https://care.qumulo.com/hc/en-us/articles/115007247168) on Qumulo Care. * Update the Supported Drive List on your new node. For more information, {{site.contactQumuloCare}}. ## Step 2: Add Your New Nodes to an Existing Qumulo Cluster -1. Log in to the Web UI. +1. Log in to the Qumulo Core Web UI. 1. Click **Cluster > Add Nodes**. @@ -48,4 +48,4 @@ To receive support for new, Qumulo-certified drives, do one of the following: Qumulo Core configures your new nodes and adds them to your cluster. -On the **Cluster** page, the Web UI shows the banner **Successfully added <N> nodes to the cluster** and the total available storage. +On the **Cluster** page, the Qumulo Core Web UI shows the banner **Successfully added <N> nodes to the cluster** and the total available storage. diff --git a/administrator-guide/node-addition-replacement/replacing-nodes-transparent-platform-refresh.md b/administrator-guide/node-addition-replacement/replacing-nodes-transparent-platform-refresh.md index 7fbc1a55c..12ac1768c 100644 --- a/administrator-guide/node-addition-replacement/replacing-nodes-transparent-platform-refresh.md +++ b/administrator-guide/node-addition-replacement/replacing-nodes-transparent-platform-refresh.md @@ -43,13 +43,13 @@ There are two node replacement plan types: * - While a node replacement step is in progress, both new nodes and nodes marked for replacement appear on the **Cluster** page of the Web UI and clients can connect to any of the nodes in the _combined cluster_ while the step is in progress. + While a node replacement step is in progress, both new nodes and nodes marked for replacement appear on the **Cluster** page of the Qumulo Core Web UI and clients can connect to any of the nodes in the _combined cluster_ while the step is in progress. * When a node replacement step is complete, the reassignment of static IP addresses differs between versions of Qumulo Core: * In Qumulo Core 6.3.0.1 (and higher), the static IP addresses assigned to nodes remain unchanged and Qumulo Core removes only the static IP addresses for nodes removed from the cluster. - * In Qumulo Core versions lower than 6.3.0.1, Qumulo Core reassigns static IP addresses to different nodes. To view the reassigned IP addresses in the Web UI, click **Cluster > Network Configuration.** + * In Qumulo Core versions lower than 6.3.0.1, Qumulo Core reassigns static IP addresses to different nodes. To view the reassigned IP addresses in the Qumulo Core Web UI, click **Cluster > Network Configuration.** * When Qumulo Core adds nodes to a cluster, it assigns node IDs sequentially, without reusing or changing IDs. @@ -132,7 +132,7 @@ Ensure that the number of static and floating IP addresses is equal to or greate After each node replacement step, Qumulo Core begins to migrate data from existing nodes in the backround. - {% include note.html content="This is a long process (that can take days or weeks). When the data migration is complete, Qumulo Core removes the nodes marked for replacement from the cluster. These nodes no longer appear on the **Cluster** page of the Web UI." %} + {% include note.html content="This is a long process (that can take days or weeks). When the data migration is complete, Qumulo Core removes the nodes marked for replacement from the cluster. These nodes no longer appear on the **Cluster** page of the Qumulo Core Web UI." %} 1. Unrack the removed nodes from your data center. diff --git a/administrator-guide/snapshots/managing-snapshots.md b/administrator-guide/snapshots/managing-snapshots.md index a8e6ba69b..014e43260 100644 --- a/administrator-guide/snapshots/managing-snapshots.md +++ b/administrator-guide/snapshots/managing-snapshots.md @@ -1,6 +1,6 @@ --- title: "Managing Snapshots in Qumulo Core" -summary: "This section explains how to create on-demand snapshots and snapshot policies, view and search for existing snapshots, and delete snapshots by using the Web UI. It also explains how to create snapshots on a schedule, create a snapshot with an expiration time, and modify a snapshot's expiration time." +summary: "This section explains how to create on-demand snapshots and snapshot policies, view and search for existing snapshots, and delete snapshots by using the Qumulo Core Web UI. It also explains how to create snapshots on a schedule, create a snapshot with an expiration time, and modify a snapshot's expiration time." permalink: /administrator-guide/snapshots/managing-snapshots.html redirect_from: - /managing-snapshots.html diff --git a/administrator-guide/upgrading-qumulo-core/feature-log.md b/administrator-guide/upgrading-qumulo-core/feature-log.md index ae82c47f9..ba1e3caf3 100644 --- a/administrator-guide/upgrading-qumulo-core/feature-log.md +++ b/administrator-guide/upgrading-qumulo-core/feature-log.md @@ -58,7 +58,7 @@ For information about upgrade types for each release, see
    • This release resolves an issue in Qumulo 6.2.1.1 that interrupted the functioning of cross-realm Kerberos authentication when the system returns CNAMEs for PTR records while performing reverse DNS lookups.
      • -
    • This release resolves an issue in Qumulo Core 6.2.1 that affected the persistence of cluster network settings configured by using the Web UI.
      • +
    • This release resolves an issue in Qumulo Core 6.2.1 that affected the persistence of cluster network settings configured by using the Qumulo Core Web UI.
    • This release removes the flag --dns-config-id that was added in Qumulo Core 6.2.1. This flag prevents the normal functioning of the qq fs_list_locks command.
    • This release resolves an issue that we have identified in Qumulo Core 6.1.0 (and higher), where a potential session impersonation exploit was possible when a client accesses a Qumulo cluster by using the SMB protocol.
    @@ -133,12 +133,12 @@ For information about upgrade types for each release, see Performing Qumulo Core Upgrades by Using the qq CLI on Qumulo Care." -permalink: /administrator-guide/upgrading-qumulo-core/instant-software-platform.html +title: "Performing Qumulo Core Upgrades" +summary: "This section explains the difference between Qumulo Core Instant Software Upgrades and Platform Upgrades and how to perform upgrades." +permalink: /administrator-guide/upgrading-qumulo-core/performing-upgrades.html redirect_from: + - /administrator-guide/upgrading-qumulo-core/instant-software-platform.html - /administrator-guide/upgrades/instant-software-platform.html sidebar: administrator_guide_sidebar varContactQumuloCare: If you perform multiple upgrades back to back, you might encounter one or more platform upgrades in one of the incremental releases; you must install these upgrades before you continue. Before performing back to back upgrades, contact the Qumulo Care team for guidance. @@ -49,7 +50,6 @@ The reboot process differentiates platform upgrades from instant software upgrad ## Understanding the Upgrade Phases - Every Qumulo Core upgrade has two phases, _preparation_ and _commit_. 1. **Preparation:** Qumulo Core stages a new image in an alternate boot drive partition while the current image continues to run. This phase is responsible only for the background work (unpacking and writing the platform image and upgrade firmware, and so on). When the preparation phase is complete, we continue to the commit phase. @@ -74,3 +74,41 @@ To determine what phase an upgrade is in, use the `qq upgrade_status` command wh "blocked_reason": "" } ``` + +## Upgrading Your Qumulo Cluster +{{site.data.alerts.important}} +
      +
    • Before beginning the upgrade process, make sure that you have the correct cloud upgrade image{{site.loginRequired}} or on-premises upgrade image{{site.loginRequired}}.
      • +
    • To allow certain background processes to run, multiple sequential Qumulo Core upgrades might require a waiting period between specific releases. Before installing multiple Qumulo Core releases within an extended maintenance window, {{site.contactQumuloCare}}.
      • +
    • When the node to which you are connected reboots, the Qumulo Core Web UI might redirect you to the Cluster is booting... page. To view the reboot status, you can connect to a different node or wait until the current node goes online and then click Support > Software Upgrade.
      • +
    • During rolling reboots, the system reboots one or more nodes (depending on the configured protection level) in the cluster in succession. If your cluster is under heavy load due to write or delete operations, this proces can take a long time.
      • +
    +{{site.data.alerts.end}} + +### To Upgrade Your Qumulo Cluster + +1. Upload the `qumulo_core_x.x.x.qimg` upgrade file to any directory on your cluster by using a client protocol such as NFS or SMB. + +1. Log in to the Qumulo Core Web UI. + +1. **Click Support > Software Upgrade**. + +1. On the **Software Upgrade** page, enter the file system path for the upgrade file without the leading slash, for example: `upgrade/qumulo_core_7.1.0.qimg`. + +1. Click **Upgrade...** + + Depending on the [upgrade mode for your release](mode-reference.html), continue to one of the following sections. + + * **Instant Software Upgrade:** In the **Ready to upgrade?** dialog box, confirm the current and new versions of Qumulo Core and then click **Start Upgrade**. + + On the **Software Upgrade** page, the upgrade progress is displayed. + + * **Platform Upgrade:** In the **Ready to upgrade?** dialog box, choose one of the following modes and then click **Start Upgrade**. + + * **Complete reboot (with SMB and NFS client interruption):** You can't access your cluster during the reboot process. + + * **Rolling reboot (with SMB client impact):** You can access your cluster during reboot, but SMB connectivity to specific nodes is impacted. + + Qumulo Core prepares the upgrade then installs Qumulo software on your cluster. + + When the upgrade is complete, the message **You have successfully upgraded from Qumulo Core x.x.x to y.y.y** is displayed. diff --git a/administrator-guide/web-ui/inactivity-timeout.md b/administrator-guide/web-ui/inactivity-timeout.md index 87a2b8e1a..6c2962e49 100644 --- a/administrator-guide/web-ui/inactivity-timeout.md +++ b/administrator-guide/web-ui/inactivity-timeout.md @@ -1,5 +1,5 @@ --- -title: "Setting the Web UI Inactivity Timeout" +title: "Setting the Qumulo Core Web UI Inactivity Timeout" summary: "This section explains how to set an inactivity timeout for the Qumulo Core Web UI." permalink: /administrator-guide/web-ui/inactivity-timeout.html redirect_from: diff --git a/administrator-guide/web-ui/login-banner.md b/administrator-guide/web-ui/login-banner.md index e9990fecd..02ded00ca 100644 --- a/administrator-guide/web-ui/login-banner.md +++ b/administrator-guide/web-ui/login-banner.md @@ -1,5 +1,5 @@ --- -title: "Setting the Web UI Login Banner" +title: "Setting the Qumulo Core Web UI Login Banner" summary: "This section explains how to set a login banner for the Qumulo Core Web UI." permalink: /administrator-guide/web-ui/login-banner.html redirect_from: diff --git a/azure-administrator-guide/getting-started/deploying-instance-azure-native-qumulo.md b/azure-administrator-guide/getting-started/deploying-instance-azure-native-qumulo.md index 9c2a04513..0094c3eea 100644 --- a/azure-administrator-guide/getting-started/deploying-instance-azure-native-qumulo.md +++ b/azure-administrator-guide/getting-started/deploying-instance-azure-native-qumulo.md @@ -73,7 +73,7 @@ This section explains how to deploy the {{site.azure.qumuloOnAzureShort}} servic 1. To create a service, click **Next: Review + Create >**. -## Viewing Service Information and Connecting to the Web UI +## Viewing Service Information and Connecting to the Qumulo Core Web UI When Azure finishes creating your service, you can view information about the service and start using the Qumulo Core Web UI. ### Viewing the IP Addresses of Your Service @@ -81,8 +81,8 @@ To view the IP addresses associated with your service, click **IP Addresses** on {% include tip.html content="We recommend using round-robin DNS to [load balance](virtual-networking-prerequisites-azure-native-qumulo.html#load-balanced-endpoints) traffic across your service IP addresses." %} -### To Log in to the Web UI -To log in to the Web UI, you must identify your service endpoint. +### To Log in to the Qumulo Core Web UI +To log in to the Qumulo Core Web UI, you must identify your service endpoint. 1. Click **Overview** and then copy the **Qumulo Core Web UI Login** URL. For example: diff --git a/azure-administrator-guide/kerberos/kerberos-configuring-active-directory.md b/azure-administrator-guide/kerberos/kerberos-configuring-active-directory.md index 9aec8a503..9a2c2bba0 100644 --- a/azure-administrator-guide/kerberos/kerberos-configuring-active-directory.md +++ b/azure-administrator-guide/kerberos/kerberos-configuring-active-directory.md @@ -3,7 +3,7 @@ title: "Configuring Active Directory for Use With Kerberos" summary: "This section describes the Active Directory Domain Controller (DC) configuration changes necessary for enabling NFSv4.1 with Kerberos." permalink: /azure-administrator-guide/kerberos/kerberos-configuring-active-directory.html sidebar: azure_administrator_guide_sidebar -varMachineAccount: To find the machine account name in the Web UI, click **Cluster > Active Directory** and write down the name under **Machine Account**. +varMachineAccount: To find the machine account name in the Qumulo Core Web UI, click **Cluster > Active Directory** and write down the name under **Machine Account**. varLowercase: To maximize compatibility with Linux, we recommend formatting SPN entries in lowercase. include_content: content-reuse/admin-guides/kerberos/kerberos-configuring-active-directory.md --- diff --git a/azure-administrator-guide/snapshots/managing-snapshots.md b/azure-administrator-guide/snapshots/managing-snapshots.md index ff2b74822..6eb46905e 100644 --- a/azure-administrator-guide/snapshots/managing-snapshots.md +++ b/azure-administrator-guide/snapshots/managing-snapshots.md @@ -1,6 +1,6 @@ --- title: "Managing Snapshots in Qumulo Core" -summary: "This section explains how to create on-demand snapshots and snapshot policies, view and search for existing snapshots, and delete snapshots by using the Web UI. It also explains how to create snapshots on a schedule, create a snapshot with an expiration time, and modify a snapshot's expiration time." +summary: "This section explains how to create on-demand snapshots and snapshot policies, view and search for existing snapshots, and delete snapshots by using the Qumulo Core Web UI. It also explains how to create snapshots on a schedule, create a snapshot with an expiration time, and modify a snapshot's expiration time." permalink: /azure-administrator-guide/snapshots/managing-snapshots.html sidebar: azure_administrator_guide_sidebar varLogin: 1. Log in to the Qumulo Core Web UI. diff --git a/azure-administrator-guide/web-ui/inactivity-timeout.md b/azure-administrator-guide/web-ui/inactivity-timeout.md index 27b7bb19f..dd4adc507 100644 --- a/azure-administrator-guide/web-ui/inactivity-timeout.md +++ b/azure-administrator-guide/web-ui/inactivity-timeout.md @@ -1,5 +1,5 @@ --- -title: "Setting the Web UI Inactivity Timeout" +title: "Setting the Qumulo Core Web UI Inactivity Timeout" summary: "This section explains how to set an inactivity timeout for the Qumulo Core Web UI." permalink: /azure-administrator-guide/web-ui/inactivity-timeout.html sidebar: azure_administrator_guide_sidebar diff --git a/azure-administrator-guide/web-ui/login-banner.md b/azure-administrator-guide/web-ui/login-banner.md index 4b44e27af..5fa881844 100644 --- a/azure-administrator-guide/web-ui/login-banner.md +++ b/azure-administrator-guide/web-ui/login-banner.md @@ -1,5 +1,5 @@ --- -title: "Setting the Web UI Login Banner" +title: "Setting the Qumulo Core Web UI Login Banner" summary: "This section explains how to set a login banner for the Qumulo Core Web UI." permalink: /azure-administrator-guide/web-ui/login-banner.html sidebar: azure_administrator_guide_sidebar diff --git a/qq-cli-command-guide/cluster/cluster_create.md b/qq-cli-command-guide/cluster/cluster_create.md index b6e2b49c6..67d0d4218 100644 --- a/qq-cli-command-guide/cluster/cluster_create.md +++ b/qq-cli-command-guide/cluster/cluster_create.md @@ -65,4 +65,4 @@ usage: "qq cluster_create [-h] --cluster-name CLUSTER_NAME [--admin-password ADM zendesk_source: qq CLI Command Guide --- -{% include important.html content="To ensure that the Web UI displays the nodes in your cluster in the same order that they are racked, enter the node UUIDs in the same order when you run the `qq cluster_create` command." %} +{% include important.html content="To ensure that the Qumulo Core Web UI displays the nodes in your cluster in the same order that they are racked, enter the node UUIDs in the same order when you run the `qq cluster_create` command." %} diff --git a/qq-cli-command-guide/saml/saml_modify_settings.md b/qq-cli-command-guide/saml/saml_modify_settings.md index 5b2c788c5..c4d24cd28 100644 --- a/qq-cli-command-guide/saml/saml_modify_settings.md +++ b/qq-cli-command-guide/saml/saml_modify_settings.md @@ -35,7 +35,7 @@ optional_options: - alternate: [] help: If set, requires SSO for Active Directory (AD) users to be able to manage this cluster. The cluster rejects password-based authentication from AD users - of the Web UI, qq CLI, and REST API. This setting does not restrict access over + of the Qumulo Core Web UI, qq CLI, and REST API. This setting does not restrict access over file protocols such as SMB. name: --require-sso required: false diff --git a/qq-cli-command-guide/ssl/ssl_modify_certificate.md b/qq-cli-command-guide/ssl/ssl_modify_certificate.md index 17cc878bd..ac7966348 100644 --- a/qq-cli-command-guide/ssl/ssl_modify_certificate.md +++ b/qq-cli-command-guide/ssl/ssl_modify_certificate.md @@ -18,7 +18,7 @@ positional_options: [] sidebar: qq_cli_command_reference_sidebar summary: This section explains how to use the qq ssl_modify_certificate command. -synopsis: Set the SSL certificate chain and private key for the web UI and REST servers +synopsis: Set the SSL certificate chain and private key for the Qumulo Core Web UI and REST servers title: qq ssl_modify_certificate usage: qq ssl_modify_certificate [-h] -c CERTIFICATE -k PRIVATE_KEY zendesk_source: qq CLI Command Guide diff --git a/qq-cli-command-guide/web/web_ui_get_settings.md b/qq-cli-command-guide/web/web_ui_get_settings.md index 4293d3cce..29c839d91 100644 --- a/qq-cli-command-guide/web/web_ui_get_settings.md +++ b/qq-cli-command-guide/web/web_ui_get_settings.md @@ -15,7 +15,7 @@ positional_options: [] sidebar: qq_cli_command_reference_sidebar summary: This section explains how to use the qq web_ui_get_settings command. -synopsis: Get configuration options for the Web UI +synopsis: Get configuration options for the Qumulo Core Web UI title: qq web_ui_get_settings usage: qq web_ui_get_settings [-h] [--inactivity-timeout | --login-banner] zendesk_source: qq CLI Command Guide diff --git a/qq-cli-command-guide/web/web_ui_modify_settings.md b/qq-cli-command-guide/web/web_ui_modify_settings.md index 3366d72dd..98154b0fc 100644 --- a/qq-cli-command-guide/web/web_ui_modify_settings.md +++ b/qq-cli-command-guide/web/web_ui_modify_settings.md @@ -23,7 +23,7 @@ positional_options: [] sidebar: qq_cli_command_reference_sidebar summary: This section explains how to use the qq web_ui_modify_settings command. -synopsis: Modify configuration options for the Web UI +synopsis: Modify configuration options for the Qumulo Core Web UI title: qq web_ui_modify_settings usage: qq web_ui_modify_settings [-h] [--inactivity-timeout MINUTES | --disable-inactivity-timeout] [--login-banner BANNER_MARKDOWN_FILE | --disable-login-banner] diff --git a/qumulo-alerts-guide/installing-configuring-qumulo-alerts.md b/qumulo-alerts-guide/installing-configuring-qumulo-alerts.md index 8f2e4a7d6..3fb2371dd 100644 --- a/qumulo-alerts-guide/installing-configuring-qumulo-alerts.md +++ b/qumulo-alerts-guide/installing-configuring-qumulo-alerts.md @@ -154,7 +154,7 @@ To be able to generate access tokens, you must create a local user for Qumulo Al 1. Click **Save**. ### Step 4: Assign the Qumulo Alerts Role to Your Local Qumulo Core User -1. In the Web UI, click **Cluster > Role Management**. +1. In the Qumulo Core Web UI, click **Cluster > Role Management**. 1. On the **Role Management** page, in the **QumuloAlerts** section, click **Add Member**.