Issue link: https://read.uberflip.com/i/1173428
On any platform, a shipwide fabric based on InfiniBand and RDMA represents an excellent flexible organic shipboard interconnect "utility." Ship systems integration engineers will have the option to configure protected subnets to build any or all of the aforementioned systems on this utility grid. An Equal Cost Multi-Path (ECMP) or Open Shortest Path First (OSPF) fabric based on 200 Gb Infiniband would likely last through several generations of technology insertion and will be the right choice for future systems, such as CESARS-SPECS, wherein large, simultaneous, and continuous super high-resolution video and infrared imagery will need to be captured, stored, and processed in real time to cue defensive weapons systems against stealthy, optically guided antiship missiles, unmanned aerial vehicles (UAVs), and even smaller threats like jet skis and rubber rafts Disaggregation Once deployed to the platform, a HyperScale fabric enables disaggregation of shipboard computing plants, including, disaggregation of: servers storage networks, and even equipment racks. A disaggregation strategy minimizes, or eliminates physical appliances via extreme modularity, composability, and software-defined everything (SDx). For example, servers are no longer part of a monolithic chassis and storage no longer exists local to the servers as islands of storage or within expensive appliances. Equipment racks together with modular subracks effectively represent "hotel" spaces for disaggregated modules, software-defined networks support virtualization of fewer higher-bandwidth pipes, and servers routinely connect to 100 GbE networks. Creating an organic shipboard architecture via the Hyper Infrastructure Navy platforms can leverage these commercial strategies to create an organic shipboard architecture that enables multiple options for hosting mission-critical applications from dedicated bare-metal machines to SDx. We call this the Hyper Infrastructure and its hierarchy is 1. HyperScale 2. HyperCompose 3. HyperConverge Instead of large naval platforms (ship, aircraft, etc.) hosting a plethora of stovepipe or dedicated systems on one or more traditional networks, the larger platform can comprise an interconnect utility with CMERs pre-installed. This organic platform or "utility" will comprise a high-bandwidth, low-latency, and deterministic shipwide data communications fabric (essentially a large, nonblocking crossbar switch) populated with a number of common processing, storage, I/O, and network function modules. We envision these modules being installed virtually anywhere and everywhere on the fabric, which we call the Hyperscale interconnect fabric. 5 Common Modular Rack Industry Standard Architecture Components Module Cooling Method(s) (Forced-Air) Scalable Platform Management System (Zabbix, Redfish, etc) Shock/Vibration Isolation System Power Distribution, Cooling, and Rack Interconnect Fabrics (e.g., Ethernet, PCIe, InfiniBand) Power Distribution Method(s) (AC/DC) MicroCluster (Express) Fabric (PCIe) COMMON COMMON Common Modular Subrack Common Module Library Processor Module(s) IO Module(s) Storage Module(s) Specific Fuction or OEM Module(s) Figure 3: Common Modular Rack. Modular Commonality minimizes the need for redundancy in infrastructure design and component selection, qualification, environmental certification and non value- add shipboard industrial work