Physical to virtual network transport function abstraction
First Claim
1. A method, comprising:
- sending, with a virtual machine (“
VM”
) manager, first information to a virtual infrastructure manager (“
VIM”
);
sending, with the VIM, second information to one of a virtualized application manager or an orchestrator;
sending, with the one of the virtualized application manager or the orchestrator, third information to a virtualized application running in a virtual machine or container; and
based on the second information, determining, with one of the virtualized application manager or the orchestrator, whether connectivity to the virtualized application is failing;
based on the determination that connectivity to the virtualized application is failing, performing, with one of the virtualized application manager or the orchestrator, at least one of notifying the virtual infrastructure manager or a host that connectivity to the virtualized application is failing or determining a course of action, wherein the course of action comprises at least one of fixing a connectivity issue, instructing the virtualized application to suspend operation until the connectivity issue is fixed, or passing the connectivity issue through to the virtualized application;
wherein at least one of the first, second, or third information comprises one or more of loss of signal (“
LOS”
) notifications, carrier group alarm (“
CGA”
) notifications, jabber, fragmented frames, functionality information, information on test frames, or information on synthetic frames, wherein the at least one of the first, second, or third information further comprises one or more of alarm indication signal (“
AIS”
) notifications, flow level statistics, label-switched path (“
LSP”
) tunnel status information, switch monitoring (“
SMON”
) counters, remote network monitoring (“
RMON”
), maintenance entity information, ping information, trace router information, loopback information, or information on connectivity, and wherein the flow level statistics comprise statistics related to one or more of utilization, discarded frames, or capacity.
1 Assignment
0 Petitions
Accused Products
Abstract
When the physical network is transitioned into a virtual network, functionality provided by physical ports are no longer available in the virtual machine (“VM”) environments. Physical to virtual network transport function abstraction may be implemented to provide software applications running in the VM with state information or similar information necessary for the software applications to continue running, without the physical ports that would provide such information in a physical system. In some embodiments, a virtual machine manager might send first information to a virtual infrastructure manager, which might send second information to a virtualized application manager or orchestrator. The virtualized application manager or orchestrator might in turn send third information to a virtualized application running in a virtual machine or container. The first, second, and/or third information might include state information (e.g., state change information) that enable software applications running in the VM to continue running, without physical ports.
-
Citations
8 Claims
-
1. A method, comprising:
-
sending, with a virtual machine (“
VM”
) manager, first information to a virtual infrastructure manager (“
VIM”
);sending, with the VIM, second information to one of a virtualized application manager or an orchestrator; sending, with the one of the virtualized application manager or the orchestrator, third information to a virtualized application running in a virtual machine or container; and based on the second information, determining, with one of the virtualized application manager or the orchestrator, whether connectivity to the virtualized application is failing; based on the determination that connectivity to the virtualized application is failing, performing, with one of the virtualized application manager or the orchestrator, at least one of notifying the virtual infrastructure manager or a host that connectivity to the virtualized application is failing or determining a course of action, wherein the course of action comprises at least one of fixing a connectivity issue, instructing the virtualized application to suspend operation until the connectivity issue is fixed, or passing the connectivity issue through to the virtualized application; wherein at least one of the first, second, or third information comprises one or more of loss of signal (“
LOS”
) notifications, carrier group alarm (“
CGA”
) notifications, jabber, fragmented frames, functionality information, information on test frames, or information on synthetic frames, wherein the at least one of the first, second, or third information further comprises one or more of alarm indication signal (“
AIS”
) notifications, flow level statistics, label-switched path (“
LSP”
) tunnel status information, switch monitoring (“
SMON”
) counters, remote network monitoring (“
RMON”
), maintenance entity information, ping information, trace router information, loopback information, or information on connectivity, and wherein the flow level statistics comprise statistics related to one or more of utilization, discarded frames, or capacity. - View Dependent Claims (2, 3, 4)
-
-
5. A system, comprising:
-
a first host computing system, said first host computing system comprising one or more first processors, one or more first hardware components, and a first non-transitory computer readable medium having encoded thereon a first set of instructions that, when executed by the one or more first processors, causes the first host computing system to perform one or more operations, the first set of instructions comprising; instructions to run a virtual machine (“
VM”
);instructions to run a virtualized application on the VM; instructions to run a VM manager to manage the VM; and instructions for the VM to send first information to a virtual infrastructure manager (“
VIM”
);a second host computing system, said second host computing system comprising one or more second processors, one or more second hardware components, and a second non-transitory computer readable medium having encoded thereon a second set of instructions that, when executed by the one or more second processors, causes the second host computing system to perform one or more operations, the second set of instructions comprising;
instructions to run the VIM;instructions for the VIM to send second information to one of a virtualized application manager or an orchestrator; instructions to determine, with one of the virtualized application manager or the orchestrator, whether connectivity to the virtualized application is failing, based on the second information; and instructions to, based on the determination that connectivity to the virtualized application is failing, perform at least one of notifying the virtual infrastructure manager or a host that connectivity to the virtualized application is failing or determining a course of action, wherein the course of action comprises at least one of fixing a connectivity issue, instructing the virtualized application to suspend operation until the connectivity issue is fixed, or passing the connectivity issue through to the virtualized application; a third host computing system, said third host computing system comprising one or more third processors, one or more third hardware components, and a third non-transitory computer readable medium having encoded thereon a third set of instructions that, when executed by the one or more third processors, causes the third host computing system to perform one or more operations, the third set of instructions comprising; instructions to run the one of the virtualized application manager or the orchestrator; and instructions for the one of the virtualized application manager or the orchestrator to send third information to a virtualized application running in a virtual machine or container; wherein at least one of the first, second, or third information comprises one or more of loss of signal (“
LOS”
) notifications, carrier group alarm (“
CGA”
) notifications, jabber, fragmented frames, functionality information, information on test frames, or information on synthetic frames, wherein the at least one of the first, second, or third information further comprises one or more of alarm indication signal (“
AIS”
) notifications, flow level statistics, label-switched path (“
LSP”
) tunnel status information, switch monitoring (“
SMON”
) counters, remote network monitoring (“
RMON”
), maintenance entity information, ping information, trace router information, loopback information, or information on connectivity, and wherein the flow level statistics comprise statistics related to one or more of utilization, discarded frames, or capacity. - View Dependent Claims (6, 7, 8)
-
Specification