Hello.
Welcome to CloudNets.
Today we have a special episode, we have a special guest and you have me is also a special host.
Topic of this session is about real life experience.
You’ve heard a lot of things from me and from Dudy about, in theory, how this is good, but you know that there is one big customer where the CloudNets or Network Cloud is being installed, and that customer is AT&T.
We have one guy who has been there from the very beginning and up until now.
That’s Abishek.
So Abishek, a few points from your perspective of your experience with Network Cloud.
Sure.
So Network Cloud is basically you get the ability to manage multiple devices as a single entity, which you don’t see in a Clos architecture.
And we can monitor services and services running on the cluster and the health of the cluster or up to the resolution of each entity in real time.
And this is one of the main highlights of the orchestrator that we have with DNOR.
And when we do have an issue, we get the looking glass view into the cluster as to where this issue is.
And it’s very easy to isolate and fix the issue.
Cool.
So I think these are very important when you’re operating the cluster and it gives a real time view of the system and it makes it even more easier for the operations to use it.
Nice.
So if I bring this down to my perspective of looking at things, first off is that we have one network element eventually, which we are building, and it can scale up as much as we want, but DNOR makes it
into one element which is being managed and then tracks everything that is going on on the inside.
So we have full visibility of the details of the services of the cluster, health, all this kind of issue.
And then when something goes wrong, we have DNOR for the rescue and it helps us in terms of pinpointing the problem and patching in kind of a localized fix to it.
Exactly.
Classic.
Wonderful.
Okay, Abishek, thank you very much for coming all the way for having this session.
And thank you guys for chiming in once again.
Cheers.
Thank you.
