Installing VMR in Standalone Mode - Cisco...Installing VMR in Standalone Mode ThischapterprovidesinstructionsforinstallingandupgradingVMRinstandalonemode.Itincludesthe followingtopics:

Installing VMR in Standalone Mode

This chapter provides instructions for installing and upgrading VMR in standalone mode. It includes thefollowing topics:

• Introduction, page 1

• Pre-installation Procedure, page 2

• Install VMR in Standalone Mode, page 7

• Upgrade Standalone VMR, page 12

IntroductionVMR, as an application, can be configured and deployed in a standalone mode using a script. This script canbe run in the following modes, depending on the task you want to perform:

• Config—Running the script in configmode is the first step in the VMR standalone installation process.Currently, the config mode can be executed as a one-time installation step.

• Start—Running the script in start mode is the second step in the VMR standalone installation process.This will bring up the VMR services and pods, create OpenShift routes for dash-origin andrecorder-manager, and check if all pods are running.

• Stop—Running the script in stop mode completely stops the application; you use this mode to performany reconfigurations.

• Upgrade—Running the script in upgrademode upgrades the VMR services and pods, checks if all podsare running and provides periodic deployment status. See Upgrade Standalone VMR.

If you need to reconfigure the application, perform the following steps in this exact order:

1 Run the script in stop mode to remove VMR services, pods and endpoints.

2 Run the script in config mode to reconfigure the VMR application.

3 Run the script in start mode to bring back the services, pods and endpoints.

The procedures in this section provide sample outputs. The output in your environment will vary but shouldbe similar to the examples provided.

Cisco Virtual Media Recorder 1.3.3 Deployment Guide 1

Pre-installation ProcedureThis deployment assumes that an unmanaged Kubernetes cluster setup using OpenShift is already available.The following steps should be performed as part of the pre-install for VMR on the Kubernetes master.

Procedure

Step 1 Log in to Kubernetes (k8s) master.

OpenShift Deployer/Launcher is used in the followingexamples.

Note

Step 2 Log in to the load-balancer or OpenShift master nodes using the following command:oc login -u system -p admin --insecure-skip-tls-verify=true -n default :8443

Example

[root@ivpcoe-deployer ~]# oc login -u system -p admin --insecure-skip-tls-verify=true -ndefault 172.22.7.85:8443

Result:

Login successful.You have access to the following projects and can switch between them with 'oc project':* defaultkube-systemloggingmanagement-infraopenshiftopenshift-infravmrUsing project "default".

Step 3 The project is “default” and needs to be changed to vmr. You must first make sure the vmr namespace exists,and if not, create it.a) Run the following command to verify the vmr namespace exists:

[root@ivpcoe-deployer ~]# kubectl get namespaces

Result:

NAME STATUS AGEdefault Active 6dkube-system Active 6dlogging Active 6dmanagement-infra Active 6dopenshift Active 6dopenshift-infra Active 6d

b) If the vmr namespace does not exist (the above example shows that it does not exist), run the followingcommand to create it, and then verify that it was created:[root@ivpcoe-deployer ~]# kubectl create namespace vmrnamespace "vmr" created

[root@ivpcoe-deployer ~]# kubectl get namespaces

Cisco Virtual Media Recorder 1.3.3 Deployment Guide2

Installing VMR in Standalone ModePre-installation Procedure

Result:

NAME STATUS AGEdefault Active 6dkube-system Active 6dlogging Active 6dmanagement-infra Active 6dopenshift Active 6dopenshift-infra Active 6dvmr Active 6s

c) Change the project to vmr using the following command:oc project

Example:

[root@ivpcoe-deployer ~]# oc project vmr

Result:

Now using project "vmr" on server "https://172.22.7.85:8443".

Step 4 Verify that the nodes for vmr exist using the following command:[root@ivpcoe-deployer ~]# kubectl get nodes

Result:

NAME STATUS AGEivpcoe-master1 Ready,SchedulingDisabled 9divpcoe-master2 Ready,SchedulingDisabled 9divpcoe-master3 Ready,SchedulingDisabled 9divpcoe-node1 Ready 9divpcoe-node2 Ready 9divpcoe-node3 Ready 9d

Step 5 Verify the vmr namespaces using the following command:[root@ivpcoe-deployer ~]# kubectl get namespaces

Result:

