Skip to content

Instantly share code, notes, and snippets.

View sargun's full-sized avatar

Sargun Dhillon sargun

  • Netflix
  • United States
View GitHub Profile
iface eth0 inet static
address 169.254.1.10
netmask 255.255.0.0
mtu 9000
iface eth0 inet static
address 10.243.234.81
netmask 255.255.255.255
gateway 169.254.1.1
mtu 9000
@sargun
sargun / gist:11010886
Created April 17, 2014 20:53
Fuck me.
[ 0.135696] ------------[ cut here ]------------
[ 0.137042] WARNING: at /build/buildd/linux-lts-raring-3.8.0/drivers/iommu/intel_irq_remapping.c:552 intel_enable_irq_remapping+0x77/0x1ad()
[ 0.140657] Hardware name: ProLiant DL360e Gen8
[ 0.141960] Your BIOS is broken and requested that x2apic be disabled
[ 0.141960] This will leave your machine vulnerable to irq-injection attacks
[ 0.141960] Use 'intremap=no_x2apic_optout' to override BIOS request
[ 0.147582] Modules linked in:
[ 0.148488] Pid: 1, comm: swapp0 Not tainted 3.8.0-38-generic #56~precise1-Ubuntu
[ 0.250695] Call Trace:
I am Sargun Dhillon. I posted this on IRC. It was to electronerd. It's 5/6/2014.
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1
owEBiQJ2/ZANAwACARNxNCc1k6elActZYgBTaJzgSSBhbSBTYXJndW4gRGhpbGxv
bi4gSSBwb3N0ZWQgdGhpcyBvbiBJUkMuIEl0IHdhcyB0byBlbGVjdHJvbmVyZC4g
SXQncyA1LzYvMjAxNC4gCgqJAhwEAAECAAYFAlNonOAACgkQE3E0JzWTp6XEEw/9
FKLasskfHJili0W7mBoAbz8rXJBOVAxwmX0vdYCqomxnR0Ga/ew8UR7Vpf9j8D7M
@sargun
sargun / Output
Last active August 29, 2015 14:02
border1-n3064-1:Ethernet1/9 -> border1-leaf1-n3048-1:Ethernet1/49
border1-n3064-1:Ethernet1/10 -> border1-leaf1-n3048-2:Ethernet1/49
border1-n3064-1:Ethernet1/11 -> border1-leaf1-n3048-3:Ethernet1/49
border1-n3064-1:Ethernet1/12 -> border1-leaf1-n3048-4:Ethernet1/49
border1-n3064-2:Ethernet1/9 -> border1-leaf1-n3048-1:Ethernet1/50
border1-n3064-2:Ethernet1/10 -> border1-leaf1-n3048-2:Ethernet1/50
border1-n3064-2:Ethernet1/11 -> border1-leaf1-n3048-3:Ethernet1/50
border1-n3064-2:Ethernet1/12 -> border1-leaf1-n3048-4:Ethernet1/50
border1-n3064-3:Ethernet1/9 -> border1-leaf1-n3048-1:Ethernet1/51
border1-n3064-3:Ethernet1/10 -> border1-leaf1-n3048-2:Ethernet1/51
command 'sysmgr_show_sys_gdb'
syntax show system gdb
keyword show "Show running system information"
keyword system "System-related show commands"
keyword gdb "Displays pids under gdbserver control"
hidden gdb
mode '/exec'
handler function sysmgr_show_pid cli-sysmgr args-legacy
end

So, I'm sure people want to know more of my opinions. I've been a long-standing advocate of pushing complexity out of the network as much as possible. First though, let's talk about the network and think of it as closer to a sphere. For the sake of reasoning, the "edge" is the core of the sphere, and the computers cover the surface of the sphere. First, let's talk about the common case failures. As failures get closer to the core of the sphere, they inherently introduce more risk, because they end up propagating in all directions equally, as opposed to a failure at a point on the edge - which propagates to far fewer nodes in comparison.

Complexity & Failures: Complexity will cause failures. It typically falls under the special causes, where something that you didn't predict blindsides you. The key to this is not concentrating complexity. As to the earlier analogy, by concentrating fault domains in the center of the sphere, you inherently introduce more risk. This, of course, assumes that the failures at han

package memberview
import "github.com/hashicorp/serf/serf"
import "time"
import "bytes"
import "math/rand"
import "strings"
import "log"
type MemberView struct {
{
"id": "inky",
"container": {
"docker": {
"image": "mesosphere/inky"
},
"type": "DOCKER",
"volumes": []
},
"args": ["hello"],
% @doc Increment VClock at Node.
-spec increment(Node :: vclock_node(), VClock :: vclock()) -> vclock().
increment(Node, VClock) ->
increment(Node, timestamp(), VClock).
% @doc Increment VClock at Node.
-spec increment(Node :: vclock_node(), IncTs :: timestamp(),
VClock :: vclock()) -> vclock().
increment(Node, IncTs, VClock) ->
{{_Ctr, _TS}=C1,NewV} = case lists:keytake(Node, 1, VClock) of
setup_bucket() ->
case riak_core_bucket_type:status(?consistent_type) of
ready ->
riak_core_bucket_type:activate(?consistent_type);
created ->
timer:sleep(100),
setup_bucket();
undefined ->
riak_core_bucket_type:create(?consistent_type, [{consistent, true}]),
setup_bucket();