(upbeat music)
Hi, everyone.
My name is Kyle.
I'm a Product Major here at Microsoft on the Azure team.
Today, I'm going to walk you through something super cool,
a much easier way of setting up Arc VM Management
on your address stack share cluster.
So here's the plot for today.
First, I'll kick things off with a quick rundown
of what Arc VM Management is all about.
Then we'll dive into some of the hurdles
that might come across when setting it up.
But don't sweat because I'm going to introduce you
with a fresh approach to take to get Arc VM Management
up and running and last but not the least,
we will jump right into a quick demo.
Without further ado, let's get started.
The Arc VM Management is a powerful tool
that lets you provision and manage VMs hosted
in your on-prem HCI environment,
and helps to control your VMs
through a single pair of glass, Azure portal.
It also provides Azure services
such as Azure Monitoring, Defender, and so forth.
As we can see on diagram where Azure sits in the top
and your Edge Location at the bottom,
let's envision a scenario where you possess
a formal HJ cluster hosting all your on-prem VMs.
The question becomes, how can we seamlessly connect this
to Azure and leverage the power of Azure services?
This is where our VM management setup steps comes into play.
By initiating the steps, you will introduce a few components
to your cluster including the arch resource bridge VM
positioned on wifi nodes.
This arch resource bridge function as a crucial connector
projecting your on-prem VMs and all their resources
onto Azure and the result are empowered
seamless management of your VMs directly from Azure
releasing a new level control and optimization.
The execution set process can be somewhere daunting
and involve with multiple steps such as installing
modules and packages, installing Moc,
deploy the arc resource bridge,
installing Kubermetes extensions for the VM operator,
and creating custom location.
As a processor requires executing more than 20 commands
and inputing more than 10 parameters,
thereby increasing the chances of user errors.
Moreover, in even though fail deployment,
the responsibility currently lies with the users
to mainly clean up their environment.
This extent you mainly collecting logs for diagnosing
and addressing any issues, adding another layer
of complexity to the user experience.
In essence, we recognize that the current setup process
can be labor intensive and potentially
challenging our customers.
This is why we're going to present you with a much easier
way of setting this whole thing up.
Now I'm thrilled to introduce to you this new way
of setting up Arc VM management slated for launch
this coming June.
This new approach revolutionizes the setup experience,
drastically reducing complexity
and enhance user friendliness.
Where previously user had to navigate
through over 20 commands, this new setup bring it down
to just two.
The requirement for input parameters has also been
significantly reduced from over 10 to just two
for dhtp configuration and five
for static epic configuration.
Moreover, we've taken step to lift the responsibility
from our users for certain tasks that
were previously manual with automated pre-checks to ensure
reliability in the event of a field deployment
and auto cleanup will kick in, clean the environment
without your intervention.
This new set of process signifies our commitment
to enhance user experience, reducing complexity
emphasizing a smoother, more efficient path to benefit
Arc VM management.
So now let's do a quick demo on the installation
of the Arc VM management.
The installation process requiring just two commands:
install ARC HCM Moc and install arch HDM management.
This one, install Moc AQ management,
a property extension and creating customer location.
Both install commands will automatically run pre-checks
and prevent installation if pre-checks fail.
The pre-check commands can also be run separately
before running the install commands
and these commands are test arc hta nimble Moc
and test arc hcm enable management.
So let's start by looking at the pre-checks that's been
added to the install process test
as well as the install arc. HTA Moc take one parameter,
which is the volume path.
So these are the pre-checks that are run.
We have four different pre-checks here.
We check the partial modules that are require are installed,
if the cluster is healthy,
if the specific volume is available.
We also check that it require Hyper V feature
and the cluster reset is valid.
So if we try install a HTM management right now
it should fail because Moc has not even installed
and this is one of the required pre-checks
for install aqc management.
So let's go ahead and run the command.
As we can see the install aqc management
towards an error because Moc is not even installed.
Now let's go ahead and install Moc.
Moc is only set of pre-checks that are running addition
to the pre-checks that we added earlier.
In order to verify the Moc being installed
we can run get ARC HT Moc to the Moc configuration.
Now that Moc has been installed,
we can move on to the ARC V management installation.
The only required parameters for install aqt
management command are the virtual switch name
and the controlling IP address.
A start and end IP addresses are required
in the case of static IP configuration.
So let's finish the install process by running install
ARC HCM management with value parameters.
Something to note here is that both install RTM Moc
and RTC management come with an option to skip rechecks.
Please bear in mind that the entire install
commands take around 20 minutes to complete.
We can verify that RQ CM Management has been installed
by running get R HCM management.
In addition, we can also run get VM to see
that arc applies VM is not running and that's it.
Here are the links for the Rqm management public
documentation and please keep in mind that the new way
of setting this up is coming in June.
Also, please stay tuned for the latest update.
(upbeat music)
That's all for the session.
I hope you enjoyed and thank you for your time.
(upbeat music)