Friday Sep 21, 2012

So far in this series we have looked at creating asset within the
EMOC BUI but the Exalogic 2.0.1 installation also provide the Iaas
cli as an alternative to most of the common functionality
available within EMOC. The IaaS cli interface provides access to
the functions that are available to a user logged into the BUI
with the CloudUser Role.

As such not all functionality is available from the command line
interface however having said that the IaaS cli provides all the
functionality required to create the Assets within a specific
Account (Tenure). Because these action are common and repeatable I
decided to wrap the functionality within a simple script that
takes a simple input file and creates the Asset.

Following the Script through will show us the required steps
needed to create the various Assets within an Account and hence I
will work through the various functions within the script below
describing the steps.

You will note from the various steps within the script that it is
designed to pause between actions allowing the proceeding action
to complete. The reason for this is because we could swamp EMOC
with a series of actions and may end up with a situation where we
are trying to action a Volume attached before the creation of the
vServer and Volume have completed.[Read More]

Thursday Jul 26, 2012

Before we can create Virtual Servers within Enterprise Manager
Ops Centre (EMOC) we will need to import an appropriate Server
Template that will be used to create the Virtual Server. Server
templates are associated with accounts and hence may be imported
on an account by account basis or for common base templates we can
import them once and make them Public. Once we have configured the
imported template to be Public it will be available to all
accounts and users.

Serve templates can be uploaded to an account in 3 simple steps
although this initial upload will make the template private to an
account its properties can be set to public by simply changing the
"Public" flag within the account Server Template tab. The
following steps are required to import a template and make it
public.

Once we have created our Users and Networks we will want to
enable the Virtual Data Centre (vDC) for access by the Cloud
Users. To facilitate this we will need to create Accounts within
the vDC / Cloud and allocate the users to these accounts. Once a
Cloud User has been allocated to an account they will be able to
access that account and hence create / manage Virtual Servers
within that account / Pool.

To create an Account within a vDC / Pool you will
need to be logged into Enterprise Manager Ops Centre (EMOC) with
the appropriate Role, and this is generally done using you Cloud
Administrator, then simply navigate to the vDC Management
Accordion, vDC, your Cloud and finally Accounts.

By default once a Network has been created within the Enterprise
Manager Ops Centre (EMOC) it can be allocated to vServers during
their creation. At this point an IP Address will be allocated
automatically from the pool of Allocated IPs associated with the
Network and Account combination.

In many customer solutions the vServers will need to be allocated
a specific IP address so that they can be accessed externally at a
know location. To achieve this we must Allocate a number of vIPs
within the range allocated to the Account. This is done on an
Account by Account basis as follows.

In the majority or Real World scenarios we will need to access
the Virtual Servers running within the Exalogic from an external
client network. To facilitate this we will want to leverage the
10Gb Ethernet connection and hence we will need to create 1 or
more EoIB networks that can be accessed by the Virtual Servers.

During the installation of the Exalogic 2.0.1 Virtual environment
we create a single "EoIB-external-mgmt" network that we could, in
theory, use to access the Virtual Servers we create. Although this
is possible, assuming it has enough IP Address, this would be bad
practice because this network is intended solely for management
functionality and access to the Control VMs. Therefore to provide
the Virtual Servers with external Ethernet access we will need to
create additional EoIB interfaces. Each of these will need to be
VLAN tagged to provide network isolation and partitioning.

Creating Cloud Users and Administrators will be one of the first
tasks when setting up a new Exalogic 2.1 environment. We will step
through the simple process of creating users and describe a few
key user types. Initially we will need to login as either the root
user or the exl-admin user.

Before adding users to the Exalogic 2.1 environment they must
exist as either local users on the physical machine running the
Exalogic Control Virtual Server or existing within an appropriate
repository, LDAP etc, used by the machine for authentication. This
is required because Enterprise Manager Ops Centre 12c (EMOC) does
not store any account authorisation information instead this is
left tot he underlying OS. It is assumed within this blog that
this has been done.

Wednesday Jul 25, 2012

With the release of Exalogic 2.0.1 and the new Virtual Environment I
have put together a number of short blog entries in a Tea Break
Snippets series that will take the user though various standard
functionality and processes associated with new Exalogic
Implementations.

Monday Mar 12, 2012

At the Oracle Open World 2011 conference, I had presented a session titled "Enterprise-class SOA on Exalogic"
along with Vikas Anand and Manas Deb. Exalogic is part of Oracle's new
breed of engineered systems, and is geared towards the middleware space.
For those new to the term, an 'engineered system' is one where a single
vendor provides everything from hardware, network, OS, middleware,
applications, etc in one appliance. The hardware and software are fully
integrated out of the box and designed for... read more

About

The primary contributors to this blog are comprised of the Exalogic and Cloud Application Foundation contingent of Oracle's Fusion Middleware Architecture Team, fondly known as the A-Team. As part of the Oracle development organization, The A-Team supports some of Oracle's largest and most strategic customers worldwide. Our mission is to provide deep technical expertise to support various Oracle field organizations and customers deploying Oracle Fusion Middleware related products. And to collect real world feedback to continuously improve the products we support. In this blog, our experts and guest experts will focus on Exalogic, WebLogic, Coherence, Tuxedo/mainframe migration, Enterprise Manager and JDK/JRockIT performance tuning. It is our way to share some of our experiences with Oracle community. We hope our followers took away something of value from our experiences. Thank you for visiting and please come back soon.