For any network that provides routing services to customers it is important to segregate them in different virtual topologies that don’t interfere with each other.
This post is not about NFV, but it is important to understand …
It’s amazing how sometimes people fond of sharing their opinions and buzzwords on various social media can’t answer simple questions. Today’s blog post is based on a true story… a “senior network architect” fully engaged in a recent hype cycle couldn’t answer a simple question:
Why exactly would you need VXLAN and EVPN?
We could spend a day (or a week) discussing the nuances of that simple question, but all I have at the moment is a single web page, so here we go…
As the name of this publication suggests, we are system thinkers and we like to watch the evolution of a collection of tools into a platform. …
The GPU Database Evolves Into An Analytics Platform was written by Timothy Prickett Morgan at The Next Platform.
New applications and workloads are constantly being added to Kubernetes clusters. Those same apps need to securely communicate with resources outside the cluster behind a firewall or other control point. Firewalls require a consistent IP, but routable IPs are a limited resource that can be quickly depleted if applied to every service.
With the Calico Egress Gateway, a new feature in Calico Enterprise 3.0, existing firewalls and control points can now be used to securely manage access to infrastructure and services outside of the cluster. In addition, IT teams are now able to identify an application/workload in a Kubernetes namespace via the source IP.
As organizations progress on their Kubernetes journey from pilot to production, they begin migrating existing applications into the cluster, which has merged with the greater IT environment. For the platform teams involved, this creates challenges because these apps will need to communicate to services outside of the cluster.
Wound-licking Cisco targeted the next cloud computing wave; Nokia cried foul on rivals' 800G...
If your idea for interconnection and migration to the private cloud involves using NSX and L2VPN so that you can “stretch the vlan” between your NSX private farm and the one into the Cloud you are doing it wrong.
No matter if you are using VXLAN as a transport or any other technology, if your plan involves layer 2 extension you are doing it wrong.
Not every application should be migrated to the public cloud, and most definitely you should not migrate something that relies on a layer 2 adjacency to work.
If layer 2 extension is a way to allow ip mobility, then again, it’s just a lazy design. There are better ways to provide same-subnet IP mobility that doesn’t require layer 2 (see LISP or BGP-EVPN Type 5 routing for example).
Even if it works on Power Point or on a small demo, you really should NOT.
Red Hat Ansible Automation Platform introduces automation services catalog, a new hosted service for Red Hat Ansible customers to extend their automation in a controlled way to the various end users who need it. This is a deep dive into the capabilities and features of the offering.
The automation services catalog is designed to be a familiar experience, providing an easy and intuitive user interface for ordering products (automation resources).
Products to Order
The idea is that those using the automation services catalog may not know that what they are ordering is actually Ansible Automation. For example, a product could be a business function, like ordering a new OpenShift project or onboarding a user to a new platform.
Ordering a product will present the user with options to facilitate the order. This could be provisioning the datacenter or applying permissions for a Kubernetes project. Upon submitting the order, the user can see the progress in their order queue. Users can search for past orders and see those currently in progress indicated by statuses including: Order, Failed, Approval Pending and Completed. Orders that are pending approval can be compared with ordering a product from a website and seeing Continue reading
In this episode of the Hedge, Stephane Bortzmeyer joins Alvaro Retana and Russ White to discuss draft-ietf-dprive-rfc7626-bis, which “describes the privacy issues associated with the use of the DNS by Internet users.” Not many network engineers think about the privacy implications of DNS, a important part of the infrastructure we all rely on to make the Internet work.
Quarkus is a Kubernetes native Java framework that allows the programming language to be more...
“It’s not a secret that we did not do as well as we wanted to in the first phase of the web...
The Toronto-based telecom claims the service will provide customers with tools to support both...
The network integrator needed a services management platform that would allow it to configure...
Do you remember the first time you used Docker? I do. It was about six years ago and like many folks at the time it looked like this:
docker run -it redis
I was not using Redis at the time but it seemed like a complicated enough piece of software to put this new technology through its paces. A quick Docker image pull and it was up and running. It seemed like magic. Shortly after that first Docker command I found my way to Docker Compose. At this point I knew how to run Redis and the docs had an example Python Flask application. How hard could it be to put the two together?
version: '3'
services:
web:
build: .
ports:
- "5000:5000"
redis:
image: “redis”
I understood immediately how Docker could help me shorten my developer “commute.” All the time I spent doing something else just to get to the work I wanted to be doing. It was awesome!
As time passed, unfortunately my commute started to get longer again. Maybe I needed to collaborate with a colleague or get more resources then I had locally. Ok, I can run Docker in the cloud, let me see how Continue reading
On 15 May, the Telegraph reported that The Five Eyes intelligence alliance planned to meet to explore legal options to block plans to implement end-to-end encryption on Facebook Messenger. According to the UK-based newspaper, the discussions between the governments of the United States, the United Kingdom, Australia, Canada, and New Zealand would focus on how the “duty of care,” a basic concept found in tort law, could be stretched to force online platforms to remove or refrain from implementing end-to-end encryption. (A duty of care is the legal responsibility of a person or organization to avoid any behaviors or omissions that could reasonably be foreseen to cause harm to others.)
It’s easy to predict what such a strategy might look like – the playbook is familiar. In this case, if duty of care becomes the rationale for banning end-to-end encryption, it could be used as a framework to ban future deployments. Additionally, similar to other legislation, including the Online Harms, there will be an argument that social media companies have a special duty of care to protect vulnerable groups. This is nothing more Continue reading
Today's Day Two Cloud podcast gets into the nerdy details of how an infrastructure professional can use GitHub Actions. Actions lets you chain together steps or instructions and trigger them to run as a workflow. Our guest and guide to GitHub Actions is Chris Wahl.
The post Day Two Cloud 050: Nerding Out On GitHub Actions With Chris Wahl appeared first on Packet Pushers.
In order to help easily migrate from NSX for vSphere to NSX-T, with minimal downtime, the latest release of VMware NSX-T 3.0 introduces Maintenance Mode to NSX-T Migration Coordinator (a tool that has been built into NSX-T since the 2.4 release). The Migration Coordinator tool is designed to run in-place on the same hardware that is running NSX for vSphere, and swap out NSX for vSphere bits with NSX-T.
This blog post is a follow up to the previous blog, Migration from VMware NSX for vSphere to NSX-T, which covers Migration Coordinator. For more details on the Migration Process, please check out the previous blog. This blog focuses on the Maintenance Mode feature which is part of the NSX-T 3.0 release.
Migration Coordinator is a tool that runs on NSX-T Manager. Its disabled by default since migrating from NSX for vSphere to NSX should only be a one-time task.
To enable Migration Coordinator, simply log in to NSX Manager via SSH and run the command “start service migration-coordinator”.
Note: This command is also Continue reading