[nox-dev] NOX startup script

[Josh Smift]

JBS> We've created a NOX package that seems to run the 'switch' module
JBS> successfully outside of the build directory, including an init.d
JBS> script that starts up NOX instances based on config files in an
JBS> /etc/nox/instances.d directory. I'm going through the BBN process to
JBS> publish the script, and will follow up when I've done that...

I've finally done this; it's posted on the GENI software download site at
http://software.geni.net/local-sw/, and includes the init.d script, and a
README file with a link to the steps to build the package that it works with.

If the nox-dev folks wanted to incorporate this into NOX somehow, that
could be nifty. If they don't, folks are welcome to use it if they find it
useful.

  -Josh (j...@bbn.com)

___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] Contributing to Nox

[Derek Cormier]

Hello,
Here are two patches for destiny for the Python API.

patch 1:
 - in pyrt.cc, add datapath id to the dictionaries created by 
Flow_removed_event and Error_event


patch2:
- add lots of doxygen doc strings to core.api
- add callback generators for flow mod and flow removed events
- change the names of callback generators to make them more readable
- add more constants for dictionary keys

-Derek

On 01/04/2011 10:27 AM, kk yap wrote:

Hi Derek,

Thanks.  Doxygen comments are presented in the code.  E.g.,

/** \brief Event
  * Some event
  *
  * @author ykk
  * @date Jan 2011
  */
struct x_event
{
   ...
}

They are more in-depth example in the components.

Regards
KK

On 3 January 2011 17:19, Derek Cormier  wrote:

Sure thing. Where do the doxygen comments go? I've never used doxygen
before, I'm assuming they go above the struct definition but I don't see any
such comments in the files I edited. Is there another file?

Thanks,
-Derek

On 01/04/2011 06:20 AM, kk yap wrote:

Hi Derek,

Sorry it took me a while to get to this.  Can you put in doxygen
comments for these patches?  The patches includes new structs and so
on from what I can see.  Else, I can do it.  But I doubt I can get to
it fast enough.  Thanks.

Regards
KK

On 27 December 2010 23:23, Derek Cormier
  wrote:

Here's a couple more patches for destiny.

'barrier-reply.tar.gz'  -  make barrier reply events available to the
Python
API.
'flow-stats-in.tar.gz'  -  add a convenience method in component to
register
for flow stats in events.

-Derek

On 12/28/2010 01:30 AM, Martin Casado wrote:

Thanks KK.  I pushed a few edits as well.


Hi,

I have done that for destiny and pushed the file.  Martin, you should
probably check the list again.  If I have missed you out (since I only
exploited git log), do let me know.

Regards
KK


___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org








>From d62016396cbe6df330d8c487c0601152fbcf09f6 Mon Sep 17 00:00:00 2001
From: Derek Cormier 
Date: Tue, 11 Jan 2011 16:02:27 +0900
Subject: [PATCH 3/4] Add doxygen doc strings to methods in core.py and
 make the Python API a bit more accessible.

core.py:
  - Added callback generators for flow removed and flow mod events.
- No components in the repo use the register_for_flow_*
  for these events, but if your own components do you
  will need to modify the method headers (see docstrings).
  - Added more constants for dictionary keys.

util.py:
  - Added datapath id arg to error event callback generator.
  - Callback generator names are now more readable.
---
 src/nox/lib/core.py |  596 ---
 src/nox/lib/util.py |   49 +++--
 2 files changed, 363 insertions(+), 282 deletions(-)

diff --git a/src/nox/lib/core.py b/src/nox/lib/core.py
index 5c77708..7d3485c 100644
--- a/src/nox/lib/core.py
+++ b/src/nox/lib/core.py
@@ -14,6 +14,7 @@
 # 
 # You should have received a copy of the GNU General Public License
 # along with NOX.  If not, see .
+
 import logging
 import array
 import struct
@@ -54,6 +55,13 @@ CAPABILITES = 'caps'
 ACTIONS = 'actions'
 PORTS   = 'ports'
 
