Skip to content

Latest commit

 

History

History
94 lines (87 loc) · 3.99 KB

architecture_overview.md

File metadata and controls

94 lines (87 loc) · 3.99 KB

Hailstorm Architecture

The demo has a layered Architecture which looks as follows:

                         +---------+
                         |Container|
                         |(12)     |                                  Layer 4
                         +---------+--+
                         |OpenShift   |
                         |V3.x (11)   |
                         +----------------+ +-----+                   Layer 3
                         | Virtual Guests | |Cloud|                  
                         | / Instances (9)| |Forms|(10)
 +---------+ +---------+ +----------+------------+ +-------+ +---+
 |Satellite| |Infra-   | |Nested    | |Nested    | |RH     | |RH |
 |         | |structure| |Hypervisor| |Hypervisor| |Storage| |IDM|    Layer 2
 |      (3)| |      (4)| |1      (5)| |2      (6)| |    (7)| |(8)|
++-----------+-------------------------------------+--------------+
|                        RHEL (KVM Host)     (2)                  |   Layer 1
+-----------------------------------------------------------------+
|                         Hardware           (1)                  |   Layer 0
+-----------------------------------------------------------------+

From bottom to top:

  1. Hardware:
  • A single, portable 2 HU server
  • plenty of CPU cores
  • plenty of RAM
  • RAID6 protected storage
  • Fast SSD storage
  1. RHEL (KVM Host):
  • Base Operating System, to be defined whether RHEL or RHEL-Atomic Host.
  • Configured to allow nested virtualization.
  • Acts as NTP server for all layer2 hosts
  • KVM based virtualization allows to partition the hardware
  • Multiple internal VLANs realized as virbr devices
  • NAT enables a private IP space which can be connected into any LAN
    • To be discussed: How to enable DNS + Mail in NAT scenario
  • Runtime environment for scripts / playbooks / ... which
    1. configure the OS itself (Kernel Params, OVS config, NAT config, ...)
    2. bring up the KVM instances running on top of it
  • There is NO explicit GUI / WebUI on this layer
  1. Satellite:
  • Core service (not in nested virt)
  • Subscription Management for ALL virtual machines on Layer 2 and up
  • Content Views for ALL virtual machines on Layer 2 and up
  1. Infrastructure:
  • Core service (not in nested virt)
  • may be one or more virtual machines
  • DNS server
  • To be discussed: DHCP server
  • Mail (SMTP+IMAP) server
  • NFS Server (e.g. for RHEV)
  1. Nested Hypervisor 1: classic HV for Mode 1 workloads
  • one RHEV-M
  • two RHEV-H
  1. Nested Hypervisor 2: OpenStack for Mode 2 workloads
  • one RHEL-OSP installer/director
  • three RHEL-OSP controllers
  • three RHEL-OSP nodes
  • additional empty VMs to simulate rollout of new OSP instance
  1. Red Hat Storage (OPTIONAL):
  • Optional component to provide NFS, Block or Object Storage
  • Augments or replaces NFS server in 4. Infrastructure
  1. Red Hat Identity Management and/or KeyCloak (OPTIONAL):
  • Single point of authentication
  • Primarily for web authentication
  • LDAP containing SSH public keys so we don't have to copy&paste keys
  1. Virtual Guests / Instances
  • Image-based deployment of RHEL and Windows
  • (potentially) Subscribed in 3. Satellite
  1. CloudForms
  • Guest on RHEV (Nested Hypervisor 1)
  • Manages underlying Hypervisors
  • Manages OpenShift (Note: even though the graphic suggests otherwise, CF and OpenShift are on the same layer (3)).
  1. OpenShift V3
  • One or three Masters
  • two Nodes
  • Potentially rolled out via CloudForms
  • Potentially rolled out via OpenStack HEAT
  • Potentially rolled out just via Ansible Script
  1. Container
  • Any containerized workload
  • Developed in OpenShift or externally

Further Details