VNIC Configuration Database for Virtual Machine Network Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Virtual machines lack control over network configuration parameters and may inadvertently change unauthorized settings, leading to potential network disruptions and security risks.

Innovation Solution

A method and system that allow virtual machines to request changes to network configuration parameters, which are then validated and updated by a virtual network interface card (VNIC) configuration database, ensuring only authorized changes are made and notifying the virtual machine of the changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If virtual machines are given control over network configuration parameters, then ease of operation is improved, but reliability deteriorates due to potential unauthorized changes and network disruptions

Engineering Contradiction:
Improvevirtual machine control over network configurationVSAvoidnetwork stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

A VNIC configuration database is introduced as an intermediary between virtual machines and network configuration parameters. The database stores allowed configuration parameters and their values, acting as a mediator that validates and controls which changes can be applied. When a virtual machine attempts to change a network configuration parameter, the request is checked against the database to ensure it is authorized, thus maintaining reliability while allowing operational flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If virtual machines can change network configuration parameters freely, then adaptability is improved, but object-generated harmful factors worsen due to security risks and network disruptions

Engineering Contradiction:
Improvenetwork configuration flexibilityVSAvoidunauthorized modifications and security risks
Core Design Contradiction:
Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The system applies preliminary anti-action by pre-defining and storing allowed network configuration parameters and their valid values in the VNIC configuration database before any changes are attempted. This preemptive measure establishes a whitelist of authorized configurations, preventing unauthorized modifications before they can occur. The database serves as a preventive control mechanism that blocks harmful changes while allowing legitimate adaptability.

Inventive Principle:
Principle #9Preliminary anti-action

3Reliability

If network configuration changes are strictly controlled, then reliability is improved, but ease of operation deteriorates due to limited virtual machine autonomy

Engineering Contradiction:
Improvenetwork stabilityVSAvoidvirtual machine configuration autonomy
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables self-service by allowing virtual machines to autonomously request and apply network configuration changes, provided those changes are pre-approved in the VNIC configuration database. The virtual machine can independently modify its network configuration without requiring manual administrator intervention for each change, as long as the change is within the authorized parameters stored in the database. This maintains reliability through pre-approval while providing operational autonomy through automated self-configuration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8713202B2Method and system for network configuration for virtual machines
Publication Date: 2014.04.29 SUN MICROSYSTEMS INC
  • US8713202B2 patent drawing
  • US8713202B2 patent drawing
  • US8713202B2 patent drawing

AI summary

A method for changing network configuration parameters that includes generating a request to change a network configuration parameter, where the request is generated by a virtual machine, sending the request to a virtual network interface card (VNIC) associated with the virtual machine, sending the request to a VNIC configuration database associated with the VNIC, determining whether the virtual machine is allowed to change the network configuration parameter, if the virtual machine is allowed to change the network configuration parameter, updating the VNIC configuration database and VNIC to reflect the change in the network configuration parameter, and notifying the virtual machine that the change in network configuration parameter is allowed, and if the virtual machine is not allowed to change the network configuration parameter, dropping the request.