30.11.2020: Updated with the new patchseries and instructions for Windows
02.12.2020: Added tweaks
08.12.2020: Updated with patchseries v4
31.01.2020: Updated with patchseries v6
| #!/bin/bash | |
| gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont' |
| #!/usr/bin/env python | |
| import os | |
| import sys | |
| import argparse | |
| import logging | |
| from datetime import datetime, timedelta | |
| from typing import List, Optional | |
| from collections import defaultdict |
| --- | |
| apiVersion: v1 | |
| kind: PersistentVolume | |
| metadata: | |
| # Can be anything, but has to be matched at line 47 | |
| # Also should avoid conflicts with existing PV names in the namespace | |
| name: preprov-pv-cephfs-01 | |
| spec: | |
| accessModes: | |
| - ReadWriteMany |
I suggest that you create one or more Api.fs files to expose F# code in a C# friendly way.
In this file:
PascalCase names. They will appear to C# as static methods.| if sysbench.cmdline.command == nil then | |
| error("Command is required. Supported commands: run") | |
| end | |
| sysbench.cmdline.options = { | |
| point_selects = {"Number of point SELECT queries to run", 5}, | |
| skip_trx = {"Do not use BEGIN/COMMIT; Use global auto_commit value", false} | |
| } | |
| local page_types = { "actor", "character", "movie" } |
| #!/bin/bash | |
| RESULT_FILE=/tmp/result_$$ | |
| rm -rf $HOME/tmp-fio | |
| mkdir -p $HOME/tmp-fio && cd $HOME/tmp-fio | |
| echo "Starting storage tests" | |
| echo "Results will be saved in $RESULT_FILE" |
| import pandas as pd | |
| #https://github.com/RomelTorres/alpha_vantage | |
| from alpha_vantage.timeseries import TimeSeries | |
| ALPHA_VANTAGE_KEY = 'XXXXXXXXXXXX' | |
| ################################## | |
| # Alpha vantage version of data.history and data.current | |
| def av_data_history(assets, fields, bar_count, frequency): | |
| ts = TimeSeries(key=ALPHA_VANTAGE_KEY, output_format='pandas') |
| File | Purpose |
|---|---|
/etc/compose/docker-compose.yml |
Compose file describing what to deploy |
/etc/systemd/system/docker-compose-reload.service |
Executing unit to trigger reload on docker-compose.service |
/etc/systemd/system/docker-compose-reload.timer |
Timer unit to plan the reloads |
/etc/systemd/system/docker-compose.service |
Service unit to start and manage docker compose |
| # How to monitor a secure external etcd service with Prometheus Operator | |
| This guide will help you monitor an external etcd cluster. When the etcd is not hosted inside Kubernetes. | |
| This is often the case with the Kubernetes setup. This has been tested with kube-aws but same principals will apply to other tools. | |
| # Step 1 - Make the etcd certificates available to Prometheus pod | |
| Prometheus Operator (and Prometheus) allow us to specify a tlsConfig. This is required as most likely your etcd metrics end points is secure. | |
| ## a - Create the secrets in the namespace | |
| Prometheus Operator allows us to mount secrets in the pod. By loading the secrets as files, they can be made available inside the Prometheus pod. |