You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yet another IPAM-related Network enhancement. Currently calling the next_network or next_address methods on a Network object will only show you eligible network objects, but will not actually create them.
Let's think about implementing an object flag or alternative endpoint that will allocate or reserve the networks in the same call.
Maybe it could be as simple as implementing support for POST to allocate/reserve, where GET only shows you what is available?
For example:
See the next two (2) available /28 networks:
GET /api/networks/1/next_network/?prefix_length=28&num=2
Automatically allocate the next two (2) available /28 networks:
POST /api/networks/1/next_network/?prefix_length=28
The text was updated successfully, but these errors were encountered:
User can send a post request to next_network and next_address
actions. If it is a post request, then the action will
get the networks or addresses and then save them in as network
objects in the db
User can send a post request to next_network and next_address
actions. If it is a post request, then the action will
get the networks or addresses and then save them in as network
objects in the db
Yet another IPAM-related Network enhancement. Currently calling the
next_network
ornext_address
methods on a Network object will only show you eligible network objects, but will not actually create them.Let's think about implementing an object flag or alternative endpoint that will allocate or reserve the networks in the same call.
Maybe it could be as simple as implementing support for
POST
to allocate/reserve, whereGET
only shows you what is available?For example:
See the next two (2) available
/28
networks:Automatically allocate the next two (2) available
/28
networks:The text was updated successfully, but these errors were encountered: