Hello, I'm Dean Campiglio. Welcome to cyber ery or working with virtualization installation configuration management tasks. Our next lesson is less and five from module seven, where we're going to be exploring some of the features and capabilities of the V app.
So we'll describe what Avi Up is,
how you go about building of the app
and then ability to manage your virtual machines by using a Viet.
Then we'll follow that up with doing Lab 13
so effectively. Avi App gives you a new object in your inventory. It's a different looking icon.
It looks a little bit like
Indra. Exactly right. But close to that
and what this provides you is a container for
managing multiple be EMS as a unit.
This is important because it allows you to deal with multi tiered applications. Your Web server, your application server, a database server, for instance. You could bundle all those together as one of'em
the fact that all of that is together and manages one unit gives you a lot of advantages. It means it's much more portable.
It's easier to deploy to multiple locations,
and you could enforce dependencies that those three applications are that those three v EMS I mentioned might have with each other.
Maybe your database server has to come up first,
Web server, then the application server. You can set up a boot delays and different things in order to facilitate those dependencies.
The AP's come in two different formats. We have the ovf format, open virtualization
or open virtualization appliance O V. A format.
And as you'll see in the lab, it's very easy to
create a V M on your own. You don't need to pick one that's already prepackaged, although plenty of
third party vendors create the APS
that provides some functionality, maybe a firewall in proxy combination or something of that nature,
but very easy to create one in the inventory directly,
so some of the characteristics to think about
when we create a B F. We have ah CP with memory allocation,
so you can do this as a as a as one unit, as it's an aggregate value if you will,
and you also have to think about how you're going to allocate your I P addresses.
These could either be fixed
where you designate them manually. You configure them annually,
or you can make them transient,
where we've got a pool of addresses that are available to be app
and they get chosen when the when the Viet boots up
when it boots. At some point in the future, it may get different addresses
from that same pool.
It just depends on how you have that configured,
and your last option is to use plain old D A C P,
which gives an address based on the pools that are available to your organization as a whole or on that particular network as a whole.
There are some advanced settings
you can look at when you're investigating the Viet Properties. You can see the product and vendor info in the case of, ah, buying or getting an appliance and more of those two formats.
And then we also have any custom properties that are related to the way the VM is configured or its functionality. And then, lastly, the I P allocation scheme that we would pick from these three choices. Okay, so lab 13 you'll be creating a V app powering it on and then removing it from the inventory.
Thank you, Becca. Who's lesson