commit | 7ea29aa8316054b1e30e3f1d1f7dd6ab411b6ce5 | [log] [tgz] |
---|---|---|
author | Pingping Lin <pingping@onlab.us> | Tue Oct 03 16:39:23 2017 -0700 |
committer | Andy Bavier <andy@onlab.us> | Tue Oct 10 14:43:27 2017 -0700 |
tree | 4e4674922ef7cc5b68947d45c39ffb725db23a3d | |
parent | 5b7a5d48134b8d4ba36b8d5afbd9402ff1bd09c9 [diff] |
move all 3.0 files to 4.1 as the first step Change-Id: Iab7810a02bfdf25bffca4e144fcae994f72e0048
To onboard this service in your system, you can add the service to the mcord.yml
profile manifest:
xos_services: - name: vmme path: orchestration/xos_services/vmme keypair: mcord_rsa synchronizer: true
Once you have added the service, you will need to rebuild 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