commit | a1733f0eb2c1b499faa82e443ad20ec99e106b67 | [log] [tgz] |
---|---|---|
author | Omar Abdelkader <omikader@gmail.com> | Fri Sep 15 12:49:13 2017 -0500 |
committer | Omar Abdelkader <omikader@gmail.com> | Fri Sep 15 12:49:13 2017 -0500 |
tree | e6bc3d8f81ee407467ff0aafb18932acd776e36f | |
parent | 0cc3937d3cd9a173bf6544a240b3b9de72af92e3 [diff] |
add xos_base_props to Vendor model Change-Id: If94363d2005e52b87db6b98455442eeecc573c5a
To onboard this service in your system, you can add the service to the mcord.yml
profile manifest:
xos_services: - name: vhss path: orchestration/xos_services/vhss 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