Appendix: Step-wise Platform Deployment

After you have installed the Turbonomic VM that will host the platform, you can install the platform components, as follows:

Optionally, configure Single Sign-On Authentication (SSO) for this installation.

If you plan to use SSO to authenticate your Turbonomic users, you can configure it now. To configure SSO you will edit the charts_v1alpha1_xl_cr.yaml file. You can edit it now, before you complete the installation, or you can edit it later and restart the affected components. For more information, see Single Sign-On Authentication.
Deploy Turbonomic Kubernetes nodes.

When you deploy Turbonomic on Kubernetes, you deploy one Kubernetes node as a VM that will host pods to run the Turbonomic components. The script to deploy and initialize the Kubernetes node also deploys the Kubernetes pods that make up the Turbonomic application.

Start a secure session (SSH) on your Turbonomic VM as the turbo user and perform the following steps:
1. Initialize the Kubernetes node and deploy the pods.
  
  Execute the script: /opt/local/bin/t8c.sh
  
  Do not specify sudo when you execute this script.
  
  The script should take up to 20 minutes to complete.
  Note:
  You can specify the host name for the Turbonomic deployment.
  
  By default, the Turbonomic platform deploys to a host named node1. To specify a different host name, execute the script with the -h flag as follows:
```
/opt/local/bin/t8c.sh -h <MyHostName>
```
  Where <MyHostName>:
  - Consists of lower-case alphanumeric characters, '.', or '-'
  - Begins and ends with an alphanumeric character
  Also note that after you change the hostname, you must reboot the VM for the name change to take effect.
2. Verify that the deployment succeeded.
  
  At the end of the script output, in the summary section, verify that no errors are reported. If any errors are reported, contact Turbonomic Support.
3. Verify that the Turbonomic application installed correctly.
  
  To verify the installation of the application, execute the command:
  
  kubectl get pods -n turbonomic
  
  After all of the pods start up, the READY column should read 1/1 and the STATUS column should read Running for each pod.
  
  You should see output similar to the following:
```
NAME                                         READY   STATUS    RESTARTS 
action-orchestrator-b6454c9c8-mfl85          1/1     Running   0         
api-7887c66f4b-shndq                         1/1     Running   0         
arangodb-7f646fc5fc-zhcwf                    1/1     Running   0         
auth-5b86976bc8-vxwz4                        1/1     Running   0         
clustermgr-85548678d9-r5wb8                  1/1     Running   0         
consul-7f684d8cb8-6r677                      1/1     Running   0         
cost-5f46dd66c4-6d6cb                        1/1     Running   0          
extractor-5f41dd61c4-4d6lq                   1/1     Running   0        
group-5bfdfbc6f8-96bsp                       1/1     Running   0         
history-5fc7fbc855-6zslq                     1/1     Running   0         
kafka-74cc77db94-dfrbl                       1/1     Running   0         
market-5f54699447-z4wkm                      1/1     Running   0         
mediation-actionscript-57b4fc6df-4lzfv       1/1     Running   0         
mediation-appdynamics-6d65f8766f-kb44l       1/1     Running   0         
mediation-hpe3par-d7c475c4c-v8ftc            1/1     Running   0         
mediation-hyperv-6bd8c94df5-4dbzx            1/1     Running   0         
mediation-netapp-7f8fc955d9-4kkdl            1/1     Running   0         
mediation-oneview-7dbd7b54cf-7rfqp           1/1     Running   0         
mediation-pure-58c4bd8cd9-8n256              1/1     Running   0         
mediation-ucs-6f4bb9889-9rnqk                1/1     Running   0         
mediation-vcenter-5bc4f5fbd4-nzm4j           1/1     Running   0         
mediation-vcenterbrowsing-5c5987f66c-bfjq4   1/1     Running   0         
mediation-vmax-6c59969b89-28t9j              1/1     Running   0         
mediation-vmm-9c4878cf9-rfxnl                1/1     Running   0         
nginx-5b775f498-sm2mm                        1/1     Running   0         
plan-orchestrator-6dffc4c9b6-p5t5n           1/1     Running   0         
reporting-b44fbdfb4-8fjv5                    1/1     Running   0         
repository-6d555bb4bf-fxldh                  1/1     Running   0         
rsyslog-fd694878c-5tb2c                      1/1     Running   0         
t8c-operator-558bcc758d-5h8mp                1/1     Running   0         
topology-processor-b646b786b-9skp7           1/1     Running   0         
zookeeper-5f65b5bf69-nnmbt                   1/1     Running   0         
              
```
4. Synchronize the system clock.
  
  To ensure correct display of data, and to support Single Sign-On (SSO) authentication, you need to synchronize the system clock.
  
  For information, see Synchronizing Time and Single Sign-On Authentication.
5. Verify that the Load Balancer has installed correctly.
  
  To verify the presence of the Load Balancer, execute the command:
  
  kubectl get services -n turbonomic | grep LoadBalancer
  
  You should see output similar to the following:
