Anda di halaman 1dari 37

HOL 6767

Managing and Using a Private Cloud


with Oracle VM and Oracle Enterprise
Manager 13c
Christophe Pauliat
Sales Consultant, Oracle Solution Center
christophe.pauliat@oracle.com

CONTENTS
1

INTRODUCTION ........................................................................................................................................... 3
1.1
1.2
1.3
1.4

LAB OBJECTIVE ............................................................................................................................................. 3


PREPARATION (DONE BEFORE LAB) ............................................................................................................... 3
SUMMARY OF STEPS ..................................................................................................................................... 4
GLOBAL PICTURE .......................................................................................................................................... 4
PREPARATION OF THE ENVIRONMENT. ................................................................................................. 5

2.1
2.2
2.3
3

START THE 3 SERVERS (VIRTUALBOX VMS) ................................................................................................... 5


FIX ORACLE VM SERVER DISKS RENAMING (ORACLE VM VIRTUALBOX) ........................................................... 6
FORCE SYNCHRONIZATION OF EM13C AND ORACLE VM MANAGER ................................................................. 8
REQUEST A NEW VIRTUAL MACHINE AS A SELF SERVICE USER .................................................... 11

3.1
3.2
3.3
3.4
3.5
3.6
4

SET THE SELF SERVICE USER PREFERENCES ............................................................................................... 11


CREATE A NEW VIRTUAL MACHINE AS A SELF SERVICE USER ......................................................................... 13
CONNECT TO THE NEW VIRTUAL MACHINE ..................................................................................................... 18
MODIFY A STOPPED VIRTUAL MACHINE AS A SELF SERVICE USER ................................................................... 20
MODIFY A RUNNING VIRTUAL MACHINE AS A SELF SERVICE USER ................................................................... 21
DELETE A VIRTUAL MACHINE AS A SELF SERVICE USER ................................................................................. 22
CHARGEBACK .......................................................................................................................................... 23

4.1
4.2
4.3
4.4
5

INTRODUCTION ........................................................................................................................................... 23
CHARGEBACK INFORMATION SEEN BY THE SELF SERVICE USER ..................................................................... 23
CHARGEBACK INFORMATION SEEN BY THE CLOUD ADMINISTRATOR ................................................................ 24
CHARGEBACK REPORTS .............................................................................................................................. 27
CONFIGURE THE INFRASTRUCTURE ORACLE VM SELF SERVICE PORTAL ................................ 31

5.1
5.2
6

INTRODUCTION ........................................................................................................................................... 31
TEST THE NEWLY CONFIGURED SELF SERVICE PORTAL ................................................................................. 35
APPENDIX A: REFERENCES ................................................................................................................... 36

6.1
6.2
6.3

ORACLE ENTERPRISE MANAGER CLOUD CONTROL 13C DOCUMENTATION ..................................................... 36


ORACLE VM DOCUMENTATION..................................................................................................................... 37
GET THIS DOCUMENT .................................................................................................................................. 37

Last update: September 2, 2016


Author: Christophe Pauliat
Special thanks to: Simon Coter, Simon Hayler

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

1 Introduction
1.1

Lab objective

This document details all actions that we will be run during Oracle OpenWorld 2016 session Hands On Lab HOL6767.
This hands-on lab takes you through private cloud management with Oracle VM and Oracle Enterprise Manager Cloud Control 13c (EM13c)
In this lab, you will play the roles of 3 different people:

The private Cloud administrator (user cloudadm)


o
Configure the infrastructure Self Service portal for the Self Services users
o
Configure Chargeback

A first Self Service user: a developer who needs a complete environment: OS + DB (user dev1)
o
Deploy a new Oracle VM virtual machine with Oracle Linux 6 and Oracle Database 12c

A second Self Service user: IT staff dedicated to the Sales organization: (user salesfr1)
o
Deploy a new Oracle VM virtual machine with Oracle Linux 6 and Oracle Database 12c

Note: in this document, EM13c stands for Oracle Enterprise Manager Cloud Control 13c.

1.2

Preparation (done before Lab)

To save time and fit in the one hour slot of this Oracle OpenWorld lab, some actions were made before the actual lab.
Here is a list of these actions:
o
Install Oracle Linux 7.2 (64 bits) on all the laptops.
o
Install Oracle VM VirtualBox 5.1.4 + extensions on all the laptops.
o
Install an Oracle VM Manager 3.4.1 server in an Oracle VM VirtualBox virtual machine.
o
Install an Oracle VM Server 3.4.1 server in an Oracle VM VirtualBox virtual machine.
o
Install an Oracle Enterprise Manager Cloud Control 13c R2 (beta version) server in an Oracle VM VirtualBox virtual
machine.
o
Deploy an EM13c agent on the Oracle VM Manager.
o
Deploy the Oracle Virtualization plugin on the EM13c server.
o
Deploy the Oracle Virtualization plugin on the EM13c agent.
o
Configure secure/SSL communication between Oracle VM Manager and EM13c agent.
o
Create roles and users in EM13c (Cloud administrator and Self Service users)
o
Create an Oracle VM assembly for the latest Oracle Database 12c (12.1.0.2.0) with Oracle Linux 6
o
Import this Oracle VM assembly in the EM13c software library
o
Configure Chargeback in EM13c (charge plans and cost centers)
o
From EM13c, configure Oracle VM Infrastructure:

register the Oracle VM Manager

discover the Oracle VM Server

configure the Oracle VM networks

create an Oracle VM server pool and Oracle VM zone

create an Oracle VM repositories


o
From EM13c, configure the Infrastructure Self Service Portal for user dev1
Note: Oracle Enterprise Cloud Control 13c R2 beta
During the preparation of this lab, Enterprise Manager Cloud Control 13c R2 was not yet officially released, so we use a beta version.
Enterprise Manager Cloud Control 13c R1 was not an option, because it does not support Oracle VM 3.4.1 (only version 3.3.3 or earlier).
Note: to run this lab at home of office
Requirements: X86 machine with at least 16GB of RAM and 4 CPU cores.
Any X86 Operating System supported by Oracle VM VirtualBox is OK (Microsoft Windows, most Linux distributions, Oracle Solaris X86,
Apple Mac OSX, )
Read appendix A

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

1.3

Summary of steps

In this lab, you will execute the following steps in EM13c :


As the Cloud administrator, setup the Infrastructure environment:
o
Discover the Oracle VM Manager.
o
Discover the Oracle VM Server.
o
Configure network and VNICs (Virtual Network Interface Cards).
o
Create a non clustered server pool.
o
Create a zone.
o
Create a storage repository.
o
Import an Oracle VM assembly in the repository (Oracle Linux 6 + Database 12c)
o
Setup the Infrastructure Self Service portal
o
Configure the Chargeback feature
As a Self Service user:
o
Deploy a new Oracle VM virtual machine from the imported assembly.
o
Access the new VM and database instance
Note: Operations from EM13c graphical desktop
To ease reusability of this lab on any X86 server with any X86 operating system, all operations can be done from the EM13c graphical
desktop (user oracle and password welcome1).
In case you need them, the root password is ovsroot on the 3 Oracle VM VirtualBox virtual machines.
Note: keyboard layout
By default, the EM13c graphical desktop is configured to use a us/qwerty keyboard layout. If you use a different keyboard, you can change
the keyboard layout by clicking on the Linux penguin icon (bottom left corner), then System Settings, then Regional and Language, then
Keyboard Layout. Here you can add another layout and enable it.

1.4

Global picture

The following picture shows all the components with their hostnames and configuration (memory, IP addresses)

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

2 Preparation of the environment.


2.1

Start the 3 servers (VirtualBox VMs)

