[OOR-Devel] Vagrant setup

[Lori Jakab]

Happy New Year OOR Community!

I just pushed some more Vagrant work into the testing branch [3], this
time Android related.

A new VM allows an Android APK to be built purely from the command
line, without the use of Android Studio. This is especially useful if
you work on the core code, not the Android specific bits, but want to
test the changes on a phone. It can also be a first step on the road
automating the release process.

Let me know if you run into any kind of issues with this setup.

Regards,
-Lori

[3] https://github.com/OpenOverlayRouter/oor/commit/28b323e142040fbb3b517c021a79272ec224bff0

On Wed, Dec 13, 2017 at 3:38 PM, Lori Jakab <lorand.jakab at gmail.com> wrote:
> On Tue, Dec 12, 2017 at 11:43 AM, Lori Jakab <lorand.jakab at gmail.com> wrote:
>
> [...]
>
>> My plan is to also create a more complex Vagrant setup to automate the
>> creation of a testbed with multiple VMs with different roles (MN, xTR,
>> MS, etc.) so different scenarios can be tested quickly,
>
> As a first step I committed [0] work to enable a testbed with three
> nodes: an OOR based map server, pre-provisioned with two /32 EID
> prefixes, and two mobile nodes, each registering one of those
> prefixes. When Vagrant finishes provisioning, OOR is running on all
> nodes with the correct configuration file, so one can just ssh in, and
> ping one node from the other (and a ping command is saved to the
> pre-provisioned .bash_history file, to make everything even quicker).
> It is also possible to monitor traffic with the preinstalled TShark.
> See the documentation [1] for full details.
>
> I captured ideas for future development of this setup in a TODO file [2].
>
> -Lori
>
> [0] https://github.com/OpenOverlayRouter/oor/commit/b5e3cc8df708b5050deb3d9e6724df46a5d31b2d
> [1] https://github.com/OpenOverlayRouter/oor/blob/testing/vagrant/README.md
> [2] https://github.com/OpenOverlayRouter/oor/blob/testing/vagrant/TODO.md