commit | e5f2b9cca5a9b1804a33d81263fa228a80fb6d60 | [log] [tgz] |
---|---|---|
author | Yunpeng Zhang <zyp8884625@gmail.com> | Sun Jul 30 00:23:38 2017 -0400 |
committer | Yunpeng Zhang <zyp8884625@gmail.com> | Sun Jul 30 00:23:38 2017 -0400 |
tree | 81b5453bc4725ab4da4b4029a2c6b0124d4f98ff | |
parent | 316ccb370445cdc26ea2f1c0e2d1c0de596d1051 [diff] |
Fixed Sync Problem which will cause MAAS failed Change-Id: I696abcf35774339689c3d97eabd7ab88612fd740
To onboard this service in your system, you can add the service to the mcord.yml
profile manifest:
xos_services: - name: vBBU path: orchestration/xos_services/vBBU 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