Hierarchical network managers
US-2016352560-A1 · Dec 1, 2016 · US
US10601637B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10601637-B2 |
| Application number | US-201916403253-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 3, 2019 |
| Priority date | May 21, 2013 |
| Publication date | Mar 24, 2020 |
| Grant date | Mar 24, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Some embodiments provide a network system that includes several host machines for hosting virtual machines, divided into several different domains. The network system includes several local domain management servers. A first local domain management server of a first domain is for (i) initiating creation of a set of distributed virtual switch ports associated with a particular logical network identifier on a host machine within its domain and (ii) attaching a first virtual machine on the host machine to a created port associated with the particular logical network identifier in order for the first virtual machine to send traffic over the logical network. The network system includes a second level management server for coordinating the use of logical network identifiers between multiple different logical domain management servers in order for the first virtual machine to communicate via the logical network with a second virtual machine in a second domain.
Opening claim text (preview).
We claim: 1. For a local physical domain manager at a particular physical domain of a plurality of physical domains of a hosting system spanned by a logical network, a method comprising: receiving instructions from a network management server regarding the logical network, the instructions comprising (i) a set of virtual machines on a set of host machines within the particular physical domain that are in the logical network and (ii) a logical network identifier allocated for the logical network by the network management server, wherein the logical network identifier is used across the plurality of physical domains in order to enable virtual machines in one of the physical domains to communicate via the logical network with virtual machines in the other physical domains; initiating creation of at least one set of distributed virtual switch ports associated with the logical network identifier on the set of host machines; and attaching the set of virtual machines to the set of created ports associated with the logical network identifier in order for the virtual machines to send traffic through the logical network. 2. The method of claim 1 , wherein traffic from a first virtual machine in the logical network to a second virtual machine in the logical network is isolated from other logical networks spanning the physical domain by using the logical network identifier. 3. The method of claim 2 , wherein using the logical network identifier to isolate traffic from other logical networks comprises adding, at a distributed virtual switch, the logical network identifier to packets from the first virtual machine to the second virtual machine in the logical network. 4. The method of claim 1 further comprising: receiving instructions from the network management server for removing a particular virtual machine from the logical network; and detaching the particular virtual machine from a created distributed virtual switch port. 5. The method of claim 1 further comprising: receiving instructions from the network management server for adding a particular virtual machine to the logical network; and attaching the particular virtual machine to a created distributed virtual switch port in order for the particular virtual machine to send traffic through the logical network. 6. The method of claim 1 further comprising sending status information about the logical network to the network management server. 7. The method of claim 6 further comprising: identifying the set of hosts associated with the logical network using the database; requesting status information about the logical network from the identified set of hosts; and receiving status information from the identified set of hosts, wherein the status information sent to the network management server is based on the status information received from the set of hosts. 8. The method of claim 7 , wherein the local physical domain manager aggregates the status information received from the set of hosts to produce aggregated status information and the status information sent to the network management server is the aggregated status information. 9. The method of claim 6 , wherein the status information is sent in response to a request for status information about the logical network received from the network management server. 10. A non-transitory machine readable medium storing a program executable by at least one processing unit of a local physical domain manager at a particular physical domain of a plurality of physical domains of a hosting system spanned by a logical network, the program comprising sets of instructions for: receiving instructions from a network management server regarding the logical network, the instructions comprising (i) a set of virtual machines on a set of host machines within the particular physical domain that are in the logical network and (ii) a logical network identifier allocated for the logical network by the network management server, wherein the logical network identifier is used across the plurality of physical domains in order to enable virtual machines in one of the physical domains to communicate via the logical network with virtual machines in the other physical domains; initiating creation of at least one set of distributed virtual switch ports associated with the logical network identifier on the set of host machines; and attaching the set of virtual machines to the set of created ports associated with the logical network identifier in order for the virtual machines to send traffic through the logical network. 11. The non-transitory machine readable medium of claim 10 , wherein traffic from a first virtual machine in the logical network to a second virtual machine in the logical network is isolated from other logical networks spanning the physical domain by using the logical network identifier. 12. The non-transitory machine readable medium of claim 11 , wherein using the logical network identifier to isolate traffic from other logical networks comprises adding, at a distributed virtual switch, the logical network identifier to packets from the first virtual machine to the second virtual machine in the logical network. 13. The non-transitory machine readable medium of claim 10 , wherein the local physical domain manager comprises a database storing an association of the logical network identifier with the set of host machines in the particular physical domain. 14. The non-transitory machine readable medium of claim 13 , wherein the program further comprises a set of instructions for sending status information about the logical network to the network management server. 15. The non-transitory machine readable medium of claim 14 , wherein the program further comprises sets of instructions for: identifying the set of hosts associated with the logical network using the database; requesting status information about the logical network from the identified set of hosts; and receiving status information from the identified set of hosts, wherein the status information sent to the network management server is based on the status information received from the set of hosts. 16. A non-transitory machine readable medium storing a program executable by at least one processing unit of a network management server, the program for creating a logical network that spans a plurality of physical domains within a hosting system, the program comprising sets of instructions for: receiving a specification for a logical network, the specification comprising (i) a plurality of virtual machines to connect to the logical network and (ii) a set of at least two physical domains in which the virtual machines are located; from a range of available logical network identifiers stored by the management server, allocating a particular logical network identifier for the specified logical network; and sending instructions to a local physical domain manager at each of the physical domains in which the virtual machines are located in order for the local physical domain manager to attach the virtual machines in its domain to the logical network using the allocated logical network identifier. 17. The non-transitory machine readable medium of claim 16 further comprising a set of instructions for removing the particular logical network identifier from the range of available logical network identifiers. 18. The non-transitory machine readable medium of claim 16 further comprising a set of instructions for storing the specification for the logical network and the allocated logical network identifier in a database for repl
Real-time or near real-time messaging, e.g. instant messaging [IM] · CPC title
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
Active monitoring, e.g. heartbeat, ping or trace-route · CPC title
Discovery or management of network topologies · CPC title
comprising hierarchical management structures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.