Hi this is Alexis from weaveworks, just to say you can see how we support kubeflow here - https://www.weave.works/blog/kubeflow-and-weave-cloud
Hi, alexis richardson here from weaveworks. We have a berlin office and would love to hire people who want to work in our main areas. See https://www.weave.works/company/hiring/
to elaborate for @hueving @mugsie et al., consider that OpenStack is organised around Nova, the scheduler++ that is at the heart of any OpenStack deployment. If the CNCF was "like OpenStack" then it could mandate that…
Yes we do allow competing APIs. You said it yourself in another comment on here: "It's never blatant, it's always calls for seemingly good things like extra pluggable points to make sure we don't favor particular…
Projects can do what they like. We believe that users, communities, market pressures, and so on, will drive good outcomes here. For example to date, all projects have worked to interoperate of their own volition. No…
"how are the end user groups requirements put forward? what mechanisms is there to ensure developers work on the defined priorities?" --> projects are run by their leads, they are not told what to work on. In this…
Hi, I'm alexis richardson and chair of the TOC for CNCF. The answer is YES we allow competing implementations.
What is a small packet here?
(weaveworks person here) If you check out the PDF that fons posted above, http://rp.delaat.net/2015-2016/p50/report.pdf, then you will see pretty extensive testing showing that Weave Net, flannel, and Docker Networking…
No. http://www.weave.works/weave-fast-datapath/
+1 to @jbeda, but let me offer some comments for the avoidance of possible confusion among potential Weave users. Weave aims to deliver a completely portable network. In other words if you create an application using…
Hi this is Alexis from weaveworks, just to say you can see how we support kubeflow here - https://www.weave.works/blog/kubeflow-and-weave-cloud
Hi, alexis richardson here from weaveworks. We have a berlin office and would love to hire people who want to work in our main areas. See https://www.weave.works/company/hiring/
to elaborate for @hueving @mugsie et al., consider that OpenStack is organised around Nova, the scheduler++ that is at the heart of any OpenStack deployment. If the CNCF was "like OpenStack" then it could mandate that…
Yes we do allow competing APIs. You said it yourself in another comment on here: "It's never blatant, it's always calls for seemingly good things like extra pluggable points to make sure we don't favor particular…
Projects can do what they like. We believe that users, communities, market pressures, and so on, will drive good outcomes here. For example to date, all projects have worked to interoperate of their own volition. No…
"how are the end user groups requirements put forward? what mechanisms is there to ensure developers work on the defined priorities?" --> projects are run by their leads, they are not told what to work on. In this…
Hi, I'm alexis richardson and chair of the TOC for CNCF. The answer is YES we allow competing implementations.
What is a small packet here?
(weaveworks person here) If you check out the PDF that fons posted above, http://rp.delaat.net/2015-2016/p50/report.pdf, then you will see pretty extensive testing showing that Weave Net, flannel, and Docker Networking…
No. http://www.weave.works/weave-fast-datapath/
+1 to @jbeda, but let me offer some comments for the avoidance of possible confusion among potential Weave users. Weave aims to deliver a completely portable network. In other words if you create an application using…