Docs:
I assume that you have a running debian wheezy host with libvirt and qemu/kvm
installed. You need two guest VMs for this. The first guest will get the IP
192.168.100.2 and the second will get 192.168.100.100. All following commands
must be run with sudo or under root.
We create a new network named internal with libvirt and use it with the IP
So how would you use your text editor to make a day notes?
For vim I end up using simple approach:
-
have a
~/docs/journal/directory where I keep yearly journals in asciidoc format (one can use markdown of course). -
have a mapping to quickly open a journal ready to enter you thoughts, notes or a todos for a day.
The IBM Kubernetes service free clusters consist of a single worker node with 2 CPU and 4 GB of memory for experimenting with Kubernetes. Unlike the fee-based service, these clusters do not include capabilities for application load balancing using ingress out-of-the-box. However, if you manage a DNS domain (any provider will suffice) and can add an A record, it's possible for you to configure your own ingress that can provide http and https session termination for your containerized applications. Getting a TLS-enabled website or simply an external REST API couldn't be easier!
- Free IBM Kubernetes Cluster (IKS) - upgrade your account from Lite plan to create one. In the example commands, we'll assume that this cluster is named
mycluster - kubectl - match your cluster API version (as of 5/17/20 - this is ~1.16.9)
- helm v3
- DNS domain that you can edit to configure
| # Print status for all fail2ban jails. | |
| function f2bstall() { | |
| JAILS=($(fail2ban-client status | grep "Jail list" | sed -E 's/^[^:]+:[ \t]+//' | sed 's/,//g')) | |
| for JAIL in ${JAILS[@]} | |
| do | |
| echo "--------------- π JAIL STATUS: $JAIL ... ---------------" | |
| fail2ban-client status $JAIL | |
| echo "--------------- ... ---------------" | |
| done | |
| } |
People
:bowtie: |
π :smile: |
π :laughing: |
|---|---|---|
π :blush: |
π :smiley: |
:relaxed: |
π :smirk: |
π :heart_eyes: |
π :kissing_heart: |
π :kissing_closed_eyes: |
π³ :flushed: |
π :relieved: |
π :satisfied: |
π :grin: |
π :wink: |
π :stuck_out_tongue_winking_eye: |
π :stuck_out_tongue_closed_eyes: |
π :grinning: |
π :kissing: |
π :kissing_smiling_eyes: |
π :stuck_out_tongue: |
| # Please see the following blog post for more information: | |
| # | |
| # https://www.hashicorp.com/blog/using-hashicorp-vault-with-chef.html | |
| # | |
| resource_name :vault_secret | |
| property :path, String, name_property: true | |
| property :destination, String |
YARD CHEATSHEET http://yardoc.org
cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
| # On the remote node/server: | |
| winrm quickconfig -q | |
| winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="300"}' | |
| winrm set winrm/config '@{MaxTimeoutms="1800000"}' | |
| # When NOT USING a domain-based authentication (i.e., from Linux/Unix to Windows node): | |
| winrm set winrm/config/service/auth '@{Basic="true"}' |
Chef and VMware are a natural pairing and there are several tools available to enhance the integration.
Knife is a command-line tool that provides an interface between a local chef-repo and the Chef server and allows you to manipulate objects on the Chef server. Knife plugin allows your computer to talk to a 3rd party systems like vSphere or vRA. A plugin can create a VM in vSphere and then bootstrap it with Chef, for example, or it can expose your vRa catalog to your workstation so you don't need to use a GUI.
The following are the main interfaces with VMware and Chef our "knife" plugins.