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.
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.
Subscribe to:
Posts (Atom)