IP Library Patent Application 18195836
Patent Application
App. No. 18/195,836

DEPLOYMENT OF NETWORK MANAGEMENT SERVICES IN PUBLIC CLOUD

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
18/195,836
Abstract

Some embodiments provide a method for deploying network management services for a group of datacenters. From a tenant of a network management system deployed in a container cluster of the public cloud, the method receives (i) a definition of a group of datacenters for the network management system to manage and (ii) a selection of a set of network management services from a plurality of network management services offered by the network management service. For each respective selected network management service, the method defines a respective namespace of the container cluster. The method deploys each respective selected network management service as a plurality of microservices in the respective namespace.

Claims (38)

1 . A method for deploying network management services for a group of datacenters, the method comprising:

from a tenant of a network management system deployed in a container cluster of the public cloud, receiving (i) a definition of a group of datacenters for the network management system to manage and (ii) a selection of a set of network management services from a plurality of network management services offered by the network management service; and

for each respective selected network management service, defining a respective namespace of the container cluster; and

deploying each respective selected network management service as a plurality of microservices in the respective namespace.

2 . The method of claim 1 , wherein the method is performed by a multi-tenant service operating in a separate namespace of the container cluster.

3 . The method of claim 2 , wherein the tenant is a first tenant, the group of datacenters is a first group of datacenters, and the set of network management services is a second set of network management services, the method further comprising:

from a second tenant of the network management system, receiving (i) a definition of a second group of datacenters for the network management system to manage and (ii) a selection of a second set of network management services from the plurality of network management services offered by the network management service; and

for each respective network management service of the second set of network management services, defining a respective namespace of the container cluster; and

deploying each respective network management service of the second set of network management services as a plurality of microservices in the respective namespace.

4 . The method of claim 1 , wherein the group of datacenters is a first group of datacenters and the set of network management services is a second set of network management services, the method further comprising:

from the tenant, receiving (i) a definition of a second group of datacenters for the network management system to manage and (ii) a selection of a second set of network management services from the plurality of network management services offered by the network management service;

for each respective network management service of the second set of network management services, defining a respective namespace of the container cluster; and

deploying each respective network management service of the second set of network management services as a plurality of microservices in the respective namespace.

5 . The method of claim 1 , wherein the plurality of network management services comprises at least (i) a policy management service for defining logical network policies for a logical network spanning the group of datacenters and (ii) a network monitoring service for monitoring data flows in the logical network.

6 . The method of claim 1 further comprising defining firewall rules for data communication between the namespaces.

7 . The method of claim 6 , wherein the firewall rules allow communication between the namespaces defined for the set of network management services for the group of datacenters.

8 . The method of claim 6 , wherein defining the firewall rules comprises instructing a cluster controller to define the firewall rules and to specify for container cluster network elements to enforce the firewall rules.

9 . The method of claim 1 , wherein the group of datacenters comprises at least one virtual datacenter implemented in a public cloud and at least one physical on-premises datacenter.

10 . The method of claim 1 , wherein the container cluster is a Kubernetes cluster.

11 . A non-transitory machine-readable medium storing a program which when executed by at least one processing unit deploys network management services for a group of datacenters, the program comprising sets of instructions for:

from a tenant of a network management system deployed in a container cluster of the public cloud, receiving (i) a definition of a group of datacenters for the network management system to manage and (ii) a selection of a set of network management services from a plurality of network management services offered by the network management service; and

for each respective selected network management service, defining a respective namespace of the container cluster; and

deploying each respective selected network management service as a plurality of microservices in the respective namespace.

12 . The non-transitory machine-readable medium of claim 11 , wherein the program is a multi-tenant service executing in a separate namespace of the container cluster.

13 . The non-transitory machine-readable medium of claim 12 , wherein the tenant is a first tenant, the group of datacenters is a first group of datacenters, and the set of network management services is a second set of network management services, the multi-tenant service further comprising sets of instructions for:

from a second tenant of the network management system, receiving (i) a definition of a second group of datacenters for the network management system to manage and (ii) a selection of a second set of network management services from the plurality of network management services offered by the network management service; and

for each respective network management service of the second set of network management services, defining a respective namespace of the container cluster; and

deploying each respective network management service of the second set of network management services as a plurality of microservices in the respective namespace.

14 . The non-transitory machine-readable medium of claim 11 , wherein the group of datacenters is a first group of datacenters and the set of network management services is a second set of network management services, the program further comprising sets of instructions for:

from the tenant, receiving (i) a definition of a second group of datacenters for the network management system to manage and (ii) a selection of a second set of network management services from the plurality of network management services offered by the network management service;

for each respective network management service of the second set of network management services, defining a respective namespace of the container cluster; and

deploying each respective network management service of the second set of network management services as a plurality of microservices in the respective namespace.

15 . The non-transitory machine-readable medium of claim 11 , wherein the plurality of network management services comprises at least (i) a policy management service for defining logical network policies for a logical network spanning the group of datacenters and (ii) a network monitoring service for monitoring data flows in the logical network.

16 . The non-transitory machine-readable medium of claim 11 , wherein the program further comprises a set of instructions for defining firewall rules for data communication between the namespaces.

17 . The non-transitory machine-readable medium of claim 16 , wherein the firewall rules allow communication between the namespaces defined for the set of network management services for the group of datacenters.

18 . The non-transitory machine-readable medium of claim 16 , wherein the set of instructions for defining the firewall rules comprises a set of instructions for instructing a cluster controller to define the firewall rules and to specify for container cluster network elements to enforce the firewall rules.

19 . The non-transitory machine-readable medium of claim 11 , wherein the group of datacenters comprises at least one virtual datacenter implemented in a public cloud and at least one physical on-premises datacenter.

20 . The non-transitory machine-readable medium of claim 11 , wherein the container cluster is a Kubernetes cluster.

Assignments (2)
CHANGE OF NAME Recorded Feb 27, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 066692/0103 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2023
From: SADASIVAN, GANESH; MARGARIAN, PAVLUSH; KUMAR, ABHISHEK; RAJAGOPALAN, RANGANATHAN
To: VMWARE, INC.
Reel/Frame 063606/0685 →