Fix #223: Enhance Network "get_next" methods to optionally allocate/reserve at the same time

[rmhasan]

Users 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 as network objects in the database as allocated. If the user sends the reserve flag and sets it as true, then it will be saved in the reserved state.

[rmhasan]

Hi @nickpegg I added the following changes

• I removed setting is_ip from the next_network and next_address views.
• In model.Network, for the is_ip field I set editable to False.
• In the next_network and next_address views, I use the RESERVED and ALLOCATED constants from the model.Network class
• In the next_network and next_address views, I moved the network.get_next_network function call out of the if clause, and set the as_objects paramter to True. Also I removed the else clause
• Also take a look at dropbox/pynsot#132. It allows users to send post requests to next_network and next_address

EDIT:

• Also in the Interface model functions get_ancestors and get_descendants, I am removing a separate list for id's. This change makes the functions more space efficient.

[jathanism]

@rmhasan We miss you! <3

[rmhasan]

Hi @jathanism, sorry I've been gone for so long. I implemented the changes you asked for, please take a look when you get a chance.

[jathanism]

@rmhasan Awesome! Welcome back. This is great! We'll go ahead and get this released soon. :)