Today we are thrilled to welcome UK2 Group as a CloudFlare partner. Customers of UK2 Group (including its brands UK2.net, Midphase, and Westhost) are now able to access CloudFlare’s web performance and security solutions with a single click. Backed by CloudFlare, UK2 Group’s customers can now protect their websites against security threats, ensure only clean traffic gets served, and speed up site performance no matter where visitors are located. Customers in need of advanced features, and even more performance and security, can sign up for CloudFlare Plus—a plan only offered through our reseller partners.
UK2 Group is one of the innovators of the hosting industry and operates globally. While its name points to its roots (located just down the road from the CloudFlare office in London), it also has an extensive presence in the US. We’re excited to partner with UK2 Group to provide the best web performance and security to its numerous customers.
As we reported last April, Cisco changed the CCIE Lab Exam retake policy to an exponential backoff, meaning that the more attempts you took at the lab the more time you had to wait between attempts.
In a sudden change of heart, today Cisco announced that they are reversing their policy change until at least December 31st 2015. Per Cisco:
“For a limited time, we will waive the current lab retake policy so that all lab candidates will be able to retest for their lab exam with only a 30-day wait period.” “If you register for any CCIE lab exam between now and December 31, 2015, you will have the option of retaking the exam with only a 30-day wait regardless of the number of attempts you may have already made.”
Frequently Asked Questions about the policy changes:
Q: Does this mean that between now and December 31, I can take the lab every 30 days?
A: Yes.Q: Is the original policy back in place after December 31?
A: What happens after December 31 is dependent on the results of our research from now until that date.Q: What does this mean if my current Continue reading
Tech media speculates on Microsoft acquiring AMD and Docker. And here's why drones and people don't always mix.
The post Microsoft Acquisition Rumors & Drones Vs. People appeared first on Packet Pushers Podcast and was written by Drew Conry-Murray.
INE’s CCIE Service Provider v4 Advanced Technologies Class continues today at 08:00 PDT (15:00 UTC) with Inter-AS MPLS L3VPN. All Access Pass subscribers can attend at http://live.INE.com. Recordings of some of the previous class sessions up to this point are now available via AAP library here.
Additionally, INE’s CCIE SPv4 Workbook is now available in beta format here.
Hope to see you in class!
CloudFlare's DNS server, RRDNS, is written in Go and the DNS team used to generate a file called version.go
in our Makefile. version.go
looked something like this:
// THIS FILE IS AUTOGENERATED BY THE MAKEFILE. DO NOT EDIT.
// +build make
package version
var (
Version = "2015.6.2-6-gfd7e2d1-dev"
BuildTime = "2015-06-16-0431 UTC"
)
and was used to embed version information in RRDNS. It was built inside the Makefile using sed
and git describe
from a template file. It worked, but was pretty ugly.
Today we noticed that another Go team at CloudFlare, the Data team, had a much smarter way to bake version numbers into binaries using the -X
linker option.
The -X
Go linker option, which you can set with -ldflags
, sets the value of a string variable in the Go program being linked. You use it like this: -X main.version 1.0.0
.
A simple example: let's say you have this source file saved as hello.go
.
package main
import "fmt"
var who = "World"
func main() {
fmt.Printf("Hello, %s.n", who)
}
Then you can use go run
(or other build commands like go build
or go install
Continue reading
Is it just me, or did we used to call this a mainframe?
The post Rule 11 Redux appeared first on 'net work.
Imagine you’ve just woken up and found yourself in a small kingdom someplace in Europe around 1200 AD. You wander outside, interested in your surroundings, and find yourself in the middle of a fair. Taking stock, you see a man standing in a tent across the way who appears to be tapping on something with a small hammer. Working your way to the tent, you find he is actually tapping out intricate patterns on a small silver disc. While you’re not certain what the disc is for, you take a moment to ask — as any geek would — “are you in the information technology business?”
The tinker, living in 1200 AD, probably doesn’t even understand the question. “What’s information technology?,” he might ask. But let’s consider the tinker’s business. What does a tinker really do?
He takes some material, combines it with technical knowhow, including the development and use of tools, to create a product he knows customers will want. He can’t just use any old tool, or any old technique — he must know something about the correct technology to apply to the problem at hand. And he can’t just hammer anything out on the little Continue reading
A few weeks ago at AnsibleFest in NYC, we did something a little bit different: we assembled a panel of networking experts and had a very interesting discussion about some of the challenges and opportunities around networking automation. With representatives from Cisco, Cumulus, World Wide Technologies, and Network to Code, we dug into some of the reasons to automate your network, the technical and organizational challenges, and we reviewed some of the new Ansible modules being written for various networking components. Network automation is an exciting and early area for us, and we are looking forward to what the future holds.