search

vulcand / vulcand

Programmatic load balancer backed by Etcd
http://vulcand.readthedocs.io/
Apache License 2.0
3.08k stars 225 forks source link

[Enhancement] Export/Import settings #115

Open schmitch opened 9 years ago

schmitch commented 9 years ago

Hello, it would be great to have a export / import function of the settings so that we could create predefined settings and import them easily.

aezell commented 9 years ago

@c-schmitt When you refer to settings, do you mean configurations like hosts, upstreams, rate limits, etc? If so, would you want to import/export them via etcd, vulcanctl, or the API?

schmitch commented 9 years ago

Yeah I meant the configuration. Like Hosts, Upstreams, Rate Limits, etc.. So in case of a failure of your cluster you could easily reimport. Or maybe to bootstrap a cluster with a predefined hosts/upstreams/etc...

Importing / Exporting could be done via vulcanctl, but I think most parts could be done via etcd, vulcanctl and the API. I mean vulcanctl is just a wrapper for the API. Problematic will be Export/Import via ETCD. Especially the import.

fracklen commented 9 years ago

Which part about the import is difficult?

You can write etcd export and import (to json) in about 10 lines of ruby/python each.

That will not include ttl, version number etc. Den 12/11/2014 23.05 skrev "Schmitt Christian" notifications@github.com:

Yeah I meant the configuration. Like Hosts, Upstreams, Rate Limits, etc.. So in case of a failure of your cluster you could easily reimport. Or maybe to bootstrap a cluster with a predefined hosts/upstreams/etc...

Importing / Exporting could be done via vulcanctl, but I think most parts could be done via etcd, vulcanctl and the API. I mean vulcanctl is just a wrapper for the API. Problematic will be Export/Import via ETCD. Especially the import.

— Reply to this email directly or view it on GitHub https://github.com/mailgun/vulcand/issues/115#issuecomment-62803562.