commit | 01762cb04b3ca7fa25fab4a73de610c87f1bea62 | [log] [tgz] |
---|---|---|
author | Yunpeng Zhang <zyp8884625@gmail.com> | Sun Jul 30 00:25:42 2017 -0400 |
committer | Yunpeng Zhang <zyp8884625@gmail.com> | Sun Jul 30 00:25:42 2017 -0400 |
tree | a768803467b18c5f525b981fcb77c2be1bda9d50 | |
parent | 8be6e07a78bc9ff4844ed1e47ebbcb04194043c2 [diff] |
Fixed sync problem which will cause MAAS failed Change-Id: I73221668629b476b0b126419b00a5e455ee22a6f
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 :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