1. Execute the following commands after uploading the csv files to Cluster Manager VM:

   /var/qps/install/current/scripts/import/import_deploy.sh

2. Execute the following command to validate the imported data:

   cd /var/qps/install/current/scripts/deployer/support/
   python jvalidate.py

   The above script validates the parameters in the Excel/csv file against the ESX servers to make sure ESX server can support the configuration and deploy VMs.

cd /mnt/iso
./install.sh
Please enter install type [mobile|wifi|mog|arbiter]: arbiter ----> Select arbiter for this option
Would you like to initialize the environment... [y|n]: y     ----> Enter y to continue

1) New Deployment
2) Upgrade from existing 9.0 system
3) In-Service Upgrade from 7.0.5 onwards (eg: 7.0.5 to 9.x)

Select 1 for new Arbiter deployment. For further steps, refer to Example: New Deployment of Arbiter.

firewall_disabled=0
internal_address=XX.XX.XX.XX             ---> update XX.XX.XX.XX to your internal IP address 
internal_device=0                        ---> update 0 to your device ID
internal_guest_nic=eth0                  ---> update eth0 to other port if it is not using default NIC for internal address
 

echo "XX.XX.XX.XX hostname1" >> /etc/hosts --> edit this line
echo "XX.XX.XX.XX hostname2" >> /etc/hosts --> edit this line
echo "XX.XX.XX.XX hostname3" >> /etc/hosts --> edit this line

For example:

/etc/broadhop/mongoConfig.cfg:
[SESSION-SET1]
SETNAME=set01
OPLOG_SIZE=5120
ARBITER=arbiter-site3:27717
ARBITER_DATA_PATH=/var/data/sessions.1/set01
PRIMARY-MEMBERS
MEMBER1=sessionmgr01-site1:27717
MEMBER2=sessionmgr02-site1:27717
SECONDARY-MEMBERS
MEMBER1=sessionmgr01-site2:27717
MEMBER2=sessionmgr02-site2:27717
DATA_PATH=/var/data/sessions.1/set01
[SESSION-SET1-END]

For above mongoConfig.cfg file, below host entries are needed in /etc/hosts file:

echo "192.168.1.1 arbiter-site3" >> /etc/hosts
echo "192.168.1.2 sessionmgr01-site1" >> /etc/hosts
echo "192.168.1.3 sessionmgr02-site1" >> /etc/hosts
echo "192.168.1.4 sessionmgr01-site2" >> /etc/hosts
echo "192.168.1.5 sessionmgr02-site2" >> /etc/hosts

cd /root

umount /mnt/iso

rm xxxx.iso

where, xxxx.iso is the name of the ISO image used.

1. Run hostname xxx, where xxx is the new host name for the Arbiter.
2. Edit /etc/sysconfig/network to add the new host name for the Arbiter.

nova flavor-create --ephemeral 0 arbiter auto 4096 0 2

Create arbiter-cloud.cfg file with the following content:

#cloud-config
write_files:
 - path: /etc/sysconfig/network-scripts/ifcfg-eth0
   encoding: ascii
   content: |
     DEVICE=eth0
     BOOTPROTO=none
     NM_CONTROLLED=none
     IPADDR=172.20.38.251           ---> update with your internal address 
     NETMASK=255.255.255.0          ---> update with your netmask
     GATEWAY=172.20.38.1            ---> update with your gateway
     NETWORK=172.20.38.0            ---> update with your network
   owner: root:root
   permissions: '0644'
 - path: /var/lib/cloud/instance/payload/launch-params
   encoding: ascii
   owner: root:root
   permissions: '0644'
 - path: /root/.autoinstall.sh
   encoding: ascii
   content: |
     #!/bin/bash
     if [[ -d /mnt/iso ]] && [[ -f /mnt/iso/install.sh ]]; then
       /mnt/iso/install.sh << EOF
     arbiter
     y
     1
     EOF
     fi
     /root/.enable_firewall.sh
     /root/.add_db_hosts.sh
     if [[ -x "/var/qps/install/current/scripts/upgrade/reinit.sh" ]]; then
         /var/qps/install/current/scripts/upgrade/reinit.sh
     fi
   permissions: '0755'
 - path: /root/.enable_firewall.sh
   encoding: ascii
   content: |
     #!/bin/bash
     mkdir -p /etc/facter/facts.d/
     cat <<EOF >/etc/facter/facts.d/qps_firewall.txt
     firewall_disabled=0            ---> change it to 1 if you do not want firewall enabled on this setup and remove below fields
     internal_address=172.20.38.251 ---> update with your internal address
     internal_device=0
     EOF
   permissions: '0755'
 - path: /root/.add_db_hosts.sh  ---> update db hosts IP as per requirement
   encoding: ascii
   content: |
     #!/bin/bash
     #Example if /etc/broadhop/mongoConfig.cfg:
     #[SESSION-SET1]
     #SETNAME=set01
     #OPLOG_SIZE=5120
     #ARBITER=arbiter-site3:27717
     #ARBITER_DATA_PATH=/var/data/sessions.1/set01
     #PRIMARY-MEMBERS
     #MEMBER1=sessionmgr01-site1:27717
     #MEMBER2=sessionmgr02-site1:27717
     #SECONDARY-MEMBERS
     #MEMBER1=sessionmgr01-site2:27717
     #MEMBER2=sessionmgr02-site2:27717
     #DATA_PATH=/var/data/sessions.1/set01
     #[SESSION-SET1-END]
     #For above mongoConfig.cfg below hosts entries are needed in /etc/hosts, edit below list as per your requirement
     cat <<EOF >> /etc/hosts
     192.168.1.1 arbiter-site3
     192.168.1.2 sessionmgr01-site1
     192.168.1.3 sessionmgr02-site1
     192.168.1.4 sessionmgr01-site2
     192.168.1.5 sessionmgr02-site2
     EOF
   permissions: '0755'
mounts:
 - [ /dev/vdb, /mnt/iso, iso9660, "auto,ro", 0, 0 ]
runcmd:
 - ifdown eth0
 - echo 172.20.38.251 installer arbiter >> /etc/hosts ---> update this IP
 - ifup eth0
 - /root/.autoinstall.sh

Before executing nova boot command, confirm that the cloud configuration file (arbiter-cloud.cfg) exists in the right directory.

Execute the following command to create arbiter VM with two NICs:

source ~/keystonerc_core
nova boot --config-drive true --user-data=arbiter-cloud.cfg  --file /root/keystonerc_user=/root/keystonerc_core 
--image "base_vm" --flavor "arbiter" 
--nic net-id="9c89df81-90bf-45bc-a663-e8f80a8c4543,v4-fixed-ip=172.16.2.19" 
--nic net-id="dd65a7ee-24c8-47ff-8860-13e66c0c966e,v4-fixed-ip=172.18.11.101"
--block-device-mapping "/dev/vdb=eee05c17-af22-4a33-a6d9-cfa994fecbb3:::0"
--availability-zone "az-2:os24-compute-2.cisco.com" arbiter

For example,

nova boot --config-drive true --user-data=arbiter-cloud.cfg  
--file /root/keystonerc_user=/root/keystonerc_core 
--image "base_vm" --flavor "arbiter" --nic net-id="<Internal n/w id>,v4-fixed-ip=<Interanl n/w private ip>" 
--nic net-id="<Management n/w id>,v4-fixed-ip=<Management n/w public ip>"
--block-device-mapping "/dev/vdb=<Volume id of iso>:::0" 
--availability-zone "<availability zone:Host info>" arbiter

The following examples can be used to get the internal and management IP addresses and volume IDs which are used to spin arbiter VM.

source ~/keystonerc_core

neutron net-list

nova volume-list

telnet qns01 9091
addshard sessionmgr03,sessionmgr04 27717 1 backup
addshard sessionmgr03,sessionmgr04 27717 2 backup
addshard sessionmgr03,sessionmgr04 27717 3 backup
addshard sessionmgr03,sessionmgr04 27717 4 backup
rebalance
migrate
disconnect
y

1. Login to primary administration database using port#<admin DB port> and verify the collection shards in shading database.

   mongo sessionmgr01:27721
   MongoDB shell version: 2.6.3
   connecting to: sessionmgr01:27721/test
   set05:PRIMARY> use sharding
   switched to db sharding
   set05:PRIMARY> db.shards.find()
   { "_id" : 1, "seed_1" : "sessionmgr03", "seed_2" : "sessionmgr04", "port" : 27717, "db" : "session_cache_2", "online" : 
   true, 
   "count" : NumberLong(0), "backup_db" : true } 
   { "_id" : 2, "seed_1" : "sessionmgr03", "seed_2" : "sessionmgr04", "port" : 27717, "db" : "session_cache_3", "online" : 
   true, 
   "count" : NumberLong(0), "backup_db" : true }
   { "_id" : 3, "seed_1" : "sessionmgr04", "seed_2" : "sessionmgr04", "port" : 27717, "db" : "session_cache_4", "online" : 
   true, 
   "count" : NumberLong(0), "backup_db" : true }
   { "_id" : 4, "seed_1" : "sessionmgr03", "seed_2" : "sessionmgr04", "port" : 27717, "db" : "session_cache", "online" : 
   true, 
   "count" : NumberLong(0), "backup_db" : true }
   set05:PRIMARY

For more information on how to add the parameter in Configuration.csv file, refer to CPS Installation Guide for 9.0.0 and prior releases or CPS Installation Guide for VMware for 9.1.0 and later releases.

cd /var/qps/install/current/scripts/deployer/support/

python jvalidate.py

For more information on configuring GR features, refer to CPS Mobile Configuration Guide.

For more information on how to add the parameter in Configuration.csv file, refer to CPS Installation Guide for 9.0.0 or prior releases and CPS Installation Guide for VMware for 9.1.0 and later releases.

Add the following content in the configuration file (mon_db_for_callmodel.conf):

#this file contains set names that are available in mongoConfig.cfg. Add set names one below other.
#Refer to README in the scripts folder.
SESSION-SET1
SESSION-SET2
BALANCE-SET1
SPR-SET1

When we recover GR site, we have to manually start UAPI interface (if it is disabled) by executing the following command as a root user on lb01 and lb02:

echo "enable frontend https-api" | socat stdio /tmp/haproxy

cd /var/qps/install/current/scripts/deployer/support/

python jvalidate.py