cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Changing the CloudCenter Orchestrator to direct clients to an internal repo

444
Views
5
Helpful
0
Comments

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
FormatUsernamePassword
vCenterOVArootwelcome2cliqr
Amazon AWSAMIcentosN/A  *key pair required
OpenStackQCOWrootN/A  *key pair required
MetaCloudRAW (converted from QCOW)rootwelcome2cliqr 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
      Screen+Shot+2016-07-26+at+9.45.41+PM.png
  • Step 2: Create a backup of the gateway.properties file

    • commandcp gateway.properties{,.bak}
      Screen+Shot+2016-07-26+at+9.59.10+PM.png
  • Step 3: Edit the gateway.properties file
    • command
      vi gateway.properties

Screen+Shot+2016-07-26+at+9.54.32+PM.png

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

  • 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

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards
This widget could not be displayed.