| commit | a2c2733d06fd14ce8115af5f346ce4f292c3f5c2 | [log] [tgz] |
|---|---|---|
| author | Yunpeng Zhang <zyp8884625@gmail.com> | Tue Aug 15 23:00:11 2017 -0400 |
| committer | Yunpeng Zhang <zyp8884625@gmail.com> | Wed Aug 16 17:24:06 2017 -0700 |
| tree | eab325db91f7783951155ad8d9a3e20222a7ea60 | |
| parent | 6999fe2e238ff615bd3eb6a9c9e388c3eaba5c55 [diff] |
add vSGWU services Change-Id: I8fb098b5cf81a6dc9061b6fd4187ce62164997c7
To onboard this service in your system, you can add the service to the mcord.yml profile manifest:
xos_services:
- name: vsgwu
path: orchestration/xos_services/vsgwu
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 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