Job scripting is a key capability for NetMRI and for the Automation Change Manager system. Job scripting allows use of two linguistic approaches to script job-based automation: a proprietary language, called CCS (Change Control Scripting), a standard-language Perl API, and a standard-language Python API. This chapter focuses on Perl/Python scripting.
...
Create and manage scripts at Configuration Management –> > Job Management tab –> > Scripts tab.
The following table describes user privileges required for scripts.
...
Note: Well-known variables for Perl and CCS scripting are listed in the topic Scripting Well-Known Variables (Perl, Python, and CCS) bookmark654 bookmark654.
...
Perl scripts use a script header similar to a CCS script, contained within a well-known comment block. The script header block influences a number of runtime behaviors, including:
...
Perl scripts run inside the sandbox, using the Perl API to communicate with the Device Interaction Server (DIS) on NetMRI. The DIS proxies CLI requests/responses to/from network devices on behalf of the Perl scripts. Before commands can be sent to a network device, a Perl script must first establish a DIS session (see v2 API object DisSession). After a session has been established, a CLI connection with the target device must be established for the given session (see v2 API object CliConnection). The majority of the time, a Perl script will follow this same initialization sequence. First, establish the API session, establish the DIS session, then establish a CLI connection with the target device. For this reason, Infoblox_Job.pm, a pre-installed Perl library, is provided in the appliance (see Configuration Management –> > Job Management –> > Library –> > Infoblox_Job).
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Note: Well-known variables for Python scripting are listed in the topic Scripting Well-Known Variables (Perl, Python, and CCS) bookmark654 bookmark654.
...
Python scripts use a script header similar to a CCS script, contained within a well-known comment block.
...
Python scripts run inside the sandbox, using the Pyrthon API to communicate with the Device Interaction Server (DIS) on NetMRI. The DIS proxies CLI requests/responses to/from network devices on behalf of the Python scripts. Before commands can be sent to a network device, a Python script must first establish a DIS session (see v2 API object DisSession). After a session has been established, a CLI connection with the target device must be established for the given session (see v2 API object CliConnection). The majority of the time, a Python script will follow this same initialization sequence. First, establish the API session, establish the DIS session, then establish a CLI connection with the target device. For this reason, netmri_easy.py, a pre-installed Python library, is provided in the appliance (see Configuration Management –> > Job Management –> > Library –> > netmri_easy).
About netmri_easy.py
...
Platforms supporting a local sandbox automatically perform the necessary setup and configuration steps; platforms that need a remote sandbox require a manual setup and configuration process. The topic Setting up a Remote Sandbox #bookmark649 describes remote sandbox setup and configuration.
...
Note: The instructions in this section are for the VMware VSphere® platform. For the OpenStack platform, refer to the Infoblox Deployment Guide for NetMRI and Operations Center.
...
To configure the Remote Sandbox, do the following:
- Open the administrative shell.
- Download the Sandbox VM file from Infoblox using any scp program (such as WinSCP).
If you chose the OVF file type, the downloaded file contains an OVF file, a VMDK file, an MF file, a README file and a LICENSE file. The OVF file is what you will need to import into your VMware hypervisor. The MF file contains checksums of the OVF and VMDK files to verify that the exported files are correct before importing. The README file contains detailed instructions for deployment of the remote sandbox.
The standard VMX and VMDK files along with a README file and a LICENSE file, may also be deployed into VMware Workstation. You import the VMX file into the VMware hypervisor. The README file contains detailed instructions for deployment of the remote sandbox. - Load the files into the hypervisor.
For example, In VSphere, choose File –> > Deploy OVF Template and select the file from the correct folder.
After the file loads, give the virtual machine a new name, choose where the VM is deployed, and choose its datastore.
...
- Start VMware Workstation.
- Choose File –> > Import or Export... The Import Virtual Appliance Wizard appears.
- Click Next and then click Next again in the wizard.
- Choose Virtual Appliance from the dropdown and click Next.
- Click on the File System radio button and click 'Browse...'.
- Select the .vmx file that was previously unpacked from the exported ZIP file, and click Open.
- Click Next and then click Next again in the wizard.
- Choose Other Virtual Machine and click Next.
- Enter a name and location for the Virtual Machine and click Next.
- Click Next.
- Click Next again (the network must be bridged for the VM-based NetMRI Sandbox).
- Click Next.
- Verify that your settings are correct and click Finish.
After 20-30 minutes (depending on your hardware and network speed), the NetMRI Sandbox Virtual Appliance will complete import to the VMware host. - Select the NetMRI Sandbox Virtual Appliance you imported and instruct it to Power On.
- Open the console for the Sandbox VM.
- Enter the following in the Sandbox command line:
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
NetMRI admins can determine whether creators of configuration management jobs can self-approve their Perl/CCS script jobs, or require a NetMRI super admin to approve jobs execution. For a quick refresher on administrator accounts and the Roles they inhabit, see Understanding Users and Roles, as user accounts have a close relationship to job execution.
You can define the minimum script run level at which the appliance requires user-provided CLI credentials when scheduling or running a job.
...
NetMRI provides Configuration Management settings (under Settings icon –> > General Settings –> > Advanced Settings) to enforce organization policies for securely executing script jobs:
...
To set job approval settings for all NetMRI admin accounts, do the following:
- On the Settings icon –> > General Settings –> > Advanced Settings page, under the Configuration Management category, click the Edit icon for Job Self Approval.
- To allow all user accounts to self-approve running automated jobs that use CCS and Perl scripts, choose True. Otherwise, choose False.
- Click OK to commit the setting.
To require NetMRI admin accounts to use CLI credentials when executing scripts of a specific risk level, do the following:
1. On the Settings icon –> > General Settings –> > Advanced Settings page, under the Configuration Management category, click the Edit icon for Job Requires User Credentials.
...