Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No test environment #6

Closed
abgordon opened this issue Feb 12, 2020 · 3 comments · Fixed by #14
Closed

No test environment #6

abgordon opened this issue Feb 12, 2020 · 3 comments · Fixed by #14

Comments

@abgordon
Copy link
Collaborator

abgordon commented Feb 12, 2020

Reading #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

@abgordon
Copy link
Collaborator Author

Resolved by #14

@abgordon
Copy link
Collaborator Author

@bediger4000 If you have a moment to run the setup-minikube script, i'd appreciate any feedback

@abgordon
Copy link
Collaborator Author

Docker compose would probably be the best tool for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant