Send Netdot-devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."


Today's Topics:

   1. [Netdot - Support #1719] (New) Topology grapherror
      ([email protected])
   2. [Netdot - Feature #1720] (New) wireless product
      ([email protected])
   3. [Netdot - Feature #1721] (New) machine type
      ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Sun, 6 Jan 2013 13:34:22 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Support #1719] (New) Topology
        grapherror
To: [email protected], [email protected],
        [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1719 has been reported by Ahmad  Hassan.

----------------------------------------
Support #1719: Topology grapherror 
https://osl.uoregon.edu/redmine/issues/1719

Author: Ahmad  Hassan
Status: New
Priority: High
Assignee: Carlos Vicente
Category: Netdot
Target version: 1.0.2
Resolution: 


find the attached error picture that showing when try to open the topology 
graph 

error 
topology_graph.html produced the following error:


Cannot find root device: localhost

please your advice 


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

Message: 2
Date: Sun, 6 Jan 2013 13:58:10 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1720] (New) wireless
        product
To: [email protected], [email protected],
        [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1720 has been reported by Ahmad  Hassan.

----------------------------------------
Feature #1720: wireless product  
https://osl.uoregon.edu/redmine/issues/1720

Author: Ahmad  Hassan
Status: New
Priority: Normal
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.0.2
Resolution: 


Hi,

is it possible to add  Radwin & Wavion & engenius to the the product list, I 
tried to add  Radwin Microwave link it didn't show any parameters such as radio 
frequency , wireless interface status , radio info.

please your advice 


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

Message: 3
Date: Mon, 7 Jan 2013 07:32:32 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1721] (New) machine type
To: [email protected], [email protected],
        [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1721 has been reported by Ahmad  Hassan.

----------------------------------------
Feature #1721: machine type 
https://osl.uoregon.edu/redmine/issues/1721

Author: Ahmad  Hassan
Status: New
Priority: High
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 
Resolution: 


hi, 

Would be useful to develop tab for the Machines types ( change device or edit 
device type ) & devices category.

thanks 


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel


End of Netdot-devel Digest, Vol 70, Issue 5
*******************************************

Reply via email to