| #using https://github.com/cli/cli and jq. | |
| gh repo list -L 80 --json name,description,isArchived,createdAt,updatedAt,url --jq '.[] | [.name, .description, .createdAt, .isArchived, .url]' RADAR-base > radar-base-repos.csv |
| #DESC: Providing a overview of all the Instances running across the individual regions, something not readily available in AWS web UI :-/ | |
| # Install AWS CLI https://aws.amazon.com/cli/ | |
| #-------------------------------------------------------------------------------------- | |
| # List all aws instances in all regions, parse out response JSON | |
| # Props to: https://github.com/aws/aws-cli/issues/1777 | |
| #-------------------------------------------------------------------------------------- | |
| function aws-ls-ec2-vm | |
| { |
#Container Resource Allocation Options in docker-run
now see: https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources
You have various options for controlling resources (cpu, memory, disk) in docker. These are principally via the docker-run command options.
##Dynamic CPU Allocation
-c, --cpu-shares=0
CPU shares (relative weight, specify some numeric value which is used to allocate relative cpu share)
#Docker on GCE see:
##Instantiate a docker VM
#Some discussions on logging from docker: Using logstash Using Papertrail
A lot of this boils down to whether you want a single or multi-process (systemd, supervisord etc.) container...