IMPORTANT: Since the VMs startup takes about 15 minutes on our laptops, we advise you to
start the 3 VMs as soon as possible when you arrive in the room if they are not already
started.
As previously explained, we will use Oracle VM VirtualBox to host the 3 servers (Oracle VM Server, Oracle VM Manager and
Oracle Enterprise Manager Cloud Control) on a single laptop.
Those 3 servers were pre-installed and preconfigured before this lab to save time. Thus, you just have to start them here.
a)

Start the Oracle VM VirtualBox console if not yet started by clicking icon

b)

In this console, you will see the 3 VMs we will use in this lab.

c)

Select the 3 VMs called HOL6767_emcc, HOL6767_mgr and HOL6767_srv

d)

Click the icon

e)

Wait for the 3 VMs to be ready (This will take about 15 minutes)
o
Wait for the graphical environment to be displayed in HOL6767_emcc VM console (auto-login to user oracle)
o
When this environment is displayed, all VMs are ready (since EM13c is the longest to start)

to start them

Note: for this lab, we will work in the Graphical environment of HOL6767_emcc Oracle VM VirtualBox virtual machine, so you can minimize
windows for the other 2 virtual machines (HOL6767_mgr and HOL6767_srv)
Note: If running this lab at office/home on Microsoft Windows machine, you may get a warning about network configuration as the default
VirtualBox Ethernet adapter is called VirtualBox Host-Only Ethernet Adapter instead of vboxnet0 on non-Windows machines.

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

2.2

Fix Oracle VM Server disks renaming (Oracle VM Virtualbox)

Those 3 VMs were created in Oracle VM VirtualBox by import from .ova files. During this import operation, UUIDs of disks are modified (new
random UUIDs assigned). This is confusing for Oracle VM Server when you have Oracle VM Storage repositories. The actions here are done
to fix this.

a)

In the HOL6767_emcc window, click OVM_Mgr to open Oracle VM Manager web console in Firefox
(URL is https://mgr.example.com:7002/ovm/console)

b)

Login to Oracle VM Manager using the following credentials

Username
: admin

Password
: Welcome1

c)

In Servers and VMs tab, click icon

d)

Click srv.example.com then select Physical Disks in Perspective

e)

Select the 2 lines with Event Severity Warning, right click, then click Delete and OK to confirm deletion

f)

Select the 2 remaining lines, then click icon

to expand Server Pools and self_svc_pool

to refresh those 2 physical disks

After refresh, you should notice that a new File System appeared, called fs on 1ATA_VBOX

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

g)

In Storage tab, click Local File Systems

h)

Select the filesystem, then click icon

to refresh this filesystem

After the refresh, you should notice the repository in Location

i)

Present the repository to the server:


o
In Repositories tab, expand Repositories
o

Click self_svc_repo, then click icon

Click icon

to select the only server then click OK

After that, you should see srv.example.com in the Presented to Servers list

j)

Refresh the repository by clicking icon

k)

Migrate discovered VM to the Oracle VM Server:


o
In Servers and VMs tab, click Unassigned Virtual Machines

o
o
o
o
o

Right click the VM with 1300 MB of memory (please ignore the other one with 256 MB of memory)
Click Migrate or Move
Select Migrate a VM to a different Server, Server Pool or Unassigned State
Select Specified Server and srv.example.com
Click Finish

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

2.3

Force synchronization of EM13c and Oracle VM Manager

This is only needed during this hands-on lab because of Oracle VM VirtualBox disk renaming. In real life, you can have auto-synchronization
between EM13c and Oracle VM Manager (needed in case you execute some actions in Oracle VM Manager)

a)

In the Firefox window, click bookmark Enterprise manager 13c to open the EM13c console in Firefox
(URL is https://emcc.example.com:7802/em)
You should see the following login page

b)

Login with the following credentials:


o
User Name
: cloudadm
o
Password
: cloudadm

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

c)

Click Enterprise, Cloud, Oracle VM Infrastructure Home to go to the Oracle VM Infrastructure home page

d)

In the top left corner, click icon

to display the Target Navigation panel.

You should see that the status of the Oracle VM Manager (mgr.example.com) is wrong (white cross on orange background)
e)

Right click mgr.example.com, then click Synchronize to synchronize EM13c with Oracle VM Manager

f)

Click Submit

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

g)

Click Close in the Confirmation window

h)

Wait for a few seconds, then click icon

i)

The Oracle VM Manager should now be ready (green arrow)

j)

Click View, Expand All

(top right corner) to refresh the page.

You should see the complete Oracle VM infrastructure (Oracle VM Manager, Oracle VM zone, Oracle VM Server Pool and Oracle VM
Server, and Oracle VM Virtual Machine (just one).

k)

Log out by clicking CLOUDADM, then Log Out

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

10

3 Request a new virtual machine as a Self Service user


In this chapter, you will request a new virtual machine as the Self Service user called dev1.

3.1
a)

Set the Self Service user preferences


Log in EM13c console with the following credentials:
o
User Name
: dev1
o
Password
: dev1
This user has limited privileges and can only access the Self Service Portals.
You can see the Self Service Portal for 'Infrastructure Oracle VM Cloud Services' in the following picture (default Self Service
Portal for this user)

On the left side, you can see the quotas allocated to this user: this user is allowed to request a maximum of 5 virtual machines (5
Servers), with up to 10 vcpus (virtual CPU or thread), 10 GB of ram and 250 GB of storage.
In the 10 Last requested servers, you can see that this user has already a virtual machine (created on August 9, 2016). This VM is
stopped (red arrow), has 1 vcpu, 1.27GB (1300 MB) of memory and 25GB of disk storage. So far, it costed 297.72$ (see Chargeback
chapter later). Finally, it will expire on August 9th, 2017 (see explanations about expiry date later in this document).

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

11

b)

Set the Self Service user preferences

A Self Service user can enter some preferences for the Self Service Portal (for instance, a default root password for VM, or the email
address for notifications about expiry)
To see/change those preferences, click DEV1, then Preferences, then SSA Portal Settings

You can set General preferences (like email address for instance)

You can also set some preferences for a specific portal (Infrastructure Oracle VM for instance)

In this case, you can see that there is a default root password for the requested virtual machines (it is Welcome1), and also a default zone
(self_svc_zone) and a default source (oracle DB 12.1.0.2 + Linux 6.7).

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

12

3.2

Create a new virtual machine as a Self Service user

a)

Click Request Servers to request a new virtual machine

b)

For zone, leave the default value: self_svc_zone


Note: an Oracle VM Server Pool is a group of one or more Oracle VM Server(s) that can run virtual machines (VM). VMs from the
same Server Pool can be live migrated from a server to another server in the same pool. It is also possible to enable High Availibility at
the VM level to make sure the VM will restart on another server in the same pool in case the original server fails. An Oracle VM zone
contains 1 or more Oracle VM Server Pool(s).
In this lab, due to limited resources available on the laptops, we have a single server (srv.example.com) belonging to a single server
pool (self_svc_pool) and a single zone (self_svc_zone)

c)

For source, leave the default value: Oracle DB 12.1.0.2 + Linux 6.7
This is the Oracle VM assembly you will use to create the virtual machine. You can have many Oracle VM templates and assemblies,
depending on what the Cloud administrator gives you access to.
In this lab, we use a manually created assembly containing Oracle Linux 6.7 + Oracle Database 12.1.0.2 binaries and a very small
database (limited resources).

d)

For Name, leave the default value

e)

Click Next

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

13

f)

Select line containing 1, 1, 64 to display/change the VM parameters

g)

You can enter a root password for the VM. By default, the root password used by this user is Welcome1 (set in the Self Service user
preferences), so just can just leave this password.

h)

You could change the size of the VM (memory and CPU), but please dont because we have very limited resource on the laptop to
run this lab. (we use 1300 MB of memory and 1 virtual cpu)

