Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for the creation of a GNS3 appliance file #1

Merged
merged 1 commit into from
Oct 2, 2019

Conversation

mikelazar
Copy link
Owner

- 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 sonin-vs.img (SONiC Virtual Switch).

The appliance file (and sonic-vs.img file) can subsequently be imported into a GNS3 simulation environment.

The script sonic-gns3a.sh creates a GNS3 appliance flle, that points to a sonin-vs.img (SONiC Virtual Switch).

The appliance file (and sonic-vs.img file) can subsequently be imported into a GNS3 simulation environment.
@mikelazar mikelazar merged commit c959ee3 into master Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant