+1 for "container-in-vm"
On Fri, Nov 6, 2015 at 10:48 PM, Antoni Segura Puimedon <
toni+openstac...@midokura.com> wrote:
>
>
> On Fri, Nov 6, 2015 at 1:20 PM, Baohua Yang wrote:
>
>> It does cause confusing by calling container-inside-vm as nested
>> container.
>>
>> The
It does cause confusing by calling container-inside-vm as nested container.
The "nested" term in container area usually means
container-inside-container.
we may refer this (container-inside-vm) explicitly as vm-holding container.
On Fri, Nov 6, 2015 at 12:13 PM, Vikas Choudhary
On Fri, Nov 6, 2015 at 1:20 PM, Baohua Yang wrote:
> It does cause confusing by calling container-inside-vm as nested
> container.
>
> The "nested" term in container area usually means
> container-inside-container.
>
I try to always put it as VM-nested container. But I
The current OVS binding proposals are not for nested containers.
I am not sure if you are asking about that case or about the nested
containers inside a VM case.
For the nested containers, we will use Neutron solutions that support this
kind of configuration, for example
if you look at OVN you
2015-11-05 21:30 GMT+09:00 Gal Sagie :
> The current OVS binding proposals are not for nested containers.
> I am not sure if you are asking about that case or about the nested
> containers inside a VM case.
>
> For the nested containers, we will use Neutron solutions that
@Gal, I was asking about "container in nova vm" case.
Not sure if you were referring to this case as nested containers case. I
guess nested containers case would be "containers inside containers" and
this could be hosted on nova vm and nova bm node. Is my understanding
correct?
Thanks Gal and
Hi All,
I would appreciate inputs on following queries:
1. Are we assuming nova bm nodes to be docker host for now?
If Not:
- Assuming nova vm as docker host and ovs as networking plugin:
This line is from the etherpad[1], "Eachdriver would have an
executable that receives