SevOne Data Insight Installation Guide

The following are the default IP ranges used by SevOne Data Insight.

If there is an IP range conflict with your environment, please refer to SevOne Data Insight Administration Guide > Deployment > Handle IP Conflicts to override the defaults.

A working DNS configuration is a requirement for any SevOne Data Insight deployment. Otherwise, SevOne Data Insight will not work.

Please refer to SevOne Data Insight Troubleshooting / Debug / Tools Guide > Troubleshooting > General Issues > section Domain Name Resolution (DNS) not working for details.

If you are deploying SevOne Data Insight from a .iso image, you must execute the following steps.

# copy over the default ansible config
$ sudo cp -r /opt/SevOne/upgrade/ansible/playbooks/inventory/* /etc/ansible/

# install base packages
$ sevone-cli playbook up --tags os --extra-vars "freight_install_skip_broken=yes"

# provision kubernetes
$ sevone-cli playbook up --extra-vars "freight_install_skip_broken=yes"

As a security measure, fresh installations do not ship with pre-generated SSH keys. Execute the following command to generate unique SSH keys for your cluster.

$ sevone-cli cluster setup-keys

SOA is a required dependency of SevOne Data Insight and must be installed on your SevOne NMS.

$ sevone-cli soa upgrade \
/opt/SevOne/upgrade/utilities/SevOne-soa-*.rpm \
<enter SevOne NMS IP address>

You will be prompted for the following information when running the bootstrap command.

1. Execute the bootstrap command.

   $ sevone-cli sdi connect-nms

   
   

   Example: Run bootstrap command

   Note: In this example, I have provided the following information at the prompts.
   

   • Name: SevOne
   • URL: https://10.129.14.168
   • Login instead of providing an API key? [ y/n ]: y
   • Username: admin
   • Password: SevOne
   • Name: SevOne (this is the tenant name)
   • Tenant Alternate/Display Name: hit <RETURN key>
   • Username: admin
   • Would you like to Add an object metadata filter? [y/N] N
   
   

   
   $ sevone-cli sdi connect-nms
   
   Defaulted container "graphql" out of: graphql, fix-shared-storage-permission (init)
   
   > @sevone/insight-server@6.8.0 prod:bootstrap
   > NODE_PATH=./dist/libs node dist/scripts/database-init/bootstrap.js
   
   info: Authsource Configuration
       Enter the name of your authentication source. Note that it may be the same
       as your datasource. Ex: , SevoneNMS8, Auth Serv, Datasource 123
   Name: SevOne
   info: Enter the NMS base URL to your authentication source.
       Ex: https://api.example.com
   URL: https://10.129.14.168
   Login instead of providing an API key? [y/n]: y
   Username: admin
   Password: ******
   info: [SevOne@reconfigure-datasource] SOA request (SOA-1) post https://10.129.14.168/api/v3/users/signin
   (node:248) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
   (Use `node --trace-warnings ...` to show where the warning was created)
   info: [SevOne@reconfigure-datasource] SOA response (SOA-1) elapsed 1994ms.
   info: [SevOne@reconfigure-datasource] SOA request (SOA-2) post https://10.129.14.168/api/v3/users/apikey
   info: [SevOne@reconfigure-datasource] SOA response (SOA-2) elapsed 72ms.
   info: Tenant Configuration
       Enter the name of your tenant. This is independent to Data Insight.
       Ex: WestCoast BestCoast, EastCoast BeastCoast
   Name: SevOne
   (OPTIONAL. Hit enter to skip) Enter the alternate/display name of your tenant.
   Tenant Alternate/Display Name: 
   info: Super Admin User Configuration
       Enter the username of your Retina Super Admin user. Note that this user
       MUST match a user with appropriate permissions on your authsource. Even
       if it's not a Super User on your authsource, it WILL be on Retina.
       Ex: JJJSchmidt, jsmith
   Username: admin
   info: [SevOne@reconfigure-datasource] SOA request (SOA-3) get https://10.129.14.168/api/v3/health/ping
   info: [SevOne@reconfigure-datasource] SOA response (SOA-3) elapsed 7ms.
   info: Bootstrap complete.
   Defaulted container "graphql" out of: graphql, fix-shared-storage-permission (init)
   
   > @sevone/insight-server@6.8.0 prod:provision
   > NODE_PATH=./dist/libs node dist/scripts/database-init/provision.js
   
   
   No existing object metadata filters.
   
   Would you like to Add an object metadata filter? [y/N] N
   (node:275) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
   (Use `node --trace-warnings ...` to show where the warning was created)
   info: [SevOne@SevOne] SOA request (SOA-1) post https://datasource-di-1.default.svc.cluster.local.:443/api/v3/users
   info: [SevOne@SevOne] SOA response (SOA-1) elapsed 54ms.
   info: Provisioning complete.
   

   Important: The command above can be retried to change your values in the event of typos or incorrect credentials.
   Note: If you need to connect to a different NMS, please refer to section Configuration > Tenants and Datasources > Configuration > Manage Datasources via CLI or User Interface > Modify a Datasource in SevOne Data Insight Administration Guide
2. SevOne Data Insight is now provisioned. From a web browser of your choice, enter <SevOne Data Insight IP address or hostname> in the URL to access the graphical user interface.

If you are deploying SevOne Data Insight from a .iso image, you must execute the following steps.

# copy over the default ansible config
$ sudo cp -r /opt/SevOne/upgrade/ansible/playbooks/inventory/* /etc/ansible/

# install base packages
$ sevone-cli playbook up --tags os --extra-vars "freight_install_skip_broken=yes"

Every SevOne Data Insight node ships as a running single-node Kubernetes cluster. In order to create a multi-node cluster, you must designate one of the nodes to be your control plane node.

Example

Execute the following steps.

1. Using ssh, log into the designated SevOne Data Insight control plane node as sevone.

   $ ssh sevone@<SevOne Data Insight 'control plane' node IP address or hostname>

   
   

   Example

   $ ssh sevone@10.123.45.67

2. Register and configure your agent nodes.
   Important: You will be prompted for your SSH password.

   
   $ sevone-cli cluster worker add <'agent1' IP address> --hostname <'agent1' host name>
   
   $ sevone-cli cluster worker add <'agent2' IP address> --hostname <'agent2' host name>
   

   
   

   Example

   
   $ sevone-cli cluster worker add 10.123.45.68 --hostname sdi-node02
   
   $ sevone-cli cluster worker add 10.123.45.69 --hostname sdi-node03
   

3. Teardown the Kubernetes cluster.

   
   $ sevone-cli cluster down
   

4. Spin up the cluster.

   
   $ sevone-cli cluster up
   

   Important: This command will automatically take the IP addresses of the agent nodes from /etc/ansible/hosts file.
5. Verify that your agent node(s) have been added to the Kubernetes cluster.

   
   $ /usr/local/bin/kubectl get nodes
   NAME                             STATUS   ROLES                  AGE     VERSION
   <your 'control plane' hostname>  Ready    control-plane,master   52d     v1.28.2+k3s1
   <your 'agent1' hostname>         Ready    <none>                 2m25s   v1.28.2+k3s1
   <your 'agent2' hostname>         Ready    <none>                 2m45s   v1.28.2+k3s1
   ...
   <your 'agent<n>' hostname>       Ready    <none>                 3m05s   v1.28.2+k3s1
   

   
   

   Example

   
   $ /usr/local/bin/kubectl get nodes
   NAME         STATUS   ROLES                  AGE     VERSION
   sdi-node01   Ready    control-plane,master   52d     v1.28.2+k3s1
   sdi-node02   Ready    <none>                 2m25s   v1.28.2+k3s1
   sdi-node03   Ready    <none>                 2m45s   v1.28.2+k3s1
   

SOA is a required dependency of SevOne Data Insight and must be installed on your SevOne NMS.

$ sevone-cli soa upgrade \
/opt/SevOne/upgrade/utilities/SevOne-soa-*.rpm \
<enter SevOne NMS IP address> --all-peers

Connect SevOne Data Insight to your SevOne NMS. For details, please refer to section Connect NMS for single node.