04 Setting Cloud for IaaS 3
Overview
I am continuing on from 03 Setting Cloud for IaaS 2 to set up a private cloud.
References
- Oracle® Enterprise Manager Cloud Administration Guide 12c Release 3 (12.1.0.3)
- 4 Setting Cloud for IaaS
- 4.9 Registering Storage Servers
- 4.9.1 Registering the File Server
- 4.9.2 Registering the Storage Array
- 4.10 Creating a Storage Repository
- 4.11 Presenting the Storage Repository
- 4.12 Using Self Update to Download Oracle VM Templates and Virtual Assemblies
- 4.13 Importing Assemblies, Templates, and Virtual Disks into the Storage Repository
- 4.14 Creating a Virtual Server Pool
- 4.15 Creating a Zone
- 4.16 Setting Up the Storage Quality of Service (QoS)
- 4.9 Registering Storage Servers
- 4 Setting Cloud for IaaS
Procedure
Setting Up File Shares
Two (2) file shares are registered on NARRABRI:
OEM_Staging
for the staging area used by OEMOVM_Repository
for the repository used by OVM
Settings for OEM_Staging
Only NFS is enabled with read/write access by any host for OEM_Staging, as shown below:
And anyone can read and write to the NFS share as shown below:
Settings for OVM_Repository
The settings for OVM_Repository are the same as for OEM_Staging.
4.9 Registering Storage Servers
Followed the procedure in 4.9 Registering Storage Servers to set up NFS and iSCSI.
4.9.1 Registering the File Server
As described in 4.9.1 Registering the File Server, I registered a File Server on NARRABRI with the following parameters:
Two (2) NFS shares are exposed:
Note: For each exposed share, I also did a Refresh operation by selecting the share first then clicking on the Refresh button. This is needed to be done so that the creation of the storage repository can proceed.
I also added the following comments for each share (via the Edit button):
Name
nfs:/data/OEM_Staging
nfs:/data/OVM_Repository
Description
Staging area for patches and software used by OEM
OVM repository
4.9.2 Registering the Storage Array
Following the procedure in 4.9.2 Registering the Storage Array, I registered an array of iSCSI LUNs as follows:
However, the problem is that there are no physical disks in this storage array:
I will leave this mystery until later.
4.10 Creating a Storage Repository
Following the procedure in 4.10 Creating a Storage Repository, I created the storage repository with the following details:
The result is as follows:
The storage details for the Narrabri NFS now looks like:
4.11 Presenting the Storage Repository
Following the procedure in 4.11 Presenting the Storage Repository, I ended up with the following result:
4.12 Using Self Update to Download Oracle VM Templates and Virtual Assemblies
Following the procedure in 4.12 Using Self Update to Download Oracle VM Templates and Virtual Assemblies, I downloaded and applied Oracle Linux OL6.2 for x86_64 PVM as shown below:
4.13 Importing Assemblies, Templates, and Virtual Disks into the Storage Repository
Following the procedure in 4.13 Importing Assemblies, Templates, and Virtual Disks into the Storage Repository, I tried to import into Assembly from Software Library Component as shown below:
It looks like I skipped a step somewhere as I got the following error message:
(This is done in 4.16.4 Configuring the Software Library User with External Management Agent below.)
However, I was able to import an ISO image from the Software share that I created on NARRABRI which is accessible at ftp://?uname?:?pwd?@narrabri.yaocm.id.au/Software/V41362-01.iso
(where ?uname?
and ?pwd?
are replaced by the appropriate username and password for access to the NARRABRI NAS. The result is shown below:
4.14 Creating a Virtual Server Pool
Following the procedure in 4.14 Creating a Virtual Server Pool, I created a single pool as I only have one (1) VM server: VICTORIA.
First, I created a new NFS share on NARRABRI called Victoria_Share using a similar procedure described above. I ran a discovery on Narrabri NFS to discover all shares, and then:
- Ran a refresh on
nfs:/data/Victoria_Share
—successful - Tried to delete
nfs:/data/Software
—failed with the following message: - oracle.sysman.vt.ovm.integration.api.EMOVMCommunicationServiceException: 5047: Error while performing the operation: Commiting the ovm job EM_DeleteFileSystem_nfs:/data/Software_2014-06-09_16-52-02-664 failed.[com.oracle.ovm.mgr.api.exception.RuleException:OVMRU_002013E: File system delete is not supported by generic plugin associated with this file server : Narrabri NFS. [Mon Jun 09 16:52:02 EST 2014]]
The final status of the file systems on Narrabri NFS is:
I created a virtual server pool with the following settings:
Note: The Virtual IP address has to be on the same subnet as the pool VIP, otherwise the following message is raised:
Error when invoking OVM API oracle.sysman.vt.ovm.integration.api.EMOVMCommunicationServiceException: 2002: Error while performing the operation: Commiting the ovm job EM_AddServer_victoria.yaocm.id.au_ToPool_Home_2014-06-09_17-11-28-974 failed.[com.oracle.ovm.mgr.api.exception.RuleException:OVMRU_000030E Cannot add server: victoria.yaocm.id.au, to pool: Home. Server Mgt IP address: 192.168.1.100, is not on same subnet as pool VIP: 192.168.2.1. [Mon Jun 09 17:11:29 EST 2014]]
Updated IP Addresses to register 192.168.1.105 as being used.
4.15 Creating a Zone
Following the procedure in 4.15 Creating a Zone, I created a zone with the following settings:
4.16.3 Configuring the Software Library User
Following the procedure in 4.16.3 Configuring the Software Library User, I granted view access to the named credential called HOST_ORACLE (which is the credential used by the oracle user to access hosts). The result is as follows:
4.16.4 Configuring the Software Library User with External Management Agent
Following the procedure in 4.16.4 Configuring the Software Library User with External Management Agent, CLOUD_SWLIB_USER is granted Execute privileges on melbourne.yaocm.id.au
. The result is as follows:
Import OEL 6U2 Assembly
With CLOUD_SWLIB_USER set up correctly, I am now able to import the downloaded assembly, Oracle Linux OL6.2 for x86_64 PVM, by following the procedure in 4.13 Importing Assemblies, Templates, and Virtual Disks into the Storage Repository. I ended up with the following new components:
This assembly consists of one (1) VM Template:
This VM Template has one (1) Virtual Disk:
Other Steps
I did not set up the following options:
- Setting Up the Storage Quality of Service (QoS)
- Patching the Oracle VM Server
- Acknowledging OVM Events
- Managing the NTP Configuration
- Importing Virtual Machines
- Acknowledging the Repository Events