# VMWare
## Version
* Linux Control Center = 2.10.X or Higher
* VMWare ESXi = 7.0 U2 or Higher
## Requirements
* Access credentials with VMware snapshot permission.
* Hosts in the LCC database previously configured
## Overview
The native integration with VMWare Vcenter is classified as a Rollback Item within the scope of Linux Control Center. A Rollback Item generally aims to start a backup task, create a snapshot, recovery point or similar item within the integration scenario, with the aim of ensuring the rollback of a system if a modification generates some unexpected behavior in your technology park.
Whenever one or more actions selected in the integration are called by the LCC, they will trigger the command to create a snapshot, and only after confirmation that the snapshot was successfully created in VMware, the action will be executed.
{% hint style="warning" %}
Please note that all third-party solutions that interact with LCC must be configured correctly. Inconsistent data from these solutions cannot be reliably processed or presented by LCC.
{% endhint %}
## Objective
This guide provides information and step-by-step instructions for integrating Linux Control Center with the VMware vSphere virtualization system.
## VMware Integration with LCC
### Integration Configuration
1. Click **Config** in the left side menu of LCC
1. Click the **VMware** button
1. Click the **Create** button
1. Fill in the fields with your environment information**Name**: Name to identify the integration\
**URL**: VMware vSphere URL address\
**Username**: User with the environment domain Ex: @vsphere.local\
**Password**: Access password\
**GOVC**: Defines the binary version for integration with VMware, leave it as is **default**\
**Default Data Center**: Enter the exact name of the VMware Data Center in your environment in this field\
**Ignore SSL**: Button to ignore communication with SSL
{% hint style="warning" %}
If you need to perform the integration in more than one Data Center, you will need to create an integration for each of them.
{% endhint %}
1. Click **Save** after entering the data correctly
### Connection Test
1. After saving, click **Test Connection** to perform the connection with VMware and wait for the action to finish
1. You will be able to see the status icon in green, confirming that the connection was successful.
### Host Synchronization
1. After the connection is validated, click on the **Hosts** tab and click on **Sync** and wait for the synchronization action to finish.
1. After the synchronization is finished, refresh the screen and the hosts will be listed in the **Hosts** tab of the integration.
### Host Selection for Rollback
{% hint style="warning" %}
If any VMware host does not appear on the integration hosts screen, make sure that it was inserted in the LCC database.
{% endhint %}
1. To remove one or more hosts from the snapshot task, uncheck it in the **Enable** column and click **Save**. This way, VMware will not create a snapshot of the unchecked hosts when a predefined action is executed in the LCC.
### Snapshot Action
1. Click on the **Actions** tab and select as many actions as you want, so that whenever executed by the LCC, it will send the command to create a snapshot of the machines selected on the **Hosts** screen
2. Click on **Save**
### Executing the Snapshot Trigger Action
* The action used for demonstration was the **Host Ping** action
1. Click on **Hosts**
1. To execute the action on only a single host, select the desired host and click on **Actions** in the host line
1. To run the action on more than one host, select as many as you want in the box on the left column and click **Actions** at the top of the page
1. To run the action on all hosts in the LCC database, select the box next to Hostname and click **Actions** at the top of the page
### Scheduling Snapshot Listing
1. On the VmWare integration screen, click the **Schedule** tab
1. Click **Add Schedule**
**Test Connection:** Performs a connection test connection with VmWare to validate the integration\
**Sync Assets:** Updates the list of VmWare assets according to the LCC host database
4. Then, define a name for the schedule in the **Name** field and choose one of the actions in the **Action** line
By default, the scheduling screen opens with the **One Time** option, to schedule a single execution at a specific hour, minute and date, as shown in the image below;
1. By checking the **Repeatedly** box together with **Minutes** it is possible to execute the action every X defined minutes.
1. Checking the **Repeatedly** box together with the **Daily** option allows you to run the action every day, every X hours and X minutes.
1. Checking the **Repeatedly** box together with the **Advanced** option allows you to choose the custom schedule, where you can choose the hour, minute, day of the week, day of the month and the desired month.
1. After creating and saving a schedule, you can pause it if necessary by clicking **Disable** and monitor the status of whether it is enabled or not in the **Active** column.
1. The **Next Run** column displays when the next run will be and the **Last Run** column displays when the last run was. The **Count** column counts how many times the schedule has been run.
1. You can also delete a schedule by clicking the trash can icon next to the Disable/Enable button.
## Snapshot Validation
* You can validate if the snapshot was successfully created in Vmware by LCC.
1. Click on **Hosts**
1. Click on the **Host** where you performed the action.
1. Click on the **ROLLBACK** tab and click on **SYNC**
* The host's snaphost will appear in **Rollback Items** with the description **Created By LCC**
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.linuxcontrolcenter.com.br/en/configs-integrations/integrations/vmware.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.