Merge pull request #148 from NetAppDocs/mgmt_svcs_brycecanyon_release

Merging PR for GA Bryce Canyon.

Author: netapp-mwallis

_data/sidebars/docs_sidebar.yml

@@ -30,9 +30,13 @@ entries:
             url: /concept_hci_volumes.html
           - title: Volume access groups
             url: /concept_hci_volume_access_groups.html
+          - title: Initiators
+            url: /concept_hci_initiators.html
           # url: /concept_hci_storage.html
       - title: Licensing
         url: /concept_cg_hci_licensing.html
+      - title: NetApp Hybrid Cloud Control configuration maximums
+        url: /reference_hcc_config_maximums.html
       - title: Security
         url: /concept_cg_hci_security.html
       - title: Performance
@@ -156,10 +160,14 @@ entries:
         entries:
           - title: Create and manage user accounts
             url: /task_hcc_manage_accounts.html
+          - title: Add and manage storage clusters
+            url: /task_hcc_manage_storage_clusters.html
           - title: Create and manage volumes
             url: /task_hcc_manage_vol_management.html
           - title: Create and manage volume access groups
             url: /task_hcc_manage_vol_access_groups.html
+          - title: Create and manage initiators
+            url: /task_hcc_manage_initiators.html
           - title: Create and manage volume QoS policies
             url: /task_hcc_qos_policies.html
       - title: Work with the management node
@@ -201,16 +209,24 @@ entries:
                 url: task_mnode_multi_vcenter_config.html
               - title: Add compute and controller assets to the management node
                 url: task_mnode_add_assets.html
-              - title: Remove an asset from the management node
-                url: task_mnode_remove_assets.html
+              - title: Create and manage storage cluster assets
+                url: /task_mnode_manage_storage_cluster_assets.html
               - title: View or edit existing controller assets
                 url: task_mnode_edit_vcenter_assets.html
+              - title: Remove an asset from the management node
+                url: task_mnode_remove_assets.html
               - title: Configure a proxy server for the management node
                 url: /task_mnode_configure_proxy_server.html
-              - title: Create and manage storage cluster assets
-                url: /task_mnode_manage_storage_cluster_assets.html
-          - title: Enable remote NetApp Support connections
-            url: /task_mnode_enable_remote_support_connections.html
+              - title: Verify management node OS and services versions
+                url: /task_mnode_api_find_mgmt_svcs_version.html
+              - title: Getting logs from management services
+                url: /task_mnode_logs.html
+          - title: Manage support connections
+            entries:
+              - title: Start a remote NetApp Support session
+                url: /task_mnode_enable_remote_support_connections.html
+              - title: Manage SSH functionality on the management node
+                url: /task_mnode_ssh_management.html
       - title: Power your NetApp HCI system off or on
         entries:
           - title: NetApp HCI power overview
@@ -273,6 +289,40 @@ entries:
        url: /task_hcc_expand_compute_and_storage.html
      - title: Remove Witness Nodes after expanding cluster
        url: /task_hci_removewn.html
+  - title: Use Rancher on NetApp HCI
+    entries:
+     - title: Rancher on NetApp HCI overview
+       url: /concept_rancher_product_overview.html
+     - title: Concepts
+       url: /concept_rancher_concepts.html
+     - title: Requirements for Rancher on NetApp HCI
+       url: /rancher_prereqs_overview.html
+     - title: Deploy Rancher on NetApp HCI
+       url: /task_rancher_deploy.html
+     - title: Post deployment tasks
+       entries:
+        - title: Post deployment tasks overview
+          url: /concept_rancher_post_deployment_overview.html
+        - title: Ensure Rancher Support parity
+          url: /task_rancher_ensure_rancher_support_parity.html
+        - title: Improve Rancher VM resiliency
+          url: /task_rancher_config_anti_affinity.html
+        - title: Configure monitoring
+          url: /task_rancher_enable_monitoring.html
+        - title: Install Trident
+          url: /task_rancher_trident.html
+        - title: Enable Trident support for user clusters
+          url: /task_trident_configure_networking.html
+     - title: Deploy user clusters and applications
+       url: /task_rancher_deploy_user_clusters.html
+     - title: Manage Rancher on NetApp HCI
+       url: /task_rancher_manage.html
+     - title: Monitor Rancher on NetApp HCI
+       url: /task_rancher_monitor.html
+     - title: Upgrade Rancher on NetApp HCI
+       url: /task_rancher_upgrades.html
+     - title: Remove a Rancher installation on NetApp HCI
+       url: /task_rancher_remove_deployment.html
   - title: Maintain H-series hardware
     entries:
      - title: H-series hardware maintenance overview

