Welcome everyone, my name is Don
Pinto and I'm a technical product
marketing manager at Red Hat.
If you're wondering how to move your Red Hat
Enterprise Linux workloads to the cloud,
you have come to the right session
and today I'll discuss about moving
to none other than the Azure cloud
with Image Builder tool available
in Red Hat Enterprise Linux.
So let's get started.
Now, there are various reasons why
you may want to move to the cloud.
Sometimes it's just about reducing
the cost of your existing apps,
other times it may be just modernization
of your existing IT environment.
Whether you're building a new service,
modernizing an existing app,
running in containers,
or you're just an ISV,
you need a solid operating system
platform to standardize your workloads
across your deployment footprints.
Whether it's physical, virtual, private,
public clouds, or out to the edge.
With Red Hat Enterprise Linux,
you can standardize your workloads
in this hybrid cloud environment.
Simplicity,
consistency and repeatability are key
elements of the solution when it comes
to moving your workloads to the cloud.
In this journey.
Creating the image is the first step.
With red hats,
image builder technology,
you can build standardized images,
configure them,
and customize them as you want and
quickly deploy them in a variety of
cloud and virtualized environments.
Now you can also use REL image
Builder with other tools in
your environment like satellite.
Imagine building an image with
REL image builder and then using
satellite to provision it across
multiple hosts at scale.
You can also use Ansible to automate
your journey through the Deployement
maintenance upgrade or retirement
phases and with Red Hat Insights
that is included with every run
subscription you can get deeper.
Identify and remediate risks.
Across security compliance and
configuration areas based on
Red Hat's best practices,
the image builder depends on multiple
key concepts and in this slide will
talk about image types and blueprints.
Image types are outputs of the image builder.
2.
In this case,
we support a variety of different
cloud and virtualized environments,
and for this session the Azure disk image
or the VHD format is of great importance.
We also have blueprints
that provide customizations,
including setting up users which
packages to use with services to run,
and so forth.
Now, if you're running in edge scenarios,
Red Hat image Builder can also help.
With Red Hat image builder.
You can generate purpose built
images for these environments.
We use a technology called Green Boot
that is able to generate OS 3 RPM images.
This effectively means couple of things.
Number one you can get started within
minutes using built-in defaults.
#2 you can get atomic updates and
rollback capabilities if things go wrong,
which is very crucial for
edge environments #3.
If edge environments are running
in low bandwidth scenarios,
you can get optimized over the air updates.
And #4.
It's designed for containerized edge
environments so that you can quickly
spin up containers when needed to scale.
So in the next few minutes,
let's go over a demo.
So that you can see in action Red Hat
image Builder and how you can build
images that are customized as per your
requirement and push them to none
other than the Microsoft Azure Cloud.
When it comes to moving workloads
to the cloud, simplicity,
consistency and repeatability are
the key elements of your solution.
The first steps in this wonderful journey
to the cloud is to create an image.
With the image builder technology
in Red Hat Enterprise Linux,
you can have a standardized way to
configure and create custom images.
And quickly deploy them in the
cloud environments of your choice.
Let me show you today how you can do that.
With RELS image filter technology.
Anne. Microsoft Azure cloud.
So what you can see on the screen here is.
The rail web console.
For those of you not familiar with console.
It is an easy to use web based tool.
So that any System Administrator can quickly.
Take a look at what's going on in the system.
From help to usage metrics to
general system information,
the Web console is your friend.
So let's. Talk about image Builder
more and you can see on the left
menu year under apps is we can see
that we have an image builder item,
so let's select that.
There are multiple concepts
related to image builder,
but it all starts with creating a blueprint.
A blueprint is like a template.
Providing customization packages
that you could pick from to
create to include in your image
as well as image output formats.
In this case,
I have a way simple customization
to create a user called ZZ test.
In terms of packages,
I've also selected just a single package.
the Apache web server package.
However, you can choose to add
more packages. If you wish.
By typing in the name of the package,
version number or release. Finally.
You need to tell Image Builder.
What is the output format of your images?
But before we do that?
Let's quickly look at the setup
in the Microsoft Azure portal.
So here you can see that I'm
in the Microsoft Azure portal.
I've logged in.
And I have a subscription.
Associated to my account,
which is my Azure self.
I also have a storage account which
is associated with the subscription.
In this case my Image Store 1.
And inside this my Image
Store 1 storage account.
I have a container. Which I've called.
My image container one.
So those are some of the
things that we will need.
In the next step.
To input in the REL web console.
We also see on the left that we
have something called access keys.
These are keys that allow you to
access your particular storage account.
So I'm going to hit show keys to
reveal the keys that I need to use.
So that relative image builder
can write the output image into
this particular storage account.
So I'm going to copy that over.
Let's go back. 2. RELS image builder.
I'm going to select the output
image format in this case
to be the Azure disk image.
Gonna tell Image Builder to
upload the image to Azure.
Bono give it? The access key that I copied.
And I'm going to give it the
name of my storage account.
Just my image store 1.
Next time I want to give it the
name of the image that I want to
write into the Azure container.
And also tell it the name
of my storage container.
So now that I've input all this
information. I'm going to hit finish
and let Image Builder do its job.
You can see that.
The image builder in REL has
added the image creation.
An image upload to a queue.
And the job to build the image
and upload the image has started.
Now that the image is
getting built and uploaded.
Let us explore a few more things
inside the rail web console.
A good place to start is to look
at system Overview section again.
Will dig a little bit more
into the usage browse.
What you can see here is.
How I'm utilizing?
The four CPUs that I have on the system.
Memory and swap memory.
Disk IO as well as network.
The network section is very
interesting in this case because
as images are getting pushed
to the cloud you should see.
A few more spikes in the network traffic.
Let's come back to the web console
in a few more minutes after the
image is push to the cloud.
And so welcome back.
Back at inside the REL web
console and we can see that
the image build and the image
upload task has been completed.
Let's actually go and verify that.
In the Azure portal.
So again, you're inside the my image store,
one which is our storage account in Azure.
Ann again, within that I have a container
which is called my image container one.
So let us go and explore that
container and what we can see in this
case is we have the VHD image file,
my image one which is now available.
Inside this container.
By clicking on. The image.
Inside the image container we can get
a few more details about the image.
One of the most interesting
attribute is the URL.
Off the image in the Blob store.
So we're going to copy that over,
and we're going to show how we can
spin up a virtual machine in Azure.
From this particular image that
was pushed into the Azure cloud.
And for that I'm going to switch back to.
The real machine.
And we'll explore the Azure CLI.
So. What I've done here is
I've already installed.
The Azure CLI tools for Linux.
In this case it's running. Unreal.
And so the first command that I'm going
to show you is the easy login command.
And so this command essentially. Uses.
The CLI to basically login to Azure.
So let's try to do that.
You'll see that it opens a browser window.
You might have to pick your account here.
And once you have successfully
logged into Azure,
you can return back to the console.
So in this case you can see
that I'm back to the console.
It's kind of telling me a bunch of different
details associated with my account.
I'm also going to tell of my subscriptions
that I applied to this particular account,
so for that you can see you can
use the Etsy Account List command
and output it in the form of a
nice nicely formatted table.
So you can see that I have two subscriptions.
But in this case,
be using the my Azure subscription.
And this particular subscription has a
unique subscription ID that is associated
with this particular subscription,
so we're going to use that subscription
ID in the next CLI command.
So I'm going to again set a
particular subscription ID.
If you have multiple subscriptions,
you might want to use this
command to pick a particular
subscription to go against.
So in this case I'm going to
use the subscription ID tide
to my my Azure subscription.
And I'll. Data set.
What I'm going to do next is.
Show you the command to
basically get a VM based on.
The image that we already had uploaded.
So in this case it is the ASDM create
command we're telling it to create
an image with a particular name,
particular resource group and go with that.
So let's run this particular command.
And So what you'll see here is
this command has started running.
It will go over the network to create
a new virtual machine with the image
that we just pushed into Azure.
You can look at go back to home and
try to look at virtual machines.
You may not immediately see
a virtual machine up.
In this case, yes it is.
It's already up there and
this particular VM is created.
An is is running with that particular
disk image that we had uploaded.
Let's again go back to our console.
You kind of see that and you can see
that that VM is now up and running.
With the disk image.
So I hope you enjoyed this demo of how to.
Build.
A new image that is customized
to meet your use case is push the
image to a cloud environment.
In this case the Microsoft Azure Cloud,
thank you.