CloudNets S5 E2 Network Upgrade Considerations

This episode of CloudNets explains how network operators should prioritize upgrades by balancing new feature value against security, reliability, and SLA risks. It highlights the importance of addressing security vulnerabilities quickly using targeted hot patches, which reduce testing scope and operational risk while allowing upgrades to be scheduled and deployed with minimal network disruption.

𝗟𝗲𝗮𝗿𝗻 𝗺𝗼𝗿𝗲 𝗮𝗯𝗼𝘂𝘁 𝗗𝗿𝗶𝘃𝗲𝗡𝗲𝘁𝘀 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗖𝗹𝗼𝘂𝗱
https://drivenets.com/products/

𝗪𝗵𝗲𝗿𝗲 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗗𝗿𝗶𝘃𝗲𝗡𝗲𝘁𝘀
LinkedIn: https://linkedin.com/drivenets  
X: https://x.com/drivenets

𝗣𝗼𝗱𝗰𝗮𝘀𝘁𝘀
Apple:  https://podcasts.apple.com/il/podcast/cloudnets/id1589786423
Spotify:  https://open.spotify.com/show/1q8e4hNOyaz5ySTeRjTP25

𝗪𝗮𝘁𝗰𝗵 𝗠𝗼𝗿𝗲 𝗩𝗶𝗱𝗲𝗼𝘀
   • https://youtu.be/-8EbkT524yo?si=qs70VVUFBqrTQtki
   • https://youtu.be/F7MwHpnbGP0?si=L5R-s3Kq4PgcyVOh
   • https://youtu.be/SI5MPwFy_XM?si=MJAgiWkQl91vIH6Y

Transcript

 Welcome to CloudNets where networks meet cloud. Today we're going to talk again about some upgrade considerations and we have David, our upgrade expert here with us. Thank you for joining, David. So, David, when you come to plan your upgrade plan, you have different types of new versions. Some are big feature rich versions some, some are smaller but crucial security patches. How do you plan it? What's the consideration?

 What the operators are taking into consideration is one, the features that are coming in there, are they valuable to them? Are they revenue generating for them, those things? The other thing is, are they solving a risk scenario that may have either is it addressing a reliability issue the network or is it a security risk on the network as we're going through? So they're kind of balancing kind of their business needs against kind of their security and kind of their SLA needs that they have in the network.

 Okay. I think in terms of priorities, you need to tackle the security as soon as you can, as soon as you go. And it is a bit painful because these are often unexpected patches you need to run through the network. Is there a way to make it less painful?

 There is, there is. You know, as a supplier, we sometimes say, stay current, take the biggest release you can. We'll get that security fix into there and take it out. But what we want to do is we want to take that one security fix that they have, that CV that may be released. Maybe there's a security breach that happened maybe a week or two ago. They need to get their network secure. They need to make the network they have for their customers, their business customers, risk free. And so when we do that, we can actually take these CVEs and introduce them into hot patches as we go through. So very targeted releases, small bundles, low risk for them to introduce them. And what that helps them to do is they know that this is a targeted fix for the network. So their testing efforts can be very targeted, reducing their risk. And then we can actually schedule this maintenance as we go out, allowing for them to basically know how long it will take for them to complete this upgrade.

 Okay, that's great. So basically the guidance is first go with the security patches because you need those in your network. But the combination of hot patches and scheduled maintenance allows you to do it pretty much safely and without the overhead of rattling the network every couple of weeks.

 Exactly.

 Okay, thank you very much, David, for this valuable information. Thank you for watching and see you next time on Cloudnets. Bye bye.