Protected: NSX Multi-Tenancy Journey
The post Protected: NSX Multi-Tenancy Journey appeared first on Network and Security Virtualization.
The post Protected: NSX Multi-Tenancy Journey appeared first on Network and Security Virtualization.
When you’re designing a Kubernetes environment, whether it’s small or large, there are a few things that you must think about prior to writing the code to deploy the cluster or implementing the GitOps Controller for all of your Continuous Delivery needs. First, you must plan. Planning is the most important phase. In blog one […]
The post Build Your K8s Environment For The Real World Part 1 – Day Zero Ops appeared first on Packet Pushers.
Nvidia is not rich enough – or dumb enough – to build a cloud to rival the likes of Amazon Web Services, Microsoft Azure, or Google Cloud. …
Nvidia Bends The Clouds To Its Own Financial Will was written by Jeffrey Burt at The Next Platform.
Like the rest of the world, we have been watching Microsoft’s increasing use of foundation models as it transforms its services and software. …
Inside The Infrastructure That Microsoft Builds To Run AI was written by Timothy Prickett Morgan at The Next Platform.
Differences between project (disruption, replacement), service (smooth, continuous) and product (updates, changes) mean that process and people have very different approach to technology management and operations.
The post Heavy Strategy 43 Is The IT Team In The Service, Project or Product Business appeared first on Packet Pushers.
It has arrived! The latest reference architecture showcasing the best practices for deploying Red Hat Ansible Automation Platform 2.3 on Red Hat OpenShift!
With Ansible Automation Platform running on top of Red Hat OpenShift, you get the best of both worlds. You can now focus on what really matters - automation - while taking advantage of Red Hat Ansible Automation Platform Operator to do the heavy lifting of deploying, managing, scaling and upgrading your Ansible Automation Platform environment.
This reference architecture not only focuses on the step-by-step to deploy Red Hat Ansible Automation Platform 2.3 on Red Hat OpenShift, but focuses on key aspects including:
Sizing your automation controller: Learn how to size your automation controller by understanding its control capacity and how many automation jobs can run concurrently.
Resource management: Discover how to set resource requests and limits for the Ansible Automation Platform, ensuring that your deployment has enough resources to run smoothly and efficiently.
Installation guidance: Understand key considerations prior to your deployment of Red Hat Ansible Automation Platform.
Monitoring your Ansible Automation Platform: Learn how to use Prometheus and Grafana to monitor your Ansible Continue reading
The evolution of WAN architectures has historically paralleled that of application architectures. When we primarily connected terminals to mainframes, the WAN architecture was largely point-to-point links connecting back to data center facilities. As traffic converged to remove OpEx-intensive parallel network structures, the WAN evolved to architectures that enabled site-to-site connectivity in a full mesh or configurable mesh and then enabled multi-tenancy for carrier cost optimization.
A networking engineer attending the Building Next-Generation Data Center online course asked this question:
What is the best practice to connect DC fabric to outside world assuming there are 2 spine switches in the fabric and EVPN VXLAN is used as overlay? Is it a good idea to introduce edge (border) switches, or it is better to connect outside world directly to the spine?
As always, the answer is “it depends,” this time based on:
A networking engineer attending the Building Next-Generation Data Center online course asked this question:
What is the best practice to connect DC fabric to outside world assuming there are 2 spine switches in the fabric and EVPN VXLAN is used as overlay? Is it a good idea to introduce edge (border) switches, or it is better to connect outside world directly to the spine?
As always, the answer is “it depends,” this time based on:
I see this question rather often asked on various social media. A post on Twitter a few days ago triggered this little blog post and I deeply appreciate the poster. The question was simple “Is it really necessary for an engineer to know or understand the key RFC numbers?”. Some of the engineers I work […]
The post The Networking RFCs: To read or not to read? appeared first on Packet Pushers.
The BackBox network automation platform comes with many pre-built functions to make routine tasks performed by network administrators simple & foolproof. In this demo, BackBox’s Senior Product Manager Perry Greenwood shows Packet Pushers’ Ethan Banks how to automate network device upgrades using BackBox. We look at the entire lifecycle of the upgrade process, including scheduling, […]
The post Demo Bytes: Upgrading Network Devices With BackBox – Video appeared first on Packet Pushers.
One of the things that people have mentioned to me in the past regarding my event management skills is my reaction time. They say, “You are always on top of things when they go wrong. How do you do it?”
My response never fails to make them laugh. I offer, “I always assume something is going to go wrong. I may not know what it is but when it does happen I’m ready to fix it.”
That may sound like a cynical take on planning and operations but it’s served me well for many years. Why is it that things we spend so much time working on always seem to go off the rails?
Whether it’s an event or a network or even a carpentry project you have to assume that something is going to go wrong. Why? Because the more complex the project the more likely you are to hit a snag. Systems that build on themselves and require input to proceed are notorious for hitting blocks that cause the whole thing to snarl into a mess of missed timelines.
When I was in college studying project management I learned there’s even a term for Continue reading
Late last year, we introduced a Red Hat Ansible Certified Collection Collection for Terraform. This was an important step in automation, as these two tools really are great together and leveraging Ansible's ability to orchestrate other tools in the enterprise made this a no-brainer. Terraform with its infrastructure as code (IaC) provisioning and Ansible’s strength in configuration as code are a synergy that cannot be ignored - we are better together! Organizations are now in the position to utilize their existing infrastructure as code manifests and extend their automation with Terraform and Ansible together.
Now, we are back with help from our partners at Kyndryl and XLAB and adding more value and magic to infrastructure as code - This time we have some extra muscle with an addition to the Red Hat Ansible Certified Content Collection: The Ansible provider for Terraform.
So what does the provider help us with?
Without a provider, we would need to rely on inventory plugins for the different cloud platforms and use filters to grab instance information from our freshly "Terraformed" infrastructure. This allows us to update our inventory so we can run automated tasks against these hosts. This is pretty smooth in Continue reading