Thursday Jun 25, 2009
Announce: EMRA v6.2-0.06 Uploaded
The EMRA Toolkit v6.2-0.06 is ready for download. The changelog for this latest version is shown below:
Changelog for The EMRA Toolkit
v6.2-0.06
==========
General Information
Date : 25-Jul-2009
Purpose : Updated to support Comms Suite 6 update 2
scripts/common.directory_svr.configure.sh
When creating a directory server instance, one must also
include the dirmanager DN otherwise it will default to
"cn=Directory Manager". This will lead to cases where the
dirmanager_dn in the emra.conf is different and the directory
server is not maneagable because of the differing DN value
scripts/axs-mgr.commcli-modify-domain-params.sh
Added logic to detect if the preferred webcontainer is either
application server or webserver. Given that one or both
containers may be present and running on the system, the script
now detects which http port to connect based on the admin
parameters associated with the preferred web container service
scripts/common.application_svr.install.sh
On some systems, the BEGIN and END labels of the savestate file
would be considered corrupt even though the contents of the
install state file were correct. Code was added to test the
exit code and to attempt a switch of the labels before giving
up entirely.
In both cases the savestate ID was properly computed and the
only change was to the label.
scripts/axs-mgr.identity_svr.configure.sh
Added logic to detect if the preferred webcontainer is either
application server of webserver. Given that one of both
containers may be present and running on the system, the script
now detects which http port to connect based on the admin
parameters associated with the preferred web container service
scripts/common.automate_zonelevel_deployments.sh
The script will only rely on the zones that are defined as part
of the deployment (and only inside of the emra.conf file)
rather than using the output of zoneadm list -cv. This is to
eliminate/minimize any interference with zones that are on
the system which are not part of the EMRA automated deployment.
templates/SUNWappserver
Moved templates/SUNWappserver to the supportfiles directory and
renamed it to 'SUNWappserver.initscript'
install
New feature: Deployment Groups or PODS.
This is used to setup a group of machines that share common
configuration parameters within the group but are distinct
from other groups of machines that are also managed by the
same Jumpstart Server machine. This allows for a single
jumpstart server to serve multiple groups of machines.
New feature: USE_LOCAL_CDROM (true/false)
Allows the deployment to expect the software bits to be located
on a CDROM that is attached to the client machine that is
jumpstarted instead of on a local NFS server. This feature is
used when creating the Comms Suite Virtual Machine demos
supportfiles/S99automate_comms_deployment
Created a boot script in each zone such that the automation
will be done as part of the boot process. Added a flag to
to this script to prevent duplicate initiation of the
automation process.
templates/common.appserver.install.state {removed}
Application server install statefiles are now stored in the
same rcdir as the comms suite release it belongs to. So the
install statefile is found in cs6u2.d for an install of
Comms Suite 6 update 2 and in cs6u1.d for an install of Comms
Suite 6 update 1.
scripts/common.create_localzones.sh
Attachment of loopback mounts to the localzone is done in
a separate subroutine than the one used for zone creation.
site-programs/Utils/common.customize-instant_messaging-configs.sh.example
Major rewrite to include the option of modifing the schema
before continuing to modify the im config files
site-programs/Utils/common.customize-integrated_web_client-configs.sh.example
Corrected the case where the default domains were separated by
commas instead of spaces. When the separator was incorrect,
the IM panel for Convergence would be permanently show
a 'connecting' status
scripts/common.fix_hosts_file.sh
Rather than replacing the entire nsswitch.conf, it is much safer
to just modify the 'hosts:' line directly. This was proven in a
case where there were options in the nsswitch.conf file that
were already customized.
postinstall
Made sure that the DISPLAY_OPTION matched with the copilot
mode when doing the configure step
Use this link to download a copy of the toolkit.
Enjoy!
Posted at 05:58PM Jun 25, 2009 by Anthony Waldron in The EMRA Toolkit | Comments[0]
Comments: