Oracle VM management: Managing Server Pool

A Server Pool is logically an autonomous region that contains one or more physical servers and the dynamic nature of such pool and pools of pools makes what we call an infinite Cloud infrastructure.

Currently Oracle has its Cloud portal with Amazon but it is very much viable to have an IntraCloud portal or private Cloud where we can run all sorts of Linux and Windows flavors on our Cloud backbone. It eventually rests on the array of SAN, NAS, or other next generation storage substrate on which the VMs reside.

We must ensure that we have the following prerequisites properly checked before creating the Virtual Machines on our IntraCloud Oracle VM.

• Oracle VM Servers: These are available to deploy as Utility Master, Server Master pool, and Virtual Machine Servers.
• Repositories: Used for Live Migration or Hot Migration of the VMs and for local storage on the Oracle VM Servers.
• FQDN/IP address of Oracle VM Servers: It is better to have the Oracle VM Servers known as OracleVM01.AVASTU.COM and OracleVM02.AVASTU. COM. This way you don't have to bother about the IP changes or infrastructural relocation of the IntraCloud to another location.
• Oracle VM Agent passwords: Needed to access the Oracle VM Servers.

Let's now go about exploring the designing process of the Oracle VM. Then we will do the following systematically:

• Creating the Server Pool
• Editing Server Pool information
• Search and retrieval within Server Pool
• Restoring Server Pool
• Enabling HA
• Deleting a Server Pool

However, we can carry out these actions only as a Manager or an Administrator. But first let's take a look at the decisions on what type of Server Pools will suit us the best and what the architectural considerations could be around building your Oracle VM farm.