| commit | b5a1a0ae0b2785698d49ebf48eef0fc042caa5b3 | [log] [tgz] |
|---|---|---|
| author | Pingping Lin <pingping@onlab.us> | Thu Sep 08 01:14:48 2016 +0000 |
| committer | Pingping Lin <pingping@onlab.us> | Thu Sep 08 01:14:56 2016 +0000 |
| tree | bb0e73f84c41a3ccf1110e61a9be406e88554b17 | |
| parent | c3d88009843e70c4dc16a128522433d7e50c2523 [diff] |
Add vsg,vrouter relative code for short term
(1) once onos synchronizer does not depend on vsg and vrouter,
we should remove vsg and vrouter from M-CORD
(2) changed the compute node name
(3) comment the CORDSubscriber and CORDUser relative code inside setup.yaml for now,
because currently, this two objects are inside olt service.
Change-Id: Ice69e4aa22276da3e94373c0b777303d87c9a703
This repository contains service profiles. Each service profile specifies a graph of services that will be instantiated.
Notable service profiles include:
cord-pod: Standard R-CORD service stack, for both single-node-pod and multiple node pod installs.frontend: Designed for frontend development, this profile starts XOS, but does not start any synchronizers other than the onboarding synchronizer.test-standalone: Runs a test suite that tests the REST API and Tosca API.The directory common is not a service profile, but contains various common files and tools that are used by the other service profiles.