Closed abessiari closed 3 months ago
Sample config. stitch_with
supports more than network.
resource:
- network:
- cnet:
provider: '{{cloudlab.cloudlab_provider }}'
layer3: "{{ layer3.my_layer }}"
- fabric_network:
provider: '{{ fabric.fabric_provider }}'
layer3: "{{ layer3.my_layer }}"
stitch_with:
- network: '{{ network.cnet }}'
stitch_option:
device_name: CloudLab-Clemson
- network: '{{ network.chi_network }}'
stitch_option:
site: '{{ var.site }}'
- chi_network:
provider: '{{ chi.chi_provider }}'
name: stitch_net
layer3: "{{ layer3.my_layer }}"
Sample config that is also supported.
resource:
- network:
- cnet:
provider: '{{cloudlab.cloudlab_provider }}'
layer3: "{{ layer3.my_layer }}"
stitch_with:
- network: '{{ network.fabric_network }}'
stitch_option:
device_name: CloudLab-Clemson
- fabric_network:
provider: '{{ fabric.fabric_provider }}'
layer3: "{{ layer3.my_layer }}"
stitch_with:
- network: '{{ network.chi_network }}'
stitch_option:
site: '{{ var.site }}'
- chi_network:
provider: '{{ chi.chi_provider }}'
name: stitch_net
layer3: "{{ layer3.my_layer }}"
Work in progress.
Phase 2 is Done. Verified that dataplane works between cloudlab nodes and fabric nodes. Now phase 3 begins. Test and Make sure old fabfed config files still work.
Done
Use Case: Chameleon nodes communicating with Cloudlab nodes via fabric L2STS stitched network.
Old Way Of Stitching Will Still Be Supported. The config sample below is here for convenience. So that we can compare it with the new config files that support multiple stitch networks.