commit | 676b9aa8e45d403b051324e6b86035656cf2e04f | [log] [tgz] |
---|---|---|
author | Omar Abdelkader <omikader@gmail.com> | Wed Aug 30 10:40:49 2017 -0600 |
committer | Omar Abdelkader <omikader@gmail.com> | Tue Sep 05 14:22:16 2017 -0600 |
tree | 9dfd0c2a7e26f95d6fd4984bf4aa9b24f25191f5 | |
parent | e4080aed4ebd5d412ba1a5f442f5692f8b05269e [diff] |
epc-as-a-service functionality added Change-Id: Ia1da1cb2c82eaf77cf87e9e80f3f1a93c433cbe5
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