作者: | @voluntas |
---|---|
バージョン: | 0.2.1 |
URL: | https://voluntas.github.io/ |
まだ個人の興味で作ってるだけです
#!/usr/bin/ruby | |
require 'json' | |
require 'net/http' | |
require 'shellwords' | |
require 'time' | |
require 'uri' | |
require 'yaml' | |
@target_sidecar_image = YAML.load(YAML.load(`kubectl --namespace=istio-system get configmap istio-sidecar-injector -o yaml`)['data']['config'])['template'].match(/.*(eu.gcr.io\/at-artefacts\/platform-istio-proxy.*)".*/)[1] |
FROM alpine | |
COPY configure-node.sh configure-node.sh | |
CMD ["/bin/sh", "configure-node.sh"] |
sudo rm -fr /Library/Java/JavaVirtualMachines/jdk-9.jdk/ | |
sudo rm -fr /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin | |
sudo rm -fr /Library/PreferencePanes/JavaControlPanel.prefPane | |
package main | |
import ( | |
"crypto/aes" | |
"crypto/cipher" | |
"crypto/rand" | |
"encoding/hex" | |
"fmt" | |
"io" | |
) |
# Run a PCI/SMBios/net inventory scan and upload the results. This gives us a | |
# way of tracking nodes to some extent, leaving us less blind than usual. | |
# | |
# We use the iPXE pciscan command to enumerate the PCI bus. For each device, we | |
# check the 'header type' register at offset 0x0e. If it's type 0 (endpoint), | |
# we can read the subsystem vendor and device registers too. Unfortunately, if | |
# the 7th bit of the header type field is set (0x80), it indicates a | |
# multi-function device. So to check the type, this bit should be masked out. | |
# Masking is not possible with iPXE commands, so we have to duplicate some of | |
# the iseq tests. |
作者: | @voluntas |
---|---|
バージョン: | 0.2.1 |
URL: | https://voluntas.github.io/ |
まだ個人の興味で作ってるだけです
JEP-123 で利用時に指定する方法が提案されてJava8で使えるようになったらしい。Linuxだと標準で /dev/random
を使うからエントロピーが全部消費されてる状態だとブロックされてた。
# Problem: | |
# | |
# If you use git submodules linking two private github repos, you'll need to create a separate deploy key for each. | |
# Multiple keys are not supported by Ansible, nor does ansible (when running git module) resort to your `.ssh/config` file. | |
# This means your ansible playbook will hang in this case. | |
# | |
# You can however use the ansible git module to checkout your repo in multiple steps, like this: | |
# | |
- hosts: webserver | |
vars: |
Ruby 2.1.0 in Production: known bugs and patches | |
Last week, we upgraded the github.com rails app to ruby 2.1.0 in production. | |
While testing the new build for rollout, we ran into a number of bugs. Most of | |
these have been fixed on trunk already, but I've documented them below to help | |
anyone else who might be testing ruby 2.1 in production. | |
@naruse I think we should backport these patches to the ruby_2_1 branch and | |
release 2.1.1 sooner rather than later, as some of the bugs are quite critical. | |
I'm happy to offer any assistance I can to expedite this process. |