i)

Tags are optional, but very convenient when you have a huge number of VMs.

j)

Expand the network section (click icon

k)

Select line eth0 and click Edit

l)

You can see that this user can only select network dev_network (restrictions decided by the Cloud administrator)

Select 'Network Profile' in IP Assignement

Scroll down and select dev_netprofile in Network Profile Name

Click OK to close the Edit NIC: eth0 window

in front of Network)

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

14

A network profile is used to automate assignment of static IP addresses to guest virtual machines. A network profile is a list or range
of IP address along with host names. It defines a set of IP addresses, their associated host-names, and common networking attributes
for them.
This dev_netprofile network profile was defined before the lab and contains the following information:
o
Name
: dev_netprofile
o
Domain name : example.com
o
Netmask
: 255.255.255.0
o
Gateway
: 192.168.56.1
o
DNS
: 192.168.56.1
o
IP Address
: Range
o
Range

Hostname Pattern : dev

Start Value
:1

First IP Address
: 192.168.56.11

Last IP Address
: 192.168.56.20
Note: there is a second network profile called prod_network using IP addresses 10.10.10.x, but it is not accessible to this user.
m)

Click Next

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

15

n)

In the 'New Server Request : Schedule' window, you can choose the Start Date (keep Immediately) and the Expiry Date / End Date
(one year from now as set by default by the Cloud administrator).
Note: expiry date
If you choose to have an expiry date for your VM (or if the Cloud administrator forces you to), then the VM will be automatically
stopped and deleted when the expiry date is reached.

o)

Click Next

p)

In the 'New Server Request : Review' window, click Finish to deploy the new VM

Note: before clicking Finish, you could click Save As Deployment Plan to save all parameters in a deployment plan. This can be
useful if you need to create several VMs with the same or similar parameters.
q)

You should get a message saying that the request was submitted successfully

r)

Click icon

to refresh the page.

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

16

You can notice that the quota usage was updated (2 Servers, 2 CPUs, 2.54 GB of memory).
The disk storage consumption is not correct as long as the deployment is not finished (3.34GB is the size of the compressed
assembly. After uncompression, the new VM will use 25GB)
s)

It will take several minutes for the VM creation to be finished, especially because the Oracle VM assembly (source) used will be
imported into the Oracle VM Storage repository (done when the assembly is first used). The deployment of a second VM from this
assembly will be much faster (see deployment of VM by user salesfr1 later in this document).
While waiting, you can go to the next chapter (Chargeback)
Refresh the page until you see the new VM.

The new VM is called dev2.example.com


It is up and running (green arrow)
You can see from this hostname that the network profile was used to allocate the hostname.
Note: you may get another hostname (between dev3.example.com and dev10.example.com)

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

17

3.3

Connect to the new virtual machine

a)

Right click the VM and click Launch VNC Console to get the VM console

b)

Login using the following credentials

Login:
root

Password:
Welcome1

c)

Check the static IP address that was allocated using the network profile
# ifconfig

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

18

You can see that, in this case, the IP address is 192.168.56.12, which matches the hostname dev2.example.com in the network
profile. If you got a different hostname, you should have a different IP address (ex: 192.168.56.13 for dev3.example.com)
d)

Check that you have a small Oracle Database 12c instance called ORCL running in the VM.
# su - oracle
$ sqlplus / as sysdba
SQL> select instance_name,version,status,database_status in v$instance;

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

19

3.4

Modify a stopped virtual machine as a Self Service user

a)

Right click the already existing and stopped VM: dev1.example.com

b)

Click Modify Configuration

c)

On this stopped VM, you can see that you can modify all parameters:
o
Enable High Avaibility
o
Keymap
o
Tags
o
Server Size (Cpu, max Cpu, Memory, Max Memory)
o
Network interfaces (remove existing or add new)
o
Storage (add new storage or attach existing storage volume)

d)

