“We need to combine AI with that human apathy,” she said during an RSA keynote. “We need both...
Interacting directly with the AWS APIs—using a tool like Postman (or, since I switched back to macOS, an application named Paw)—is something I’ve been doing off and on for a little while as a way of gaining a slightly deeper understanding of the APIs that tools like Terraform, Pulumi, and others are calling when automating AWS. For a while, I struggled with AWS authentication, and after seeing Mark Brookfield’s post on using Postman to authenticate to AWS I thought it might be helpful to share what I learned as well.
The basis of Mark’s post (I highly encourage you to go read it) is that he was having a hard time getting authenticated to AWS in order to automate the creation of some Route 53 DNS records. The root of his issue, as it turns out, was a mismatch between the region specified in his request and the API endpoint for Route 53. I know this because I ran into the exact same issue (although with a different service).
The secret to uncovering this mismatch can be found in this “AWS General Reference” PDF. Specifically with regard to Route 53, check out this quote from the document:
Or why you should stop travelling for a while
The post My Personal Notes on Corona Virus (COVID-19) And Travelling appeared first on EtherealMind.
We are using AMD 2nd Gen EPYC 7642 for our tenth generation “Gen X” servers. We found many aspects of this processor compelling such as its increase in performance due to its frequency bump and cache-to-core ratio. We have partnered with AMD to get the best performance out of this processor and today, we are highlighting our tuning efforts that led to an additional 6% performance.
Thermal design power (TDP) and dynamic power, amongst others, play a critical role when tuning a system. Many share a common belief that thermal design power is the maximum or average power drawn by the processor. The 48-core AMD EPYC 7642 has a TDP rating of 225W which is just as high as the 64-core AMD EPYC 7742. It comes to mind that fewer cores should translate into lower power consumption, so why is the AMD EPYC 7642 expected to draw just as much power as the AMD EPYC 7742?
Let’s take a step back and understand that TDP does not always mean the maximum or average power that the processor will draw. At a glance, Continue reading
For the past few years we’ve held a conference specifically for contributors at the same time as AnsibleFest. The additional days brought together existing contributors to the open source Ansible code base and those wanting to get involved.
It is with great pleasure that we announce a European Contributor Summit will be held in Gothenburg, Sweden, ahead of the usual summit at AnsibleFest! On March 29 we’ll be welcoming new and old contributors alike. So if you already contribute to Ansible, or would like to, but don’t know how or where to start, this event is for you.
Contributor Summit US will again be held the day before this year’s AnsibleFest event in San Diego. You can sign up for AnsibleFest updates here.
Ansible Contributor Summit is a day-long working session with the core developer team and key contributors. We’ll discuss important issues affecting the Ansible community, and you can take part in person or online. Information for remote participation will be announced about a week beforehand. There is an additional hackathon the following day, on March 30, where you can sit down with fellow contributors to work through anything specific.
The event is free to attend, although registration is Continue reading
Starting with a short message to anyone interested in our on-site events in Switzerland: on March 10th we’re running our first 2020 workshop, focusing on Docker and containers.
I totally reworked the material, adding tons of new Docker networking examples (including deep dive into iptables) and a few fun things like building an Ansible container, or starting the whole NetBox stack with a single command. Even if you don’t plan to deploy containers in your production network, you might drop by just for that part.
And now for the upcoming webinars:
Starting with a short message to anyone interested in our on-site events in Switzerland: on March 10th we’re running our first 2020 workshop, focusing on Docker and containers.
I totally reworked the material, adding tons of new Docker networking examples (including deep dive into iptables) and a few fun things like building an Ansible container, or starting the whole NetBox stack with a single command. Even if you don’t plan to deploy containers in your production network, you might drop by just for that part.
And now for the upcoming webinars:
Read more ...A discussion with panelists from the U.S. Department of Defense, Huawei, a conservative think tank,...
While substantial, the investment pledge is down from the $13 billion Google invested in the space...
Informed consent of genetic data is critical, but people aren’t always clear about what they are...
The Facebook-backed consortium announced a string of new initiatives including the launch of its...
Cisco SD-WAN targeted FedRAMP; Verizon warned of mobile security risks; and the Russians are coming...
Southwest Airlines’ Carrie Mills says CISOs want less agents, fewer point products, and more...
The vendor's boldly named Project Maestro is now on the market under the more strait-laced VMware...
In another part of his never-ending EVPN/BGP saga Ivan Pepelnjak argued with Juniper fanboys once again about sanity of iBGP-over-eBGP and eBGP-over-eBGP designs and all that fun stuff. I’ve already written my opinion about that topic in my previous post and numerous comments to Ivan’s posts (TL;DR: iBGP-over-eBGP design has its advantages, just implement it wisely – don’t place RR on spine switches).
But there is one thing that worries me. In almost every one of his posts Ivan talks about some mythical Junos limitations that don’t allow Juniper to support eBGP only (over single session) design. So let’s find out what these limitaions are.
Juniper has freely available version of vQFX for Vagrant. There are a few lab topologies available on GitHub. I will be using full-2qfx-4srv-evpnvxlan topology in this post.
This topology comes with Ansible playbook that configures vQFX switches with iBGP-over-OSPF EVPN. Standard Juniper configuration, just for reference:
Yaml- YAML Ain’t markup langauge
The devices need a standard protocol to communicate between each other , similarly there is requirement of specific standard data format to communicate between application .YAML is one of the data format and is best known to be human friendly means it’s easier to understand and write for human compare to other well know data format such as JSON and XML
YAML document starts with 3 hyphen ‘—‘ at top ,it indicate beginning of YAML document .
We can have mix data types in YAML, let’s see with an yaml example
ex1_ya.yaml
---
IOS: CISCO
JNOS: JUNIPER
CISCO:
- Router
- 7600
- True
- ['interface','ip address']First and second item i.e IOS: CISCO and JNOS: JUNIPER is dictionary where ‘IOS’ and ‘JNOS’ is key and ‘CISCO’ and ‘JUNIPER’ is respective values
Third Item too is dictionary which comprises of list having different data type as below:
‘Router’ is string type.
‘7600’ is integer type
‘True’ is Boolean type
Fourth item [‘interface’,’ip address’] is list containing strings
Working with YAML using Python
The first and foremost thing to use YAML is to install PyYAML , it’s a YAML parser .
anurudh@anurudh:~/newfolder$ Continue reading
More than 600 of the world’s leading Internet engineers from 60 economies gathered last week at APRICOT, and it was encouraging to see routing security take center stage in the largest meeting of the technical community in the region.
The Internet Society is a long-time partner of the annual event, also called the Asia Pacific Regional Internet Conference on Operational Technologies, and this year we held two community gatherings, spoke in several sessions, and ran a booth throughout the conference.
The ten-day meeting consisted of workshops, tutorials, conference sessions, birds-of-a-feather sessions, and peering forums from 12-21 February in Melbourne, Australia. This year marked the 25th anniversary of APRICOT, and it was good to recognize how the event has grown over time and contributed to technical capacity building in the region. It also gave me the chance to reflect on my own participation in the event over the years, including from when I was in the private sector prior to my current role.
One of the things Internet builders get together for at APRICOT is to share the technical knowledge needed to run and expand the Internet securely. So it was a great opportunity to bring attention to the Mutually Continue reading
Once Russian state-sponsored groups compromise just one machine, they can move laterally to other...
The networking giant needs FedRAMP authorization before it can begin deploying its SD-WAN offerings...