4 | | 1) Create a stitched slice between the two AMs, with one VM/bare metal on either side, but use the `-o` option to `stitcher` to generate the request RSpecs. It places multiple rspecs in `/tmp`, one for each aggregate. |
5 | | 2) Using `omni`, delete the slice at the OpenGENI aggregate: |
| 4 | 1) Create a stitched slice between the two AMs, with one VM/bare metal on either side, but use the `-o` option to `stitcher` to generate the request RSpecs. It places multiple rspecs in `/tmp`, one for each aggregate. |
| 5 | |
| 6 | 2) Using `omni`, delete the slice at the OpenGENI aggregate: |
11 | | 3) Get the OpenGENI RSpec request from `/tmp`, which `stitcher` created, and edit it as follows: |
12 | | a) Add as many VMs as you want, but make sure they have different names and IP addresses and at least one interface. |
13 | | b) In the link section of the RSpec, add an interface for each VM. This will create a multipoint link. (OpenGENI supports multipoint links, though this might not be true for the rest of GENI). |
14 | | 4) Provision this modified VM at the OpenGENI aggregate using `omni` (not `stitcher`). |
| 12 | 3) Get the OpenGENI RSpec request from `/tmp`, which `stitcher` created, and edit it as follows: |
| 13 | a) Add as many VMs as you want, but make sure they have different names and IP addresses and at least one interface. |
| 14 | |
| 15 | b) In the link section of the RSpec, add an interface for each VM. This will create a multipoint link. (OpenGENI supports multipoint links, though this might not be true for the rest of GENI). |
| 16 | |
| 17 | 4) Provision this modified VM at the OpenGENI aggregate using `omni` (not `stitcher`). |