Feat/add vagrant vm #1113
Open
Feat/add vagrant vm #1113
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change was made to reduce writes to modern SSDs as storage and bandwidth is rather cheap. Still, this provides backwards compatibility.
14109e4 to
b1d0d8a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As stated in #1099 i thought about providing a Vagrantfile to make it easier to experiment with Mininet.
I could reproduce many bugs or check multiple other issues with the help of a simple
vagrant destroy -f; vagrant up; vagrant sshand had a new, clean VM within seconds.Also other users are running Mininet in a Vagrant VM (see username in the shell prompt #892 and #467 (comment)).
I've also included a provisioning file, unsure if this should be included by default tho, as it installs Mininet from scratch.
We could also use this provisioning script to generate upstream Vagrant boxes so users can simply pull the premade Vagrant box instead of building it on their local machines.
I have read through #251 and i think Vagrant has improved massively since back then.
The base box i chose runs on VirtualBox, libvirt, parallels, VMware and hyper-v, so i guess this allows for way more flexibility than the old image.
Also, this is no cloud image, yet has no graphical interface, so i could also install a GUI if necessary for new users.
So far, this is only tested with the libvirt and VirtualBox providers.
@lantz