Create SONiC VS GNS3 appliance file #3553
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
Added a script. The script is executed offline (does not impact the build or the SONIC target)
- How I did it
Generate a standard GNS3 appliance template.
- How to verify it
Execute the script:
./sonic-gns3a.sh -r MyRelease -b <store_path>/sonic-vs.image"
Import the resulting GNS3 app file into a GNS3 environment
Please refer to the file README.gns3.md for details (and the online GNS3 documentation)
- Description for the changelog
The script sonic-gns3a.sh creates a GNS3 appliance flle, that points to a sonic-vs.img (SONiC Virtual Switch). The image must be obtained separately (e.g. from SONiC build)
The appliance file (and sonic-vs.img file) can subsequently be imported into a GNS3 simulation environment.
- A picture of a cute animal (not mandatory but encouraged)
N/A