Virtual Infrastructure DB Project
Jump to navigation
Jump to search
This started life as small script to collect VM info from 5 or 6 vCentre's (that were a mix of v2.5 and v4, and weren't linked together), so that VM's could be easily found without having to search through each one. There are essentially 3 components to it...
- Data collection scripts (run from a Windows desktop)
- A daily PowerCLI script that collects data from all vCenters (and updates the database)
- An intra-day PowerCLI script (say every 15mins) that collects basic cluster status data (and updates the database)
- MySQL database (run on an Ubuntu VM)
- PHP front end (delivered by Apache running on same Ubuntu VM)
Releases
Matrix
| Release | Database | Data Collection | Presentation (Main) | Presentation (Other) | |||
|---|---|---|---|---|---|---|---|
| Version 1 | initial | db-base-data-v1.0.ps1 | db-esx-check-v4.ps1 | index.php v1 | status.php v1 | alpha.css v1 | vc-detail.php v1, cluster-detail.php v1, vm-detail.php v1 |
| Version 1.1 | db-base-data-v1.1.ps1 | ||||||
| Version 1.2 | update-v1.2 | db-base-data-v1.2.ps1 | index.php v1.2 | snaps.php v1.2 | |||
- Standard include files...
- Standard.ps1 - Basic PowerShell helper (logging etc)
- PowerCLI-helper-v1.1.ps1 - PowerCLI helper (provides API bug workarounds)
- DS-LUN-v4.ps1 - PowerCLI Datastore helper (LUN's etc)
- getsnapshotsize-1.ps1 - PowerCLI Get_Snapshot bug workaround
Change Log
Version 1.1
- Bugfix: Where VC provides no VM FolderID, VM is assigned incorrect VC folder path - now catch as error
- Bugfix: VM's having no IPAddress in vCentre not handled properly, causing errors - now handled silently
- Bugfix: Added vmvcid to better handle Lab Manager v4 VM's with duplicate UUIDs
- Bugfix: ESX's moving clusters causes duplicate ESX entries - old ESX/cluster entry now gets expired
- Added snapshot info (data collection only, db table already existed)