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. REST API: getting the top level ipblocks (Sparks, Alan)
2. Re: REST API: getting the top level ipblocks (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Jul 2016 20:37:02 +0000
From: "Sparks, Alan" <[email protected]>
Subject: [Netdot-users] REST API: getting the top level ipblocks
To: "[email protected]" <[email protected]>
Message-ID:
<cs1pr84mb0008cf74d8d353767f2f0ecaae...@cs1pr84mb0008.namprd84.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Apologize if this is a FAQ, but can't otherwise find the answer.... Is there
a means to query the REST interface for a level of ipblocks? For instance,
the top-level ipblocks? Have been trying to use Python clients, I can get
/all/ the ipblocks returned, or specific ones returned, but no obvious way to
get only the ones that are "top level".
Would like to create a drillable hierarchy of blocks and children, to show
their descriptions, etc. I can get all of them and do the work in the client,
but that "all" request is a slow hit, so was hoping for something a bit more
efficient. Thanks in advance for any tips.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20160719/1330b750/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 19 Jul 2016 16:41:13 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] REST API: getting the top level ipblocks
To: "Sparks, Alan" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Hi Alan,
Good question. The criteria to match top-level blocks is that the parent field
is undefined.
I _think_ that the last time I checked it wasn?t possible to specify ?undef? as
a field value using the REST API.
I don?t really have time right now to fix that, but I?d be very glad to receive
a patch or pull request.
Best regards,
cv
On Jul 19, 2016, at 4:37 PM, Sparks, Alan <[email protected]> wrote:
> Apologize if this is a FAQ, but can?t otherwise find the answer?. Is there
> a means to query the REST interface for a level of ipblocks? For instance,
> the top-level ipblocks? Have been trying to use Python clients, I can get
> /all/ the ipblocks returned, or specific ones returned, but no obvious way to
> get only the ones that are ?top level?.
>
> Would like to create a drillable hierarchy of blocks and children, to show
> their descriptions, etc. I can get all of them and do the work in the
> client, but that ?all? request is a slow hit, so was hoping for something a
> bit more efficient. Thanks in advance for any tips.
> -Alan
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 88, Issue 3
*******************************************
