commit | d01f3ce178be76cda8fd812fb273a41348b3407c | [log] [tgz] |
---|---|---|
author | Yunpeng Zhang <zyp8884625@gmail.com> | Thu Jul 06 20:06:35 2017 -0400 |
committer | Yunpeng Zhang <zyp8884625@gmail.com> | Thu Jul 06 23:09:56 2017 -0700 |
tree | d7b4780e8b861b20d53e288ee889ec11f544bc14 | |
parent | 4a96206e272226f03b3ab37a2d1669b9653d5c2e [diff] |
Refactor vBBU from 2.0 to 3.0, not for master Change-Id: Ib2d68852ad4065d8c34599dca731123ed6297e84
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