NAME STATUS AGEdefault Active 9dkube-system Active 9dlogging Active 9dmanagement-infra Active 9dopenshift Active 9dopenshift-infra Active 9dvmr Active 9d

Step 6 Determine the current context for the kubectl config using the following command:[root@ivpcoe-deployer ~]# kubectl config view

Result:

apiVersion: v1clusters:- cluster:

api-version: v1insecure-skip-tls-verify: trueserver: https://172.22.7.85:8443

name: 172-22-7-85:8443- cluster:

insecure-skip-tls-verify: true



server: https://ivpcoe-master1.sekannia01.mosdns.com:8443name: ivpcoe-master1-sekannia01-mosdns-com:8443

contexts:- context:

cluster: 172-22-7-85:8443namespace: defaultuser: system/172-22-7-85:8443

name: default/172-22-7-85:8443/system- context:

cluster: ivpcoe-master1-sekannia01-mosdns-com:8443namespace: defaultuser: system/ivpcoe-master1-sekannia01-mosdns-com:8443

name: default/ivpcoe-master1-sekannia01-mosdns-com:8443/system- context:

cluster: 172-22-7-85:8443namespace: vmruser: system/172-22-7-85:8443

name: vmr/172-22-7-85:8443/systemcurrent-context: vmr/172-22-7-85:8443/systemkind: Config preferences: {}users:- name: system/172-22-7-85:8443user:

token: b0BLMeh3p30qJT-foBIX_AsYbn6rO0fsbMwiubLEEdI- name: system/ivpcoe-master1-sekannia01-mosdns-com:8443user:

token: RITipsPLgptSskjUAYNdwWN4m_kfyr5_NOipcanDa1E

Step 7 If necessary, set the correct context for kubectl using the following command:[root@ivpcoe-deployer ~]# kubectl config use-context vmr/172-22-7-85:8443/system

Result:

Switched to context "vmr/172-22-7-85:8443/system".

Step 8 Get the latest Cisco VMR bundle from the release page using the following command.[root@ivpcoe-deployer ~]# wget http://172.22.110.186/vmr-releases/vmr-cisco-1.2.5_latest/v2pc-npm-packages/cisco-vmr-1.2.500102.tgz

The examples in this section use VMR version 1.2.5; be sure to replace with the appropriate version.Note

Step 9 Unpack the cisco-vmr image in the target directory under using the following command:mkdir -p && tar -xvzf --strip 1 -C

Example:

[root@ivpcoe-deployer ~]# mkdir -p /root/cisco-vmr-1.2.5_001/ && tar -xvzfcisco-vmr-1.2.500102.tgz --strip 1 -C /root/cisco-vmr-1.2.5_001/

Step 10 Run the following command to locate the cisco-vmr.cfg.template file:[root@ivpcoe-deployer ~]# cd /root/cisco-vmr-1.2.5_001/templates/[root@ivpcoe-deployer templates]# lscisco-vmr.cfg.template inventory_template

Step 11 Edit the sample cisco-vmr.cfg.template file to specify MemSQL, VSRM, docker registry, COS and relevantconfiguration information:{"reconpath": "rio/recon-oc-shpadman","archivepath": "rio/archive-oc-shpadman",



"activepath": "rio/active-oc-shapdman","siteId": "ciscok8s","locality": "OC-SHPADMAN_RECORDER_MGR","vsrm": "172.22.110.171","k8sMaster": "172.22.7.85","objstorePassword": "cisco123","objstoreUsername": "cisco","objectstore": ["172.22.110.158"],"dbPassword": "","dbUsername": "root","databasePort": 3306,"databaseIP": ["172.22.7.122"],"databaseMasterPort": 3306,"databaseMasterIP": [],"dockerRegIp": "172.22.7.58""bulkDelete": "false","objStoreVip": "","optimizeObjStore": "proxy","usePutCopy": false,"adaptationBaseURL": false,"maxChannels": 5,"jitpServicePort": 9080,"rioApiPort": 9449,"dataPlaneVip": "","haproxyVip": "172.22.7.77","vmrServiceIp": "172.22.7.77","vmrServiceFqdn": "vmr-3.mosdns.com","openshiftPlatform": "Yes","jitpServiceHost": "http://riompe.pe1.mosdns.com/vmrstandalonempe/","rioApiHost": "pluto.cisco.com""httpsProxy": "","httpProxy": "","kafkaDefaultTopic": "logs","kafkaIhPort": "127.0.0.1:2182","usernameToken": "","vmrSelfHostname": "v2pcvmr-oc.cisco.com","logServer": "172.22.7.105","logServerType": "ELK""platformInfo": {"path": "platform/resources/config","packageName": "cisco-k8s-upic",}}

