Re: [ovs-dev] [PATCH] Update tutorial for newer versions of Faucet and Open vSwitch.

2020-12-21 Thread Ilya Maximets
On 11/19/20 4:30 AM, Brad Cowie wrote:
> Hi Ilya,
> 
> Sorry for the late reply, this email got lost in my inbox.
> 
> Yes this patch is still good to go and happy for it to be merged.

Great.  Thanks for the patch!

Applied to master.

Best regards, Ilya Maximets.

> 
> Thanks,
> Brad
> 
> On 10/09/20 12:39 am, Ilya Maximets wrote:
>> On 9/12/18 1:53 AM, Brad Cowie wrote:
>>> Newer versions of Faucet use a dynamic OpenFlow pipeline based on what
>>> features are enabled in the configuration file. Update log output, flow
>>> table dumps and explanations to be consistent with newer Faucet versions.
>>>
>>> Remove mentions of bugs that we have since fixed in Faucet since the
>>> tutorial was originally written.
>>>
>>> Adds documentation on changes to Open vSwitch commands to recommend
>>> using a version that is compatible with the features of the tutorial.
>>>
>>> Reported-by: Matthias Ableidinger 
>>> Reported-at: 
>>> https://mail.openvswitch.org/pipermail/ovs-discuss/2018-August/047180.html
>>> Signed-off-by: Brad Cowie 
>>> ---
>>
>> Hi.  I'm looking through old patches after the patchwork cleanup and
>> this one seems to be never applied.  I do not have any experience with
>> Faucet, but the patch looks ok and it's still applicable.
>>
>> Brad, Ben, if it still valid I could apply it.  What do you think?
>>
>> Best regards, Ilya Maximets.
>>

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] [PATCH] Update tutorial for newer versions of Faucet and Open vSwitch.

2020-11-18 Thread Brad Cowie

Hi Ilya,

Sorry for the late reply, this email got lost in my inbox.

Yes this patch is still good to go and happy for it to be merged.

Thanks,
Brad

On 10/09/20 12:39 am, Ilya Maximets wrote:

On 9/12/18 1:53 AM, Brad Cowie wrote:

Newer versions of Faucet use a dynamic OpenFlow pipeline based on what
features are enabled in the configuration file. Update log output, flow
table dumps and explanations to be consistent with newer Faucet versions.

Remove mentions of bugs that we have since fixed in Faucet since the
tutorial was originally written.

Adds documentation on changes to Open vSwitch commands to recommend
using a version that is compatible with the features of the tutorial.

Reported-by: Matthias Ableidinger 
Reported-at: 
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-August/047180.html
Signed-off-by: Brad Cowie 
---


Hi.  I'm looking through old patches after the patchwork cleanup and
this one seems to be never applied.  I do not have any experience with
Faucet, but the patch looks ok and it's still applicable.

Brad, Ben, if it still valid I could apply it.  What do you think?

Best regards, Ilya Maximets.


___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] [PATCH] Update tutorial for newer versions of Faucet and Open vSwitch.

2020-09-09 Thread Ilya Maximets
On 9/12/18 1:53 AM, Brad Cowie wrote:
> Newer versions of Faucet use a dynamic OpenFlow pipeline based on what
> features are enabled in the configuration file. Update log output, flow
> table dumps and explanations to be consistent with newer Faucet versions.
> 
> Remove mentions of bugs that we have since fixed in Faucet since the
> tutorial was originally written.
> 
> Adds documentation on changes to Open vSwitch commands to recommend
> using a version that is compatible with the features of the tutorial.
> 
> Reported-by: Matthias Ableidinger 
> Reported-at: 
> https://mail.openvswitch.org/pipermail/ovs-discuss/2018-August/047180.html
> Signed-off-by: Brad Cowie 
> ---

Hi.  I'm looking through old patches after the patchwork cleanup and
this one seems to be never applied.  I do not have any experience with
Faucet, but the patch looks ok and it's still applicable.

Brad, Ben, if it still valid I could apply it.  What do you think?

Best regards, Ilya Maximets.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] [PATCH] Update tutorial for newer versions of Faucet and Open vSwitch.

2019-07-28 Thread Brad Cowie




On 18/09/18 4:50 PM, Ben Pfaff wrote:

On Wed, Sep 12, 2018 at 11:53:28AM +1200, Brad Cowie wrote:


Reported-by: Matthias Ableidinger 
Reported-at: 
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-August/047180.html
Signed-off-by: Brad Cowie 


This is really nice.  Thank you.

To avoid causing even more confusion, I'm going to hold off on applying
it until the series that it relies on has been applied.  I hope that is
soon.


Looks like the other patch series was eventually merged, shall we merge 
this patch in now too?


Brad
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] [PATCH] Update tutorial for newer versions of Faucet and Open vSwitch.

2018-09-17 Thread Ben Pfaff
On Wed, Sep 12, 2018 at 11:53:28AM +1200, Brad Cowie wrote:
> Newer versions of Faucet use a dynamic OpenFlow pipeline based on what
> features are enabled in the configuration file. Update log output, flow
> table dumps and explanations to be consistent with newer Faucet versions.
> 
> Remove mentions of bugs that we have since fixed in Faucet since the
> tutorial was originally written.
> 
> Adds documentation on changes to Open vSwitch commands to recommend
> using a version that is compatible with the features of the tutorial.
> 
> Reported-by: Matthias Ableidinger 
> Reported-at: 
> https://mail.openvswitch.org/pipermail/ovs-discuss/2018-August/047180.html
> Signed-off-by: Brad Cowie 

