Translating a network configuration request for a network control apparatus
An enterprise network may be managed by enabling provision of a graphical user interface that shows IP address allocations for the network and that allows a user to configure DHCP scopes, receiving a DHCP scope request based on a user interaction with the graphical user interface, translating the request into a protocol for communicating with a DHCP control server, providing the translated request to the DHCP control server for processing at the DHCP control server, and updating configurations of multiple DHCP servers. The updated configurations may be sent from the DHCP control server to a configuration storage system and the multiple DHCP servers may be enabled to access the updated configurations from the configuration storage system.
1. A method for managing a network, the method performed by one or more processors, including:
receiving, by a client Application Program Interface (“API”), a request to modify a network from a display application, the request received in a first format, the request comprising at least one of a reserve host request and an unreserve host request;
translating, by the client API, the request from the first format into a message of a second format, the second format being a lightweight DNS management protocol (LDMP) for communicating with a network control apparatus, the network control apparatus being a DNS management server;
providing, by the client API, the message of the second format to the network control apparatus to enable an updated configuration for the network, wherein the updated configuration for the network includes updating a configuration of a DNS server to include one of a newly created host reservation and an excluded host that has been unreserved;
validating, by the client API, a response received from the network control apparatus in the second format; and
translating, by the client API, the validated response from the second format into the first format for display by the display application.
2. The method of claim 1 , wherein the message of the second format for communicating with the network control apparatus comprises an XML-based protocol.
3. The method of claim 1 , further comprising:
receiving, by the client API, a request to create, update, or delete a DHCP scope, and
in response to the received request, receiving, by the client API, updates to multiple DHCP servers, the updates including a newly created scope, an updated scope, or a deleted scope based on the received request.
4. The method of claim 1 , further comprising:
receiving, by the client API, a reserve zone request, an unreserve zone request, or an update zone request; and
in response to the received request, receiving, by the client API, from the DNS server, updates to the configuration of the DNS server, the updates including a newly created zone reservation, an updated zone, or an excluded zone that has been unreserved based on the received request.
5. The method of claim 1 , wherein translating the request further comprises:
determining a type of the request using a delegate component of the client API and sending the request type to a generator component of the client API, and
generating a translated request using the generator component of the client API based on the request type.
6. The method of claim 1 , wherein the display application provides a graphical user interface configured to show IP address allocations for the network, and wherein receiving the request to modify the network further comprises:
receiving, by a delegate component of the client API, the request to modify the network from the display application based on a user interaction with the graphical user interface.
7. The method of claim 1 , wherein the first format is at least one of hypertext markup language (HTML) and a Java object.
8. A system for managing a network, the system comprising:
a web layer comprising at least one first computer processor providing a graphical user interface configured to display IP address allocations for a network; and
an application layer comprising at least one second computer processor providing a client Application Program Interface (“API”) that performs operations including:
receiving a request to modify the network from a display application providing the graphical user interface, the request received in a first format, the request comprising at least one of a reserve host request and an unreserve host request;
translating the request from the first format into a message of a second format, the second format being a lightweight DNS management protocol (LDMP) for communicating with a network control apparatus, the network control apparatus being a DNS management server;
providing the message of the second format to the network control apparatus to enable an updated configuration for the network, wherein the updated configuration for the network includes updating a configuration of a DNS server to include one of a newly created host reservation and an excluded host that has been unreserved;
validating a response received from the network control apparatus in the second format; and
translating the validated response from the second format into the first format for display by the display application.
9. The system of claim 8 , wherein the message of the second format for communicating with the network control apparatus comprises an XML-based protocol.
10. The system of claim 8 , further comprising:
receiving, by the client API, a request to create, update, or delete a DHCP scope, and
in response to the received request, receiving, by the client API, updates to multiple DHCP servers, the updates including a newly created scope, an updated scope, or a deleted scope based on the request to modify the network.
11. The system of claim 8 , further comprising:
receiving, by the client API, a reserve zone request, an unreserve zone request, or an update zone request; and
in response to the received request, receiving, by the client API, from the DNS server, updates to the configuration of the DNS server, the updates including a newly created zone reservation, an updated zone, or an excluded zone that has been unreserved based on the received request.
12. The system of claim 8 , wherein translating the request by the client API further comprises:
determining a type of the request using a delegate component of the client API and sending the request type to a generator component of the client API, and
generating a translated request using the generator component of the client API based on the request type.
13. The system of claim 8 , wherein receiving the request to modify the network further comprises:
receiving, by a delegate component of the client API, the request from the display application based on a user interaction with the graphical user interface.
14. A non-transitory computer-readable medium storing instructions that, when executed by a computer comprising one or more processors, cause the computer to perform operations for managing a network comprising:
receiving, by a client Application Program Interface (“API”), a request to modify the network from a display application, the request received in a first format, the request comprising at least one of a reserve host request and an unreserve host request;
translating, by the client API, the request from the first format into a message of a second format, the second format being a lightweight DNS management protocol (LDMP) for communicating with a network control apparatus, the network control apparatus being a DNS management server;
providing, by the client API, the message of the second format to the network control apparatus to enable an updated configuration for the network, wherein the updated configuration for the network includes updating a configuration of a DNS server to include one of a newly created host reservation and an excluded host that has been unreserved;
validating, by the client API, a response received from the network control apparatus in the second format; and
translating, by the client API, the validated response from the second format into the first format for display by the display application.
15. The computer-readable medium of claim 14 , wherein the message of the second format for communicating with the network control apparatus comprises an XML-based protocol.
16. The computer-readable medium of claim 14 , further comprising:
receiving, by the client API, a request to create, update, or delete a DHCP scope, and
in response to the received request, receiving, by the client API, updates to multiple DHCP servers, the updates including a newly created scope, an updated scope, or a deleted scope based on the received request.
17. The computer-readable medium of claim 14 , further comprising:
receiving, by the client API, a reserve zone request, an unreserve zone request, or an update zone request; and
in response to the received request, receiving, by the client API, from the DNS server, updates to the configuration of the DNS server, the updates including a newly created zone reservation, an updated zone, or an excluded zone that has been unreserved based on the received request.
18. The computer-readable medium of claim 14 , wherein translating the request further comprises:
determining a type of the request using a delegate component of the client API and sending the request type to a generator component of the client API, and
generating a translated request using the generator component of the client API based on the request type.
19. The computer-readable medium of claim 14 , wherein the display application provides a graphical user interface configured to show IP address allocations for the network, and wherein receiving the request to modify the network further comprises:
receiving, by a delegate component of the client API, the request from the display application based on a user interaction with the graphical user interface.