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 - Feature #1713] (Resolved) Option for vlan renaming
([email protected])
2. [Netdot - Bug #1716] (Resolved) REST interface method post is
brocken ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Wed, 2 Jan 2013 11:13:49 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1713] (Resolved) Option for
vlan renaming
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1713 has been updated by Carlos Vicente.
Category set to DeviceManagement
Status changed from New to Resolved
Assignee set to Carlos Vicente
Target version set to 1.0.5
Resolution set to fixed
The code will now only set, not update, VLAN names based on device discovery.
----------------------------------------
Feature #1713: Option for vlan renaming
https://osl.uoregon.edu/redmine/issues/1713#change-3029
Author: Wim Vandersmissen
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.0.5
Resolution: fixed
Netdot automatically renames a vlan when it finds that it's name has changed.
It would be handy to have an option to disable this behaviour. (also this isn't
being logged in the audit log)
Vlan names can differ on different switches (e.g. because of MAB
implementation), but we want to have the name that we specified to be static.
(for now I commented the renaming code)
Alternatively, the vlan rename feature can be enabled but so that it only
renames when the vlan name used on the router (that routes this vlan) is
changed.
--
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: Wed, 2 Jan 2013 11:24:57 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1716] (Resolved) REST interface
method post is brocken
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1716 has been updated by Carlos Vicente.
Status changed from New to Resolved
Assignee set to Carlos Vicente
Target version set to 1.0.5
Resolution set to fixed
Thank you!
----------------------------------------
Bug #1716: REST interface method post is brocken
https://osl.uoregon.edu/redmine/issues/1716#change-3030
Author: Andreas Kunberger
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category:
Target version: 1.0.5
Resolution: fixed
When I try to update an object using Netdot::Client::REST
like
<pre>
my %data = ();
$data{id} = $key ;
$data{info}= "";
eval {$netdot->post("/site/$key", \%data);};
</pre>
(with a valid $key), I get:
Netdot::throw_fatal('Netdot::REST=HASH(0x7ff0b9611388)', 'Missing required
arguments: data') called at /usr/local/netdot/lib/Netdot/REST.pm line 346
It works, if I comment out line 347 of REST.pm on the server:
<pre>
# $self->throw_fatal("Missing required arguments: data");
</pre>
See appended files.
--
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 1
*******************************************
