Enterprise Fabric Server Virtualization for Dynamic Resource Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current server architectures face challenges in dynamically provisioning and managing compute, storage, and network resources efficiently, leading to suboptimal datacenter availability, efficiency, and utilization.
Innovation Solution
The Enterprise Fabric (EF) architecture introduces a hybrid server/multi-layer switch system with virtualized resources, including Virtual Network Interface Controllers (VNICs) and Virtual Input/Output Controllers (VIOCs), enabling dynamic provisioning and management of virtual servers with scalable, coordinated resources and high-bandwidth, low-latency I/O operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional server architectures are used with static resource allocation, then hardware provisioning is straightforward, but datacenter efficiency and resource utilization are suboptimal
Solution Approach 1:
The patent segments physical server resources into virtual components (VNICs, VIOCs, virtual servers) that can be independently managed and allocated. This segmentation enables dynamic resource provisioning while maintaining manageable system complexity through modular architecture.
Solution Approach 2:
The Enterprise Fabric architecture creates a universal resource pool that can serve multiple functions and applications. The same physical infrastructure supports diverse workloads through virtualization, improving datacenter efficiency without proportionally increasing complexity.
2Adaptability or versatility
If dynamic resource provisioning is implemented, then resource utilization improves, but management complexity increases
Solution Approach 1:
The patent introduces an intermediary management layer that abstracts the complexity of dynamic resource provisioning. This layer handles the coordination between physical resources and virtual instances, enabling adaptability while shielding users from management complexity.
Solution Approach 2:
The system implements self-service capabilities where virtual servers can dynamically allocate and manage their own resources through automated provisioning mechanisms. This reduces manual management complexity while maintaining high adaptability.
3Adaptability or versatility
If virtualized resources are used, then resource flexibility increases, but system architecture complexity increases
Solution Approach 1:
The patent merges multiple physical resources into a unified virtualized pool managed through a common fabric architecture. This consolidation provides resource flexibility while managing architecture complexity through integration rather than proliferation of separate systems.
Solution Approach 2:
The system employs dynamic resource allocation where virtual server configurations can be modified in real-time without physical reconfiguration. This dynamic capability provides flexibility while the underlying fabric architecture maintains structural simplicity.
4Productivity
If traditional provisioning methods are used, then initial setup is simple, but scalability and performance modifications are slow
Solution Approach 1:
The patent establishes preliminary virtualized resource pools and fabric infrastructure in advance, enabling rapid provisioning and scaling. The pre-configured virtualization layer allows quick deployment of new services without complex physical reconfiguration.
Solution Approach 2:
The system enables rapid cloning and replication of virtual server configurations through the fabric architecture. Performance and scale modifications can be implemented by copying existing virtual instances rather than building from scratch, maintaining operational simplicity.
Data Source
AI summary
A system is taught in which a module having processing elements can access network and storage interfaces that are external to the module of the processing elements as though those interfaces were located internal to the module of the processing elements. The system may be operated as one or more provisioned servers, each of the provisioned servers including capabilities as identified by a corresponding set of specifications and attributes, according to various embodiments. Typically the specifications (or constraints) and attributes are specified with a Server Configuration File. An Enterprise Server system may be provisioned into any combination and number of servers according to needed processing and I/O capabilities. Each of these servers may include distinct compute, storage, and networking performance. Provisioned servers may be managed similar to conventional servers, including operations such as boot and shutting down.