kvm examples

bitcoin-cli examples

README.md

@@ -0,0 +1,4 @@
+Docsite -=Ger=-
+========================
+
+Zie hier een aantal handige docs inzake projectjes waar ik mee bezig ben!

Vagrantfile.centos7

@@ -0,0 +1,110 @@
+# coding: utf-8
+# copyright Utrecht University
+# -*- mode: ruby -*-
+# vi: set ft=ruby :
+
+# GS: run script after install:
+$post_script = <<SCRIPT
+yum install epel-release -y
+yum install htop -y
+yum install net-tools -y
+useradd ger
+mkdir /home/ger/.ssh
+chown ger:ger /home/ger/.ssh/
+chmod 700 /home/ger/.ssh/
+cat /tmp/ger.pubkey >> /home/ger/.ssh/authorized_keys
+mkdir /root/.ssh
+chown root:root /root/.ssh/
+chmod 700 /root/.ssh/
+cat /tmp/ger.pubkey >> /root/.ssh/authorized_keys
+cp /tmp/hosts /etc/hosts
+cp /tmp/fire_stop.sh /root/fire_stop.sh
+SCRIPT
+
+# Retrieve instance from command line.
+require 'getoptlong'
+
+opts = GetoptLong.new(
+  [ '--instance', GetoptLong::OPTIONAL_ARGUMENT ]
+)
+
+instance='combined'
+opts.each do |opt, arg|
+  case opt
+    when '--instance'
+      instance=arg
+  end
+end
+
+# Configuration variables.
+VAGRANTFILE_API_VERSION = "2"
+
+BOX = 'centos/7'
+GUI = false
+CPU = 1
+RAM = 1024
+
+DOMAIN  = ".ger.test"
+NETWORK = "192.168.50."
+NETMASK = "255.255.255.0"
+
+if instance == "scoop" then
+  HOSTS = {
+    "portal"   => [NETWORK+"11", CPU, RAM, GUI, BOX],
+    "icat"     => [NETWORK+"12", CPU, RAM, GUI, BOX],
+    "resc1"    => [NETWORK+"13", CPU, RAM, GUI, BOX],
+    "resc2"    => [NETWORK+"14", CPU, RAM, GUI, BOX],
+  }
+else
+  HOSTS = {
+    "combined" => [NETWORK+"10", 2, 4096, GUI, BOX],
+  }
+end
+
+if instance == "irods" then
+  HOSTS = { 
+   "irods02"   => [NETWORK+"16", CPU, RAM, GUI, BOX],
+  }
+end
+
+if instance == "kubernetes" then
+  HOSTS = { 
+   "master"  => [NETWORK+"21", CPU, RAM, GUI, BOX],
+   "worker1"  => [NETWORK+"22", CPU, RAM, GUI, BOX],
+   "worker2"  => [NETWORK+"23", CPU, RAM, GUI, BOX],
+  }
+end
+
+Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
+  #config.ssh.insert_key ='true' 
+  config.vm.provision "file", source: "/home/ger/.ssh/id_ecdsa.pub", destination: "/tmp/ger.pubkey"  
+  config.vm.provision "file", source: "/etc/hosts", destination: "/tmp/hosts"
+  config.vm.provision "file", source: "/home/ger/fire_stop.sh", destination: "/tmp/fire_stop.sh"
+
+  HOSTS.each do | (name, cfg) |
+    ipaddr, cpu, ram, gui, box = cfg
+
+    config.vm.define name do |machine|
+      machine.vm.box = box
+
+      machine.vm.provider "virtualbox" do |vbox|
+        vbox.gui    = gui
+        vbox.cpus   = cpu
+        vbox.memory = ram
+        vbox.name   = name
+        vbox.customize ["guestproperty", "set", :id, "/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 10000]
+      end
+
+      machine.vm.hostname = name + DOMAIN
+      machine.vm.network 'private_network', ip: ipaddr, netmask: NETMASK
+      machine.vm.synced_folder ".", "/vagrant", disabled: true
+      machine.vm.provision "shell",
+        inline: "sudo timedatectl set-timezone Europe/Amsterdam"
+      machine.vm.provision "shell", 
+        inline: "cat /tmp/ger.pubkey >> /home/vagrant/.ssh/authorized_keys"
+      machine.vm.provision "shell", 
+        inline: $post_script
+    end
+  end
+
+end

bitcoin

@@ -0,0 +1,137 @@
+
+start daemon:
+
+bitcoind -daemon --datadir=/data/bitcoin --printtoconsole --rpcuser=ger --rpcpassword=<secret>
+
+memory-conservative options:
+
+bitcoin-d -daemon --datadir=/data/bitcoin --printtoconsole --rpcuser=ger --rpcpassword=<secret> --blocksonly --dbcache=50 --maxsigcachesize=4 --maxconnections=4 --rpcthreads=1 --banscore=1 --maxmempool=100  --maxorphantx=10
+
+
+check if node is online on bitcoin-network:
+
+https://bitnodes.io/nodes/94.212.140.57-8333/
+
+check if you can get hash of genesis block 0:
+
+bitcoin@raspberrypi:~$ bitcoin-cli getblockhash 0
+000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
+
+
+create backup of wallet:
+
+bitcoin@raspberrypi:~$ bitcoin-cli backupwallet ~/walletbackup.dat
+
+create new pubkey/address to sent bitcoin to:
+
+bitcoin@raspberrypi:~$ bitcoin-cli -named getnewaddress address_type=bech32
+bc1qc2ykz4fvru7x5a03ulrt7lu08qmmqandkrc4xh
+
+<sent 1 EU to address..>
+
+
+check unconfirmed_balance:
+
+bitcoin@raspberrypi:~$ bitcoin-cli getunconfirmedbalance
+0.00000000
+
+check which block we are at/sync:
+
+bitcoin@raspberrypi:~$ bitcoin-cli getblockcount 
+369100
+
+check number of connections:
+
+bitcoin@raspberrypi:~$ bitcoin-cli getconnectioncount
+4
+
+check blockchaininfo:
+
+bitcoin@raspberrypi:~$ bitcoin-cli getblockchaininfo 
+{
+  "chain": "main",
+  "blocks": 369130,
+  "headers": 664786,
+  "bestblockhash": "0000000000000000117a24b7765058486ff569c9db743c3ba262fa3d47719159",
+  "difficulty": 52699842409.34701,
+  "mediantime": 1439149569,
+  "verificationprogress": 0.1329346278189584,
+  "initialblockdownload": true,
+  "chainwork": "00000000000000000000000000000000000000000009204346abde553d962c70",
+  "size_on_disk": 48331158857,
+  "pruned": false,
+  "softforks": {
+    "bip34": {
+      "type": "buried",
+      "active": true,
+      "height": 227931
+    },
+    "bip66": {
+      "type": "buried",
+      "active": true,
+      "height": 363725
+    },
+    "bip65": {
+      "type": "buried",
+      "active": false,
+      "height": 388381
+    },
+    "csv": {
+      "type": "buried",
+      "active": false,
+      "height": 419328
+    },
+    "segwit": {
+      "type": "buried",
+      "active": false,
+      "height": 481824
+    }
+  },
+  "warnings": ""
+}
+
+bitcoin@raspberrypi:~$ bitcoin-cli getnetworkinfo
+{
+  "version": 200100,
+  "subversion": "/Satoshi:0.20.1/",
+  "protocolversion": 70015,
+  "localservices": "0000000000000409",
+  "localservicesnames": [
+    "NETWORK",
+    "WITNESS",
+    "NETWORK_LIMITED"
+  ],
+  "localrelay": true,
+  "timeoffset": -13,
+  "networkactive": true,
+  "connections": 4,
+  "networks": [
+    {
+      "name": "ipv4",
+      "limited": false,
+      "reachable": true,
+      "proxy": "",
+      "proxy_randomize_credentials": false
+    },
+    {
+      "name": "ipv6",
+      "limited": false,
+      "reachable": true,
+      "proxy": "",
+      "proxy_randomize_credentials": false
+    },
+    {
+      "name": "onion",
+      "limited": true,
+      "reachable": false,
+      "proxy": "",
+      "proxy_randomize_credentials": false
+    }
+  ],
+  "relayfee": 0.00001000,
+  "incrementalfee": 0.00001000,
+  "localaddresses": [
+  ],
+  "warnings": ""
+}
+

check-ssl-cert.sh

@@ -0,0 +1 @@
+ ssh ger@rdms-prod-icat00.data.rug.nl "openssl x509 -dates -noout -in /etc/irods/localhost_and_chain.crt"

git.howto

@@ -176,4 +176,74 @@ Date:   Tue Mar 20 11:04:40 2018 +0100
     eerste commit
 
 
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git branch
+* master
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git branch features
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git branch
+  features
+* master
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git checkout features
+Switched to branch 'features'
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git branch
+* features
+  master
+
+  ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git checkout master
+Switched to branch 'master'
+Your branch is up to date with 'origin/master'.
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git branch
+  features
+* master
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git checkout features
+Already on 'features'
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git add ./hoi.txt 
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git commit -m "test"
+On branch features
+nothing to commit, working tree clean
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git push origin features 
+Username for 'https://git.web.rug.nl': g.j.c.strikwerda@rug.nl
+Password for 'https://g.j.c.strikwerda@rug.nl@git.web.rug.nl': 
+
+Enumerating objects: 4, done.
+Counting objects: 100% (4/4), done.
+Delta compression using up to 8 threads
+Compressing objects: 100% (2/2), done.
+Writing objects: 100% (3/3), 271 bytes | 271.00 KiB/s, done.
+Total 3 (delta 0), reused 0 (delta 0)
+remote: 
+remote: Create a new pull request for 'features':
+remote:   https://git.web.rug.nl/p216149/git-workshop/compare/master...features
+remote: 
+To https://git.web.rug.nl/p216149/git-workshop.git
+ * [new branch]      features -> features
+
+ ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git branch
+  features
+* master
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git merge features
+Already up to date.
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git status
+On branch master
+Your branch is ahead of 'origin/master' by 2 commits.
+  (use "git push" to publish your local commits)
+
+ger@ger-lpt-werk:~/Desktop/CIT/git-workshop$ git push 
+Username for 'https://git.web.rug.nl': g.j.c.strikwerda@rug.nl
+Password for 'https://g.j.c.strikwerda@rug.nl@git.web.rug.nl': 
+Total 0 (delta 0), reused 0 (delta 0)
+To https://git.web.rug.nl/p216149/git-workshop.git
+   5605e6f..bb99908  master -> master
+
+
 

hosts

@@ -0,0 +1,16 @@
+[rugcms]
+
+cms-fa21 ansible_host=cms-fa21.service.rug.nl ansible_port=22
+cms-fa22 ansible_host=cms-fa22.service.rug.nl ansible_port=22
+cms-fa23 ansible_host=cms-fa23.service.rug.nl ansible_port=22
+cms-fa24 ansible_host=cms-fa24.service.rug.nl ansible_port=22
+
+cms-fp21 ansible_host=cms-fp21.service.rug.nl ansible_port=22
+cms-fp22 ansible_host=cms-fp22.service.rug.nl ansible_port=22
+cms-fp23 ansible_host=cms-fp23.service.rug.nl ansible_port=22
+
+[acc]
+cms-fa[21:24]
+
+[prod]
+cms-fp[21:23]

install_lb.yml

@@ -0,0 +1,6 @@
+---
+- hosts: lb
+  gather_facts: yes
+  become: yes
+  roles:
+    - web

install_webservers.yml

@@ -0,0 +1,6 @@
+---
+- hosts: webservers
+  gather_facts: yes
+  become: yes
+  roles:
+    - web

iptables-stop

@@ -0,0 +1,13 @@
+#!/bin/bash
+
+# firewall stop scriptje
+
+# reset all:
+iptables -F
+iptables -X
+iptables -Z
+
+# set policies wide-open:
+iptables -P INPUT ACCEPT
+iptables -P OUTPUT ACCEPT
+iptables -P FORWARD ACCEPT

irods-admin

@@ -0,0 +1,122 @@
+irods-admin:
+
+[root@test ~]# su - irods
+Last login: Fri Oct 26 11:59:25 CEST 2018 on pts/0
+
+-bash-4.2$ iinit
+Enter your current iRODS password:
+
+-bash-4.2$ ils
+/testZone/home/irods:
+
+-bash-4.2$ ils -A
+/testZone/home/irods:
+        ACL - irods#testZone:own   
+        Inheritance - Disabled
+
+create user in irods:
+
+-bash-4.2$ iadmin mkuser g.j.c.strikwerda@rug.nl rodsuser
+
+set password for user:
+
+-bash-4.2$ iadmin moduser g.j.c.strikwerda@rug.nl password ir0ds
+
+check as user:
+
+[root@test ~]# su - ger
+
+init your environment:
+
+[ger@test ~]$ iinit
+ ERROR: environment_properties::capture: missing environment file. should be at [/home/ger/.irods/irods_environment.json]
+One or more fields in your iRODS environment file (irods_environment.json) are
+missing; please enter them.
+Enter the host name (DNS) of the server to connect to: localhost
+Enter the port number: 1247
+Enter your irods user name: g.j.c.strikwerda@rug.nl
+Enter your irods zone: testZone
+Those values will be added to your environment file (for use by
+other iCommands) if the login succeeds.
+
+Enter your current iRODS password:
+
+check:
+
+[ger@test ~]$ ils
+/testZone/home/g.j.c.strikwerda@rug.nl:
+
+make file:
+
+[ger@test ~]$ touch ./iets.txt
+
+put file in irods vault:
+
+[ger@test ~]$ iput ./iets.txt 
+
+[ger@test ~]$ ils
+/testZone/home/g.j.c.strikwerda@rug.nl:
+  iets.txt
+
+[ger@test ~]$ ils -A
+/testZone/home/g.j.c.strikwerda@rug.nl:
+        ACL - g.j.c.strikwerda@rug.nl#testZone:own   
+        Inheritance - Disabled
+  iets.txt
+        ACL - g.j.c.strikwerda@rug.nl#testZone:own   
+
+[ger@test ~]$ ilsresc --tree
+demoResc:unixfilesystem
+
+create group:
+
+-bash-4.2$ iadmin mkgroup users
+
+make user member to group:
+
+-bash-4.2$ iadmin atg users g.j.c.strikwerda@rug.nl
+
+[ger@test ~]$ iuserinfo
+name: g.j.c.strikwerda@rug.nl
+id: 10016
+type: rodsuser
+zone: testZone
+info: 
+comment: 
+create time: 01540548708: 2018-10-26.12:11:48
+modify time: 01540548708: 2018-10-26.12:11:48
+member of group: g.j.c.strikwerda@rug.nl
+member of group: public
+member of group: users
+
+remove local file and retrieve it from irods:
+
+[ger@test ~]$ rm iets.txt
+
+[ger@test ~]$ iget iets.txt
+
+[ger@test ~]$ ls -l ./iets.txt 
+-rw-r-----. 1 ger ger 0 Oct 26 13:05 ./iets.txt
+
+[ger@test ~]$ imeta add -d iets.txt beschrijving metadata
+
+[ger@test ~]$ imeta ls -d iets.txt
+AVUs defined for dataObj iets.txt:
+attribute: beschrijving
+value: metadata
+units: 
+
+[ger@test ~]$ imeta add -d iets.txt maand november
+
+[ger@test ~]$ imeta ls -d iets.txt
+AVUs defined for dataObj iets.txt:
+attribute: beschrijving
+value: metadata
+units: 
+----
+attribute: maand
+value: november
+units: 
+
+
+

irods-install

@@ -0,0 +1,253 @@
+irods installation on centos7:
+
+# rpm --import https://packages.irods.org/irods-signing-key.asc
+# wget -qO - https://packages.irods.org/renci-irods.yum.repo | sudo tee /etc/yum.repos.d/renci-irods.yum.repo
+
+# yum install irods-server irods-database-plugin-postgres
+
+
+# yum install postgresql-server
+
+# postgresql-setup initdb
+Initializing database ... OK
+
+# systemctl start postgresql
+
+# su - postgres
+Last login: Fri Oct 26 11:30:44 CEST 2018 on pts/0
+
+$ psql
+psql (9.2.24)
+Type "help" for help.
+
+postgres=# CREATE USER irods WITH PASSWORD 'ir0ds';
+CREATE ROLE
+postgres=# CREATE DATABASE "ICAT";
+CREATE DATABASE
+postgres=# GRANT ALL PRIVILEGES ON DATABASE "ICAT" TO irods;
+GRANT
+postgres=# \l
+                                  List of databases
+   Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges   
+-----------+----------+----------+-------------+-------------+-----------------------
+ ICAT      | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =Tc/postgres         +
+           |          |          |             |             | postgres=CTc/postgres+
+           |          |          |             |             | irods=CTc/postgres
+ postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
+ template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
+           |          |          |             |             | postgres=CTc/postgres
+ template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
+           |          |          |             |             | postgres=CTc/postgres
+(4 rows)
+
+
+# python /var/lib/irods/scripts/setup_irods.py 
+The iRODS service account name needs to be defined.
+iRODS user [irods]: 
+iRODS group [irods]: 
+
++--------------------------------+
+| Setting up the service account |
++--------------------------------+
+
+Existing Group Detected: irods
+Existing Account Detected: irods
+Setting owner of /var/lib/irods to irods:irods
+Setting owner of /etc/irods to irods:irods
+iRODS server's role:
+1. provider
+2. consumer
+Please select a number or choose 0 to enter a new value [1]: 
+Updating /etc/irods/server_config.json...
+
++-----------------------------------------+
+| Configuring the database communications |
++-----------------------------------------+
+
+You are configuring an iRODS database plugin. The iRODS server cannot be started until its database has been properly configured.
+
+ODBC driver for postgres [PostgreSQL]: 
+Database server's hostname or IP address [localhost]: 
+Database server's port [5432]: 
+Database name [ICAT]: 
+Database username [irods]: 
+
+-------------------------------------------
+Database Type: postgres
+ODBC Driver:   PostgreSQL
+Database Host: localhost
+Database Port: 5432
+Database Name: ICAT
+Database User: irods
+-------------------------------------------
+
+Please confirm [yes]: 
+Database password: 
+Updating /etc/irods/server_config.json...
+Error encountered running setup_irods:
+Traceback (most recent call last):
+  File "/var/lib/irods/scripts/setup_irods.py", line 437, in main
+    setup_server(irods_config, json_configuration_file=options.json_configuration_file)
+  File "/var/lib/irods/scripts/setup_irods.py", line 116, in setup_server
+    database_interface.setup_database_config(irods_config)
+  File "/var/lib/irods/scripts/irods/database_interface.py", line 176, in setup_database_config
+    if database_already_in_use_by_irods(irods_config):
+  File "/var/lib/irods/scripts/irods/database_interface.py", line 73, in database_already_in_use_by_irods
+    with contextlib.closing(database_connect.get_database_connection(irods_config)) as connection:
+  File "/var/lib/irods/scripts/irods/database_connect.py", line 218, in get_database_connection
+    sys.exc_info()[2])
+  File "/var/lib/irods/scripts/irods/database_connect.py", line 201, in get_database_connection
+    return pypyodbc.connect(connection_string.encode('ascii'), ansi=True)
+  File "/var/lib/irods/scripts/irods/pypyodbc.py", line 2452, in __init__
+    self.connect(connectString, autocommit, ansi, timeout, unicode_results, readonly)
+  File "/var/lib/irods/scripts/irods/pypyodbc.py", line 2501, in connect
+    check_success(self, ret)
+  File "/var/lib/irods/scripts/irods/pypyodbc.py", line 988, in check_success
+    ctrl_err(SQL_HANDLE_DBC, ODBC_obj.dbc_h, ret, ODBC_obj.ansi)
+  File "/var/lib/irods/scripts/irods/pypyodbc.py", line 966, in ctrl_err
+    raise DatabaseError(state,err_text)
+IrodsError: pypyodbc encountered an error connecting to the database:
+('28000', '[28000] [unixODBC]FATAL: Ident authentication failed for user "irods"')
+Exiting...
+
+# vi /var/lib/pgsql/data/pg_hba.conf:
+
+host all all 127.0.0.1/32 md5
+
+# systemctl restart postgresql
+
+# python /var/lib/irods/scripts/setup_irods.py 
+The iRODS service account name needs to be defined.
+iRODS user [irods]: 
+iRODS group [irods]: 
+
++--------------------------------+
+| Setting up the service account |
++--------------------------------+
+
+Existing Group Detected: irods
+Existing Account Detected: irods
+Setting owner of /var/lib/irods to irods:irods
+Setting owner of /etc/irods to irods:irods
+iRODS server's role:
+1. provider
+2. consumer
+Please select a number or choose 0 to enter a new value [1]: 
+Updating /etc/irods/server_config.json...
+
++-----------------------------------------+
+| Configuring the database communications |
++-----------------------------------------+
+
+You are configuring an iRODS database plugin. The iRODS server cannot be started until its database has been properly configured.
+
+ODBC driver for postgres [PostgreSQL]: 
+Database server's hostname or IP address [localhost]: 
+Database server's port [5432]: 
+Database name [ICAT]: 
+Database username [irods]: 
+
+-------------------------------------------
+Database Type: postgres
+ODBC Driver:   PostgreSQL
+Database Host: localhost
+Database Port: 5432
+Database Name: ICAT
+Database User: irods
+-------------------------------------------
+
+Please confirm [yes]: 
+Database password: 
+Updating /etc/irods/server_config.json...
+Listing database tables...
+Salt for passwords stored in the database: 
+Updating /etc/irods/server_config.json...
+
++--------------------------------+
+| Configuring the server options |
++--------------------------------+
+
+iRODS server's zone name [tempZone]: testZone
+iRODS server's port [1247]: 
+iRODS port range (begin) [20000]: 
+iRODS port range (end) [20199]: 
+Control Plane port [1248]: 
+Schema Validation Base URI (or off) [file:///var/lib/irods/configuration_schemas]: 
+iRODS server's administrator username [rods]: irods
+
+-------------------------------------------
+Zone name:                  testZone
+iRODS server port:          1247
+iRODS port range (begin):   20000
+iRODS port range (end):     20199
+Control plane port:         1248
+Schema validation base URI: file:///var/lib/irods/configuration_schemas
+iRODS server administrator: irods
+-------------------------------------------
+
+Please confirm [yes]: yes
+iRODS server's zone key: 
+Zone key must be at least 1 character in length.
+iRODS server's zone key: 
+iRODS server's negotiation key (32 characters): 
+Negotiation key must be exactly 32 characters in length.
+iRODS server's negotiation key (32 characters): 
+Control Plane key (32 characters): 
+Updating /etc/irods/server_config.json...
+
++-----------------------------------+
+| Setting up the client environment |
++-----------------------------------+
+
+
+iRODS server's administrator password: 
+
+Updating /var/lib/irods/.irods/irods_environment.json...
+
++--------------------------+
+| Setting up default vault |
++--------------------------+
+
+iRODS Vault directory [/var/lib/irods/Vault]: 
+
++-------------------------+
+| Setting up the database |
++-------------------------+
+
+Listing database tables...
+Creating database tables...
+
++-------------------+
+| Starting iRODS... |
++-------------------+
+
+Validating [/var/lib/irods/.irods/irods_environment.json]... Success
+Validating [/var/lib/irods/VERSION.json]... Success
+Validating [/etc/irods/server_config.json]... Success
+Validating [/etc/irods/host_access_control_config.json]... Success
+Validating [/etc/irods/hosts_config.json]... Success
+Ensuring catalog schema is up-to-date...
+Updating to schema version 2...
+Updating to schema version 3...
+Updating to schema version 4...
+Updating to schema version 5...
+Catalog schema is up-to-date.
+Starting iRODS server...
+Success
+
++---------------------+
+| Attempting test put |
++---------------------+
+
+Putting the test file into iRODS...
+Getting the test file from iRODS...
+Removing the test file from iRODS...
+Success.
+
++--------------------------------+
+| iRODS is installed and running |
++--------------------------------+
+
+
+
+

irods_2019_rug.txt

@@ -0,0 +1,432 @@
+
+basic-design:
+
+create a datavault-storage abstraction system "data-as-a-service"
+
+start-simple: "grow-as-you-go"
+
+1 icat-server (icat-service + postgresql database local vsan)
+OS: CentOS7
+3 resource-servers (with 2 local mounts each)
+3 datacenters
+2 replica's of data
+1 replica in 1 datacenter, other replica in other datacenter
+- encrypt storage (because cloudstorage)
+- all servers are esx vm's (rug-cloud)
+- all storage is vmware datastore (rug-cloud)
+- all irods-servers/clients connect via SSL
+- authentication via ldap
+
+connection from peregrine to irods-servers is 10 Gb ethernet
+
+irods-lingo:
+
+icat-server: server containing metadata database
+irods-resource-server: server with mountpoint storing data
+provider: icat-server
+consumer: irods-resource server
+collections: directories
+objects: files
+
+local-lingo:
+
+peregrine: our HPC cluster in Groningen
+
+irods installation on centos7 2019:
+
+the icat-server:
+
+- basic/normal configuration
+- disable selinux
+- enable/configure firewall
+- set/enable ntpd
+
+# rpm --import https://packages.irods.org/irods-signing-key.asc
+# wget -qO - https://packages.irods.org/renci-irods.yum.repo | sudo tee /etc/yum.repos.d/renci-irods.yum.repo
+
+# yum install irods-server irods-database-plugin-postgres
+
+# yum install postgresql-server
+
+# postgresql-setup initdb
+Initializing database ... OK
+
+# systemctl start postgresql
+
+# su - postgres
+Last login: Fri Oct 26 11:30:44 CEST 2018 on pts/0
+
+$ psql
+psql (9.2.24)
+Type "help" for help.
+
+postgres=# CREATE USER irods WITH PASSWORD 'xxxxx';
+CREATE ROLE
+postgres=# CREATE DATABASE "ICAT";
+CREATE DATABASE
+postgres=# GRANT ALL PRIVILEGES ON DATABASE "ICAT" TO irods;
+GRANT
+postgres=# \l
+                                  List of databases
+   Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges   
+-----------+----------+----------+-------------+-------------+-----------------------
+ ICAT      | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =Tc/postgres         +
+           |          |          |             |             | postgres=CTc/postgres+
+           |          |          |             |             | irods=CTc/postgres
+ postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
+ template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
+           |          |          |             |             | postgres=CTc/postgres
+ template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
+           |          |          |             |             | postgres=CTc/postgres
+(4 rows)
+
+
+# vi /var/lib/pgsql/data/pg_hba.conf:
+
+host all all 127.0.0.1/32 md5
+host all all 129.125.77.0/32 md5
+
+# systemctl restart postgresql
+
+# python /var/lib/irods/scripts/setup_irods.py 
+The iRODS service account name needs to be defined.
+iRODS user [irods]: 
+iRODS group [irods]: 
+
++--------------------------------+
+| Setting up the service account |
++--------------------------------+
+
+Existing Group Detected: irods
+Existing Account Detected: irods
+Setting owner of /var/lib/irods to irods:irods
+Setting owner of /etc/irods to irods:irods
+iRODS server's role:
+1. provider
+2. consumer
+Please select a number or choose 0 to enter a new value [1]: 
+Updating /etc/irods/server_config.json...
+
++-----------------------------------------+
+| Configuring the database communications |
++-----------------------------------------+
+
+You are configuring an iRODS database plugin. The iRODS server cannot be started until its database has been properly configured.
+
+ODBC driver for postgres [PostgreSQL]: 
+Database server's hostname or IP address [localhost]: 
+Database server's port [5432]: 
+Database name [ICAT]: 
+Database username [irods]: 
+
+-------------------------------------------
+Database Type: postgres
+ODBC Driver:   PostgreSQL
+Database Host: localhost
+Database Port: 5432
+Database Name: ICAT
+Database User: irods
+-------------------------------------------
+
+Please confirm [yes]: 
+Database password: 
+Updating /etc/irods/server_config.json...
+Listing database tables...
+Salt for passwords stored in the database: 
+Updating /etc/irods/server_config.json...
+
++--------------------------------+
+| Configuring the server options |
++--------------------------------+
+
+iRODS server's zone name [tempZone]: testZone
+iRODS server's port [1247]: 
+iRODS port range (begin) [20000]: 
+iRODS port range (end) [20199]: 
+Control Plane port [1248]: 
+Schema Validation Base URI (or off) [file:///var/lib/irods/configuration_schemas]: 
+iRODS server's administrator username [rods]: irods
+
+-------------------------------------------
+Zone name:                  testZone
+iRODS server port:          1247
+iRODS port range (begin):   20000
+iRODS port range (end):     20199
+Control plane port:         1248
+Schema validation base URI: file:///var/lib/irods/configuration_schemas
+iRODS server administrator: irods
+-------------------------------------------
+
+Please confirm [yes]: yes
+iRODS server's zone key: 
+Zone key must be at least 1 character in length.
+iRODS server's zone key: 
+iRODS server's negotiation key (32 characters): 
+Negotiation key must be exactly 32 characters in length.
+iRODS server's negotiation key (32 characters): 
+Control Plane key (32 characters): 
+Updating /etc/irods/server_config.json...
+
++-----------------------------------+
+| Setting up the client environment |
++-----------------------------------+
+
+iRODS server's administrator password: 
+
+Updating /var/lib/irods/.irods/irods_environment.json...
+
++--------------------------+
+| Setting up default vault |
++--------------------------+
+
+iRODS Vault directory [/var/lib/irods/Vault]: 
+
++-------------------------+
+| Setting up the database |
++-------------------------+
+
+Listing database tables...
+Creating database tables...
+
++-------------------+
+| Starting iRODS... |
++-------------------+
+
+Validating [/var/lib/irods/.irods/irods_environment.json]... Success
+Validating [/var/lib/irods/VERSION.json]... Success
+Validating [/etc/irods/server_config.json]... Success
+Validating [/etc/irods/host_access_control_config.json]... Success
+Validating [/etc/irods/hosts_config.json]... Success
+Ensuring catalog schema is up-to-date...
+Updating to schema version 2...
+Updating to schema version 3...
+Updating to schema version 4...
+Updating to schema version 5...
+Catalog schema is up-to-date.
+Starting iRODS server...
+Success
+
++---------------------+
+| Attempting test put |
++---------------------+
+
+Putting the test file into iRODS...
+Getting the test file from iRODS...
+Removing the test file from iRODS...
+Success.
+
++--------------------------------+
+| iRODS is installed and running |
++--------------------------------+
+
+installation of irods-resource-server:
+
+- disable selinux
+- enable/configure firewall
+- set/enable ntpd
+
+install irods-repository:
+
+# rpm --import https://packages.irods.org/irods-signing-key.asc
+# wget -qO - https://packages.irods.org/renci-irods.yum.repo | sudo tee /etc/yum.repos.d/renci-irods.yum.repo
+# yum install epel-release
+# yum install irods-server
+# python /var/lib/irods/scripts/setup_irods.py 
+
+set this server to a consumer (resource-server) provider= icat-server
+
+encrypt storage:
+
+create keyfile:
+
+# echo "some difficult string" >> /etc/keyfile
+# chmod 600 /etc/keyfile
+
+# cryptsetup luksFormat -y -v /dev/sdb --key-file /etc/keyfile
+# cryptsetup luksFormat -y -v /dev/sdc --key-file /etc/keyfile
+
+open encrypted storage:
+
+# cryptsetup luksOpen /dev/sdb irods01 --key-file /etc/keyfile
+# cryptsetup luksOpen /dev/sdc irods02 --key-file /etc/keyfile
+
+format storage:
+
+# mkfs.xfs /dev/mapper/irods01
+# mkfs.xfs /dev/mapper/irods02
+
+mount storage:
+
+# mount /dev/mapper/irods01 /mnt/01/
+# mount /dev/mapper/irods02 /mnt/02/
+
+create resources:
+
+as user irods on whatever irods-server:
+
+iadmin mkresc ReplA replication
+iadmin mkresc ReplB replication
+iadmin mkresc ReplC replication
+
+iadmin mkresc Vol01 rdms-prod-resc0.data.rug.nl:/mnt/01/Vault
+iadmin mkresc Vol02 rdms-prod-resc0.data.rug.nl:/mnt/02/Vault
+
+iadmin mkresc Vol11 rdms-prod-resc1.data.rug.nl:/mnt/11/Vault
+iadmin mkresc Vol12 rdms-prod-resc1.data.rug.nl:/mnt/12/Vault
+
+iadmin mkresc Vol21 rdms-prod-resc2.data.rug.nl:/mnt/21/Vault
+iadmin mkresc Vol22 rdms-prod-resc2.data.rug.nl:/mnt/22/Vault
+
+iadmin addchildtoresc ReplA Vol02
+iadmin addchildtoresc ReplA Vol11
+
+iadmin addchildtoresc ReplB Vol01
+iadmin addchildtoresc ReplB Vol22
+
+iadmin addchildtoresc ReplC Vol12
+iadmin addchildtoresc ReplC Vol21
+
+iadmin mkresc pta passthru
+iadmin mkresc ptb passthru
+iadmin mkresc ptc passthru
+
+iadmin addchildtoresc pta ReplA
+iadmin addchildtoresc ptb ReplB
+iadmin addchildtoresc ptc ReplC
+
+iadmin mkresc Randy random
+
+iadmin addchildtoresc Randy pta
+
+iadmin mkresc pt_top passthru
+iadmin addchildtoresc pt_top Randy
+
+p216149@pg-interactive:~ ilsresc 
+
+pt_top:passthru
+└── Randy:random
+    ├── pta:passthru
+    │   └── ReplA:replication
+    │       ├── Vol02:unixfilesystem
+    │       └── Vol11:unixfilesystem
+    ├── ptb:passthru
+    │   └── ReplB:replication
+    │       ├── Vol01:unixfilesystem
+    │       └── Vol22:unixfilesystem
+    └── ptc:passthru
+        └── ReplC:replication
+            ├── Vol12:unixfilesystem
+            └── Vol21:unixfilesystem
+            
+proof:
+
+p216149@pg-interactive:~ ils -l
+/rug/home/g.j.c.strikwerda@rug.nl:
+  g.j.c.strikw      0 pt_top;Randy;ptb;ReplB;Vol01    515106669 2019-06-13.16:48 & tivo.tar.gz
+  g.j.c.strikw      1 pt_top;Randy;ptb;ReplB;Vol22    515106669 2019-06-13.16:48 & tivo.tar.gz
+
+file: tivo.tar.gz is stored on Vol01 and on Vol22 (replicated by ReplB resource)
+  
+p216149@pg-interactive:~ iput ./package.tar.gz 
+p216149@pg-interactive:~ ils -l
+/rug/home/g.j.c.strikwerda@rug.nl:
+  g.j.c.strikw      0 pt_top;Randy;pta;ReplA;Vol02        36609 2019-07-03.11:24 & package.tar.gz
+  g.j.c.strikw      1 pt_top;Randy;pta;ReplA;Vol11        36609 2019-07-03.11:24 & package.tar.gz
+
+file: package.tar.gz is stored on Vol02 and on Vol11 (replicated by ReplA resource)
+
+client-config looks like this:
+
+p216149@pg-interactive:.irods cat irods_environment.json
+{
+    "irods_client_server_negotiation": "request_server_negotiation", 
+    "irods_client_server_policy": "CS_NEG_REQUIRE",
+    "irods_connection_pool_refresh_time_in_seconds": 300, 
+    "irods_default_hash_scheme": "SHA256", 
+    "irods_default_number_of_transfer_threads": 4, 
+    "irods_default_resource": "pt_top", 
+    "irods_encryption_algorithm": "AES-256-CBC", 
+    "irods_encryption_key_size": 32, 
+    "irods_encryption_num_hash_rounds": 16, 
+    "irods_encryption_salt_size": 8, 
+    "irods_host": "rdms-prod-icat.data.rug.nl", 
+    "irods_match_hash_policy": "compatible", 
+    "irods_maximum_size_for_single_buffer_in_megabytes": 32, 
+    "irods_port": 1247, 
+    "irods_transfer_buffer_size_for_parallel_transfer_in_megabytes": 4, 
+    "irods_user_name": "g.j.c.strikwerda@rug.nl", 
+    "irods_zone_name": "rug", 
+    "schema_name": "irods_environment", 
+    "schema_version": "v3"
+}
+
+
+backup-strategy:
+
+july 2019:
+
+- icat: daily dump of pg-database to /var/backups/ daily backup to our tivoli TSM system
+- resc-servers: daily backup of /mnt/vol<number>/Vault/Trash/ to our tivoli TSM system
+
+so we only backup the trash! Which is most of the time the data users want back after error-deletion
+
+metalnx webfrontend for irods:
+
+checkout software:
+
+$ git clone https://github.com/irods-contrib/metalnx-web.git
+
+create db for metalnx on postgres:
+
+$ (sudo) su - postgres
+postgres$ psql
+psql> CREATE USER metalnx WITH PASSWORD '<db password metalnx>';
+psql> CREATE DATABASE "IRODS-EXT";
+psql> GRANT ALL PRIVILEGES ON DATABASE "IRODS-EXT" TO metalnx;
+
+change config:
+
+vi /home/ger/metalnx/metalnx-web/etc/irods-ext/metalnx.properties:
+
+$ cat metalnx.properties
+irods.host=<ipaddress icat-server>
+irods.port=1247
+irods.zoneName=<your zone-name>
+irods.admin.user=irods
+irods.admin.password=<irods admin pass>
+
+# metalnx database settings
+
+db.driverClassName=org.postgresql.Driver
+db.url=jdbc:postgresql://<ip-address icat-server:5432/IRODS-EXT
+db.username=metalnx
+db.password=<db password metalnx>
+
+run:
+
+$ docker run -d   -p 8080:8080   -v /home/ger/metalnx/metalnx-web/etc/irods-ext:/etc/irods-ext   --add-host hostcomputer:172.17.0.1   --name metalnx   irods/metalnx:latest
+
+connect:
+
+http://icat-server:8080/metalnx/
+
+
+
+Future work:
+
+- clean up the trash regularly (script?)
+- build more irods environments/playgrounds to learn/test/play/fun
+- set up auditing (ampq with ELK stack backend)
+- set a performance baseline
+- find out user needs (budget, storage, performance)
+- create replication-check-scripts (check/pinpoint/report missing replica's)
+- do some disaster drills/scenario's 
+- create 2 resource servers in irods on datahandeling nodes (Lustre backend, IB network, direct connected to peregrine)
+- performance testing (what will be the current bottleneck?)
+- adding more icat-servers (behind F5 loadbalancer) connected to a separate database(cluster) (icat-scaleing)
+- create landingzone on peregrine (for irods to pick up files automated)
+- compute-to-data, data-to-compute testing
+- irods-hpc-testing: integration metadata BeeGFS, integration metadata Lustre, let iRODS read changelogs@metadata
+- storage-tiering: tape-archive
+- test out this new iput-on-steriods for HPC performance testing/differences
+- test with S3 object store  as storage-backends (big-data-not-on-filesytem, but big-data-object-storage)

kube-cluster/README.md

@@ -0,0 +1,51 @@
+kubernetes ala Ger:
+
+1 Vagrantfile for provisioning 3 clean CentOS7 virtualbox vm's:
+
+Vagrantfile:
+
+- master.ger.test  (master-node)
+- worker1.ger.test (worker-node)
+- worker2.ger.test (worker-node)
+
+kube-depencies.yml: installing kubernetes depencies on all the nodes:
+master.yml        : containing the setup of the kubernetes-cluster on the master:
+worker.yml        : containing setup of workers/joining the cluster
+
+- /etc/hosts: host-file
+
+hosts: ansible hosts info
+
+Use:
+
+provision nodes:
+
+$ vagrant --instance=kubernetes 
+
+install depencies:
+
+$ ansible-playbook -i hosts ./kube-dependencies.yml
+
+install master-node:
+
+$ ansible-playbook -i hosts ./master.yml
+
+install worker-nodes:
+
+$ ansible-playbook -i hosts ./workers.yml
+
+klaar:
+
+$ ssh ger@master
+
+[ger@master ~]$ kubectl get nodes
+NAME               STATUS   ROLES    AGE   VERSION
+master.ger.test    Ready    master   2d    v1.12.1
+worker1.ger.test   Ready    worker   47h   v1.12.1
+worker2.ger.test   Ready    worker   47h   v1.12.1
+
+possilbe extras:
+
+/etc/sysconfig/kubelet:  KUBELET_EXTRA_ARGS=--runtime-cgroups=/systemd/system.slice --kubelet-cgroups=/systemd/system.slice
+
+label node: kubectl label node worker1.ger.test node-role.kubernetes.io/worker=worker

kube-cluster/Vagrantfile

@@ -0,0 +1,93 @@
+# coding: utf-8
+# -*- mode: ruby -*-
+# vi: set ft=ruby :
+
+# GS: run script after install:
+ $post_script = <<SCRIPT
+ yum install epel-release -y
+ yum install htop -y
+ yum install net-tools -y
+ 
+ useradd ger
+ mkdir /home/ger/.ssh
+ chown ger:ger /home/ger/.ssh/
+ chmod 700 /home/ger/.ssh/
+ cat /tmp/ger.pubkey >> /home/ger/.ssh/authorized_keys
+ 
+ mkdir /root/.ssh
+ chown root:root /root/.ssh/
+ chmod 700 /root/.ssh/
+ cat /tmp/ger.pubkey >> /root/.ssh/authorized_keys
+ 
+ cp /tmp/hosts /etc/hosts
+ cp /tmp/fire_stop.sh /root/fire_stop.sh
+ SCRIPT
+
+# Retrieve instance from command line.
+require 'getoptlong'
+
+opts = GetoptLong.new(
+  [ '--instance', GetoptLong::OPTIONAL_ARGUMENT ]
+)
+
+instance='combined'
+opts.each do |opt, arg|
+  case opt
+    when '--instance'
+      instance=arg
+  end
+end
+
+# Configuration variables.
+VAGRANTFILE_API_VERSION = "2"
+
+BOX = 'centos/7'
+GUI = false
+CPU = 1
+RAM = 1024
+
+DOMAIN  = ".ger.test"
+NETWORK = "192.168.50."
+NETMASK = "255.255.255.0"
+
+if instance == "kubernetes" then
+  HOSTS = { 
+   "master"   => [NETWORK+"21", CPU, RAM, GUI, BOX],
+   "worker1"  => [NETWORK+"22", CPU, RAM, GUI, BOX],
+   "worker2"  => [NETWORK+"23", CPU, RAM, GUI, BOX],
+  }
+end
+
+Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
+  #config.ssh.insert_key ='true' 
+  config.vm.provision "file", source: "/home/ger/.ssh/id_ecdsa.pub", destination: "/tmp/ger.pubkey"  
+  config.vm.provision "file", source: "/etc/hosts", destination: "/tmp/hosts"
+  config.vm.provision "file", source: "/home/ger/fire_stop.sh", destination: "/tmp/fire_stop.sh"
+
+  HOSTS.each do | (name, cfg) |
+    ipaddr, cpu, ram, gui, box = cfg
+
+    config.vm.define name do |machine|
+      machine.vm.box = box
+
+      machine.vm.provider "virtualbox" do |vbox|
+        vbox.gui    = gui
+        vbox.cpus   = cpu
+        vbox.memory = ram
+        vbox.name   = name
+        vbox.customize ["guestproperty", "set", :id, "/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", 10000]
+      end
+
+      machine.vm.hostname = name + DOMAIN
+      machine.vm.network 'private_network', ip: ipaddr, netmask: NETMASK
+      machine.vm.synced_folder ".", "/vagrant", disabled: true
+      machine.vm.provision "shell",
+        inline: "sudo timedatectl set-timezone Europe/Amsterdam"
+      machine.vm.provision "shell", 
+        inline: "cat /tmp/ger.pubkey >> /home/vagrant/.ssh/authorized_keys"
+      machine.vm.provision "shell", 
+        inline: $post_script
+    end
+  end
+
+end

kube-cluster/etc.hosts

@@ -0,0 +1,20 @@
+127.0.0.1	localhost
+127.0.1.1	ger-lpt-werk
+
+# The following lines are desirable for IPv6 capable hosts
+::1     ip6-localhost ip6-loopback
+fe00::0 ip6-localnet
+ff00::0 ip6-mcastprefix
+ff02::1 ip6-allnodes
+ff02::2 ip6-allrouters
+
+192.168.50.11 portal.ger.test portal
+192.168.50.12 icat.ger.test icat
+192.168.50.13 resc1.ger.test resc1
+192.168.50.14 resc2.ger.test resc2
+
+192.168.50.15 test01
+
+192.168.50.21 master.ger.test master
+192.168.50.22 worker1.ger.test worker1
+192.168.50.23 worker2.ger.test worker2

kube-cluster/fire_stop.sh

@@ -0,0 +1,15 @@
+#!/bin/bash
+
+iptables -F
+iptables -X
+iptables -Z
+iptables -N LOGDROP
+iptables -A LOGDROP -j LOG
+iptables -A LOGDROP -j DROP
+
+
+iptables -P FORWARD ACCEPT
+iptables -P OUTPUT ACCEPT
+iptables -P INPUT ACCEPT
+iptables --list | grep policy
+

kube-cluster/hosts

@@ -0,0 +1,6 @@
+[masters]
+master ansible_host=master ansible_user=root
+
+[workers]
+worker1 ansible_host=worker1 ansible_user=root
+worker2 ansible_host=worker2 ansible_user=root

kube-cluster/kube-dependencies.yml

@@ -0,0 +1,86 @@
+- hosts: all
+  become: yes
+  tasks:
+   - name: remove swap from /etc/fstab
+     mount:
+       name: swap
+       fstype: swap
+       state: absent
+
+   - name: disable swap
+     command: swapoff -a
+     when: ansible_swaptotal_mb > 0
+
+   - name: install Docker
+     yum:
+       name: docker
+       state: present
+       update_cache: true
+
+   - name: start Docker
+     service:
+       name: docker
+       state: started
+
+   - name: enable Docker
+     service: 
+       name: docker
+       state: started
+       enabled: yes 
+
+   - name: disable firewalld
+     service: 
+       name: firewalld
+       enabled: no 
+
+   - name: disable SELinux
+     command: setenforce 0
+
+   - name: disable SELinux on reboot
+     selinux:
+       state: disabled
+
+   - name: ensure net.bridge.bridge-nf-call-ip6tables is set to 1
+     sysctl:
+      name: net.bridge.bridge-nf-call-ip6tables
+      value: 1
+      state: present
+
+   - name: ensure net.bridge.bridge-nf-call-iptables is set to 1
+     sysctl:
+      name: net.bridge.bridge-nf-call-iptables
+      value: 1
+      state: present
+
+   - name: add Kubernetes' YUM repository
+     yum_repository:
+      name: Kubernetes
+      description: Kubernetes YUM repository
+      baseurl: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
+      gpgkey: https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
+      gpgcheck: yes
+
+   - name: install kubelet
+     yum:
+        name: kubelet
+        state: present
+        update_cache: true
+
+   - name: install kubeadm
+     yum:
+        name: kubeadm
+        state: present
+
+   - name: start kubelet
+     service:
+       name: kubelet
+       enabled: yes
+       state: started
+
+- hosts: master
+  become: yes
+  tasks:
+   - name: install kubectl
+     yum:
+        name: kubectl
+        state: present

kube-cluster/master.yml

@@ -0,0 +1,31 @@
+- hosts: master
+  become: yes
+  tasks:
+    - name: initialize the cluster
+      shell: kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.50.21 >> cluster_initialized.txt
+      args:
+        chdir: $HOME
+        creates: cluster_initialized.txt
+
+    - name: create .kube directory
+      become: yes
+      become_user: ger
+      file:
+        path: $HOME/.kube
+        state: directory
+        mode: 0755
+
+    - name: copy admin.conf to user's kube config
+      copy:
+        src: /etc/kubernetes/admin.conf
+        dest: /home/ger/.kube/config
+        remote_src: yes
+        owner: ger
+
+    - name: install Pod network
+      become: yes
+      become_user: ger
+      shell: kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml >> pod_network_setup.txt
+      args:
+        chdir: $HOME
+        creates: pod_network_setup.txt

kube-cluster/workers.yml

@@ -0,0 +1,22 @@
+- hosts: master
+  become: yes
+  gather_facts: false
+  tasks:
+    - name: get join command
+      shell: kubeadm token create --print-join-command
+      register: join_command_raw
+
+    - name: set join command
+      set_fact:
+        join_command: "{{ join_command_raw.stdout_lines[0] }}"
+
+
+- hosts: workers
+  become: yes
+  tasks:
+    - name: join cluster
+      shell: "{{ hostvars['master'].join_command }} >> node_joined.txt"
+      args:
+        chdir: $HOME
+        creates: node_joined.txt
+

kubernetes.replicasets

@@ -0,0 +1,93 @@
+kubernetes replica sets:
+
+aanmaken manifest met replicas: 1
+
+[ger@master ~]$ cat kuard-rs.yaml 
+apiVersion: extensions/v1beta1
+kind: ReplicaSet
+metadata: 
+  name: kuard
+spec:
+  replicas: 1
+  template: 
+    metadata: 
+      labels:
+        app: kuard
+        version: "2"
+    spec:
+      containers:
+        - name: kuard
+          image: "gcr.io/kuar-demo/kuard-amd64:2"
+
+
+[ger@master ~]$ kubectl apply -f ./kuard-rs.yaml 
+replicaset.extensions/kuard created
+
+check:
+
+[ger@master ~]$ kubectl get pods
+NAME          READY   STATUS    RESTARTS   AGE
+kuard-f25dt   1/1     Running   0          24s
+
+
+meer info:
+
+[ger@master ~]$ kubectl describe rs kuard
+Name:         kuard
+Namespace:    default
+Selector:     app=kuard,version=2
+Labels:       app=kuard
+              version=2
+Annotations:  kubectl.kubernetes.io/last-applied-configuration:
+                {"apiVersion":"extensions/v1beta1","kind":"ReplicaSet","metadata":{"annotations":{},"name":"kuard","namespace":"default"},"spec":{"replica...
+Replicas:     1 current / 1 desired
+Pods Status:  1 Running / 0 Waiting / 0 Succeeded / 0 Failed
+Pod Template:
+  Labels:  app=kuard
+           version=2
+  Containers:
+   kuard:
+    Image:        gcr.io/kuar-demo/kuard-amd64:2
+    Port:         <none>
+    Host Port:    <none>
+    Environment:  <none>
+    Mounts:       <none>
+  Volumes:        <none>
+Events:
+  Type    Reason            Age   From                   Message
+  ----    ------            ----  ----                   -------
+  Normal  SuccessfulCreate  40s   replicaset-controller  Created pod: kuard-f25dt
+
+opschalen naar 4 replica's:
+
+[ger@master ~]$ kubectl scale rs kuard --replicas=4 --all
+replicaset.extensions/kuard scaled
+
+[ger@master ~]$ kubectl get pods
+NAME          READY   STATUS              RESTARTS   AGE
+kuard-66877   0/1     ContainerCreating   0          9s
+kuard-8trx2   0/1     ContainerCreating   0          9s
+kuard-dlb2c   0/1     ContainerCreating   0          9s
+kuard-f25dt   1/1     Running             0          4m59s
+
+[ger@master ~]$ kubectl get pods
+NAME          READY   STATUS    RESTARTS   AGE
+kuard-66877   1/1     Running   0          30s
+kuard-8trx2   1/1     Running   0          30s
+kuard-dlb2c   1/1     Running   0          30s
+kuard-f25dt   1/1     Running   0          5m20s
+
+autoscale:
+
+[ger@master ~]$ kubectl autoscale rs kuard --min=2 --max=5 --cpu-percent=80
+horizontalpodautoscaler.autoscaling/kuard autoscaled
+
+
+check hpa (horizontal pod autoscaler):
+
+[ger@master ~]$ kubectl get hpa
+NAME    REFERENCE          TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
+kuard   ReplicaSet/kuard   <unknown>/80%   2         5         0          11s
+
+
+

kubernetes.runapp

@@ -0,0 +1,62 @@
+running application on kubernetes:
+
+[ger@master ~]$ kubectl get nodes
+NAME               STATUS   ROLES    AGE    VERSION
+master.ger.test    Ready    master   7d1h   v1.12.1
+worker1.ger.test   Ready    worker   7d1h   v1.12.1
+worker2.ger.test   Ready    worker   7d1h   v1.12.1
+
+create deployment nginx:
+
+[ger@master ~]$ kubectl run nginx --image nginx --port 80
+kubectl run --generator=deployment/apps.v1beta1 is DEPRECATED and will be removed in a future version. Use kubectl create instead.
+deployment.apps/nginx created
+
+create service nginx and expose port 80:
+
+[ger@master ~]$ kubectl expose deploy nginx --port 80 --target-port 80 --type NodePort
+service/nginx exposed
+
+[ger@master ~]$ kubectl get services
+NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
+kubernetes   ClusterIP   10.96.0.1       <none>        443/TCP        7d1h
+nginx        NodePort    10.109.244.16   <none>        80:32368/TCP   71s
+
+port 80 nginx is now exposed on one of the nodes on port 32368:
+
+[ger@master ~]$ curl worker2.ger.test:32368
+<!DOCTYPE html>
+<html>
+
+<h1>Welcome to nginx!</h1>
+<p>If you see this page, the nginx web server is successfully installed and
+working. Further configuration is required.</p>
+
+<p>For online documentation and support please refer to
+<a href="http://nginx.org/">nginx.org</a>.<br/>
+Commercial support is available at
+<a href="http://nginx.com/">nginx.com</a>.</p>
+
+<p><em>Thank you for using nginx.</em></p>
+</body>
+</html>
+
+cleanup:
+
+first delete service:
+
+[ger@master ~]$ kubectl delete service nginx
+service "nginx" deleted
+
+[ger@master ~]$ kubectl get service
+NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
+kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP   7d1h
+
+then delete deployment:
+
+[ger@master ~]$ kubectl delete deployment nginx
+deployment.extensions "nginx" deleted
+
+[ger@master ~]$ kubectl get deployment
+No resources found.
+

kvm.txt

@@ -0,0 +1,90 @@
+
+create image: 
+
+ger@ger-lpt-werk:~/vm$ qemu-img create -f qcow2 test-image.qcow2 25G
+Formatting 'test-image.qcow2', fmt=qcow2 size=26843545600 cluster_size=65536 lazy_refcounts=off refcount_bits=16
+
+ger@ger-lpt-werk:~/vm$ ls -ltr
+total 196
+-rw-r--r-- 1 ger ger 197008 apr  8 16:53 test-image.qcow2
+
+download iso_image
+
+create/start vm:
+
+ger@ger-lpt-werk:~/vm$ qemu-system-x86_64 -cdrom ../iso/ubuntu-server.iso -cpu host -enable-kvm -m 2G -smp 2 -drive file=./test-image.qcow2,format=qcow2
+
+start vm after install:
+
+ger@ger-lpt-werk:~/vm$ qemu-system-x86_64 -cpu host -enable-kvm -m 2G -smp 2 -drive file=./test-image.qcow2,format=qcow2 -name vm01
+
+create extra disk:
+
+ger@ger-lpt-werk:~/vm$ qemu-img create -f qcow2 ./extra_disk.qcow2 5G
+Formatting './extra_disk.qcow2', fmt=qcow2 size=5368709120 cluster_size=65536 lazy_refcounts=off refcount_bits=16
+
+$ virsh attach-disk vm01 /home/ger/vm/extra_disk.qcow2 vdb --cache none
+
+virsh run:
+
+ger@ger-lpt-werk:~/vm$ virt-install --name=vm01 --ram=2048 --vcpus=2 --disk path=./test-image.qcow2 --boot=hd
+WARNING  No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results.
+
+Starting install..
+
+ger@ger-lpt-werk:~/vm$ virsh destroy vm01
+Domain vm01 destroyed
+
+ger@ger-lpt-werk:~/vm$ virsh start vm01
+Domain vm01 started
+
+ger@ger-lpt-werk:~/vm$ virsh list --all
+ Id   Name   State
+----------------------
+ 2    vm01   running
+  
+add disk via dd:
+
+ger@ger-lpt-werk:~/vm$ dd if=/dev/zero of=./disk_dd.dsk count=5000 bs=1M
+5000+0 records in
+5000+0 records out
+5242880000 bytes (5,2 GB, 4,9 GiB) copied, 6,34483 s, 826 MB/s
+ger@ger-lpt-werk:~/vm$ du -sh ./disk_dd.dsk 
+4,9G    ./disk_dd.dsk
+
+ger@ger-lpt-werk:~/vm$ virsh attach-disk vm01 /home/ger/vm/disk_dd.dsk vdb --cache none
+Disk attached successfully
+
+persistent disk:
+
+ger@ger-lpt-werk:~/vm$ virsh attach-disk vm01 /home/ger/vm/disk_dd.dsk vdb --persistent --cache none
+Disk attached successfully
+
+create extra disk ala rdms:
+
+ger@ger-lpt-werk:~/vm$ qemu-img create -o preallocation=metadata -f qcow2 rdms-prod.qcow2 2G
+Formatting 'rdms-prod.qcow2', fmt=qcow2 size=2147483648 cluster_size=65536 preallocation=metadata lazy_refcounts=off refcount_bits=16
+
+ger@ger-lpt-werk:~/vm$ virsh attach-disk vm01 --target vdd --persistent --driver qemu --subdriver qcow2 --source /home/ger/vm/rdms-prod.qcow2
+Disk attached successfully
+
+root@irods01:/home/ger# lsblk
+NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+sda                         8:0    0   25G  0 disk 
+├─sda1                      8:1    0    1M  0 part 
+├─sda2                      8:2    0  1.5G  0 part /boot
+└─sda3                      8:3    0 23.5G  0 part 
+  └─ubuntu--vg-ubuntu--lv 253:0    0 11.8G  0 lvm  /
+vda                       252:0    0  4.9G  0 disk 
+vdb                       252:16   0    2G  0 disk 
+
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: [1af4:1001] type 00 class 0x010000
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: reg 0x10: [io  0x0000-0x007f]
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: reg 0x14: [mem 0x00000000-0x00000fff]
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit pref]
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: BAR 4: assigned [mem 0x100000000-0x100003fff 64bit pref]
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: BAR 1: assigned [mem 0x80000000-0x80000fff]
+[Wed Apr 13 07:24:06 2022] pci 0000:00:09.0: BAR 0: assigned [io  0x1000-0x107f]
+[Wed Apr 13 07:24:06 2022] virtio-pci 0000:00:09.0: enabling device (0000 -> 0003)
+[Wed Apr 13 07:24:06 2022] virtio_blk virtio3: [vdb] 4194304 512-byte logical blocks (2.15 GB/2.00 GiB)
+ 

lustre.peer_credits

@@ -0,0 +1,91 @@
+IB tweaks Mellanox:
+
+default ko2iblnd.conf:
+
+[root@pg-mds01 ~]# cat /etc/modprobe.d/ko2iblnd.conf 
+
+alias ko2iblnd-opa ko2iblnd
+options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024 concurrent_sends=256 ntx=2048 map_on_demand=32 fmr_pool_size=2048 fmr_flush_trigger=512 fmr_cache=1 conns_per_peer=4
+
+install ko2iblnd /usr/sbin/ko2iblnd-probe
+
+ko2iblnd-opa is the 'wrong' interface, we use Mellanox cards. 
+
+To check for example the peer_credits setting in this example:
+
+[root@pg-mds01 ~]# cat /proc/sys/lnet/peers
+nid                      refs state  last   max   rtr   min    tx   min queue
+0@lo                        1    NA    -1     0     0     0     0     0 0
+172.23.52.179@o2ib          1    NA    -1     8     8     8     8    -8 0
+172.23.52.35@o2ib           1    NA    -1     8     8     8     8    -4 0
+172.23.52.124@o2ib          1    NA    -1     8     8     8     8   -11 0
+172.23.52.69@o2ib           1    NA    -1     8     8     8     8   -11 0
+172.23.52.158@o2ib          1    NA    -1     8     8     8     8   -11 0
+172.23.52.14@o2ib           1    NA    -1     8     8     8     8   -11 0
+172.23.52.103@o2ib          1    NA    -1     8     8     8     8   -11 0
+172.23.52.192@o2ib          1    NA    -1     8     8     8     8   -10 0
+172.23.52.48@o2ib           1    NA    -1     8     8     8     8   -11 0
+172.23.52.137@o2ib          1    NA    -1     8     8     8     8    -9 0
+172.23.54.2@o2ib            1    NA    -1     8     8     8     8    -8 0
+172.23.52.82@o2ib           1    NA    -1     8     8     8     8   -11 0
+172.23.55.212@o2ib          1    NA    -1     8     8     8     8     8 0
+
+You can see the peer_credits have max value of 8..
+
+
+should be like this:
+
+[root@dh2-mds01 ~]# cat /etc/modprobe.d/ko2iblnd.conf 
+
+options ko2iblnd peer_credits=128 peer_credits_hiw=64 credits=1024 concurrent_sends=256 ntx=2048 map_on_demand=32 fmr_pool_size=2048 fmr_flush_trigger=512 fmr_cache=1 conns_per_peer=4
+
+After reboot/reload of lnd module you can check the peer_credits:
+
+[root@dh2-mds01 ~]# cat /proc/sys/lnet/peers
+nid                      refs state  last   max   rtr   min    tx   min queue
+0@lo                        1    NA    -1     0     0     0     0     0 0
+172.23.53.156@o2ib2         1    NA    -1   128   128   128   128   -19 0
+172.23.57.43@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.4@o2ib2           2    NA    -1   128   128   128   127   -49 672
+172.23.53.9@o2ib2           1    NA    -1   128   128   128   128   126 0
+172.23.53.1@o2ib2           1    NA    -1   128   128   128   128   102 0
+172.23.53.158@o2ib2         1    NA    -1   128   128   128   128 -1601 0
+172.23.57.45@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.6@o2ib2           1    NA    -1   128   128   128   128   121 0
+172.23.53.155@o2ib2         1    NA    -1   128   128   128   128   -92 0
+172.23.57.42@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.57.47@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.8@o2ib2           1    NA    -1   128   128   128   128   126 0
+172.23.57.52@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.157@o2ib2         1    NA    -1   128   128   128   128    32 0
+172.23.57.44@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.204@o2ib2         1    NA    -1   128   128   128   128   127 0
+172.23.53.5@o2ib2           1    NA    -1   128   128   128   128   100 0
+172.23.57.49@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.10@o2ib2          1    NA    -1   128   128   128   128   126 0
+172.23.57.41@tcp12          1    NA    -1     8     8     8     8     6 0
+172.23.53.2@o2ib2           1    NA    -1   128   128   128   128   103 0
+172.23.57.46@tcp12          1    NA    -1     8     8     8     8     6 0
+
+On ib interfaces you can now see the peer_credits are on 128, on tcp (not changed) the peer credits are still on default(8).
+
+Futher explanation of the settings:
+     
+peer_credits=128 - the number of concurrent sends to a single peer
+peer_credits_hiw=64 - Hold in Wait – when to eagerly return credits
+credits=1024 - the number of concurrent sends (to all peers)
+concurrent_sends=256 - send work-queue sizing
+ntx=2048 - the number of message descriptors that are pre-allocated when the ko2iblnd module is loaded in the kernel
+map_on_demand=32 - the number of noncontiguous memory regions that will be mapped into a virtual contiguous region
+fmr_pool_size=2048 - the size of the Fast Memory registration (FMR) pool (must be >= ntx/4)
+fmr_flush_trigger=512 - the dirty FMR pool flush trigger
+fmr_cache=1 - enable FMR caching
+conns_per_peer=4 - create multiple queue pairs per peer to allow higher throughput from a single client. This is of most benefit to OPA interfaces, when coupled with the krcvqs parameter of the OPA hfi1 kernel driver. The hfi1 driver option krcvqs must also be set. It is recommended to set krcvqs=4. In some cases, setting krcvqs=8 will yield improved IO performance, but this can impact other workloads, especially on clients. If queue-pair memory usage becomes excessive, reduce the ko2iblnd conns_per_peer value to 2 and krcvqs=2. 
+
+The default values used by Lustre if no parameters are given is:
+
+peer_credits=8
+peer_credits_hiw=8
+concurrent_sends=8
+credits=64
+

lustre.tips

@@ -0,0 +1,153 @@
+Lustre tips/tricks:
+
+check if quota is set on MDT's:
+
+[root@umcg-metadata03 ~]# lctl get_param osd-ldiskfs.*.quota_slave.info
+osd-ldiskfs.umcgst08-MDT0000.quota_slave.info=
+target name:    umcgst08-MDT0000
+pool ID:        0
+type:           md
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+
+check if quota is set on OST's:
+
+[root@umcg-storage03 ~]# lctl get_param osd-ldiskfs.*.quota_slave.info
+osd-ldiskfs.umcgst08-OST0001.quota_slave.info=
+target name:    umcgst08-OST0001
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0002.quota_slave.info=
+target name:    umcgst08-OST0002
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0003.quota_slave.info=
+target name:    umcgst08-OST0003
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0004.quota_slave.info=
+target name:    umcgst08-OST0004
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0005.quota_slave.info=
+target name:    umcgst08-OST0005
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0006.quota_slave.info=
+target name:    umcgst08-OST0006
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+
+enable quota:
+
+# lctl conf_param umcgst08.quota.mdt=ug
+# lctl conf_param umcgst08.quota.ost=ugLustre tips/tricks:
+
+check if quota is set on MDT's:
+
+[root@umcg-metadata03 ~]# lctl get_param osd-ldiskfs.*.quota_slave.info
+osd-ldiskfs.umcgst08-MDT0000.quota_slave.info=
+target name:    umcgst08-MDT0000
+pool ID:        0
+type:           md
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+
+check if quota is set on OST's:
+
+[root@umcg-storage03 ~]# lctl get_param osd-ldiskfs.*.quota_slave.info
+osd-ldiskfs.umcgst08-OST0001.quota_slave.info=
+target name:    umcgst08-OST0001
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0002.quota_slave.info=
+target name:    umcgst08-OST0002
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0003.quota_slave.info=
+target name:    umcgst08-OST0003
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0004.quota_slave.info=
+target name:    umcgst08-OST0004
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0005.quota_slave.info=
+target name:    umcgst08-OST0005
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+osd-ldiskfs.umcgst08-OST0006.quota_slave.info=
+target name:    umcgst08-OST0006
+pool ID:        0
+type:           dt
+quota enabled:  none
+conn to master: setup
+space acct:     ug
+user uptodate:  glb[0],slv[0],reint[0]
+group uptodate: glb[0],slv[0],reint[0]
+
+enable quota:
+
+# lctl conf_param umcgst08.quota.mdt=ug
+# lctl conf_param umcgst08.quota.ost=ug

netdata

@@ -0,0 +1,31 @@
+howto run netdata (in a docker) monitoring on a server:
+
+disable ipv6:
+
+# vi /etc/sysctl.conf:
+net.ipv6.conf.all.disable_ipv6 = 1
+net.ipv6.conf.default.disable_ipv6 = 1
+
+rerun sysctl:
+
+# sysctl -p
+
+install docker:
+
+# yum install docker -y
+
+disable iptables/docker
+
+# vi /etc/docker/deamon.json
+{
+"iptables": false
+}
+
+enable/start docker-service:
+
+# systemctl enable docker
+# systemctl start  docker
+
+run netdata:
+
+# docker run --network host --hostname=cms-fa22 -d --cap-add SYS_PTRACE -v /proc:/host/proc:ro  -v /sys:/host/sys:ro -p 19999:19999 titpetric/netdata

openssl-enc

@@ -0,0 +1,9 @@
+
+encrypt file:
+
+$ openssl aes-256-cbc -a -salt -in hoi.test -out hoi.test.enc
+
+decrypt file:
+
+openssl aes-256-cbc -d -a -in hoi.test.enc -out hoi.test.new
+

playbooks/tivoli-client/ansible.cfg

@@ -0,0 +1,5 @@
+[defaults]
+hostfile = hosts
+remote_user = root
+private_key_file = /home/ger/.ssh/id_dsa
+host_key_checking = false

playbooks/tivoli-client/backup-client.yml

@@ -0,0 +1,8 @@
+---
+- hosts: stimmen 
+ 
+  tasks: 
+     - name: uitrol tivoli client 
+       include_role:
+          name: tivo 
+

playbooks/tivoli-client/hosts

@@ -0,0 +1,4 @@
+[backup-clients]
+
+stimmen ansible_host=stimmen.housing.rug.nl ansible_port=22
+cms-fp11 ansible_host=cms-fp11.service.rug.nl ansible_port=22

playbooks/tivoli-client/tivo/README.md

@@ -0,0 +1,38 @@
+Role Name
+=========
+
+A brief description of the role goes here.
+
+Requirements
+------------
+
+Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
+
+Role Variables
+--------------
+
+A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
+
+Dependencies
+------------
+
+A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
+
+Example Playbook
+----------------
+
+Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
+
+    - hosts: servers
+      roles:
+         - { role: username.rolename, x: 42 }
+
+License
+-------
+
+BSD
+
+Author Information
+------------------
+
+An optional section for the role authors to include contact information, or a website (HTML is not allowed).

playbooks/tivoli-client/tivo/defaults/main.yml

@@ -0,0 +1,2 @@
+---
+# defaults file for tivo

playbooks/tivoli-client/tivo/files/README.htm

@@ -0,0 +1,267 @@
+<!DOCTYPE html
+  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us">
+<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+
+<meta name="copyright" content="© Copyright IBM Corporation 2017" />
+<meta name="DC.Rights.Owner" content="© Copyright IBM Corporation 2017" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<meta name="DC.Type" content="reference" />
+<meta name="DC.Title" content="IBM Spectrum Protect Backup-Archive Client Version 8.1.4" />
+<meta name="DC.Date" scheme="iso8601" content="2017-10-03" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="README_81" />
+<meta name="DC.Language" content="en-us" />
+<meta name="IBM.Country" content="ZZ" />
+<!-- Licensed Materials - Property of IBM -->
+<!-- US Government Users Restricted Rights -->
+<!-- Use, duplication or disclosure restricted by -->
+<!-- GSA ADP Schedule Contract with IBM Corp. -->
+
+<title>IBM Spectrum Protect Backup-Archive Client Version 8.1.4</title>
+</head>
+<body id="README_81"><div role="main">
+<h1 class="title topictitle1">IBM Spectrum Protect Backup-Archive
+Client Version 8.1.4</h1>
+<div class="body refbody"><div class="section"><p class="p">Licensed Materials - Property of IBM</p>
+
+<p class="lines">5725-W98<br />
+5725-W99<br />
+5725-X15</p>
+
+<p class="p">Copyright International Business Machines Corp. 2017.</p>
+
+<p class="p">US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
+Schedule Contract with IBM Corp.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Installation instructions</h2>
+<p class="p">For installation instructions, see <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(Opens in a new tab or window)">Installing the IBM Spectrum Protect™ backup-archive clients</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Release notes</h2>
+<p class="p">For access to the product announcement, known issues, system requirements, installation
+instructions, and updates, see <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(Opens in a new tab or window)">Release notes for IBM Spectrum Protect Backup-Archive Client Version 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme files</h2>
+<p class="p">Readme files for the IBM Spectrum Protect
+V8.1 backup-archive client fix packs are available in the Support knowledge base when there is a fix
+pack update.</p>
+
+<p class="p">For the latest updates, system requirements, known limitations, and the fix history for a fix
+pack, see the Support knowledge base:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(Opens in a new tab or window)">View IBM Spectrum Protect
+V8.1 backup-archive client fix pack readme files</a></p>
+
+<p class="p">To view additional information about IBM
+Spectrum Protect, see the <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Opens in a new tab or window)">online product documentation</a>. </p>
+</div>
+</div>
+</div>
+
+<hr> <!-- Chinese-Simplified -->
+<div class="section"><h2 class="title sectiontitle">安装指示信息</h2>
+<p class="p">有关安装指示信息，请参阅<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="（在新的选项卡或窗口中打开）">安装 IBM Spectrum Protect™ 备份/归档客户机</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">发行说明</h2>
+<p class="p">要访问产品声明、已知问题、系统需求、安装指示信息和更新，请参阅 <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="（在新的选项卡或窗口中打开）">IBM Spectrum Protect 备份/归档客户机 V8.1 发行说明</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">自述文件</h2>
+<p class="p">当存在修订包更新时，IBM Spectrum Protect V8.1 备份/归档客户机修订包的自述文件可在“支持”知识库中获取。</p>
+
+<p class="p">有关修订包的最新更新、系统需求、已知限制和修订历史记录，请参阅“支持”知识库：</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="（在新的选项卡或窗口中打开）">View IBM Spectrum Protect
+V8.1 备份/归档客户机修订包自述文件</a></p>
+
+<p class="p">要查看有关 IBM Spectrum Protect 的其他信息，请参阅<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="（在新的选项卡或窗口中打开）">联机产品文档</a>。</p>
+</div>
+
+<hr> <!-- Chinese-Traditional -->
+<div class="section"><h2 class="title sectiontitle">安裝指示</h2>
+<p class="p">如需安裝指示，請參閱<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="（在新分頁或視窗中開啟）">安裝 IBM Spectrum Protect™ 備份保存用戶端</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">版本注意事項</h2>
+<p class="p">若要存取產品公告、已知問題、系統需求、安裝指示及更新項目，請參閱 <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="（在新分頁或視窗中開啟）">IBM Spectrum Protect Backup-Archive Client 8.1 版版本注意事項</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme 檔</h2>
+<p class="p">具有修正套件更新項目時，IBM Spectrum Protect 8.1 版備份保存用戶端修正套件的 Readme 檔位於支援中心知識庫內。</p>
+
+<p class="p">如需修正套件的最新更新項目、系統需求、已知限制及修正歷程，請參閱支援中心知識庫：</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="（在新分頁或視窗中開啟）">檢閱 IBM Spectrum Protect 8.1 版備份保存用戶端修正套件 Readme 檔</a></p>
+
+<p class="p">若要檢視 IBM Spectrum Protect 的其他相關資訊，請參閱<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="（在新分頁或視窗中開啟）">線上產品說明文件</a>。</p>
+</div>
+
+<hr> <!-- French -->
+<div class="section"><h2 class="title sectiontitle">Instructions d'installation</h2>
+<p class="p">Pour obtenir des instructions sur l'installation, voir
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">Installation des clients de sauvegarde-archivage IBM Spectrum Protect</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Notes sur l'édition</h2>
+<p class="p">Pour accéder à l'annonce du produit, consulter les problèmes recensés, la configuration système requise, les instructions d'installation et les mises à jour, voir les <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">Notes sur l'édition du client de sauvegarde-archivage IBM Spectrum Protect version 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Fichiers Readme</h2>
+<p class="p">Les fichiers Readme des groupes de correctifs du client de sauvegarde-archivage IBM Spectrum Protect
+version 8.1 sont disponibles dans la base de connaissances du support
+lorsqu'une mise à jour d'un groupe de correctifs est publiée.</p>
+
+<p class="p">Pour en savoir plus sur les dernières mises à jour, la configuration système requise, les limitations connues et l'historique des correctifs pour un groupe de correctifs, voir la base de connaissances du support :</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">Afficher les fichiers Readme des groupes de correctifs du client de sauvegarde-archivage IBM Spectrum Protect version 8.1</a></p>
+
+<p class="p">Pour consulter des informations supplémentaires sur IBM
+Spectrum Protect, voir la <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">documentation du produit en ligne</a>. </p>
+</div>
+
+<hr><!-- German -->
+<div class="section"><h2 class="title sectiontitle">Installationsanweisungen</h2>
+<p class="p">Installationsanweisungen finden Sie in
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">IBM Spectrum
+Protect-Clients für Sichern/Archivieren installieren</a>. </p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Releaseinformationen</h2>
+<p class="p">Für den Zugriff auf die Produktankündigung sowie auf bekannte Probleme, Systemvoraussetzungen, Installationsanweisungen und Aktualisierungen
+lesen Sie die <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">Releaseinformationen
+für den IBM Spectrum Protect-Client für Sichern/Archivieren Version 8.1</a>. </p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme-Dateien</h2>
+<p class="p">Readme-Dateien für die Fixpacks des IBM Spectrum Protect-Clients für Sichern/Archivieren
+Version 8.1 sind in der Unterstützungswissensbasis verfügbar, wenn eine Fixpackaktualisierung vorhanden ist. </p>
+
+<p class="p">Die neuesten Aktualisierungen, Systemvoraussetzungen und bekannten Einschränkungen sowie das Fixprotokoll für ein Fixpack finden Sie in der
+Unterstützungswissensbasis: </p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">Readme-Dateien für Fixpacks des
+IBM Spectrum Protect-Clients für Sichern/Archivieren Version 8.1 anzeigen</a></p>
+
+<p class="p">Zusätzliche Informationen zu IBM Spectrum Protect finden Sie in der
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">Onlineproduktdokumentation</a>. </p>
+</div>
+
+<hr><!-- Hungarian -->
+<div class="section"><h2 class="title sectiontitle">Telepítési útmutatás</h2>
+<p class="p">A telepítésre vonatkozó útmutatásokat az
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">IBM Spectrum
+Protect mentési-archiválási ügyfelek telepítése</a> című dokumentum tartalmazza.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Kiadási megjegyzések</h2>
+<p class="p">A termékbejelentésekkel, ismert problémákkal, rendszerkövetelményekkel, telepítési
+útmutatásokkal és frissítésekkel kapcsolatos információkat az
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">IBM
+Spectrum Protect mentési-archiválási ügyfél V8.1 kiadási megjegyzések</a>
+tartalmazzák.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme fájlok</h2>
+<p class="p">Az IBM Spectrum Protect
+V8.1 mentési-archiválási ügyfél javítócsomagok readme fájljai a támogatási tudásbázisban érhetők el a frissítések megjelenésekor.</p>
+
+<p class="p">A frissítésekkel, rendszerkövetelményekkel, ismert korlátozásokkal és a javítócsomagok
+előzményeivel kapcsolatos legfrissebb információkat a támogatási tudásbázis tartalmazza:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">IBM Spectrum Protect
+V8.1 mentési-archiválási ügyfél javítócsomag readme fájljainak megtekintése</a></p>
+
+<p class="p">Ha további információkra van szüksége az IBM
+Spectrum Protect termékről, látogassa meg az
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">online
+termékdokumentációt</a>. </p>
+</div>
+
+<hr> <!-- Polish -->
+<div class="section"><h2 class="title sectiontitle">Instrukcje instalowania</h2>
+<p class="p">Szczegółowe instrukcje instalowania zawiera sekcja <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(otwiera się w nowym oknie lub karcie)">Instalowanie
+klientów kopii zapasowych i archiwalnych produktu IBM Spectrum Protect</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Uwagi do wydania</h2>
+<p class="p">Aby uzyskać dostęp do ogłoszeń dostępności produktu, znanych problemów, wymagań systemowych, instrukcji instalowania oraz aktualizowania, zapoznaj się z dokumentem
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(otwiera się w nowym oknie lub karcie)">Klient kopii zapasowych i archiwalnych produktu
+IBM Spectrum Protect, wersja 8.1 - uwagi do wydania</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Pliki readme</h2>
+<p class="p">Pliki readme dla pakietów poprawek klienta kopii zapasowych i archiwalnych produktu IBM Spectrum Protect 8.1 są umieszczane w bazie
+wiedzy działu wsparcia po opublikowaniu pakietu.</p>
+
+<p class="p">Najnowsze aktualizacje, opis wymagań systemowych, znane ograniczenia oraz historia poprawek zostały umieszczone w bazie wiedzy działu wsparcia:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(otwiera się w nowym oknie lub karcie)">Wyświetl pliki readme pakietu poprawek klienta kopii zapasowych i archiwalnych produktu
+IBM Spectrum Protect 8.1</a></p>
+
+<p class="p">Aby wyświetlić dodatkowe informacje na temat produktu IBM Spectrum Protect, przejdź do serwisu z
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(otwiera się w nowym oknie lub karcie)">dokumentacją produktu</a>. </p>
+</div>
+
+<hr> <!-- Portuguese-Brazilian -->
+<div class="section"><h2 class="title sectiontitle">Instruções de instalação</h2>
+<p class="p">Para obter instruções de instalação, consulte <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(Abre em uma nova guia ou janela)">Instalando
+os clientes de backup-archive do IBM Spectrum Protect</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Notas sobre o Release</h2>
+<p class="p">Para acessar o anúncio do produto, os problemas conhecidos, os requisitos do sistema, as instruções de instalação e as atualizações, consulte as
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(Abre em uma nova guia ou janela)">Notas
+sobre a liberação do IBM Spectrum Protect Backup-Archive Client Versão 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Arquivos leia-me</h2>
+<p class="p">Os arquivos leia-me dos fix packs do cliente de backup-archive do IBM Spectrum Protect
+V8.1 estão disponíveis na base de conhecimento de suporte quando há uma atualização de fix pack.</p>
+
+<p class="p">Para ter acesso às atualizações mais recentes, aos requisitos do sistema, às limitações conhecidas e ao histórico de correções para um fix pack, consulte a base de conhecimento de suporte:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(Abre em uma nova guia ou janela)">Visualizar
+os arquivos leia-me do cliente de backup-archive do IBM Spectrum Protect V8.1</a></p>
+
+<p class="p">Para visualizar informações adicionais sobre o IBM
+Spectrum Protect, consulte a <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Abre em uma nova guia ou janela)">documentação do produto on-line</a>. </p>
+</div>
+
+<hr> <!-- Russian -->
+<div class="section"><h2 class="title sectiontitle">Инструкции по установке</h2>
+<p class="p">Инструкции по установке смотрите в документе
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(Будет открыта новая вкладка или окно)">Установка клиента резервного копирования и архивирования
+IBM Spectrum Protect</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Замечания по выпуску</h2>
+<p class="p">Чтобы получить доступ к объявлениям о продукте, информации об известных проблемах, требованиях к системе, инструкциям по установке и обновлениям,
+смотрите документ
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(Будет открыта новая вкладка или окно)">Замечания по выпуску
+для клиента резервного копирования и архивирования IBM Spectrum Protect версии 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Ознакомительные файлы Readme</h2>
+<p class="p">Файлы Readme для пакетов исправлений клиента резервного копирования и архивирования IBM Spectrum Protect V8.1 становятся
+доступны в информационной базе службы поддержки, когда появляется обновление пакета исправлений. </p>
+
+<p class="p">Чтобы узнать о последних обновлениях, требованиях к системе, известных ограничениях и хронологии исправлений для пакета исправлений, смотрите
+информационную базу службы поддержки:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(Будет открыта новая вкладка или окно)">Прочитать файлы Readme для пакета исправлений
+клиента резервного копирования и архивирования IBM Spectrum Protect V8.1</a></p>
+
+<p class="p">Чтобы ознакомиться с дополнительной информацией по IBM Spectrum Protect, смотрите
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Будет открыта новая вкладка или окно)">электронную документацию по
+продукту</a>. </p>
+</div>
+
+<hr> <!-- Spanish -->
+<div class="section"><h2 class="title sectiontitle">Instrucciones de instalación</h2>
+<p class="p">Para obtener instrucciones de instalación, consulte <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/c_inst.html" target="_blank" title="(Abre en una nueva sesión o ventana)">Instalación de clientes de archivado y copia de seguridad de IBM Spectrum
+Protect</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Notas del release</h2>
+<p class="p">Para acceder al anuncio del producto, a los requisitos del sistema, a las instrucciones de instalación y actualizaciones, consulte las <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/client/relnotes_81.html" target="_blank" title="(Abre en una nueva sesión o ventana)">Notas del release para IBM Spectrum Protect Backup-Archive Client Versión 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Archivos léame</h2>
+<p class="p">Los archivos léame para los fixpacks del cliente de archivado y copia de seguridad de IBM Spectrum Protect
+V8.1 se encuentran disponibles en la base de conocimiento de soporte cuando hay una actualización de un fixpack.</p>
+
+<p class="p">Para conocer las actualizaciones, los requisitos de sistema, las limitaciones conocidas y el historial de arreglos para un fixpack, consulte la base de conocimiento de soporte:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048724" target="_blank" title="(Abre en una nueva sesión o ventana)">Vista de los archivos léame del fixpack de cliente de archivado y copia de seguridad de IBM Spectrum Protect
+V8.1</a></p>
+
+<p class="p">Para ver información adicional sobre IBM
+Spectrum Protect, consulte la <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Abre en una nueva sesión o ventana)">documentación de producto en línea</a>. </p>
+</div>
+
+</body>
+</html>

playbooks/tivoli-client/tivo/files/README_api.htm

@@ -0,0 +1,267 @@
+<!DOCTYPE html
+  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us">
+<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+
+<meta name="copyright" content="© Copyright IBM Corporation 2017" />
+<meta name="DC.Rights.Owner" content="© Copyright IBM Corporation 2017" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<meta name="DC.Type" content="reference" />
+<meta name="DC.Title" content="IBM Spectrum Protect Application Programming Interface Version 8.1.4" />
+<meta name="DC.Date" scheme="iso8601" content="2017-10-03" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="README_api_81" />
+<meta name="DC.Language" content="en-us" />
+<meta name="IBM.Country" content="ZZ" />
+<!-- Licensed Materials - Property of IBM -->
+<!-- US Government Users Restricted Rights -->
+<!-- Use, duplication or disclosure restricted by -->
+<!-- GSA ADP Schedule Contract with IBM Corp. -->
+
+<title>IBM Spectrum Protect Application Programming Interface Version 8.1.4</title>
+</head>
+<body id="README_api_81"><div role="main">
+<h1 class="title topictitle1">IBM Spectrum Protect Application
+Programming Interface Version 8.1.4</h1>
+<div class="body refbody"><div class="section"><p class="p">Licensed Materials - Property of IBM</p>
+
+<p class="lines">5725-W98<br />
+5725-W99<br />
+5725-X15</p>
+
+<p class="p">Copyright International Business Machines Corp. 2017.</p>
+
+<p class="p">US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
+Schedule Contract with IBM Corp.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Installation instructions</h2>
+<p class="p">For installation instructions, see <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(Opens in a new tab or window)">Installing the API</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Release notes</h2>
+<p class="p">For access to the product announcement, known issues, system requirements, installation
+instructions, and updates, see <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(Opens in a new tab or window)">Release notes for IBM Spectrum Protect™ Application Programming Interface Version 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme files</h2>
+<p class="p">Readme files for the IBM Spectrum Protect
+V8.1 API fix packs are available in the Support knowledge base when there is a fix pack update.</p>
+
+<p class="p">For the latest updates, system requirements, known limitations, and the fix history for a fix
+pack, see the Support knowledge base:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(Opens in a new tab or window)">View IBM Spectrum Protect
+V8.1 API fix pack readme files</a></p>
+
+<p class="p">To view additional information about IBM
+Spectrum Protect, see the <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Opens in a new tab or window)">online product documentation</a>. </p>
+</div>
+</div>
+</div>
+
+<hr> <!-- Chinese-Simplified -->
+<div class="section"><h2 class="title sectiontitle">安装指示信息</h2>
+<p class="p">有关安装指示信息，请参阅<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="（在新的选项卡或窗口中打开）">安装 API</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">发行说明</h2>
+<p class="p">有关产品声明、已知问题、系统需求、安装指示信息和更新的访问权，请参阅 <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="（在新的选项卡或窗口中打开）">IBM Spectrum Protect™ 应用程序编程接口 V8.1 的发行说明</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">自述文件</h2>
+<p class="p">当存在修订包更新时，“支持”知识库中提供了 IBM Spectrum Protect V8.1 API 修订包的自述文件。</p>
+
+<p class="p">有关修订包的最新更新、系统需求、已知限制和修订历史记录，请参阅“支持”知识库：</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="（在新的选项卡或窗口中打开）">查看 IBM Spectrum Protect V8.1 API 修订包自述文件</a></p>
+
+<p class="p">要查看有关 IBM
+Spectrum Protect 的其他信息，请参阅<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="（在新的选项卡或窗口中打开）">在线产品文档</a>。</p>
+</div>
+
+<hr> <!-- Chinese-Traditional -->
+<div class="section"><h2 class="title sectiontitle">安裝指示</h2>
+<p class="p">如需安裝指示，請參閱<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="（在新分頁或視窗中開啟）">安裝 API</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">版本注意事項</h2>
+<p class="p">如需存取產品公告、已知問題、系統需求、安裝指示以及更新項目，請參閱 <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="（在新分頁或視窗中開啟）">IBM Spectrum Protect™ 應用程式設計介面 8.1 版的版本注意事項</a>。</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme 檔</h2>
+<p class="p">當有修正套件更新時，會在支援中心知識庫中提供 IBM Spectrum Protect
+8.1 版 API 修正套件的 Readme 檔。</p>
+
+<p class="p">如需修正套件的最新更新項目、系統需求、已知限制以及修正歷程，請參閱支援中心知識庫：</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="（在新分頁或視窗中開啟）">檢視 IBM Spectrum Protect
+8.1 版 API 修正套件 Readme 檔</a></p>
+
+<p class="p">若要檢視 IBM
+Spectrum Protect 的其他相關資訊，請參閱<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="（在新分頁或視窗中開啟）">線上產品說明文件</a>。</p>
+</div>
+
+<hr> <!-- French -->
+<div class="section"><h2 class="title sectiontitle">Instructions d'installation</h2>
+<p class="p">Pour obtenir des instructions sur l'installation, voir
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">Installation de l'API</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Notes sur l'édition</h2>
+<p class="p">Pour accéder à l'annonce du produit, consulter les problèmes recensés, la configuration système requise, les instructions d'installation et les mises à jour, voir les <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">Notes sur l'édition de l'API IBM Spectrum Protect version 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Fichiers Readme</h2>
+<p class="p">Les fichiers Readme des groupes de correctifs de l'API IBM Spectrum Protect
+version 8.1 sont disponibles dans la base de connaissances du support
+lorsqu'une mise à jour d'un groupe de correctifs est publiée.</p>
+
+<p class="p">Pour en savoir plus sur les dernières mises à jour, la configuration système requise, les limitations connues et l'historique des correctifs pour un groupe de correctifs, voir la base de connaissances du support :  </p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">Afficher les fichiers Readme des groupes de correctifs de l'API IBM Spectrum Protect version 8.1</a></p>
+
+<p class="p">Pour consulter des informations supplémentaires sur IBM
+Spectrum Protect, voir la <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(S'ouvre dans un nouvel onglet ou une nouvelle fenêtre)">documentation du produit en ligne</a>. </p>
+</div>
+
+<hr> <!-- German -->
+<div class="section"><h2 class="title sectiontitle">Installationsanweisungen</h2>
+<p class="p">Installationsanweisungen finden Sie in
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">API installieren</a>. </p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Releaseinformationen</h2>
+<p class="p">Für den Zugriff auf die Produktankündigung sowie auf bekannte Probleme, Systemvoraussetzungen, Installationsanweisungen und Aktualisierungen
+lesen Sie die <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">Releaseinformationen
+für die IBM Spectrum Protect-Anwendungsprogrammierschnittstelle Version 8.1</a>. </p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme-Dateien</h2>
+<p class="p">Readme-Dateien für die Fixpacks der IBM Spectrum Protect-Anwendungsprogrammierschnittstelle
+Version 8.1 sind in der Unterstützungswissensbasis verfügbar, wenn eine Fixpackaktualisierung vorhanden ist. </p>
+
+<p class="p">Die neuesten Aktualisierungen, Systemvoraussetzungen und bekannten Einschränkungen sowie das Fixprotokoll für ein Fixpack finden Sie in der
+Unterstützungswissensbasis: </p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">Readme-Dateien für Fixpacks der
+IBM Spectrum Protect-Anwendungsprogrammierschnittstelle Version 8.1 anzeigen</a></p>
+
+<p class="p">Zusätzliche Informationen zu IBM Spectrum Protect finden Sie in der
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(In neuer Registerkarte/neuem Fenster öffnen)">Onlineproduktdokumentation</a>. </p>
+</div>
+
+<hr> <!-- Hungarian -->
+<div class="section"><h2 class="title sectiontitle">Telepítési útmutatás</h2>
+<p class="p">A telepítésre vonatkozó útmutatásokat az
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">API
+telepítése</a> című dokumentum tartalmazza.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Kiadási megjegyzések</h2>
+<p class="p">A termékbejelentésekkel, ismert problémákkal, rendszerkövetelményekkel, telepítési
+útmutatásokkal és frissítésekkel kapcsolatos információkat az
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">IBM
+Spectrum Protect API V8.1 kiadási megjegyzések</a>
+tartalmazzák.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Readme fájlok</h2>
+<p class="p">Az IBM Spectrum Protect
+V8.1 API javítócsomagok readme fájljai a támogatási tudásbázisban érhetők el a frissítések megjelenésekor.</p>
+
+<p class="p">A frissítésekkel, rendszerkövetelményekkel, ismert korlátozásokkal és a javítócsomagok
+előzményeivel kapcsolatos legfrissebb információkat a támogatási tudásbázis tartalmazza: </p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">IBM Spectrum Protect
+V8.1 API javítócsomag readme fájljainak megtekintése</a></p>
+
+<p class="p">Ha további információkra van szüksége az IBM
+Spectrum Protect termékről, látogassa meg az
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Új lapon vagy ablakban nyílik meg)">online
+termékdokumentációt</a>. </p>
+</div>
+
+<hr> <!-- Polish -->
+<div class="section"><h2 class="title sectiontitle">Instrukcje instalowania</h2>
+<p class="p">Szczegółowe instrukcje instalowania zawiera sekcja
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(otwiera się w nowym oknie lub karcie)">Instalowanie interfejsu API</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Uwagi do wydania</h2>
+<p class="p">Aby uzyskać dostęp do ogłoszeń dostępności produktu, znanych problemów, wymagań systemowych, instrukcji instalowania oraz aktualizowania, zapoznaj się z dokumentem
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(otwiera się w nowym oknie lub karcie)">Interfejs API produktu
+IBM Spectrum Protect, wersja 8.1 - uwagi do wydania</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Pliki readme</h2>
+<p class="p">Pliki readme dla pakietów poprawek interfejsu API produktu IBM Spectrum Protect 8.1 są umieszczane w bazie wiedzy działu wsparcia po
+opublikowaniu pakietu. </p>
+
+<p class="p">Najnowsze aktualizacje, opis wymagań systemowych, znane ograniczenia oraz historia poprawek zostały umieszczone w bazie wiedzy działu wsparcia:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(otwiera się w nowym oknie lub karcie)">Wyświetl pliki readme pakietu poprawek interfejsu API produktu
+IBM Spectrum Protect 8.1</a></p>
+
+<p class="p">Aby wyświetlić dodatkowe informacje na temat produktu IBM Spectrum Protect, przejdź do serwisu z
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(otwiera się w nowym oknie lub karcie)">dokumentacją produktu</a>. </p>
+</div>
+
+<hr> <!-- Portuguese-Brazilian -->
+<div class="section"><h2 class="title sectiontitle">Instruções de instalação</h2>
+<p class="p">Para obter instruções de instalação, consulte <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(Abre em uma nova guia ou janela)">Instalando a API</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Notas sobre o Release</h2>
+<p class="p">Para acessar o anúncio do produto, os problemas conhecidos, os requisitos do sistema, as instruções de instalação e as atualizações, consulte as
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(Abre em uma nova guia ou janela)">Notas sobre a liberação do
+IBM Spectrum Protect Application Programming Interface Versão 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Arquivos leia-me</h2>
+<p class="p">Os arquivos leia-me dos fix packs da API do IBM Spectrum Protect
+V8.1 estão disponíveis na base de conhecimento de suporte quando há uma atualização de fix pack.</p>
+
+<p class="p">Para ter acesso às atualizações mais recentes, aos requisitos do sistema, às limitações conhecidas e ao histórico de correções para um fix pack, consulte a base de conhecimento de suporte:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(Abre em uma nova guia ou janela)">Visualizar os arquivos leia-me da API do
+IBM Spectrum Protect V8.1</a></p>
+
+<p class="p">Para visualizar informações adicionais sobre o IBM
+Spectrum Protect, consulte a <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Abre em uma nova guia ou janela)">documentação
+do produto on-line</a>. </p>
+</div>
+
+<hr> <!-- Russian -->
+<div class="section"><h2 class="title sectiontitle">Инструкции по установке</h2>
+<p class="p">Инструкции по установке смотрите в документе
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(Будет открыта новая вкладка или окно)">Установка API</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Замечания по выпуску</h2>
+<p class="p">Чтобы получить доступ к объявлениям о продукте, информации об известных проблемах, требованиях к системе, инструкциям по установке и
+обновлениям, смотрите документ
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(Будет открыта новая вкладка или окно)">Замечания по
+выпуску для интерфейса прикладного программирования (API) IBM Spectrum Protect версии
+8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Ознакомительные файлы Readme</h2>
+<p class="p">Файлы Readme для пакетов исправлений API IBM Spectrum Protect
+V8.1 становятся доступны в информационной базе службы поддержки, когда появляется обновление пакета исправлений. </p>
+
+<p class="p">Чтобы узнать о последних обновлениях, требованиях к системе, известных ограничениях и хронологии исправлений для пакета исправлений, смотрите
+информационную базу службы поддержки:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(Будет открыта новая вкладка или окно)">Прочитать файлы Readme для пакета исправлений
+API IBM Spectrum Protect V8.1</a></p>
+
+<p class="p">Чтобы ознакомиться с дополнительной информацией по IBM Spectrum Protect, смотрите
+<a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Будет открыта новая вкладка или окно)">электронную документацию
+по продукту</a>. </p>
+</div>
+
+<hr> <!-- Spanish -->
+<div class="section"><h2 class="title sectiontitle">Instrucciones de instalación</h2>
+<p class="p">Para obtener las instrucciones de instalación, consulte <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/t_install_api.html" target="_blank" title="(Abre en una nueva sesión o ventana)">Instalación de la API</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Notas del release</h2>
+<p class="p">Para acceder al anuncio del producto, a los problemas conocidos, a los requisitos del sistema, a las instrucciones de instalación y actualizaciones, consulte las <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/api/relnotes_api_81.html" target="_blank" title="(Abre en una nueva sesión o ventana)">Notas del release de IBM Spectrum Protect Application Programming Interface Versión 8.1</a>.</p>
+</div>
+<div class="section"><h2 class="title sectiontitle">Archivos léame</h2>
+<p class="p">Los archivos léame de los fixpacks de la API de IBM Spectrum Protect
+V8.1 se encuentran disponibles en la base de conocimiento cuando haya una actualización de un fixpack.</p>
+
+<p class="p">Para conocer las actualizaciones, los requisitos de sistema, las limitaciones conocidas y el historial de fixpack más recientes, consulte la base de conocimiento de soporte:</p>
+
+<p class="p"><a class="xref" href="http://www.ibm.com/support/docview.wss?uid=swg27048831" target="_blank" title="(Abre en una nueva sesión o ventana)">Vista de los archivos de léame del fixpack de la API de IBM Spectrum Protect
+V8.1</a></p>
+
+<p class="p">Para obtener información adicional sobre IBM
+Spectrum Protect, consulte <a class="xref" href="https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.4/tsm/welcome.html" target="_blank" title="(Abre en una nueva sesión o ventana)">la documentación de producto en línea</a>. </p>
+</div>
+
+</body>
+</html>

playbooks/tivoli-client/tivo/files/dsm.opt

@@ -0,0 +1,2 @@
+SErvername  RCBACKUP01
+Quiet

playbooks/tivoli-client/tivo/files/dsm.sys

@@ -0,0 +1,31 @@
+*** The following replication server connection information is automatically updated
+*** These options should not be changed manually
+REPLSERVERNAME          RCBACKUP02
+   REPLTCPSERVERADDRESS rcbackup02.service.rug.nl
+   REPLTCPPORT          1500
+   REPLSERVERGUID       1e.d6.aa.86.46.2c.e8.11.ac.9a.50.9a.4c.ab.2d.e4
+   REPLSSLPORT          1505
+
+*** end of automatically updated options
+SErvername  RCBACKUP01
+   *** The MYREPLICATIONServer and MYPRIMARYServername options are automatically updated and should not be changed manually
+   MYREPLICATIONServer RCBACKUP02
+   MYPRIMARYServername RCBACKUP01
+COMMmethod         TCPip
+TCPPort            1500
+HTTPPORT           1581
+TCPServeraddress   rcbackup01.service.rug.nl
+SCHEDMODE          PROMPTED
+TCPBUFFSIZE        512
+TCPWINDOWSIZE      2048
+COMPRESSION        NO
+nodename           peregrine 
+passwordaccess     generate
+users              root backup
+inclexcl           /opt/tivoli/tsm/client/ba/bin/dsm.exclude
+errorlogname       /var/log/adsm/dsmerror.log
+schedlogname       /var/log/adsm/dsmsched.log
+resourceutilization 10
+errorlogretention  14
+schedlogretention  14 
+VIRTUALMOUNTPOINT /home

playbooks/tivoli-client/tivo/handlers/main.yml

@@ -0,0 +1,2 @@
+---
+# handlers file for tivo

playbooks/tivoli-client/tivo/meta/main.yml

@@ -0,0 +1,57 @@
+galaxy_info:
+  author: your name
+  description: your description
+  company: your company (optional)
+
+  # If the issue tracker for your role is not on github, uncomment the
+  # next line and provide a value
+  # issue_tracker_url: http://example.com/issue/tracker
+
+  # Some suggested licenses:
+  # - BSD (default)
+  # - MIT
+  # - GPLv2
+  # - GPLv3
+  # - Apache
+  # - CC-BY
+  license: license (GPLv2, CC-BY, etc)
+
+  min_ansible_version: 1.2
+
+  # If this a Container Enabled role, provide the minimum Ansible Container version.
+  # min_ansible_container_version:
+
+  # Optionally specify the branch Galaxy will use when accessing the GitHub
+  # repo for this role. During role install, if no tags are available,
+  # Galaxy will use this branch. During import Galaxy will access files on
+  # this branch. If Travis integration is configured, only notifications for this
+  # branch will be accepted. Otherwise, in all cases, the repo's default branch
+  # (usually master) will be used.
+  #github_branch:
+
+  #
+  # platforms is a list of platforms, and each platform has a name and a list of versions.
+  #
+  # platforms:
+  # - name: Fedora
+  #   versions:
+  #   - all
+  #   - 25
+  # - name: SomePlatform
+  #   versions:
+  #   - all
+  #   - 1.0
+  #   - 7
+  #   - 99.99
+
+  galaxy_tags: []
+    # List tags for your role here, one per line. A tag is a keyword that describes
+    # and categorizes the role. Users find roles by searching for tags. Be sure to
+    # remove the '[]' above, if you add tags to this list.
+    #
+    # NOTE: A tag is limited to a single word comprised of alphanumeric characters.
+    #       Maximum 20 tags per role.
+
+dependencies: []
+  # List your role dependencies here, one per line. Be sure to remove the '[]' above,
+  # if you add dependencies to this list.

playbooks/tivoli-client/tivo/tasks/change-node-name.yml

@@ -0,0 +1,5 @@
+- replace:
+         path: /opt/tivoli/tsm/client/ba/bin/dsm.sys
+         regexp: 'nodename'
+         replace: 'nodename="{{ ansible_hostname }}'
+         backup: yes

playbooks/tivoli-client/tivo/tasks/copy-config.yml

@@ -0,0 +1,13 @@
+- copy:
+    src: files/dsm.sys 
+    dest: /opt/tivoli/tsm/client/ba/bin/dsm.sys_new 
+    owner: root
+    mode: 0600
+    force: no
+
+- copy:
+    src: files/dsm.opt
+    dest: /opt/tivoli/tsm/client/ba/bin/dsm.opt_new 
+    owner: root
+    mode: 0600
+    force: no    

playbooks/tivoli-client/tivo/tasks/copy-files.yml

@@ -0,0 +1,11 @@
+- file: path=/root/tivo state=directory
+
+- copy:
+    src: "{{ item }}" 
+    dest: /root/tivo/
+    owner: root
+    mode: 0600
+    force: no
+  with_fileglob:
+    - files/*
+    

playbooks/tivoli-client/tivo/tasks/install-rpms.yml

@@ -0,0 +1,13 @@
+ - name: Find all rpm files in /tmp folder
+   find:
+     paths: "/root/tivo"
+     pattern: "*.rpm"
+   register: rpm_files
+
+ - set_fact:
+    rpm_list: "{{ rpm_files.files | map(attribute='path') | list}}"
+
+ - name: installing the rpm files
+   yum:
+     name: "{{rpm_list}}"
+     state: present

playbooks/tivoli-client/tivo/tasks/main.yml

@@ -0,0 +1,6 @@
+---
+# tasks file for tivo
+   - include: copy-files.yml
+   - include: install-rpms.yml
+   - include: copy-config.yml
+   - include: change-node-name.yml

playbooks/tivoli-client/tivo/tests/inventory

@@ -0,0 +1,2 @@
+localhost
+

playbooks/tivoli-client/tivo/tests/test.yml

@@ -0,0 +1,5 @@
+---
+- hosts: localhost
+  remote_user: root
+  roles:
+    - tivo

playbooks/tivoli-client/tivo/vars/main.yml

@@ -0,0 +1,2 @@
+---
+# vars file for tivo

portainer

@@ -0,0 +1,9 @@
+Portainer is a nice gui/browser tool to manage your docker images/containers
+
+create /opt/portainer/ direcory:
+
+# mkdir /opt/portainer/
+
+run portainer as a docker:
+
+# docker run -d -p 9000:9000 --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /opt/portainer:/data portainer/portainer

portscan.ssl

@@ -0,0 +1,4 @@
+
+check ciphers on ssl-website:
+
+nmap -p 443 -v --script ssl-enum-ciphers webdav-test.data.rug.nl

slurm.tips

@@ -0,0 +1,5 @@
+slurm tips/tricks:
+
+howto see all jobs that are on /scratch:
+
+$ squeue -O jobid,workdir | grep scratch | awk '{print $1}'

vagrant.centos7.ansible

@@ -0,0 +1,116 @@
+Vagrant centos7 vm met Ansible als provisioner:
+
+ger@ger-xiaomi:~$ cd centos_vagrant/
+
+ger@ger-xiaomi:~/centos_vagrant$ wget https://github.com/tommy-muehle/puppet-vagrant-boxes/releases/download/1.1.0/centos-7.0-x86_64.box
+Saving to: ‘centos-7.0-x86_64.box’
+
+centos-7.0-x86_64.box                        100%[============================================================================================>] 475,10M  2,87MB/s    in 2m 17s 
+
+
+ger@ger-xiaomi:~/centos_vagrant$ vagrant box add centos-7.0-x86_64.box --name centos7
+==> box: Box file was not detected as metadata. Adding it directly...
+==> box: Adding box 'centos7' (v0) for provider: 
+    box: Unpacking necessary files from: file:///home/ger/centos_vagrant/centos-7.0-x86_64.box
+==> box: Successfully added box 'centos7' (v0) for 'virtualbox'!
+
+  config.vm.box = "centos7"
+
+ger@ger-xiaomi:~/centos_vagrant$ vi Vagrantfile 
+
+  config.vm.box = "centos7"
+
+ger@ger-xiaomi:~/centos_vagrant$ vagrant up
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'centos7'...
+==> default: Matching MAC address for NAT networking...
+==> default: Setting the name of the VM: centos_vagrant_default_1523562614992_68521
+==> default: Clearing any previously set forwarded ports...
+==> default: Clearing any previously set network interfaces...
+==> default: Preparing network interfaces based on configuration...
+    default: Adapter 1: nat
+==> default: Forwarding ports...
+    default: 22 (guest) => 2222 (host) (adapter 1)
+==> default: Booting VM...
+==> default: Waiting for machine to boot. This may take a few minutes...
+    default: SSH address: 127.0.0.1:2222
+    default: SSH username: vagrant
+    default: SSH auth method: private key
+    default: 
+    default: Vagrant insecure key detected. Vagrant will automatically replace
+    default: this with a newly generated keypair for better security.
+    default: 
+    default: Inserting generated public key within guest...
+    default: Removing insecure key from the guest if it's present...
+    default: Key inserted! Disconnecting and reconnecting using new SSH key...
+==> default: Machine booted and ready!
+==> default: Checking for guest additions in VM...
+    default: The guest additions on this VM do not match the installed version of
+    default: VirtualBox! In most cases this is fine, but in rare cases it can
+    default: prevent things such as shared folders from working properly. If you see
+    default: shared folder errors, please make sure the guest additions within the
+    default: virtual machine match the version of VirtualBox you have installed on
+    default: your host and reload your VM.
+    default: 
+    default: Guest Additions Version: 4.3.28
+    default: VirtualBox Version: 5.1
+==> default: Mounting shared folders...
+    default: /vagrant => /home/ger/centos_vagrant
+
+ger@ger-xiaomi:~/centos_vagrant$ vi Vagrantfile 
+
+  config.vm.provision "ansible" do | ansible|
+    ansible.playbook = "playbook.yml"
+    ansible.sudo = true
+   end
+
+
+ger@ger-xiaomi:~/centos_vagrant$ vi playbook.yml
+
+---
+- hosts: all
+  tasks:
+  - yum: pkg=httpd state=installed
+
+ger@ger-xiaomi:~/centos_vagrant$ vagrant provision 
+==> default: Running provisioner: ansible...
+    default: Running ansible-playbook...
+ ____________
+< PLAY [all] >
+ ------------
+        \   ^__^
+         \  (oo)\_______
+            (__)\       )\/\
+                ||----w |
+                ||     ||
+
+ ________________________
+< TASK [Gathering Facts] >
+ ------------------------
+        \   ^__^
+         \  (oo)\_______
+            (__)\       )\/\
+                ||----w |
+                ||     ||
+
+ok: [default]
+ ____________
+< TASK [yum] >
+ ------------
+        \   ^__^
+         \  (oo)\_______
+            (__)\       )\/\
+                ||----w |
+                ||     ||
+
+changed: [default]
+ ____________
+< PLAY RECAP >
+ ------------
+        \   ^__^
+         \  (oo)\_______
+            (__)\       )\/\
+                ||----w |
+                ||     ||
+
+default                    : ok=2    changed=1    unreachable=0    failed=0