commit | 6e3df1dfcc5a1ff77f3ead40258867d28dc2b4fd | [log] [tgz] |
---|---|---|
author | Omar Abdelkader <omikader@gmail.com> | Thu Aug 03 20:12:09 2017 -0500 |
committer | Omar Abdelkader <omikader@gmail.com> | Thu Aug 03 20:12:09 2017 -0500 |
tree | c2b3ba3a0b4968213cfbb40aa04f8415f4bb3322 | |
parent | fd63fdda07fd048bc73c61844f886c182a1b1533 [diff] |
change property requirement Change-Id: Ibb7df10ea9246e0d7efe7656faf19f8b2eb9ad07
To onboard this service in your system, you can add the service to the mcord.yml
profile manifest:
xos_services: - name: vsgw path: orchestration/xos_services/vsgw 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