Rare project developers

[Antoni Przygienda <>]

Sorry, I cannot drop you vmx images easily. Product not supported, only internal stuff, images not supposed to go out and I’m not sure you’ll be able to run 22.x stuff anyway, tons stuff has changed since we supported the product.

 

Kithara is trivial, just grab a standard ub18 container, throw your stuff onto it, snapshot the image and give it to kithara on a lab. To test rift stuff properly you’ll be building pretty soon lots tooling yourself to bring up CLOS networks and then realize you cannot run it with VMs at any reasonable size and end up with containers anyway (or namespaces as Bruno’s code can partially do but that’s also super limited). RIFT only starts to really cranck once you’re at couple hundred nodes at least 😉

 

Very simplest stuff is to run within my Jason environ just like Bruno does, there is no virtualization/data plane at all but you can build very large topologies within seconds. We could easily extend it from “don’t run the passive nodes” to “run only nodes with this simulation-partition-id” if you want and then can mix all implementations in any fashion …

 

 

If you need kithara help I can hook you up directly with one of the authors, I know them well, they’ll be more than happy to bring freerouter in

 

--t ony

 

From: mc36 <>
Date: Saturday, 17 December 2022 at 16:19
To: Antoni Przygienda <>, <>
Subject: Re: [rare-dev] FW: rift in freerouter

[External Email. Be cautious of content]


On 12/17/22 16:18, mc36 wrote:
> that way i'm pretty sure will work and i already have a rift build for that vmx from 2020-10-xx...
surely a typo, 2022

Juniper Business Use Only