Hello, I was wondering if the batman code in the kernel make batman not compatible with lxc.
Lxc are the linux containers that permit to have virtual machines with the least overhead (native speed) but those machines use the host's kernel. If you know openvz, lxc is the same technology.
It would be nice to be able to have lxc compatible with batman so as to test big networks on a single machine.
Vincent
On Wednesday 14 September 2011 18:43:36 clownix@clownix.net wrote:
Hello, I was wondering if the batman code in the kernel make batman not compatible with lxc.
Lxc are the linux containers that permit to have virtual machines with the least overhead (native speed) but those machines use the host's kernel. If you know openvz, lxc is the same technology.
It would be nice to be able to have lxc compatible with batman so as to test big networks on a single machine.
At least OpenVZ support would mean: one batman-adv instance which provides separate interfaces for the different namespaces.
We looked at it and found no useful scenario for the OpenVZ support. And your example doesn't seem to make sense for me right now. It would be one batman- adv instance which is connected to itself... not a big virtual network.
We tend to use something like kvm for big virtual network tests.
Kind regards, Sven
So, for the multiplication of machines in a big network, you confirm that batman-adv is not compatible with lxc.
However something is still not clear: with one batman-adv per namespace, would it be possible to have what you have with kvm but with lxc? The gain for this work would be only performance, the useful scenario being no other than what you have with kvm: big (independant) networks.
Thanks for your answer. Kind Regards Vincent
On Wednesday 14 September 2011 18:43:36 clownix@clownix.net wrote:
Hello, I was wondering if the batman code in the kernel make batman not compatible with lxc.
Lxc are the linux containers that permit to have virtual machines with the least overhead (native speed) but those machines use the host's kernel. If you know openvz, lxc is the same technology.
It would be nice to be able to have lxc compatible with batman so as to test big networks on a single machine.
At least OpenVZ support would mean: one batman-adv instance which provides separate interfaces for the different namespaces.
We looked at it and found no useful scenario for the OpenVZ support. And your example doesn't seem to make sense for me right now. It would be one batman- adv instance which is connected to itself... not a big virtual network.
We tend to use something like kvm for big virtual network tests.
Kind regards, Sven
On Thursday 15 September 2011 08:40:15 clownix@clownix.net wrote:
So, for the multiplication of machines in a big network, you confirm that batman-adv is not compatible with lxc.
I never said that it is not compatible with lxc
However something is still not clear: with one batman-adv per namespace, would it be possible to have what you have with kvm but with lxc?
No, this is not possible by definition. kvm == multiple batman-adv instances, batman-adv in lxc == one instance with interfaces in different namespaces.
The gain for this work would be only performance, the useful scenario being no other than what you have with kvm: big (independant) networks.
No, by definition those networks aren't independent as they share resources inside batman-adv (and many other resources).
As far as I understand: You want to create batman-adv interfaces in different namespaces without having colliding names. Feel free to submit patches for it (or enthuse some developers with spare time).
But I am still waiting for an actual usage scenario. KVM is mostly used for debugging purposes... something were we want to have separate instances which don't crash the developer machine. And I don't see the reason for having the overhead of batman-adv in all namespaces instead of a single entry/exit point.
Kind regards, Sven
All is now clear, I have no idea about how namespaces work and neither about the batman-adv instances, I am a simple user preparing for a future batman-adv demo network on a single PC. This information is what I wanted, so thanks a lot. I agree that I do not see any other usage scenario than demo-scenario.
Kind Regards Vincent
On Thursday 15 September 2011 08:40:15 clownix@clownix.net wrote:
So, for the multiplication of machines in a big network, you confirm that batman-adv is not compatible with lxc.
I never said that it is not compatible with lxc
However something is still not clear: with one batman-adv per namespace, would it be possible to have what you have with kvm but with lxc?
No, this is not possible by definition. kvm == multiple batman-adv instances, batman-adv in lxc == one instance with interfaces in different namespaces.
The gain for this work would be only performance, the useful scenario being no other than what you have with kvm: big (independant) networks.
No, by definition those networks aren't independent as they share resources inside batman-adv (and many other resources).
As far as I understand: You want to create batman-adv interfaces in different namespaces without having colliding names. Feel free to submit patches for it (or enthuse some developers with spare time).
But I am still waiting for an actual usage scenario. KVM is mostly used for debugging purposes... something were we want to have separate instances which don't crash the developer machine. And I don't see the reason for having the overhead of batman-adv in all namespaces instead of a single entry/exit point.
Kind regards, Sven
On Thursday 15 September 2011 09:39:51 clownix@clownix.net wrote:
All is now clear, I have no idea about how namespaces work and neither about the batman-adv instances, I am a simple user preparing for a future batman-adv demo network on a single PC. This information is what I wanted, so thanks a lot. I agree that I do not see any other usage scenario than demo-scenario.
Now we have at least a usage scenario :D
I don't have time right now to implement something like that at the moment. But feel free to submit a feature/wishlist in our batman-adv bug tracker and add this thread as reference. I am interested working a little bit with namespaces in the future... far, far, far future.
Kind regards, Sven
b.a.t.m.a.n@lists.open-mesh.org
-
clownix＠clownix.net -
Sven Eckelmann