Dear Readers,
My name is Franz Devantier, creator of this blog. I am an Oracle Certified
Professional (OCP DBA 11g) Security DBA.
I will be sharing with you the basic duties of an Oracle DBA, and also
some of the undocumented, and not so well known tasks.
I will make a deal with you: If you refer me to a company that needs
database support, from a few hours per week to full time, and I am able to sign
a contract with them.
Then I will give you 10% of the monthly
contract or deal price every month. When
the contract ends, and we re-sign the contract, I will again give you 10% of
the monthly contract price. This will go
on until the company no longer employs or contracts me or my agents to look
after their databases.
I can do this, because that 10% is my
marketing budget. When we re-sign the
contract, in the future, it may depend on you giving the thumbs up again, and
that is worth 10% of the monthly contract price, to be given to you as
commission.
Contact:
Franz
Exalogic
Task Overview Concepts - Part 1
Task Overviews and Basic Concepts
There are various tasks that are split between the users:
. Exalogic Systems Administrator
. Cloud Administrator
. Cloud User
Cloud Administrator Tasks
Account Creation
The Account will enable and entitle the Cloud Users the
authorization to use the computing, network, and storage resources of the
Exalogic vDC. The Account provides the
required capabilities to manage all of these resources.
Before you create an account:
-> Estimate the
resource quotas to be allocated for the account
-> Identify the
Cloud users to be assigned to the new Account
You define the quota for vCPU, memory, and storage
resources during the Account creation process.
In the Account Creation Wizard, the Resource Quota information is
displayed, and indicates how much of the corresponding vDC resources can be
used or allocated. You will also be able
to see if the vDC resources are oversubscribed or undersubscribed.
You will continue by setting the Account to be able to
create a certain number of private vNets.
The maximum number is 4096 private vNets. Then you will go on to look at defining your
private networks. The maximum number of
allowable defined private networks, is a function of the server pool
configuration that is defined in the Exalogic vDC. Within each server pool, you can create a
maximum number of 64 private networks.
Some of the number up to 64 are already defined for use by the Exalogic
control, so you will have to settle for a few less than 64.
When you create an Account, the public networks that are
available in the vDC are listed. From
this listing you can set the number of public IP addresses allocated to the
Account. The public IP addresses can be
used by the Cloud User to assign to the vServer, as required. You have the option to decide which defined
public networks will be available to a specific Account.
The virtual resources for an Account are controlled by
means of an Entitlement that you will set up during Account creation. To allocate resources to an Account, you
allocate them from the vDC. You can
oversubscribe the total allocation of resources for all the accounts in a vDC,
which means that there are more resources allocated than the actual resources
in the vDC. You need to plan the
allocation of resources properly, in order to avoid oversubscribing the
vDC. You will need a carefully worked
out resource plan, and update the resource configuration when the need
arises. If an Account user does not have
sufficient resources, then that Cloud User will get notifications that they
cannot create vServers, for example, because there are not enough resources
available.
As
the Cloud Administrator, you need to monitor the resource usage and
re-configure resources when required.
You will need to create as many Accounts as your business requires. You can partition the Exalogic vDC by
Account. The separation of the Accounts
is based on resource allocation.
Account Management
The
Cloud Administrator has a lot of power.
The Cloud Administrator can update the resource configuration for an
account. He can assign Cloud Users to
the Account. He can delete an Account.
The
Cloud Users can be assigned to the Account during the account creation or done
separately afterwards. A Cloud User only
has access to the Accounts that the Cloud Administrator has added them to. The Cloud Administrator can manage the access
of all the Cloud Users, to all of the Accounts in the Exalogic vDC.
vServer Type Creation
vServer
Types are profiles of virtual machines that define the computing resources, for
example the CPU, memory, and storage size.
A Cloud User is restricted to using these definitions in order to
implement and create vServers. A vServer
Type that has been created, is available for all the Accounts in the Exalogic
vDC.
The
Cloud Administrator, can capture the user requirements and create different
vServer Types. There are also some
default system-defined vServer Types that are available in the Exalogic vDC.
->
EXTRA_LARGE vServer: This has 16GB of
memory, and 4 vCPUs.
->
LARGE vServer: This vServer has 8GB of
memory, and 2 vCPUs.
->
SMALL vServer: This vServer has 4GB of
memory and 1 vCPU
The
Cloud Administrator can create and delete vServer Types. However the Cloud administrator, can delete
the system-defined vServer Types. These
three system defined vServer Types are always present. When you create a vServer Type in the wizard,
the VM hosting details display some information that is based on the resources
defined in the vDC.
->
The number of Oracle VM Servers that are in the Exalogic vDC, and that they
will have sufficient resources to host the vServer that has been defined with a
set of resources.
->
There is an estimation of the number of vServers that can be hosted with the
total number of physical resources of the vDC.
->
A warning message will display, when the defined value for the memory size of
the vServer, exceeds the available storage in the vDC.
Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com
No comments:
Post a Comment