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

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-users
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-users digest..."


Today's Topics:

   1. Re: RESTful interface questions (Matej Vadnjal)
   2. Multiple instances of Netdot (Bill Green)


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

Message: 1
Date: Wed, 13 Feb 2013 10:50:19 +0100
From: Matej Vadnjal <[email protected]>
Subject: Re: [Netdot-users] RESTful interface questions
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 12. 02. 2013 18:12, Patrick Landry wrote:
>
>
> ------------------------------------------------------------------------
>
>
>     On 11. 02. 2013 20:43, Patrick Landry wrote:
>     >  One thing I did find was that in order to update a host you
>     need to
>     > include the 'name' parameter in the data portion of the POST.
>     Unless
>     > this is a requirement of the Netdot-Client-REST module only, the
>     > manual is incomplete in this regard.
>     Thats odd. It works for me. I tried this:
>
> I am attempting to update a host (DNS record). It is easy to code it 
> such that it works.
>
Ah, sorry I misunderstood. I thought you were changing devices. As for 
updating hosts, you are right. If you don't supply a name parameter it 
is assumed to be undefined. If the user changing the record has non 
admin privileges hostname validation fails. If the user is an admin the 
record is updated and the hostname is set to blank.

I opened a bug report: https://osl.uoregon.edu/redmine/issues/1736 
<https://osl.uoregon.edu/redmine/issues/1736>. There is also a fix attached.


--
Matej Vadnjal
Arnes



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

Message: 2
Date: Wed, 13 Feb 2013 18:54:27 +0000
From: Bill Green <[email protected]>
Subject: [Netdot-users] Multiple instances of Netdot
To: "[email protected]" <[email protected]>
Message-ID:
        
<3930ce50306d1d42847d5d84b264497201159...@exchange-2010.ops.tcpipservices.com>
        
Content-Type: text/plain; charset="us-ascii"

Hi folks.

Can somebody point me in the direction of how to run multiple instances of 
Netdot? We currently manage different networks for various customers, and 
running separate instances seems like the most obvious way to keep vlans / 
RFC1918 space from colliding.

I've got a separate DB / user set up, but my ignorance of Mason is keeping me 
from understanding how to separate the functional part.

I'd greatly appreciate a hint.

Netdot is a fantastic tool, btw. You guys do great work.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130213/7ffab26e/attachment-0001.html
 

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

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


End of Netdot-users Digest, Vol 51, Issue 5
*******************************************

Reply via email to