commit | a9808975463ecbb8d3e737b959f2385a7ccef4b7 | [log] [tgz] |
---|---|---|
author | Omar Abdelkader <omikader@gmail.com> | Fri Sep 15 12:50:32 2017 -0500 |
committer | Omar Abdelkader <omikader@gmail.com> | Fri Sep 15 12:50:32 2017 -0500 |
tree | 3826dbf0a5aaa3d3692a9c2b8b1bf06d2d070fc7 | |
parent | 683d7a6bd35d3df2bafb122884fa9eded6e1aa99 [diff] |
add xos_base_props to Vendor model Change-Id: I9b7b9945242c04043f59f95f784bcac4c289ad9a
To onboard this service in your system, you can add the service to the mcord.yml
profile manifest:
xos_services: - name: vpgwc path: orchestration/xos_services/vpgwc 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