You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow my prev issue #1, I found it's too hard to contribute k8s/etcd code in this official repo [Still have some compile/link error in your repo]. So I create a new repo to hack it and verify some idea. Since someone may be interested in it, I post some progress at here.
k8s-freeflow
TO-DO List
IP Hunter: write changed nodes and map(vip, pip) into ETCD periodically CODE
GoogleTest PASS: ETCD V3 API's watch mode for ffrouter CODE
The Watch API provides an event-based interface for asynchronously monitoring changes to keys. An etcd3 watch waits for changes to keys by continuously watching from a given revision, either current or historical, and streams key updates back to the client. https://coreos.com/etcd/docs/latest/learning/api.html
GoogleTest PASS: ETCD V3 API's range mode for ffrouter
GoogleTest PASS: ETCD V2 API's put mode for ffrouter
new ffrouter depends on curl, base64 and jsoncpp. CODE
Follow my prev issue #1, I found it's too hard to contribute k8s/etcd code in this official repo [Still have some compile/link error in your repo]. So I create a new repo to hack it and verify some idea. Since someone may be interested in it, I post some progress at here.
k8s-freeflow
TO-DO List
IP Hunter: write changed nodes and map(vip, pip) into ETCD periodically CODE
IP Hunter's Docker Image CODE
Have yet Test ffrouter update HOST_LIST and vip_map via RESTful API of ETCD's Watch mode periodically**. CODE
ffouter docker image
client docker image
GoogleTest PASS: ETCD V3 API's watch mode for ffrouter CODE
The Watch API provides an event-based interface for asynchronously monitoring changes to keys. An etcd3 watch waits for changes to keys by continuously watching from a given revision, either current or historical, and streams key updates back to the client. https://coreos.com/etcd/docs/latest/learning/api.html
GoogleTest PASS: ETCD V3 API's range mode for ffrouter
GoogleTest PASS: ETCD V2 API's put mode for ffrouter
new ffrouter depends on curl, base64 and jsoncpp. CODE
the process of compilation passed. CODE
testing new ffouter with IP hunter and fix bug.
IP Hunter -> Kubernetes POD: ip_hunter_pod.yaml
ffrouter -> Kubernetes Daemonset: ffrouter_daemonset.yaml
Benchmark: baseline Kubeflow
The text was updated successfully, but these errors were encountered: