Kim Cheung

There are multiple options on AWS for running containers but my go to default approach is with the Elastic Container Service (ECS). AWS doesn’t charge to run the ECS control plane and it’s easier to setup than Kubernetes. With ECS you can use EC2 instances for worker nodes or use serverless compute with Fargate. When using Fargate you just pick the CPU and Memory amounts you want and AWS takes care of spinning up and managing the compute. An example for setting up ECS using Terraform is presented below from Pankaj Makhijani. Using Terraform makes setting ECS up really easy. https://lnkd.in/ed9MeiS6

51

8 Comments

Just because AI can generate network automation scripts doesn’t mean you should run them in production. There’s been a big shift lately. Engineers are using large language models to build their first scripts, often without fully understanding what the code does. And I get it. When you’re under pressure to automate, and tools like ChatGPT promise working solutions in seconds, it’s easy to take the shortcut. But infrastructure is not a sandbox. Network automation touches the systems we rely on every day. It connects services, businesses, and controls how data flows securely across organizations. One wrong line of code can take down more than just a lab environment. Out of curiosity, I’ve tested this myself. I took some of the workbook tasks from my Masterclass and asked an LLM to solve them. What happened: → Some scripts looked okay at first glance, but missed key context. → Others skipped important validation steps or made incorrect assumptions. → Most gave answers that were confidently wrong (with zero indication anything was off). None of them would pass the DevNet Expert Lab exam. And more importantly, I wouldn’t run any of them in production. AI will play a growing role in how we work. It already is. But if you can’t evaluate the code it gives you (if you don’t understand what it does and why) then you’re not automating. You’re just delegating blindly. Code will be written once and read countless times. Make sure you can read and not just write. Automation is a skill and like all skills, it’s only valuable if you understand the consequences of what you’re doing. Especially when the network is involved. If you're aiming to sharpen both your tooling and your thinking, the next Masterclass starts August 19.

58

9 Comments

Having problems with BGP? First, you need to identify where the problem is: 1. BGP neighbor establishment (flapping or failing to peer) 2. Routes missing from the routing table 3. BGP route advertisement issues 3. Multihoming inbound 4. Multihoming outbound Second, dive deeper into the specific section. For example, if routes are missing from the routing table, you may need to use a few commands to validate: 1. Verify BGP peer establishment using the commands: show ip bgp summary show ip bgp neighbor 2. Verify routes learned from peers using the command: show ip bgp neighbor a.b.c.d routes 3. Verify filters using the command: show running-config | include route-map|prefix You can find additional strategies to troubleshoot BGP by following the link below. https://lnkd.in/dX-uf7nf #binaryavenue #bgp

29

3 Comments

🔥OpenShift for Telco 5G Workloads (CNFs vs VNFs) I found the OpenShift for Telco 5G Workloads (CNFs vs VNFs) document to be very insightful and easy to follow. It clearly explains the differences between VNFs and CNFs, breaking down their architectures, scaling models, and lifecycle management approaches in a simple comparison table. I especially liked how the document connects these concepts to 5G use cases such as URLLC, eMBB, and mMTC, showing why CNFs are more suited for modern telco environments. The explanation of OpenShift’s role in enabling carrier-grade Kubernetes, automation with Operators, and edge computing support was very practical. Real-world use cases like 5G core functions, RAN, and MEC made the content highly relatable. I also appreciated that the challenges—such as cultural shifts, performance tuning, and hybrid deployments—were discussed honestly instead of only highlighting advantages. Overall, this document provides a strong foundation for telecom professionals exploring CNF adoption on OpenShift in their 5G journey. 💬 Comment “CNFs vs VNFs” below if you’d like me to send you the OpenShift for Telco 5G Workloads (CNFs vs VNFs) PDF 📥 — it’s ready to share! #OpenShift #DevOps #Kubernetes #RedHat #CloudNative #5GNetwork #Learning #handsonLabs #Telco5G #NetworkFunctions #Network  

87

210 Comments

Agents can now manually prioritize the next important task, email, or chat in a queue. For example, when a customer calls in to enquire about their previously submitted refund request, an agent can search for any pending tickets related to the case, assign it to themselves, and resolve it immediately. https://lnkd.in/gEvgZ8zd

24