(Optional) Enabling and disabling probe components
In Turbonomic, a probe is a platform component that connects to a target. A probe discovers the target's entities, loads the entities into the Turbonomic supply chain, and runs actions in the target environment. Turbonomic includes many probe components that you can use to connect Turbonomic with your environment.
Depending on your installation method, Turbonomic may enable probes by default. Each probe uses resources in your Turbonomic installation. If probes are not needed, consider disabling them. If there are disabled probes that you need, enable them to put them into service.
This topic explains how to enable probe components in an on-prem OVA deployment. To enable probes in a deployment other than OVA, refer to the applicable deployment topic for the steps to enable targets.
- Red Hat OpenShift OperatorHub users should refer to the information here.
- SaaS users should refer to the "Enabling and Adding Targets" section of the applicable deployment topic.
Viewing the current list of available probes
As Turbonomic evolves, the set of delivered probes change. Also, from one version to the next, the set of probes that are enabled by default can change. When you update to a new version, the update does not change your probe configuration. An update to a newer version does not automatically enable any new probes in your deployment. If you want to take advantage of new probes in an update, then you must enable them manually.
To enable any new probes, you must first know the internal name for the probe. To get
a list of probes that are available to your current version, you can view the contents of the
values.yaml
file.
-
Open an SSH terminal session to your Turbonomic instance.
Log in with the System Administrator that you set up when you installed Turbonomic:
-
Username:
turbo
-
Password:
[your_private_password]
-
Display the list of available probes.
cat /opt/turbonomic/kubernetes/operator/helm-charts/xl/values.yaml
The output is similar to the following example:
customdata: enabled: false dynatrace: enabled: false gcp: enabled: false hpe3par: enabled: false ...
This list gives the internal names of the probes. If you want to add a new probe to your list of configured probes, you must use the internal name, and set
enabled: true
.
Viewing the current list of configured probes
Your current installation of Turbonomic has a set of available
probes. Some of these will be enabled, and it is likely that some probes are disabled. To view the
current configuration of probes that are available, open the cr.yaml
file for your
Turbonomic installation and review the probe entries:
In the same SSH session, open the
cr.yaml
file for editing.vi /opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml
Search for the list of probes that are configured for your current installation.
The output is similar to the following example:
actionscript: enabled: true appdynamics: enabled: true aws: enabled: true azure: enabled: true dynatrace: enabled: true hpe3par: enabled: true horizon: enabled: false hyperflex: enabled: false ...
This list identifies all the probes that are configured for your installation, and shows whether they are enabled (
true
) or disabled (false
).Note:This list of probes is not identical to the list of probe pods that are running in your installation. Some probes use multiple pods. Probe pod names use the following convention, where
<ProbeName>
is the probe internal name (mentioned in the preceding lists), and<NameExtension>
is an optional extension to that name in case there are multiple pods for this probe:mediation-<ProbeName><NameExtension>
For example, if you run
kubectl get pods -n turbonomic
, the results can show the following for thevcenter
probe:NAME READY STATUS RESTARTS mediation-vcenter-5bc4f5fbd4-nzm4j 1/1 Running 0 mediation-vcenterbrowsing-5c5987f66c-bfjq4 1/1 Running 0
Enabling or disabling probes
To enable or disable probes, edit the cr.yaml
file. You can add
new probes, change the values of the enabled:
properties, and apply
changes to reload the platform components.
-
Log in to an SSH terminal session for your Turbonomic instance and display the list of available probes.
In the SSH session, open the
cr.yaml
file for editing.vi /opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml
Edit the probe entries.
To enable or disable currently configured probes, find the probes to edit and change the settings to
true
(enable) orfalse
(disable).To add new probes to the list, copy the probe entry you want from the output when you used
cat
to view the available probes. Then paste that entry into thecr.yaml
file and setenabled: true
.Save your changes to the platform.
Note:During the online or offline upgrade process, you should not use
kubectl
to apply these changes now.After you save your changes, apply the changes:
kubectl apply -f /opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml
Verify that the probes have installed correctly and all the Turbonomic pods have started.
kubectl get pods -n turbonomic
Review the list for the mediation pods that implement your probes. All pods should display READY and STATUS states similar to:
NAME READY STATUS RESTARTS [...] 1/1 Running 0
View the new probe configuration in the user interface.
Refresh your browser and go to the Target Management page. You will now see the target categories and types to match your configuration changes.