Author Archives: Russ
Author Archives: Russ
The post Worth Reading: Solving network documentation with code appeared first on 'net work.
The post On the ‘net: The Foggy Future of Network Engineering appeared first on 'net work.
Last time we looked at the snaproute BGP code, we discovered the peer bringup process is a finite state machine. With this in mind, let’s try to unravel the state machine into a set of calls, beginning from our original starting point, a debug message that prints on the screen when a new peering relationship is established. The key word in the debug message was ConnEstablished,
which led to:
func (fsm *FSM) ConnEstablished() {
fsm.logger.Info(fmt.Sprintln("Neighbor:", fsm.pConf.NeighborAddress, "FSM", fsm.id, "ConnEstablished - start"))
fsm.Manager.fsmEstablished(fsm.id, fsm.peerConn.conn)
fsm.logger.Info(fmt.Sprintln("Neighbor:", fsm.pConf.NeighborAddress, "FSM", fsm.id, "ConnEstablished - end"))
}
From here, we searched for calls to ConnEstablished,
and found—
func (fsm *FSM) ChangeState(newState BaseStateIface) {
...
if oldState == BGPFSMEstablished && fsm.State.state() != BGPFSMEstablished {
fsm.ConnBroken()
} else if oldState != BGPFSMEstablished && fsm.State.state() == BGPFSMEstablished {
fsm.ConnEstablished()
}
}
Looking for ChangeState
leads us to a lot of different calls, but only one that seems to relate to establishing a new peer, as evidenced by a state that relates to established in some way. This, in turn, leads to—
func (st *OpenConfirmState) processEvent(event BGPFSMEvent, data Continue reading
The post Worth Reading: How Facebook makes you miss out on life appeared first on 'net work.
The post On the ‘Net: Big thinkers leave Cisco appeared first on 'net work.
The post On the ‘Net: You keep using that SDN word… appeared first on 'net work.
The post Worth Reading: Protecting your assets appeared first on 'net work.
The post Worth Reading: Microsoft’s Bid for LinkedIn appeared first on 'net work.
The post Worth Reading: Open Internet access on the line appeared first on 'net work.
This is a recent round table discussion I participated in over at LightReading. My friends over at ECI put this together.
The post Worth Watching: Has SDN lived up to the hype? appeared first on 'net work.
The post On the ‘net: What does a control plane do? appeared first on 'net work.
The post Worth Reading: Navigating EU safe harbor appeared first on 'net work.
The post Worth Reading: All the Apache streaming projects appeared first on 'net work.
This is coming out of the architecture team at LinkedIn—it’s really interesting for mid-tier scalers, large financials, and the like, so I thought I’d share it here as well.
The post Open19: A New Vision for the Data Center appeared first on 'net work.
The overall design of Ambry should look fairly familiar. There are frontend servers that handle incoming requests (there are just three operations: put, get, and delete) and route them to backend data nodes which store the actual data. A ZooKeeper-based cluster manager looks after the state of the cluster itself. —the morning paper (the full paper is here)
The post Worth Reading: LinkedIn’s Ambry appeared first on 'net work.
The post Worth Reading: Hyperties appeared first on 'net work.
The post Worth Reading: Sharing your password is illegal appeared first on 'net work.