White Paper

Managing life cycle and network interoperability challenges on Navy platforms

Issue link: https://read.uberflip.com/i/1173428

Contents of this Issue

Navigation

Page 3 of 6

w w w. t m s . m r c y. c o m WHITE PAPER Defining elements of a common modular infrastructure for the Navy To apply these strategies to naval systems, first we need to define a common modular infrastructure. We propose a Navy-standard tactical system infrastructure based on: 1. "HyperScale" Leaf and Spine Interconnect Fabric; 2. Common Modular Equipment Rack (CMER); 3. Common Modular Subrack (CMSR); 4. "HyperComposable" compute, storage, networking, graphics, and special function modules; and 5. Software-defined everything; i.e., virtualization for converged and hyperconverged system-level building blocks. Together, these elements form an enduring foundation for any number of mission-critical weapons, combat, C4ISR, and machinery control systems. These systems will comprise a relatively small set (m) of common compute, storage, and I/O modules (as building blocks) for (n) systems of virtually any size and scope – where (m) is potentially orders of magnitude smaller than (n). See Figure 2: Strategic Hierarchy For existing or legacy network topologies, HyperComposable systems can be deployed in the same way as any contemporary commercial rackmount or bladed server system. For new construction and extensive technology insertion cycles, the adoption of a high-performance, low latency, highly resilient – versus redundant – Infiniband or Ethernet fabric as the core network will further enable the concept of the disaggregated system, and may remain viable for half (or more) of the life of the ship or platform. This strategy is firmly aligned with Modular Open Systems Approach (MOSA) guidelines within both business and technical areas, with particular focus on open modular design; technology insertion; extensibility; reusability; and most importantly, composability. Composability enables configuration of a virtually limitless range of systems from the smallest possible number and type of common compute, I/O, and graphics modules. Any combination of a small set of common modules should be deployable anywhere on a network in virtually any system configuration. (See Figure 3: Common Modular Rack.) Composable modules will include: 1. CMSRs; 2. Common processing modules (e.g., Intel, AMD, Power, ARM); 3. Common I/O modules; 4. Common display modules; 5. Common attached processor module – GPGPU and FPGA; 6. Common network switch modules; 7. Common storage modules – HDD/SSD (SAS, SATA); U.2 NVME; RSSD NVME; and 8. Common special function modules – e.g., WAN fabric extender, system resource manager. 4 Figure 2. Strategic Hierarchy. Mercury High Density Modular Systems is in alignment with contemporary commercial enterprise data center strategies: Every element is a server, Appliance-free systems, Multi- supplier for every component, Software defined functions where possible STRATEGIC HIERARCHY ARCHITECTURE SYSTEMS MODULES COMPONENTS 1 2 3 n

Articles in this issue

view archives of White Paper - Managing life cycle and network interoperability challenges on Navy platforms