Applications
In the Applications section, you manage software components used in VM templates, virtual machines, or environments.
This allows you to keep track of which software versions are used in your OpenVLE infrastructure and to document them systematically.
Where can I find this section?
Via main menu: Infrastructure → Applications
Alternatively accessible via: Linked from Vendors, Virtual Machines, or VM templates
Features at a glance
- View, create, edit, and delete applications
- Assign an application to a vendor
- Capture version information and descriptions
- Link applications to VM templates or environments
- Support for inventory management of deployed software
Important fields at a glance
| Field name | Description |
|---|---|
Description | Brief description or version information of the application, e.g. "Office suite for word processing, spreadsheets, and presentations". |
Name | The name of the application, e.g. "LibreOffice" or "Visual Studio Code". Displayed in lists and associations. |
Vendor | Relationship to the vendor that provides the application. Enables consistent assignment and filtering within the infrastructure. |
Creating an application
- Open the Infrastructure → Applications section from the main menu.
- Click Add to create a new application.
- Enter a name, a vendor, and a description for the application.
- Save the application.
- Then switch to the VMs or VM templates tab to add or remove the required VM templates for the application.
The required vendor must exist before creating the application.
Editing an application
- Open the Infrastructure → Applications section from the main menu.
- Find the desired application in the list.
- Click Edit, or open the context menu of the application and select Edit.
- The form displays all current data of the application.
- Adjust the desired fields -- for example Name or Description.
- Save the changes.
If a software version has been updated, e.g. from Office 2016 to Office 2019, it is recommended to create a new application.
This prevents already assigned VMs and VM templates from being affected by this version change.
Otherwise, it would appear in OpenVLE as though all assigned systems had been upgraded to the new version.
Deleting an application
- Open the Infrastructure → Applications section from the main menu.
- Find the desired application in the list.
- Click Delete, or open the context menu of the application and select Delete.
- Confirm the deletion in the displayed dialog.
- The application is then permanently removed.
When deleting an application, all assignments to VMs and VM templates are removed.
However, the affected VMs and VM templates themselves remain unchanged.
Example or use case
An administrator wants to document an application for all training machines.
She opens the Infrastructure → Applications section, clicks Add, and enters the data:
- Name: LibreOffice
- Vendor: The Document Foundation
- Description: Office suite for word processing, spreadsheets, and presentations
She then assigns the application to the relevant VM templates to ensure clean inventory management.
Notes / special considerations
- Applications serve exclusively for documentation and assignment -- they are not automatically installed.
- An application can be assigned to multiple VM templates or virtual machines.
- When an application is deleted, existing assignments in VMs or VM templates are also removed.
- Vendors must already exist before creating an application.
Relationships to other objects
Many objects in OpenVLE are related to other elements within the system. The following overview shows which relationships exist and whether they trigger certain automations.
| Object | Description | Automatic behavior |
|---|---|---|
| Changelogs | All changes to the object are automatically logged. | Automatic removal when the object is deleted. |
| Permissions | Object-specific permissions can be assigned directly to the object. | Automatic removal when the object is deleted. |
| Tags | Objects can be tagged with any number of tags to categorize or filter them. | Automatic removal when the object is deleted. |
| Vendor | Exactly one vendor can be assigned to an application. | No automations. |
| VM templates | Any number of VM templates can be assigned to an application. | No automations. |
| VMs | Any number of VMs can be assigned to an application. | No automations. |
Required permissions
The permissions required for actions can be assigned via roles or individually. If you lack certain rights, the corresponding functions in the user interface are hidden or disabled.
| Action | Required permission | Path | Additional information |
|---|---|---|---|
| View applications | applications_read | / or /<objectID> | |
| Create applications | applications_create | / | |
| Edit applications | applications_update | / or /<objectID> | |
| Delete applications | applications_delete | / or /<objectID> | |
| View vendors | vendors_read | / |
Example:
/4a3bc312-d1af-4b3f-b222-f5e9cecbf007 – This gives the user access to this single object only.If the path / is used, the permission applies globally to all objects of this type.
For *_create permissions, only the global path / is allowed.