How to bring Single Titan Node up using automation : Versa Support

This article shows how to bring Single Titan Node up using automation

Prerequisite

Create a VM with 16.04 Server (It should have 8 core CPU , 16 GB ram and 80 GB storage)
Server should have Internet Reachability

versa@ubuntu:~$ sudo cat /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

nameserver 10.48.0.99

nameserver 8.8.8.8

The Time of the Server and Host should be in sync

The Headend should be deployed (Follow : How to create Headend for Titan )

Step 1 >

Run the clone command to copy the file from git to server (Link : http://gitlab.versa-networks.com/contus/automationdeploy )

versa@ubuntu:~$ git clone http://gitlab.versa-networks.com/contus/automationdeploy.git

· Change the Name of the folder to automationdeploy-master from automationdeploy

versa@ubuntu:~/automationdeploy$ cd ../

versa@ubuntu:~$ mv automationdeploy automationdeploy-master

Step 2 >

Update the files locally to release-1.3R6GA using the below commands

versa@ubuntu:~/automationdeploy-master$ git branch

* master

versa@ubuntu:~/automationdeploy-master$ git fetch && git checkout release-1.3R6GA

Branch release-1.3R6GA set up to track remote branch release-1.3R6GA from origin.

Switched to a new branch 'release-1.3R6GA'

versa@ubuntu:~/automationdeploy-master$ git branch

master

* release-1.3R6GA

versa@ubuntu:~/automationdeploy-master$ git pull origin release-1.3R6GA

From http://gitlab.versa-networks.com/contus/automationdeploy

* branch release-1.3R6GA -> FETCH_HEAD

Step 3>

Update the configuration.yml file as per your setup

versa@ubuntu:~$ more /home/versa/automationdeploy-master/configuration.yml

docker_images:

chat: 'saasrepo.versa-networks.com:8443/versa-chat:1.3R6GA'

api: 'saasrepo.versa-networks.com:8443/versa_api:1.3R6GA'

shop: 'saasrepo.versa-networks.com:8443/versa_shop:1.3R6GA'

kafka: 'saasrepo.versa-networks.com:8443/kafka-docker:1.3R6GA'

mysql: 'saasrepo.versa-networks.com:8443/versa-galera-mysql:1.3R6GA'

mongodb: 'saasrepo.versa-networks.com:8443/mongo:1.3R6GA'

dashboard: 'saasrepo.versa-networks.com:8443/versa_dashboard:1.3R6GA'

zookeeper: 'saasrepo.versa-networks.com:8443/zookeeper:1.3R6GA'

saasconfig: 'saasrepo.versa-networks.com:8443/versa_geosaasconfig:1.3R6GA'

logstash: 'saasrepo.versa-networks.com:8443/versa_logstash_kafka:1.3GA'

nodesocket: 'saasrepo.versa-networks.com:8443/versa_nodesocket:1.3R6GA'

devicefacingapi: 'saasrepo.versa-networks.com:8443/versa_device_facing_api:1.3R6GA'

streamprocessor_filtering: 'saasrepo.versa-networks.com:8443/versa_streamprocessor:1.3R6GA'

streamprocessor_monitoring: 'saasrepo.versa-networks.com:8443/versa_streamprocessor:1.3R6GA'

streamprocessor_update_event: 'saasrepo.versa-networks.com:8443/versa_streamprocessor:1.3R6GA'

gluu_oxauth: 'saasrepo.versa-networks.com:8443/gluufederation-oxauth:1.3R6GA'

gluu_oxtrust: 'saasrepo.versa-networks.com:8443/gluufederation-oxtrust:1.3R6GA'

gluu_nginx: 'saasrepo.versa-networks.com:8443/versa-nginx-lua:1.3R6GA'

gluu_consul: 'saasrepo.versa-networks.com:8443/consul:1.3R6GA'

gluu_opendj: 'saasrepo.versa-networks.com:8443/gluufederation-opendj:1.3R6GA'

gluu_configinit: 'saasrepo.versa-networks.com:8443/gluufederation-config-init:1.3R6GA'

gluu_oxpassport: 'saasrepo.versa-networks.com:8443/gluufederation-oxpassport:1.3R6GA'

gluu_oxshibboleth: 'saasrepo.versa-networks.com:8443/gluufederation-oxshibboleth:1.3R6GA'

gluu_registrator: 'saasrepo.versa-networks.com:8443/registrator:1.3R6GA'

haproxy_analytics: 'saasrepo.versa-networks.com:8443/haproxy-versa-analytics:1.3R6GA'

endpoints:

app_endpoint: '10.192.234.30' #IP Address of the Server

oauth_endpoint: '10.192.234.30' # IP Address of the Server

user_inputs:

condition_flags:

deploy_with_cert: false

device_facing:

clone_org: 'VERSA' #Clone org name is VERSA

default_template: 'VERSA' #Default template name is VERSA

master_template: 'MASTERTENANT' #Master template name

vd_username: 'Administrator'

vd_password: 'Versa@1234'

analytics_cluster: 'titan-analytics'

analytics_ip: '10.192.234.23'

analytics_port: '1234'

speedtest_ip: '127.0.0.1'

director_ip: '10.192.234.21'

provider_org: 'VERSA'

provider_org_id: '1'

primary_controller_ip: '10.192.23.27'

primary_controller_name: 'controller-1'

secondary_controller_ip: '10.192.23.28'

secondary_controller_name: 'controller-2'

wan1_controller_network_name: 'MPLS'

wan2_controller_network_name: 'INTERNET'

logstash:

amqp_ip: '10.192.132.65'

amqp_port: '5672'

amqp_user: 'versa'

amqp_password: 'versa123'

amqp_exchange: 'systemExchange'

amqp_queue: 'versa-queue'

van_port: '10519'

versa@ubuntu:~$

STEP 4>

Create a folder, copy the docker Images (Images are available in 10.192.234.1 server )

scp -r versa@10.192.234.1:/home/versa/TITAN/Titan_Docker_Images/* .

Go to /home/versa/automationdeploy-master/scripts

chmod docker.sh

sudo ./docker.sh

Run the docker load script

chmod docker_load.sh

versa@ubuntu:~/docker_images$ sudo ./docker_load.sh

Run docker access setup for docker daemon and docker login

versa@ubuntu:~/automationdeploy-master/autodeploy$ sudo python3 saas_shop_setup.py --with-install-env --insecure-docker-reg

Step 5 > Follow how to create API region Document

Step 6>

Go to api.env (/home/versa/automationdeploy-master/stack/single_node/configs/api.env) and add the highlighted configuration

Run the below mentioned command to update that api.env file

versa@ubuntu:~/automationdeploy-master/autodeploy$ sudo python3 update.py versa_api=saasrepo.versa-networks.com:8443/versa_api:1.3R6GA

Now we will be able to access the Shop as well as the Dashboard

How to bring Single Titan Node up using automation

Modified on: Mon, 6 Apr, 2020 at 8:31 AM

More articles in Other Basic Configurations