[MUSIC]
Hello everyone. I'm Monika Machado,
Principal Program Manager for the Azure Public
Multi Access Edge or Azure Public MEC, for short.
Hi. I am Moushumi Ghosal,
Principal Program Manager for Azure Public MEC.
With Azure Public MEC, our goal
is to empower enterprises and
developers to take full advantage of
the low latency compute and public 5G connectivity.
I will talk about Azure
Public MEC's value proposition and
show you how we can deploy
compute resources like virtual machines,
Azure Kubernetes service and
other networking services at the Azure Public MEC.
In an ever connected world.
5G and Edge computing [inaudible]
is at the head of the new wave of enterprise
in customer connectivity transformation.
Between 2017 and 2023,
there's an 80 percent expected increase
in the number of connected devices.
According to Pew Research,
72 percent of enterprises
believe the importance of edge computing
data streams in business process is
either critically important or very important.
According to Gartner research,
50 percent of enterprises generated data will be created
and processed outside of data centers or Clouds by 2022.
Furthermore, they will be expecting
5 billion mobile internet users worldwide by 2025.
To deliver immersive experience and meet
requirements for low latency applications,
Azure is adding public MEC solution category
to the existing private MEC solution,
which was announced in June 2021.
Depending on your use cases,
the type of solution and deployment scenario you
can choose between these complementary solutions.
Private MEC enables operators
and integrators to quickly integrate
compute networking and first and third party services
on edge platforms in order to deploy at enterprise edge.
For more information about private MEC,
check out the Azure website.
There is a decision with focus on Azure Public MEC.
For enterprises and developers
wanting to run low latency applications by
harnessing the deep integration between
Azure compute and the mobile operator 5G connectivity.
Azure Public MEC is the right solution.
5G and edge computing integration will unlock
many new and exciting use cases in several verticals.
It will also help address
business challenges for many industries.
For example, the alcohol industry
requires reliable, scalable,
secure connectivity in order to support
mission critical functions for connected vehicles,
as well as rich in-vehicle experience.
There can be many cases in
safety through monitoring enhanced vehicle
telemetry all these
provided by the Public MEC.
With all current challenges created by the pandemic,
health care industry can benefit
from Azure Public MEC in several areas.
For remote patient care to remote clinical education and
new services or as
a pop up care and service
tailored to a specific communities.
Retail industry is going through
a big transformation to provide
the best experience for customers.
By using Azure Public MEC, retailers can provide
a personalized and fun shopping experience
for the customers and at the same time,
managing inventory and reducing cost.
Public infrastructure is an ideal case for public MEC.
With examples of
monitoring and management of critical infrastructure,
drones and emergency services in stadiums and venues can
also benefit by providing social
services at extremity of events,
immersive fun experiences or remote event production.
This technology will unlock not many new use cases,
it will benefit enterprises and customers.
Microsoft, as a Cloud provider,
has the most comprehensive and trusted Cloud.
Azure Public MEC will provide
Azure native infrastructure that will be
essential to enable and elevate
performance of latency sensitive applications.
This solution will offer new services with
immersive experiences at the edge
optimized connectivity to their 5G or LTE network.
Applications can now be
enabled using a new class of low latency,
highly reliable mobile networks and
edge computing technology running at
the network edge that allows to
analyze data closer to where it is captured.
With Azure Public MEC, we are
also bringing the power of Azure Automation,
leading security and developer experience to
the network edge so that enterprise customers can build,
manage and deploy their applications
anywhere they need using common tools.
Azure Public MEC is envisioned to
provide the best Cloud platform that will improve
efficiency and reduce cost by extending
Cloud solutions to the edge
using mobile operators 5G infrastructure.
Enhancing that user experience using network slicing
capabilities that allows to
distinguish traffic light use cases,
an ability to place applications on
demand closer to that users when they need it.
The goal of Azure Public MEC is to
power the organizations to build
the digital capability while ensuring
independence and sovereignty of the customer workloads,
leveraging the ecosystem of offerings for networking,
security and latency sensitive applications.
The solution enables key Azure
compute services like Virtual Machines,
Virtual Machine Scale set, Azure Kubernetes service,
networking services like Standard Load Balancers,
Virtual Network, Public IPs
running at these extended locations,
and more services would follow.
To enable our enterprise customers
to bring in their key scenarios,
we are partnering with many operators and ISVs.
Here you can see
a sample list of Azure Public MEC operators and
ISV partners.
Using the Azure portal
and leveraging the newly introduced user experience,
customers can deploy Azure services
at the Azure Public MEC's location.
Let me show you a demonstration of deployment of
an Azure Kubernetes service
at the Azure Public MEC location.
Using the Azure portal,
you can deploy an Azure Kubernetes cluster
at the Azure Public MEC location.
Once you log on to
the Azure portal with
your credentials and a subscription,
you are presented with
all the services that are available in Azure.
You pick the Azure Kubernetes Service.
Once you've picked Azure Kubernetes Service,
you can proceed to create a Kubernetes cluster.
For creation of the Kubernetes cluster,
you're presented with the next screen,
wherein you can choose
the location where you can deploy the cluster.
At the region locator,
you can see there's an additional option that we have
introduced or the See all Deployment Options.
Once you select the "See All Deployment options",
you are presented with the locations where you
can deploy the Kubernetes cluster at the edge.
In this screen as you can see,
I am choosing the ATT Atlanta A as
a location where I would be
deploying my Azure Kubernetes cluster.
Once you select the Atlanta A location,
the location gets populated at
the region locator where you can see
the exact place where you are going to
deploy the Kubernetes cluster in Azure Public MEC.
Next, you proceed to create the node pools.
For creating the node pools, you have
an option to add a node pool along with
the existing node pool that is added by
default as part of creating the Kubernetes cluster.
To add a node pool, you need to pick a node size.
To choose a node size,
you have to find the Virtual Machine size
that you want to use to create the additional node pool.
For example, here I have chosen
the standard B2s virtual machine
to create my additional node pool.
Once I have selected that,
you can proceed to go to the next step.
Next step is authentication.
In the authentication, you can keep all
of the default configurations that are presented to you.
Next, you proceed with the networking options.
In the networking options, the
default configurations always holds.
You can select any other options that you need
based on the requirements
that you have for your application.
Next, you proceed with the integration solution.
If you need to add anything,
any tags, you can proceed to do that.
After that, you can review
and create the Kubernetes cluster.
While reviewing, it runs some validation
to make sure all the parameters are correct.
After the validation has passed you can
select the Create a Kubernetes cluster,
then the deployment proceeds.
To step by step, you will
see how the deployment is progressing.
As the deployment progresses you can
see all other resources and the types and
the status of those resources that are being
created to deploy the Kubernetes cluster.
At the end of the deployment, you will be able to see
the status of all the resources that got created.
Once the resources are all
created your deployment is complete.
Now you can go to the resources.
Once you select "Go To the Resources", you can
see the Kubernetes cluster that has been created.
You are presented with the location
where this cluster was created as well.
Here you can see the Atlanta location
and your home region where you have the control then
and the details of the Kubernetes cluster
that has been created as well.
You can proceed to see
other options that are presented as part of the solution.
You can see the monitoring options,
any recommendations that are provided with Azure.
In this case, the resources are
following all of Azure's best practices.
You can proceed to see what are the different workloads
that got created as part of this service deployment.
You will also see the services and ingresses
options that got created as part of this deployment.
You can check to see what's
the health of the resource that you got created.
In this case, you see
the resources available and it is healthy.
Thank you for watching the video of an
Azure Public MEC and being
part of our journey as we bring Azure to the edge.
>> We are incredibly excited about our new solution,
Azure Public MEC and it's critical role in
the industry and the transformation
that is going to drive.
Microsoft and the telecom operators are bringing
this joint solution together to enable all key customers.
We are working hard to ensure you
can leverage Azure technologies
and services at the edge
with all the tools that you're familiar.
We have worked with our operator partners and
ISVs to build a full range of
capabilities that we can enable
to create the next generation enterprise solutions.
We like to invite you to sign up
and come to build with us and
experience how easy it is to build public MEC solutions.
[MUSIC]