commit | 3068347d22595259525ebd411d5faf4feae95518 | [log] [tgz] |
---|---|---|
author | Yunpeng Zhang <zyp8884625@gmail.com> | Sat Jul 15 15:26:25 2017 -0400 |
committer | Yunpeng Zhang <zyp8884625@gmail.com> | Sat Jul 15 12:27:46 2017 -0700 |
tree | b1654a81213907fd4aa513a2ac9ffb7fb19223f2 | |
parent | d01f3ce178be76cda8fd812fb273a41348b3407c [diff] |
Add vBBU services to Services List, for cord-3.0 Change-Id: Ia5e3bf608a705ce06f09784f83fcb1e4245e0b3b
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