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 2
Cloud User Tasks
A Cloud User who has been granted access to an Account has
all the privileges needed to manage and use the Computing, Network, and storage
resources in an Exalogic vDC. This would
be within the limitations of the quotas that were granted to the Account that
the Cloud User is working in.
Cloud Users can create vServers, and manage the entire life
cycle of the vServer , which they may be doing for their applications. These are the resources that a Cloud User
can manage:
-> Virtual Network resources
-> Server templates
-> Virtual Storage Resources
-> Distribution Groups
-> vServers
Virtual Network Resources
A Virtual Network will restrict the network connectivity of
a vServer. Virtual network management
will involve connecting and restricting the network access to vServers. A Cloud User can see the following types of
virtual networks:
-> Public External Networks
These are defined by Cloud Administrators. Cloud users can’t create, update, or delete
this type of vNet. This type of virtual
network can be shared among many Accounts in an Exalogic vDC. If a vServer is a member of a Public External
vNet, then it will also have external communication beyond the Exalogic
vDC. Such vServers can be used to host
public services. A separate IP address
is allocated for this type of virtual network.
-> Private vNets
These Private vNets are defined by Cloud Users, according
to their requirements, and within the limits of the Account quota. A private vNet is created based on the
private network of the network domain of the Exalogic vDC. Private vNets are only accessible within an
Account. All vServers that have
membership of a private vNet in common with other vServers, can communicate freely
throughout that subnet.
The Cloud User defines the private vNets to which vServers
are assigned. Membership of a vServer to
one or more vNets can only be specified at the vServer creation time. Cloud Users can also reserve a number of IP
addresses from any existing virtual network.
Reserved IP addresses can be used later on for static allocation to
vServers.
When creating vServers, a Cloud User can choose different
methods to allocate IP addresses to a vServer.
-> Static Method
With the static method you require a reserved IP address,
from each selected virtual network to the vServer. You can only use this method, when you are
creating a dingle vServer at a time.
-> Automatic Method
This method of doing it will dynamically allocate an IP
address from each selected virtual network.
This method is good if you are creating multiple vServers at a time.
A
Cloud User can when required release a reserved IP address that is not
allocated to a vServer. On the other
hand IP addresses that are dynamically allocated to vServers are released
automatically when the vServers are deleted.
A
vNet has a number of attributes that are visible to Cloud Users:
->
Name: An identifier in the system for
the vNet.
->
Description: This is descriptive test for the vNet.
->
Type: This can be a Private vNet, or a
Public External vNet.
->
Subnet: This attribute defines the IP address range for a vNet.
->
Allocatable Addresses: This is the maximum number of IP addresses that can be
allocated to vServers from a vNet.
->
Reserved Addresses: This is the number of reserved IP addresses.
->
Status: This is the current status of the vNet.
Tags: This is the available tags for a vNet. Tags can be used for better identification
and classification of the vNet.
Server
Templates
A
Server Template is an OS image that can be used to create a vServer. The OS image needs to be in a certain
format. Server templates are specific to
the processor architecture of the server pool and virtualization type. You need to have a server template for
creating vServers.
Server
templates are loaded into the central software library associated with the
Exalogic vDC, and they can’t be changed later on. Server templates are bound to a specific
Account by default. Inside the Exalogic vDC,
you can register a server template for public use within any Acccount.
You
can also upload a new server template, to be used for creating vServers. There are a number of attributes of a server
template that are visible to Cloud Users.
->
Name: This is an identifier within the system for the server template.
->
Description: This is descriptive text for the server template.
->
Size: This refers to the size of the server template in GB.
->
Memory: Memory that has been defined for the server template in GB
->
OS: This is the type of operating system that is defined for the server
template.
->
CPUs: This is the number of CPUs defined for the server template.
->
Assembly: This is the name of the assembly of the server template. This field is empty because you are uploading
the server template using a template sub-type file.
->
Public: This filed indicates if the server template is shared with other
Accounts in the Exalogic vDC.
->
Tags: All the available tags for a server template. Tags can be used for better identification
and classification of the server template.
Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com
No comments:
Post a Comment