Click Cancel (no need to modify this VM)

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

20

3.5

Modify a running virtual machine as a Self Service user

a)

Right click the new running VM: dev2.example.com then click Modify Configuration

b)

You should see the following picture

You can see that you can modify all parameters while the VM is running except the following ones:

Maximum Memory

Maximum Number of CPUs

Network interfaces
Note: Maximum Number of CPUs
You can increase or decrease the number of cpus of a running VM as long as this number is between 1 and Maximum Number of
CPUs.
Note: Maximum Memory

For PVM (paravirtualized) virtual machines (only available on Linux 5.x and Linux 6.x), you can have Maximum Memory different
than Memory. In this case, you can increase or decrease the amount of memory while the VM is running (cannot have more than
Maximum memory).

For HVM (hardware assisted virtualization) virtual machines, Maximum Memory must be identical to Memory, so it is not
possible to change the amount of memory while the VM is running.

When running Oracle VM Server in Oracle VM VirtualBox (this is the case here), you can only create PVM VMs.
c)

Click Cancel

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

21

3.6

Delete a virtual machine as a Self Service user

Note: this is mandatory to have enough resources available to provision a new VM with user salesfr1 later.

a)

Right click the new running VM: dev2.example.com then click Stop to shutdown the VM

b)

Click Stop in the Confirmation window

c)

Click icon
to refresh the page.
After a few seconds/minutes, the VM should be stopped (red arrow)

d)

Right click the VM then click Delete to delete the VM

e)

Click Delete in the Confirmation window

f)

Click icon
to refresh the page.
After a few seconds, the VM should not be there any more.

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

22

4 Chargeback
4.1

Introduction

Chargeback is a key feature of private clouds. It enables internal and external users of the cloud to be charged depending on the resources
they actually use.
To configure chargeback, the Cloud administrator must define a charge plan and cost centers for users.
A charge plan defines the resources to charge for and their associated rates. Chargeback offers two types of charge plan: the universal
charge plan and extended charge plans. The universal charge plan contains the rates for three common resources: CPU, Memory and
Storage. Extended charge plans provides greater flexibility by adding entity specific charges, for example type of OS (Windows, Linux, ),
Oracle Database edition,
Costs created by resources consumption are assigned to cost centers. Each user has it own cost center. Cost centers are typically
organized in a business hierarchy and may correspond to business unitssales, engineering, human resources, and so forth.

4.2

Chargeback information seen by the Self Service user

a)

From the Self Service portal with user dev1, click icon

to see the chargeback data for this user

b)

You can see the currently used extended charge plan (called cpa_plan)
Expand CPU Rate Factor, Memory Rate Factor and Storage Rate Factor to see all information

You can also see the costs generated by your VMs


By default, costs are calculated every day (automatic EM13c job run every day at 3am)
In this case, there is no cost for the newly created VM, only from the existing VM.
In the bottom on the above picture, you can see that this already existing VM generated a cost of 297.72$ so far. You can also see that
another previous VM (no longer existing) generated a cost of 99.24$
c)

Log out by clicking DEV1 and Log Out

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

23

4.3

Chargeback information seen by the Cloud administrator

a)

Log in as the Cloud administrator


o
User name
: cloudadm
o
Password
: cloudadm

b)

Click Enterprise, then Chargeback


You should see the following screen

In this Home tab, the Cloud administrator can choose several settings:

The Currency Symbol: in our case, it is $ (USD Dollar)

The Peak Times (used if the Cloud administrator wants to charge different prices according to hour/day of the week)

The Uptime Calculations (if Uptime included is selected, then the cost of VMs is adjusted to substract cost when the VM is
not running)
c)

Click Charge Plans tab, then expand plan cpa_plan and click Oracle VM Guest

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

24

You can see details about the currently used extended charge plan, called cpa_plan
d)

Click Cost centers tab, then expand All Users and click Development

