that contains all the resources needed to develop new
modules. Some of the use cases for Open Automation are
the following:
Adding the ability to control a new type of device with Cisco UCS
Director
Designing custom menus for displaying new devices or components
Taking inventory of new devices
Developing custom Cisco UCS Director reports and report actions
Developing tasks that can be used in workflowsCustom tasks enable developers to perform customized
operations on Cisco UCS Director resources. Custom
tasks are written using CloupiaScript, a language similar
to JavaScript. Custom tasks can be used like any other
task, including in workflows that orchestrate how the
system works. Script bundles are collections of custom
tasks that are included with each Cisco UCS Director
release and are used for a variety of specific applications.
Script bundles can be downloaded, and the custom tasks
that are contained in a bundle can be imported into Cisco
UCS Director. The main goal with custom tasks is to
expand the range of tasks that is available for use in
orchestration workflows.
Script modules are used to integrate third-party JARs
(Java Archives) and custom libraries with Cisco UCS
Director to add custom functionality to the Cisco UCS
Director user interface. Some script module operations
are already defined in Cisco UCS Director, such as
creating advanced controls to collect user input in
workflows and context workflow mapping, which enables
an administrator to attach workflows to custom actions
in a report in Cisco UCS Director. Script modules can be
exported and reused in different instances of Cisco UCS
Director. Script modules, although named similarly to
script bundles, have in fact a very different role. Script
bundles, as we’ve seen previously, are packaged
collections of workflow tasks that are released with Cisco
UCS Director. Script modules, on the other hand, make it