This is really nice.  Thank you.

To avoid causing even more confusion, I'm going to hold off on applying
it until the series that it relies on has been applied.  I hope that is
soon.

Thanks again!
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


[ovs-dev] [PATCH] Update tutorial for newer versions of Faucet and Open vSwitch.

2018-09-11 Thread Brad Cowie
Newer versions of Faucet use a dynamic OpenFlow pipeline based on what
features are enabled in the configuration file. Update log output, flow
table dumps and explanations to be consistent with newer Faucet versions.

Remove mentions of bugs that we have since fixed in Faucet since the
tutorial was originally written.

Adds documentation on changes to Open vSwitch commands to recommend
using a version that is compatible with the features of the tutorial.

Reported-by: Matthias Ableidinger 
Reported-at: 
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-August/047180.html
Signed-off-by: Brad Cowie 
---
 Documentation/tutorials/faucet.rst | 596 +++--
 1 file changed, 304 insertions(+), 292 deletions(-)

diff --git a/Documentation/tutorials/faucet.rst 
b/Documentation/tutorials/faucet.rst
index 9696dfd..82e5efa 100644
--- a/Documentation/tutorials/faucet.rst
+++ b/Documentation/tutorials/faucet.rst
@@ -68,9 +68,9 @@ approaches:
  $ git clone https://github.com/openvswitch/ovs.git
  $ cd ovs
 
-   The default checkout is the master branch.  You can check out a tag
-   (such as v2.8.0) or a branch (such as origin/branch-2.8), if you
-   prefer.
+   The default checkout is the master branch.  You will need to use the master
+   branch for this tutorial as it includes some functionality required for this
+   tutorial.
 
 2. If you do not already have an installed copy of Open vSwitch on your system,
or if you do not want to use it for the sandbox (the sandbox will not
@@ -80,6 +80,13 @@ approaches:
 
  $ tutorial/ovs-sandbox
 
+   .. note::
+
+ The default behaviour for some of the commands used in this tutorial
+ changed in Open vSwitch versions 2.9.x and 2.10.x which breaks the
+ tutorial.  We recommend following step 3 and building master from
+ source or using a system Open vSwitch that is version 2.8.x or older.
+
If it is successful, you will find yourself in a subshell environment, which
is the sandbox (you can exit with ``exit`` or Control+D).  If so, you're
finished and do not need to complete the rest of the steps.  If it fails,
@@ -90,6 +97,12 @@ approaches:
tutorial, there is no need to compile the Linux kernel module, or to use any
of the optional libraries such as OpenSSL, DPDK, or libcap-ng.
 
+   If you are using a Linux system that uses apt and have some ``deb-src``
+   repos listed in ``/etc/apt/sources.list``, often an easy way to install
+   the build dependencies for a package is to use ``build-dep``::
+
+ $ sudo apt-get build-dep openvswitch
+
 4. Configure and build Open vSwitch::
 
  $ ./boot.sh
@@ -130,7 +143,7 @@ between one and the other.
 
 2. Build a docker container image::
 
- $ docker build -t faucet/faucet .
+ $ sudo docker build -t faucet/faucet -f Dockerfile.faucet .
 
This will take a few minutes.
 
@@ -147,7 +160,7 @@ between one and the other.
 
 4. Create a container and start Faucet::
 
- $ docker run -d --name faucet --restart=always -v 
$(pwd)/inst/:/etc/faucet/ -v $(pwd)/inst/:/var/log/faucet/ -p 6653:6653 -p 
9302:9302 faucet/faucet
+ $ sudo docker run -d --name faucet --restart=always -v 
$(pwd)/inst/:/etc/faucet/ -v $(pwd)/inst/:/var/log/faucet/ -p 6653:6653 -p 
9302:9302 faucet/faucet
 
 5. Look in ``inst/faucet.log`` to verify that Faucet started.  It will
probably start with an exception and traceback because we have not
@@ -156,17 +169,17 @@ between one and the other.
 6. Later on, to make a new or updated Faucet configuration take
effect quickly, you can run::
 
- $ docker exec faucet pkill -HUP -f faucet.faucet
+ $ sudo docker exec faucet pkill -HUP -f faucet.faucet
 
Another way is to stop and start the Faucet container::
 
- $ docker restart faucet
+ $ sudo docker restart faucet
 
You can also stop and delete the container; after this, to start it
again, you need to rerun the ``docker run`` command::
 
- $ docker stop faucet
- $ docker rm faucet
+ $ sudo docker stop faucet
+ $ sudo docker rm faucet
 
 Overview
 
@@ -260,17 +273,16 @@ to be 0x1.
 
   This also sets high MAC learning and ARP timeouts.  The defaults are
   5 minutes and about 8 minutes, which are fine in production but
-  sometimes too fast for manual experimentation.  (Don't use a timeout
-  bigger than about 65000 seconds because it will crash Faucet.)
+  sometimes too fast for manual experimentation.
 
 Now restart Faucet so that the configuration takes effect, e.g.::
 
-  $ docker restart faucet
+  $ sudo docker restart faucet
 
 Assuming that the configuration update is successful, you should now
 see a new line at the end of ``inst/faucet.log``::
 
-  Jan 06 15:14:35 faucet INFO Add new datapath DPID 1 (0x1)
+  Sep 10 06:44:10 faucet INFO Add new datapath DPID 1 (0x1)
 
 Faucet is now waiting for a switch with datapath ID 0x1 to connect to
 it over OpenFlow, so our next step is to create a switch with OVS an