Step 12 Run the following commands under where the cisco-vmr bundle was unpacked to downloadall the VMR docker images:[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# cd /root/cisco-vmr-1.2.5_001[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# wget -r -np -nH --cut-dirs=2--exclude-directories=.svn --reject "index.html*,vmr_release*" http://172.22.110.186/

vmr-releases/vmr-cisco-1.2.5_latest/rio-docker-images/



Step 13 Run the following commands to copy the load_to_registry.sh script file from the scripts folder and load therio-docker-images to the Docker registry set in the cisco-vmr.cfg.template file. Tag the VMR version to thescript.[root@ivpcoe-deployer vmr-docker-images]# cd /root/cisco-vmr-1.2.5_001/rio-docker-images/[root@ivpcoe-deployer vmr-docker-images]# cp ../scripts/load_to_registry.sh ../load_to_registry.sh

Example:

[root@ivpcoe-deployer rio-docker-images]# ./load_to_registry.sh 172.22.7.58 cisco-1.2.5_001

Step 14 Run the following command to verify that all VMR images are tagged correctly in the Docker registry:docker images | grep

Example:

root@ivpcoe-deployer rio-docker-images]# docker images | grep 172.22.7.58

Result:

172.22.7.58:5000/vmr_release/health-monitor cisco-1.2.5_001 20c1e5b5efe8 5 weeks ago 200.8MB172.22.7.58:5000/vmr_release/api cisco-1.2.5_001 8ca07583e836 5 weeks ago 33.24 MB172.22.7.58:5000/vmr_release/a8-updater cisco-1.2.5_001 fe90dbe980bc 5 weeks ago 20.47 MB172.22.7.58:5000/vmr_release/nsa cisco-1.2.5_001 16246d59e4f1 5 weeks ago 20.47 MB172.22.7.58:5000/vmr_release/segment-recorder cisco-1.2.5_001 4d88bccf6249 5 weeks ago19.22 MB172.22.7.58:5000/vmr_release/recorder-manager cisco-1.2.5_001 b8e445abe7cd 5 weeks ago20.41 MB172.22.7.58:5000/vmr_release/reconstitution-agent cisco-1.2.5_001 a62626914dd4 5 weeks ago21.14 MB172.22.7.58:5000/vmr_release/manifest-agent cisco-1.2.5_001 9a6f02e4a3cd 5 weeks ago 22.78MB172.22.7.58:5000/vmr_release/dash-origin cisco-1.2.5_001 ca3912fbd323 5 weeks ago 21.41 MB172.22.7.58:5000/vmr_release/archive-agent cisco-1.2.5_001 49a018ba80b2 5 weeks ago 22.45MB172.22.7.58:5000/vmr_release/fluent cisco-1.2.5_001 18b3bd0256de 7 weeks ago 780.4 MB172.22.7.58:5000/vmr_release/ui cisco-1.2.5_001 9f5fa13f29f3 10 weeks ago 492.8 MB172.22.7.58:5000/vmr_release/cfgtool cisco-1.2.5_001 598056eb056b 10 weeks ago 19.4 MB172.22.7.58:5000/vmr_release/ipvs 1.0.9 852dc9202665 10 months ago 33.03 MB172.22.7.58:5000/vmr_release/rio-dev ZK_MHT_002 aaf4dd3dc6eb 14 months ago 299 MB

