| commit | bf7d6c50efc13333c176e6f040a79145ed73dbdc | [log] [tgz] |
|---|---|---|
| author | Omar Abdelkader <omikader@gmail.com> | Wed Sep 13 21:18:43 2017 -0500 |
| committer | Omar Abdelkader <omikader@gmail.com> | Thu Sep 14 12:17:33 2017 -0500 |
| tree | bd85f5a44915b2e50835401b43e2f4415828e29c | |
| parent | 457b88c4c66b9ca0f74451be1951dcb06070fcc7 [diff] |
Fix m4 import typo Change-Id: Ifb88d5de5b3db62cb05af84fb977ac300729bbb9
To onboard this service in your system, you can add the service to the mcord.yml profile manifest:
xos_services:
- name: vsgwc
path: orchestration/xos_services/vsgwc
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 PIprepPlatform $ ./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
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 --remove-orphans" $ 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