To accommodate time division control of virtual local area networks (VLANs) by multiple virtual applications

Abstract

The disclosed method defines VLAN slots for one or more VLANs within an HCI environment. A management resource can control access of virtual applications to each VLAN according to the VLAN slots, where only one virtual application can connect to a VLAN during a VLAN slot. The disclosed method can define a VLAN slot for each of a plurality of virtual applications. The VLAN slots can be dynamically defined, where a duration of the VLAN slots can be recalculated at each VLAN cycle. The duration of the VLAN slot for a particular virtual application can be determined based on a number of packets transmitted by the virtual application during a previous VLAN cycle. Each VLAN slot can include an active interval for transmitting packets and an inactive interval. Each active interval can include a fixed duration base interval and a variable duration dynamic interval.

Description

Technical Field

[0001] This disclosure relates to the management of information processing systems, and more specifically, to the management of virtualized applications communicating via virtualized local area networks. Background Technology

[0002] As the value and use of information continue to increase, individuals and businesses are seeking alternative ways to process and store information. One option available to users is an information processing system. Information processing systems typically process, compile, store, and / or communicate information or data for business, personal, or other purposes, allowing users to leverage the value of this information. Because technology and information processing needs and requirements can vary between different users or applications, information processing systems can also vary in terms of what information is processed, how it is processed, how much information is processed, stored, or communicated, and how quickly and efficiently it can be processed, stored, or communicated. Variations in information processing systems allow them to be general-purpose or configured for specific users or purposes (e.g., financial transaction processing, flight booking, enterprise data storage, or global communications). Furthermore, information processing systems can include a variety of hardware and software components that can be configured to process, store, and communicate information, and can include one or more computer systems, data storage systems, and networking systems.

[0003] Information processing systems can be configured with hyperconverged infrastructure (HCI), typically using standard hardware, including x86-based servers as a non-limiting example. For example, in the context of a data center, HCI can be broadly defined as an information technology (IT) implementation that natively integrates all data center functions, including compute, storage, and networking, within a virtualized platform operated and monitored through a unified management console. HCI environments can create a very large number of virtual applications within a single Layer 2 domain (e.g., a single Ethernet network). However, due to the 12-bit VLAN ID (VID) specified by IEEE 802.1Q, Ethernet networks cannot support more than 4096 Virtual Local Area Networks (VLANs). Therefore, HCI environments may experience or exhibit VLAN scarcity and / or contention. Summary of the Invention

[0004] Based on the teachings disclosed herein, the resource management methods and systems disclosed address common problems associated with a potentially excessive number of virtualized computing resources competing for a potentially limited number of virtualized network / access resources within an HCI or similar environment. The disclosed system can divide a time domain into multiple time slots corresponding to multiple virtualized computing resources. Within any one of these time slots, only one VAPP can connect to a VID. Scripts can be used to dynamically and periodically control connections based on network usage or packet traffic. The disclosed system may include a management resource configured to perform the disclosed resource management operations. The management resource can define time slots for one or more virtualized network resources, which, as an illustrative and non-limiting example, include one or more Virtual Local Area Networks (VLANs), each associated with a VLAN identifier (VID). Each of the multiple virtualized computing resources, including virtual machines (VMs) and virtual applications (VAPPs) operating within an HCI environment, can be associated with a corresponding VID. In at least one embodiment, the management resource defines a time slot, referred to herein as a VLAN time slot, for each computing resource associated with a VID. The sum of all VLAN time slots defined for a specific VID can be referred to as a VLAN period in this document. Management resources can control access to VLANs, ensuring that each virtual application associated with a VLAN can access the VLAN during one time slot of each VLAN period, and that no more than one virtual application can access the VLAN during any time slot.

[0005] In some implementations, VLAN time slots can be dynamically defined, where the duration of a VLAN time slot can be recalculated for each VLAN period. The duration of a VLAN time slot for a particular virtual application can be determined at least in part based on the number of packets transmitted or otherwise processed by the particular virtual application during one or more previous VLAN periods. As shown above, each VLAN time slot can be associated with a corresponding virtual application. Additionally, each VLAN time slot can include an active interval and an inactive interval during which one or more packets can be transmitted and packet transmission can be disabled during the inactive interval. In such implementations, each active interval can include a base interval with a fixed duration and a dynamic interval with a variable duration.

[0006] The duration of a dynamic interval for a specific virtual application may be based at least in part on the number of packets transmitted by the specific virtual application during one or more previous VLAN periods. Additionally, the duration of a dynamic interval for a specific virtual application may be based at least in part on the packet ratio of the specific virtual application, where the packet ratio indicates the ratio of packets transmitted by the specific virtual application during one or more VLAN periods to the total number of packets transmitted during one or more previous VLAN periods. Furthermore, the duration of a dynamic interval for a specific virtual application may be equal to the product of the packet ratio of the specific application during previous VLAN periods and the sum of all dynamic intervals of said previous VLAN periods.

[0007] An HCI environment can include and / or support multiple distinct VLANs corresponding to multiple VIDs, and in such an environment, the exposed time-slot-based access control method can be executed independently for each distinct VID. For example, different VLAN time slots can be defined for each of the multiple VIDs.

[0008] The technical advantages of this disclosure will be apparent to those skilled in the art from the accompanying drawings, description, and claims included herein. The objects and advantages of the embodiments will be realized and obtained through the elements, features, and combinations particularly pointed out in the claims.

[0009] It should be understood that the foregoing general description and the following detailed description are merely examples and explanations, and not limitations on the claims set forth in this disclosure. Attached Figure Description

[0010] A more complete understanding of this embodiment and its advantages can be obtained by referring to the following description taken in conjunction with the accompanying drawings, in which the same reference numerals indicate the same features, and wherein:

[0011] Figure 1 A block diagram of a hyperconverged infrastructure (HCI) environment including one or more HCI clusters is shown, wherein each HCI cluster may include one or more HCI nodes;

[0012] Figure 2 The elements of an HCI node are shown;

[0013] Figure 3 An exemplary information processing system is shown;

[0014] Figure 4 This is a block diagram showing two VAPPs, where each VAPP contains two VMs connected to a VLAN;

[0015] Figure 5 This shows a large number of VAPP contentions in a relatively small number of VLANs;

[0016] Figure 6 A flowchart illustrating the disclosed resource management method based on the disclosed teachings is shown; and

[0017] Figure 7 An exemplary implementation of VLAN timeslots based on the disclosed teachings is shown. Detailed Implementation

[0018] Exemplary implementation schemes and their advantages are explained by reference. Figures 1 to 7 To obtain the best understanding. The same numbers are used to indicate identical and corresponding parts, unless otherwise explicitly stated.

[0019] For the purposes of this disclosure, an information processing system may include any tool or set of tools operable to calculate, classify, process, transmit, receive, retrieve, generate, switch, store, display, indicate, detect, record, reproduce, dispose of, or utilize information, intelligence, or data of any form for commercial, scientific, control, entertainment, or other purposes. For example, an information processing system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device, and may vary in size, shape, performance, functionality, and price. An information processing system may include memory, one or more processing resources such as a central processing unit (“CPU”), a microcontroller, or hardware or software control logic. Additional components of the information processing system may include one or more storage devices, one or more communication ports for communicating with external devices, and various input / output (“I / O”) devices (such as a keyboard, mouse, and video display). The information processing system may also include one or more buses operable to transmit communication between various hardware components.

[0020] Additionally, the information processing system may include firmware for controlling and / or communicating with, for example, hard disk drives, network circuitry, memory devices, I / O devices, and other peripheral devices. For example, a management program and / or other components may include firmware. As used in this disclosure, firmware includes software embedded in an information processing system component for performing predefined tasks. Firmware is typically stored in non-volatile memory or memory that does not lose stored data upon power failure. In some embodiments, firmware associated with an information processing system component is stored in non-volatile memory accessible to one or more information processing system components. In the same or alternative embodiments, firmware associated with an information processing system component is stored in non-volatile memory dedicated to and including as a part of that component.

[0021] For the purposes of this disclosure, a computer-readable medium may include any tool or set of tools that can retain data and / or instructions for a period of time. A computer-readable medium may include, but is not limited to: storage media such as direct access storage devices (e.g., hard disk drives or floppy disks), sequential access storage devices (e.g., magnetic tape drives), compact optical discs, CD-ROMs, DVDs, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and / or flash memory; and communication media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and / or optical carrier waves; and / or any combination of the foregoing.

[0022] For the purposes of this disclosure, information processing resources can be broadly defined as any component system, apparatus or device of an information processing system, including but not limited to processors, service processors, basic input / output systems (BIOS), buses, memory, I / O devices and / or interfaces, storage resources, network interfaces, motherboards and / or any other components and / or elements of the information processing system.

[0023] In the following description, details are illustrated by way of example to facilitate discussion of the disclosed subject matter. However, it will be apparent to those skilled in the art that the disclosed embodiments are exemplary and not exhaustive of all possible embodiments.

[0024] Throughout this disclosure, the hyphenated form of the reference numerals refers to a specific instance of an element, while the non-hyphenated form refers to an element in general. Thus, for example, "Apparatus 12-1" refers to an instance of a class of apparatuses that can be collectively referred to as "Apparatus 12," and any one of the apparatuses therein can be generally referred to as apparatus "12."

[0025] As used herein, when two or more elements are referred to as “coupled” to each other, such a term indicates that such two or more elements are in electronic communication, mechanical connection, whether indirect or direct, with or without an intermediate element.

[0026] Before describing the public features for monitoring and managing event messages in a distributed computing environment, an exemplary HCI platform suitable for implementing these features is provided. Referring now to the accompanying drawings, Figure 1 and Figure 2 An exemplary information processing system 100 is shown. Figure 1 and Figure 2 The information processing system 100 shown includes a platform 101 communicatively coupled to a platform administrator 102. Figure 1The platform 101 shown is an HCI platform in which computing, storage, and networking resources are virtualized to provide software-defined information technology (IT) infrastructure. Administrator 102 can be any computing system with functions for overseeing the operation and maintenance of hardware, software, and / or firmware elements associated with the HCI platform 101. Platform administrator 102 can interact with the HCI platform 101 via requests to an application programming interface (API) (not explicitly depicted) and responses from said API. In such an implementation, the requests may relate to event messaging monitoring and event messaging status management as described below. Figure 1 The HCI platform 101 shown can be implemented as or within data centers and / or cloud computing resources, characterized by software-defined integration and virtualization of various information processing resources, including but not limited to servers, storage, networking resources, management resources, etc.

[0027] Figure 1 The HCI platform 101 shown includes one or more HCI clusters 106-1 to 106-N, which are communicatively coupled to each other and to a platform resource monitor (PRM) 114. Figure 1 Each HCI cluster 106 shown contains a set of HCI nodes 110-1 to 110-M configured to share information processing resources. In some embodiments, resource sharing may require virtualizing the resources in each HCI node 110 to create a logical pool of those resources, which can then be provisioned on all HCI nodes 110 in the HCI cluster 106 as needed. For example, when considering storage resources, physical devices representing local storage resources on each HCI node 110 (e.g., hard disk drives (HDDs), solid-state drives (SSDs), etc.) can be virtualized to form a clustered distributed file system (DFS) 112. In at least some of these embodiments, the clustered DFS 112 corresponds to a logical pool of storage capacity formed by some or all of the storage within the HCI cluster 106.

[0028] HCI cluster 106 and one or more HCI nodes 110 within the cluster may represent or correspond to one or more of the entire application or multiple microservices implementing the application. As an example, HCI cluster 106 may be dedicated to a specific microservice, where multiple HCI nodes 110 provide redundancy and support high availability. In another example, the HCI nodes 110 within HCI cluster 106 may include one or more nodes corresponding to each microservice associated with a specific application.

[0029] Figure 1The illustrated HCI cluster 106-1 also includes a cluster network device (CND) 108 that facilitates communication and / or information exchange between HCI nodes 110 of HCI cluster 106-1 and other clusters 106, PRM 114, and / or one or more external entities, including, for example, a platform administrator 102. In at least some embodiments, the CND 108 is implemented as a physical device, examples of which include, but are not limited to, a network switch, a network router, a network gateway, a bridge, or any combination thereof.

[0030] PRM 114 can be implemented using one or more servers, each of which can correspond to a physical server in a data center, a cloud-based virtual server, or a combination thereof. PRM 114 can be communicatively coupled to all HCI nodes 110 and platform administrator 102 on all HCI clusters 106 in HCI platform 101. PRM 114 may include a Resource Utilization Monitoring (RUM) service or feature with the ability to monitor Resource Utilization Parameters (RUP) associated with HCI platform 101.

[0031] Figure 2 An exemplary HCI node 110 according to the disclosed subject matter is shown. The HCI node 110 can be implemented using physical devices (e.g., servers (not shown)) to implement a hyperconverged architecture, thereby integrating virtualization, compute, storage, and networking resources into a single solution. The HCI node 110 may include a resource utilization agent (RUA) 202 that is communicatively coupled to network resources 204, compute resources 206, and node controller 216. Figure 2 The node controller 216 shown is coupled to a hypervisor 208 that supports one or more virtual machines (VMs) 210-1 to 210-L, each of which is shown as having an operating system (OS) 214 and one or more applications 212. The node controller 216 shown is further coupled to storage components, including zero or more optional storage controllers 220, such as Small Computer System Interface (SCSI) controllers, and storage components 222.

[0032] In some implementations, the task of RUA 202 is to monitor the utilization of virtualization, compute, storage, and / or network resources on HCI node 110. Therefore, node RUA 202 may include the following functions: monitoring the utilization of network resources 204 to obtain network resource utilization parameters (RUP), monitoring the utilization of compute resources 206 to obtain compute RUP, monitoring the utilization of virtual machines 210 to obtain virtualization RUP, and monitoring the utilization of storage resources 222 to obtain storage RUP. RUA 202 may periodically provide some or all of the RUPs to the Environmental Resource Monitor (ERM) 226 via pull and / or push mechanisms.

[0033] Now for reference Figure 3 , Figure 1 and Figure 2 One or more HCI components shown can be instantiated as by Figure 3 The information processing system 300 shown illustrates physical resources or is instantiated therein. The information processing system includes one or more general-purpose processors or central processing units (CPUs) 301, which are communicatively coupled to memory resources 310 and input / output hubs 320, with various I / O resources and / or components communicatively coupled to the input / output hubs. Figure 3 The I / O resources explicitly depicted include a network interface 340, commonly referred to as a NIC (Network Interface Card), storage resources 330, and additional I / O devices, components, or resources, which, as non-limiting examples, include a keyboard, mouse, monitor, printer, speaker, microphone, etc. The illustrated information processing system 300 includes a baseboard management controller (BMC) 360 that provides out-of-band management resources and other features and services, which may be coupled to a management server (not depicted). In at least some embodiments, the BMC 360 can manage the information processing system 300 even when it is powered off or powered on to a standby state. The BMC 360 may include a processor, memory, an out-of-band network interface separate and physically isolated from the in-band network interface of the information processing system 300, and / or other embedded information processing resources. In some embodiments, the BMC 360 may include or be a component of a remote access controller (e.g., a Dell remote access controller or an integrated Dell remote access controller) or a chassis management controller.

[0034] Figure 4 Exemplary virtualized computing resources are shown that can benefit from the disclosed methods for managing potentially scarce virtualized network resources. More specifically, Figure 4 Two instances of VAPP are shown, including vApp1 401-1 and vApp2 401-2 coupled to VLAN 410. Each of the VAPPs 401 shown includes or contains two VMs 210, where vApp1 401-1 includes or contains VMs 210-1 and 210-2, while vApp2 401-2 includes or contains VMs 210-3 and 210-4. Figure 4As shown, the VAPP 401 combines multiple VMs 210 into different virtualization objects. The VMs 210 associated with VAPP 401 can represent some or all of the microservices providing an enterprise application. As an illustrative example, VAPP 401 may include a first VM 210-1 for providing a front-end web server, a second VM 210-2 for providing an application server, and a third VM (in...) for providing a back-end database server. Figure 4 (Not explicitly described in the text).

[0035] In at least some cases, vApp2401-2 can be created by cloning vApp1 401-1. If the Media Access Control (MAC) address of VM 210 in vApp2 401-2 is not modified, those skilled in the art of networking will recognize the potential for conflicts and ambiguity due to the presence of multiple resources with shared public MAC addresses coupled to Ethernet VLANs. In addition to addressing the problem associated with a potentially large number of virtualization resources contending for a potentially small number of virtualized network resources, the disclosed systems and methods for implementing VLAN slots also address the issue of duplicate MAC addresses by allocating each resource with a shared public address to the corresponding VLAN slot.

[0036] Figure 5 It shows that it may be caused by Figure 5 The previously discussed conflicts and / or contention issues arise from a potentially very large number of virtualized computing resources represented by multiple VAPPs 401, which execute within a Layer 2 domain 501 such as an IEEE 802.3 Ethernet domain, and contend for a relatively small number of virtualized network resources 502, including but not strictly limited to VLANs under IEEE 803.1Q.

[0037] Figure 6 This is a flowchart illustrating a method 600 for managing virtualized network resources, including but not strictly limited to VLANs. The method 600 shown can be adapted for use with VAPP and other virtualized computing resources instantiated within an HCI environment. Figure 1The management resource execution of Platform Administrator 102 or PRM 114, as shown, defines (Operation 602) multiple VLAN time slots for one or more VLANs, where each VLAN time slot can be associated with a unique and corresponding VID. The VLAN time slots defined for a VLAN can include time slots corresponding to each of the multiple instantiated VAPPs associated with the VLAN VID. As an example, if ten (10) instantiated VAPPs are assigned to a specific VID or otherwise associated with a specific VID, the management resource can define ten VLAN time slots for each VLAN period, where each VLAN time slot is associated with a corresponding VAPP in a 1:1 relationship.

[0038] Then, management resources can control access to each VLAN according to the defined VLAN time slots (Operation 604), so that each VAPP associated with a specific VID can access the corresponding VLAN in one and no more than one period of the defined VLAN time slots, and no more than one VAPP can access the VLAN in any period of the defined VLAN time slots. The following is about... Figure 7 An exemplary implementation of VLAN timeslots is described in more detail.

[0039] In at least one implementation, the VLAN timeslots and timeslot-based access control described herein are implemented as Layer 2 or data link layer features. In these implementations, the implementation and management of VLAN timeslots are advantageously transparent to application layer software.

[0040] Now for reference Figure 7 An exemplary implementation of the previously described VLAN timeslots is shown for the hypothetical VLAN 710. Specifically, Figure 7 An exemplary VLAN period 701 is illustrated, comprising three VLAN time slots (702-1, 702-2, and 702-3) corresponding to three instantiated, active, and / or executed VAPPs 704 (VAPP1 704-1, VAPP2 704-2, and VAPP3 704-3) associated with VLAN 710. As depicted, the illustrated VLAN 710 has a VID value of VID1, and the three illustrated VAPPs 704 are configured to use VID1 as the value in the VID field of the header of transmitted packets. Figure 7 The VAPP 704 shown is intended to represent all active VAPPs associated with VLAN 710. For clarity, Figure 7 Only three VAPPS are shown, but a skilled technician will recognize that more than three VAPPS can be associated with a specific VLAN 710.

[0041] Figure 7 Each of the VLAN timeslots 702 shown consists of an active interval 712 and an inactive interval 714. In at least some embodiments, packet transmission and / or processing is permitted during the active interval 712 and prohibited during the inactive interval 714. Therefore, each VAPP 704 can access or connect to VLAN 710 during the active interval 712 of the appropriate VLAN timeslot 702. Figure 7 For example, VAPP1 704-1 can connect to VLAN 710 during the active interval 712 of the first VLAN timeslot 702-1, VAPP2 can connect to VLAN 710 during the active interval 712 of the second VLAN timeslot 702-2, and so on.

[0042] Figure 7 Further illustration shows that each activity interval 712 includes Figure 7 The fixed interval portion marked as basic interval 722 and Figure 7 The variable interval portion, identified as dynamic interval 724, is implemented in a manner that allows the duration of the variable interval to vary over time based on one or more parameters, characteristics, or conditions. As an example, management resources can monitor packet traffic associated with each VAPP over one or more VLAN periods. The management resources can then define the duration of the dynamic interval 724 for each VAPP based on packet traffic relative to packet traffic associated with each of one or more other VAPPs.

[0043] In at least some implementations, management resources can recalculate the duration of the dynamic interval 724 for each VLAN slot 702 based on one or more parameters and a dynamic interval algorithm. In at least one implementation, management resources can access data indicating the total number of packets transmitted during a previous VLAN period, the total duration of the VLAN period, and the number of VAPPs associated with a particular VLAN. Using this data, management resources can determine a total dynamic interval equal to the sum of the durations of each individual dynamic interval 724. This total dynamic interval can then be allocated to the dynamic interval 724 for each VAPP based at least in part on the percentage of total packet traffic handled by the particular VLAN. To illustrate an example of three VAPPs associated with a particular VLAN, after calculating the total dynamic interval for one or more previous VLAN periods, the duration of each dynamic interval 724 for the next VLAN period can be calculated. If the first VAPP transmits 25% of all packet traffic handled by the particular VLAN, then the dynamic interval 724 for the next period can be calculated as 25% of the total dynamic interval for the previous VLAN periods.

[0044] This disclosure covers all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that would be contemplated by those skilled in the art. Similarly, where appropriate, the appended claims cover all changes, substitutions, variations, alterations, and modifications to the exemplary embodiments herein that would be understood by those skilled in the art. Furthermore, references in the appended claims to a device or system or a component of a device or system adapted to, arranged to, capable of, configured to, enabled to, operable to, or operated to perform a particular function cover that device, system, or component, whether or not it is activated, turned on, or unlocked, provided that the device, system, or component is adapted to, arranged to, capable of, configured to, enabled to, operable to, or operated to perform the particular function.

[0045] All examples and conditional language described herein are intended for pedagogical purposes to aid the reader in understanding the principles of this disclosure and the conception of the facilitating technology provided by the inventors, and should be interpreted as not limiting the scope of such specific examples and conditions. Although embodiments of this disclosure have been described in detail, it should be understood that various changes, substitutions, and modifications can be made thereto without departing from the spirit and scope of this disclosure.

Claims

1. A method for managing an information processing system, comprising: Define VLAN time slots for VLANs that correspond to a specific Virtual Local Area Network (VLAN) identifier (VID); as well as Access to the VLAN is controlled according to multiple VLAN time slots, wherein each of the multiple virtual applications (VAPPs) can access the VLAN during one of the multiple VLAN time slots, and wherein no more than one of the multiple VAPPs can access the VLAN during any one of the VLAN time slots, wherein each VLAN time slot is associated with a corresponding virtual application, and wherein each VLAN time slot includes an active interval and an inactive interval, during which one or more packets can be transmitted and during which packet transmission is prohibited; Each active interval includes a basic interval and a dynamic interval, wherein the duration of the basic interval is fixed, while the duration of the dynamic interval is variable, wherein the duration of the dynamic interval for a particular virtual application is at least partially based on the packet ratio of the particular virtual application, wherein the packet ratio indicates the ratio of the packets transmitted by the particular virtual application during one or more VLAN periods to the total number of packets transmitted during one or more previous VLAN periods.

2. The method of claim 1, wherein defining the VLAN timeslot includes defining a VLAN timeslot for each of the plurality of virtual applications for each VLAN period.

3. The method of claim 2, wherein defining the VLAN timeslot includes dynamically defining the VLAN timeslot, wherein the duration of the VLAN timeslot is recalculated for each VLAN period.

4. The method of claim 1, wherein the length of the VLAN timeslot of the particular virtual application is determined at least in part based on the number of packets transmitted by the particular virtual application during one or more previous VLAN periods.

5. The method of claim 1, wherein the duration of the dynamic interval for a particular virtual application is at least in part based on the number of packets transmitted by the particular virtual application during one or more previous VLAN cycles.

6. The method of claim 1, wherein the duration of the dynamic interval of the particular virtual application is equal to the product of the packet ratio of the particular virtual application during a previous VLAN period and the sum of all dynamic intervals of the previous VLAN period.

7. The method of claim 1, wherein the information processing system is configured with a hyperconverged infrastructure (HCI) environment, the HCI environment comprising multiple different VLANs corresponding to multiple VIDs, and wherein a VLAN time slot is defined for each of the multiple VIDs.

8. An information processing system, comprising: Central Processing Unit (CPU); Non-transitory memory resources, communicatively coupled to the CPU, include process-executable program instructions that, when executed by the CPU, cause the information processing system to perform management operations, the management operations including: Define multiple Virtual Local Area Network (VLAN) time slots for a VLAN, wherein the multiple VLAN time slots include VLAN time slots corresponding to each of multiple Virtual Applications (VAPPs) associated with the VLAN; Access to the VLAN is controlled according to the plurality of VLAN time slots, wherein each of the plurality of virtual applications (VAPPs) can access the VLAN during one of the plurality of VLAN time slots, and wherein no more than one of the plurality of VAPPs can access the VLAN during any one of the VLAN time slots, wherein each VLAN time slot is associated with a corresponding virtual application, and wherein each VLAN time slot includes an active interval and an inactive interval, during which one or more packets can be transmitted and during which packet transmission is prohibited; Each active interval includes a basic interval and a dynamic interval, wherein the duration of the basic interval is fixed, while the duration of the dynamic interval is variable, wherein the duration of the dynamic interval for a particular virtual application is at least partially based on the packet ratio of the particular virtual application, wherein the packet ratio indicates the ratio of the packets transmitted by the particular virtual application during one or more VLAN periods to the total number of packets transmitted during one or more previous VLAN periods.

9. The information processing system of claim 8, wherein defining the VLAN timeslot includes defining one VLAN timeslot for each of the plurality of virtual applications for each VLAN period.

10. The information processing system of claim 9, wherein defining the VLAN timeslot includes dynamically defining the VLAN timeslot, wherein the duration of the VLAN timeslot is recalculated for each VLAN period.

11. The information processing system of claim 8, wherein the length of the VLAN timeslot of the particular virtual application is determined at least in part based on the number of packets transmitted by the particular virtual application during one or more previous VLAN periods.

12. The information processing system of claim 8, wherein the duration of the dynamic interval of a particular virtual application is at least in part based on the number of packets transmitted by the particular virtual application during one or more previous VLAN periods.

13. The information processing system of claim 8, wherein the duration of the dynamic interval of a particular virtual application is equal to the product of the packet ratio of the particular virtual application during a previous VLAN period and the sum of all dynamic intervals of the previous VLAN period.

14. The information processing system of claim 8, wherein the information processing system is configured with a hyperconverged infrastructure (HCI) environment, the HCI environment comprising a plurality of different VLANs corresponding to a plurality of VIDs, and wherein a VLAN timeslot is defined for each of the plurality of VIDs.

Images