You can see that costs for users DEV1 and DEV2 are consolidated in the Development cost center
You can also display this in a tree view (click Tree View in the top right corner)

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

25

e)

Click Entities tab

If you want to manually calculate costs without waiting for the automatic job run at 3am (for instance after modifying the charge plan),
you can click Action, On-demand data collection.
f)

Click Reports tab


Select Aug 1, 2016 Aug 31, 2016 for Date Range and Development for Cost Center then click View report

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

26

4.4

Chargeback reports

As seen in the previous section, the Cloud administrator can view full reports from EM13c, and the Self Service users can view their own
costs directly in the Self Service portal.
Generally, managers and directors want to receive weekly/monthly reports for their teams.
The Cloud administrator can create reports in different formats and send them to the managers/directors.
This can be manual or automatic using Oracle BI Publisher (included and installed with EM13c)
In this case, you will see how to automatically send emails with weekly reports to the director of development.
a)

In Firefox, click bookmark Oracle BI Publisher to open the Oracle BI Publisher WebUI
(URL is https://emcc.example.com:9851/xmlpserver)

b)

Log in as the Cloud administrator


o
User name
: sysman
o
Password
: welcome1
Note: by default, only an EM13c Super-administrator has access to this (sysman for instance).
It is possible to grant access to the Cloud administrator, but this was not done here, so we use the sysman user.

c)

Once connected, click Catalog Folders on the left panel

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

27

d)

Expand (click +) Shared Folders, then Enterprise Manager Cloud Control, then select Chargeback

e)

In Charge Summary Report, click Schedule to configure automatic chargeback reports

f)

In the General tab, select *** Development as the Cost Center.

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

28

g)

Click Output tab

Select the desired format for the report (you can choose between HTML, PDF, RTF, Excel and PowerPoint)

Select Email as Destination Type and click Add Destination

Enter the recipients email (ex: dev_director@example.com)

Enter Subject and Message

h)

Click Schedule tab to define the frequency of reports


For instance, you can select weekly reports sent every Monday at 6am

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

29

i)

Click Notification tab


If needed, the Cloud administrator can ask to receive notifications about those reports

j)

Finally, you would need to click Submit to create the automatic report.
In our case, click Return

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

30

5 Configure the Infrastructure Oracle VM Self Service Portal


Before the Self Service users can create VM from the Infrastructure Oracle VM Self Service Portal, the Cloud administrator must configure
this portal.
This section briefly shows you how to do this for the user salesfr1 (role 0_HOL_SALES)
Note: the portal configuration is done at the role level (not users level). All users having the same role will have the same rights and quotas.

5.1

Introduction

a)

Connect to EM13c Web UI (URL https://emcc.example.com:7802/em in Firefox) with the Cloud administrator user
o
User Name
: cloudadm
o
Password
: cloudadm

b)

Click Setup, Cloud, Infrastructure

c)

Click Request Settings on the left panel

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

31

Those settings are global to all Self Service users.


Some of them maybe be overridden for some specific users (roles)
d)

Click Roles on the left panel then click Assign Quota to Role

Note: so far, only users having role 0_HOL_DEV (users dev1 and dev2) are allowed to use the Infrastructure Self Service Portal.
e)

In the Assign Quotas, Zones & Network profiles to Role window:


o
Select role 0_HOL_SALES
o
Select zone self_svc_zone
o
Enter the following information (resource limits for all Self Service users with role 0_HOL_SALES)

Number of Servers
:3

Number of VCPUs
:6

Memory (GB)
: 10

Local Disk (GB)