docs/concept_cg_hci_accounts.adoc

@@ -54,7 +54,7 @@ Authoritative user accounts can authenticate against any storage asset associate
 
 Authoritative user accounts are managed from the top right menu User Management option in NetApp Hybrid Cloud Control.
 
-The authoritative storage cluster is the storage cluster that NetApp Hybrid Cloud Control uses to authenticate users.
+The link:concept_hci_clusters.html#authoritative-storage-clusters[authoritative storage cluster] is the storage cluster that NetApp Hybrid Cloud Control uses to authenticate users.
 
 All users created on the authoritative storage cluster can log into the NetApp Hybrid Cloud Control. Users created on other storage clusters _cannot_ log into Hybrid Cloud Control.
 

docs/concept_hci_initiators.adoc

@@ -0,0 +1,23 @@
+---
+sidebar: docs_sidebar
+permalink: docs/concept_hci_initiators.html
+summary: Learn about initiators and how you can use them to permit access to storage in volume access groups.
+keywords: netapp, hci, initiator, storage volume, solidfire volume, element volume, access group
+---
+
+= Initiators
+:hardbreaks:
+:nofooter:
+:icons: font
+:linkattrs:
+:imagesdir: ../media/
+
+[.lead]
+Initiators enable external clients access to volumes in a cluster, serving as the entry point for communication between clients and volumes. You can use initiators for CHAP-based rather than account-based access to storage volumes. A single initiator, when added to a volume access group, allows volume access group members to access all storage volumes added to the group without requiring authentication. An initiator can belong to only one access group.
+
+== Find more information
+* link:task_hcc_manage_initiators.html[Manage initiators]
+* link:concept_hci_volume_access_groups.html[Volume access groups]
+* link:task_hcc_manage_vol_access_groups.html[Manage volume access groups]
+* https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
+* http://docs.netapp.com/sfe-122/index.jsp[SolidFire and Element Software Documentation Center^]

docs/concept_rancher_concepts.adoc

