Exactly, this certainly looks like an older pyqt version. I am using 4.7.2,
although anything after 4.6 should be ok.
I think this line might be necessary; although you'll probably start seeing
nodes if you comment it out, you'll have issues if you move them around.
You'd better install a latest pyqt, as this is not the only part of the code
that uses > 4.6
Yes, the components are populated from the log messages. Also, hosts are not
displayed at this point, just switches
On Thu, Nov 11, 2010 at 7:12 AM, Murphy McCauley
<murphy.mccau...@gmail.com>wrote:
> I think you're using too old a version of qt/pyqt. I don't know exactly,
> but you need at least 4.6.
>
> You *might* be able to get away with just commenting out the erroring line
> (38 in gui/topology.py).
>
> -- Murphy
>
> On Nov 11, 2010, at 6:50 AM, "Christopher J. Tengi" <
> te...@cs.princeton.edu> wrote:
>
> Kyriakos,
> I am now running nox_core with this command line:
>
> ./nox_core -i ptcp:6633 switch switch_management hostip hosttracker
> monitoring jsonmessenger
>
> Here is what I get when I start the GUI:
>
> ========
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Xlib: extension "Generic Event Extension" missing on display
> "localhost:11.0".
> Sending ...{'command': 'request', 'node_type': 'all', 'type': 'lavi',
> 'xid': 1}
> Sending ...{'command': 'request', 'type': 'lavi', 'link_type': 'all',
> 'xid': 2}
> Sending ...{'command': 'subscribe', 'node_type': 'all', 'type': 'lavi',
> 'xid': 3}
> Sending ...{'command': 'subscribe', 'type': 'lavi', 'link_type': 'all',
> 'xid': 4}
> Sending ...{'command': 'subscribe', 'type': 'monitoring', 'msg_type':
> 'linkutils', 'xid': 5}
> Traceback (most recent call last):
> File "/var/local/src/nox/src/gui/topology.py", line 726, in got_topo_msg
> nodeItem = Node(self, nodeID)
> File "/var/local/src/nox/src/gui/topology.py", line 38, in __init__
> self.setFlag(QtGui.QGraphicsItem.ItemSendsGeometryChanges)
> AttributeError: type object 'QGraphicsItem' has no attribute
> 'ItemSendsGeometryChanges'
> ========
>
> When I click on the "Component" button, the "Filter by component" box comes
> up empty.
>
> Starting nox_core with '-v' yields the following:
>
> ========
> 00001|nox|INFO:Starting nox_core
> (/var/local/src/nox/build/src/.libs/lt-nox_core)
> 00002|pyrt|DBG:Loading a component description file
> 'nox/coreapps/pyrt/meta.json'.
> 00003|pyrt|DBG:Loading a component description file
> 'nox/coreapps/simple_c_app/meta.json'.
> 00004|pyrt|DBG:Loading a component description file
> 'nox/coreapps/snmp/meta.json'.
> 00005|pyrt|DBG:Loading a component description file
> 'nox/coreapps/testharness/meta.json'.
> 00006|pyrt|DBG:Loading a component description file
> 'nox/coreapps/examples/meta.json'.
> 00007|pyrt|DBG:Loading a component description file
> 'nox/coreapps/examples/t/meta.json'.
> 00008|pyrt|DBG:Loading a component description file
> 'nox/coreapps/hub/meta.json'.
> 00009|pyrt|DBG:Loading a component description file
> 'nox/coreapps/switch/meta.json'.
> 00010|pyrt|DBG:Loading a component description file
> 'nox/coreapps/coretests/meta.json'.
> 00011|pyrt|DBG:Loading a component description file
> 'nox/coreapps/messenger/meta.json'.
> 00012|pyrt|DBG:Loading a component description file
> 'nox/coreapps/simple_c_py_app/meta.json'.
> 00013|pyrt|DBG:Loading a component description file
> 'nox/netapps/switch_management/meta.json'.
> 00014|pyrt|DBG:Loading a component description file
> 'nox/netapps/monitoring/meta.json'.
> 00015|pyrt|DBG:Loading a component description file
> 'nox/netapps/topology/meta.json'.
> 00016|pyrt|DBG:Loading a component description file
> 'nox/netapps/switchstats/meta.json'.
> 00017|pyrt|DBG:Loading a component description file
> 'nox/netapps/user_event_log/meta.json'.
> 00018|pyrt|DBG:Loading a component description file
> 'nox/netapps/authenticator/meta.json'.
> 00019|pyrt|DBG:Loading a component description file
> 'nox/netapps/flow_fetcher/meta.json'.
> 00020|pyrt|DBG:Loading a component description file
> 'nox/netapps/discovery/meta.json'.
> 00021|pyrt|DBG:Loading a component description file
> 'nox/netapps/hoststate/meta.json'.
> 00022|pyrt|DBG:Loading a component description file
> 'nox/netapps/route/meta.json'.
> 00023|pyrt|DBG:Loading a component description file
> 'nox/netapps/networkstate/meta.json'.
> 00024|pyrt|DBG:Loading a component description file
> 'nox/netapps/tablog/meta.json'.
> 00025|pyrt|DBG:Loading a component description file
> 'nox/netapps/lavi/meta.json'.
> 00026|pyrt|DBG:Loading a component description file
> 'nox/netapps/tests/meta.json'.
> 00027|pyrt|DBG:Loading a component description file
> 'nox/netapps/storage/meta.json'.
> 00028|pyrt|DBG:Loading a component description file
> 'nox/netapps/storage/t/meta.json'.
> 00029|pyrt|DBG:Loading a component description file
> 'nox/netapps/routing/meta.json'.
> 00030|pyrt|DBG:Loading a component description file
> 'nox/netapps/bindings_storage/meta.json'.
> 00031|pyrt|DBG:Loading a component description file
> 'nox/netapps/bindings_storage/t/meta.json'.
> 00032|pyrt|DBG:Loading a component description file
> 'nox/netapps/data/meta.json'.
> 00033|pyrt|DBG:Loading a component description file
> 'nox/webapps/webservice/meta.json'.
> 00034|pyrt|DBG:Loading a component description file
> 'nox/webapps/miscws/meta.json'.
> 00035|pyrt|DBG:Loading a component description file
> 'nox/webapps/webserver/meta.json'.
> 00036|messenger_core|DBG:messenger TCP interface bound to port 2703
> 00037|dht-storage|DBG:Creating a table: bindings_host
> 00038|dht-storage|DBG:Creating a table: bindings_user
> 00039|dht-storage|DBG:Creating a table: bindings_dladdr
> 00040|dht-storage|DBG:Creating a table: bindings_link
> 00041|dht-storage|DBG:Creating a table: bindings_location
> 00042|pycomponent|DBG:Importing Python module
> nox.netapps.bindings_storage.pybindings_storage
> 00043|dht-storage|DBG:Creating a table: user_event_log
> 00044|dht-storage|DBG:Creating a table: user_event_log_names
> 00045|pycomponent|DBG:Importing Python module
> nox.netapps.data.datatypes_impl
> 00046|pycomponent|DBG:Importing Python module
> nox.netapps.data.datacache_impl
> 00047|pycomponent|DBG:Importing Python module
> nox.netapps.user_event_log.pyuser_event_log
> 00048|pycomponent|DBG:Importing Python module
> nox.netapps.discovery.discovery
> 00049|pycomponent|DBG:Importing Python module
> nox.netapps.monitoring.monitoring
> 00050|monitoring|DBG:Simple monitoring started!
> 00051|monitoring|DBG:updated clock: 1
> 00052|monitoring|DBG:Finished configuring monitoring
> 00053|nox|DBG:Application installation report:
> 00054|nox|DBG:built-in event dispatcher:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00055|nox|DBG:lavi links:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'jsonmessenger' OK
>
> 00056|nox|DBG:pyuser_event_log:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'user_event_log' OK, 'pydatatypes' OK, 'pydatacache'
> OK, 'python' OK
>
> 00057|nox|DBG:topology:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'discovery' OK
>
> 00058|nox|DBG:datapathmem:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00059|nox|DBG:hosttracker:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00060|nox|DBG:lavi_switches:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'lavi nodes' OK, 'datapathmem' OK
>
> 00061|nox|DBG:pydatatypes:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'datatypes' OK, 'python' OK
>
> 00062|nox|DBG:switch_management:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00063|nox|DBG:user_event_log:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'storage-backend' OK, 'bindings_storage' OK,
> 'datatypes' OK
>
> 00064|nox|DBG:link event:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00065|nox|DBG:hostip:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00066|nox|DBG:lavi_swlinks:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'lavi links' OK, 'datapathmem' OK, 'topology' OK
>
> 00067|nox|DBG:messenger_core:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00068|nox|DBG:storage-common:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00069|nox|DBG:built-in DSO deployer:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00070|nox|DBG:discovery:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'link event' OK, 'pybindings_storage' OK,
> 'pyuser_event_log' OK, 'python' OK
>
> 00071|nox|DBG:jsonmessenger:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'messenger_core' OK
>
> 00072|nox|DBG:bindings_storage:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'storage-backend' OK, 'datatypes' OK, 'data_cache' OK
>
> 00073|nox|DBG:lavi nodes:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'jsonmessenger' OK
>
> 00074|nox|DBG:data_cache:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'datatypes' OK
>
> 00075|nox|DBG:python:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00076|nox|DBG:monitoring:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'python' OK, 'lavi_switches' OK, 'lavi_swlinks' OK,
> 'lavi nodes' OK, 'python' OK
>
> 00077|nox|DBG:storage-backend:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'storage-common' OK
>
> 00078|nox|DBG:pydatacache:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'data_cache' OK, 'python' OK
>
> 00079|nox|DBG:switch:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
> 00080|nox|DBG:pybindings_storage:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies: 'bindings_storage' OK, 'python' OK
>
> 00081|nox|DBG:datatypes:
> Current state: INSTALLED
> Required state: INSTALLED
> Dependencies:
>
> 00082|openflow|DBG:Passive tcp interface bound to port 6633
> 00083|nox|INFO:nox bootstrap complete
> ========
>
> When I *then* start the GUI, clicking on the "Component" button then yields
> a substantial list. Is the component list populated by the components
> appearing in the log message stream? That certainly appears to be the case.
>
> So, it now looks like I have the GUI doing something, but I see no
> topology displayed. Will I only see a topology if I have OpenFlow switches
> connected directly to each other? Should connected hosts show up? Does the
> traceback shown at the top of this message (and below) have anything to do
> with the lack of display? Any time I hit "R" in the GUI, I see the
> following displayed in the terminal window from which I am running it:
>
> ========
> Sending ...{'command': 'request', 'node_type': 'all', 'type': 'lavi',
> 'xid': 12}
> Sending ...{'command': 'request', 'type': 'lavi', 'link_type': 'all',
> 'xid': 13}
> Traceback (most recent call last):
> File "/var/local/src/nox/src/gui/topology.py", line 726, in got_topo_msg
> nodeItem = Node(self, nodeID)
> File "/var/local/src/nox/src/gui/topology.py", line 38, in __init__
> self.setFlag(QtGui.QGraphicsItem.ItemSendsGeometryChanges)
> AttributeError: type object 'QGraphicsItem' has no attribute
> 'ItemSendsGeometryChanges'
> ========
>
> Thanks to everyone for helping me to get this far. The tool looks
> promising, if I can figure out how to make it give up the rest of its
> display secrets. :-)
>
> /Chris
>
> On 11/10/2010 05:42 PM, Kyriakos Zarifis wrote:
>
> Hi there,
>
> Unfortunately I can't reproduce this, so some additional information
> would help. Do you get any errors on the shell where you started the GUI?
>
> Also, what do you see when you click on the "components" button at the
> bottom of the left sife panel of the GUI?
>
> Regards,
> Kyriakos
>
> On Wed, Nov 10, 2010 at 12:06 PM, Christopher J. Tengi
> <<te...@cs.princeton.edu>
> te...@cs.princeton.edu> wrote:
>
>> KK,
>> What components must be included on the nox_core command line in order
>> for nox-gui.py to be able to talk to it? Are there any components that must
>> *not* be included? For example, I tried this:
>>
>> ./nox_core -i ptcp:6633 \
>> switch switch_management \
>> hostip hosttracker \
>> lavi monitoring \
>> discovery topology \
>> messenger jsonmessenger
>>
>> but the GUI displays nothing useful in either window, and pressing the
>> "Send" button only results in a "jsonmessenger is not running" message in
>> the left-side window.
>>
>> Thanks,
>> /Chris
>>
>>
>> On 10/21/2010 02:31 AM, kk yap wrote:
>>
>>> Hi El,
>>>
>>> Try the instructions here? <http://noxrepo.org/noxwiki/index.php/NOX_GUI>
>>> http://noxrepo.org/noxwiki/index.php/NOX_GUI
>>>
>>> Regards
>>> KK
>>>
>>>
>>> On 20 October 2010 13:18, el beckhov< <beck...@gmail.com>
>>> beck...@gmail.com> wrote:
>>>
>>>> hi,
>>>> i'm a student in montreal (canada)
>>>> i'm new with nox and i have some difficulty to download and try the GUI
>>>> can you please help me ?
>>>> thank you
>>>> PS: i don't know how to access the Destiny branch of the noxrepo
>>>>
>>> _______________________________________________
>>> nox-dev mailing list
>>> <nox-dev@noxrepo.org>nox-dev@noxrepo.org
>>> <http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org>
>>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>>
>>
>> _______________________________________________
>> nox-dev mailing list
>> <nox-dev@noxrepo.org>nox-dev@noxrepo.org
>> <http://noxrepo.org/mailman/listinfo/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
>
>
_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
