[{"_1":2,"_197":-5,"_198":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_170":171},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":11,"_17":11,"_18":19},"username","isBillingDecouplingSeatCount","isSearchBoxExperimentEnabled","isAskGordonEnabled",true,"routes/_layout.r.$namespace.$reponame",{"_22":23,"_24":-5,"_25":11,"_26":11,"_27":28,"_29":30,"_31":-5,"_32":11,"_33":34,"_90":91,"_115":116,"_163":-5,"_164":11,"_165":11,"_166":11,"_167":-5,"_168":169},"canonicalUrl","https://hub.docker.com/r/nlnetlabs/gantry/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","nlnetlabs","reponame","gantry","cloudBuildSource","isAutobuildsAvailable","repo",{"_35":36,"_45":46,"_48":49,"_50":51,"_52":11,"_53":54,"_55":56,"_57":58,"_38":30,"_27":28,"_60":61,"_62":47,"_63":64,"_65":66,"_67":68,"_69":-5,"_70":64,"_71":72,"_73":11,"_74":28,"_75":76,"_81":11,"_82":83,"_87":28,"_88":89},"categories",[37,42],{"_38":39,"_40":41},"name","Networking","slug","networking",{"_38":43,"_40":44},"Integration & delivery","integration-and-delivery","content_types",[47],"image","date_registered","2019-04-04T08:35:09.002919Z","description","A tool for deploying and testing network routers in the cloud.","is_private","last_updated","2020-10-09T12:53:44.845269Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[59],"application/vnd.docker.container.image.v1+json","pull_count",3534,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","[![Travis CI status badge](https://travis-ci.com/NLnetLabs/gantry.svg?branch=master)](https://travis-ci.com/NLnetLabs/gantry)\n\n# Gantry\n\n> _a structure built on a rocket launch pad to facilitate assembly and servicing_\n\nNLnet Labs Gantry is a tool for deploying and testing network routers in the cloud, built to support the [NLnet Labs Routinator](https://www.nlnetlabs.nl/projects/rpki/routinator/) project.\n\nThis project exists to answer the question \"Does the Routinator work with real routers?\" and to make it easy to keep checking that answer as the Routinator grows and the set of test routers and router versions increases.\n\n## Here be dragons!\n\nWarning: This is very definitely an early work-in-progress, it has bugs, it's incomplete, and running and hacking on it will require effort. This is not yet for the faint of heart.\n\n## Quick Start\n\nAssuming you are running on Ubuntu 18.10 and have Docker, a DigitalOcean account, and a private Docker registry containing one or more supported virtual router images with any necessary licenses, then:\n\n```\n$ cp gantry.cfg.example gantry.cfg\n$ vi gantry.cfg # edit the values to match your setup\n$ ./gantry deploy routinator\n$ ./gantry logs routinator\n...\nRTR: Listening on 0.0.0.0:3323.\n$ ./gantry deploy vr-sros:16.0.R6 # or the router that you wish to deploy\n```\n\nSit back and drink a coffee while the rocket launches!\n\n```\n...\nTASK [ON ROUTER vr-sros-16.0.R6 @ 134.209.202.139 : WAIT FOR CONNECTION ESTABLISHED ...\nok: [134.209.202.139 ]\n\nTASK [debug] *********************************************************************************\nok: [134.209.202.139 ] => {\n \"result.stdout_lines\": [\n [\n \"===============================================================================\",\n \"Rpki Session Information\",\n \"===============================================================================\",\n \"IP Address : 134.209.198.136\",\n \"-------------------------------------------------------------------------------\",\n \"Port : 3323 Oper State : established\",\n \"UpTime : 0d 00:00:02 Flaps : 0\",\n \"Active IPv4 records: 6986 Active IPv6 records: 1258\",\n \"===============================================================================\",\n \"No. of Rpki-Sessions : 1\",\n \"===============================================================================\"\n ]\n ]\n}\n```\n\n## Configuring and testing with data directory Ansible fragments\n\nGantry can execute Ansible based router post-deployment configuration steps, and optional test suites, using Ansible fragments that you supply in the Gantry data directory.\n\nTest execution takes place inside the Gantry Docker container and so only Ansible playbooks accessible to the container via the Gantry data directory can be executed. By default the host directory `/tmp/gantry` is mapped into the container. You can override this location using the `--data-dir ` command line option.\n\n- Any `config-*.yml` files in the Gantry data directory will be included as task sets to be executed post deployment.\n- All `test-*.yml` files will be executed by `./gantry test all`.\n- Individual playbooks in the Gantry data directory can be executed using `./gantry test `, .e.g `./gantry test test-compare-vrps`.\n\n## Upgrading\n\nWhen using the `./gantry` wrapper script the Gantry Docker image is fetched the first time you use it. To upgrade it after that, assuming that a newer version of Gantry has been built over on [Docker Hub](https://hub.docker.com/r/nlnetlabs/gantry/builds), you can issue the following command:\n\n```\n$ ./gantry upgrade\nlatest: Pulling from nlnetlabs/gantry\nDigest: sha256:16c8559eed1543a4cbc8e3324aae131cb0e6246df0668b41bb13dbd8a99c6c40\nStatus: Downloaded newer image for nlnetlabs/gantry:latest\n```\n\n## Preparing router images\n\nGantry contains support for building and publishing router images to a private Docker registry. Assuming that you have in your possession the router image file and any required license file you can use Gantry to build and publish it.\n\nBelow is an example of how to build and publish a Nokia SROS 16.0.R6 router image:\n\n```\n$ mkdir /tmp/gantry\n$ cp /path/to/your/19.0.R6/sros-vm.qcow2 /tmp/gantry/sros-19.0.R6.qcow2\n$ cp /path/to/your/19.0.R6/license.txt /tmp/gantry/sros-19.0.R6.qcow2.license\n$ ./gantry registry publish\n2019-12-09 11:05:21 +0000: Publishing builds a vrnetlab router image and publishes it to your private Docker registry.\n2019-12-09 11:05:21 +0000: The router images and licenses must be supplied by you.\n2019-12-09 11:05:21 +0000: Do you wish to proceed? [y/N] y\n2019-12-09 11:05:22 +0000:\n2019-12-09 11:05:22 +0000: Which of the following router image types do you want to publish?\n csr\n nxos\n openwrt\n routeros\n sros\n veos\n vmx\n vqfx\n vrp\n vsr1000\n xrv\n xrv9k\n2019-12-09 11:05:22 +0000: Router type, e.g. sros: sros\n2019-12-09 11:05:23 +0000:\n2019-12-09 11:05:23 +0000: Please copy or sym link your .qcow2 router image, and optionally a .qcow2.license file, into:\n2019-12-09 11:05:23 +0000: /tmp/gantry\n2019-12-09 11:05:23 +0000:\n2019-12-09 11:05:23 +0000: Please read CAREFULLY the instructions that will be printed next on your screen.\n2019-12-09 11:05:23 +0000: If you do not name the copied/linked files correctly the build will FAIL.\n2019-12-09 11:05:23 +0000: Do you wish to proceed? [y/N] y\n2019-12-09 11:05:24 +0000:\nvrnetlab / Nokia VSR SROS\n=========================\nThis is the vrnetlab docker image for Nokia VSR / SROS.\n...\n... skip vrnetlab router specific README ...\n...\n2019-12-09 11:05:24 +0000: Do you wish to proceed? [y/N] y\n...\n... skip make and Docker build process output ...\n...\n2019-12-09 11:05:28 +0000:\n2019-12-09 11:05:29 +0000: The image build has finished. Does the following identify the image that was built?\n2019-12-09 11:05:29 +0000: vrnetlab/vr-sros:19.10.R1\n2019-12-09 11:05:29 +0000: Do you wish to proceed? [y/N] y\n...\n... skip Docker push output ...\n...\n2019-12-09 11:06:07 +0000: Done.\n```\n\n## Status\nDeployment of components to test:\n- [ ] NLnet Labs Krill\n- [x] NLnet Labs Routinator\n- [x] Nokia/Alcatel SROS 16.0.R6 virtual router\n- [x] Juniper VMX 18.2R1.9 virtual router\n- [ ] Cisco IOS XRv 9000 virtual router\n- [ ] Cisco CSR 1000 virtual router\n- [ ] Other RPKI caches (TBD)\n\nConfigure virtual routers to populate their RPKI VRP database from the Routinator:\n- [x] Nokia/Alcatel SROS 16.0.R6\n- [x] Juniper VMX 18.2R1.9\n- [ ] Cisco IOS XRv 9000 virtual router\n- [ ] Cisco CSR 1000 virtual router\n- [ ] Configure virtual routers to populate their RPKI VRP database from other RPKI caches (TBD)\n- [ ] Configure RPKI caches to use Krill as their data source\n\nTest scenarios:\n- [x] Symmetric diff of virtual router VRP database to that of the VRP source (done with Routinator)\n- [ ] Others (TBD)\n\n## Architecture\n\nGantry depends heavily on the [vrnetlab](https://github.com/plajjan/vrnetlab) project which is used to build the virtual router Docker images that are deployed and tested. Currently the vr-sros image build is slightly patched to enable outbound connectivity to the Routinator. With a better understanding of vrnetlab and routers the patch might turn out to be unnecessary, otherwise I would like to see if it is something that makes sense to somehow contribute pack to the vrnetlab project.\n\nInfrastructure is spun up using Docker Machine and DigitalOcean.\n\nRouter images are provisioned using Docker Machine, Docker and Ansible.\n\nTerraform is used to deploy a private Docker registry to store the router images. The [reg](https://github.com/genuinetools/reg) tool is used to work with the registry.\n\nDocker, Docker Hub and Bash are used to wrap the project up and make it easy to use. The \"simple\" Bash wrapper script has already grown beyond the initial expectation and is overdue for a rewrite in Python.\n\nThe manner in which different routers with different VM size requirements and post-deployment setup commands is supported will likely evolve, at present it's a bit of an Ansible/Docker/Bash hack.\n\n## Help\n\nFor questions, suggestions, and contributions please use GitHub issues and pull requests.\n\nConsulting the Gantry `--help` output is a good way to get a feel for what Gantry can do and how to do it:\n\n```\n$ ./gantry --help\nGantry: \"a structure built on a rocket launch pad to facilitate assembly and servicing\"\n\nNLnet Labs Gantry is a tool for deploying and testing network routers in the cloud, built to support the NLnet Labs Routinator project.\n\nUsage: gantry help|--help\n\nComponent management commands:\n gantry deploy [..] [--region ] \n gantry docker ..commands..\n gantry exec ..commands..\n gantry ip \n gantry logs [--follow]\n gantry ssh [--host]\n gantry status\n gantry undeploy [..] [--force]\n\nDocker registry commands:\n gantry registry ls|deploy|publish\n gantry registry rm /:\n\nTest suite commands:\n gantry test |all []\n\nWrapper commands:\n gantry shell\n gantry upgrade\n\nWrapper options:\n gantry --data-dir \n gantry --version\n\nWhere COMPONENT can be one of: (deploy and undeploy also accept special component 'all')\n COMPONENT VENDOR\n routinator NLnet Labs\n vr-csr:16.09.02 Cisco CSR1000v\n vr-sros:16.0.R6 Nokia/Alcatel SROS\n vr-vmx:18.2R1.9 Juniper vMX\n```\n\n_Note: The list of COMPONENTs shown is the set for which specific playbooks exist in the `playbooks/` directory. You will need the appropriate virtual router image published in your Docker registry in order to actually deploy one of these routers._\n\n## Upgrading the Routinator version\n\nThe Routinator image is pulled from the private Docker registry, NOT from the public registry.\n\nYou can upgrade it like so:\n\n```\n$ docker pull nlnetlabs/routinator:latest\n$ docker tag nlnetlabs/routinator:latest docker-reg.do.nlnetlabs.nl/nlnetlabs/routinator:latest\n$ docker push /nlnetlabs/routinator:latest\n```\n\nThe registry FQDN and login details (you might need to do `docker login` before you can push) can be found in your `gantry.cfg` file.\n\n## Hacking\n\nIf you know what you are doing and want to take full control you can dive into the Gantry wrapper container shell prompt:\n\n```\n$ ./gantry shell\nEntering shell mode..\n\nroot@a18e60b24e33:/opt/nlnetlabs/gantry# \n```\n\n## TO DO\n\nFinish this README.\n","has_starred","hub_user","immutable_tags_settings",{"_77":11,"_78":79},"enabled","rules",[80],".*","is_automated","permissions",{"_84":19,"_85":11,"_86":11},"read","write","admin","user","storage_size",3656316904,"orgData",{"_92":93,"_94":95,"_96":97,"_98":28,"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":110,"_111":104,"_112":113,"_114":19},"id","98dd59ddd218413e9181258e64d84461","uuid","98dd59dd-d218-413e-9181-258e64d84461","type","organization","orgname","full_name","NLnet Labs","location","Amsterdam","company","","profile_url","https://nlnetlabs.nl","date_joined","2018-11-22T08:55:02.114424Z","gravatar_url","https://www.gravatar.com/avatar/da73ac5719ebf33be95e4b44d72c2c3a?s=80&r=g&d=mm","gravatar_email","badge","open_source","is_active","recentTags",[117,153],{"_118":47,"_119":120,"_121":122,"_92":123,"_124":125,"_53":142,"_143":120,"_144":28,"_145":59,"_38":146,"_147":148,"_149":133,"_150":142,"_151":68,"_152":19},"content_type","creator",4669854,"full_size",439714475,51856713,"images",[126],{"_127":128,"_129":130,"_131":104,"_132":133,"_134":135,"_136":137,"_138":104,"_139":-5,"_140":122,"_65":68,"_141":-5},"architecture","amd64","digest","sha256:d1698f5c5cbf5455ac43f9e64ba4aa8fe4c3a7bdf05be0e6cb69f92da3e9c2c1","features","last_pulled","2026-07-15T00:29:19.265868778Z","last_pushed","2020-10-09T12:53:45Z","os","linux","os_features","os_version","size","variant","2020-10-09T12:53:44.554554Z","last_updater","last_updater_username","media_type","latest","repository",6929682,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_118":47,"_119":120,"_121":154,"_92":155,"_124":156,"_53":161,"_143":120,"_144":28,"_145":59,"_38":162,"_147":148,"_149":159,"_150":161,"_151":68,"_152":19},387635328,55071097,[157],{"_127":128,"_129":158,"_131":104,"_132":159,"_134":160,"_136":137,"_138":104,"_139":-5,"_140":154,"_65":68,"_141":-5},"sha256:d67cb38006ce71d9d966aea591ecfeb8a4720184428ea826f15cd1101e64b255","2026-07-14T07:34:05.093049837Z","2019-05-09T12:59:08Z","2019-05-09T12:59:07.755461Z","v0.1-alpha","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_33":172,"_181":182,"_168":195,"_196":11},{"_35":173,"_45":176,"_48":49,"_50":51,"_52":11,"_53":54,"_55":56,"_57":177,"_38":30,"_27":28,"_60":61,"_62":47,"_63":64,"_65":66,"_67":68,"_69":-5,"_70":64,"_71":72,"_73":11,"_74":28,"_75":178,"_81":11,"_82":180,"_87":28,"_88":89},[174,175],{"_38":39,"_40":41},{"_38":43,"_40":44},[47],[59],{"_77":11,"_78":179},[80],{"_84":19,"_85":11,"_86":11},"tags",{"_183":184,"_185":-5,"_186":-5,"_187":188},"count",2,"next","previous","results",[189,192],{"_118":47,"_119":120,"_121":122,"_92":123,"_124":190,"_53":142,"_143":120,"_144":28,"_145":59,"_38":146,"_147":148,"_149":133,"_150":142,"_151":68,"_152":19},[191],{"_127":128,"_129":130,"_131":104,"_132":133,"_134":135,"_136":137,"_138":104,"_139":-5,"_140":122,"_65":68,"_141":-5},{"_118":47,"_119":120,"_121":154,"_92":155,"_124":193,"_53":161,"_143":120,"_144":28,"_145":59,"_38":162,"_147":148,"_149":159,"_150":161,"_151":68,"_152":19},[194],{"_127":128,"_129":158,"_131":104,"_132":159,"_134":160,"_136":137,"_138":104,"_139":-5,"_140":154,"_65":68,"_141":-5},[],"canDeleteTags","actionData","errors"]

nlnetlabs/gantry

Tags for nlnetlabs/gantry