##Dockerfile | |
FROM centos:7 | |
RUN yum update -y && yum install -y wget perl openssl-devel dmidecode | |
RUN wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash | |
RUN yum install -y srvadmin-idracadm7 | |
RUN cp /opt/dell/srvadmin/bin/idracadm7 /usr/local/bin/racadm | |
##Build via... (run inside somedir/Dockerfile) |
- Combine the pull secrents from Quay and the one from the local registry
jq -s '.[0] * .[1]' pull-secret.json local-auth.json > pull-secret-2.json
- Mirror relrease
export AIRGAP_SECRET_JSON='pull-secret-2.json'
#!/bin/sh | |
# profile patches are cumulative: http://blogs.vmware.com/vsphere/2013/10/are-esxi-patches-cumulative.html | |
# favour update over install: http://www.v-front.de/2013/05/quickest-way-to-update-your-standalone.html | |
esxcli network firewall ruleset list | grep httpClient | |
# Enable http: | |
esxcli network firewall ruleset set -e true -r httpClient | |
# List updates: | |
esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | |
# Only relevant updates: | |
esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | sort | grep -w standard | grep "ESXi-5.1.0-20" |
Synology NAS - How to make a program run at startup | |
The other day I created a little node.js project to keep track of some finances. Synology has a node.js package but that just installs the tools - it has no 'container' or any other support to drop files and have it run automagically. Maybe one day. | |
In the meantime, you can start your project when you SSH into the NAS. My project has a 'www' script which bootstraps my project, so to start I simply type 'node bin/www' from the project directory. But, it only runs while I'm logged in, and if I log out for any reason, the process dies. That's hardly useful when I'm away from home, or on a different PC. So I decided to have a look at starting my project as a Linux service. | |
After doing a lot of research into how Synology does services, and a few failed attempts at init scripts, I found that Synology DSM (since version 5 perhaps) bundles Upstart, which is a neat little tool to deal with services on Linux. It's most prevalent on Debian and derivatives (notably Ub |
[CoreDNS][coredns] was designed from the ground up to provide robust, plugin-based DNS server for use in cloud environments. Namely, it serves as the default primary service discovery mechanism for Kubernetes.
Using CoreDNS allows us to have a lightweight DNS server on RockNSM (11 Mb binary is all that's needed!) to facilitate multi-node service discovery. Alternatively, if another existing DNS service is available, this can be used instead. Aligning with the way the Kubernetes manages service discovery also allows us to build new RockNSM features in parallel with the coming Kubernetes support.
Based on info from http://peterdowns.com/posts/open-iterm-finder-service.html but with modified behavior and fixed to work with iTerm2 version 3 or later. It will not work with older versions of iTerm. The modified behavior is to open a new terminal window for each invocation instead of reusing an already open window. Update - The original author released a build script for the newer iTerm2 versions at https://github.com/peterldowns/iterm2-finder-tools that keeps the original behavior of reusing an open iTerm2 window.
- Run Automator, select a new Service
- Select Utilities -> Run AppleScript
- Service receives selected 'folders' in 'finder.app'
- Paste script:
Setting up an OS to work with xhyve can be a bit tricky, but it's not impossible. These intructions should be generally applicable to most versions of Linux.
Xhyve will use a file as a logical disk. Be sure you have the filesize you need, because growing the file later is tricky to impossible (you could try to use qcow
or similar to get around this, but qcow volumes can be tricky to mount).
dd if=/dev/zero of=hdd.img bs=1g count=32 # Create a 32 gig disk. Raise 'count' as desired
Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.
This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.
There is a companion feature matrix of various tools. Comments are welcome in the same manner.