This change ensures that we always end up with two elements even
if the name of the physical port contains dashes. For example, a
binding of "0100-br0-eth1" will be split to ["0100", "br0-eth1"]
instead of ["0100", "br0", "eth1"].
Si
That's a more elegant solution. Yes, that works for me. Thanks! :-)
On Wed, Sep 10, 2014 at 8:51 AM, Gurucharan Shetty
wrote:
> On Tue, Sep 9, 2014 at 9:18 AM, Mark Maglana wrote:
> > On Tue, Sep 9, 2014 at 8:04 AM, Gurucharan Shetty
> > wrote:
> >>
> >>
On Tue, Sep 9, 2014 at 8:04 AM, Gurucharan Shetty
wrote:
> I see that there is a bug. With your patch, would we still hit the bug
> if the port name has a "--" in it?
>
Definitely. Although I'm guessing that the probability of "--" being in the
port name is negligible. I can make it more unique
Mininet is attached to a logical switch.
Signed-off-by: Mark Maglana
---
vtep/ovs-vtep | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/vtep/ovs-vtep b/vtep/ovs-vtep
index 721063b..bcd8b06 100755
--- a/vtep/ovs-vtep
+++ b/vtep/ovs-vtep
@@ -286,9 +286,9 @@
Thank you for the quick feedback and the corrections. This looks good.
On Thu, Aug 14, 2014 at 1:05 PM, Gurucharan Shetty
wrote:
> From: Mark Maglana
>
> The README was not clear on whether the steps are for attaching physical
> or virtual machines to the emulated VTEP. This adds
The README was not clear on whether the steps are for attaching physical
or virtual machines to the emulated VTEP. This adds more detail to the
README so that readers will know what to do if they want to attach physical
machines or otherwise.
Signed-off-by: Mark Maglana
---
vtep/README.ovs-vtep
