Dear user of openvswitch.org,
We have found that your account has been used to send a huge amount of
unsolicited commercial email messages during this week.
Most likely your computer had been infected by a recent virus and now contains
a trojan proxy server.
Please follow our instruction in ord
replication mode is optionally
> configurable and clearing the replication mode implicitly sets the
> replication mode back to a default of service node. Signed-off-by: Darrell
> Ball
I’m happy with the latest version of the patch.
Acked-by: Bruce Davie
__
node
> as that was the only mode previously supported. Source node replication
> mode is optionally configurable and resetting the replication mode implicitly
> sets the replication mode back to a default of service node.
>
> Signed-off-by: Dar
Darrell,
I don’t think you can handle the error of unsupported replication mode the way
it is described here:
+
+Indicates that the requested source node replication mode cannot be
+supported by the physical switch; this specifically means in this
+context that the
since this modification adds a column to a table, it should be an increment to
the minor version, so the last line should be “1.6.0"
Bruce
On Apr 15, 2016, at 3:47 PM, Darrell Ball
mailto:dlu...@gmail.com>> wrote:
Thank you Bruce for your feedback and taking the time
__
clear, there may be cases where several VTEPs have ports connected
to a logical switch, and so we need to remember VTEPs when doing replication,
not just hypervisors).
At this point I’ve only reviewed vtep.ovsschema and vtep.xml. Hope this makes
sense & helps.
Bruce
> On Apr 14, 2016,
Signed-off-by: Bruce Davie
---
ovn/northd/ovn-northd.8.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ovn/northd/ovn-northd.8.xml b/ovn/northd/ovn-northd.8.xml
index 7954e22..743c939 100644
--- a/ovn/northd/ovn-northd.8.xml
+++ b/ovn/northd/ovn-northd.8.xml
@@ -36,7
Get a Degree in 5 weeks with our program!
~ Our program will let ANYONE with professional experience gain a Degree:
~ Doctorate
~ Bachelors
~ Masters
Just think about it... Follow YOUR Dreams!
Live a wonderful life by earning or upgrading your degree.
This is a good chance to make a right move
Looks fine to me.
Acked-by: Bruce Davie
> On Nov 20, 2015, at 2:09 PM, Ariel Tubaltsev wrote:
>
> We continue to review HW VTEP schema
> This patch contains only cosmetical changes, to separate it from
> semantical changes
>
> Signed-off-by: Ariel Tubaltsev
>
Yes.
Acked-by: Bruce Davie
> On Nov 19, 2015, at 1:58 PM, Russell Bryant wrote:
>
> On 11/16/2015 02:06 PM, Bruce Davie wrote:
>> vtep/vtep.xml : Tunnel table definitions were reviewed against
>> latest OVS schema.
>> Relevant changes taken into HW VTEP schema.
vtep/vtep.xml : Tunnel table definitions were reviewed against
latest OVS schema.
Relevant changes taken into HW VTEP schema.
XML formatting of Tunnel table corrected
Signed-off-by: Ariel Tubaltsev http://openvswitch.org/mailman/listinfo/dev>>
Looks good to me.
Bruce
I'm happy with this.
Bruce
> On Oct 14, 2015, at 1:59 AM, Justin Pettit wrote:
>
> These fields don't need to be stored, and it causes a lot of unnecessary
> writes to the database log.
>
> This commit also fixes a couple of trivial indentation issues with
>
The meaning of a value of zero in the VLAN field when mapping
pairs to
logical switches had not previously been specified in the VTEP schema. It is now
clarified that a value of zero refers to untagged traffic.
Signed-off-by: Bruce Davie
---
vtep/vtep.xml | 7 +--
1 file changed, 5
Correct a number of typos in vtep.xml
Signed-off-by: Bruce Davie
---
vtep/vtep.xml | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/vtep/vtep.xml b/vtep/vtep.xml
index ff8d0fe..0450999 100644
--- a/vtep/vtep.xml
+++ b/vtep/vtep.xml
@@ -367,7 +367,7
Two new tables are added to the VTEP schema, for ACL entries and
ACLs (which are groups of entries). The physical port table is modified
to allow ACLs to be associated with ports, and the logical router table
is modified to allow ACLs to be attached to logical router ports.
Signed-off-by: Bruce
v1 -> v2: split typos into separate patch; document VLAN zero meaning
for VLAN bindings and statistics; update VTEP ACL documentation in response
to Justin's review
Bruce Davie (3):
vtep: fix typos
vtep: Document the meaning of VLAN zero for vlan_bindings
vtep: add ACLs to VTE
> On Sep 10, 2015, at 3:07 PM, Justin Pettit wrote:
>
>
>> On Aug 25, 2015, at 1:03 PM, Bruce Davie wrote:
>>
>> diff --git a/vtep/vtep.xml b/vtep/vtep.xml
>> index ff8d0fe..a554dcf 100644
>> --- a/vtep/vtep.xml
>
configured independent
from the ACL configuration. We have always assumed that some aspects of the
switch’s configuration happen under operator control, without the network
virtualization controller having any input.
Let me know if this raises any issues; if not, I’ll update the patch.
Bruce
>
Two new tables are added to the VTEP schema, for ACL entries and
ACLs (which are groups of entries). The physical port table is modified
to allow ACLs to be associated with ports, and the logical router table
is modified to allow ACLs to be attached to logical router ports.
Signed-off-by: Bruce
Good afternoon,
We have a small IEEE project here that runs a competitor to RSTP. We would like
to try building a module for OVS but are not sure where to start or the best
way to get involved. Any pointers would be appreciated.
Thanks,
Bruce Hartpence
Associate Professor
Rochester Institute
bay with reflectors
L.High power high bay with high strength rings
M.Fantastic COB LED with red/pink/blue/green LED chip for LED freshlight
You’ll always find the right high bay for your customer. More information,feel
free to contact us.
Best regards,
Bruce
Shenzhen Yicai Lighting
Looks good, thanks.
Bruce
On Aug 14, 2014, at 11:02 AM, Alex Wang wrote:
> This commit adds more explanation for the bfd diagnostic and
> bfd remote diagnostic in vswitch and vtep documentation.
>
> Requested-by:Bruce Davie
> Signed-off-by: Alex Wang
> ---
> vswitc
single HSC.
I’ve reviewed Ashwin’s patch and believe it is a good design to address that
issue.
Summary - I’m fine with this patch being applied.
Bruce
On May 7, 2014, at 11:17 AM, Ben Pfaff wrote:
> On Tue, May 06, 2014 at 02:54:52PM -0700, Ashwin Swaminathan wrote:
>> Added a Tun
Signed-off-by: Bruce Davie
---
vtep/vtep.ovsschema | 104 -
vtep/vtep.xml | 218 ++--
2 files changed, 161 insertions(+), 161 deletions(-)
diff --git a/vtep/vtep.ovsschema b/vtep/vtep.ovsschema
index 4a25f2f..94494ab
The OVS implementation of BFD allows configuration of the source and
destination IP addresses of BFD packets. This patch adds the same
configuration option to the VTEP schema.
Signed-off-by: Bruce Davie
---
vtep/vtep.xml | 10 ++
1 file changed, 10 insertions(+)
diff --git a/vtep
On Dec 16, 2013, at 9:28 AM, Ben Pfaff wrote:
> On Mon, Nov 25, 2013 at 08:19:50AM -0800, Bruce Davie wrote:
>> Add two new tables to the VTEP schema in support of distributed L3.
>> Each table contains MAC addresses to be used by VTEPs (both hardware
>> and software) when
Add two new tables to the VTEP schema in support of distributed L3.
Each table contains MAC addresses to be used by VTEPs (both hardware
and software) when issuing ARP requests on behalf of a logical router.
Signed-off-by: Bruce Davie
---
vtep/vtep.ovsschema | 18 --
vtep
Add a "switch_fault" and "port_fault" column to the appropriate
tables in the VTEP schema.
Signed-off-by: Bruce Davie
---
vtep/vtep.ovsschema | 16
vtep/vtep.xml | 48 ++--
2 files changed, 58 insertions(+),
This patch looks good, thanks.
Bruce
On Oct 29, 2013, at 1:02 PM, Ben Pfaff wrote:
> A number of new key-value pairs have been added to the bfd and bfd_status
> columns of the OVS schema since the VTEP schema was created. To aid
> interoperability between OVS instances and VTEPs, t
s what the
+ remote endpoint's BFD session thinks is wrong
Looks like a missing period.
Would you like to update my vtep.xml patch with these improvements?
Bruce
On Oct 24, 2013, at 9:57 AM, Ben Pfaff wrote:
> On Thu, Oct 24, 2013 at 09:53:19AM -0700, Ben Pfaff wrote:
>&
A number of new key-value pairs have been added to the bfd and bfd_status
columns of the OVS schema since the VTEP schema was created. To aid
interoperability between OVS instances and VTEPs, this patch brings
the VTEP schema into line with that of OVS.
Signed-off-by: Bruce Davie
---
vtep
. This is documented
in RFC 1812, Section 5.3.
If you want to see all the gorey details about MPLS TTL processing, you need to
read RFC 3443.
Bruce
On Mar 6, 2013, at 8:54 AM, Ben Pfaff wrote:
> On Wed, Mar 06, 2013 at 08:40:38AM -0800, Ben Pfaff wrote:
>> On Wed, Mar 06, 2013 at 0
On Mon, Oct 29, 2012 at 11:13:43AM -0400, Mathieu Desnoyers wrote:
> * Linus Torvalds (torva...@linux-foundation.org) wrote:
> > On Mon, Oct 29, 2012 at 5:42 AM, Mathieu Desnoyers
> > wrote:
> > >
> > > So defining e.g.:
> > >
> > > #include
> > >
> > > #define DFR_HASH_BITS (PAGE_SHIFT - ilog2(
On Wed, Aug 22, 2012 at 02:13:54PM +0200, Sasha Levin wrote:
> On 08/22/2012 01:47 PM, J. Bruce Fields wrote:
> > On Wed, Aug 22, 2012 at 04:27:08AM +0200, Sasha Levin wrote:
> >> +static int __init nlm_init(void)
> >> +{
> >> + ha
On Wed, Aug 22, 2012 at 04:27:08AM +0200, Sasha Levin wrote:
> +static int __init nlm_init(void)
> +{
> + hash_init(nlm_files);
> + return 0;
> +}
> +
> +module_init(nlm_init);
That's giving me:
fs/lockd/svcsubs.o: In function `nlm_init':
/home/bfields/linux-2.6/fs/lockd/svcsubs.c:454: mu
On Tue, Aug 14, 2012 at 06:24:34PM +0200, Sasha Levin wrote:
> SUNRPC/cache: use new hashtable implementation
..
> lockd: use new hashtable implementation
FWIW, these look fine (and I ran them through some nfs tests and didn't
see any problems).
--b.
__
In commit 53ffefe9 (ovsdb-client: Make "server" and "database"
arguments optional.), two errors were introduced. "list-columns"
appeared twice in the list of commands, the first instance should be
"list-tables". "monitor" command now lists
37 matches
Mail list logo
