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

[Converters] Automate migration from Propritery vendors #7

Open
nrshrivatsan opened this issue Sep 23, 2018 · 2 comments
Open

[Converters] Automate migration from Propritery vendors #7

nrshrivatsan opened this issue Sep 23, 2018 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@nrshrivatsan
Copy link

nrshrivatsan commented Sep 23, 2018

TL;DR

Script to migrate Hardware Load Balancers' routing rules into EnvoyConfigs

Why

  • Potential users of Envoy need to migrate legacy systems from Proprietary vendors
  • Envoy's Control Plane APIs are awesome, but seamless migration from legacy to Software Layer-7 Proxies is expensive and cost-inhibiting
  • Open automation tools to migrate from Proprietary DSLs into Envoy config syntax could save a lot of time for Envoy Users

What

  • Proprietary vendors have open specs
  • Create a syntax tree parser to migrate from a vendor's DSL into Envoy config
  • Provide automated validation scripts to validate the conversion

References

@mattklein123 mattklein123 added the enhancement New feature or request label Sep 23, 2018
@htuch
Copy link
Member

htuch commented Sep 23, 2018

@nrshrivatsan agreed that this would be useful. Do you have plans to contribute here or should we mark this as "help wanted"?

@nrshrivatsan
Copy link
Author

@htuch - Help wanted.

PS - I will check with our engineers and get back if this could be open-sourced.

@htuch htuch added the help wanted Extra attention is needed label Sep 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants