Techniques for a configuration mechanism of a virtual switch

Examples include techniques for a configuration mechanism of a virtual switch. Example techniques include monitoring a database including parameter to configure a virtual switch at a computing platform hosting a plurality of virtual machines or containers. Changes to one or more parameters may cause changes in allocations of computing resources associated with supporting the virtual switch.

BACKGROUND

Computing platforms such as those commonly used in today's telecommunication networks may have hardware platforms arranged for fixed functions and dimensioned for worst case requirements related to latency, maximum supported input/output (I/O) ports and highest supported data bandwidth. These worst case requirements may be set at computing platform design time. In some examples, each computing platform (e.g., a blade) may be arranged to support a single network function for a telecommunication network. The single network function may include multiple software applications. Typically, applications and associated hardware to support these applications may be tightly coupled and deployed as a single network function.

In contrast to computing platforms deployed in today's telecommunication networks, network function virtualization (NFV) computing platforms to be deployed in future telecommunication and/or data center networks may be designed to host many different virtual network functions (VNFs) as well as many different application types running in or being executed by virtual machines (VMs) and/or containers to support VNFs. As a result, requirements for NFV computing platforms may vary and are likely not fully defined at time of computing platform design or definition. Also, each hosted application may have its own service level agreement (SLA) requirements such as requirements for latency, bandwidth, compute resources or I/O. A VNF may be supported by several VMs and in a fluid NFV environment, these supporting VMs and/or containers may have peer VMs or containers located on a same hosting computing platform or remotely deployed on a different and/or a remote hosting computing platform.

DETAILED DESCRIPTION

As contemplated in the present disclosure, a VNF may be supported by one or more VMs in a fluid NFV environment. A fluidity of deployment of VMs to support VNFs may lead to dimensioning challenges for configuring computing platforms hosting these VMs. Dimensioning may refer to how physical or virtual resources at a computing platform may be allocated at a computing platform to host VMs supporting one or more VNFs. These dimensioning challenges may include, but are not limited to, unpredictable latency changes based on a load to a computing platform directly related to VNF workloads that are not always known in advance. For example, memory load latency increases when memory bandwidth utilization increases for a given VNF workload. In a case were a computing platform hosts multiple VMs (e.g., associated with multiple tenants), the VMs may impact each other's performance and potentially violate SLAs based on their respective VNF workloads. Also, multi-platform types of networks such as those included in today's data centers and possible used in NFV telecommunication networks may have computing platforms including central processing units (CPUs) that differ in various ways such as, but not limited to, number of cores, operating frequency, instruction set or I/O processing capabilities. Other resources of these multi-platform types may also differ such that impacts from CPU and/or other resource variability may be difficult to determine.

A virtual switch hosted by a computing platform may be a key piece of infrastructure to enable VMs supporting VNFs to meet performance requirements. Inter-VM communications and/or ingress and egress data packets transverse a virtual switch. However, due to the difficulties associated with determining resource needs to meet performance requirements, a virtual switch may be manually configured to use a fixed number of computing resources such as a fixed number of CPU cores. Use of a fixed number of physical computing resources may be akin to traditional approaches of fixing hardware at time of computing platform design and is problematic to meeting performance requirements in a fluid VM deployment environment.

FIG. 1illustrates an example first system. As shown inFIG. 1, the example first system includes system100. Also as shown inFIG. 1, system100includes a computing platform101coupled to a network170. In some examples, as shown inFIG. 1, computing platform101may couple to network170via a network communication (comm.) channel175and through a network IO device110(e.g., a network interface card (NIC)) having one or more ports connected or coupled to network comm. channel175.

According to some examples, computing platform101, as shown inFIG. 1, may include circuitry120, memory130, a network (NW) I/O device driver140, an operating system150or one or more application(s)160. In some examples, as shown inFIG. 1, circuitry120may communicatively couple to memory130and network I/O device110via comm. link155. Although not shown inFIG. 1, in some examples, operating system150, NW IO device driver140or application(s)160may be implemented at least in part via cooperation between one or more memory devices included in memory130(e.g., volatile memory devices) and elements of circuitry120such as processing cores112-1to112-m, where “m” is any positive whole integer greater than 2. Application(s)160may be associated with one or more VNFs supported by VMs (not shown) hosted by computing platform101.

In some examples, computing resources of computing platform101such as, but not limited to, circuitry120, memory130and network I/O device110may be allocated to enable one or more VMs to support one or more VNFs. As described more below, allocation of these computing resources may be related to virtual switch (vSwitch) dimensioning triggered by requirements changes (e.g., initiated by a network management system). Also, as described more below, dimensioning may be based on a dynamic check that self-tests a computing platform's ability to meet performance requirements (e.g., SLAs) using a representative set of data traffic routed before actually applying configuration changes.

According to some examples, dimensioning may also be based on a static check that may not involve a self-test, but rather may statically estimate, via models, whether performance requirements may be met before applying configuration changes. Choosing dynamic or static checks may be based, at least in part, on potential impacts of self-tests degrading performance below an acceptable level during these self-tests such that a static estimate may be used to avoid the unacceptable degradation of performance.

In some examples, computing platform101, may include, but is not limited to, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, or combination thereof. Also, circuitry120having processing cores122-1to122-mmay include various commercially available processors, including without limitation an AMD® Athlon®, Duron® and Opteron® processors; ARM® application processor embedded and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Qualcomm® Snapdragon® processors; Intel® Atom®, Celeron®, Core (2) Duo®, Core i3, Core i5, Core i7, Itanium®, Pentium®, Xeon® or Xeon Phi® processors; and similar processors.

According to some examples, memory130may be composed of one or more memory devices or dies which may include various types of volatile and/or non-volatile memory. Volatile memory may include, but is not limited to, random-access memory (RAM), Dynamic RAM (D-RAM), double data rate synchronous dynamic RAM (DDR SDRAM), static random-access memory (SRAM), thyristor RAM (T-RAM) or zero-capacitor RAM (Z-RAM). Non-volatile memory may include, but is not limited to, non-volatile types of memory such as 3-D cross-point memory that may be byte or block addressable. These byte or block addressable non-volatile types of memory may include, but are not limited to, memory that uses chalcogenide phase change material (e.g., chalcogenide glass), multi-threshold level NAND flash memory, NOR flash memory, single or multi-level phase change memory (PCM), resistive memory, nanowire memory, ferroelectric transistor random access memory (FeTRAM), magnetoresistive random access memory (MRAM) that incorporates memristor technology, spin transfer torque MRAM (STT-MRAM), or a combination of any of the above, or other non-volatile memory types.

FIG. 2illustrates an example system200. In some examples, as shown inFIG. 2, system200includes a computing platform201having vSwitch resources220, VMs230-1to230-N (where “n” is any positive whole integer greater than 2) and a vSwitch dimensioning manager240. As described more below, vSwitch dimensioning manger240includes logic and/or features to determine whether to apply configuration changes to vSwitch resources220and still meet performance requirements associated with one or more VNF workloads232-1to232-N supported by respective VMs230-1to230-N. Although not shown inFIG. 2, containers implemented by VMs230-1to230-N and may also support VNF workloads232-1to232-N. As described more below, the configuration changes may be responsive to parameter changes indicated in a table such as table262maintained in a database such as database260. Table262may have been changed or modified to indicate the parameter changes through a network management entity such as network management system250. For these examples, other elements such as an operating system, network I/O device driver, circuitry, memory or network I/O devices as described for system100inFIG. 1may be included in a computing platform similar to computing platform201, but these other elements are not shown in order to simplify the description of particular processes or operations for system200.

In some examples, VNF workloads232-1to232-n, may represent workloads associated with respective applications for VNFs supported by elements of computing platform201. For these examples, vSwitch resources220may be allocated or dimensioned to support intra-VM communications and/or process ingress/egress data packets received or transmitted from computing platform201in order to maintain or complete VNF workloads231-1to232-nbased on meeting performance requirements (e.g., SLAs). According to some examples, VNF workloads232-1to232-nmay be related to fulfilling a function, task or service that may include, but is not limited to, firewalling, domain service, network address translation, session border controller, caching, video-optimizer, content distribution network, wireless base station or radio network controller or wireless local area network access point or gateway. VNF workloads232-1to232-2may be related to all or least a portion of one or more functions, tasks or services supported by respective VMs230-1to230-N.

According to some examples, logic and/or features of vSwitch dimensioning manager240such as update logic242and/or change logic244may be arranged to facilitate determinations of whether or not to apply configuration changes to vSwitch resources220. For these examples, update logic242may be capable of monitoring table262maintained in database260and determine whether changes to parameter to configure a vSwitch have changed as indicated in table262such that a new dimensioning of vSwitch Resources220is needed. For example, network management system250may want to migrate a VM to computing platform201or may want to replace a current VM with another VM having a higher VNF workload. Both examples may require a need for adjustments or dimensioning of vSwitch Resources220.

In some examples, as described more below, logic and/or features of vSwitch dimensioning manger240such as change logic244may perform dynamic or static checks to determine whether configuration changes may be applied to vSwitch resources220while maintaining performance requirements for completing VNF workloads232-1to232-N. Performance requirements may be based on SLA requirements and may include, but are not limited to, meeting latency, data throughput, error rate thresholds or I/O bandwidth requirements and/or may be based on meeting a power budget allocated to computing platform201.

According to some examples, database260may operate as an Open vSwitch Database (OVSDB). For these examples, update logic242or network management system250may use protocols described in Request for Comments (RFC) 7047, The Open vSwitch Database Management Protocol, published in December 2013, to access table262. For these examples, table262may be an Open_vSwitch table including configuration information for configuring vSwitch resources220to handle network traffic according to a specification published by the Open Networking Foundation (ONF) such as the OpenFlow Switch specification, Version 1.5.1, published in March, 2015, and/or later versions of this OpenFlow Switch specification.

FIG. 3illustrates an example partial table300. According to some examples, partial table300may illustrate at least a portion of table262maintained in database260shown inFIG. 2and mentioned above. As mentioned previously, table262may include vSwitch configuration information and may be arranged according the Open vSwitch specification. For these examples, partial table300indicates parameters to configure a vSwitch such as parameters for flow-limit, I/O bandwidth and workload maximum and respective values310,330and340. All or at least a portion of these parameters of partial table300may be maintained or included in a larger Open_vSwitch table. In some examples, values310,330or340may be modified or changed through network management system250to reflect parameters for vSwitch operations to support a migration of a new VM (with or without containers) to computing platform201as well as maintaining support for current VMs hosted by computing platform201.

According to some examples, value310for the flow-limit parameter may indicate a maximum number of flows allowed in a data path flow table (e.g., a forwarding information base (FIB) table) maintained at computing platform201. The flow-limit parameter may be based on real-time network conditions to ensure that computing platforms coupled to a network do not disproportionately overburden a network managed by network management system250. For example, value310may have a default value of 200,000 that may be raised or lowered based on real-time network conditions. For a vSwitch operating according to the Open vSwitch specification, value310for the flow-limit may be indicated in a “flow-limit” field of the Open_vSwitch table.

In some examples, value330for I/O bandwidth may indicate an amount of I/O bandwidth needed to support vSwitch operations for handling VMs to be hosted by computing platform201. Value330, for example may indicate a given I/O bandwidth (e.g., 40 gigabits per second (Gbps) needed to support the vSwitch operations. For a vSwitch operating according to the Open vSwitch specification, value330for I/O bandwidth may also be indicated in a field of the Open_vSwitch table. The field may be an “I/O_bandwidth” field or similar field that indicates an I/O bandwidth.

According to some examples, value340for workload maximum may indicate an expected peak or maximum load placed on vSwitch resources220in order to support vSwitch operations for handling VMs to be hosted by computing platform201. Value340, for example may indicate estimated or expected packet processing loads if all VNF workloads are at their highest level and thus place a peak or maximum load on vSwitch resources220. For example, value340may indicate a maximum throughput for all VMs executing their respective VNF workloads during peak or maximum load. For a vSwitch operating according to the Open vSwitch specification, value340for the workload maximum may be also be indicted in a field of the Open_vSwitch table. The field may be a “workload_maximum” field or similar field that indicates a workload maximum.

FIG. 4illustrates an example logic flow400. In some examples, elements of systems100and200as shown inFIGS. 1 and 2and the parameters shown inFIG. 3may be used to illustrate example operations related to logic flow400. The described example operations are not limited to implementations on systems100or200or to the parameters of partial table described therein forFIGS. 1-3.

Starting at block410(Read Database), logic and/or features of vSwitch dimensioning manager240such as update logic242may read database260in order to monitor table261. Moving to decision block415(Updates>Previous Values?), update logic242may determine if any updates or modifications have been made to table262. In some examples, if an update has been made to table262, update logic242may then determine whether the updates increased at least some values of table262. For example, an increasing of one or more values310,330or340or partial table300. For these examples, increasing values may indicate that at least some vSwitch dimensioning may be needed to accommodate a possible migration of a new VM or an increased VNF workload for VMs hosted by computing platform201. If updates are greater than previous values for one or more of values310,330or340, logic flow moves to decision block415. Otherwise, process flow400is done as no vSwitch dimensioning may be needed due to same or lower parameters indicated in values310,330or340.

Moving from decision block415to decision block420(Dynamic or Static Check?), logic and/or features of vSwitch dimensioning manager240such as change logic244may determine whether a dynamic or static check is to be conducted. In some examples, a static check may be desired if vSwitch resources220are at or near peak load to support VMs230-1to230-N and a self test may possibly degrade performance of VNF workloads232-1to232-N below SLA or other types of performance requirements. For these examples, logic flow moves to block425. Otherwise, if vSwitch resources220are not at or near peak load and/or a self test can be performed and still meet performance requirement, logic flow moves to block440.

Moving from decision block420to block425(No Self Test), logic and/or features of vSwitch dimensioning manager240such as change logic244may implement a static check that does not include a self test. In some examples, a number of cores required to meet changes to values310,330or340of partial table300may be estimated statically be modelling behavior of vSwitch resources220. One example of a model for when value310for flow-limit has increased is indicated below in example equation (1).

Example Equation (1)

Moving to decision block430(Required Core Count Available?), change logic244may determine whether CPU cores are available from among those allocated to vSwitch resources220to meet what the static check indicated as being needed. Using example equation (1) above as a model, a given flow-limit increase for value310may require more CPU cores than available to vSwitch resources220. For this examples, no configuration changes would be made based at least on the change to value310. If additional CPU cores are available, logic flow400moves to block435.

Moving from decision block430to block435(Apply Changes), logic and/or features of vSwitch dimensioning manager240such as change logic244may apply changes to vSwitch resources220to utilize more CPU cores in order to adjust to the change in at least value310.

Moving from decision block420to block440, (Initiate Self Test for Representative Workload), logic and/or features of vSwitch dimensioning manager240such as change logic244may cause a dynamic check that includes initiation of a self test for a representative workload or workloads for VMs230-1to230-N. In some examples, the representative workload may reflect peak demand loads (e.g., indicated in value340) for VNF workloads232-1to232-N and may also include a VNF workload supported by a possibly migrated VM.

Moving to decision block445(Meet Requirement(s)?), change logic244may determine whether computing platform201can meet one or more performance requirement(s) (e.g., SLAs) based on the self test. For example, if performance requirements for latency, data throughput, error rates or available data bandwidth are met, logic flow400moves to block435and change logic244applies the changes. Otherwise, logic flow400moves to block450.

Moving from decision block445to block450(Calculate Performance Delta Feedback to Self Test), logic and/or features of vSwitch dimensioning manager240such as change logic244may calculate a performance delta feedback to determine what vSwitch resources220were lacking in computing platform201's configuration that caused performance requirements to not be met. For examples, insufficient CPU cores to meet latency or data throughput requirements.

Moving to block455(Calculate Core Count to Meet Requirements), change logic244may calculate a core count to meet the performance requirements. For example, estimate (e.g., via use of a model) a number of additional CPU core resources to add to vSwitch resources220to lower latency times or increase data throughput in order to meet the performance requirements.

Moving to decision block460(Required Core Count Available?), change logic244may determine whether CPU cores are available from among those allocated to vSwitch resources220to meet what was estimated to be needed. If additional CPU cores are available, logic flow400moves to block440for initiation of another self test that now includes more CPU cores for vSwitch resources220. If additional CPU cores are not available, no change is made and logic flow400is done.

As indicated above, logic flow400pertains to a particular vSwitch resource included in vSwitch resources220based on CPU core counts available. Examples are not limited to vSwitch dimensioning based on only CPU core counts. Other vSwitch resources included in vSwitch resources220such as, but not limited to memory allocations, CPU cache way allocations, I/O port allocations, etc. may also be considered when deciding whether to apply changes based on static or dynamic checks following updates or changes to parameter values maintained in partial table300. Also, logic flow400describes VMs as supporting VNF workloads, examples are not limited to only VMs supporting VNF workloads. Examples, may include combinations of VMs and containers supporting a same or different VNF workloads.

FIG. 5illustrates an example block diagram for apparatus500. Although apparatus500shown inFIG. 5has a limited number of elements in a certain topology, it may be appreciated that the apparatus500may include more or less elements in alternate topologies as desired for a given implementation.

According to some examples, apparatus500may be supported by circuitry520. For these examples, circuitry520may be circuitry for a computing system, e.g., circuitry120as shown inFIG. 1. The circuitry for the computing system support one or more VMs and/or containers that may separately or collectively execute VNF workloads. Circuitry520may be arranged to execute one or more software or firmware implemented modules, components or logic522-a(module, component or logic may be used interchangeably in this context). It is worthy to note that “a” and “b” and “c” and similar designators as used herein are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value for a=2, then a complete set of software or firmware for modules, components or logic522-amay include logic522-1or522-2. The examples presented are not limited in this context and the different variables used throughout may represent the same or different integer values. Also, “logic”, “module” or “component” may also include software/firmware stored in computer-readable media, and although types of logic are shown inFIG. 5as discrete boxes, this does not limit these types of logic to storage in distinct computer-readable media components (e.g., a separate memory, etc.).

According to some examples, circuitry520may include a processor, processor circuit or processor circuitry. Circuitry520may be generally arranged to execute one or more software components522-a. Circuitry520may be any of various commercially available processors, including without limitation an AMD® Athlon®, Duron® and Opteron® processors; ARM® application, embedded and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Atom®, Celeron®, Core (2) Duo®, Core i3, Core i5, Core i7, Itanium®, Pentium®, Xeon®, Xeon Phi® and XScale® processors; and similar processors. According to some examples circuitry520may also include an application specific integrated circuit (ASIC) and at least some logic522-amay be implemented as hardware elements of the ASIC. According to some examples, circuitry520may also include a field programmable gate array (FPGA) and at least some logic522-amay be implemented as hardware elements of the FPGA.

According to some examples, apparatus500may include an update logic522-1. Update logic522-1may be executed by circuitry520to monitor a database arranged to maintain parameters to configure a virtual switch at the computing platform including circuitry520. Update logic522-1may determine whether the parameters to configure the virtual switch have been changed to indicate that additional computing resources at the computing platform are to be allocated to the virtual switch. In some examples, database changes may be included in database changes505.

In some examples, apparatus500may include a change logic522-2. Change logic522-2may be executed by circuitry520to implement a static check or a dynamic check to determine whether or not to allocate the additional computing resources, the static check to include an estimation of the additional computing resources needed based on a static model, the dynamic check to include running a self test for a representative workload executed by the plurality of VMs to determine whether the additional computing resources are needed. Change logic522-2may also cause an allocation of the additional computing resources to configure the virtual switch based on the static or dynamic check. What additional computing resources to be allocated may be included in applied changes515. In some examples, the static model may be maintained by change logic522-2in models524-a(e.g., in a look up table (LUT)).

In some examples, change logic522-2may determine that implementing the dynamic check causes the plurality of VMs or the virtual switch to fail to meet one or more performance requirements to include a latency threshold requirement, a data throughput requirement or an error rate requirement. Change logic522-2may then implement the static check based on the determination that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet the one or more performance requirements. For these examples, change logic522-2may maintain the one or more performance requirements in performance requirement(s)524-b(e.g., in a LUT).

Various components of apparatus800and a device or node implementing apparatus800may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Example connections include parallel interfaces, serial interfaces, and bus interfaces.

A logic flow may be implemented in software, firmware, and/or hardware. In software and firmware embodiments, a logic flow may be implemented by computer executable instructions stored on at least one non-transitory computer readable medium or machine readable medium, such as an optical, magnetic or semiconductor storage. The embodiments are not limited in this context.

FIG. 6illustrates an example of a logic flow600. Logic flow600may be representative of some or all of the operations executed by one or more logic, features, or devices described herein, such as apparatus600. More particularly, logic flow600may be implemented by at least update component522-1or change component522-2.

According to some examples, logic flow600at block602may monitor, at a processor circuit, a database maintaining parameters for configuring a virtual switch at a computing platform hosting a plurality of VMs or containers. For these examples, Update logic may monitor the database.

In some examples, logic flow600at block604may determine whether the parameters for configuring the virtual switch have been changed to indicate that additional computing resources at the computing platform are to be allocated to the virtual switch. For these examples, update logic622-1may determine whether the parameters have been changed.

In some examples, logic flow600at block606may implement a static check or a dynamic check to determine whether or not to allocate the additional computing resources, the static check including estimating the additional computing resources needed based on a static model, the dynamic check including running a self test for a representative workload executed by the plurality of VMs or containers to determine whether the additional computing resources are needed. For these examples, change logic622-2may implement the static or dynamic check.

According to some examples, logic flow600at block608may allocate the additional computing resources to configure the virtual switch based on the static or dynamic check. For these examples, change logic622-1may cause the allocation of the additional computing resources.

FIG. 7illustrates an example of a first storage medium. As shown inFIG. 7, the first storage medium includes a storage medium700. The storage medium700may comprise an article of manufacture. In some examples, storage medium700may include any non-transitory computer readable medium or machine readable medium, such as an optical, magnetic or semiconductor storage. Storage medium700may store various types of computer executable instructions, such as instructions to implement logic flow700. Examples of a computer readable or machine readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The examples are not limited in this context.

FIG. 8illustrates an example computing platform800. In some examples, as shown inFIG. 8, computing platform800may include a processing component840, other platform components850or a communications interface860.

According to some examples, processing component840may execute processing operations or logic for apparatus500and/or storage medium700. Processing component840may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, ASICs, programmable logic devices (PLDs), digital signal processors (DSPs), FPGAs, memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, device drivers, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an example is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given example.

In some examples, communications interface860may include logic and/or features to support a communication interface. For these examples, communications interface860may include one or more communication interfaces that operate according to various communication protocols or standards to communicate over direct or network communication links. Direct communications may occur via use of communication protocols or standards described in one or more industry standards (including progenies and variants) such as those associated with the PCIe specification. Network communications may occur via use of communication protocols or standards such those described in one or more Ethernet standards promulgated by the Institute of Electrical and Electronics Engineers (IEEE). For example, one such Ethernet standard promulgated by IEEE may include, but is not limited to, IEEE 802.3-2012, Carrier sense Multiple access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, Published in December 2012 (hereinafter “IEEE 802.3 specification”). Network communication may also occur according to one or more OpenFlow specifications such as the OpenFlow Hardware Abstraction API Specification. Network communications may also occur according to Infiniband Architecture specification.

Computing platform800may be implemented in a server or client computing device. Accordingly, functions and/or specific configurations of computing platform800described herein, may be included or omitted in various embodiments of computing platform800, as suitably desired for a server or client computing device.

Some examples may be described using the expression “coupled” and “connected” along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, descriptions using the terms “connected” and/or “coupled” may indicate that two or more elements are in direct physical or electrical contact with each other. The term “coupled” or “coupled with”, however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

The follow examples pertain to additional examples of technologies disclosed herein.

An example apparatus may include circuitry for a computing platform arranged to host a plurality of VMs or containers. The apparatus may also include update logic for execution by the circuitry to monitor a database arranged to maintain parameters to configure a virtual switch at the computing platform and determine whether the parameters to configure the virtual switch have been changed to indicate that additional computing resources at the computing platform are to be allocated to the virtual switch. The apparatus may also include change logic for execution by the circuitry to implement a static check or a dynamic check to determine whether or not to allocate the additional computing resources. The static check may include an estimation of the additional computing resources needed based on a static model. The dynamic check may include running a self test for a representative workload executed by the plurality of VMs or containers to determine whether the additional computing resources are needed. The update logic may also cause an allocation of the additional computing resources to configure the virtual switch based on the static or dynamic check.

An apparatus of example 1, the change logic to determine that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet one or more performance requirements to include a latency threshold requirement, a data throughput requirement or an error rate requirement. The change logic may implement the static check based on the determination that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet the one or more performance requirements.

The apparatus of example 1, the parameters to configure the virtual switch comprises a flow-limit, input/output bandwidth or a workload maximum.

The apparatus of example 3, the parameters to configure the virtual switch may be changed based on migrating an additional VM or container to the computing platform.

The apparatus of example 1, the additional computing resources may include additional CPU cores, additional memory allocations, additional input/output port allocations or additional CPU cache way allocations.

The apparatus of example 1, the database may be an Open vSwitch Database (OVSDB) arranged to operate in accordance with an OpenFlow Switch specification.

The apparatus of example 6, the parameters to configure the virtual switch may be included in an Open_vSwitch table maintained in the OVSDB.

The apparatus of example 1 may also include a digital display coupled to the circuitry to present a user interface view.

An example method may include monitoring, at a processor circuit, a database maintaining parameters for configuring a virtual switch at a computing platform hosting a plurality of VMs or containers. The method may also include determining whether the parameters for configuring the virtual switch have been changed to indicate that additional computing resources at the computing platform are to be allocated to the virtual switch. The method may also include implementing a static check or a dynamic check to determine whether or not to allocate the additional computing resources. The static check may include estimating the additional computing resources needed based on a static model. The dynamic check may include running a self test for a representative workload executed by the plurality of VMs or containers to determine whether the additional computing resources are needed. The method may also include allocating the additional computing resources to configure the virtual switch based on the static or dynamic check.

The method of example 9 may also include determining that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet one or more performance requirements including a latency threshold requirement, a data throughput requirement or an error rate requirement. The method may also include implementing the static check based on the determination that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet the one or more performance requirements.

The method of example 9, the parameters for configuring the virtual switch may include a flow-limit, input/output bandwidth or a workload maximum.

The method of example 11, the parameters for configuring the virtual switch may be changed based on migrating an additional VM or container to the computing platform.

The method of example 9, the additional computing resources may include additional CPU cores, additional memory allocations, additional input/output port allocations or additional CPU cache way allocations.

The method of example 9, the database comprising an Open vSwitch Database (OVSDB) operating in accordance with an OpenFlow Switch specification.

The method of example 14, the parameters for configuring the virtual switch may be included in an Open_vSwitch table maintained in the OVSDB.

An examples at least one machine readable medium may include a plurality of instructions that in response to being executed by a system may cause the system to carry out a method according to any one of examples 9 to 15.

An example apparatus may include means for performing the methods of any one of examples 9 to 15.

An example at least one machine readable medium may include a plurality of instructions that in response to being executed by a system at a computing platform may cause the system to monitor a database maintaining parameters to configure a virtual switch at the computing platform, the computing platform hosting a plurality of VMs or containers. The instructions may also cause the system to determine whether the parameters to configure the virtual switch have been changed to indicate that additional computing resources at the computing platform are to be allocated to the virtual switch. The instructions may also cause the system to implement a static check or a dynamic check to determine whether or not to allocate the additional computing resources. The static check may include an estimation of the additional computing resources needed based on a static model. The dynamic check may include running a self test for a representative workload executed by the plurality of VMs or containers to determine whether the additional computing resources needed. The instructions may also cause the system to allocate the additional computing resources to configure the virtual switch based on the static or dynamic check.

The at least one machine readable medium of example 18, the instructions may further cause the system to determine that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet one or more performance requirements to include a latency threshold requirement, a data throughput requirement or an error rate requirement. The instructions may also cause the system to implement the static check based on the determination that implementing the dynamic check causes the plurality of VMs, containers or the virtual switch to fail to meet the one or more performance requirements.

The at least one machine readable medium of example 18, the parameters to configure the virtual switch may include a flow-limit, input/output bandwidth or a workload maximum.

The at least one machine readable medium of example 20, the parameters to configure the virtual switch may be changed based on migrating an additional VM or container to the computing platform.

The at least one machine readable medium of example 18, the additional computing resources may include additional CPU cores, additional memory allocations, additional input/output port allocations or additional CPU cache way allocations.

The at least one machine readable medium of example 18, the database may be an Open vSwitch Database (OVSDB) arranged to operate in accordance with an OpenFlow Switch specification.

The at least one machine readable medium of example 23, the parameters to configure the virtual switch may be included in an Open_vSwitch table maintained in the OVSDB.