Summary:
Certain deployments may restrict application nodes from accessing the internet when they are provisioned by CloudCenter (CC), thereby limiting their access to required files hosted by CC's public repositories. In such cases, it is necessary for an internal repo server(s) to be deployed to mimic the public repos. Internal repositories require routine maintenance, specifically to keep their file versions parallel to those of the CC appliances.
Logging on to the CloudCenter Orchestrator (CCO):
The following are sample methods of authenticating to a CCO image provided by Cisco
| IaaS | Format | Username | Password |
|---|---|---|---|
| vCenter | OVA | root | welcome2cliqr |
| Amazon AWS | AMI | centos | N/A *key pair required |
| OpenStack | QCOW | root | N/A *key pair required |
| MetaCloud | RAW (converted from QCOW) | root | welcome2cliqr or key pair |
Editing the properties files:
- Step 1: On the CCO, navigate to /usr/local/tomcat/webapps/ROOT/WEB-INF
command cd /usr/local/tomcat/webapps/ROOT/WEB-INF 
- Step 2: Create a backup of the gateway.properties file
command cp gateway.properties{,.bak} 
- Step 3: Edit the gateway.properties file
command vi gateway.properties
- the following is a sample of the file's content
gateway.properties ## Encryption parameters
salt=cliqr technology inc. secret salt
bootstrapData=osmosix
useStrongEncryption=true
## URL to bootstrap script
agent.bundle.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap-cliqr-worker.sh
agent.bundle.url.windows=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap-cliqr-worker.ps1
dfs.bundle.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap-cliqr-dfs.sh
hazelcast.mapstore.enabled=true
#separate ldap and activemq from gateway
gateway.separate.enabled=false
ldap.server.ip=localhost
jms.server.ip=localhost
hazelcast.mapstore.enabled=true
hazelcast.tcpip.enabled=true
hazelcastIPList=127.0.0.1
bootstrap.js.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap.json
bootstrap.ssh.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap-cliqr-ssh.sh
bootstrap.py.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/cliqr-bootstrap.py
bootstrap.win.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap-cliqr-init.ps1
bootstrap.linux.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/bootstrap-cliqr-init.sh
bootstrap.ps.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/cliqr-bootstrap.ps1
#Time gateway waits before performming bootstrapping
bootstrap.waittime=15
#path to repo containing all system service bundles
system.service.bundle.path=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/services
#path to repo containing all external system service bundles
system.external.service.bundle.path=http://sp-poc.s3.amazonaws.com/bundle/services/external
#optional path to the repo server containing all the .deb and .rpm packages
custom.repository.url=http://repo.cliqrtech.com
# Agent Upgrade metada
agent.upgrade.linux.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/upgrade-linux.json
agent.upgrade.win.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/upgrade-win.json
node.metadata.url=http://cdn.cliqr.com/release-4.5.2-20160609.3/bundle/cloud-node-metadata.war
maximum.bootstrap.wait.time=3600
node.heartbeat.time=180000
- To redirect clients to an internal repo, look for the values starting with "http://*" and change them from "cdn.cliqr.com/*" to the IP address of the repo server
- in this example, the text containing "http://cdn.cliqr.com/release-4.5.2-20160609.3" will be changed to "http://192.168.200.130"
- Step 4:
- the following is a sample of the changes
| gateway.properties |
|---|
## Encryption parameters salt=cliqr technology inc. secret salt bootstrapData=osmosix useStrongEncryption=true ## URL to bootstrap script agent.bundle.url=http://192.168.200.130/bundle/bootstrap-cliqr-worker.sh agent.bundle.url.windows=http://192.168.200.130/bundle/bootstrap-cliqr-worker.ps1 dfs.bundle.url=http://192.168.200.130/bundle/bootstrap-cliqr-dfs.sh hazelcast.mapstore.enabled=true #separate ldap and activemq from gateway gateway.separate.enabled=false ldap.server.ip=localhost jms.server.ip=localhost hazelcast.mapstore.enabled=true hazelcast.tcpip.enabled=true hazelcastIPList=127.0.0.1 bootstrap.js.url=http://192.168.200.130/bundle/bootstrap.json bootstrap.ssh.url=http://192.168.200.130/bundle/bootstrap-cliqr-ssh.sh bootstrap.py.url=http://192.168.200.130/bundle/cliqr-bootstrap.py bootstrap.win.url=http://192.168.200.130/bundle/bootstrap-cliqr-init.ps1 bootstrap.linux.url=http://192.168.200.130/bundle/bootstrap-cliqr-init.sh bootstrap.ps.url=http://192.168.200.130/bundle/cliqr-bootstrap.ps1 #Time gateway waits before performming bootstrapping bootstrap.waittime=15 #path to repo containing all system service bundles system.service.bundle.path=http://192.168.200.130/bundle/services #path to repo containing all external system service bundles system.external.service.bundle.path=http://sp-poc.s3.amazonaws.com/bundle/services/external #optional path to the repo server containing all the .deb and .rpm packages custom.repository.url=http://repo.cliqrtech.com # Agent Upgrade metada agent.upgrade.linux.url=http://192.168.200.130/bundle/upgrade-linux.json agent.upgrade.win.url=http://192.168.200.130/bundle/upgrade-win.json node.metadata.url=http://192.168.200.130/bundle/cloud-node-metadata.war maximum.bootstrap.wait.time=3600 node.heartbeat.time=180000 |
- If the repo server for *.deb and *.rpm packages is also hosted on an internal server, change the custom.repository.url value (these packages are intended for CC's out-of-box services)
- An example would be to change the default value of http://repo.cliqrtech.com to http://192.168.200.130
- Step 5:
keystroke :%s#http://repo.cliqrtech.com#http://192.168.200.130# Press ENTER/RETURN Press ESC, then :wq to save the changes to the file
- Step 6: On the internal repo server, navigate to the bundle directory (the location of this directory is dependent upon the user's discretion at the time of the repo server's deployment). This example assumes that the files pertaining to the Package repo and the Bundle repo are hosted on the same server, and that package files are stored in the /repo directory and bundle files are stored in the /repo/bundle directory
command cd /repo/bundle
- Step 7: Execute the set_bundle_location.sh script
command ./set_bundle_location http://192.168.200.130/bundle
