perfSONAR User Q&A and Other Discussion

[Humberto Galiza <>]

Sorry, I didn’t realize there was another thread discussing the same subject.


Humberto Galiza ..::.. Senior Network Engineer
AmLight: http://www.amlight.net
AMPATH (ASN 20080): http://www.ampath.net
P:+55 (19) 3787-3367 
M:+55 (19) 971-445-570 
Skype: humbertogaliza

> On Mar 9, 2016, at 12:58 PM, Christopher J. Tengi 
> <>
>  wrote:
> 
> We are using IP-based authentication on our MA, and I noticed today that we 
> were getting a number of “401 UNAUTHORIZED” errors for an endpoint that I 
> *thought* I had added for IP auth. So, I got onto the MA and tried using 
> the list command (after doing the python27 shuffle).  Here are the results:
> 
> ==========
> (esmond)[root@perfsonar-ma-2
>  esmond]# python esmond/manage.py list
> System check identified some issues:
> 
> WARNINGS:
> api.IfRef.ipAddr: (fields.W900) IPAddressField has been deprecated. Support 
> for it (except in historical migrations) will be removed in Django 1.9.
>       HINT: Use GenericIPAddressField instead.
> api.LSPOpStatus.dstAddr: (fields.W900) IPAddressField has been deprecated. 
> Support for it (except in historical migrations) will be removed in Django 
> 1.9.
>       HINT: Use GenericIPAddressField instead.
> api.LSPOpStatus.srcAddr: (fields.W900) IPAddressField has been deprecated. 
> Support for it (except in historical migrations) will be removed in Django 
> 1.9.
>       HINT: Use GenericIPAddressField instead.
> ==========
> 
> If there is another way to list the users/hosts I’ve added for IP-based 
> authentication, I’d be happy to use it, but I *think* this is what I’m 
> supposed to use, right? Assuming that this may be upgrade-related, please 
> let me know what I can do to help resolve this issue. If it’s me, just slap 
> me.  :-)
> 
> Thanks,
> /Chris
>