Security and Performance Help Mainframes Stand the Test of Time



  • mainframe

    “The mainframe has always stood for four guiding principles: availability, scalability, security and performance from the introduction of the mainframe in 1964 on through to today,” says John Mertic of the Open Mainframe Project.

    As of last year, the Linux operating system was running 90 percent of public cloud workloads; has 62 percent of the embedded market share and runs all of the supercomputers in the TOP500 list, according to The Linux Foundation Open Mainframe Project’s 2018 State of the Open Mainframe Survey report.

    Despite a perceived bias that mainframes are behemoths that are costly to run and unreliable, the findings also revealed that more than nine in 10 respondents have an overall positive attitude about mainframe computing.

    The project conducted the survey to better understand use of mainframes in general. “If you have this amazing technology, with literally the fastest commercial CPUs on the planet, what are some of the barriers?” said John Mertic, director of program management for the foundation and Open Mainframe Project. “The driver was, there wasn’t any hard data around trends on the mainframe.”

    Cloud vs. Mainframe

    Respondents were asked how they view cloud computing in comparison to mainframes, “and overwhelmingly, they said it’s going to augment the mainframe and not replace it,’’ Mertic says. Eighty-five percent of respondents said they are using cloud in addition to the mainframe, while 15 percent said cloud is replacing the mainframe.

    This parallels the rest of industry, he says, noting that “everything’s going hybrid. You’re going to have some degree of private cloud, public cloud, some SaaS, some IoT solutions — and the mainframe fits in there. Isn’t it great we have a menu of choices in architecture, and that they complement each other.”

    In terms of security, only five percent of overall respondents said cloud solutions are at least as secure as mainframes, which Mertic said surprised him the most. Even among self-identified cloud users, only six percent agreed that cloud is at least as secure as mainframes.

    “These are people who feel cloud is the future, but then say, ‘Wow, if security is a top priority, cloud isn’t there compared to mainframe, which is still far more secure,’’’ he said. “That surprised us, especially among people who self-identified as being on the cloud bandwagon.”

    General findings include:

    • Both users and non-users of Linux on the mainframe agree on the mainframe platforms strengths of performance, security, and cost reduction.
    • Cloud computing is perceived to augment the mainframe, not replace it.
    • Mainframe will continue to have a key role in a hybrid computing world.

    More specifically:

    • 28 respondents said cloud solutions are significantly less costly to implement, compared to 31 percent of self-identified cloud users.
    • 47 percent of respondents said cloud solutions provide much greater flexibility in adding power or scalability, compared to 52 percent of self-identified cloud users.
    • 15 percent of both self-identified cloud users and overall respondents said that over the long run, cloud solutions are far less expensive to maintain, while 57 percent of general respondents disagreed with that, compared to 59 percent of self-identified cloud users.

    Standing the Test of Time

    Key workloads for Linux on the mainframe are application servers, database servers and data analytics, Mertic says. Even though IT infrastructure has changed compared to what it was 10, 15 and 20 years ago, the mainframe has withstood the test of time, he says.

    “The mainframe has always stood for four guiding principles: availability, scalability, security and performance from the introduction of the mainframe in 1964 on through to today,” Mertic says. “IT in 2018 has tons of choices, and if a first-class open source platform with those guiding principles are what your organization requires at a ‘10’ level, then modern mainframe is an architecture you should consider.”

    The survey of 145 mainframe professionals was conducted between Aug. and Oct. 2017.

    Stay tuned for part two of the Open Mainframe Project survey in the fall, which will provide broader insights into how the general IT market views the modern mainframe.

    The post Security and Performance Help Mainframes Stand the Test of Time appeared first on The Linux Foundation.

    https://www.linuxfoundation.org/blog/security-and-performance-help-mainframes-stand-the-test-of-time/





Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:

    lsblk

    Output:

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s

    Fin!

    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more
});