On Thu, Mar 28, 2013 at 12:58:51PM +0800, Hongwei Fu wrote:
> We're trying to setup OVS1.4.0 within lxc.
> I'm trying to do this,
> ovs-vsctl add-br br0
> ovs-vsctl set bridge br0 datapath_type=netdev
> ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre
GRE and other tunneling mechanisms o
Hi,
We're trying to setup OVS1.4.0 within lxc.
I'm trying to do this,
ovs-vsctl add-br br0
ovs-vsctl set bridge br0 datapath_type=netdev
ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre
options:remote_ip=1.2.3.4
ovs-vsctl get Interface gre0 ofport
I get []
When I tried this on a machine u
Once we mapped the virtual NIC to particular VM, the OVS does not come into
the process( OVS usually installed in Hypervisor). All packets are directly
go through the VNIC and through the outside world. This is case with SFC (
SR-IOV) or Intel (IO-MMU) 10Gb cards.
On Wed, Mar 27, 2013 at 11:51
On Wed, Mar 27, 2013 at 11:13 AM, Kyle Mestery (kmestery)
wrote:
>
> On Mar 27, 2013, at 12:41 PM, Jesse Gross wrote:
>
>> On Wed, Mar 27, 2013 at 6:06 AM, Atam wrote:
>>> Hi all,
>>>
>>> OVS is a software solution switch as i understand. It is able to utilize
>>> offloading features of the Eth
On Mar 27, 2013, at 12:41 PM, Jesse Gross wrote:
> On Wed, Mar 27, 2013 at 6:06 AM, Atam wrote:
>> Hi all,
>>
>> OVS is a software solution switch as i understand. It is able to utilize
>> offloading features of the Ethernet adapter I read somewhere...
>>
>> - What features are those? Is it
Jesse, thanks a lot for the insights,
Kind regards,
Atam
On Wed, Mar 27, 2013 at 6:41 PM, Jesse Gross wrote:
> On Wed, Mar 27, 2013 at 6:06 AM, Atam wrote:
> > Hi all,
> >
> > OVS is a software solution switch as i understand. It is able to utilize
> > offloading features of the Ethernet adap
On Wed, Mar 27, 2013 at 6:06 AM, Atam wrote:
> Hi all,
>
> OVS is a software solution switch as i understand. It is able to utilize
> offloading features of the Ethernet adapter I read somewhere...
>
> - What features are those? Is it desirable to invest in 10GB adapters with
> full TCP chimney s
Hi all,
OVS is a software solution switch as i understand. It is able to utilize
offloading features of the Ethernet adapter I read somewhere...
- What features are those? Is it desirable to invest in 10GB adapters with
full TCP chimney support like Emulex (OCe11102) or Broadcom (57810S) ? Or
is
On Wed, Mar 27, 2013 at 12:48 AM, Daniel Dehennin
wrote:
> Jesse Gross writes:
>
>
> [...]
>
>> It's difficult to read your diagram but isn't vnet16 (where DHCP
>> responses are still seen) after OVS?
>
> Sorry, I'm not sure to understand your question:
>
> - vnet16 is the interface of the DHCP s
Just in case anybody else will be interested -- what I forgot is to
update "bridges" in "Open_vSwitch" table with reference to freshly
created bridge.
On 03/27/2013 11:25 AM, Boris Tobotras wrote:
Looks like I'm almost there:
me>ovsdb:
{"method":"transact","params":["Open_vSwitch",{"uuid-na
Jesse Gross writes:
[...]
> It's difficult to read your diagram but isn't vnet16 (where DHCP
> responses are still seen) after OVS?
Sorry, I'm not sure to understand your question:
- vnet16 is the interface of the DHCP server
- isw is the name of the Open vSwitch
- vnet18 is the interface o
Hi Ben,
On 03/26/2013 08:45 PM, Ben Pfaff wrote:
You can't use hard-coded uuids to refer to new rows, because you
cannot know what the uuid of a new row is. Use a named-uuid.
Looks like I'm almost there:
me>ovsdb:
{"method":"transact","params":["Open_vSwitch",{"uuid-name":"paci1faced","op"
12 matches
Mail list logo
