4 ms·

I REALLY wish that Clocker would support (and document how to use) something besides Weave - weave is intolerably slow for anything that requires some kind of m

I REALLY wish that Clocker would support (and document how to use) something besides Weave - weave is intolerably slow for anything that requires some kind of more serious throughput between nodes. It is very, very unfortunate Clocker doesn't document how to not use Weave (for example, simply use whatever is already in place) as the rest of Clocker rocks, and the seemingly hard dependency on Weave makes it un-deployable for serious production use. I did pop into their IRc channel a few times with a question around this, but over the space of 3 days all activity on the IRC channel was tumbleweed and crickets..

weavenetwork 12y ago
What throughput do you need, on a per-host basis?
- mdekkers 12y ago
  about 8Gbits/sec
  - weavenetwork 12y ago
    cripes. on each host? what kind of physical network are you using, and how many containers per host? how many hosts? let me know if I should email about this instead.
  - techdragon 12y ago
    Wow. Is that a full 8Gbit/sec of data per host or a logical 8Gbit/sec of raw frames? Either way, you're an ideal candidate for closed beta access to the performance focused container networking tools my startup is developing. I can contact you via email if you're interested.
    - mdekkers 12y ago
      happy to have a chat - mdekkers at cynaptic dot eu
grkvlt 12y ago
The latest version of Clocker does support Calico as well, now! But I agree there isn't much in the way of documentation on how to change this. I updated the README and the main page at http://clocker.io/ http://clocker.io/ to reflect the changes in Clocker 0.8.1 but it's not immediately obvious. Try this: ./bin/clocker.sh jclouds:provider:region calico
- mdekkers 12y ago
  that's great, thanks for answering! I have not yet looked at Calico - I have OVS-VXLAN between my worker nodes, which is a simple solution that works great. Is it possible to say "use whatever is already in place"?
  - grkvlt 12y ago
    It may be possible by writing a slightly modified YAML file for the Clocker blueprint itself. To avoid dragging this thread further off-topic, please drop me a line at the email address in my profile, and I can probably help you.
    - mdekkers 12y ago
      awesome, thanks!!

weavenetwork 12y ago

What throughput do you need, on a per-host basis?

mdekkers 12y ago
about 8Gbits/sec
- weavenetwork 12y ago
  cripes. on each host? what kind of physical network are you using, and how many containers per host? how many hosts? let me know if I should email about this instead.
- techdragon 12y ago
  Wow. Is that a full 8Gbit/sec of data per host or a logical 8Gbit/sec of raw frames? Either way, you're an ideal candidate for closed beta access to the performance focused container networking tools my startup is developing. I can contact you via email if you're interested.
  - mdekkers 12y ago
    happy to have a chat - mdekkers at cynaptic dot eu

grkvlt 12y ago

The latest version of Clocker does support Calico as well, now! But I agree there isn't much in the way of documentation on how to change this. I updated the README and the main page at http://clocker.io/ http://clocker.io/ to reflect the changes in Clocker 0.8.1 but it's not immediately obvious. Try this: ./bin/clocker.sh jclouds:provider:region calico

mdekkers 12y ago
that's great, thanks for answering! I have not yet looked at Calico - I have OVS-VXLAN between my worker nodes, which is a simple solution that works great. Is it possible to say "use whatever is already in place"?
- grkvlt 12y ago
  It may be possible by writing a slightly modified YAML file for the Clocker blueprint itself. To avoid dragging this thread further off-topic, please drop me a line at the email address in my profile, and I can probably help you.
  - mdekkers 12y ago
    awesome, thanks!!