-
Notifications
You must be signed in to change notification settings - Fork 1
Fabric Scenarios.
We have a number of examples under the example directory. Here we highlight are some simple recipes that are supported as of release 1.8. They are a good place to start. For example the stitch examples below take less than two minutes.
This example can be useful for fabric users that want to provision two nodes on two different fabric sites and connect them via an L2STS fabric network service.
resource:
- node:
- wash_node:
provider: '{{ fabric.fabric_provider }}'
site: WASH
network: '{{ network.fabric_network }}'
- salt_node:
provider: '{{ fabric.fabric_provider }}'
site: SALT
network: '{{ network.fabric_network }}'
- network:
- fabric_network:
provider: '{{ fabric.fabric_provider }}'
layer3: "{{ layer3.my_layer }}"
This example can be useful for fabric users that want to provision two nodes or more nodes on the same fabric site and connect them via an L2Bridge fabric network service.
resource:
- node:
- rocky_node:
provider: '{{ fabric.fabric_provider }}'
site: WASH
count: 2
image: default_rocky_8
nic_model: NIC_Basic
flavor: {'cores': 2, 'ram': 8, 'disk': 10}
network: '{{ network.fabric_network }}'
- network:
- fabric_network:
provider: '{{ fabric.fabric_provider }}'
layer3: "{{ layer3.my_layer }}"
This example is for fabric users that want to stitch fabric to chameleon. It is a good place to start. It is kept simple as it does not provision nodes. And so the network stitching workflow takes about a minute. Nodes can always be added as needed after a a successful deployment. As of 1.8, Fabfed allows for nodes to be added and deleted by simply adding them or deleting them from the fabfed config.
- network:
- chi_network:
provider: '{{ chi.chi_provider }}'
layer3: "{{ layer3.my_layer }}"
- fabric_network:
provider: '{{ fabric.fabric_provider }}'
layer3: "{{ layer3.my_layer }}"
stitch_with: '{{ network.chi_network }}'
This example is for fabric users that want to stitch fabric to cloudlab. It is a good place to start. It is kept simple as it does not provision nodes. And so the network stitching workflow takes about a minute. Nodes can always be added as needed after a a successful deployment. As of 1.8, Fabfed allows for nodes to be added and deleted as needed.
resource:
- network:
- cnet:
provider: '{{cloudlab.cloudlab_provider }}'
layer3: "{{ layer3.my_layer }}"
- fabric_network:
provider: '{{ fabric.fabric_provider }}'
layer3: "{{ layer3.my_layer }}"
stitch_with: '{{ network.cnet }}'