Page History

...

1. Follow steps 1. and 2. in The Packet Optical Dev Environment - ONOS.
   
   

2. Set up cells. Each domain should have a different controller cluster controlling it, and therefore, have separate cell configurations. For example, for two instances at addresses 192.168.64.45 and 192.168.64.46 (the metro core and CO #1), the cell files are:
   optical layer - core domain:

   Code Block
   language text
   # cell for core domain (optical network) export ONOS_NIC=192.168.64.* export OC1="192.168.64.45" export OCI=$OC1 export OCN="192.168.64.43" export ONOS_APPS="drivers,drivers.optical,openflow,proxyarp,optical"

   packet layer - central office 1:

   Code Block
   language text
   # cell for central office domains (packet networks) export ONOS_NIC=192.168.64.* export OC1="192.168.64.46" export OCI=$OC1 export OCN="192.168.64.43" export ONOS_APPS="drivers,openflow,segmentrouting"

   The remaining COs would have cell files similar to that of CO 1 above, but with OC1 set to their own deploy target host address.

    

3. Apply the cells to each terminal.
   
   

4. Prepare component configurations for each CO's virtual big switch application. The file for CO 1 contains the following:

   Code Block
   language text
   { "org.onosproject.ecord.co.BigSwitchDeviceProvider": { "providerScheme": "bigswitch1", "providerId": "org.onosproject.bigswitch", "remoteUri": "grpc://192.168.64.45:11984", "metroIp": "192.168.64.45" } }

   Note that the value for "providerScheme" should be different for each CO (here, the convention is bigswitchN for CO N). This scheme will be used as part of the virtual switch's device URI/ID. Set the files aside in a known location. ${CFG_LOC} refers to this location in the remainder of this page.

...