Hello, and welcome to the Red Hat OpenStack certification preparation
training track. This is the first course of the track.
I am Bernd Bausch and will lead you on a journey through the
fascinating world of OpenStack.
You might be here because of headlines like these, which explain why
an IT professional might be interested in acquiring OpenStack skills.
LinkedIn considered cloud-computing skills the hottest in 2015.
As a cloud expert, your salary is growing.
This quotation doesn't say so, but salaries of cloud operators are
about 20% higher than those of Linux operators.
Finally, there is no shortage of open jobs for OpenStack experts,
as you can see.
What better way to prove that you are fit for OpenStack then by
showing a certificate, and not just any certificate.
Red Hat is by far the leading contributor to the OpenStack project,
and this training track prepares you for the Red Hat Certified System
Administrator in Red Hat OpenStack. What is the profile of somebody
aiming for this certificate? You should have an RHSCA-certificate or
equivalent Linux system administration skills, and you plan to extend
your career beyond Linux. Alternatively, you are an RHCE,
and work towards the Red Hat Architect certificate, which has RHCSA
OpenStack as one of its prerequisites. This course expects you to
have RHCSA skills, use the commandline with ease, and have no problems
operating Linux technologies like LVM, KVM, and libvirt, or networking.
You can find a description of this exam on the Red Hat website,
by searching for its number EX210. These are the skills enumerated on
the EX210 page. On the left, how to use OpenStack, in the middle,
how to operate it, and on the right, how to deploy and manage a Red
Hat OpenStack cloud with Red Hat's own tool named Director.
Thus, this course track has three matching parts.
As mentioned already, you are currently watching part 1.
To be precise, part 1 really consists of 2 courses separated at this point.
I will now show you how an OpenStack cloud can be used to build an application.
It will be a multi-tiered application. Before I enter the cloud,
allow me to explain what I mean. An application might consist of web
servers fronted by a load balancer, then application servers perhaps
on a separate network, and database servers again on a separate network.
So here we have three networks interconnected with routers,
and the first network is also routed to the world.
Note that to access this application from outside, we only need to
connect to the load balancer. All other servers require internal IP
addresses, but don't have to be accessed from the world.
To save time, I will start with a less elaborate application.
The deployment tool that I use to create the cloud has already
provisioned a router and the first tier network.
I will add a server to it, create the second tier network and its
router, and add a server to this network as well.