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/ to reflect the changes in Clocker 0.8.1 but it's not immediately obvious. Try this:
./bin/clocker.sh jclouds:provider:region calicothat'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"?
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.
awesome, thanks!!
Re:Weave is kinda slow
by weavenetwork on Thursday May 07, 2015 @07:14AM
(#9504223)
What throughput do you need, on a per-host basis?
about 8Gbits/sec
Re:Weave is kinda slow
by techdragon on Thursday May 07, 2015 @09:36AM
(#9504908)
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.
happy to have a chat - mdekkers at cynaptic dot eu
Re:Weave is kinda slow
by weavenetwork on Thursday May 07, 2015 @08:07AM
(#9504452)
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.
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..