In the blog entry "Exalogic Virtual Tea Break Snippets - Create Assets Evolution" I described how the our asset / asssembley creation scripts had evolved to Python as a processing language and JSON as a file format. As part of that blog I briefly described the assembly configuration section and how it defines scripts that can be executed on the previously created vServers. Within this blog I intend to provide a Cookbook for using the new functionality to install and configure a simple OTD / WLS installation consisting of 3 OTD vServers and 3 WLS vServers linked over the Infiniband network. All scripts associated with the process can be found in Exalogic A-Team Tools folder (/exalogic-att) on the downloadable PythonUtilityTemplate and with some simple tweaks you should be able to build your own test environment.
Cyberspace is big. You just won't believe how vastly, hugely, mind-bogglingly big it is.
Showing posts with label IaaS. Show all posts
Showing posts with label IaaS. Show all posts
Friday, 11 July 2014
Friday, 20 June 2014
Exalogic Virtual Tea Break Snippets - Pythonised SimpleExaCli
Having completed the CreateAssembly (Create Assets) re-write of the SimpleExaCli I decided it was time to migrate some of the additional functionality I use and enhancing the outputs to match my requirements. This quick blog entry will describe the currently migrated commands and their new output structure. In accordance with my previous CreateAssembly blog I have split the functions into smaller commands and subsequently wrapped calls to these into a top level SimplePythonExaCli.sh. Although this is not a full re-write the list of functions will grow but currently comprise of the following:
Each will be described in more detail but all follow the same underlying principles on parameter requirements and processing described below.
Each will be described in more detail but all follow the same underlying principles on parameter requirements and processing described below.
Friday, 6 June 2014
Exalogic Virtual Tea Break Snippets - Create Assets Evolution
Following the success of the CreateAssets shell script and it's subsequent merging into the SimpleExaCli script I decided to extend the features and leverage the full functionality of the 2.0.6.x (Echo) IaaS. As part of the revisit of the code a rewrite in python was performed and the primary reason for this was it allowed for simple coding to read and access the new JSON format definition file. The additional flexibility that the python language allows provided a framework within which we can build a simple assembly builder.
Because I have chosen to use Python 3 and the pexpect libraries this version of the CreateAssets functionality will only be released as a vServer Template, that is an extension of the Echo template described here, and can be downloaded from the link below.
The rest of this blog entry will describe the new calling mechanism and focus on the new structure within the JSON files. The scripts and files described can all be found within the examples directory in the template.
Because I have chosen to use Python 3 and the pexpect libraries this version of the CreateAssets functionality will only be released as a vServer Template, that is an extension of the Echo template described here, and can be downloaded from the link below.
The rest of this blog entry will describe the new calling mechanism and focus on the new structure within the JSON files. The scripts and files described can all be found within the examples directory in the template.
Tuesday, 3 June 2014
Exalogic Virtual Tea Break Snippets – IaaS Utility vServer
Following a number of discussions around the SimpleExaCli
Script and the ModifyLVM
Script that are available from this blog site I decided to
package the scripts and any future scripts within a simple Utility
vServer that was then converted to a template using the SimpleExaCli
script. The advantage of constructing this standard utility
vServer is that it can be configured in an appropriate manner to
allow simple use of all the scripts to control and configure your
Exalogic Environment.
The Utility vServer currently comes in two flavours 2.0.4.x (Navstar) and 2.0.6.x (Echo) the key difference being the version of the IaaS Cli installed and hence the appropriate version should be downloaded and are available here.
The Utility vServer currently comes in two flavours 2.0.4.x (Navstar) and 2.0.6.x (Echo) the key difference being the version of the IaaS Cli installed and hence the appropriate version should be downloaded and are available here.
Wednesday, 14 August 2013
Exalogic Virtual Tea Break Snippets – Creating Assets with the Simplified Exalogic Cli (A SimpleExaCli.sh Tutorial)
In a previous blog entry I described a script for creating
assets (Distribution Groups, vServers, etc) but since that initial
script I have written and blogged about the Simple Exalogic Cli Script
and therefore have decided to write this short tutorial on the
"--create-asset" command option. This version is expanded from it's
original release last September so I will run through all the features
available within this command.
Tuesday, 30 July 2013
Exalogic Virtual Tea Break Snippets - Modifying Memory, CPU and Storage on a vServer (A SimpleExaCli.sh Tutorial)
With the current release of Exalogic Virtual the Enterprise Manager Ops
Center interface does not provide a support method for increasing the
reasources associated with a running vServer. Therefore to increase the
CPU, Memory or Disk size of a vServer we need to recreate vServer using
the same Network information, mapped storage etc but with the new CPU,
Memory and Disks space. Rather than simply destrying and then manually
recreating the vServer we can use the SimpleExaCli.sh script described
in the blog entry "Exalogic Virtual Tea Break Snippets - Simplified Exalogic IaaS Cli"
to first create a template and capture the network information. Then
using the generated Template and captured information to recreate the
vServer with a new "VServer Type" that defines the new resource
requirements. This blog entry will take you through the simple process
of resizing the resources associated with an already existing Exalogic
vServer.
Tuesday, 23 July 2013
Exalogic Virtual Tea Break Snippets – Simplified Exalogic IaaS Cli
In previous blogs I have built and documented a number of extensions
to the standard Exalogic IaaS Cli that either simplify the Cli usage or
provide additional functionality. Following feedback from the various
user I have enhanced and amalgamated a number of my scripts into a new
single “SimpleExCli.sh”. In addition the SimpleExCli.sh script contains a
number of new options for creating and managing vServers within your
Exalogic environment.
The aim of this blog entry is to introduce the new script and document the commands available providing a starting point for script usage. I will produce a number of additional short targeted tutorials that will work through the individual commands in more detail.
The aim of this blog entry is to introduce the new script and document the commands available providing a starting point for script usage. I will produce a number of additional short targeted tutorials that will work through the individual commands in more detail.
Monday, 1 July 2013
Exalogic Virtual Tea Break Snippets - Power Cycling Your Virtual Exalogic Rack
On rare occasions you may need to Power Cycle / Shutdown your
Virtualised Exalogic Rack. Although the Power Cycle for the
Physical Rack is documented in the "Exalogic
Machine Owners Guide" and the Control Stack procedure is
defined within a MOS note we do not have a single source that
documents the Power Down / Power Up procedure for a fully
Virtualised Exalogic Rack. This simple short blog entry will bring
the distributed information into a single location and will also include the processes required for guest vServers.
At a High level the Power Cycle procedure is as follows:
At a High level the Power Cycle procedure is as follows:
Power Down
- Shutdown all guest vServers.
- Shutdown Control vServers (Control Stack).
- Power down Physical Rack.
Power Up
- Power Up Physical Rack.
- Start-up Control vServers
- Start-up guest vServers.
Tuesday, 26 February 2013
Exalogic Virtual Tea Break Snippets - Wrapping the Exalogic iaas cli
Having worked with the Exalogic Command Line for a while I
decided to wrap some of the common functions in a simplified bash
script. This saves me creating the keys, connecting and
identifying the appropriate Ids. Instead I can simply specify the
Name and the script will do the rest of the work. This initial
version has just a few commands in it but as I add more the blog
entry will expand, as will the script, and document the new
functionality.
Monday, 25 February 2013
Exalogic Virtual Tea Break Snippets - Cloning an existing vServer
Following on from my Blog entry "Scripted
Template Generation from an existing vServer" I have built a
wrapper script that can be used to execute the Template Generation
script or Clone a specific vServer. This script was not
incorporated into the original script because it must be executed
on a Compute Node with access to the /OVS/Repositories directory
and the Compute Node are a minimal install and hence do not have
all the required software available. As part of the Cloning
process this new script will create an Assets input file that can
be used with the CreateAssets.sh describe in the blog "Scripting
Asset Creation" and optionally execute the result to create
the clone.
Friday, 21 September 2012
Exalogic Virtual Tea Break Snippets - Scripting Asset Creation
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.
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.
Subscribe to:
Posts (Atom)