Introduction to ScienceLogic Libraries and Execution Environments

This section describes how to create and manage ScienceLogic Libraries and Execution Environments.

What is a ScienceLogic Library?

Some Dynamic Applications, credential tests, and Run Book Actions in SL1 collect data or complete automated actions by executing one or more blocks of Python code, called snippets. When this happens, SL1 passes credentials and other configuration information to the snippet, and at the end of execution, the snippet either passes collected data back to SL1 or runs an action.

A ScienceLogic Library is a package consisting of metadata and Python files that can be used by the Dynamic Applications, credential tests, and Run Book Actions that use snippets. ScienceLogic Libraries can be included in a PowerPack along with the Dynamic Applications, credential tests, and Run Book Actions that they support.

As of SL1 12.1.0, ScienceLogic Libraries are built using Python 3.

These are a few reasons you might want to create and use a ScienceLogic library in your PowerPack. For example, if you have a Python package you created that you want to share between snippets, or you have a third-party package that needs to be available during snippet execution.

ScienceLogic Libraries use the py_package (.tar) format. This file type includes metadata and Python packages, and allows you to take advantage of unit tests, automatic versioning, and other common packaging practices. This format requires an understanding of Python packaging tools.

Older versions of SL1 bundled ScienceLogic Libraries in a py_directory format. That format has since been deprecated. Current ScienceLogic Libraries should be bundled only in a py_package format.

ScienceLogic Libraries can be installed on SL1 in three ways:

• Some libraries are included when you install SL1 or run system updates.
• Libraries that are included in a PowerPack are installed on SL1 when you install the PowerPack.
• Libraries can be manually imported into SL1.

You can view all of the installed ScienceLogic Libraries on the ScienceLogic Library Manager page (System > Customize > ScienceLogic Libraries).

For details about how to manage libraries in SL1, see the Managing ScienceLogic Libraries section.

What is an Execution Environment?

To use a ScienceLogic Library, you must align it with an execution environment.

In the SL1 user interface, an execution environment is a list of one or more ScienceLogic libraries. When a Dynamic Application snippet, Run Book Automation snippet, or credential test is executed, the execution environment defines a virtual Python environment that is deployed on-demand and includes all of the ScienceLogic libraries aligned with it for use during snippet execution.

A ScienceLogic Library can be associated with multiple execution environments, allowing you to share code between snippets, Dynamic Applications, and PowerPacks.

Execution environments must be specified when creating or editing the following:

• Snippets
• Credential tests
• Run Book Action policies that execute a snippet

When SL1 runs a snippet embedded in a Dynamic Application, credential test, or a Run Book Action, it automatically deploys the runtime environment defined by the execution environment. The runtime environment includes each library aligned with the execution environment, plus system libraries that are provided by SL1.

If you do not specify the execution environment for a Dynamic Application, credential test, or Run Book Action, SL1 aligns them with a system-default execution environment. This default execution environment is defined in each SL1 System update.

When you build a PowerPack, it automatically includes the execution environments that are aligned with the PowerPack's Dynamic Applications, credential tests, and Run Book Actions that execute snippets.

For details about how to create and manage execution environments in SL1, see the Managing Execution Environments section.

For more information about aligning execution environments with Dynamic Applications, credential tests, or Run Book Actions, see the following sections:

• Dynamic Application Properties
• Creating a Credential Test
• Creating a Run Book Action Policy that Executes a Snippet