: 100
o
Allow Archiving to Software Library : Yes
(see note 1 below)
o
Allow Save to Library on Expiry
: Yes
(see note 2 below)
o
Select Networks
: prod_network
o
Select Network Profile
: prod_netprofile
o
Override Global Request Settings : enabled
o
Future Reservation
: No Restriction
o
Request Duration
: Restricted
o
Default duration
: 1 month
o
Maximum duration
: 3 months
o
Configure EM Agent
: disabled
(see note 3 below)
Note 1: archiving to Software Library
When this is enabled, a Self Service user can archive a stopped VM in EM13c software library as a template. Later, this user will be
able to create a new virtual machine from this template.
Note 2: expiry of virtual machines
If a VM has an expiry date, it will be automatically stopped and deleted when the date is reached (You can have email notifications
before expiry). If Allow Save to Library on Expiry is enabled, then the VM will be automatically archived as a template before deletion,
so the user will be able to recreate a new VM from this template.
Note 3: deployment of EM13c agent in the VM
It is possible to automatically deploy an EM13c agent in the VM during VM provisioning. This will require a few more minutes during
VM provisioning. To save time during this lab, it is disabled. In real life, it is recommended to enable it.

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

32

Click Save

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

33

f)

Click Software Components on the left panel to grant access to Oracle VM assemblies or Oracle VM templates for some role

Note: we only have 1 assembly here, already accessible to users dev1 and dev2 (role 0_HOL_DEV), so we just need to add access to
it for role 0_HOL_SALES

Select line Oracle DB12.. and click Edit


Below Select Roles, click Add
Select role 0_HOL_SALES
Click Publish to grant access to this software component to role 0_HOL_SALES

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

34

5.2

Test the newly configured Self Service Portal

a)

Logout from EM13c

b)

Login again as a new Self Service users (IT person working for the SALES department)
o
User Name
: salesfr1
o
Password
: salesfr1

c)

Click Request Servers

d)

Select source Oracle DB 12.1.0.2 + Linux 6.7

e)

Click Next

f)

Select line 1, 1, 64 to enter parameters

g)

High Availability: leave disabled


Note: when you have at least 2 Oracle VM Server in a Server Pool (not the case here), you can enable HA for a VM. In this case,
Oracle VM will make sure the VM is always on (unless you manually stop it from EM13c or Oracle VM Manager)

h)

Enter and confirm a root password: Welcome1


There is no default password entered for this user, so you must enter a password (see note about Self Service Portal preferences
below)

i)

Expand network

j)

Select line eth0 and click Edit


Note: you can see that this user has only access to network prod_network (dev_network not visible)

k)

Select Network Profile in IP Assignment

l)

Select prod_netprofile in Network Profile Name


Note: you cannot see the dev_netprofile as it is related to a network you dont have access to (dev_network )

m)

Click Next

n)

In the New Server Request: Schedule window, select Indefinitely as the End Date

o)

Click Next
You should get an error because the Cloud administrator does not allow users with this role to request VMs for more than 3 months

p)

Change the End Date to any date before the 3 months deadline and click Next again

q)

Click Finish to launch the deployment of the VM.


Note: this time the deployment of the VM should be much faster than for user dev1 user since the assembly is already imported into
the Oracle VM storage repository.

Congratulations !

You have successfully completed this lab.


We hoped you enjoyed it.

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

35

6 Appendix A: References
6.1

Oracle Enterprise Manager Cloud Control 13c documentation

http://docs.oracle.com/cd/E63000_01/index.htm

Note: Documentation for Enterprise Manager Cloud Control 13c R2 not yet available

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

36

6.2

Oracle VM documentation

http://docs.oracle.com/cd/E64076_01/index.html

6.3

Get this document

This document is available online at http://blogs.oracle.com/cpauliat/entry/hol_oow2016

Oracle Corporation, World Headquarters

Worldwide Inquiries

500 Oracle Parkway

Phone: +1.650.506.7000

Redwood Shores, CA 94065, USA

Fax: +1.650.506.7200

CONNECT WITH US

blogs.oracle.com/oracle

twitter.com/oracle

Copyright 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission.

oracle.com

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

facebook.com/oracle

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0916

HOL6767: MANAGING AND USING A PRIVATE CLOUD WITH ORACLE VM AND ORACLE ENTERPRISE MANAGER 13C

37