Managing Execution Environments

Execution environments in Skylar One (formerly SL1) let you share code between snippets, Dynamic Applications, and PowerPacks. Execution environments have a global unique identifier (GUID), a name, and list of associated libraries. The libraries associated with an execution environment provide a way to bundle reusable code in a self-contained environment available in snippets. You can use different execution environments for different Dynamic Application requirements.

Viewing the List of Execution Environments

The Environment Manager page (System > Customize > ScienceLogic Libraries > Actions > Execution Environments) displays a list of all existing execution environments.

For each execution environment, the page displays the following information:

To sort the list of execution environments, click on a column heading. The list will be sorted by the column value, in ascending order. To sort by descending order, click the column heading again.

• Environment Name. The name of the execution environment.
• Env GUID. The execution environment's globally unique identifier.
• Env Type. The Python runtime version selected for the execution environment.
• Libs. The number of ScienceLogic Libraries aligned with the execution environment. Click the View Aligned Libraries icon () to view the list of ScienceLogic Libraries that are aligned to a particular execution environment.

Creating an Execution Environment

Skylar One includes several execution environments from preloaded PowerPacks and system updates for your use. If needed, you can also create new execution environments. After you have successfully created an execution environment, it will appear in the list of execution environments available for aligning with Dynamic Applications, credential tests, and Run Book Actions.

To create an execution environment:

1. From the Environment Manager page (System > Customize > ScienceLogic Libraries > Actions > Execution Environments), click the New button.

2. On the Environment Editor page, type a name for the new execution environment in the Environment Name field, select a Python version from the Environment Type drop-down, and then click the save icon ().

   Each execution environment is assigned an Env GUID, which makes it unique. Since two environments can share a name, it is a best practice to use the Name field to version an environment when updating its contents.

3. The Library Alignment pane appears, displaying a list of ScienceLogic Libraries that you can align with the new execution environment. Click the align icon () for a ScienceLogic Library to align that library to the new execution environment.

   You can select the Filter Libraries By Python Version drop-down to filter ScienceLogic libraries compatible with the execution environment runtime. This feature is set to on by default.

4. Align any additional ScienceLogic libraries to the execution environment as needed.

   If necessary, you can click the unalign icon () for a ScienceLogic Library to remove that library's alignment with the new execution environment.

5. When you are finished, click the save icon () again to save the execution environment with the ScienceLogic Library alignment you selected, and then click Close.

Editing an Execution Environment

You can edit an execution environment by clicking its wrench icon (). When you do so, you can change the environment's name, align additional ScienceLogic Libraries to the environment, or remove its alignment with one or more libraries.

To edit an execution Environment:

1. From the Environment Manager page (System > Customize > ScienceLogic Libraries > Actions > Execution Environments), click the edit icon () for the execution environment that you want to edit.

2. On the Environment Editor page, you can do any of the following:

• Change the environment's name in the Environment Name field.
• Align additional ScienceLogic Libraries to the execution environment by clicking the appropriate align icons ().
• Remove the execution environment's alignment with one or more libraries by clicking the appropriate unalign icons ().

3. When you are finished, click the save icon () and then click Close.

Copying an Execution Environment

If you want to create a new execution environment that has traits similar to an existing environment, you can make a copy of the existing execution environment that you can then edit as needed. When you copy an existing execution environment, the new environment includes the same libraries as the original environment, but it will have a new globally unique identifier (GUID).

Making a copy of an execution environment does not mean there will be a duplicate runtime environment. Environments that share a set of libraries will result in the same virtual runtime environment to optimize space on the Data Collector.

To copy an execution environment: 

1. From the Environment Manager page (System > Customize > ScienceLogic Libraries > Actions > Execution Environments), click the copy icon () for the execution environment that you want to copy. A confirmation message appears.

2. Click OK to continue. A copy of the selected execution environment appears on the Environment Manager page. By default, it has the same name as the original execution environment, followed by the word "(copy)".

Deleting an Execution Environment

If you no longer need an execution environment and it is not currently aligned with a Dynamic Application, credential test, or Run Book Action, then you can delete it. Skylar One will not allow you to delete execution environments that are being used by any Dynamic Applications, credential tests, or Run Book Actions.

To delete an execution environment:

1. From the Environment Manager page (System > Customize > ScienceLogic Libraries > Actions > Execution Environments), click the delete icon () for the execution environment that you want to delete. A confirmation message appears.

2. Click OK to continue. The execution environment is deleted from the Environment Manager page.