commit | f9b38f5dd1d88fd20cd2370906e061c152b00c88 | [log] [tgz] |
---|---|---|
author | Omar Abdelkader <omikader@gmail.com> | Mon Jul 17 18:13:50 2017 -0600 |
committer | Omar Abdelkader <omikader@gmail.com> | Mon Jul 17 18:13:50 2017 -0600 |
tree | d1a9da3ff29bca2a427992af05ebf4d53b241501 | |
parent | 5023a8f6740db75fad155e3d2f458c0c791765d2 [diff] |
Fix vPGWC synchronizer issue Change-Id: I27cff20e4814a7ee2aef7cb3a23b89ccbf687882
To onboard this service in your system, you can add the service to the mcord.yml
profile manifest:
xos_services: - name: vPGWC path: orchestration/xos_services/vPGWC keypair: mcord_rsa synchronizer: true
Once you have added the service, you will need to rebuilt and redeploy the XOS containers from source. Login to the corddev
vm and cd /cord/build
$ ./gradlew -PdeployConfig=config/mcord_in_a_box.yml :platform-install:buildImages $ ./gradlew -PdeployConfig=config/mcord_in_a_box.yml :platform-install:publish $ ./gradlew -PdeployConfig=config/mcord_in_a_box.yml :orchestration:xos:publish $ ./gradlew -PdeployConfig=config/mcord_in_a_box.yml PIprepPlatform
Now the new XOS images should be published to the registry on prod
. To bring them up, login to the prod
VM and define these aliases:
$ CORD_PROFILE=$( cat /opt/cord_profile/profile_name ) $ alias xos-pull="docker-compose -p $CORD_PROFILE -f /opt/cord_profile/docker-compose.yml pull" $ alias xos-up="docker-compose -p $CORD_PROFILE -f /opt/cord_profile/docker-compose.yml up -d" $ alias xos-teardown="pushd /opt/cord/build/platform-install; ansible-playbook -i inventory/head-localhost --extra-vars @/opt/cord/build/genconfig/config.yml teardown-playbook.yml; popd" $ alias compute-node-refresh="pushd /opt/cord/build/platform-install; ansible-playbook -i /etc/maas/ansible/pod-inventory --extra-vars=@/opt/cord/build/genconfig/config.yml compute-node-refresh-playbook.yml; popd"
To pull new images from the database and launch the containers, while retaining the existing XOS database, run:
$ xos-pull; xos-up
Alternatively, to remove the XOS database and reinitialize XOS from scratch, run:
$ xos-teardown; xos-pull; xos-launch; compute-node-refresh