| commit | e876c0910dc6eb529fa5c69da4eeecb8d22c1a26 | [log] [tgz] |
|---|---|---|
| author | Sapan Bhatia <sapan@opennetworking.org> | Wed Sep 20 06:42:38 2017 -0700 |
| committer | Sapan Bhatia <sapan@opennetworking.org> | Wed Sep 20 14:51:07 2017 -0700 |
| tree | f3a42f22788c309eee2bc9de5e56bfd3f6f2f64e | |
| parent | 39d789f9bde6aa4cadcba620f5ff8ea7ea0c5378 [diff] |
CORD-1913: Restore execution of custom service save() methods in attics Change-Id: I66f57e6ac6cf4abb350400e27f4ad8572ab15f7d (cherry picked from commit 4c30cf0b9f91e5d054627b48acfdbbae8611abee)
The vTR service is designed to perform a connectivity test in place of the subscriber. It will save you time and costs of sending a truck to the subscriber premises to perform the same kind of test.
To onboard this service in your system, you can execute the onboard-vtr.yaml playbook, using this command:
ansible-playbook -i /etc/maas/ansible/pod-inventory --extra-vars=@/opt/cord/build/genconfig/config.yml onboard-vtr-playbook.yaml