Commissioning/decommissioning networks in orchestrated or software-defined computing environments

1. A server computer comprising:

a processing system comprising at least one processing unit storing applications and data; wherein the server computer commissions/decommissions networks and provisions the said networks to one or more orchestration solutions;

wherein the one or more orchestration solutions and the server computer constitute a client-server architecture;

wherein the processing system comprises program code instructions instructing the processing system to implement the following features:

a user interface for the management of the server computer, wherein the user interface provides access to data managed by the server computer;

a web-based application programming interface that supports service oriented architecture [“SOA”]; and

a network management logic that dynamically assigns and releases networks and provisions the said networks to one or more orchestration solutions and the web-based application programming interface,

wherein the network management logic dynamically assigns and releases network blocks and individual network prefixes, networks, subnetworks and microsegments within each network block.

2. The server computer of claim 1 , wherein the network management logic processes a request in which a network requested and assigns the requested network from a network block if at least one of the following conditions are true:

the request specifies a network block or prefix that has been tagged to the network user;

the server computer has configured a default bitmask, which is available in a network block tagged to the network user;

the request indicates an IP address or bitmask and the requested network and/or a public network of a size corresponding to the IP address or bitmask is available; and

the server computer has been configured with a default bitmask, and a network with a size corresponding to the default bitmask is available in at least one public network block.

3. The server computer of claim 2 , configured to manage network blocks of which part is managed by techniques other than the orchestration solution.

4. The server computer of claim 1 , wherein the server computer, responsive to detecting that a previously assigned network is no longer being used, releases the previously assigned network.

5. The server computer of claim 4 , wherein the server computer performs said detecting by tracking actual usage of the previously assigned network.

6. The server computer of claim 1 , wherein the processing system further comprises program code instructions instructing the processing system to implement the following features:

dynamically assigning and releasing Internet Protocol [“IP”] resources to a plurality of hosts via the one or more orchestration solutions and the web-based application programming interface;

creating at least one unique IP resource for each of two or more hosts, wherein the two or more hosts are nodes of networks with overlapping address spaces, and

wherein the at least one unique IP resource is based on a combination of a name of a private network of a respective one of the two or more hosts, and an IP address within that private network.

7. A server computer comprising:

a processing system comprising at least one processing unit storing applications and data;

wherein the server computer commissions/decommissions networks to be activated/deactivated by one or more SDN controllers;

wherein the one or more SDN controllers and the server computer constitute a client-server architecture;

wherein the processing system comprises program code instructions instructing the processing system to implement the following features:

a user interface for remote management of the SDN controller, wherein the user interface provides access to data managed by the SDN controller;

a web-based client connector that communicates with an application programming interface of the SDN controller; and

a network management logic that dynamically assigns and releases networks to be activated/deactivated by one or more SDN controllers,

wherein the network management logic dynamically assigns and releases network blocks and individual network prefixes, networks, subnetworks and microsegments within each network block.

8. The server computer of claim 7 , wherein the network management logic processes a request in which a network requested and assigns the requested network from a network block if at least one of the following conditions are true:

the request specifies a network block or prefix that has been tagged to the network user;

the server computer has configured a default bitmask, which is available in a network block tagged to the network user;

the request indicates an IP address or bitmask and the requested network and/or a public network of a size corresponding to the IP address or bitmask is available; and

the server computer has been configured with a default bitmask, and a network with a size corresponding to the default bitmask is available in at least one public network block.

9. The server computer of claim 8 , configured to manage network blocks of which part is managed by techniques other than the SDN controller.

10. The server computer of claim 7 , wherein the server computer, responsive to detecting that a previously assigned network is no longer being used, releases the previously assigned network.

11. The server computer of claim 10 , wherein the server computer performs said detecting by tracking actual usage of the previously assigned network.

12. The server computer of claim 7 , wherein the processing system further comprises program code instructions instructing the processing system to implement the following features:

dynamically assigning and releasing Internet Protocol [“IP”] resources to a plurality of hosts via the one or more orchestration solutions and the web-based application programming interface;

creating at least one unique IP resource for each of two or more hosts, wherein the two or more hosts are nodes of networks with overlapping address spaces, and

wherein the at least one unique IP resource is based on a combination of a name of a private network of a respective one of the two or more hosts, and an IP address within that private network.

13. A method comprising:

using a server computer having processing system comprising at least one processing unit storing program code instructions and data to commission/decommission networks and provisions the said networks to one or more orchestration solutions, wherein the one or more orchestration solutions and the server computer constitute a client-server architecture;

wherein execution program code instructions in the processing system instructing the processing system to implement the following features:

a user interface for the management of the server computer, wherein the user interface provides access to data managed by the server computer;

a web-based application programming interface that supports service oriented architecture [“SOA”]; and

a network management logic that dynamically assigns and releases networks and provisions the said networks to one or more orchestration solutions and the web-based application programming interface,

wherein the network management logic dynamically assigns and releases network blocks and individual network prefixes, networks, subnetworks and microsegments within each network block.

14. A method comprising:

using a server computer having processing system comprising at least one processing unit storing program code instructions and data to commission/decommission networks to be activated/deactivated by one or more SDN controllers, wherein the one or more SDN controllers and the server computer constitute a client-server architecture;

wherein execution program code instructions in the processing system instructing the processing system to implement the following features:

a user interface for remote management of the SDN controller, wherein the user interface provides access to data managed by the SDN controller;

a web-based client connector that communicates with an application programming interface of the SDN controller; and

a network management logic that dynamically assigns and releases networks to be activated/deactivated by one or more SDN controllers,

wherein the network management logic dynamically assigns and releases network blocks and individual network prefixes, networks, subnetworks and microsegments within each network block.

15. A computer-readable memory storing program code instructions for a server computer having a processing system comprising at least one processing unit to commission/decommission networks and provisions the said networks to one or more orchestration solutions, wherein the one or more orchestration solutions and the server computer constitute a client-server architecture; wherein execution of the program code instructions stored in the computer-readable memory instruct the processing system to implement:

a user interface for the management of the server computer, wherein the user interface provides access to data managed by the server computer;

a web-based application programming interface that supports service oriented architecture [“SOA”]; and

a network management logic that dynamically assigns and releases networks and provisions the said networks to one or more orchestration solutions and the web-based application programming interface,

wherein the network management logic dynamically assigns and releases network blocks and individual network prefixes, networks, subnetworks and microsegments within each network block.

16. A computer-readable memory storing program code instructions for a server computer having a processing system comprising at least one processing unit to commission/decommission networks to be activated/deactivated by one or more SDN controllers, wherein the one or more SDN controllers and the server computer constitute a client-server architecture; wherein execution program code instructions in the processing system instructing the processing system to implement:

a user interface for the management of the SDN controller, wherein the user interface provides access to data managed by the SDN controller;

a web-based client connector that communicates with an application programming interface of the SDN controller; and

a network management logic that dynamically assigns and releases networks to be activated/deactivated by one or more SDN controllers,

wherein the network management logic dynamically assigns and releases network blocks and individual network prefixes, networks, subnetworks and microsegments within each network block.