@@ -0,0 +1,48 @@
+---
+sidebar: docs_sidebar
+permalink: docs/concept_rancher_concepts.html
+summary: Learn about tasks you might need to perform after installing Rancher on NetApp HCI.
+keywords: netapp, hci, rancher, control plane, catalog, cluster, kubernetes
+---
+
+= Rancher on NetApp HCI concepts
+:hardbreaks:
+:nofooter:
+:icons: font
+:linkattrs:
+:imagesdir: ../media/
+
+[.lead]
+Learn basic concepts related to Rancher on NetApp HCI.
+
+* *Rancher server* or *Control plane*: The Rancher control plane, sometimes called the _Rancher Server_, provisions, manages, and monitors Kubernetes clusters used by Development and Operations teams.
+
+* *Catalogs*: Catalogs are GitHub repositories or Helm Chart repositories filled with applications that are ready-made for deployment. Rancher provides the ability to use a catalog of Helm charts that make it easy to deploy applications repeatedly. Rancher includes two types of catalogs: built-in global catalogs and custom catalogs. Trident is deployed as a catalog.  See https://rancher.com/docs/rancher/v2.x/en/helm-charts/legacy-catalogs/[Rancher documentation about catalogs].
+
+* *Management cluster*: Rancher on NetApp HCI deploys three virtual machines on the Rancher management cluster, which you can see using Rancher, Hybrid Cloud Control, and the vCenter Plug-in. The management cluster virtual machines host the Rancher server, the Rancher Kubernetes Engine (RKE), and the Linux OS.
+
+* *User clusters*: These downstream Kubernetes clusters run your apps and services. In Kubernetes installations of Rancher, the management cluster should be separate from the user clusters. Any cluster that a Rancher user deploys from Rancher, or imports into Rancher, would be considered a user cluster.
+
+* *Rancher node template*: Hybrid Cloud Control uses a Rancher node template to make deployment simpler.
+
++
+See  https://rancher.com/docs/rancher/v2.x/en/user-settings/node-templates/[Rancher documentation about node templates].
+
+== Trident software and persistent storage concepts
+Trident, itself a Kubernetes-native application, runs directly within a Kubernetes cluster. With Trident, Kubernetes users (such as developers, data scientists, and Kubernetes administrators) can create, manage, and interact with persistent storage volumes in the standard Kubernetes format that they are already familiar with. With Trident, NetApp solutions can meet persistent volume claims that are made by Kubernetes clusters.
+
+With Rancher, you can use a persistent volume, one that exists independently of any specific pod and with its own lifetime. Using Trident to manage persistent volume claims (PVCs) insulates the developers creating pods from the lower-level implementation details of the storage that they are accessing.
+
+When a containerized application issues a persistent volume claim (PVC) request, Trident dynamically provisions storage per the parameters requested against the NetApp Element software storage layer in NetApp HCI.
+
+A Trident catalog is available to Rancher on NetApp HCI and runs in the user clusters. As part of the Rancher on NetApp HCI implementation, a Trident installer is available in the Rancher catalog by default. Inclusion of this catalog simplifies the Trident deployment to user clusters.
+
+See link:task_rancher_trident.html[Install Trident with Rancher on NetApp HCI].
+
+For details, visit the https://netapp-trident.readthedocs.io/en/stable-v20.10/introduction.html[Trident documentation].
+
+[discrete]
+== Find more information
+* https://rancher.com/docs/rancher/v2.x/en/overview/architecture/[Rancher documentation about architecture^]
+* https://rancher.com/docs/rancher/v2.x/en/overview/concepts/[Kubernetes terminology for Rancher]
+* https://www.netapp.com/us/documentation/hci.aspx[NetApp HCI Resources page^]

docs/concept_rancher_post_deployment_overview.adoc

@@ -0,0 +1,30 @@
+---
+sidebar: docs_sidebar
+permalink: docs/concept_rancher_post_deployment_overview.html
+summary: Learn about tasks you might need to perform after installing Rancher on NetApp HCI.
+keywords: netapp, hci, Rancher, install, post installation, requirements, tasks
+---
+
+= Post deployment tasks overview
+:hardbreaks:
+:nofooter:
+:icons: font
+:linkattrs:
+:imagesdir: ../media/
+
+[.lead]
+After you deploy Rancher on NetApp HCI, you should continue with post-deployment activities.
+
+* link:task_rancher_ensure_rancher_support_parity.html[Ensure Rancher Support parity]
+* link:task_rancher_config_anti_affinity.html[Improve Rancher VM resiliency]
+* link:task_rancher_enable_monitoring.html[Configure monitoring]
+* link:task_rancher_trident.html[Install Trident]
+* link:task_trident_configure_networking.html[Enable Trident support for user clusters]
+
+
+[discrete]
+== Find more information
+* https://rancher.com/docs/rancher/v2.x/en/overview/architecture/[Rancher documentation about architecture^]
+* https://rancher.com/docs/rancher/v2.x/en/overview/concepts/[Kubernetes terminology for Rancher]
+* https://docs.netapp.com/us-en/vcp/index.html[NetApp Element Plug-in for vCenter Server^]
+* https://www.netapp.com/us/documentation/hci.aspx[NetApp HCI Resources page^]

docs/concept_rancher_product_overview.adoc

