Functional Overview
Through coordination, the following becomes possible:
Virtual L-Server Creation [Solaris Zones (Solaris 10)] [OVM for SPARC]
Registering BMC BladeLogic Server Automation with Resource Orchestrator as server management software enables creation of virtual L-Servers.
Virtual L-Server Operation [Solaris Zones (Solaris 10)] [OVM for SPARC]
Registering BMC BladeLogic Server Automation with Resource Orchestrator as server management software enables operations such as migration of virtual L-Servers between servers.
Function Details
Virtual L-Server Creation
For details on how to design a virtual L-Server, refer to following manual.
[Solaris Zones (Solaris 10)]
"E.6 Solaris Zones" in the "Design Guide CE"
[OVM for SPARC]
"E.7 OVM for SPARC" in the "Design Guide CE"
For details on how to create a virtual L-Server, refer to following manual.
[Solaris Zones (Solaris 10)]
"8.7 Solaris Zones"
[OVM for SPARC]
"8.8 OVM for SPARC"
Virtual L-Server Operation
For details on how to operate virtual L-Servers, refer to "Chapter 17 L-Server Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Installing BMC BladeLogic Server Automation
Install BMC BladeLogic Server Automation referring to the BMC BladeLogic Server Automation manual. The following are advisory notices regarding coordination with Resource Orchestrator.
Installation Order
The order of installation of Resource Orchestrator and BMC BladeLogic Server Automation is not important. Therefore, you can install in any order you like.
However, when BMC BladeLogic Server Automation is installed after this product, rebooting is necessary to make this product recognize the environment variables added at the time of installation of BMC BladeLogic Server Automation.
Manager Installation
It is possible to install the Resource Orchestrator manager and Application Server (the BMC BladeLogic Server Automation manager) on the same server or on separate servers.
Note
When registering BMC BladeLogic Server Automation with Resource Orchestrator as server management software, it is recommended to install it on the same server. However, when operating Resource Orchestrator managers in clusters, it is recommended to install it on a different server.
Required Coordination Components
Please install BMC BladeLogic Server Automation Console on the server on which the Resource Orchestrator manager is installed.
When creating and operating virtual L-Servers of Solaris zones (Solaris 10), introduce a RSCD agent in the global zone.
For details, refer to "E.7.2 Preparations for Servers" in the "Design Guide CE".
Setup Procedure
After installing BMC BladeLogic Server Automation, perform the following settings on the admin server. For details, contact Fujitsu technical staff.
Create Users
Create the user for coordination with Resource Orchestrator.
Make the user name "ServerAdmin".
Configure the "BLAdmins" role for the role of the "ServerAdmin" user.
Create Authentication Files
Use the bl_gen_blcli_user_info command and create an authentication file for the user created in 1.
The path and name for the file to create are as below.
[Windows]
BladeLogic_installation_folder\user
[Linux]
/opt/bmc/bladelogic/user
user_info.dat
Create Authentication Profiles
Create an authentication profile with the name "server-profile".
Specify "SRP" for the authentication method.
Confirm the Connection
Login to the admin server as the "Administrator" for Windows, or the "root" for Linux.
Start the BladeLogic console, and connect to the Application Server.