zLinux

Description

Linux on z Systems gives the flexibility of running Linux with the advantages of fault-tolerant mainframe hardware capable of over 90,000 I/O operations per second and with a mean time between failure (MTBF) measured in decades. Using virtualization, numerous smaller servers can be combined onto one mainframe, gaining some benefits of centralization and cost reduction, while still allowing specialized servers. IBM mainframes use full virtualization, which permits far greater workload density. Combining full virtualization of the hardware, plus lightweight virtual machine containers that run Linux in isolation, result in a platform that supports more virtual servers than any other in a single footprint. IBM mainframes allow transparent use of redundant processor execution steps and integrity checking, which is important for critical applications.

The zLinux Platform Hosting Service provides Customers with a standardized Linux server and operating system configurations, deployment, management, and administration of Linux-based software applications.

Benefits

  • A dedicated support team of experienced, certified professionals
  • 24/7 Service Desk support
  • Consultation available to identify the optimal solution that will meet business and IT requirements
  • No need to purchase or manage servers, system software, storage or network equipment
  • Hardware and software components are built to create a stable, secure, fault-tolerant, and scalable infrastructure
  • Customers focus on supporting their application product, not the hardware or operating system

Included

Operating System

  • Enterprise Linux
  • RedHat (6.x and 7x)
  • Ubuntu (16.04 and 18.04)

Network Connections

  • FICON channel connections
  • Redundant 10 Gbps network connection
  • One IP address per zLinux server (more can be configured if required)

Advantages

  • Fastest commercially available core clock speed and technology
    • 8 core per chip, 5.0 GHz (141 max core per box)
    • 2 threads per core
    • Each core has its own cryptographic co-processor – optimized for encryption functions
    • Additional crypto cores for additional crypto capability
    • Database workloads run 8 times faster and require 92% fewer cores than other platforms
  • Designed for large cache-intensive workloads
    • L1 cache of 224 KB vs 64 KB on other platforms
    • L2 cache of 4 MB vs 256 KB on other platforms
    • L3 cache of 64 MB vs 45 MB on other platforms
    • L4 cache of 960 MB (the only commercially available off-chip with L4 cache)
  • Designed for high I/O bandwidth workloads
    • 80 times more I/O channel processors than other typical platforms
    • Up to 24 cores dedicated to I/O processing (separate from cores dedicated to business logic)
  • Designed to ensure the highest availability and least amount of downtime
    • Built-in redundancy eliminates single points for failure
    • Built-in automated diagnostics; problem determination and isolation
    • Automated failover to speed recovery and minimize system impact
      • Every server has two cores designated as spare
      • Core failover is transparent to applications
      • Spares need not be local to the same chip, node, or drawer; any core and failover to spare – other servers do not have core sparing
    • Includes a Redundant Array of Independent Memory (RAIM) – 100% memory mirroring and more robust and cost-effective than Error Correcting Code (ECC) memory
    • 100% broad coverage – bus failures, Dual In-line Memory Module (DIMM) wipeouts, DIMM connector failures, board failures, and clock failures – a level of memory protection not found on other servers
  • Exceptional service delivery
    • Multi-dimensional growth
      • Dynamically add cores, memory, I/O adapters, devices, and network cards
      • Grow horizontally and vertically without disruption to the running environment
    • Non-disruptive scalability
      • Core ratios on the order of 10 to 1
      • Run 1.6 times more active docker containers than competing platforms
      • Supports the largest single node of MongoDB with a footprint of +1 TB, processing +2 TB documents, while maintaining fetch times under 5 ms
    • Guaranteed service delivery for all workloads
      • High priority workloads run a very high utilization with no degradation when low priority workloads are added (low priority workloads cannot steal valuable resources from high priority workloads)
    • Complete workload isolation

Languages and Development Environments

NameDescriptionLicensing
Node.jsCross-platform JavaScript run-time environmentOpen Source
RubyObject-oriented, general-purpose programming languageRudy
RailsServer-aside web application frameworkMIT
PythonInterpreted high-level programming language for general-purpose programmingPython Software Foundation
LLVMCollection of modular and reusable compiler and toolchain technologiesOpen Source
OpenJDKJava HotSpot virtual machine and compilerOpen Source
GCCGOGo Programming Language CompilerOpen Source
oCamlCross-platform programming languageLGPL
ErlangGeneral-purpose, concurrent, functional programming language. Well suited for systems with the following characteristics:
Distributed
Fault-tolerant
Soft real-time
Highly available, non-stop applications
Apache
Apache HTTP WebCross-platform web serverApache
PHPServer-side scripting language designed for web developmentPHP

Databases and Messaging

NameDescriptionLicensing
MySQLRelational database management system (RDBMS)Open Source
PostgreSQLObject-relational database management system (ORDBMS)PostgreSQL
MariaDBMySQL relational database management systemGeneral Public License (GNU)
MongoDBCross-platform document-oriented database programOpen Source
CassandraDistributed NoSQL database management system designed to handle large amounts of dataApache
RedisIn-memory distributed databaseBerkeley Software Distribution (BSD)
CouchDBDatabase software with a scalable architectureApache
GemfireDistributed data management platformPivotal
RabbitMQMessage broker softwareOpen Source
DB2Relational database management system (RDBMS)IBM
OracleRelational database management system (RDBMS)Oracle
IIBWebSphere Message BrokerIBM
WebSphereMQMessaging solution for Enterprise and IBM's Message Oriented MiddlewareIBM

Cloud Infrastructure

NameDescriptionProgramming Language
DockerOperating-system-level virtualization also known as containerizationApache
ChefConfiguration management toolRuby
PuppetSoftware configuration management toolC++
Cloud FoundryMulti-cloud application Platform as a Service (PaaS)Ruby
KubernetesSystem for automating deployment, scaling, and management of containerized applicationsGo

eCommerce and Application Servers

NameDescriptionDeveloper
jBoss (WildFly)Application serverRed Hat
WebSphereApplication and integration middlewareIBM

Security

Operating system security strictly adheres to established, applicable CDT security policies. Policies include, but are not limited to, an established quarterly operating system patch cycle and routine third-party security scans to test for known vulnerabilities.

For more information, see Security Services.

Optional

Database

We offer a number of database management system (DBMS) technologies.

Middleware

We provide a number of middleware technologies including:

Administration

The performance of a specific platform is dependent on many factors, most of which are outside the scope of the system administrators. The systems are initially sized based on project recommendations. Refreshed systems are sized based on historical information. Unplanned workload growth can affect the performance of any application. CDT will upgrade or replace servers to meet new workload demands, as requested by Customers.

Server Administration

CDT provides zLinux server maintenance including Operating System (OS) administration, patching and updating of servers, and 24/7 monitoring of the performance, wellness, security, and connectivity of the server. With planned patch management, CDT ensures the data is protected at all times. CDT informs Customers of planned maintenance (such as OS upgrades or patching). The Customer installs, maintains, patches, and troubleshoots all of the hosted application software on the provisioned servers.

File System Administration

CDT provides shared centralized file storage and retrieval for equipment connected to the CDT network. Customers may set up files to be accessible by specific groups or users.

Disk Administration

CDT monitors and manages the disk space.

Backup and Restore Administration

CDT provides backup and restore.

Backup

  • Full merge backups occur once per week and incremental backups occur on the other six days.
  • The primary copy of each backup remains at the CDT data center and is retained for 30 days.
  • The replicated copy of each backup is located at the opposite campus within the Virtual Tape System.

Monitoring

CDT proactively monitors the network and server infrastructure health with multi-layer security and monitoring systems designed specifically for the managed servers. CDT ‘s monitoring service tracks the resources, processes, and services running on servers including:

  • CPU utilization
  • Memory utilization
  • Running processes and applications
  • Vital services

Technology Refresh

Hardware is refreshed every four years or as needed.

Vendor Contract Administration

CDT manages the vendor contracts for the zLinux platform and provides licenses for hosted servers.

User Account Administration

Root level System Administration (SA) authority is restricted to CDT designated personnel. Server access is permitted based upon server function and data type. Customers must refer to the System Administrator Access Standard – 3138 should SA be provided. SA privileges are never permitted on shared services. Configuration changes made outside the scope of the service request that requires intervention, correction, or troubleshooting by CDT staff may incur additional charges.

Maintenance Schedule

Preventative Maintenance Schedule

Roles & Responsibilities

zLinux Computing Software

RoleCDTCustomer
Operating SystemX
Operating System PatchingX
Application
Exception: Dependent of the owner of the application.
XX
Application Layer Security
Exception: Dependent of the owner of the application.
XX
Application Maintenance
Exception: Dependent of the owner of the application.
XX
Application Support
Exception: Dependent of the owner of the application.
XX
DNSX
Email Relay - Additional CostXX

zLinux Storage

RoleCDTCustomer
Device(s)X
Connectivity to ServersXX
Disk Space ManagementXX
Backup and RecoveryXX
Capacity MonitoringX

zLinux Network Infrastructure

RoleCDTCustomer
Customer required network access
*Must be approved by Security.
X
Firewall context configuration and managementXX

zLinux IT Security Management

RoleCDTCustomer
Configure system security toolsX
Monitor system securityX
Ensure system securityX
Ensure system security responseX
Manage system authenticationX
Maintain user accounts
* Customer requests modification of accounts. CDT implements account request. No client root/sudo with exception.
X

zLinux Resource Administration

RoleCDTCustomer
Monitor resource performanceX
Fix resource performanceXX
Monitor resource capacityX
Add resource capacityX

Administration

RoleCDTCustomer
Hardware procurement and maintenanceX
System software procurementX
Maintenance contract managementX

