Hello again, you cloudy clowns and welcome back to cloud architecture foundations. This is cloudy or characteristics are last module and cloud characteristics where we're going to cover one of the most important concepts in all of I t. And not just cloud the concept of base lining your network operations and our last cloudy or characteristic multi tenancy.
So in our last video we had an introduction to cloud elements like hyper visors and virtual machines, and how these elements become the cloud targets of our cloud management and cloud operation systems. And we look to one of the most important cloud characteristics ever. The hugely successful cloud selling point of allowing a nightie organization to self provision
and self service. Their own cloud service is
by empowering your own I t team to manage and support their cloud service. You're maximizing your investment in your I T personnel and helping to reduce your operating expenses by not having to pay someone else of the moves, ads and changes to your cloud environment. In this video, we will be taking a look into what it means
to baseline your network operations and network service is
and we'll be looking at the interesting cloud characteristic of multi tendency. I know you're special and I know you know you're special, but to the cloud may not so much and so without further ado not the French word for goodbye. But in other words, were out of here We're done hanging out. We're going to stay in touch, but don't worry. But what I really mean is that this time
we're just gonna leave this light.
So what is a network baseline and wonder just some of the questions. Does the network baseline answer about your network in your network operations?
How do I measure normal behavior in my network and what is abnormal network behavior and went his abnormal network behavior look like abnormal behavior can mean a lot of things to me. As a network administrator, abnormal behavior could mean that I have down service's or down systems. I could be seeing unusually high demands on my network. Thus the peak in utilization or the opposite.
I have this large valley of network underutilization and underperformance,
meaning I might not be delivering the network service is my users demand so they've given up and are no longer using the network to its full potential. How do I measure network performance and my all about speed? Or am I also looking at metrics like Leighton See and delay? Or is it in user kita high response times that keep my paychecks coming 26 times a year?
Or maybe it's availability and reliability,
one of my performance levels up time and downtime across the service's and my network. This leads us to keep performance indicators. KP eyes and what are the metrics? My organization is going to hold the network accountable. Four. To get the service level agreement or s L. A. And unless I have penciled out where your network performance goals are,
how do I measure how I'm actually delivering on those goals?
Where's the network winning and where's the network losing? And without all this information, I cannot accurately and succinctly quantify risk without knowing the performance goals and KP eyes that build the foundation of our network service level agreement. How can I expect to shift any of this network responsibility to a service like the public cloud? If I'm not measuring it,
I will never be able to deliver it.
Whether the service is driven by our own network or by a cloud service provider.
As true propeller heads. It's the howl of the baseline that really gets your juices flowing. There are a ton of network measuring, scanning and monitoring tools out there. There are dozens of open source tools you can start playing with, like P, R T G and Spice works, and almost every in a mess out there offers free trials. Before your licensing goes active,
you might have to deal with advertisements and pop ups with your free versions, but you can get started working on your baseline without a big upfront capital outlay.
There are some very amazing enterprise solutions out there that can do it all from real time network monitoring, alerting and reporting thieving, having built in service ticket and help desk tracking systems.
So how did these baseline systems operate? Well, the majority of them used network censors in these lightweight pieces of software you install called agents. So if you want to measure a one link between your primary network closet in your business high rise and the backup data center across town, you would install agents on each side of the link on computer systems that are running.
And then these agents place I p calls between them and measure things like delay
variable DeLay, known by the term jitter and packet loss. Each of these different measurements could mean you have issues in the white area network hot by hot between your office and the backup site. Our problem could be something as simple as a bad patch cable in the closet or something more serious. Like Arwen, Ratter is suffering from memory leaks.
Another way, these network management systems and monitoring monitoring tools can work
is by the use of network sensors. There are actually physical network devices or sensors that you can plug into a network port on a switch, for example, and start reporting to her properly configured network management system. But in most cases will we mean by a network censor is a software center.
P A R T G, for example, uses more than 500 software center types.
For example, the use appear T G's ping sensor will check the availability and up time of your servers and other devices by running regular ping tests. There are numerous S and M p Simple network management Protocol and W M I sensors that will allow you to measure metrics such as free space and hard disks. CPU memory load
temperatures and band with usage
and packet sniffing sensors enable you to monitor and analyze band with consumption broken down by protocol and I p address.
So what the proper use of network baseline tools, whether it be packet sniffers to full blown network monitoring and management systems Our I T organization will build over time a baseline of our network behaves and will glean from this information the key performance indicators that are unique to our organization. Our network service is and how those service's perform
is what our I T organization really cares about. And here's where we're going with all of this. Now that we have the baseline information,
we have real measurements and real metrics that we can use in the negotiations with our cloud provider on the service's we need on the cloud provider SL is around our cloud needs. If its availability we care about, well, what is the cloud providers up time? If it's performance, what kind of network connectivity is organization need to deliver on cloud response times
and with our cloud performance as a service.
How much CPU RAM memory and dis storage do we require to move our business critical applications from on premise to being cloud delivered and cloud managed. Having a successful network baseline is a fundamental requirement for an organization have successful cloud adoption and successful cloud business outcomes.
Last cloud Character stuck We want to talk about his cloud Multi Tendency Bolty Tendency is an architecture that provides a single instance of an application to serve multiple clients or tenants. Tenants are allowed to have their own view of the application and make custom is ations roller meaning completely. Unaware that other cloud tenants are also using the same application,
tenants are allowed to change their user interface of the application to give it their own look and feel,
but are not allowed access to change the data and configuration of the application on their own. Implementing multi tendency if you're the cloud is more difficult than a single pertinent per application in per database environment. But multi tendency gives the cloud provider real scale real cost efficiencies while still being able to maintain
the unique security and isolation requirements of each of the cloud customers
and cloud tenants. Multi tendency could only be delivered like most of the clouds, cloudy and even cloudier characteristics through the power of software and hardware, virtual ization and remote access.
Look out, you cloudy clowns. It's time for our learning Check.
What is a network baseline? Why is the network baseline important or organization when planning a cloud migration?
What is the difference between a network monitoring agent and a network monitoring sensor? And what is cloud multi tendency? So hit pause. Put on your cloud makeup. You're Ronald McDonald hair and your bozo nose. Come up with your answers and come back and we'll review our answers together.
Okay, so what's the network baseline? A network baseline is the averaging or baseline of our network is performing, and everything can and oftentimes is measured from network band with how fast our hard drives air spinning key performance indicators are identified and then measured over time, so we have real use network data.
A network baseline is important to our organization because we can't improve or move. Our service is to a service provider like the public cloud, unless we know what service level agreements are cloud provider needs to adhere to. If we know what computing resource is, we use over time. For example, we know
what to have our cloud provider billed for us and manage for organizations use.
What is the difference between a network monitoring agent and network monitoring center? Trick question there often the same. But an agent is usually software that is installed in a network client that places network calls to other agents that we can measure. Sensors are in software, for example,
the type of calls and agent would use, like the network management in trouble, shooting protocols of Ping
and S and M P and Cloud multi tendencies, where, instead of the cloud building out separate infrastructure for each of its customers, it can deliver true scale and efficiencies by sharing. Resource is between customers through the power of hardware and software, virtual ization while ensuring the customers air securely isolated and protected from one another.
So in today's lecture, we discussed our baselines and how network monitoring agents and sensors report to network management systems and scanning tools to perform network baselines, and we spoke about the power and efficiency of the clouds, multi tendency architecture So the next time we meet, we will begin module three and start taking a deeper look into Amazon Web service is Microsoft Azure,
Microsoft Office 3 65 and Google Cloud Platforms On behalf of all of the cyber clowns here, the cyber security and I t learning. We want to wish you and all of your users
on your network very happy Cloud service is and very happy packets.