+TABLE_ID= 'table_id'
+NAME= 'name'
+MAX_ENTRIES = 'max_entries'
+ACTIVE_COUNT = 'active_count'
+LOOKUP_COUNT = 'lookup_count'
+MATCHED_COUNT = 'matched_count'
+
 PORT_NO = 'port_no'
 SPEED   = 'speed'
 CONFIG  = 'config'
@@ -64,6 +72,37 @@ SUPPORTED   = 'supported'
 PEER= 'peer'
 HW_ADDR = 'hw_addr'
 
+RX_PACKETS = 'rx_packets'
+TX_PACKETS = 'tx_packets'
+RX_BYTES   = 'rx_bytes'
+TX_BYTES   = 'tx_bytes'
+RX_DROPPED = 'rx_dropped'
+TX_DROPPED = 'tx_dropped'
+RX_ERRORS  = 'rx_errors'
+TX_ERRORS  = 'tx_errors'
+RX_FRAME_ERROR = 'rx_frame_error'
+RX_OVER_ERROR = 'rx_over_error'
+RX_CRC_ERROR = 'rx_crc_error'
+COLLISIONS = 'collisions'
+
+PACKET_COUNT = 'packet_count'
+BYTE_COUNT = 'byte_count'
+FLOW_COUNT = 'flow_count'
+
+MATCH = 'match'
+COOKIE = 'cookie'
+DUR_SEC = 'duration_sec'
+DUR_NSEC = 'duration_nsec'
+PRIORITY = 'priority'
+IDLE_TO = 'idle_timeout'
+HARD_TO = 'hard_timeout'
+
+MFR_DESC = 'mfr_desc'
+HW_DESC = 'hw_desc'
+SW_DESC = 'sf_desc'
+DP_DESC = 'dp_desc'
+SERIAL_NUM = 'serial_num'
+
 
 # API NOTES:
 #
@@ -82,7 +121,7 @@ HW_ADDR = 'hw_addr'
 ###
 
 class Component: 