Disaster Recovery

CDT Disaster Recovery services consist of the planning and preparation necessary to enable Customers to recover critical information technology applications hosted on the platform.

Features

  • Centralized backup system
  • Last backup Recovery Point Objective (RPO)
  • Capability to failover to an alternate campus
  • Hardware to support critical applications
  • Exercise schedule flexibility
  • Cost-efficient DR services
  • Technical support during an exercise and in the event of a disaster
  • 24/7 Service Desk support during DR exercises

Rates

The performance of a specific platform is dependent on many factors, most of which are outside the scope of the system administrators. The systems are initially sized based on project recommendations. Refreshed systems are sized based on historical information. Unplanned workload growth can affect the performance of any application. CDT will upgrade or replace servers to meet new workload demands, as requested by Customers.

zLinux Server – Premium

Service DescriptionService IdentifierProduct NameUnit of MeasurementRateService CodeNotes
Enterprise Linux Base Server - PremiumEnterprise Linux Server-PremiumEnterprise Linux Application HostingMonthly/Per Server$542.00 C305
Enterprise Linux vCPU - PremiumEnterprise Linux Server-PremiumEnterprise Linux Application HostingvCPU/Month$1,085.00 C306
Enterprise Linux Memory - PremiumEnterprise Linux Server-PremiumEnterprise Linux Application HostingMonthly/Per GB$54.00 C307
Enterprise Linux Server Set-up FeeEnterprise Linux Server-PremiumEnterprise Linux Application HostingOne-Time/Per Server$396.00 C308

zLinux Server – Standard

Service DescriptionService IdentifierProduct NameUnit of MeasurementRateService CodeNotes
Enterprise Linux Server Set-up FeeEnterprise Linux Server-PremiumEnterprise Linux Application HostingOne-Time/Per Server$396.00 C308
Enterprise Linux Base Server - StandardEnterprise Linux Server-StandardEnterprise Linux Application HostingMonthly/Per Server$362.00 C309
Enterprise Linux vCPU - StandardEnterprise Linux Server-StandardEnterprise Linux Application HostingvCPU/Month$362.00 C310
Enterprise Linux Memory - StandardEnterprise Linux Server-StandardEnterprise Linux Application HostingMonthly/Per GB$36.00 C311

Add-Ons

Service DescriptionService IdentifierProduct NameUnit of MeasurementRateService CodeNotes
Enterprise Linux - IBM WebSphere Application Server (WAS) SupportPremium SupportApplication ServicesMonthly/Per Server$958.00 M628
Enterprise Linux - IBM HTTP Server (IHS) Support for WASApplication ServicesMonthly/Per Server$495.00 M629
Enterprise Linux - IBM WebSphere MQ SupportApplication ServicesMonthly/Per Server$183.00 M630

Subscriptions to this service are available.

Request

Service Request NameLink
Enterprise Linux Application Hosting Service

  1. The Customer creates an architectural diagram.

  2. The Customer creates and submits a Case/Request with the architectural diagram attached.

  3. The Customer contacts their Account Lead to schedule a technical overview meeting to review the Customer’s business needs/requirements and hardware specifications listed on the zLinux Case/Request and architectural diagram.

  4. CDT develops a cost estimate based on the submittal form, architectural diagram, and the Customer’s business needs/requirements.

  5. The Customer approves the architectural design and cost estimate.

  6. CDT provisions the Linux environment including hardware, software, and network-based on the architectural diagram.

  7. The environment is turned over to the Customer.

To request to Add, Modify, or Decommission virtual server(s) within the Enterprise Linux Application Hosting Service

SLO

Service OptionFulfillment Timeframe SLONotes/Dependencies
Add New Virtual Servers95% within 60 Calendar DaysProcess includes:
  • Customer Engagement Document Completion – Avg 13 Days
    • Customer submits request, completes questionnaire and diagram

  • Architecture Review - Avg 18 Days
    • Customer, CDT Enterprise Service Delivery team and Service workgroups meet to review/approve architecture and gather tech requirements

  • Customer and CDT Commit – Avg 9 Days

  • Build - Avg 5 days
    • CDT Service workgroups plan, build, and test customer environment

  • Deliver - Avg 15 Days
    • Customer tests connectivity and installs apps

  • Includes 45 days from Case submission to “deliver” server to customer; additional 15 days for customer validation.
  • Based on “average” complexity case; 4 servers or less, only 1-2 design meetings required.

    Dependencies
    • Customer brings appropriate staff to design meetings scheduled at frequency CDT requests
    • Customer submits accurate supplemental cases - e.g., admin access, firewall.
    • Cases CDT and Customer place in "hold" status may delay completion.
  • Modify Existing Virtual Server95% within 14 Calendar DaysModifications include adding or removing CPU/memory/storage.
    Decommission Existing Virtual Server95% within 21 Calendar DaysDate from the requested decommission date in which server is taken offline and billing is stopped.