As part of your Cloud Migration journey, it is very important to have a reliable inventory of your infrastructure. Tidal Tools is able to connect to a Hypervisor to synchronize your inventory of virtual machines from vSphere.
This guide will walk you through the steps and necessary configuration to properly integrate with vSphere and capture the following data points on its VMs.
- IP Addresses
- AssignedID (InstanceUuid in vSphere)
- RAM Used (GB)
- RAMAllocated (GB)
- CPU Name
- CPU Count
- Storage Used (GB)
- Storage Allocated (GB)
- Operating System
- Operating System Version
- Tidal Tools. You can check out the Getting Started with Tidal Tools guide on how to install it.
- vSphere Credentials.
Tidal Tools is able to integrate with the following versions:
|5.5||Yes||When you set the vsphere.server you will likely need to include the default port, 443, in the url. Ex. 192.168.1:443|
First, you need to login into your workspace. On your Terminal run the login command.
Once you are logged on to the Tidal API, You can connect to your vSphere account. The following command will guide you through a set of prompts:
tidal login vsphere
- vSphere Server - Either an IP address or a FQDN that resolves to the correct IP for the ESXi or vCenter instance
- vSphere Username - A username that has read access to the vCenter or ESXi instance.
- vSphere Password - Corresponding password for the user.
- vSphere API Endpoint - The default is
/sdk, It can be left as is, unless you know your setup does not use the default.
- Use SSL/TLS? - The default is to use SSL (y), which can be left unless you know you can’t use it.
- Skip HTTPS certificate checks? - The default is to not skip (n), which can be left unless you know they need to be skipped.
After answering the above prompts, you will see the message:
Login to vSphere successful. Saving config file...Done!
Synchronizing your vSphere inventory with Tidal is simple with:
tidal sync vsphere
Loading data.. Transforming data.. Validating JSON... Valid. Logging in to server at https://demo.tidal.cloud as email@example.com Logged in. Updating via API.. Update successful
You can easily split this into two commands to allow you to inject other metadata about your inventory, if needed. To do this simply use the get command to get your inventory. Modify it as you need and then you can use the sync command to upload your data.
tidal get vsphere, will fetch your vSphere inventory and output JSON (check it out!).
Modify the data as you like from Standard Input and then send it to Standard Output.
tidal sync servers, will take that JSON from STDIN and send it to Tidal.
tidal get vsphere | ./modify_script.rb | tidal sync servers
You can easily set this to run periodically. The integration updates records if they already exist, or creates new records if they don’t. Look at setting this command up as a cron job that runs once per day.
Additional Configuration Options
The integration can be configured with several other methods besides
You can use these alternate approaches if they better suite your use case.
The other configuration options available are to set values in the configuration file (either interactively or manually) or set environment variables.
The credentials and configuration settings take precedence in the following order:
- Environment Variables
- Configuration file
- Prompt in the terminal - If neither are present, you will be prompted to enter the required details and they are stored in the default configuration file.
1) Configuration File
You can set your vSphere credentials with the following commands:
tidal config set vsphere.username [your username]
tidal config set vsphere.password [your password]
tidal config set vsphere.server 192.168.1.12
The set values are stored in the default configuration file.
You can create a file, for example
config.yml, with content similar to this:
vsphere: username: my_user_name_here server: 18.104.22.168 tidal: email: my_user_name_here url: https://my_instance_name_here.tidal.cloud
tidal config setcommand.
That can be used with a command:
tidal sync vsphere --config config.yml
2) Environment Variables
Another alternative is to set the following environment variables with the needed values and Tidal Tools will use them:
Login failing with error
expected element type <Envelope> but have <html>
The reason behind this behavior is that provided vSphere login data references vCenter REST API
service which is exposed on
Instead, Tidal Tools CLI uses vSphere Web Services API which is exposed on
endpoint. This service is enabled by default on vSphere products for versions
If you have manually disabled this service, Tidal vSphere functionalities cannot be used.
How to login?
vsphere.server: FQDN (or IP) vsphere.username: username@domain (or domain\username) vsphere.api_path: /sdk (default path to vSphere Web Services API) vsphere.tls: true (or false if using http) vsphere.insecure: true (or false to skip certificate checks)
- vSphere Automation API - provides REST API for managing and automating infrastructure operations of various vSphere services (includes vCenter REST API among other APIs).
- vSphere Web Services API - provides SOAP API for centralized management of vSphere infrastructure components (virtual machines, datacenters,…).
The difference between the APIs is that Automation API provides access to underlying service management, while Web Service API provides access to the management of individual components.