Step 15 Run the following commands to create UI secrets. Refer to Generate Kubernetes Secret for detailed instructions.[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# openssl req -newkey rsa:2048 -new -nodes-x509 -days 3650 -keyout /tmp/vmr.key -out /tmp/vmr.crt -subj "/C=US/ST=California/L=SanJose/O=ATT/CN=*.cisco.com"

Result:

Generating a 2048 bit RSA private keywriting new private key to '/tmp/vmr.key'[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# cd scripts[root@ivpcoe-deployer scripts]# sh create-vmr-secret.sh[root@ivpcoe-deployer scripts]# kubectl create -f ssl-secret.yaml --namespace=vmr[root@ivpcoe-deployer scripts]# kubectl get secrets --namespace=vmr

What to Do Next

Proceed to Install VMR in Standalone Mode.



b_VMR_Deployment_Guide_chapter_011.pdf#unique_37

Install VMR in Standalone ModeVMR standalone installation instructions can be found in the /README.md file. TheREADME.md file includes all the parameters needed to run the vmr_standalone.sh installation script. Theparameters can be exported or passed directly as arguments.[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# cd /root/cisco-vmr-1.2.5_001[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# lsapis Makefile package.json README.md rio-docker-images template.json utilsindex.js node_modules platform resources scripts templates

To install VMR, first run the installation script in Config mode and then run it in Start mode.

Run Installation Script in Config ModeThe installation script needs to be run in config mode only once as part of the installation. This script assumesthat all the parameters are configured for VMR installation in the cisco-vmr.cfg.template file.

Procedure

Step 1 Refer to the README.md file for information on each of the parameters in the script.Step 2 Run the installation script from the in config mode:

./scripts/vmr_standalone.sh $OPTION $VMR_CFG_PATH $PICINST $KUBECONFIG $TAG $DR_GROUP $CALLER$LOGFILE

Example:

[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# ./scripts/vmr_standalone.sh config /root/cisco-vmr-1.2.5_001 vmr/172-22-7-85:8443/system ~/.kube/config cisco-1.2.5_001 vmr_releasestandalone upgrade.txt

What to Do Next

Proceed to Run Installation Script in Start Mode.

Run Installation Script in Start ModeRunning the installation script in start mode brings up the VMR services and pods, creates OC routes fordash-origin and recorder-manager, and verifies that pods are running.

Procedure

Step 1 Run the installation script from the in start mode:./scripts/vmr_standalone.sh $OPTION $VMR_CFG_PATH $PICINST $KUBECONFIG $TAG $DR_GROUP $CALLER$LOGFILE


Installing VMR in Standalone ModeInstall VMR in Standalone Mode

Example:

[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# ./scripts/vmr_standalone.sh start /root/cisco-vmr-1.2.5_001 vmr/172-22-7-85:8443/system ~/.kube/config cisco-1.2.5_001 vmr_releasestandalone upgrade.txt

Refer to the README.md file for information on each of theparameters.

Note

Step 2 Run the following commands to verify that all endpoints, services, pods and routes are up.a) Run the following command to get endpoints:

root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get ep --namespace=vmr

Result:

NAME ENDPOINTS AGEa8-updater 10.128.2.205:9012,10.129.2.203:9012,10.129.2.205:9012 + 1 more... 2mactive-storage 172.22.110.158:443,172.22.110.158:80 2mapi 10.131.0.194:9999,10.131.0.194:8443 2marchive-agent 10.128.2.197:9150,10.128.2.198:9150,10.129.2.196:9150 + 3 more... 2marchive-storage 172.22.110.158:443,172.22.110.158:80 2mdash-origin 10.128.2.196:8082,10.128.2.199:8082,10.128.2.200:8082 + 9 more... 2mhealth-monitor 10.128.2.191:8083 1mmanifest-agent 10.128.2.202:8081,10.128.2.203:8081,10.129.2.201:8081 + 3 more... 2mmemsql 172.22.7.122:3306 2mmemsql-master 172.22.7.122:3306 2mnsa 10.131.0.206:9013 2mreconstitution-agent 10.128.2.192:9009,10.128.2.193:9009,10.128.2.194:9009 + 9 more...2mrecorder-manager 10.128.2.204:9004,10.129.2.208:9004,10.131.0.204:9004 2msegment-recorder 10.128.2.206:9000,10.128.2.207:9000,10.128.2.208:9000 + 9 more... 2mui 10.129.2.211:9555,10.129.2.211:9998 2mzookeeper-01 10.128.2.189:2181,10.128.2.189:9041,10.128.2.189:3888 + 1 more... 2mzookeeper-02 10.129.2.190:2181,10.129.2.190:9042,10.129.2.190:3888 + 1 more... 2mzookeeper-03 10.131.0.188:9043,10.131.0.188:2181,10.131.0.188:3888 + 1 more... 2mzookeeper-04 10.128.2.190:9044,10.128.2.190:2181,10.128.2.190:3888 + 1 more... 2mzookeeper-05 10.131.0.189:2181,10.131.0.189:9045,10.131.0.189:3888 + 1 more... 2m

b) Run the following command to get services:[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get svc --namespace=vmr

Result:

NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGEa8-updater 172.30.181.78 172.29.178.100,172.29.178.100 9012:9112/TCP 3mactive-storage 172.30.242.130 80:9102/TCP,443:9443/TCP 3mapi 172.30.150.220 172.29.110.46,172.29.110.46 9999:9999/TCP,8443:9449/TCP 3marchive-agent 172.30.183.252 172.29.109.204,172.29.109.204 9150:9150/TCP 3marchive-storage 172.30.61.240 80:9106/TCP,443:9446/TCP 3mdash-origin 172.30.141.255 172.29.117.56,172.29.117.56 8082:9182/TCP 3mhealth-monitor 172.30.251.76 172.29.214.26,172.29.214.26 8083:9170/TCP 2mmanifest-agent 172.30.146.171 172.29.159.254,172.29.159.254 8081:9181/TCP 3mmemsql 172.30.85.182 3306:9306/TCP 3mmemsql-master 172.30.115.148 3306:9307/TCP 3mnsa 172.30.46.101 172.29.101.9,172.29.101.9 9013:9113/TCP 3mreconstitution-agent 172.30.162.73 172.29.245.181,172.29.245.181 9009:9109/TCP 3mrecorder-manager 172.30.6.224 172.29.197.78,172.29.197.78 9004:9104/TCP 3msegment-recorder 172.30.1.82 172.29.147.207,172.29.147.207 9000:9100/TCP 3mui 172.30.80.62 172.29.100.254,172.29.100.254 9555:9110/TCP,9998:9998/TCP 3m


Installing VMR in Standalone ModeRun Installation Script in Start Mode

zookeeper-01 172.30.110.55 2181:9201/TCP,2888:9202/TCP,3888:9203/TCP,9041:9041/TCP3mzookeeper-02 172.30.254.239 2181:9206/TCP,2888:9207/TCP,3888:9208/TCP,9042:9042/TCP 3mzookeeper-03 172.30.131.237 2181:9211/TCP,2888:9212/TCP,3888:9213/TCP,9043:9043/TCP 3mzookeeper-04 172.30.189.219 2181:9216/TCP,2888:9217/TCP,3888:9218/TCP,9044:9044/TCP 3mzookeeper-05 172.30.241.57 2181:9221/TCP,2888:9222/TCP,3888:9223/TCP,9045:9045/TCP3m

c) Run the following command to get pods:[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get pods --namespace=vmr

Result:

NAME READY STATUS RESTARTS AGEa8-updater-dn65b 1/1 Running 0 2ma8-updater-hvhmw 1/1 Running 0 2ma8-updater-k5tkj 1/1 Running 0 2ma8-updater-qfqx6 1/1 Running 0 2mapi-v2fn9 1/1 Running 0 2marchive-agent-86wzf 1/1 Running 0 2marchive-agent-dnvss 1/1 Running 0 2marchive-agent-gm2n2 1/1 Running 0 2marchive-agent-m8jr7 1/1 Running 0 2marchive-agent-vhf9p 1/1 Running 0 2marchive-agent-vn676 1/1 Running 0 2mdash-origin-54fq7 1/1 Running 0 2mdash-origin-5x5gg 1/1 Running 0 2mdash-origin-69bpg 1/1 Running 0 2mdash-origin-9dvtq 1/1 Running 0 2mdash-origin-dc9bj 1/1 Running 0 2mdash-origin-frv5c 1/1 Running 0 2mdash-origin-hr6ts 1/1 Running 0 2mdash-origin-nx5nm 1/1 Running 0 2mdash-origin-qmslq 1/1 Running 0 2mdash-origin-rrt2m 1/1 Running 0 2mdash-origin-vb9rs 1/1 Running 0 2mdash-origin-wpflh 1/1 Running 0 2mfluent-ghdj7 1/1 Running 0 2mfluent-h6wcr 1/1 Running 0 2mfluent-hc84c 1/1 Running 0 2mfluent-nvj3t 1/1 Running 0 2mfluent-q9php 1/1 Running 0 2mfluent-tk6j5 1/1 Running 0 2mhealth-monitor-b8ht5 1/1 Running 0 2mmanifest-agent-9tz8p 1/1 Running 0 2mmanifest-agent-cj532 1/1 Running 0 2mmanifest-agent-jdh9b 1/1 Running 0 2mmanifest-agent-k2fmm 1/1 Running 0 2mmanifest-agent-p7sdx 1/1 Running 0 2mmanifest-agent-rvbhx 1/1 Running 0 2mnsa-gkxww 1/1 Running 0 2mreconstitution-agent-050n9 1/1 Running 0 2mreconstitution-agent-0mzj7 1/1 Running 0 2mreconstitution-agent-326c4 1/1 Running 0 2m



reconstitution-agent-65mvt 1/1 Running 0 2mreconstitution-agent-97sxj 1/1 Running 0 2mreconstitution-agent-bmmr8 1/1 Running 0 2mreconstitution-agent-chnb7 1/1 Running 0 2mreconstitution-agent-lcrkg 1/1 Running 0 2mreconstitution-agent-mqhtv 1/1 Running 0 2mreconstitution-agent-pp0dn 1/1 Running 0 2mreconstitution-agent-v4nqr 1/1 Running 0 2mreconstitution-agent-zs527 1/1 Running 0 2mrecorder-manager-1s0l9 1/1 Running 0 2mrecorder-manager-fp6d8 1/1 Running 0 2mrecorder-manager-s1557 1/1 Running 0 2msegment-recorder-056wq 1/1 Running 0 2msegment-recorder-279jh 1/1 Running 0 2msegment-recorder-fk6nt 1/1 Running 0 2msegment-recorder-gb3p8 1/1 Running 0 2msegment-recorder-hqvb2 1/1 Running 0 2msegment-recorder-nzpgc 1/1 Running 0 2msegment-recorder-pj35z 1/1 Running 0 2msegment-recorder-qxt92 1/1 Running 0 2msegment-recorder-sqwg8 1/1 Running 0 2msegment-recorder-vxgv0 1/1 Running 0 2msegment-recorder-xrr6q 1/1 Running 0 2msegment-recorder-zc8r3 1/1 Running 0 2mui-0m851 1/1 Running 0 2mzookeeper-01-rtz2z 1/1 Running 0 3mzookeeper-02-rqdgm 1/1 Running 0 3mzookeeper-03-jn9t0 1/1 Running 0 3mzookeeper-04-2hmxp 1/1 Running 0 3mzookeeper-05-69h3v 1/1 Running 0 3m

d) Run the following command to get routes:[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get routes --namespace=vmr

Result:

NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARDdash-origin dash-origin.dp.vmr-3.mosdns.com ... 1 more dash-origin Nonerecorder-manager recorder-manager.cp.vmr-3.mosdns.com ... 1 more recorder-manager None

Step 3 Access the VMR dashboard at https://:9110 using the following credentials:

• Username—root

• Password—deJaneiro

The cisco-vmr.cfg.template file must contain the vmrServiceIp and rioApiHost to access the VMRDashboard.

Note

Step 4 Use the VMR Dashboard to create streams. Refer to the Cisco Virtual Media Recorder User Guide forinstructions.



Manage Streams Via Rio-APIYou can also create, update and delete streams in the VMR Dashboard or by using the rio-api. This sectionprovides the commands to create, update and delete streams using the rio-api and replacing with the appropriate IP address.

Create Streamscurl -v -kH "Content-Type: application/json" -u root:deJaneiro -X POST -d @streams.jsonhttps://:9449/api/streams/create

Update Streamscurl -v -kH "Content-Type: application/json" -u root:deJaneiro -X POST -d @streams.jsonhttps://:9449/api/streams/update

Delete Streamscurl -v -kH "Content-Type: application/json" -u root:deJaneiro -X DELETE -d @streams.jsonhttps://:9449/api/streams/delete/

Sample streams.json[{"streamName": "CiscoTestStream","streamId": "4","expiry": "2027-02-19T21:25:00Z","noDeDupe": false,"url": "http://172.22.110.202/cdvr-mfc-4/4/manifest.mpd","avgBitrate": 6.557,"maxBitrate": 6.557,"archiveTime": 259200,"reArchiveTime": 86400,"archivalStartTime": "12:01AM","archivalDuration": 86400,"archivalPause": 10000}]

Run Installation Script in Stop ModeRunning the installation script in stop mode removes the VMR services, pods and endpoints. The stop modeis used if you want to completely stop the application or to perform any reconfigurations. Refer to theREADME.md file for information on each of the parameters.

Procedure

Step 1 Run the following command from the to execute the script in stop mode:./scripts/vmr_standalone.sh $OPTION $VMR_CFG_PATH $PICINST $KUBECONFIG$TAG $DR_GROUP $CALLER $LOGFILE

Example:

[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# ./scripts/vmr_standalone.sh stop/root/cisco-vmr-1.2.5_001 vmr/172-22-7-85:8443/system ~/.kube/config cisco-1.2.5_001vmr_release standalone upgrade.txt


Installing VMR in Standalone ModeRun Installation Script in Stop Mode

Step 2 Run the following commands to verify that all pods, services and endpoints are deleted. All commands shouldreturn No resources found.a) Run the following command to get pods:

[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get pods --namespace=vmr

b) Run the following command to get services:[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get svc --namespace=vmr

c) Run the following command to get endpoints:[root@ivpcoe-deployer cisco-vmr-1.2.5_001]# kubectl get ep --namespace=vmr

Upgrade Standalone VMRThis section provides instructions for upgrading a standalone VMR deployment using rolling upgrade.

Procedure

Step 1 Get the target cisco vmr bundle from the release server:[root@ivpcoe-deployer ~]# wget http:///vmr-releases/vmr-cisco-/v2pc-npm-packages/cisco-vmr-.tgz

Example:

[root@ivpcoe-deployer ~]# wget http://172.22.110.186/vmr-releases/vmr-cisco-1.3.2_009/v2pc-npm-packages/cisco-vmr-1.3.200901.tgz

Step 2 Unpack the cisco-vmr image in the target directory under mkdir -p && tar -xvzf --strip 1 -C

Example:

[root@ivpcoe-deployer ~]# mkdir -p /root/cisco-vmr-1.3.2_009 && tar -xvzfcisco-vmr-1.3.200901.tgz--strip 1 -C /root/cisco-vmr-1.3.2_009/

Step 3 Copy the cisco-vmr.cfg.template file located under /templates/ to/templates/:[root@ivpcoe-deployer ~]# cp /root/cisco-vmr-/templates/cisco-vmr.cfg.template/root/cisco-vmr-/templates

Step 4 Run the installation script in config mode from the . Refer to the README.md file forinformation on the parameters.[root@ivpcoe-deployer ~]# cd /root/cisco-vmr-./scripts/vmr_standalone.sh $OPTION $VMR_CFG_PATH $PICINST $KUBECONFIG $TAG $DR_GROUP $CALLER$LOGFILE

Example:

[root@ivpcoe-deployer cisco-vmr-1.3.200901]# ./scripts/vmr_standalone.sh config/root/cisco-vmr-1.3.200901 vmr/ru-ivpcoe-lb1-vmrru-ds5-323-tril-com:8443/system ~/.kube/configcisco-1.3.2_009vmr_release standalone Rollingupgrade_config.txt


Installing VMR in Standalone ModeUpgrade Standalone VMR

Step 5 Download the VMRdocker images under /target-directory>/rio-docker-images. Run the following commandunder where the cisco-vmr bundle was unpacked:[root@ivpcoe-deployer ~]# cd /root/cisco-vmr-/[root@ivpcoe-deployer cisco-vmr-]# wget -r -np -nH --cut-dirs=2 --no-parent--exclude-directories=.svn--reject "index.html*,vmr_release*" http:///vmr-releases/vmr-cisco-/rio-docker-images/

Step 6 Copy the load_to_registry.sh script file and tag it with the VMR version; this loads the rio-docker-imagesto the docker registry set in the cisco-vmr.cfg file.[root@ivpcoe-deployer ~]# cd /root/cisco-vmr-/rio-docker-images/[root@ivpcoe-deployer rio-docker-images]# cp ../scripts/load_to_registry.sh ../load_to_registry.sh

Example:

[root@ivpcoe-deployer rio-docker-images]# ./load_to_registry.sh 172.10.1.20 cisco-1.3.2_009

Step 7 Verify that all VMR images are correctly tagged in the docker registry:docker images | grep

Step 8 Run the installation script in upgrade mode (rolling upgrade) from the :[root@ivpcoe-deployer rio-docker-images]# cd /root/cisco-vmr-./scripts/vmr_standalone.sh $OPTION $VMR_CFG_PATH $PICINST $KUBECONFIG $TAG $DR_GROUP$CALLER $LOGFILE

Example:

[root@ivpcoe-deployer cisco-vmr-1.3.200901]# ./scripts/vmr_standalone.sh upgrade/root/cisco-vmr-1.3.200901 vmr/ru-ivpcoe-lb1-vmrru-ds5-323-tril-com:8443/system ~/.kube/config cisco-1.3.2_009 vmr_release standalone Rollingupgrade.txt

The rolling upgrade progress is displayed similar to the to following:

Cisco VMR Upgrade Progress VMR Version: from: cisco-1.3.2_004 -> to:cisco-1.3.2_009 |+-----------------------------------------------------------------------------------------------------------------------+| Microservices|Progress | Version | Status

|+-----------------------------------------------------------------------------------------------------------------------+| a8-updater|100% Completed] | cisco-1.3.2_009 | 4 running 0failed || api|[100% Completed] | cisco-1.3.2_009 | 1 running 0failed || archive-agent|[100% Completed] | cisco-1.3.2_009 | 8 running 0failed || dash-origin| [52% Completed] | cisco-1.3.2_009 | 20 running 0failed || manifest-agent| [60% Completed] | cisco-1.3.2_009 | 5 running 0failed || nsa|[100% Completed] | cisco-1.3.2_009 | 1 running 0failed ||reconstitution-agent| [54% Completed] | cisco-1.3.2_009 | 22 running 0failed || recorder-manager| [45% Completed] | cisco-1.3.2_009 | 5 running 0failed || segment-recorder| [46% Completed] | cisco-1.3.2_009 | 18 running 0failed || ui|[100% Completed] | cisco-1.3.2_009 | 1 running 0failed |



| zookeeper-01|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-02|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-03|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-04|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-05|[100% Completed] | ZK_MHT_002 | 1 running 0failed |+-----------------------------------------------------------------------------------------------------------------------+

Upon completion, the folling message is displayed indicating the rolling upgrade is successful:

+-----------------------------------------------------------------------------------------------------------------------+|Cisco VMR Upgrade Progress VMR Version: from: cisco-1.3.2_004 -> to:cisco-1.3.2_009 |+-----------------------------------------------------------------------------------------------------------------------+| Microservices| Progress | Version | Status

|+-----------------------------------------------------------------------------------------------------------------------+| a8-updater|[100% Completed] | cisco-1.3.2_009 | 4 running 0failed || api|[100% Completed] | cisco-1.3.2_009 | 1 running 0failed || archive-agent|[100% Completed] | cisco-1.3.2_009 | 8 running 0failed || dash-origin|[100% Completed] | cisco-1.3.2_009 | 40 running 0failed || manifest-agent|[100% Completed] | cisco-1.3.2_009 | 8 running 0failed || nsa|[100% Completed] | cisco-1.3.2_009 | 1 running 0failed ||reconstitution-agent|[100% Completed] | cisco-1.3.2_009 | 40 running 0failed || recorder-manager|[100% Completed] | cisco-1.3.2_009 | 10 running 0failed || segment-recorder|[100% Completed] | cisco-1.3.2_009 | 40 running 0failed || ui|[100% Completed] | cisco-1.3.2_009 | 1 running 0failed || zookeeper-01|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-02|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-03|[100% Completed] | ZK_MHT_002 | 1 running 0failed || zookeeper-04|#################### [100% Completed] | ZK_MHT_002 |

1 running 0 failed || zookeeper-05|#################### [100% Completed] | ZK_MHT_002 |

1 running 0 failed |+-----------------------------------------------------------------------------------------------------------------------++ '[' 0 -eq 1 ']'+ wait 22278



+ '[' 0 -eq 1 ']'++ timestamp++ date '+%Y-%m-%d %T'+ echo '2017-10-03 13:15:40 Upgrade Success'2017-10-03 13:15:40 Upgrade Success+ exit 0





Installing VMR in Standalone ModeIntroductionPre-installation ProcedureInstall VMR in Standalone ModeRun Installation Script in Config ModeRun Installation Script in Start ModeManage Streams Via Rio-API

Run Installation Script in Stop Mode

Upgrade Standalone VMR

Installing VMR in Standalone Mode - Cisco...Installing VMR in Standalone Mode ThischapterprovidesinstructionsforinstallingandupgradingVMRinstandalonemode.Itincludesthe followingtopics:

Documents