Using probe and import to Generate the Installer Database
Describes how to enable a manually installed cluster to use the Installer or Installer Stanza commands.
If a cluster has Data Fabric software installed but has no
      Installer database, you cannot install or upgrade the cluster using Installer Stanza commands.
      And you cannot use the web-based Installer on the cluster. However, you can generate an
      Installer database on a cluster by using the probe and
        import commands. Once the Installer database is generated, you can use the
      web-based Installer and all Installer Stanza commands on the cluster.
If you are not sure if your cluster has an Installer database, use the
        export command to generate a YAML file that describes the cluster
      configuration. See Exporting a Cluster Configuration.
Using probe
Before using the probe command, you must know the host names or IP
        addresses of the cluster nodes and the root user, which must be the same on
        all nodes. The probe command generates a template that will be used by the
          import command.
probe-generated template file. After the
        Installer database is created, you can use the export command to export a
        YAML for making changes.In this example, the probing user, mapr1, probes an array of hosts
          (config.hosts) and generates a template file
          /tmp/location.yaml. The -u option provides login
        credentials for the Installer. Note that the probing user
        must be able to do rpm and pkg queries and have permission to read certain files and
        directories within /opt/mapr.
mapr-installer-cli probe -n -o config.ssh_id=mapr1 config.ssh_password=xyz config.hosts='["hostname[1-3]","hostname7"]' -u mapr1:xyz@<installer_hostname>:9443 > /tmp/location.yaml
      The probe command uses various methods to determine the EEP version of a node. One method checks the EEP repo URL defined on the node. If multiple EEP repos are defined on the same node, the
          probe command ignores all of them and tries to determine the EEP version based on thepackages that are present.
Using import
The import command prepares the Installer database based on the probed
        template file. This example imports the probed YAML template file from the previous example.
          -t specifies the location of the template file:
mapr-installer-cli import -n -t /tmp/location.yaml
      After you use the import command, the Installer database should be
        operational. You can then use the web-based Installer or Stanzas to perform additional
        operations on the cluster. See Installer.