| Oracle® VM Manager User's Guide Release 2.2 Part Number E15441-02 |
|
|
PDF · Mobi · ePub |
| Oracle® VM Manager User's Guide Release 2.2 Part Number E15441-02 |
|
|
PDF · Mobi · ePub |
Resources include virtual machine templates, virtual machine images, ISO files, virtual disks, and converted virtual machines.
Virtual machine templates: Are imported into Oracle VM Manager and used to create virtual machines.
Virtual machine images: Are imported into Oracle VM Manager and used directly, without the process of creating.
ISO files: Are imported into Oracle VM Manager and used to create virtual machines from installation media.
Shared virtual disks: Extend the storage capability of virtual machines.
This Chapter describes how to manage resources and includes the following sections:
Note:
Only an Administrator or Manager can approve, edit, and delete the imported virtual machine templates, virtual machines, and ISO files.Virtual machine templates are shared among users to create new virtual machines. New virtual machines inherit the same contents and configurations from the template.
Typically, a virtual machine template contains basic configuration, such as the number of virtual CPUs, the size of memory, virtual disks, virtual network interfaces (VIFs), and so on. It may also contain some software applications.
You can obtain a virtual machine template by:
Saving an existing virtual machine as template. For more information, refer to Section 6.8.3, "Saving a Virtual Machine as a Template". You can then use the virtual machine template directly without importing it.
Downloading Oracle VM templates at:
http://www.oracle.com/technology/products/vm/templates.html
The password for the root user of all Oracle VM templates is ovsroot. The password for the oracle account in the OVM_EL4U5_X86_HVM_ORACLE_11G template is oracle. For more information on how to use these templates, see
http://download.oracle.com/otn_software/virtualization/README.templates
Before using the downloaded templates, you must import them into Oracle VM Manager.
Creating a virtual machine template using Oracle VM Template Builder. See the Oracle VM Template Builder Installation and User's Guide for information on using Oracle VM Template Builder to build virtual machine templates.
This section includes the following topics:
Note:
Before you import a virtual machine template, rename the configuration file of the virtual machine to vm.cfg.Depending on where your virtual machine templates are located, on the Virtual Machine Server, on other computers, or on the Internet, you can import virtual machine templates from the server pool or download them from external source. You can also convert a Linux or Windows host to a virtual machine template (P2V).
If you already have some virtual machine templates on your server pool, you can discover and register them in Oracle VM Manager directly.
Before you import a virtual machine template, make sure the uncompressed (unzipped or untared) component files of the virtual machine template are stored in the /OVS/seed_pool/template_name directory in the server pool's shared storage, and make sure the configuration file is named vm.cfg.
When importing, Oracle VM Agent can update the directory information in the vm.cfg file automatically. If you need to modify the vm.cfg file, refer to Appendix A, "Preparing Virtual Machines For Importing".
To select an existing virtual machine template from the server pool, and register it in Oracle VM Manager:
On the Resources page, click Virtual Machine Templates, and then click Import.
Select Select from Server Pool (Discover and register). Click Next.
On the General Information page, enter or select the following general information:
Server Pool Name: The server pool on which the imported virtual machine template is to be located.
Virtual Machine Template Name: The virtual machine template to be imported.
Operating System: The guest operating system of the virtual machine in the template.
Virtual Machine System Username: The user name used to log in to the virtual machine operating system.
Virtual Machine System Password: The password used to log in to the virtual machine operating system.
Description: A description of the virtual machine template.
Click Next.
Confirm the information you have entered.
After importing, the status of the virtual machine template is Pending. You need to approve it to make it available for creating virtual machines. See Section 5.1.5, "Approving the Imported Virtual Machine Template".
To download a virtual machine template from outside of the server pool, such as OTN:
http://www.oracle.com/technology/software/products/virtualization/vm_templates.html
Or your own HTTP/FTP server:
On the Resources page, click Virtual Machine Templates, and then click Import.
Select Download from External Source (HTTP and FTP). Click Next.
On the General Information page, enter or select the following general information:
Server Pool Name: The server pool on which the imported virtual machine template is to be located.
Virtual Machine Template Name: A name for the imported virtual machine template. This must be unique. The name will be used as the name of the directory under /OVS/seed_pool, where the files associated with this virtual machine template are stored.
A template name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 48 characters.
Operating System: The guest operating system of the virtual machine in the template.
Virtual Machine System Username: The user name used to log in to the virtual machine operating system.
Virtual Machine System Password: The password used to log in to the virtual machine operating system.
Description: A description of the virtual machine template.
Click Next.
On the Import Information page, enter the URL where the virtual machine template is located. For example, enter either of the following:
http://host/vm ftp://username:password@host/vm
When using a proxy, select Use Proxy, and enter the proxy address.
Click Next.
Confirm the information.
After importing, the status of the virtual machine template is Pending. You need to approve it to make it available for creating virtual machines. See Section 5.1.5, "Approving the Imported Virtual Machine Template".
You can convert a Linux or Windows host to an Oracle VM virtual machine template (Physical to Virtual, P2V). The conversion process is similar to downloading a template from external source.
Before conversion, you need to restart the Linux or Windows computer with the Oracle VM Server CD, and use P2V utility to start the conversion. For more information on how to use the P2V utility, see the Oracle VM Server User's Guide.
During the conversion, you are prompted to enter the number of virtual CPUs and memory size, and this information is configured in the vm.cfg file. The disk size in the virtual machine is determined by the size of the disks you have chosen to be included in the virtual machine. Make sure the Virtual Machine Server has sufficient resources for the conversion (disk space).
The converted virtual machine template is a hardware virtualized machine (HVM).
To convert a Linux or Windows host to a virtual machine template:
On the Resources page, click Virtual Machine Templates, and then click Import.
Select Linux/Windows P2V Import. Click Next.
On the General Information page, enter the following general information:
Server Pool Name: The server pool on which the converted virtual machine template is to be located.
Virtual Machine Template Name: A name for the converted virtual machine template. This must be unique. The name will be used as the name of the directory under /OVS/seed_pool, where the files associated with this virtual machine template are stored.
A template name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 48 characters.
Operating System: The guest operating system of the virtual machine in the template.
Virtual Machine System Username: The user name used to log in to the virtual machine operating system.
Virtual Machine System Password: The password used to log in to the virtual machine operating system.
Description: A description of the virtual machine template.
Click Next.
On the Import Information page, enter the host name or IP address of the Linux or Windows host. For example, enter:
hostname.example.com
When using a proxy, select Use Proxy, and enter the proxy address.
Click Next.
Confirm the information.
After importing, the status of the virtual machine template is Pending. You need to approve it to make it available. See Section 5.1.5, "Approving the Imported Virtual Machine Template".
The imported virtual machine template can be one of the following statuses.
Importing: The virtual machine template is being imported. Alternatively, the virtual machine template is being created from a virtual machine. See Section 6.8.3, "Saving a Virtual Machine as a Template".
Pending: The virtual machine template has been imported successfully, and is waiting for approval by the Manager.
Active: The virtual machine template has been approved, and is ready to use.
Inactive: The virtual machine template is imported, but not available.
Import Error: There were errors when importing the virtual machine template. Reimport the template, or delete it.
Error: There were errors creating the virtual machine template. Delete the template and try to save the virtual machine as the template again.
To search for a virtual machine template:
Click Show Search on the Virtual Machine Templates page.
The search criteria include: Virtual Machine Template Name, Server Pool Name, and Status. Use % as a wildcard.
Click Search to display the virtual machine templates that match your search criteria.
If an error occurs during downloading from an external source, check if the URL or proxy URL is correct, and then reimport the virtual machine template.
To reimport a virtual machine template:
On the Virtual Machine Templates page, select the virtual machine template you want to reimport, and click Reimport.
Enter the URL. When using a proxy, select Use Proxy.
Click Reimport.
After importing, the status of virtual machine templates is Pending. After the Manager or Administrator approves them, the status changes to Active and the virtual machine now becomes an available template.
To approve an imported virtual machine template, you must have the Manager or Administrator role. On the Virtual Machine Templates page, select the template you want to approve, and then click Approve.
To edit a virtual machine template:
On the Virtual Machine Templates page, select the template you want to update, and click Edit.
Update the template parameters. Click Apply.
For more information about the template parameters, refer to Section 5.1.1, "Importing a Virtual Machine Template".
Oracle VM Manager allows you to import:
Oracle VM virtual machines
VMware virtual machines in VMDK (Virtual Machine Disk) format
Virtual machines in VHD (Virtual Hard Disk) format
When you import non-Oracle VM virtual machines, Oracle VM Manager automatically converts them to Oracle VM virtual machines. This is known as virtual to virtual conversion, or V2V.
A virtual machine configuration file, vm.cfg, is required for each virtual machine that is to be imported. Virtual Iron virtual machines do not have a vm.cfg file, so you must create one before you import the VHD files as virtual machines.
Note:
If the VHD virtual machine does not have a vm.cfg file, one must be manually created. See the Oracle VM Server User's Guide for a sample guest configuration file (vm.cfg) to use when migrating Virtual Iron (VHD) virtual machines.Also check the Oracle VM home page on the Oracle Technology Network (OTN) web site for a white paper on converting VHD virtual machines, when it becomes available:
This section includes the following topics:
Note:
Before you import an Oracle VM virtual machine, make sure the configuration file is named vm.cfg.Depending on where your virtual machines are located, on the Virtual Machine Server, on other computers, or on the Internet, you can import a virtual machine image from different sources. You can also convert a Linux or Windows host to a virtual machine. This is known as physical to virtual conversion, or P2V. This section discusses the options for adding virtual machines and contains:
Note:
When importing a VMware virtual machine, make sure you have enough free disk space in the /OVS/tmp directory to convert the VMware virtual machine to an Oracle VM virtual machine. Oracle VM requires at least twice the disk space of the VMware virtual machine.If you already have virtual machine images (either native Oracle VM images, or supported non-Oracle VM images) in your server pool, you can discover and register them in Oracle VM Manager directly, without going through the downloading or copying process.
Before importing, make sure the component files of the virtual machine are stored in the /OVS/running_pool/virtual_machine_name directory on the Virtual Machine Server, and that the configuration file is named vm.cfg.
When importing, Oracle VM Agent updates the directory information in vm.cfg automatically. If you need to modify the vm.cfg file, refer to Appendix A, "Preparing Virtual Machines For Importing".
To discover and select an existing virtual machine image from the server pool, and register it in Oracle VM Manager:
On the Resources page, click Virtual Machine Images, and click Import.
Select Select from Server Pool (Discover and register). Click Next.
On the General Information page, enter the following general information:
Server Pool Name: The server pool on which the imported virtual machine is to be located.
Sharing: Whether you want to share this virtual machine.
private: The virtual machine can only be used by the user who imports it.
Shared (group_name): The virtual machine can be used by members of this specific group.
Virtual Machine Image Name: The virtual machine to be imported.
Oracle VM Agent identifies the hypervisor type of the virtual machine directory. If both Oracle VM and non-Oracle VM virtual machines are stored in the same directory, Oracle VM Agent identifies the Oracle VM virtual machine only, and ignores other types of virtual machines. If a non-Oracle VM virtual machine is detected, V2V (virtual machine to virtual machine) conversion is started.
Enable High Availability: You can enable high availability for the imported virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".
Operating System: The guest operating system of the imported virtual machine.
Virtual Machine System Username: The user name used to log in to the virtual machine.
Virtual Machine System Password: The password used to log in to the virtual machine.
Console Password: The password to use for VNC access to the virtual machine.
Confirm Console Password: Confirm the password to use for VNC access to the virtual machine.
Click Next.
Confirm the information on the Confirm Information page.
Select whether to retain or delete any non-Oracle VM virtual machine files in the server pool with the Delete V2V Source Image Files check box.
Click Confirm.
After importing, the status of the virtual machine is Pending. You need to approve it to make it available. See Section 5.2.5, "Approving the Imported Virtual Machine Image".
If the status is Import Error, click the error log link to check the detailed information.
To download a virtual machine image from outside of the server pool using FTP or HTTP:
On the Resources page, click Virtual Machine Images, and click Import.
Select Download from External Source (HTTP and FTP). Click Next.
On the General Information page, enter the following general information:
Server Pool Name: The server pool on which the imported virtual machine is to be located.
Sharing: Whether you want to share this virtual machine, or keep it private.
Private: The virtual machine can only be used by the user who imports it.
Shared (group_name): The virtual machine can be used by members of a specific group.
Virtual Machine Image Name: A name for the imported virtual machine. This must be unique. The name will be used as the name of the directory under /OVS/running_pool, where the files associated with this virtual machine are stored.
A virtual machine image name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 48 characters.
Enable High Availability: You can enable high availability for the imported virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".
Operating System: The guest operating system of the imported virtual machine.
Virtual Machine System Username: The user name used to log in to the virtual machine operating system.
Virtual Machine System Password: The password used to log in to the virtual machine operating system.
Console Password: The password to use for VNC access to the virtual machine.
Confirm Console Password: Confirm the password to use for VNC access to the virtual machine.
Click Next.
On the Import Information page, enter the URL of the folder where the virtual machine you want to import is located. For example, enter either of the following:
http://example.com/vm ftp://username:password@example.com/vm
If you are importing a non-Oracle VM virtual machine, enter the URL of the .vmx or .vhd file. For example, enter:
ftp://username:password@example.com/vm/vm.vmx
Oracle VM Manager copies the necessary files of the virtual machine to the server pool, then converts the virtual machine to an Oracle VM virtual machine, and generates the vm.cfg file.
Note:
Oracle VM Manager does not create a vm.cfg file for Virtual Iron, Citrix XenServer, and Microsoft Hyper-V virtual machines. You must manually create a vm.cfg file.When using a proxy, select Use Proxy, and enter the proxy address.
Click Next.
Confirm the information on the Confirm Information page.
Select whether to retain or delete any non-Oracle VM virtual machine files in the server pool with the Delete V2V Source Image Files check box. Source files to be retained are saved in the /OVS/seed_pool directory/vm_name directory.
Click Confirm.
After importing, the status of the virtual machine is Pending. You need to approve it to make it available. See Section 5.2.5, "Approving the Imported Virtual Machine Image".
If the status is Import Error, click the error log link to check the detailed information.
You can convert a Linux or Windows host to an Oracle VM virtual machine template (P2V). The conversion process is similar to downloading a template from an external source.
Before conversion, you need to restart the Linux or Windows computer with the Oracle VM Server CD, and use P2V utility to start the conversion. For more information on how to use the P2V utility, see the Oracle VM Server User's Guide.
During the conversion, you are prompted to enter the number of virtual CPUs and memory size, and this information is configured in the vm.cfg file. The disk size in the virtual machine is determined by the size of the disks you have chosen to be included in the virtual machine. Make sure the Virtual Machine Server has sufficient resources for the conversion (disk space).
The converted virtual machine is a hardware virtualized machine (HVM).
To convert a Linux or Windows host to a virtual machine:
On the Resources page, click Virtual Machine Images, and then click Import.
Select Linux/Windows P2V Import. Click Next.
On the General Information page, enter the following general information:
Server Pool Name: The server pool on which the imported virtual machine is to be located.
Sharing: Whether you want to share this virtual machine, or keep it private.
Private: The virtual machine can only be used by the user who imports it.
Shared (group_name): The virtual machine can be used by members of a specific group.
Virtual Machine Image Name: A name for the imported virtual machine. This must be unique. The name will be used as the name of the directory under /OVS/running_pool, where the files associated with this virtual machine are stored.
Enable High Availability: You can enable high availability for the imported virtual machine. For more information about high availability, see Section 3.5, "Enabling High Availability (HA)".
Operating System: The guest operating system of the imported virtual machine.
Virtual Machine System Username: The user name used to log in to the virtual machine operating system.
Virtual Machine System Password: The password used to log in to the virtual machine operating system.
Console Password: The password for VNC access to the virtual machine.
Confirm Console Password: Confirm the password for VNC access to the virtual machine.
Click Next.
On the Import Information page, enter the host name or IP address of the computer. For example, enter:
hostname.example.com
When using a proxy, select Use Proxy, and enter the proxy address.
Click Next.
Confirm the information.
After importing, the status of the virtual machine is Pending. You need to approve it to make it available. See Section 5.2.5, "Approving the Imported Virtual Machine Image".
If the status is Import Error, click the error log link to check the detailed information.
The imported virtual machine can be one of the following statuses:
Importing: The virtual machine is in the process of being imported.
Pending: The virtual machine has been imported successfully, and is waiting for approval by the Manager.
Import Error: There were errors during the importing process. Click the link to check the error log. You may need to reimport the virtual machine, or delete it.
To search for a virtual machine image:
Click Show Search on the Virtual Machine Images page.
The search criteria include: Virtual Machine Image Name, Server Pool Name, and Status. Use % as a wildcard.
Click Search to display the virtual machine images that match your search criteria.
If an error occurs during downloading from an external source, check if the URL or proxy URL is correct, and then reimport the virtual machine.
To reimport a virtual machine:
On the Virtual Machine Images page, select the virtual machine you want to reimport, and click Reimport.
Enter the URL. When using a proxy, select Use Proxy.
Click Reimport.
The process of approving and managing virtual machine images is similar to that of virtual machine templates. For more information, refer to Section 5.1.5, "Approving the Imported Virtual Machine Template".
After approving, click the Virtual Machines tab, and you can find the virtual machine is displayed in the Virtual Machines list.
You can change the preferred server and other configurations of the imported virtual machine. See Section 6.7, "Editing a Virtual Machine".
To edit a virtual machine image:
On the Virtual Machine Images page, select the virtual machine you want to update, and click Edit.
Update the virtual machine parameters. Click Apply.
For more information about the virtual machine parameters, refer to Section 5.2.1, "Importing a Virtual Machine Image".
To delete a virtual machine image:
On the Virtual Machine Images page, select the virtual machine you want to delete, and click Delete.
If prompted, confirm the delete operation.
You can import ISO files to provide installation media for creating virtual machines. This section includes the following topics:
Common rules about ISO files management:
Any user can import an ISO file.
The Administrator or server pool Manager approves the imported ISO files.
All ISO files of one image should belong to the same ISO group.
All users in the same server pool can share ISO files on the server pool.
Depending on where your ISO files are located, on the Virtual Machine Server, on other computers, or on the Internet, you can import ISO files from different resources as follows:
If you already have some ISO files on your server pool, you can discover and register them in Oracle VM Manager directly.
Before importing, make sure the ISO files are in the folder /OVS/iso_pool/iso_group_name on the Virtual Machine Server. You can also download ISO files from other computers, or from the Internet, and then copy them to this folder.
To select an existing ISO file on the server pool, and register it in Oracle VM Manager:
On the Resources page, click ISO Files, and then click Import.
Select Select from Server Pool (Discover and register). Click Next.
On the General Information page, select the following ISO file information:
Server Pool Name: The server pool on which the ISO file is stored.
ISO Group: The ISO group. One ISO group may contain multiple ISO files. An ISO group is created on the Oracle VM Server by creating a directory under the /OVS/iso_pool/ directory. ISO files must be placed in ISO groups (subdirectories) to be displayed in this field.
ISO Label: The ISO file you want to import.
Click Next.
Confirm the information.
After importing, the status of the ISO file is Pending. You need to approve it to make it available to use. See Section 5.3.5, "Approving the Imported ISO File".
To download an ISO file from outside of the server pool, such as your own HTTP or FTP server, or from the Internet:
On the Resources page, click ISO Files, and then click Import.
Select Download from External Source (HTTP and FTP). Click Next.
On the General Information page, enter the following ISO file information:
Server Pool Name: The server pool on which the ISO file is to be used and stored.
ISO Group: The name of the ISO group. One ISO group may contain multiple ISO files. The name is used to create the directory under /OVS/iso_pool, where the ISO files of this group are stored.
ISO Label: The ISO label used to identify the imported ISO file. For example, enter CD1.
An ISO label must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum label length is 100 characters.
URL: The URL of the ISO file. You can import the ISO file using FTP, or using HTTP. For example, enter an address similar to the following:
http://example.com/el5_img/disc1.iso
ftp://username:password@example.com/el5_img/disc1.iso
When using a proxy, select User Proxy and enter the proxy address. For example, enter a proxy address similar to the following:
http://example.com:8888
Click Next.
Confirm the information.
After importing, the status of the ISO file is Pending. You need to approve it to make it available for creating virtual machines. See Section 5.3.5, "Approving the Imported ISO File".
The imported ISO file can be one of the following statuses:
Importing: The ISO file is in the process of being imported.
Pending: The ISO file has been imported successfully, and is waiting for approval by the Manager.
Import Error: There were errors during the importing process. Reimport the ISO file, or delete it.
Active: The ISO file has been approved, and is available for creating virtual machines.
Inactive: The ISO file is imported successfully, but not available.
To search for an ISO file:
Click Show Search on the ISO Files page.
The search criteria include: ISO Label, Server Pool Name, and Status. Use % as a wildcard.
Click Search to display the ISO files that match your search criteria.
If an error occurs during external import, check if the URL or proxy URL is correct, and then reimport the ISO file.
To reimport an ISO file:
On the ISO Files page, select the ISO file you want to reimport, and click Reimport.
Enter the URL. When using a proxy, select Use Proxy.
Click Reimport.
The process of approving, and managing ISO files is similar to that of virtual machine templates. For more information, refer to Section 5.1.5, "Approving the Imported Virtual Machine Template".
To change the status of the ISO files:
Only active ISO files are available to users.
Note:
Only an Administrator or server pool Manager of the server pool can approve, and manage the imported ISO files and virtual machines.If you do not need an ISO file, or there are errors during the ISO file importing process, you can delete it.
To delete an ISO file, from the ISO page, select the ISO file you want to delete, and click Delete.
You can create shared virtual disks, and use them to expand the storage capacity of your virtual machines. The available virtual disks can also be used by other users in the group.
Oracle VM supports using files as virtual disks. In this case, the prefix of the disk in the configuration file is file. Physical devices can be used, but cannot be changed through Oracle VM Manager. The following is an example of an entry for a file-based disk in the virtual machine configuration file:
disk = [ 'file:/OVS/seed_pool/system.img,hda,w', ]
As well as file-based shared virtual disks, you can share your physical devices (multipath devices, normal Storage Area Network (SAN) LUNS devices, and so on) with all Virtual Machine Servers in the server pool. In this case, the prefix of the disk in the configuration file is phy. Multipath devices can be used, but cannot be changed through Oracle VM Manager. The following is an example of an entry for a multipath disk in the virtual machine configuration file.
disk = [ 'phy:/dev/mpath/mpath1,hdd,w', ]
You must manually configure the multipath device on each Virtual Machine Server in a server pool, then you can add the multipath device to the server pool as a shared virtual disk. The prerequisite steps to use a multipath device as a shared virtual disk are:
Manually set up the SAN connection to the multipath device on each Virtual Machine Server in the server pool.
Manually configure the multipath device on each Virtual Machine Server in the server pool.
Make sure the multipath device has the same device identifier and device path on each Virtual Machine Server in the server pool.
For example, if you want to use a multipath device with the device identifier mpath-36090a028301ffd14fca5a48246976baa a sharable disk for the virtual machines in the server pool, it must have same device path name on each Virtual Machine Server in the server pool, for example, /dev/mpath/mpath1. Do not use the path /dev/mapper/x for multipath devices, only use the path /dev/mpath/x.
Make sure the multipath device is not used for any other purpose (for example, mounted as an FTP server) to avoid any possible data corruption.
For more information on how to assign shared hard disks to a virtual machine, refer to Section 6.7.3, "Storage".
This section includes the following topics:
You cannot create a multipath device to use as a shared virtual disk. You must manually create and mount a multipath device, then import it into Oracle VM Manager.
To create a file-based shared virtual disk:
On the Resources page, click Shared Virtual Disk, then click Create.
On the Add Shared Virtual Disks page, enter or select the following parameters:
Virtual Disk Name: The name of the virtual disk.
A disk name must consist of alphanumeric characters, and must not contain spaces or special characters, except the underscore (_) or hyphen (-) characters. The maximum name length is 200 characters.
Virtual Disk Size (MB): The size of the virtual disk, in MBs. Allocate at least 1024 MB for the virtual disk.
Server Pool Name: The server pool in which the shared virtual disk can be used, and shared.
Group Name: The group that can use this shared virtual disk. You can select one of the following groups:
My Workspace: The virtual disk will be a private one, and only you can use it.
group_name: Select a specific group with whom you want to share this virtual disk. If the virtual disk is available after creation, any member of this group can use it.
Confirm the information you have entered.
A shared virtual disk can be one of the following statuses:
Importing: The shared virtual disk is in the process of being imported.
Pending: The shared virtual disk has been imported successfully, and is waiting for approval by the Manager.
Import Error: There were errors during the importing process. Reimport the shared virtual disk, or delete it.
Active: The shared virtual disk has been approved and is available.
Inactive: The shared virtual disk is imported successfully, but not available.
To search for shared virtual disk:
Click Show Search on the Shared Virtual Disks page.
The search criteria include: Virtual Disk Name, Server Pool Name, Group Name and Status. Use % as a wildcard.
Click Search to display the shared virtual disks that match your search criteria.
You can import a shared virtual disk into a server pool.
To import a shared virtual disk:
Click Import.
Enter or select the following:
Server Pool Name: The server pool in which the shared virtual disk can be used, and shared.
Group Name: The group that can use the shared virtual disk. You can select one of the following groups:
My Workspace: The virtual disk will be a private one, and only you can use it.
group_name: Select a specific group with whom you want to share this virtual disk. If the virtual disk is available after creation, any member of this group can use it.
Shared Virtual Disk Type: The type of shared virtual disk. The disk types you can select are:
File-based Disks: All available file-based disks in the server pool group are discovered.
Multipath-based Disks: All available multipath-based disks in the server pool group are discovered.
Shared Virtual Disk Files: This field is displayed if you select File-based Disks above. A list of all the discoverable shared virtual disks in the group on the server pool.
Multipath Devices: This field is displayed if you select Multipath-based Disks above. A list of all the discoverable shared virtual disks devices in the group on the server pool.
UUID: This field is displayed if you select Multipath-based Disks above. Displays the UUID of the multipath device.
Size (MB): This field is displayed if you select Multipath-based Disks above. Displays the size in MBs of the multipath device.
Description: A description of the shared virtual disk.
Click Next.
Confirm the information you have entered and click Confirm.
The shared virtual disk is imported and available to the server pool.
Note:
Make sure no application is using the virtual disk before you delete it.To delete a shared virtual disk:
Select the shared virtual disk, and click Delete.
Confirm the delete operation.
After you delete the virtual disk, all the files on it will be deleted as well.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
