One of the first things I did when I started my deep-dive into network automation topics was to figure what tools people use to automate stuff and (on a pretty high level) what each one of these tools do.
You often hear about Ansible, Chef and Puppet when talking about network automation tools, with Salt becoming more popular, and CFEngine being occasionally mentioned. However, most network automation engineers prefer Ansible. Here are a few reasons.Read more ...
I was talking to a banking customer in Northern Europe the other day and they asked me about configuration management. They had many different vendors with different management methods in their infrastructure and wanted to know how they could speed up management.
This specific customer had an outsourced infrastructure. They picked what hardware they wanted to run, but then paid a managed services company to deploy the infrastructure in a colocation facility and perform day-to-day operations.
The issue arose in the speed of deployment. When they launched a new application that required a new service in their data center, the application engineers would need to contact the network team in this bank. The network team would then open up a ticket with the managed services company to provision VLANs and open up ports on their firewalls to allow access to the application. The issue was that this process took up to one week to complete.
This bank contacted us with the hope we could help them unify their management under one framework, so that they could insource the firewall configuration to accelerate their application deployments. They asked me about automated management best practices.
Normally when I have this conversation, we Continue reading
For those of you that are looking to familiarize yourself with the Google Cloud Platform, you’re in luck! we have just released Google Cloud Platform: PaaS with App Engine. This course is now available to All Access Pass members through your members account, and to everyone else through purchase at ine.com.
This course is just one of a growing collection of Google classes offered by INE, we also plan on releasing a Google Data Storage course later this week. Until then, read on to learn about Joseph Holbrook’s latest addition to our Google video course library.
Why Study Google App Engine?
Google App Engine is an extremely useful tool; it is a fully managed platform that completely abstracts away infrastructure so you can focus only on code.
About the Course:
This course covers Google App Engine PaaS and more specifically the history, features and functions of Google App Engine. The instructor will explain the benefits of using Google App Engine with live examples and demos.
The course is 4 hours and 5 minutes long and is taught by Joseph Holbrook.
What You’ll Learn:
Students will dive into both deployment models of the App Engine and learn how Continue reading
“Future proofing” was once synonymous with long-range planning—essentially, life-cycle management that enables data center facilities and hardware investments to deliver full value before redevelopment or replacement. The definition has steadily evolved to connote a flexible, resilient architecture capable of supporting accelerated business-driven digital transformation. —Paul Mercina @The Data Center Journal
Sigfox says Proithis' departure was part of a strategic decision.
The carrier used an enhanced abstraction platform christened OSAM-HA.
DNSSEC prevents attacks in which hackers trick the DNS system into storing false IP addresses.
On 10 January 2018, China Telecom activated a long-awaited terrestrial link to the landlocked country of Nepal. The new fiber optic connection, which traverses the Himalayan mountain range, alters a significant aspect of Nepal’s exclusive dependency on India, shifting the balance of power (at least for international connectivity) in favor of Kathmandu.
— The Hindu (@the_hindu) January 13, 2018
Following a number of brief trials since mid-November, Nepal Telecom fully activated Internet transit from China Telecom at 08:28 UTC on 10 January 2018, as depicted below.
In our 2015 coverage of the earthquake that devastated Nepal, I wrote:
Nepal, as well as Bhutan, are both South Asian landlocked countries wedged between India and China that are dependent on India for a number of services including telecommunications. As a result, each country has been courting Chinese engagement that would provide a redundant source of Internet connectivity.
In December 2016, executives Ou Yan of China Telecom Global (CTG) and Lochan Lal Amatya of Nepal Telecom (pictured below) signed an agreement to route IP service through a new terrestrial cable running between Continue reading
The group elected its leadership and determined its working topics.
Route leaks and Distributed Denial of Service (DDoS) attacks have been in the news a good deal over the last several years; but the average non-transit network operator might generally feel pretty helpless in the face of the onslaught. Perhaps you can buy a DDoS mitigation service or appliance, and deploy the ubiquitous firewall at the edge of your network, but there is not much else to be done, right? Or maybe wait on the Internet at large to “do something” about these problems by deploying some sort of BGP security. But will adopting a “secure edge,” and waiting for someone else to solve the problem, really help? @ECI
Advice for entrepreneurs is school level learning
Verizon's participation is kind of amazing given that half the ONAP code came from AT&T.
Conventional wisdom for startups counsels starting with a monolith, but are there situations where you should start with microservices instead? Interviews with dozens of CTOs illuminated the key considerations when deciding whether to start with a monolith or microservices.
My good friend Darby Frey recently kicked off a greenfield project after assuming his new role as Sr. Platform Engineering Lead of Gamut. Despite starting out with monolith at his previous company Belly, he discovered that — in the right circumstances — starting with a monolith isn’t always the best way to go.
“As one does, I allowed much of my thinking in my early days [at my new company] to be influenced by my previous company,” Darby told me.
At Belly, Darby and his team broke down their monolith into a fairly large microservices architecture. They managed to get it to a good place, but only after months of trials and tribulations migrating to microservices.
With this experience fresh in his mind, he approached his new project Continue reading