Local (Single Node)

After the Plixer ML Engine completes its first boot sequence, login with the user plixer and password plixer. Accept the EULA, and then configure the network settings.

Once the initial configuration is complete, the appliance will restart, and then you can proceed with deploying a standalone (single node) host. To do this, make sure that the following prerequisites are met first:

Setting up Plixer Kubernetes locally

  1. Navigate to the /home/plixer/common/kubernetes directory.

  2. Run ./01_local_infrastructure.sh.

  3. Run kubectl get nodes to make sure that the Kubernetes infrastructure has been deployed successfully. It should return like the following:

    ../../_images/kubectl-get-nodes-sample-output.jpg

Make sure that all of the nodes have a running or ready status. If not, wait for a few minutes, and then check again.

Setting up the ML engine locally

After the Kubernetes infrastructure has been deployed and is now running successfully, you may proceed with deploying the ML engine locally.

  1. Navigate to /home/plixer/ml.

  2. Run setup.sh.

    • For offline (no internet access) installation, run: /home/plixer/ml/setup.sh --offline

    • For online installation, run: /home/plixer/ml/setup.sh.

  3. Select if your Plixer Scrutinizer instance needs a private key for SSH.

    • If Yes, enter the path to your Plixer Scrutinizer private SSH key or SSH password.

    • If No, proceed to the next step.

  4. Select whether your Plixer Scrutinizer is a distributed cluster or not.

    • If Yes, enter the IP address of your Plixer Scrutinizer reporter.

    • If No, enter the IP address of your Plixer Scrutinizer host.

  5. Enter your Plixer Scrutinizer authentication token.

  6. Run kubectl get pods. The pods will have the Running status which means that it has been deployed successfully.