-"""Abstract class to inherited by all Python components.
+"""\brief Abstract class to inherited by all Python components.
 \ingroup noxapi
 """
 def __init__(self, ctxt):
@@ -90,30 +129,38 @@ class Component:
 self.component_names = None 
 
 def configure(self, config):
-"""Configure the component.
+"""\brief Configure the component.
 Once configured, the component has parsed its configuration and
-  

[nox-dev] Dear NOX-Dev

[Min-Hyup Kang]

	
	
 Dear all,

My name is Min-Hyup Kang,

I am a student who studying about openflow.

so, I have a question. Can I ask you please ?

I have a pronto 3290 switch. so, I would like to install nox controller.'

Which can I get the nox version ? (http://noxrepo.org/wp)

Thank you for your attention :D






			==
Min-Hyup Kang
Thank you !
==  


 

___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] Dear NOX-Dev

[James "Murphy" McCauley]

Hi, and welcome to nox-dev.

I believe your switch supports OpenFlow 1.0, so either the zaku (stable)
or destiny (unstable) branch of NOX should work.

I don't know if you're familiar with git at all, but installation
instructions can be found on the wiki at:
http://noxrepo.org/noxwiki/index.php/NOX_Installation

If you want to use the destiny branch, just use "destiny" where it
specifies "" (and it's probably best to use it for
"" as well).

Hope that helps.

-- Murphy

On Tue, 2011-01-11 at 17:54 +0900, Min-Hyup Kang wrote:
>Dear all,
>
>
>
>   My name is Min-Hyup Kang,
>
>
>  I am a student who studying about openflow.
>
>
> so, I have a question. Can I ask you please ?
>
>
>  I have a pronto 3290 switch. so, I would like to install nox
>  controller.'
>
>
>   Which can I get the nox version ? (http://noxrepo.org/wp)
>
>
>Thank you for your attention :D
>
>
> 
> 
> 
> == 
> Min-Hyup Kang 
> Thank you ! 
> == 
> 
>  
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org



___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] Contributing to Nox

[Martin Casado]

Derek,

Thanks for the patches, these are very helpful.  One of us will take a 
look shortly.


.martin


Hello,
Here are two patches for destiny for the Python API.

patch 1:
 - in pyrt.cc, add datapath id to the dictionaries created by 
Flow_removed_event and Error_event


patch2:
- add lots of doxygen doc strings to core.api
- add callback generators for flow mod and flow removed events
- change the names of callback generators to make them more readable
- add more constants for dictionary keys

-Derek

On 01/04/2011 10:27 AM, kk yap wrote:

Hi Derek,

Thanks.  Doxygen comments are presented in the code.  E.g.,

/** \brief Event
  * Some event
  *
  * @author ykk
  * @date Jan 2011
  */
struct x_event
{
   ...
}

They are more in-depth example in the components.

Regards
KK

On 3 January 2011 17:19, Derek Cormier  
wrote:

Sure thing. Where do the doxygen comments go? I've never used doxygen
before, I'm assuming they go above the struct definition but I don't 
see any

such comments in the files I edited. Is there another file?

Thanks,
-Derek

On 01/04/2011 06:20 AM, kk yap wrote:

Hi Derek,

Sorry it took me a while to get to this.  Can you put in doxygen
comments for these patches?  The patches includes new structs and so
on from what I can see.  Else, I can do it.  But I doubt I can get to
it fast enough.  Thanks.

Regards
KK

On 27 December 2010 23:23, Derek Cormier
  wrote:

Here's a couple more patches for destiny.

'barrier-reply.tar.gz'  -  make barrier reply events available to the
Python
API.
'flow-stats-in.tar.gz'  -  add a convenience method in component to
register
for flow stats in events.

-Derek

On 12/28/2010 01:30 AM, Martin Casado wrote:

Thanks KK.  I pushed a few edits as well.


Hi,

I have done that for destiny and pushed the file.  Martin, you 
should
probably check the list again.  If I have missed you out (since 
I only

exploited git log), do let me know.

Regards
KK


___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org









___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org



--
~~~
Martin Casado
Nicira Networks, Inc.
www.nicira.com | www.openvswitch.org
cell: 650-776-1457
~~~

___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] Contributing to Nox

[kk yap]

Hi Derek,

Thanks.  Great patches as usual.  I have pushed them to the destiny branch.

Martin and Murphy, I believe I have pushed most (if not all) of
Derek's patches at this moment.  If anything else is missing, let me
know.

Thanks.

Regards
KK

On 11 January 2011 07:23, Martin Casado  wrote:
> Derek,
>
> Thanks for the patches, these are very helpful.  One of us will take a look
> shortly.
>
> .martin
>
> Hello,
> Here are two patches for destiny for the Python API.
>
> patch 1:
>  - in pyrt.cc, add datapath id to the dictionaries created by
> Flow_removed_event and Error_event
>
> patch2:
> - add lots of doxygen doc strings to core.api
> - add callback generators for flow mod and flow removed events
> - change the names of callback generators to make them more readable
> - add more constants for dictionary keys
>
> -Derek
>
> On 01/04/2011 10:27 AM, kk yap wrote:
>
> Hi Derek,
>
> Thanks.  Doxygen comments are presented in the code.  E.g.,
>
> /** \brief Event
>   * Some event
>   *
>   * @author ykk
>   * @date Jan 2011
>   */
> struct x_event
> {
>    ...
> }
>
> They are more in-depth example in the components.
>
> Regards
> KK
>
> On 3 January 2011 17:19, Derek Cormier  wrote:
>
> Sure thing. Where do the doxygen comments go? I've never used doxygen
> before, I'm assuming they go above the struct definition but I don't see any
> such comments in the files I edited. Is there another file?
>
> Thanks,
> -Derek
>
> On 01/04/2011 06:20 AM, kk yap wrote:
>
> Hi Derek,
>
> Sorry it took me a while to get to this.  Can you put in doxygen
> comments for these patches?  The patches includes new structs and so
> on from what I can see.  Else, I can do it.  But I doubt I can get to
> it fast enough.  Thanks.
>
> Regards
> KK
>
> On 27 December 2010 23:23, Derek Cormier
>   wrote:
>
> Here's a couple more patches for destiny.
>
> 'barrier-reply.tar.gz'  -  make barrier reply events available to the
> Python
> API.
> 'flow-stats-in.tar.gz'  -  add a convenience method in component to
> register
> for flow stats in events.
>
> -Derek
>
> On 12/28/2010 01:30 AM, Martin Casado wrote:
>
> Thanks KK.  I pushed a few edits as well.
>
> Hi,
>
> I have done that for destiny and pushed the file.  Martin, you should
> probably check the list again.  If I have missed you out (since I only
> exploited git log), do let me know.
>
> Regards
> KK
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
>
>
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
>
> --
> ~~~
> Martin Casado
> Nicira Networks, Inc.
> www.nicira.com | www.openvswitch.org
> cell: 650-776-1457
> ~~~

___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] Contributing to Nox

[kk yap]

Hi All,

With Derek's patch, the documentation for destiny branch is more
useful for those using Python.  Consequently, I have pushed the
doxygen documentation for destiny (which include Derek's patch) to
replace the one previously generated from zaku.  FYI.

Regards
KK

On 11 January 2011 11:43, kk yap  wrote:
> Hi Derek,
>
> Thanks.  Great patches as usual.  I have pushed them to the destiny branch.
>
> Martin and Murphy, I believe I have pushed most (if not all) of
> Derek's patches at this moment.  If anything else is missing, let me
> know.
>
> Thanks.
>
> Regards
> KK
>
> On 11 January 2011 07:23, Martin Casado  wrote:
>> Derek,
>>
>> Thanks for the patches, these are very helpful.  One of us will take a look
>> shortly.
>>
>> .martin
>>
>> Hello,
>> Here are two patches for destiny for the Python API.
>>
>> patch 1:
>>  - in pyrt.cc, add datapath id to the dictionaries created by
>> Flow_removed_event and Error_event
>>
>> patch2:
>> - add lots of doxygen doc strings to core.api
>> - add callback generators for flow mod and flow removed events
>> - change the names of callback generators to make them more readable
>> - add more constants for dictionary keys
>>
>> -Derek
>>
>> On 01/04/2011 10:27 AM, kk yap wrote:
>>
>> Hi Derek,
>>
>> Thanks.  Doxygen comments are presented in the code.  E.g.,
>>
>> /** \brief Event
>>   * Some event
>>   *
>>   * @author ykk
>>   * @date Jan 2011
>>   */
>> struct x_event
>> {
>>    ...
>> }
>>
>> They are more in-depth example in the components.
>>
>> Regards
>> KK
>>
>> On 3 January 2011 17:19, Derek Cormier  wrote:
>>
>> Sure thing. Where do the doxygen comments go? I've never used doxygen
>> before, I'm assuming they go above the struct definition but I don't see any
>> such comments in the files I edited. Is there another file?
>>
>> Thanks,
>> -Derek
>>
>> On 01/04/2011 06:20 AM, kk yap wrote:
>>
>> Hi Derek,
>>
>> Sorry it took me a while to get to this.  Can you put in doxygen
>> comments for these patches?  The patches includes new structs and so
>> on from what I can see.  Else, I can do it.  But I doubt I can get to
>> it fast enough.  Thanks.
>>
>> Regards
>> KK
>>
>> On 27 December 2010 23:23, Derek Cormier
>>   wrote:
>>
>> Here's a couple more patches for destiny.
>>
>> 'barrier-reply.tar.gz'  -  make barrier reply events available to the
>> Python
>> API.
>> 'flow-stats-in.tar.gz'  -  add a convenience method in component to
>> register
>> for flow stats in events.
>>
>> -Derek
>>
>> On 12/28/2010 01:30 AM, Martin Casado wrote:
>>
>> Thanks KK.  I pushed a few edits as well.
>>
>> Hi,
>>
>> I have done that for destiny and pushed the file.  Martin, you should
>> probably check the list again.  If I have missed you out (since I only
>> exploited git log), do let me know.
>>
>> Regards
>> KK
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>>
>>
>>
>>
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>>
>> --
>> ~~~
>> Martin Casado
>> Nicira Networks, Inc.
>> www.nicira.com | www.openvswitch.org
>> cell: 650-776-1457
>> ~~~
>

___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org