| Oracle® Enterprise Manager Cloud Administration Guide 12c Release 2 (12.1.0.2) Part Number E28814-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Cloud Administration Guide 12c Release 2 (12.1.0.2) Part Number E28814-03 |
|
|
PDF · Mobi · ePub |
This chapter describes the monitoring and administrative tasks that you can perform on the zones, virtual server pools, virtual servers and guest virtual machines. It includes the following sections:
The Cloud target is available out of the box and represents the entire virtualization infrastructure monitored by Enterprise Manager Cloud Control. You can view and monitor the various targets in the data center from the Infrastructure Cloud Home page. To view the Infrastructure Cloud Home page, follow these steps:
From the Enterprise menu, select Infrastructure Cloud, then select Home. The Infrastructure Cloud Home page shows the various targets such as zones, pools, and virtual servers, request status, policies, and so on. Click the video link to view a demo on setting up the cloud infrastructure.
The Infrastructure Cloud Home page shows the following details:
General: Shows the number of OVM Managers, zones, and servers, and guest virtual machines in the cloud and the status of each target. Select a link to drill down to the Members page.
Target Flux: Shows the number of guest virtual machines created and deleted over the last 30 days.
Request Status: Shows the status of various requests and reservations. Check the Only SSA Requests check box to view only the Self Service Application Requests. Click the graph to drill down to the Requests page.
CPU & Memory: Shows the CPU and memory utilization by the virtual servers in the data center.
Software Library: Shows the number of assemblies and templates available in the software library and how many have been deployed.
Policy: Shows the status of the various policies that have been defined for the cloud. It shows the number of corrective actions that were executed and whether they were successful. Click the graph to drill down to the Policy Home page.
Overview of Incidents and Problems: Shows the various incidents and policy violations that have occurred in the last 24 hours.
Resources: For each entity in the cloud you can view the total storage used, number of network profiles and VLAN groups. Click the Network or Storage link to drill down to the Network or Storage page of the corresponding OVM Manager target.
Charge Trend: Shows the charge back break-up data across the cloud. It lists the top 5 requests that have incurred the highest cost.
Inventory and Usage: Shows the inventory summaries for virtual servers, guest virtual machines, and assembly instances. Select an option from the Show drop down list to view the details. You can view the summary information in the context of different dimensions. For example, for Oracle VM Servers, you can view the number of virtual servers under each Oracle VM Manager, zone, virtual server pool, and so on.
Click on the bar charts to drill down multiple levels of inventory details. Click See Details to drill down to the Inventory and Usage Details page which provides detailed information on the selected target and associated inventory charts.
Before you can start monitoring a virtualization target, you must register the OVM Manager target. See Registering the Oracle VM Manager for details.
The OVM Manager provides the interface to monitor zones, virtual servers, virtual server pools, and guest virtual machines. A zone is a set of virtual server pools. Each virtual server pool contains one or more virtual servers and guest virtual machines. A virtual server pool cannot belong to more than one zone. To view the OVM Manager Home page, follow these steps:
From the Enterprise menu, select Infrastructure Cloud, then select Home.
Click on an OVM Manager target from the left panel. The OVM Manager Home page shows the following details:
General: Shows the number of zones, and servers, and guest virtual machines under the OVM Manager and the status of each target. Click on a link to drill down to the Members page.
Request Status: Shows the status of all requests for this OVM Manager. Click on the graph to drill down to the All Requests page.
Job Activity: Shows the list of jobs started within the last 7 days.
Policy: Shows the status of all the policies that have been defined for the OVM Manager. It shows the number of corrective actions that were executed and whether they were successful.
Overview of Incidents and Problems: Shows all the incidents and problems reported on the OVM Manager and member targets.
Inventory and Usage: Shows the inventory summaries for virtual servers, guest virtual machines, and assembly instances. Select an option from the Show drop down list to view the details. You can view the summary information in the context of different dimensions. For example, for Oracle VM Servers, you can view the number of virtual servers under each Oracle VM Manager, zone, virtual server pool, and so on.
Click on the bar charts to drill down multiple levels of inventory details. Click See Details to drill down to the Inventory and Usage Details page which provides detailed information on the selected target and associated inventory charts.
CPU & Memory: Shows the CPU and memory utilization by the virtual servers under the OVM Manager.
Software Library: Shows the templates and assemblies that have been deployed.
Charge Trend: Top 5 Tenants: Shows the charge back break-up data across the OVM Manager. It lists the top 5 requests that have incurred the highest cost.
From the OVM Manager Home page, you can do the following:
Edit OVM Manager
Synchronize OVM Manager
Deregister OVM Manager
Create a Zone
Create a Virtual Server Pool
Discover a Virtual Server
Manage Unowned Virtual Server
Manage Networks
Manage Storage
Manage Storage Repository
You can view and manage members for one or more virtualization targets on this page.
From the Enterprise menu select Cloud, then select Infrastructure Home.
Right click on the Infrastructure Home menu, select Members, then select Show All.
The list of OVM Managers, Zones, Virtual Server Pools, Virtual Servers, and Guest Virtual Machines that can be managed from the Infrastructure Cloud appear.
You can:
Click on a target to drill down to its Home page.
Select a target and click on an option from the Actions menu. The actions you can perform vary based on the target you have selected.
Note:
You can view and manage the members under a OVM Manager target, zone, virtual server pool, or virtual server. From the Infrastructure Cloud Home page, select the appropriate target (such as an OVM Manager, zone, virtual server pool, or virtual server) from the left panel. From the Infrastructure Cloud menu, select Members, then select Show All. The Members page for the selected target appears and you can perform various administrative activities on these targets.This section describes the following:
A zone is a collection of virtual server pools which share storage. It is a logical entity used to organize the guest virtual machines exposed to the self service application user. Zones have metrics that show the aggregate utilization of the zone. To view the Zone Home page, follow these steps:
From the Enterprise menu select Cloud, then select Infrastructure Home. In the left panel, click on the zone to be viewed. the The following details are displayed:
General: Shows the number of virtual servers, virtual server pools, and guest virtual machines under this zone and the status of each target. Click on a link to drill down to the Members page.
Job Activity: Shows the list of jobs started within the last 7 days.
Overview of Incidents and Problems: Shows all the incidents and problems reported on the OVM Manager and member targets.
Members: This region shows the status and other details of each virtual server pool, virtual server and guest virtual machines in the zone. Click on a link to drill down to the Members page. Select a target and click on an option from the Actions menu. The actions you can perform vary based on the target you have selected.
CPU and Memory Usage Trending: Shows the average CPU and memory utilization over the last 30 days.
CPU and Memory: Shows the CPU and memory utilization by the virtual servers and guest virtual machines in this zone.
A zone is a collection of virtual server pools which share storage. Follow these steps to create a zone:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select the OVM Manager target for which the zone is to be created, and click Create Zone from the OVM Manager menu.
In the Create Zone page, specify the zone name and description.
Indicate if this zone will be used by the self service users by checking the Cloud Self Service Zone check box.
Click Add in the Virtual Server Pool section to add one or more virtual server pools. See Creating a Virtual Server Pool for details.
Click Create Zone. The virtual server pools appear in the newly created zone on the Virtualization Central Home page.
Note:
To edit an existing zone, follow these steps:From the Enterprise menu, select Infrastructure Cloud, then select Home.
Select a zone target from the left panel.
From the Zone menu, select Target Setup, then select Edit VM Zone.
To delete a zone, follow these steps:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Click on a zone target from the left panel to navigate to the Zone Home page. From the Zone menu, select Target Setup, then select Remove Target. A confirmation message appears.
Click OK to delete the zone. Any virtual server pools that are members of this zone will now be moved under the OVM Manager target.
Note:
If Chargeback has been enabled for the zone (or virtual server pools / guest virtual machines within the zone) being deleted, the metric data is automatically disabled when the target is deleted.A virtual server pool is logically an autonomous region that contains one, or more virtual servers. A virtual server pool may or may not belong to a zone. However, it can belong to only one zone at a time. The following details are displayed:
General: Shows details of the virtual server pool such as the zone to which it belongs, the number of CPUs, memory and storage, and number of NICs.
Job Activity: Shows the list of jobs started within the last 7 days.
Issues: Shows all the incidents and problems reported on the virtual server pool and member targets.
Members: This region shows the status and other details of each virtual server and guest virtual machines belonging to the virtual server pool. Click on a link to drill down to the Members page. Select a target and click on an option from the Actions menu. The actions you can perform vary based on the target you have selected.
CPU and Memory Usage Trends: Shows the average CPU and memory utilization by the virtual servers in the zone over the last 30 days.
CPU and Memory Utilization: These charts show the CPU and memory utilization by all the virtual servers in the server pool.
This section describes the following:
A virtual server is a generic term used to describe a physical machine which has virtualization software (hypervisor) running on it. A virtual server can belong to one and only one virtual server pool at a time. Guest virtual machines and resources are also associated with the server pools.
The following regions are displayed:
General: Shows details of the virtual server such as the virtual server pool it belongs to, whether the server needs to be upgraded, if it is under maintenance, and so on.
Job Activity: Shows the list of jobs started within the last 7 days.
Configuration: The virtual server configuration such as number of enabled CPU cores and processors, memory, diskspace, OVS Agent Port, and so on.
Disk Activity: The disk throughput of the virtual server.
Members: This region shows the status and other details of all the guest virtual machines. Click on a link to drill down to the Members page. Select a target, click Guest VMs from the Actions menu. Select the action to be performed on the Guest VM.
CPU Utilization: The CPU utilization of the virtual server.
Disk Utilization: The disk utilization of the virtual server.
Network Activity: The network throughput of the virtual server.
Incident Summary: This region shows a list of incidents and problems reported on all the Guest VMs and related targets.
To edit a virtual server, follow these steps:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
In the left panel, select the virtual sever that is to be edited. The Virtual Server Home page appears.
From the Virtual Server menu, select Target Setup, then select Edit Virtual Server.
In the Edit Virtual Server page, you can modify the Description of the virtual server.
Select the Configure Server IPMI checkbox to enable the Intelligent Platform Management Interface (IPMI). Selecting this option allows you to remotely power off a virtual server and send a wake on lan message to power on a virtual server without having to physically press the power button. If this checkbox is selected, you must enter the user name, password, and IP address of the IPMI.
Click OK to confirm the changes.
After the YUM Repository has been set up (see Configuring the YUM Repository), you must upgrade the virtual server to ensure that it has the latest updates. The virtual server must be in maintenance mode if it is to be upgraded.
To upgrade the virtual server, follow these steps:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a VM Server from the left panel and select Upgrade.
After the virtual server has been upgraded, the virtual server will be restarted.
You can start a virtual server that is in a Stopped state. To start a virtual server, follow these steps:
Note:
Before you start the virtual server, you must ensure that the IPMI has been configured. See Editing a Virtual Server.From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a virtual server target in the left panel and select Start. A confirmation message appears.
Click OK to start the virtual server.
You can stop a virtual server that is Up. To stop a virtual server, follow these steps:
Login to Enterprise Manager Cloud Control.
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a virtual server target in the left panel and select Stop. A confirmation message appears.
Click OK to stop the virtual server.
You can place a virtual server in maintenance mode to perform hardware and software maintenance. When a virtual server is placed in maintenance mode, any virtual machines running on the virtual server are automatically migrated to other virtual servers in the server pool, if they are available, otherwise they are stopped. The server pool roles being performed by the virtual server are also moved to other virtual servers in the server pool, if available.To place an Oracle VM Server into maintenance mode:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select a virtual server target from left panel.
Right click on a virtual server target from the left panel and select the Start Maintenance. The virtual server target is placed in blackout mode during maintenance.
When you have finished performing maintenance, click Stop Maintenance for it to rejoin the server pool.
This section describes the following:
A guest virtual machine runs on a virtual server. You can create a guest virtual machine by using one of the following methods:
Assemblies
Templates
Installation Media (ISO or PXE)
For more details on creating a Guest VMs, see Deploying Guest Virtual Machines.
Before you create a guest virtual machine, you must have:
Discovered a virtual server.
Created a virtual server pool.
Created the necessary components in the Software Library
Deployed assemblies, templates, ISO images, or PXEs for creating virtual machines based on these.
A guest virtual machine is the container running on top of a virtual server. Multiple guest virtual machines can run on a single virtual server. The following regions are displayed:
General: Shows details of the guest virtual machine such as the virtual server pool, and virtual server it belongs to, and a description.
Job Activity: Shows the list of jobs started within the last 7 days.
CPU and Memory Utilization: The CPU and memory utilization of the guest virtual machine.
Disk Utilization: The disk utilization of the guest virtual machine.
Networks and Network Activity: The networks in the guest virtual machine and the network throughput of the guest virtual machine.
Configuration: The virtual server configuration such as number of virtual CPUs, CPU priority, allocated storage and memory, whether it is HA enabled, and the domain type.
Incidents Summary: Shows the various alerts and policy violations that have occurred in the last 31 days.
From the Guest Virtual Machine Home page, you can do the following:
Edit a Guest VM
Live Migrate a Guest VM
Clone a Guest VM
Start and Stop
Reboot, Restart, Suspend, and Resume
To live migrate one or more guest virtual machines, do the following
From the Enterprise menu, select Cloud, then select Infrastructure Home.
From the Infrastructure Cloud menu, select Members, then select Show All.
Expand the list of targets displayed and select one or more guest virtual machines from the list.
Right click the selection and select Live Migrate. The guest virtual machines to be migrated must be in the Running state.
Check the Manual check box to select a virtual server to which the guest virtual machine is to be migrated. If you do not select this check box, the system will pick up a suitable virtual server from the server pool for the guest virtual machine live migration.
Click Submit to live migrate the guest virtual machine.
After a guest virtual machine has been created, you can start it or shut it down. When a guest virtual machine is running, you can pause or suspend it temporarily:
When a Guest VM has not been used for a while, it may be shut down to release system resources. To use the Guest VM, you must start it:
Prerequisites
The guest virtual machine must be Down.
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select the guest virtual machine target from the left panel.
Click Start from the guest virtual machine menu.
You may need to reboot or restart a virtual machine if operating system updates require you to restart the virtual machine, for example Microsoft Windows updates. To reboot a guest virtual machine:
Prerequisites
The guest virtual machine must be Up.
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a guest virtual machine target from the left panel and click Restart.
You may need to stop a Guest VM that is not being used to release system resources.
Prerequisites
The guest virtual machine must be Up.
To stop a guest virtual machine:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a guest virtual machine target from the left panel and click Stop.
Prerequisites
At least one virtual machine must exist and be in a state appropriate for cloning to proceed.
You can clone a guest virtual machine to create one or more new virtual machines in the same server pool.
Note:
If you are using the Enterprise Manager for Oracle Virtualization 12.1.0.3 plug-in, you can clone running guest virtual machines if the virtual disks associated with them are thin cloneable.To clone a guest virtual machine, follow these steps:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select a guest virtual machine target from the left panel.
Click Clone from the guest virtual machine menu.
In the Select Target and Source page, specify the following:
Destination target on which the guest virtual machine is to be deployed.
Source guest virtual machine that it is to be cloned.
In the Deployment Configuration page, you can modify the following:
Guest VM:
Number of Guest VMs: The number of guest virtual machine instances being cloned.
Guest VM Naming: Indicates whether the guest virtual machine names are to be automatically generated or if the names will be uploaded from a file.
Guest VM Name: Enter a name of the guest virtual machine being cloned.
General :
Enable High Availability / Start VM After Creation: Select the Enable High Availability and Start VM After Creation checkboxes to restart the guest virtual machine automatically after any outage.
CPU Scheduling Priority: Set the Priority of the virtual machine. You can select a high, medium, low, or custom priority for the virtual CPUs.
CPU Scheduling CAP: This parameter defines the percentage to which the virtual CPUs can receive scheduled time. You can select a high, medium, low, or a custom percentage of scheduled time for the virtual CPUs.
Keymap: The keyboard mapping that will be used by the guest virtual machine being cloned.
VM Size
VM Size: The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started. The size of the guest virtual machine (memory and CPU values).
Memory: Specify the memory allocated to guest virtual machine. For a running guest virtual machine, this can be increased up to the Max Memory.
CPU Cores: Specify the number of virtual CPUs for the guest virtual machine. For a running guest virtual machine, this can be increased upto the Max virtual CPU.
NIC Configuration: You can add or delete virtual network interfaces. For more details, see Setting Up Networks.
Disk Configuration: Specify the storage type. You can use the Default type as specified by the server pool or select Override. If you select Override, you must specify the Storage QoS and click the Search icon in the Storage field to specify the Storage Type. In the Storage Type window, specify the following:
Clone Target Type: This can be Repository or Storage Array.
Clone Target: If you select Repository, select the storage location where the disk is to be created. If you select Storage Array, specify the type, which can be SAN or ISCSI storage server.
Clone Type: This can be Sparse or Non-Sparse Copy. A sparse copy is a disk image file of a physical disk, taking up only the amount of space actually in use; not the full specified disk size. A non-sparse copy is a disk image file of a physical disk, taking up the space equivalent to the full specified disk size, including empty blocks.
Click Next to continue.
On the Schedule page, specify whether the guest virtual machine is to be cloned immediately or later. Click Next.
On the Review page, review the configuration details and click Submit to run the cloning procedure.
Note:
If you edit a guest virtual machine that is Up, you cannot modify the server size, storage and network fields. To edit these values, you must stop or halt the guest virtual machine.
You can create a new disk for a guest virtual machine which is Down, if Oracle VM Manager 3.1.1 and Enterprise Manager for Oracle Virtualization 12.1.0.2 plug-in have been installed. In other cases, existing disks are attached to the guest virtual machines.
To modify the configuration of a guest virtual machine, follow these steps:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select a guest virtual machine target from the left panel. From the Guest VM menu, select Target Setup, then select Edit VM Guest. The Guest VM Configuration page appears.
You can modify the following details:
Hardware Configuration (General):
VM Size: The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started. The size of the guest virtual machine (memory and CPU values).
Memory: Specify the memory allocated to guest virtual machine. For a running guest virtual machine, this can be increased upto the Max Memory.
CPU Cores: Specify the number of virtual CPUs for the guest virtual machine. For a running guest virtual machine, this can be increased upto the Max virtual CPU.
CPU Scheduling Priority: Set the Priority of the virtual machine. You can select a high, medium, low, or custom priority for the virtual CPUs.
CPU Scheduling CAP: This parameter defines the percentage to which the virtual CPUs can receive scheduled time. You can select a high, medium, low, or a custom percentage of scheduled time for the virtual CPUs.
Hardware Configuration (Network): You can add delete virtual network interfaces. For more details, see Setting Up Networks.
Hardware Configuration (Storage):
Select the desired storage configuration of your virtual machine, such as virtual disks and ISO file.
Other Configuration (Attribute): You can set the basic attributes of the guest virtual machine such as the description and the type of operating system to be used.
Other Configuration (High Availability): If the High Availability checkbox is selected, the guest virtual machine will automatically restart after any outage.
Other Configuration (Boot Sequence): Specify the boot sequence for the guest virtual machine. This is the boot order for the guest virtual machine and indicates if the guest virtual machine is forced to boot from disk, CDROM, or network.
Other Configuration (Advanced):
Keymap Name: The name of the keyboard mapping that will be used by the guest virtual machine.
Mouse Type: The mouse type to be used for the guest virtual machine. This can be Default, PS2 Mouse, USB Mouse, or USB Tablet.
Domain Type: The domain type of the virtual machine. This can be:
Xen HVM: Hardware virtualization, or fully virtualized. When you select this option you must supply an ISO file in a repository (in the Create Storage step of the wizard) from which to create the virtual machine.
Xen HVM, PV Drivers: Identical to Xen HVM, but with additional paravirtualized drivers for improved performance of the virtual machine. This Domain Type is used to run Microsoft Windows guest operating systems with an acceptable performance level.
Xen PVM: Enables you to select a location for the mounted ISO file from which to create the virtual machine. Before you create the virtual machine using the paravirtualized method, mount the ISO file on an NFS share, or HTTP or FTP server. You supply the location of the mounted ISO file in the Network Boot Path field in the Boot Options step of the wizard.
OVM/SPARC: This domain type should be selected if the server pool and hypervisors use Oracle VM Server for SPARC as the hypervisor instead of Oracle VM Server for x86.
Unknown: This hypervisor should be selected if the domain type is unknown.
You can save a guest virtual machine as a template and use the template for provisioning guest virtual machines.
To save a guest virtual machine as a template, follow these steps:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select a Guest VM target from the left panel. From the Guest VM menu, select Target Setup, then select Save Guest VM as a Template. The Save Guest VM as Template: Select Target and Source page appears.
The name of the guest virtual machine target that is to be saved as template is displayed.
In the Target Repository field, select the repository on which the guest virtual machine template is to be stored.
Specify a name for the template and click Next.
In the Save Guest VM as Template: Deployment Configuration page, you can modify the following details:
General Configuration:
Memory and No. of CPU Cores: Specify the Memory and No of CPU Cores (virtual CPUs) for the virtual machine. The number of processors is expressed in number of physical CPU cores, and is limited to 32. The memory and the number of processors that you can select is limited to the properties of the Virtual Machine Server. If you do not select a Virtual Machine Server however, you can set your desired value. You can modify the Max Virtual CPUs and Max Memory fields without restarting the Guest VM.
CPU Scheduling Priority: Set the Priority of the virtual machine. You can select a high, medium, low, or custom priority for the virtual CPUs.
CPU Scheduling CAP: This parameter defines the percentage to which the virtual CPUs can receive scheduled time. You can select a high, medium, low, or a custom percentage of scheduled time for the virtual CPUs.
Storage: Select the desired storage configuration of your virtual machine, such as virtual disks and ISO file.
NIC:
You can add delete virtual network interfaces. For more details, see Setting Up Networks.
Guest VM Naming: Indicate whether the guest virtual machine names are to be automatically generated or if the names will be uploaded from a file.
Disk: Specify the storage type. You can use the Default type as specified by the server pool or select Override. If you select Override, you must specify the Storage QoS and click the Search icon in the Storage field to specify the Storage Type. In the Storage Type window, specify the following:
Clone Target Type: This can be Repository or Storage Array.
Clone Target: If you select Repository, select the storage location where the disk is to be created. If you select Storage Array, specify the type, which can be SAN or ISCSI storage server.
Clone Type: This can be Sparse or Non-Sparse Copy. A sparse copy is a disk image file of a physical disk, taking up only the amount of space actually in use; not the full specified disk size. A non-sparse copy is a disk image file of a physical disk, taking up the space equivalent to the full specified disk size, including empty blocks.
This section describes the various options that can be used to deploy guest virtual machines. It contains the following sections:
Provisioning Guest Virtual Machines Using Oracle Virtual Assemblies (OVA)
Provisioning a Guest Virtual Machine Using Oracle VM Templates
This section helps you get started by providing an overview of the steps involved in provisioning virtualized systems. Consider this section to be a documentation map to understand the sequence of actions you must perform to successfully provision virtualized systems. Click the reference links provided against the steps to reach the relevant sections that provide more information.
Table 7-1 Getting Started with Oracle VM Provisioning
| Step | Description | Reference Link |
|---|---|---|
|
Step 1 |
Understanding the Deployment Options Understand the deployment plans offered by Enterprise Manager for deploying virtualization systems. |
To learn about the deployment options, see Deployment Options. |
|
Step 2 |
Meeting the Prerequisites Before you run the Deployment Procedure, you must meet the prerequisites, such as setting up the provisioning environment, applying mandatory patches, and creating the Software Library components. |
To learn about the prerequisites for provisioning guest virtual machines, see Prerequisites. |
|
Step 3 |
Selecting the Use Case This section covers a few use cases for the provisioning of guest virtual machines. Select the use case that best matches your requirements. |
To provision a guest virtual machine using:
|
Enterprise Manager provides the following deployment options for provisioning guest virtual machines:
Virtual Machine Provisioning Using Assembly: Creates new guest virtual machines using an assembly component.
Virtual Machine Provisioning Using Template: Creates new guest virtual machines using a template component.
Virtual Machine Provisioning Using ISO: Creates a new guest virtual machine using an ISO image.
Virtual Machine Provisioning Using PXE: Creates a new guest virtual machine using Preboot Execution Environment. The new guest virtual machines will be PXE-booted and they will get provisioned by way of networks.
Cloning a Virtual Machine: Clones a guest virtual machine to one or more guest virtual machines.
Bare Metal Provisioning: Allows you to provision Oracle VM server software on bare metal machines.
Before you run any deployment procedures, meet the infrastructure requirements described in this section.
Mandatory Infrastructure Requirements as defined in the Enterprise Manager Lifecycle Management Administrator's Guide.
Optional Infrastructure Requirements as defined in the Enterprise Manager Lifecycle Management Administrator's Guide.
The assembly, template, or the ISO image to be deployed must be present as a Software Library component, or at an external HTTP or NFS location, or imported to the server pool shared location.
This section describes the procedure to create the virtualization components in the Software Library. It includes the following:
An assembly is a collection of virtual machine instances. When an assembly is deployed, a group of virtual machines or an assembly instance is created.
Prerequisites
The Assembly Binary, a file with a .ova extension must be present on the Management Agent or on an external http/ftp/nfs location.
Follow this process to create a new assembly component:
From the Enterprise menu, select Provisioning and Patching, then select Software Library.
Select a folder on the Software Library page. From the Actions menu, select Create Entity, then select Virtualization. You can also right click on a folder and select the virtualization option from the context menu.
From the Create Entity: Virtualization pop-up window, choose Assembly from the Select Subtype drop down list.
In the Create Assembly: Describe page, enter the following details:
Name and description of the assembly.
In the Attachments section, click Add to attach any files relevant to the entity. Ensure that the file size is less than 2 MB.
In the Notes section, include information related to the entity like changes being made to the entity or modification history that you want to track and click Add.
Click Next to continue. In the Create Assembly: Upload Files page, select one or more files to be associated with the assembly. You can either:
Upload Files: You can upload files from a storage location in the Software Library. For Software Library to become usable, at least one upload file location must be configured. Select the Upload Files option. In the Specify Destination section, click the Browse button in the Upload Location field. Two storage options are supported:
OMS Shared File System: An OMS Shared File System location is required to be shared (or mounted) across all the Oracle Management Server (OMS) hosts. This option is ideal for UNIX systems.
For single OMS environments, you can configure the Software Library either on the host where the OMS is running or in a shared location, so that it is accessible to all the OMS hosts. For multiple OMS environments, Oracle recommends that you configure the Software Library in a shared location so that the storage is accessible through NFS mount points to all Oracle Management Servers in the environment
OMS Agent File System: An OMS Agent File System location is a location that is accessible to one of the OMS host's Agent. This option is ideal for OMS installed on Windows hosts. By selecting this option for uploading files, you can avoid sharing a location between all participating OMS hosts.
Credentials must be set before using an OMS Shared File System or OMS Agent File System. For an OMS Shared File System, normal host credential must be set before configuring a storage location. However, for OMS Agent File System location configuration, a credential (preferred or named) has to be specified.
Refer Files: Select this option if you want to use an external file location where the software library files are staged. Referenced File Locations support three storage options:
HTTP: An HTTP storage location represents a base URL which acts as the source of files that can be referenced. For example, the base URL http://my.files.com/scripts could be configured as an HTTP location for sourcing files such as http://my.files.com/scripts/perl/installMyDB.pl or http://my.files.com/scripts/linux/stopMyDB.sh.
Agent: A storage location is similar to the OMS Agent File System option, but can be any host monitored by an Management Agent. The Management Agent can be configured to serve the files located on that host. For example, the directory /u01/binaries on the Enterprise Manager Host my.em.file.server could be configured as an Agent location for sourcing files such as /u01/binaries/rpms/myCustomDB.rpm or /u01/binaries/templates/myTemplate.tar.gz
These locations require a named credential to be associated which will be used to access the files from the base location on the host through the Management Agent.
Specify Source: You can add additional file storage locations.
To add a HTTP location that can be accessed through a HTTP URL, select HTTP from the Storage Type list and click Add. In the Add HTTP Location dialog box, enter a unique name and a HTTP location for the storage that you want to reference, and click OK. A new entry for the storage location is created, with details like Name, Location, and Status.
To add a Management Agent location that has read-only privileges set on it, select Agent from the Storage Type list and click Add.
Click Next. In the Assembly Details page, you will see a set of predefined deployment profiles. You will also see the structure of the assembly and all the appliances in the assembly. Click Next.
On the Review page, click Save to save the assembly component. Click Save and Upload to save the assembly component and upload it to the Software Library.
Follow these steps to create a template component
From the Enterprise menu, select Provisioning and Patching, then select Software Library.
Select a folder on the Software Library page. From the Actions menu, select Create Entity, then select Virtualization. You can also right click on a folder and select the virtualization option from the context menu.
In the Create Template: Describe page, enter the name and description of the template.
Select the Operating System Name, Type, and Virtualization Type. The Virtualization Type can be Para Virtualized, Hardware Virtualized or both. Select Para Virtualized if you want use machines that are not enabled for virtualization. Select Hardware Virtualized if you want to use machines that are enabled for virtualization.
Para Virtualized: A virtual machine with a kernel that is recompiled to be made aware of the virtual environment. Runs at near native speed, with memory, disk and network access optimized for maximum performance.
Hardware Virtualized: A virtual machine with an unmodified guest operating system. It is not recompiled for the virtual environment. There may be substantial performance penalties running as a hardware virtualized guest. Enables Microsoft Windows™ operating system to be run, as well as legacy operating systems. Hardware virtualization is only available on Intel VT or AMD SVM CPUs.
Click Next to continue. In the Create Template: Upload Files page, select one or more files to be associated with the assembly. You can:
Upload Files: You can upload files from a storage location in the Software Library. For the Software Library to become usable, at least one upload file location must be configured. Select the Upload Files option. In the Specify Destination section, click the Browse button in the Upload Location field. The following storage options are supported:
OMS Shared File System: An OMS Shared File System location is required to be shared (or mounted) across all the Oracle Management Service (OMS) hosts. This option is ideal for UNIX systems.
For single OMS environments, you can configure the Software Library either on the host where the OMS is running or in a shared location, so that it is accessible to all the OMS hosts. For multiple OMS environments, Oracle recommends that you configure the Software Library in a shared location so that the storage is accessible through NFS mount points to all Oracle Management Servers in the environment
OMS Agent File System: An OMS Agent File System location is a location that is accessible to one of the OMS host's Agent. This option is ideal for OMS installed on Windows hosts. By selecting this option for uploading files, you can avoid sharing a location between all participating OMS hosts.
Credentials must be set before using an OMS Shared File System or OMS Agent File System. For an OMS Shared File System, normal host credential must be set before configuring a storage location. However, for OMS Agent File System location configuration, a credential (preferred or named) has to be specified.
Refer Files: Select this option if you want to use a external file location where the software library files are staged. Referenced File Locations support three storage options:
HTTP: An HTTP storage location represents a base URL which acts as the source of files that can be referenced. For example, the base URL http://my.files.com/scripts could be configured as an HTTP location for sourcing files such as http://my.files.com/scripts/perl/installMyDB.pl or http://my.files.com/scripts/linux/stopMyDB.sh.
Agent: A storage location is similar to the OMS Agent File System option, but can be any host monitored by the Management Agent. The Management Agent can be configured to serve the files located on that host. For example, the directory /u01/binaries on the Enterprise Manager Host my.em.file.server could be configured as an Agent location for sourcing files such as /u01/binaries/rpms/myCustomDB.rpm or /u01/binaries/templates/myTemplate.tar.gz
These locations require a named credential to be associated which will be used to access the files from the base location on the host through the Management Agent.
Specify Source: You can add additional file storage locations.
To add a HTTP location that can be accessed through a HTTP URL, select HTTP from the Storage Type list and click Add. In the Add HTTP Location dialog box, enter a unique name and a HTTP location for the storage that you want to reference, and click OK. A new entry for the storage location is created, with details like Name, Location, and Status.
To add the Management Agent location that has read-only privileges set on it, select Agent from the Storage Type list and click Add and enter the required information in the Add Agent Location dialog box.
Click Next. In the Review page, review the details of the template and click Save. Click Save and Upload to save the template component and upload it to the Software Library. The template component will now appear as an entity in the Software Library page.
Follow these steps to create an ISO component:
From the Enterprise menu, select Provisioning and Patching, then select Software Library.
Select a folder on the Software Library page. From the Actions menu, select Create Entity, then select Virtualization. You can also right click on a folder and select the virtualization option from the context menu.
Select the Subtype as ISO.
In the Create ISO: Describe page, enter the name and description of the deployment plan.
Click Next to continue. In the Create ISO: Upload Files page, select one or more files to be associated with the assembly. You can either:
Upload Files: You can upload files from a storage location in the Software Library. For Software Library to become usable, at least one upload file location must be configured. Select the Upload Files option. In the Specify Destination section, click the Browse button in the Upload Location field. The following storage options are supported:
OMS Shared File System: An OMS Shared File System location is required to be shared (or mounted) across all the Oracle Management Service (OMS) hosts. This option is ideal for UNIX systems.
For single OMS environments, you can configure the Software Library either on the host where the OMS is running or in a shared location, so that it is accessible to all the OMS hosts. For multiple OMS environments, Oracle recommends that you configure the Software Library in a shared location so that the storage is accessible through NFS mount points to all Oracle Management Servers in the environment
OMS Agent File System: An OMS Agent File System location is a location that is accessible to one of the OMS host's Agent. This option is ideal for OMS installed on Windows hosts. By selecting this option for uploading files, you can avoid sharing a location between all participating OMS hosts.
Credentials must be set before using an OMS Shared File System or OMS Agent File System. For an OMS Shared File System, normal host credential must set before configuring a storage location. However, for OMS Agent File System location configuration, a credential (preferred or named) has to be specified.
Refer Files: Select this option if you want to use a external file location where the software library files are staged. Referenced File Locations support three storage options:
HTTP: An HTTP storage location represents a base URL which acts as the source of files that can be referenced. For example, the base URL http://my.files.com/scripts could be configured as an HTTP location for sourcing files such as http://my.files.com/scripts/perl/installMyDB.pl or http://my.files.com/scripts/linux/stopMyDB.sh.
Agent: A storage location is similar to the OMS Agent File System option, but can be any host monitored by the Management Agent. The Management Agent can be configured to serve the files located on that host. For example, the directory /u01/binaries on the Enterprise Manager Host my.em.file.server could be configured as an Agent location for sourcing files such as /u01/binaries/rpms/myCustomDB.rpm or /u01/binaries/templates/myTemplate.tar.gz
These locations require a named credential to be associated which will be used to access the files from the base location on the host through the Management Agent.
Specify Source: You can add additional file storage locations.
To add a HTTP location that can be accessed through a HTTP URL, select HTTP from the Storage Type list and click Add. In the Add HTTP Location dialog box, enter a unique name and a HTTP location for the storage that you want to reference, and click OK. A new entry for the storage location is created, with details like Name, Location, and Status.
To add an NFS shared location, select NFS from the Storage Type list and click Add. In the Add NFS Location dialog box, enter a unique name in the Name field for the storage. In NFS server field, provide a fully qualified domain name or the IP address of the hosted machine that has NFS services running on them. In the Location field, provide the shared location or directory path on the NFS server to define a storage location, then click OK. A new entry for the storage location is created in the table, with details like Name, Location, and Status.
To add a Management Agent location that has read-only privileges set on it, select Agent from the Storage Type list and click Add.
Click Next. In the Review page, review the details and click Save. Click Save and Upload to save the assembly component and upload it to the Software Library. The ISO image will now appear as an entity in the Software Library page.
Follow these steps to create a virtual disk component:
From the Enterprise menu, select Provisioning and Patching, then select Software Library.
Select a folder on the Software Library page. From the Actions menu, select Create Entity, then select Virtualization. You can also right click on a folder and select the virtualization option from the context menu.
Select the Subtype as Virtual Disk.
In the Virtual Disk: Describe page, enter the name and description of the deployment plan.
Click Next to continue. In the Create Virtual Disk: Upload Files page, select one or more files to be associated with the assembly. You can either:
Upload Files: You can upload files from a storage location in the Software Library. For Software Library to become usable, at least one upload file location must be configured. Select the Upload Files option. In the Specify Destination section, click the Browse button in the Upload Location field. The following storage options are supported:
OMS Shared File System: An OMS Shared File System location is required to be shared (or mounted) across all the Oracle Management Server (OMS) hosts. This option is ideal for UNIX systems.
For single OMS environments, you can configure the Software Library either on the host where the OMS is running or in a shared location, so that it is accessible to all the OMS hosts. For multiple OMS environments, Oracle recommends that you configure the Software Library in a shared location so that the storage is accessible through NFS mount points to all Oracle Management Servers in the environment
OMS Agent File System: An OMS Agent File System location is a location that is accessible to one of the OMS host's Agent. This option is ideal for OMS installed on Windows hosts. By selecting this option for uploading files, you can avoid sharing a location between all participating OMS hosts.
Credentials must be set before using an OMS Shared File System or OMS Agent File System. For an OMS Shared File System, normal host credential must set before configuring a storage location. However, for OMS Agent File System location configuration, a credential (preferred or named) has to be specified.
Refer Files: Select this option if you want to use a external file location where the software library files are staged. Referenced File Locations support three storage options:
HTTP: An HTTP storage location represents a base URL which acts as the source of files that can be referenced. For example, the base URL http://my.files.com/scripts could be configured as an HTTP location for sourcing files such as http://my.files.com/scripts/perl/installMyDB.pl or http://my.files.com/scripts/linux/stopMyDB.sh.
Agent: A storage location is similar to the OMS Agent File System option, but can be any host monitored by the Management Agent. The Agent can be configured to serve the files located on that host. For example, the directory /u01/binaries on the Enterprise Manager Host my.em.file.server could be configured as an Agent location for sourcing files such as /u01/binaries/rpms/myCustomDB.rpm or /u01/binaries/templates/myTemplate.tar.gz
These locations require a named credential to be associated which will be used to access the files from the base location on the host through the Management Agent.
Specify Source: You can add additional file storage locations.
To add a HTTP location that can be accessed through a HTTP URL, select HTTP from the Storage Type list and click Add. In the Add HTTP Location dialog box, enter a unique name and a HTTP location for the storage that you want to reference, and click OK. A new entry for the storage location is created, with details like Name, Location, and Status.
To add an Agent location that has read-only privileges set on it, select Agent from the Storage Type list and click Add.
Click Next. In the Review page, review the details of the virtual disk and click Save. Click Save and Upload to save the virtual disk component and upload it to the Software Library. The virtual disk component will now appear as an entity in the Software Library page.
An assembly is a packaging of a multi-tier application stack, which when deployed results in the creation of a set of related virtual machines representing every tier of the application stack. For example, a Siebel assembly can contain the Siebel mid-tier and a database. It can be deployed such that it creates 2 virtual machines for a 2-node Siebel mid-tier and 1 virtual machine running the database.
The deployment of the assembly is based on the policies/constraints defined in the assembly definition. The initial placement of virtual machines will be based on the storage, network and computational resources. Once an assembly is deployed, additional instances can be added (scale up) or removed (scale down) based on application demand.When an assembly is deployed, an assembly instance is created. An assembly instance is a collection of dependent virtual machines, which is created after an assembly is deployed. The composition of the assembly instance is dynamic in nature, as any subsequent scale-up or scale-down operations will change the membership. An assembly instance contains one or more tiers, each tier further comprising of virtual machines and or tiers.
Follow this process to deploy an assembly and create the virtual machines.
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a Virtual Server Pool target and select Deploy Assembly.
On the Assembly Deployment: Deployment Configuration page, specify the following:
Target: Select the server pool on which the guest virtual machines are to be deployed.
Source: You can select either of the following options:
Deployment Plan: If you select the Use Deployment Plan check box, you can select a deployment plan (if available) with predefined configurations. The deployment plan will be used when the assembly is deployed. (image is selected automatically when the deployment plan is selected)
Image: The assembly component to be used for this deployment. This can either be a component present in the Software Library, or at an external location. If it is stored in an external location, specify the NFS or HTTP location where the component is stored. For example, http://myvm_server/assembly or file://myvm_server/assembly.
Details:
Request Name: This is the name of the assembly deployment request.
Assembly Instance Name: The name to assigned to the assembly instance.
Allow Partial Deployment: Select this option to enable partial deployment. By default, when a deployment plan fails, all virtual machines that have been created are automatically deleted. But if partial deployment is enabled, virtual machines are not deleted even if the deployment has failed.
Assembly Content: You can disable an assembly tier or a node from being deployed. By default, all nodes and tiers in the selected component are automatically deployed. To disable a node or tier from being deployed, unselect the Deploy checkbox in the table.
Note:
A tier or a node can be disabled for deployment if the minimum number of instances for the node or tier is set to 0 in the ovf metadata file.
If you choose to use a deployment plan where a tier or a node has been enabled for deployment, that node or tier cannot be disabled.
Click Next. In the Deploy Assembly: Network and Agent page, specify the physical public and private networks to be used for the assembly instance. A public network is used for external traffic. In a private network, the guest virtual machines can communicate only within a predefined network set up by the Cloud Administrator.
Assembly network refers to the logical network defined in the OVF metadata file and the network defined here is the actual physical network to which it is to be mapped. If you do not choose to associate the network explicitly, the mappings are automatically assigned.
Click on the Browse icon in the Network field. Specify if the network should be allocated by the system or selected manually.
If you want to install the Management Agent on an assembly tier (collection of Guest VMs) or selected guest virtual machines, check the Enable EM Agent Push Configuration check box. You can then select the tiers and / or the guest virtual machines on which the Management Agent is to be installed using the Agent Push approach in the Assembly Node Selection for EM Agent Push Selection table.
Node Name: The name of the assembly tier on which the Management Agent is to be deployed.
Installation Type: The type of installation which can be Push Agent Installation, No Agent Installation, and RPM Installation.
Enable Agent Push: This checkbox is enabled only if the Enable EM Agent Push Configuration checkbox has been selected. Select this checkbox to select the tiers on which the Management Agent is to be installed by way of the Agent Push approach.
In a selected tier, you can also choose the guest virtual machines on which the Management Agent is to be installed.
Note:
If you select Push Agent Installation, you can specify the guest virtual machines that need to be enabled or disabled in the Miscellaneous tab.
For tiers that have the Management Agent as a product (as part of the binary package), the Enable Agent Push checkbox is disabled and only RPM Installation is available. In this case, you can specify the Management Agent details in the Product Configuration tab of the selected tier.
After you have specified the options to configure the Management Agent, enter the following details:
Installation Base Directory: This is the parent directory on the remote host where the Oracle home of the Management Agent is created.
Platform: The operating system on which the Management Agent is to be installed.
User: The name of the Oracle Install user is displayed here.
Port: The port used by the Management Agent for communication.
Password: This field is mandatory for PS5 assemblies if the Enable Agent Push Configuration checkbox has been selected.
Additional Parameters: Specify additional parameters to be used during the installation of the Management Agent. F or example, enter -ignoreDirPrereq to ignore the prerequisite checks during installation.
Click Next to go to the Deploy Assembly: Deployment Configuration page.
The following details are displayed:
Component: The assembly component that is being deployed.
Guest VMs: The default number of guest virtual machines as specified in the deployment profile appears. Specify the minimum and maximum number of guest virtual machines that are to be created.
Auto Scalable: If you select the Auto Scalable check box, it guarantees the availability of the guest virtual machines if the virtual server they are running on fails or restarts. When a virtual server is restarted or shut down, the guest virtual machines running on it are either restarted on, or migrated to, another virtual server.
Note: You can select the check box only if high availability has been enabled for the server pool during creation.
VM Size: The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started. The size of the guest virtual machine (memory and CPU values).
Deployment Option: The deployment for this assembly instance.
Guest VM Name Prefix: This string will be used as a prefix in the guest virtual machine name. When a guest virtual machine is created using the Enterprise Manager, guest virtual machine names will be prefixed by the virtual machine name prefix you provide here and a number.
Select the assembly component to view and customize the default configuration properties.
Product Configuration: This tab shows the properties of the products in the assembly. You can choose to view All Properties or Required Properties. For each property, the default value and the current value is displayed. Select a property to modify the value if applicable.
Miscellaneous: You can create one or more anti-affinity groups. An anti-affinity group is a group of virtual machines cannot run on the same server. Click Add and enter the Group Name and select the guest virtual machines that are to be part of the anti-affinity group.
Click a row in the table to select the tier you want to configure. There are 3 tabs that can be configured for each tier in the assembly: Guest VM Configuration, Product Configuration, and Miscellaneous.
Let us look at the first tab: Guest VM Configuration. This tab allows you to modify the resource configuration parameters for all guest virtual machine instances of the selected assembly tier.
The following parameters can be configured:
Guest VM Configuration:
Enable High Availability: If you want to enable high availability for this guest virtual machine, select this check box. If this option is enabled, the virtual server is shut down or restarted, the guest virtual machine is migrated to or restarted on another virtual server.
Note:
High availability must be enabled both on the virtual server pool and on the guest virtual machine. If it is not enabled on both, high availability is disabled.CPU Scheduling Priority: Specify the priority of a guest virtual machine to access the physical CPUs, while competing with other guest virtual machines on the same virtual server. Higher the priority, higher is the stake of the guest virtual machine in claiming CPU cycles.
CPU Scheduling Cap (%): Restricts the amount of physical CPU that a guest virtual machine can use. Use this to constrain guest virtual machine resource allocation.
Root Password: Specify the operating system root password to log in to the guest virtual machine once it is up and running.
Memory (in MB): The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started.
CPUs: The number of CPU cores to assign to this guest virtual machine. This will show up as virtual CPU (VCPU) configuration parameter for the guest virtual machine.
Disk: Specify the storage type. You can use the Default type as specified by the server pool or select Override. If you select Override, you must specify the Storage QoS and click the Search icon in the Storage field to specify the Storage Type. In the Storage Type window, specify the following:
Clone Target Type: This can be Repository or Storage Array.
Clone Target: If you select Repository, select the storage location where the disk is to be created. If you select Storage Array, specify the type, which can be SAN or ISCSI storage server.
Clone Type: This can be Sparse or Non-Sparse Copy. A sparse copy is a disk image file of a physical disk, taking up only the amount of space actually in use; not the full specified disk size. A non-sparse copy is a disk image file of a physical disk, taking up the space equivalent to the full specified disk size, including empty blocks.
Disk: Every guest virtual machine is created with at least one disk. You can specify additional disks and their sizes. These disks will be added to the guest virtual machine. After the guest virtual machine is created, log in to the guest virtual machine and reformat and mount the additional disks. Click Add to add a storage device (disk).
Specify the name of the hard disk, its size, and QoS Priority Class. You can enable the disk I/O priority by setting an appropriate QoS Priority Class. The priority class ranges from 0 to 7. The priority class 0 has the highest priority, and 7 the lowest.Select the Shared Disk check box to share this disk between multiple guest virtual machines. You can enable the disk I/O priority by setting an appropriate QoS Priority Class. The priority class ranges from 0 to 7. The priority class 0 has the highest priority, and 7 the lowest.
NIC: Specify the network interfaces for this guest virtual machine. The minimum value is 1 and maximum is 8. Click Add to add a network interface and specify the following details:
Name: Enter a name for the network resource.
Network: Assembly Network / Backend network.
Network Type: Specify if the network type is Internet Routable, Non Internet Routable, or a predefined set of IP addresses.
IP Assignment: Select the protocol to be used to assign the IP address. This can be DHCP, Network Profile, or None.
The configuration parameters you specify here will be applied to all the guest virtual machine instances of the selected node. If you want to specify a different configuration for a guest virtual machine instance, click the Guest VM Instances option. In the Deployment Configuration: GuestVM Instance page, you can select a guest virtual machine instance from the View list and specify configuration parameters for that instance.
The next tab is Product Configuration. This tab shows the properties of the products in the tier. You can choose to view All Properties or Required Properties. For each property, the default value and the current value is displayed. Select a property to modify the value if applicable.
The next tab is the Miscellaneous tab.
Miscellaneous: Specify the following details:
Log File Location: Specify the directory in which the log files are to be stored.
Timeout Settings: Specify the timeout settings for the Product Configuration and Network Configuration. The default value is 60 minutes and this value can be modified for each Oracle VM Manager target. The timeout value specifies how long Enterprise Manager should wait for either Product Configuration or Network Configuration to be completed before proceeding with the assembly deployment.
If a tier has more than one Guest VM Instance, you can configure each Guest VM Instance separately. Select the tier for each Guest VM Instance has to be separately configured. Click the Guest VM Instances link on the top right corner of the lower region. The Deployment Configuration: Configure Guest VM Instance page appears. Click Edit VM Name to modify the name of the Guest VM Instance, specify a new name and click OK. You can modify the configuration of the Guest VM and click Continue to return to the Assembly Deployment: Deployment Configuration page.
Click Next. In the Assembly Deployment: Schedule page, specify the Start and End Date for the assembly deployment. The Start Date is the date on which the request is being submitted and the End Date is the date on which the assembly deployment instances are retired. Click Next.
Click Next. The Assembly Deployment: Review page appears.
Click Next. Review the details entered so far. You can save as a plan that can be used later. Click Save as Plan, specify a name, and description for the plan. Select the folder in which the deployment plan is to be saved and click OK. Note that the deployment plan is stored as a software library component but can be created only through this procedure or by a Cloud API that generates a default deployment plan for an assembly.
Click Submit to submit the plan and complete the process.
Note:
To ensure that Enterprise Manager has been configured correctly to push a 12c Management Agent automatically on the guest virtual machines when the assembly deployed, you must change the agentpush entry in the
<OMS_ORACLE_HOME>/sysman/prov/agentpush/agentpush.properties file as follows:
From: oracle.sysman.prov.agentpush.pdpShellOutEnabled=true
To: oracle.sysman.prov.agentpush.pdpShellOutEnabled=false
After this change has been made, you must restart the Oracle Management Service.
You can create one or more virtual machines by deploying a template. The deployment of the template is based on the constraints defined while the template was created. Typically, a template can contain an operating system, basic configuration (number of CPUs, memory, disk size), and preinstalled applications. The initial placement of virtual machines will be based on the storage, network and computational resources. Once a template is deployed, additional instances can be added (scale up) or removed (scale down) based on application demand.
Note:
Enterprise Manager supports deployment of legacy Oracle VM 2.2 style Templates. This templates are available in the.tgz file format. Guest virtual machines are created when these templates are deployed, but the you need to manually login to the VNC console of the newly created virtual machines to complete the network and product configuration. Also, unlike for Oracle Virtual Assemblies (.ova file format), Enterprise Manager does not automatically push the Management Agent for Oracle VM 2.2 Templates (.tgz file format).Enterprise Manager Cloud Control is set up to manage the cloud environment.
The template is available to the zone and you have sufficient privileges to deploy it.There are sufficient resources available in the zone for successful deployment.
Follow this process to deploy a template:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a virtual server pool target and select Deploy Template.
On the Select Target and Source page, select the following:
Select the target machine on which the guest virtual machine is to be created.
In the Source section, you can select either of the following options:
Deployment Plan: If you select the Use Deployment Plan check box, you can select a deployment plan (if available) with predefined configurations. Selecting a plan at this stage allows you to prepopulate the interview with previously saved values of deployment and configuration parameters.
Template: The template component to be used for this deployment. This can either be a component present in the Software Library, or at an external location. If it is stored in an external location, specify the NFS or HTTP location where the component is stored. For example, http://myvm_server/template or file://myvm_server/template.
Click Next. The Template Deployment: Deployment Configuration page appears.
This page contains the following sections:
Guest VM
Guest VM: Number of guest virtual machines to be deployed. Click Configure Each Guest VM Instance if you want to configure each guest virtual machine instance individually.
Guest VM Naming: You can choose either of the following options:
Generate Guest VM Names Using Prefix: This string will be used as a prefix in the guest virtual machine name. When a guest virtual machine is created using the Enterprise Manager, guest virtual machine names will be prefixed by the virtual machine name prefix you provide here and a number.
Upload Guest VM Names from File: If you select this option, you can Browse and upload a file with user defined guest virtual machine names.
General Configuration
Enable High Availability: If you want to enable high availability for this guest virtual machine, select this check box. If this option is enabled, the virtual server is shut down or restarted, the guest virtual machine is migrated to or restarted on another virtual server.
Note:
High availability must be enabled both on the virtual server pool and on the guest virtual machine. If it is not enabled on both, high availability is disabled.Start VM After Creation: Specify whether the guest virtual machine should be started automatically after it is created.
CPU Scheduling Priority: Specify the priority of a guest virtual machine to access the physical CPUs, while competing with other guest virtual machines on the same virtual server. Higher the priority, higher is the stake of the guest virtual machine in claiming CPU cycles.
CPU Scheduling Cap (%): Restricts the amount of physical CPU that a guest virtual machine can use. Use this to constrain guest virtual machine resource allocation.
Keymap: The keyboard mapping to be used for the guest virtual machine.
Memory (in MB): The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started.
CPU Cores: The number of CPU cores to assign to this guest virtual machine. This will show up as virtual CPU (VCPU) configuration parameter for the guest virtual machine.
VM Size: The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started. The size of the guest virtual machine (memory and CPU values). Select the VM Size which can be Custom or Medium. If you select Custom, specify the Memory size and the number of CPUs.
NIC: Specify the network interfaces for this guest virtual machine. The minimum value is 1 and maximum is 8. Click Add to add a network interface and specify the following details:
Name: Enter a name for the network resource.
Network Type: Specify if the network type is Internet Routable, Non Internet Routable, or a predefined set of IP addresses.
IP Assignment: Select the protocol to be used to assign the IP address.
Configure EM Agent: If you want to configure the Management Agent to monitor the guest virtual machine, check the Enable EM Agent Configuration check box. Specify the following details:
Installation Base Directory: This is the parent directory on the remote host where the Oracle home of the Management Agent is created.
Platform: The operating system on which the Management Agent is to be installed.
Port: The port on which the Management Agent will communicate.
Disk:
The list of available disks appears in the Disk section. Click Add to add an additional storage. In the Add Storage Device window, enter the name of the disk and its size. Indicate if it is a shared disk and specify the priority of a guest virtual machine to access the physical CPUs, while competing with other guest virtual machines on the same virtual server. Higher the priority, higher is the stake of the guest virtual machine in claiming CPU cycles.
Click Next and Review the details entered so far.
Review the details entered so far. You can save as a plan that can be used later. Click Save as Plan, specify a name, and description for the plan. Select the folder in which the deployment plan is to be saved and click OK. If you do not wish to save the deployment procedure, click Submit to submit the plan and complete the process.
ISO images are imported into Enterprise Manager from installation media. You can create one or more virtual machines by deploying an ISO image.
Enterprise Manager Cloud Control is set up to manage the cloud environment.
The ISO image is available to the zone and you have sufficient privileges to deploy the image.There are sufficient resources available in the zone for successful deployment.
The Domain Type of the guest virtual machine being deployed must be set to HVM (hardware virtualized).
Follow this process to deploy an ISO image:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Right click on a virtual server pool target and select Deploy ISO.
On the Select Target and Source page, the server pool target on which the ISO image is to be deployed appears. In the Destination section, you can select either of the following:
Deployment Plan: If you select the Use Deployment Plan check box, you can select a deployment plan (if available) with predefined configurations. Selecting a plan at this stage allows you to pre-populate the interview with previously saved values of deployment and configuration parameters.
ISO: The ISO image to be used for this deployment. This can either be a component present in the Software Library, or at an external location. If it is stored in an external location, specify the NFS or HTTP location where the component is stored. For example, http://myvm_server/image or file://myvm_server/image.
Enter the name of the request and click Next to continue. The ISO Deployment: Deployment Configuration page appears.
This page contains the following sections:
Guest VM
Guest VM: Number of guest virtual machines to be deployed. Click Configure Each Guest VM Instance if you want to configure each guest virtual machine instance individually.
Guest VM Naming: You can choose either of the following options:
Generate Guest VM Names Using Prefix: This string will be used as a prefix in the guest virtual machine name. When a guest virtual machine is created using the Enterprise Manager, guest virtual machine names will be prefixed by the virtual machine name prefix you provide here and a number.
Upload Guest VM Names from File: If you select this option, you can Browse and upload a file with user defined guest virtual machine names.
General Configuration
Enable High Availability: If you want to enable high availability for this guest virtual machine, select this check box. If this option is enabled, the virtual server is shut down or restarted, the guest virtual machine is migrated to or restarted on another virtual server.
Note:
High availability must be enabled both on the virtual server pool and on the guest virtual machine. If it is not enabled on both, high availability is disabled.Start VM After Creation: Specify whether the guest virtual machine should be started automatically after it is created.
CPU Scheduling Priority: Specify the priority of a guest virtual machine to access the physical CPUs, while competing with other guest virtual machines on the same virtual server. Higher the priority, higher is the stake of the guest virtual machine in claiming CPU cycles.
CPU Scheduling Cap (%): Restricts the amount of physical CPU that a guest virtual machine can use. Use this to constrain guest virtual machine resource allocation.
VM Size: The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started. The size of the guest virtual machine (memory and CPU values). Select the VM Size which can be Custom or Medium. If you select Custom, specify the Memory size and the number of CPUs.
NIC: Specify the network interfaces for this guest virtual machine. The minimum value is 1 and maximum is 8. Click Add to add a network interface and specify the following details:
Name: Enter a name for the network resource.
Network Type: Specify if the network type is Internet Routable, Non Internet Routable, or a predefined set of IP addresses.
IP Assignment: Select the protocol to be used to assign the IP address.
Configure EM Agent: If you want to configure the Management Agent to monitor the guest virtual machine, check the Enable EM Agent Configuration check box. Specify the following details:
Installation Base Directory: This is the parent directory on the remote host where the Oracle home of the Management Agent is created.
Platform: The operating system on which the Management Agent is to be installed.
Port: The port on which the Management Agent will communicate.
Disk:
The list of available disks appears in the Disk section. Click Add to add an additional storage. In the Add Storage Device window, enter the name of the disk and its size. Indicate if it is a shared disk and specify the priority of a guest virtual machine to access the physical CPUs, while competing with other guest virtual machines on the same virtual server. Higher the priority, higher is the stake of the guest virtual machine in claiming CPU cycles.
Click Next. In the Schedule page, specify when the ISO image is to be deployed and click Next.
Review the details entered so far. You can save as a plan that can be used later. Click Save as Plan, specify a name, and description for the plan. Select the folder in which the deployment plan is to be saved and click OK. If you do not wish to save the deployment procedure, click Submit to submit the plan and complete the process.
One of the key requirements of provisioning is the hardware server's ability to boot over the network instead of a diskette or CD-ROM. There are several ways computers can boot over a network, and Preboot Execution Environment (PXE) is one of them. PXE is an open industry standard supported by a number of hardware and software vendors. A detailed document on PXE specification can be found at http://www.pix.net/software/pxeboot/archive/pxespec.pdf.
You can create a network bootable (PXE boot) virtual machine that has the minimum configuration information, then start the virtual machine through Preboot Execution Environment (PXE) over a network later to install the guest operating system.
Enterprise Manager Cloud Control is set up to manage the cloud environment.
There are sufficient resources available in the zone for successful deployment.
Follow this process to deploy an ISO image:
From the Enterprise menu, select Cloud, then select Infrastructure Home.
Select a Virtual Server Pool target. Select Deploy PXE from the Virtual Server Pool menu.
On the Select Target and Source page, select the following:
Select the target machine on which the guest virtual machines are to be deployed.
Select the deployment plan to be used while creating PXE bootable guest virtual machines. The Deployment Plan contains pre-configured values and configuration parameters. This is an optional field.
Click Next. In the General Configuration page, enter the following details:
Name of the guest virtual machine to be deployed. If you are deploying more than one guest virtual machine, you can use a prefix or upload a file with user defined guest virtual machine names.
Number of guest virtual machines to be deployed. Click Configure Each Guest VM Instance if you want to configure each guest virtual machine instance individually.
Select the VM Size which can be Custom or Medium. If you select Custom, specify the Memory size and the number of CPUs.
Specify the priority of a guest virtual machine to access the physical CPUs, while competing with other guest virtual machines on the same virtual server. Higher the priority, higher is the stake of the guest virtual machine in claiming CPU cycles.
Specify the cap to restrict the amount of physical CPU that a guest virtual machine can use.
CPU Cores: The number of CPU cores to assign to this guest virtual machine. This will show up as virtual CPU (VCPU) configuration parameter for the guest virtual machine.
Keymap: The keyboard mapping to be used for the guest virtual machine.
Memory (in MB): The amount of memory to be allocated to the guest virtual machine. The virtual server should have sufficient memory to run the guest virtual machine. Otherwise, the guest virtual machine will be created, but will not be started.
CPU Cores: The number of CPU cores to assign to this guest virtual machine. This will show up as virtual CPU (VCPU) configuration parameter for the guest virtual machine.
In the NIC Configuration section, you can specify the number of virtual network interfaces for this guest virtual machine. The minimum value is 1 and the maximum value is 8. You can add one or more network interfaces or edit existing ones.
Enterprise Manager Cloud Control provides a VNC console to the newly created guest virtual machine. This is the VNC password to access the VNC console.
Select a Domain Type for the virtual machine:
xen_hvm (hardware virtualization, or fully virtualized): Enables you to select an ISO file from which to create the virtual machine.
xen_pvm (para-virtualized): Enables you to select a location for the mounted ISO file from which to create the virtual machine. Before you create the virtual machine using the paravirtualized method, mount the ISO file on an NFS share, or HTTP or FTP server. The ISO file must be available in the relevant repository.
xen_hvm_pv_drivers: Identical to xen_hvm but with additional paravirtualized drivers for improved performance of the virtual machine. This Domain Type is used to run Windows guest operating systems with an acceptable performance level.
Select the Enable High Availability option if you want the guest virtual machine to run automatically on a different virtual server if the earlier virtual server shuts down.
Select the Start VM After Creation check box to indicate whether the machine should automatically be started after it is created.
The list of available disks appears in the Disk section. Click Add to add an additional storage.
Click Next. In the Schedule page, specify when the PXE bootable guest virtual machines are to be created and click Next.
Review the details entered so far and click Submit to create the PXE bootable guest virtual machines.
Bare metal provisioning involves automated discovery and deployment of the Oracle VM Server on bare metal boxes. It also allows the virtual management servers to be automatically discovered and registered to the virtual management server pool. You can create customized Oracle virtual server images and automatically deploy the Oracle VM Server software on multiple servers based on their MAC or subnet addresses. You can automatically register the provisioned Oracle VM Servers to the specified server pool.
Oracle VM Server image is modeled as a software library component that captures properties like RPM repository, disk layout, packages to be installed, operating system password, Oracle VM Agent password, NFS information, NIS information, NTP information, and so on.
During deployment, you can use a pre-created Oracle VM Server software image or specify all the required properties in the deployment flow itself. You can provision Oracle VM Server software on the following types of targets:
MAC Address: You can specify a list of MAC addresses of bare metal boxes to provisioned.
Subnet: You can specify a subnet for which the Oracle VM server software has to be staged.
Enterprise Manager Host Target: You can specify existing host targets and reprovision them with Oracle VM Server software images.
Follow this procedure to provision virtual management servers and automatically add them to the server pool.
From the Enterprise menu, select Provisioning and Patching, then select Bare Metal Provisioning.
The Bare Metal Provisioning Dashboard appears. Click the Deployments tab.
From the Provisioning menu, select Oracle VM Server. The Provision Oracle VM Server: Target Selection page appears.
Enter a name and description for the deployment procedure.
If you select MAC Addresses, click Add and add the MAC addresses of the servers that need to be provisioned. Click Add from File to add MAC addresses stored in a file.
If you select Subnet, specify the Subnet IP, Netmask, Number of Network Interfaces, and Bootable Network Interface.
Select the OVM Manager target that will be used to manage the Oracle VM Servers.
In the Provision Oracle VM Server: Deployment page, select the following:
Stage Server: During provisioning of an image on hardware servers, the required binaries and files are first transferred to a stage server. This is known as Staging phase and is responsible for preparing images to be installed over the network, and exposing installable or executable software elements over the network to the target hardware server being provisioned.
The Provisioning application requires at least one stage server on which all the activities related to staging can be performed. From the networking perspective, you are advised to keep the stage server as close to the target machines as possible. The Stage Server must be an Enterprise Manager target. If you select the Run Stage Server Pre-requisites Checks check box, you can ensure that the Stage Server meets requirements such as large storage, high memory, bandwidth and so on.
Boot Server: One of the key requirements of the application is the ability of the hardware server to boot up over the network (rather than from a local boot device). A boot server must be set up so that it is able to service the requests from the designated hardware servers in order for them to boot over the network. The Boot Server must be an Enterprise Manager target and should be able to receive the BOOTP and Trivial File Transfer Protocol (TFTP) requests over the network from the hardware server. Select the Boot Server and check the Run Boot Server Pre-requisites Checks to ensure that the Boot Server requirements are met.
Local RPM Repository: The Provisioning application picks up the RPMs for the operating system from the RPM repository. At least one repository needs to be setup for use by the Provisioning application.
Fetch Configuration Properties From Pre-Created Components: In this section, you can select preconfigured components from the Software Library.
OS Component: You can select a preconfigured OS Component which provides operating system details for the machines you are provisioning.
Disk Layout Component: You can select a preconfigured disk layout component to provide profiles for hard disk, physical disk partition, RAID configuration, logical volumes, and logical volume groups for the machines you are provisioning.
Provisioning Directive: Provisioning Directives are entities in the Software Library that represent a set of instructions to be performed. These are constructs used to associate scripts with software components and images. These scripts contain directions on how to interpret and process the contents of a particular component or an image.
Click Next to continue to Provisioning VM Server: Basic OS Details page. Set the Time Zone, OS Root Password, and OVM Agent Password. In the Add Operating System Users list section, click Add. Specify the User Name, Password, Primary Group, and Additional Groups to add the operating system users. Enable or Disable sudo access. Click Next.
The Provision Oracle VM Server: Additional OS Details page contains the following sections:
Dom0 Configuration:
Dom0 Memory: Specify the memory size for the virtual server target.
Additional Configuration and Power Interface: Specify the advanced power configuration for the virtual server target.
Additional OS Details
Mount Point Settings: Specify entries for the /etc/fstab file. You can specify mount points on the newly provisioned Linux machine. By default, mount point settings from the reference Linux machine are inherited.
NIS Settings: Specify entries for the /etc/yp.conf file. You can specify NIS settings for the newly provisioned Linux machine. By default, NIS settings from the reference Linux machine are inherited.
NTP Settings: Specify entries for the /etc/ntp.conf file. You can specify NTP settings for the newly provisioned Linux machine. By default, NTP settings from the reference Linux machine are inherited.
Kernel Parameter Settings: You can add a script in the Kernel Parameters field.
Inittab Settings: You can add a script to describe how the init process should set up the system at run-time.
Firewall Settings: Specify firewall settings for the Linux target. Firewall settings are disabled by default and can be configured. Ensure that the port used by the Management Agent is open for its communication with the Management Service. By default, the Management Agent uses port 3872 or a port number in the range 1830-1849, unless configured to use some other port.
Boot Configurations
Post Install: Specify any set of commands that need to be executed on the newly provisioned machine. These commands will be appended to the post section of the kickstart file.
First Boot: Enter the commands to be run on the system when it boots up for the first time after installation.
Click Next to continue to the Provision Oracle VM Server: Disk Layout page. In the Disk Layout Configuration page, specify hard disk profile, partition configuration, RAID configuration, Logical Volume Group configuration, and Logical Volume configuration.
Hard Disk Profile: Click Add and specify the Device Name and Capacity.
Logical Volume Group Configuration: Click Add and specify the Group Name, Partitions, and RAIDs.
Partition Configuration: Click Add and specify the Mount Point, Device Name, File System Type, and Size (MB).
Logical Volume Configuration: Click Add and specify the Mount Point, Logical Volume Name, Logical Group Name, File System Type, and Size (MB).
Click Next.
In the Network Configuration page, the list of MAC addresses to be provisioned and the network interface components are displayed. You can edit or retain these values. Click Add to add a network interface.
Click Next. In the Schedule page, the Job Name for the Oracle VM Server Bare Metal Provisioning deployment appears. Provide a schedule for the job, either immediately or at a later date. Click Next.
In the Review page, verify that the details you have selected are correctly displayed and submit the job for the deployment. Click Submit Job.
In the Jobs page, view the job steps and verify that Status is Success. If the status is Failed, view the steps that have failed, and fix them and resubmit the job.
Start Provisioning and plug in the bare metal machines when required to add Oracle VM Servers to the Server Pool.
|
 Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
