The different deployment options provide you with maximum flexibility:
You can continue to use the appliance model for ultimate price/performance.
You can also go to the public or private cloud to provision additional capacity on demand – or you can deploy a SW appliance on zLinux to avoid managing a separate environment.
The important point is that all these form factors come with one API, one database engine – so from the outside you have a uniform experience.
This allows you to invest once in enabling your applications and workloads for the accelerator and then transition easily between on-premises, private cloud and public cloud implementations.
[[Aus: Integrated Analytics System Enablement – Session 1.pptx]]
This slides shows the two main components of the IBM Integrated Analytics System (IIAS),
One Data Module consists of 2 Compute Nodes combined with 1 Flash system.
Power architecture
Higher performance across fewer nodes
CPU acceleration with multi-core and Single Instruction Multiple Data (SIMD) parallelism
Increased reliability and availability
Flash storage, standard
Near real-time latency for higher transfer speeds 99.999% reliability and operational efficiency
Why First Tier Storage? (DK) The current IIAS version is a OLAP optimized version like PDA. Different from PDOA systems which were optimized for mixed workload the PDA like IIAS requires less storage than a PDOA like system.
It‘s using fast Flash Storage for the hot data. For the PDOA like IIAS system, it‘s planned to add a Second Tier Storage system based of high speed HDDs later to allow storing cooling data on less expensive hard drives.
Open questions:
what is a Two Dimensional RAID5 ? The combination of IBM® Variable Stripe RAID and system-level RAID 5 protection across IBM MicroLatency® modules (within a flash enclosure) is called two-dimensional (2D) flash RAID.
Two-dimensional (2D) flash RAID consists of IBM Variable Stripe RAID and system-wide RAID 5. Variable Stripe RAID technology helps reduce downtime and maintain performance and capacity in the event of partial or full flash chip failures. System-wide RAID 5, with easily accessed hot swappable flash modules, helps prevent data loss and promote availability.
RAID 5 configurations provide a high degree of redundancy with Variable Stripe RAID and RAID 5 protection. RAID 5 data protection includes one IBM MicroLatency module dedicated as parity and another as a dedicated hot spare. The maximum capacity utilization for RAID 5 is provided by using 12 IBM MicroLatency modules. (see: https://www.ibm.com/support/knowledgecenter/en/STJKN5_12.0.3/fs_a9x_po_flash_raid.html)
For performance: Full Mako compares to 2/3 Acc on IIAS (we expect 2-5x performance gain)
For User capacity: Full Mako compares to full Acc on IIAS
GPFS = General Parallel File System => IBM Spectrum Scale
MLN = multiple logical nodes (each logical node works on a defined subset of the data)
LACP-> Link Aggregation Control Protocol
Outage of up to 30 min is related to the „power-recycling policy“ in Sailfish: they try to re-enable a server by reboot. This requires up to 20 min which might increase overall cycle to 30 min.
Problem Statement:
Compliance rules and regulation require Accelerator customers to encrypt sensitive data like patient information in healthcare at rest. At rest is defined as persistent user data stored on any node of the appliance and should protect this data at rest so that if one or more disks are lost then whoever gets hold of the disks will not be able to read the data. See RRC#96
Note: this includes "temporary data" stored on host disks like query spill to disk data or CDC staging data and sensitive Accelerator traces. Some customers also consider schema information (like stored in the Accelerator catalog) as sensitive - so this should be encrypted, too.
Since Mako already „data-at-rest-encryption“ available due to the ise of encryption enabled HDDs
[Copied from V51_Operation.ppt NEEDS VERIFICATION and ADAPTION]
As of Flash Storage PPT / Sailfish enablement:
IBM FlashSystem 900 Encrytion:
Key encryption is protected by an Advanced Encryption Standard (XTS-AES) algorithm key wrap using the 256-bit symmetric option in XTS mode, as defined in the IEEE1619-2007 standard.
FlashSystem 900 Encryption for data at rest will not be implemented for the Beta Systems, but will be implemented in code releases beginning with 1.5.1.x on the Maverick array but not on Texan array
DB2 Native Encryption will not be used for Data at rest for Accelerator on IAS
See AcceleratorWIKI: https://Acceleratorwiki.dst.ibm.com/index.php/Encryption_of_data_at_rest_(Db2/Sailfish)