```
nginx  LoadBalancer   10.10.10.10   10.10.10.11  443:32669/TCP,80:32716/TCP  17h
```
6. Configure mediation.
  
  The installation script automatically enables a default set of mediation probes. After installation completes, you can change the set of enabled mediation probes (see Enabling and Disabling Probe Components).
  
  For Turbonomic to manage your IT environment, it must attach to targets in your environment so it can perform discovery and execute actions. The combination of the processes of discovery and action execution is mediation. This release of Turbonomic supports mediation through the following targets. If you need to use additional targets that are not in this list, contact Turbonomic Support.
  - Applications and Databases
    - Apache Tomcat 7.x, 8.x, and 8.5.x
    - AppDynamics 4.1+
    - AppInsights
    - Dynatrace 1.1+
    - IBM WebSphere Application Server 8.5+
    - Instana, release-209 or later
    - JBoss Application Server 6.3+
    - JVM 6.0+
    - Microsoft SQL Server 2012, 2014, 2016, 2017, and 2019
    - MySQL 5.6.x and 5.7.x
    - NewRelic
    - Oracle 11g R2, 12c, 18c, and 19c
    - Oracle WebLogic 12c
  - Cloud Native
    - Kubernetes, including any compliant k8s distribution (Rancher, Tanzu, open source, etc.)
    - Cloud-hosted k8s services (AKS, EKS, GKE, IBM, Cisco IKS, ROKS, ROSA, etc.)
    - OpenShift 3.11 and higher (OCP 4.x)
  - Fabric and Network
    - Cisco UCS Manager 3.1+
    - HPE OneView 3.00.04
  - Guest OS Processes
    - SNMP
    - WMI: Windows versions 8 / 8.1, 10, 2008 R2, 2012 / 2012 R2, 2016, 2019 and 7
  - Hyperconverged
    - Cisco HyperFlex 3.5
    - Nutanix Community Edition
    - VMware vSAN
  - Hypervisors
    - Microsoft Hyper-V 2008 R2, Hyper-V 2012/2012 R2, Hyper-V 2016, Hyper-V 2019
    - VMware vCenter 6.0, 6.5, 6.7, and 7.0+
  - Orchestrator
    - Action Script
    - Flexera One
    - ServiceNow
  - Private Cloud
    - Microsoft System Center 2012/2012 R2 Virtual Machine Manager and System Center 2016 Virtual Machine Manager
  - Public Cloud
    - Amazon AWS
    - Amazon AWS Billing
    - Google Cloud Platform (GCP)
    - Google Cloud Platform (GCP) Billing
    - Microsoft Azure Service Principal
    - Microsoft Enterprise Agreement
  - Storage
    - EMC ScaleIO 2.x and 3.x
    - EMC VMAX using SMI-S 8.1+
    - EMC VPLEX Local Architecture with 1:1 mapping of virtual volumes and LUNs
    - EMC XtremIO XMS 4.0+
    - HPE 3PAR InForm OS 3.2.2+, 3PAR SMI-S, 3PAR WSAPI
    - IBM FlashSystem running on Spectrum Virtualize 8.3.1.2 or later (8.4.2.0 or later recommended)
    - NetApp Cluster Mode using ONTAP 8.0+ (excluding AFF and SolidFire)
    - Pure Storage F-series and M-series arrays
  - Virtual Desktop Infrastructure
    - VMware Horizon
  For information about these targets, see the Turbonomic Target Configuration Guide.
Log in to the Turbonomic user interface and set the administrator user account password.

Important:
You should wait until all the platform components have started up, are running, and are fully ready before your first login. If you try to add a license or add a target to the platform before the components are all ready, the platform can fail to initialize correctly. For more information, see Verify that the Turbonomic application installed correctly.

After the components start up, in your Web browser, type the static IP address of your Turbonomic VM. Your browser redirects the login page for Turbonomic users.

Turbonomic includes a default user account named administrator which has an ADMINISTRATOR role. As you log in for the first time, you must set your own password for that account. You can create or delete other accounts with the ADMINISTRATOR role, but your installation of Turbonomic must always have at least one account with that role.

In the login page, enter the information as required, and make a note of it.
- Use the default credential for USERNAME: administrator.
- Type a password for PASSWORD.
  
  The new password must comply with the strong password policy (a mixture of upper- and lower-case letters, numbers, and a symbol). Only you will know this new password.
- Type the password again to verify it for REPEAT PASSWORD.
- Click CONFIGURE.
This is the account you will use to access the Turbonomic user interface with administrator permissions. Be sure to save the user interface administrator account credentials in a safe place.

Note:
The initial login is always for the administrator account. This is an administration user account. Do not confuse this with the Turbonomic System Administrator account that you previously set up to log into shell sessions on the VM itself.
After you have logged in as administrator, you can create other user accounts, and you can give them various roles. For more information about user accounts and roles, see the Turbonomic User Guide.