InfluxData's T.I.C.K. stack is made up from the following components:
| Component | Role |
|---|---|
| Telegraf | Data collector |
| InfluxDB | Stores data |
| Chronograf | Visualizer |
| ''' | |
| Basic tail command implementation | |
| Usage: | |
| tail.py filename numlines | |
| ''' | |
| import sys | |
| import linecache |
I wanted to be really able to explain to a fair amount of detail how does the program :command:`ls` actually work right from the moment you type the command name and hit ENTER. What goes on in user space and and in kernel space? This is my attempt and what I have learned so far on Linux (Fedora 19, 3.x kernel).
How does the shell find the location of 'ls' ?
Make sure you've pulled the new upstream branch into your local repo:
git fetch upstream
to retrieve the new upstream branch 2. Create and switch to a local version of the new upstream branch (newbranch):
docker image prune -f
docker rmi $(docker images -q)
docker rm -v $(docker ps -qa)
cd Repos/atom/jdeployerSaaS
./jdeployer_image_builder.sh
docker tag jdeployer:220422 svl-artifactory.juniper.net/atom-docker/atom-of/mukil/jdeployer:R1.2
| # Reset | |
| Color_Off='\033[0m' # Text Reset | |
| # Regular Colors | |
| Black='\033[0;30m' # Black | |
| Red='\033[0;31m' # Red | |
| Green='\033[0;32m' # Green | |
| Yellow='\033[0;33m' # Yellow | |
| Blue='\033[0;34m' # Blue | |
| Purple='\033[0;35m' # Purple |
| #!/usr/bin/env bash | |
| function delete_namespace () { | |
| echo "Deleting namespace $1" | |
| kubectl get namespace $1 -o json > tmp.json | |
| sed -i 's/"kubernetes"//g' tmp.json | |
| kubectl replace --raw "/api/v1/namespaces/$1/finalize" -f ./tmp.json | |
| rm ./tmp.json | |
| } |