This procedure is tested on Mac OS X 10.12.6
PHP 7.2 installed with Homebrew.
Download the following files from Oracle website (yes, you need to create an account and accept terms):
This procedure is tested on Mac OS X 10.12.6
PHP 7.2 installed with Homebrew.
Download the following files from Oracle website (yes, you need to create an account and accept terms):
These are my notes for taking the Microsoft US Building Footprints and splitting them into more manageable chunks based on US Census Tracts.
All of this happened on an m5.xlarge in AWS and used up about ~300GB of EBS over the course of a few hours.
Make a filesystem on the EBS volume and mount it:
sudo mkfs.xfs /dev/nvme1n1
mount /dev/nvme1n1 /mnt
[ | |
{ | |
"_id": "74ad2b40-3774-11e8-8bf5-0529df825f82", | |
"_type": "visualization", | |
"_source": { | |
"title": "Amount Errors", | |
"visState": "{\"title\":\"Amount Errors\",\"type\":\"metric\",\"params\":{\"addLegend\":false,\"addTooltip\":true,\"metric\":{\"colorSchema\":\"Green to Red\",\"colorsRange\":[{\"from\":0,\"to\":10000}],\"invertColors\":false,\"labels\":{\"show\":true},\"metricColorMode\":\"None\",\"percentageMode\":false,\"style\":{\"bgColor\":false,\"bgFill\":\"#000\",\"fontSize\":60,\"labelColor\":false,\"subText\":\"\"},\"useRanges\":false},\"type\":\"metric\"},\"aggs\":[{\"id\":\"1\",\"enabled\":true,\"type\":\"count\",\"schema\":\"metric\",\"params\":{\"customLabel\":\"\"}},{\"id\":\"3\",\"enabled\":true,\"type\":\"filters\",\"schema\":\"group\",\"params\":{\"filters\":[{\"input\":{\"query\":\"log: Traceback OR log: error\"},\"label\":\"Error Log Entries\"}]}}]}", | |
"uiStateJSON": "{}", | |
"description": "", | |
"version": 1, |
Docker filesystem layers can be tricky to wrap your head around, and even more so how indoes work. Lets take an example and see what happens when you tail a file that exists in the image as part of your container entrypoint:
host$ docker run -d --rm --name test-inode debian tail -f /etc/issue
54bbfa8fa1f6751593dcf23103a1cdaec7fde8ffbcb3e31bab466b4f7a3581e7
Now make some changes to the file:
#!/usr/bin/env bash | |
#This assumes you are attempting to connect to Azure AKS from outside Azure. | |
#By default Azure doesn't provide any external access or assign an IP address to worker nodes, so this script: | |
#1. Creates a public ip address in the same region as the cluster | |
#2. Associates the ip address with the NIC card attached to the worker VM | |
#Azure creates a separate group for managed clusters e.g. MC_my_cluster_my_cluster_group_my_region | |
#Azure creates node names in the format aks_agentpool_0000000_0 | |
#The respective NIC cards have the same number as the node_number e.g. aks-agentpool-0000000-nic-0 |
I was talking to a coworker recently about general techniques that almost always form the core of any effort to write very fast, down-to-the-metal hot path code on the JVM, and they pointed out that there really isn't a particularly good place to go for this information. It occurred to me that, really, I had more or less picked up all of it by word of mouth and experience, and there just aren't any good reference sources on the topic. So… here's my word of mouth.
This is by no means a comprehensive gist. It's also important to understand that the techniques that I outline in here are not 100% absolute either. Performance on the JVM is an incredibly complicated subject, and while there are rules that almost always hold true, the "almost" remains very salient. Also, for many or even most applications, there will be other techniques that I'm not mentioning which will have a greater impact. JMH, Java Flight Recorder, and a good profiler are your very best friend! Mea
[options] | |
# | |
# WARNING: | |
# If you use the Odoo Database utility to change the master password be aware | |
# that the formatting of this file WILL be LOST! A copy of this file named | |
# /etc/odoo/openerp-server.conf.template has been made in case this happens | |
# Note that the copy does not have any first boot changes | |
#----------------------------------------------------------------------------- | |
# Odoo Server Config File - TurnKey Linux |
Nodes are not assigned public IP. If you have accessible VM in the same VNET as worker nodes, then you can use that VM as jump host and connect the worker via private IP.
Alternatively public IP can be assigned to a worker node. This readme shows how to do that.
find out the resource group that AKS created for the node VMs
N.B. SQLAlchemy now incorporates all of this information in its documentation; I’m leaving this post here, but recommend referring to SQLAlchemy instead of these instructions.
pip
or conda
, for example:After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work. | |
The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0." | |
Database files have to be updated before starting the server, here are the steps that had to be followed: | |
# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default | |
brew unlink postgresql | |
brew install [email protected] | |
brew unlink [email protected] | |
brew link postgresql |