Reading https://github.com/Comcast/Ravel/issues/5 - a user outside of Comcast doesn't have a good test environment for dev work, let alone benchmarking anything. We need a set of examples around what a configmap for a VIP looks like, and how to set up a dev environment - perhaps a host-networked coreos container / VM that can advertise a route on a local network, routing to minikube, to emulate an in-the-wild Ravel setup
Ideally, a bootstrap script could run make dev-env and set everything up. Configmap creation is left to the consumer of Ravel - the way I see it, cm's are just an interface you need to implement however you see fit to provide Ravel's state
This will likely only work on linux as net=host is not supported on mac, but it may work running as a local binary - cross-compatibility on ipvsadm remains to be tested
Reading https://github.com/Comcast/Ravel/issues/5 - a user outside of Comcast doesn't have a good test environment for dev work, let alone benchmarking anything. We need a set of examples around what a configmap for a VIP looks like, and how to set up a dev environment - perhaps a host-networked coreos container / VM that can advertise a route on a local network, routing to minikube, to emulate an in-the-wild Ravel setup
Ideally, a bootstrap script could run
make dev-env
and set everything up. Configmap creation is left to the consumer of Ravel - the way I see it, cm's are just an interface you need to implement however you see fit to provide Ravel's stateThis will likely only work on linux as
net=host
is not supported on mac, but it may work running as a local binary - cross-compatibility onipvsadm
remains to be tested