@@ -0,0 +1,65 @@
+---
+sidebar: docs_sidebar
+permalink: docs/concept_rancher_product_overview.html
+summary: Deploying Rancher on NetApp HCI deploys the Rancher Control plane, also referred to as the Rancher Server,  enables you to create on-premises Kubernetes clusters.
+keywords: netapp, hci, rancher, architecture, kubernetes, cluster
+---
+
+= Rancher on NetApp HCI overview
+:hardbreaks:
+:nofooter:
+:icons: font
+:linkattrs:
+:imagesdir: ../media/
+
+[.lead]
+Rancher is a complete software stack for teams adopting containers. Rancher addresses the operational and security challenges of managing multiple Kubernetes clusters across different infrastructures, while providing DevOps teams with integrated tools for running containerized workloads.
+
+Deploying Rancher on NetApp HCI deploys the Rancher control plane, also referred to as the _Rancher server_,  and enables you to create on-premises Kubernetes clusters. You deploy the Rancher control plane by using the NetApp Hybrid Cloud Control.
+
+After deployment, using the Rancher control Plane, you provision, manage, and monitor Kubernetes clusters used by Dev and Ops teams. Dev and Ops teams can use Rancher to perform activities on user clusters that reside on NetApp HCI itself, a public cloud provider, or any other infrastructure that Rancher enables.
+
+== Benefits of Rancher on NetApp HCI
+
+*	Ease of installation: You do not need to learn how to install and configure Rancher. You can deploy a template-based implementation, which was jointly developed by NetApp HCI and Rancher.
+*	Lifecycle management:  In a manual Rancher implementation, updates for the Rancher server application or the Rancher Kubernetes Engine (RKE) cluster are not automated. Rancher on NetApp HCI provides the ability for updates to the management cluster, that includes the Rancher server and the RKE.
+
+== What you can do with Rancher on NetApp HCI
+With Rancher on NetApp HCI, you can:
+
+* Deploy services across cloud providers and your private cloud.
+* Port the apps and data across a hybrid cloud architecture regardless of cloud location without compromising service-level agreements.
+* Spin up cloud-native applications yourself.
+* Centralize management of multiple clusters (new and existing).
+* Perform orchestration of hybrid cloud Kubernetes-based applications.
+
+== Technical Support option
+Using Rancher on NetApp HCI and Kubernetes open-source software includes free deployment and usage. License keys are not required.
+
+You can choose a NetApp Rancher Support option to obtain core-based, Rancher enterprise support.
+
+== Rancher on NetApp HCI architecture and components
+
+Here is an overview of the various components of Rancher on NetApp HCI:
+
+image::rancher_architecture_diagram1.png[Rancher on NetApp HCI architecture]
+
+* *NetApp Hybrid Cloud Control*: This interface enables you to deploy Rancher on NetApp HCI and NetApp Element software, required for Rancher on NetApp HCI.
++
+TIP: You can use NetApp Hybrid Cloud Control also to upgrade management services, expand your system, collect logs, and monitor your installation.
+
+* *Management services*: Management services run on the management node and enable you to deploy Rancher on NetApp HCI using NetApp Hybrid Cloud Control.
+
+* *Management cluster*: Rancher on NetApp HCI deploys three virtual machines on the Rancher management cluster, which you can see using NetApp Hybrid Cloud Control, vCenter Server, or the Rancher user interface. The management cluster virtual machines host the Rancher server, the Rancher Kubernetes Engine (RKE), and the Linux OS.
+
+TIP: For the best performance and greater security, consider using a dedicated Kubernetes cluster for the Rancher management server. You should not run your user workloads on the management cluster.
+
+* *User clusters*: The downstream Kubernetes user clusters run your apps and services. Any cluster that you deploy from Rancher or import into Rancher is a user cluster.
+
+* *Trident*: A Trident catalog is available to Rancher on NetApp HCI and runs in the user clusters. Inclusion of this catalog simplifies the Trident deployment to user clusters.
+
+
+[discrete]
+== Find more information
+* https://rancher.com/docs/rancher/v2.x/en/overview/architecture/[Rancher documentation about architecture^]
+* https://www.netapp.com/us/documentation/hci.aspx[NetApp HCI Resources page^]