This section includes the following information:
This guide assumes you have the following background:
Sound understanding of networks, operating environments, and system architectures.
Familiarity with the Python development language. For more information, see the following online references:
Python Development Environment (PyDEV): The PyDEV plug-in enables developers to use Eclipse* for Python and Jython development. The plug-in makes Eclipse a more robust Python IDE and comes with tools for code completion, syntax highlighting, syntax analysis, refactoring, debugging, etc.
Python Reference Manual: This reference describes the exact syntax and semantics but does not describe the Python Library Reference, which is distributed with the language and assists in development.
Python Tutorial: This online tutorial helps developers get started with Python.
The Orchestration Job Development Language (JDL) incorporates compact Python scripts to create job definitions to manage nearly every aspect of the Orchestration grid. For more information, see Section B.0, Cloud Manager Orchestration Job Classes and JDL Syntax.
Knowledge of basic UNIX shell commands or the Windows command prompt, and text editors.
An understanding of parallel computing and how applications are run on Orchestration infrastructure.
Familiarity with the Orchestration Console layout and use, as explained in the NetIQ Cloud Manager 2.1 Orchestration Console Reference.
Familiarity with basic administrative tasks, as explained in the NetIQ Cloud Manager 2.1 Orchestration Administrator Reference and in the The zosadmin Command Line Tool
section of the NetIQ Cloud Manager 2.1 Orchestration Server Command Line Reference
Familiarity with on-line Orchestration API Javadoc as you build custom client applications. For more information see Section A.0, The Cloud Manager Orchestration Client SDK.
Assumption of both Cloud Manager OrchestrationOrchestration Server administrative and end-user roles while testing and debugging jobs.
To set up a development environment for creating, deploying, and testing jobs, we recommend the following procedure:
Initially set up a simple, easy-to-manage server, agent, and client on a single machine. Even on a single machine, you can simulate multiple servers by starting extra agents (see Configuring the Orchestration Agent
in the NetIQ Cloud Manager 2.1 Orchestration Installation Guide.
As you get closer to a production environment, your setup might evolve to handle more complex system demands, such as any of the following:
An Orchestration Server instance deployed on one computer.
An Orchestration Agent installed on every managed server.
An Orchestration Console installed on your desktop machine.
From your desktop machine, you can build jobs/policies, and then remotely deploy them using zosadmin command linetool. You can then remotely modify the jobs and other grid object through the Orchestration Console.
Use a version control system, such as Subversion*, to organize and track development changes.
Put the job version number inside the deployed file. This will help you keep your job versions organized.
Create make or Ant scripts for bundling and deploying your jobs.
By leveraging the flexibility of the Orchestration environment, you should not have to write jobs targeted specifically for one hypervisor technology (Xen, VMware, etc.).