Several fixes to inefficient code have increased the performance in the key areas of ControlTier command dispatch and execution.

ProjectBuilder's load-object command has been made more efficient (ashortland)

The sending of model-change reports from Workbench to Reportcenter has been disabled by default to reduce server load. (This can be re-enabled if desired)

By default, the Process Flow Visualization in Jobcenter for workflow commands will not be available. To see it you must now run "ctl-depot -a install" with the "-w" flag to generate the appropriate files used by Jobcenter. This improves client-node ctl-depot performance. This issue will be revisited for a better solution in future.

Thursday, March 04, 2010

This release fixes quite a few bugs and even completes a fair number of feature requests. Primary development has moved onto the 3.5x development line, although future 3.4x maintenance releases are likely.

Wednesday, November 18, 2009

This release has quite a few bug fixes and improvements. It is also the first ControlTier release distributed in RPM packages.

Release 3.4.9 has both the traditional installer packages (zip,jar), and two RPM packages: ctier-server and ctier-client. The ctier-server is the full server installation with the embedded client. The ctier-client includes the client installation only allowing simpler package distribution and installation for client nodes.

Tuesday, September 29, 2009

Most ControlTier users manage their project model using XML files that define the resources that comprise their application and their environment. The ProjectBuilder module provides a command to upload these XML files to the ControlTier server webapp, Workbench. Up until 3.4.8, Workbench did not provide a direct interface to export the same data back to XML. This was particularly annoying when a project model was setup using the GUI interface of Workbench.

To export that data from Workbench click on the "simpleTomcat" object and in the toolbar you will notice an XML icon. Click that icon and the browser will be directed to a page that contains the project.xml.

The same can be done from the command line via the ProjectBuilder command, find-objects.Below, the find-objects command is used to lookup the same "simpleTomcat" object and the exported model data saved to the file: /tmp/simpleTomcat.xml

Conflation of Node name vs. hostname cropped up again in node-dispatch with CTL and the integration with Workbench. It should finally be completely resolved.

ProjectBuilder#find-objects has duplicate results: The find-objects command will now only show unique results.

Notable Improvements:

Java 6 support: Both the client and server now support Java 6.

project.xml export: Workbench and the ProjectBuilder#find-objects command can now export project.xml formatted data. Either use the -out option to find-objects, or click the "XML" toolbar button when viewing a resource in Workbench.

Node name/hostname are now correctly distinguished when installing deployments. You can now have two Nodes with the same hostname, as long as the Node names are unique, and ctl-depot -a install will work correctly.

Improvements:

Tags:

Workbench service manager views now display any Tags associated with a resource in the manager list view. Tag searching is also now fully integrated in the Workbench user interface.

Node Filtering:

CTL and CTL-EXEC now support using arbitrary attributes as node filters in the -I/-X arguments. E.g. "ctl-exec -I myattribute=something -- echo hello".

Retrying failed commands:

CTL and CTL-EXEC now also support a -F flag which lets the user specify a filepath to store a list of nodes for which failures occur. When you execute across multiple nodes using the -I/-X node filter options, and use the -K (--keepgoing) option, any nodes for which a failure occurs will be stored in the specified -F file. You can then re-execute with the exact same commandline, and CTL/CTL-EXEC will only execute on the nodes listed in the given file. If further errors occur, the nodelist will again be stored in the same file. Once all nodes have executed succesfully, the file will be removed. This facilitates retrying a failed command only on the failed nodes either manually or automatically.

Environment variables in scripts:

A new default mechanism for executing defined shell commands called "shell-exec" is introduced. This allows shell scripts/commands to acquire environment variables with values passed directly from the set of ControlTier metadata available to all commands.

Cygwin:

Installer script improvements provide a much smoother way to install ControlTier on cygwin-based Windows nodes.

Dispatching scripts to cygwin nodes via ctl-exec or Jobcenter now works correctly when the Node has os-family="cygwin", and registration of a Node via a ControlTier client installed on a cygwin node will correctly set the os-family of the Node.

Friday, June 05, 2009

ControlTier has supported the concept of continuous deployment for years and it's great that the concept is becoming increasingly main stream.

In ControlTier, the end-to-end build and deployment process is defined via the Updater "BuildAndUpdate" workflow that orchestrates the Builder's Build and the Site's Update workflows. You can read about the basics on our Wiki here: Continuous_deployment

Tuesday, June 02, 2009

This release has been focused on support for Windows in several forms:

Internet Explorer is now supported for the server web applications Workbench, Jobcenter, and Reportcenter. Both IE 7 and 8 are supported

Windows-based Examples have been added to the Wiki. See the Examples page.

Other bug fixes are also included.

Documentation:

Two new high-level Library Guides have been added to help you develop Tomcat and JBoss server management solutions. These guides tie together the related Type Modules that are included with ControlTier, and show how they can be used together to create a management solution.