Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
This article provides information about migration of Cost Driver Configuration from vRealize Business for Cloud to vRealize Operations Manager.
Cost Driver Configuration present in vRealize Business for Cloud is copied to vRealize Operations Manager.
To migrate Cost Driver Configuration from vRealize Business for Cloud to vRealize Operations Manager: Download the attached 55785_CostDriver_Scripts.tar.gz file to the /tmp folder of the vRealize Business for Cloud Virtual Appliance.Log into the vRealize Business for Cloud Virtual Appliance via SSH or Console and change to the /tmp directory.Extract all files to /tmp/costdriver_export_import/ using the following command: tar -zxvf 55785_CostDriver_ExportImport_Scripts.tar.gz Change to the /tmp/CostDriver_ExportImport_Scripts/ directory.Export Cost Driver Configuration from vRealize Business for Cloud by running this script: ./export_costdrivers.sh Import Cost Driver Configuration to vRealize Operations Manager by running this script: ./import_costdrivers.sh -i|--import "import_zip_archive" ip_or_fqdnNote: Replace import_zip_archive with the path to the Cost Driver Zip File exported from vRBC, and ip_or_fqdn with the IP address or FQDN of the vRealize Operations appliance's Primary node. To revert the imported Cost Driver configuration in vRealize Operations Manager, run this command:./import_costdrivers.sh -r|--revert "revert_json_file" ip_or_fqdnNote: Replace revert_json_file with the path to the Cost Driver Backup file obtained after Import into vRealize Operation, and ip_or_fqdn with the IP address or FQDN of the vRealize Operations appliance's Primary node.
If there is no network connectivity between the vRealize Business for Cloud and vRealize Operations Manager Virtual Appliances, then Import must occur on the vRealize Operations Manager Virtual Appliance or on an external Linux environment with Python 3.x that does. The ZIP archive exported by the Export script is also needed for the Import script. Assumptions regarding Environment: Python 2.7 on Virtual Appliance is supported for Export and Import/Revert. Python 2.6 on Virtual Appliance is supported for Import/Revert only.External Linux environment with Python 3.x is supported for Import/Revert only.Export must happen from within the Virtual Appliance.All Bash, Python script files and PEX files must be in the same directory. Export Cost Driver Configuration from vRealize Business for Cloud Export Script Usage:./export_costdrivers.sh Script outputs to Console: Directories for exported file paths is created in the same directory path as the export script: ./vrbc_costdrivers/.File paths for log file and the exported data files are written to Console Standard Out.Error log messages are also written to Console Standard Out.Any other directives are also printed to Console Standard Out. Log Messages: Export logs specify if any processing occurred before exporting the Cost Driver data to a Zip archive.If no Cost Drivers are modified, then a warning is written to the log and nothing is exported. Assumptions regarding Cost Driver Configuration: Cost Drivers not modified in vRealize Business for Cloud are not exported, but individual rates no modified in vRealize Business for Cloud are exported. Hence, Reference Database must be the same across both vRealize Business for Cloud and vRealize Operations Manager.Datacenter-specific values in vRealize Business for Cloud are averaged out and then exported.Total monthly costs for Labor, Network and Facilities in vRealize Business for Cloud are ignored. Datacenter-specific costs still averaged out, but Datacenter-specific total monthly cost is omitted from the calculation of average.Depreciation Configuration is also exported from vRealize Business for Cloud, but not actually imported by the Import script into vRealize Operations Manager. Hence, it is to be imported manually. Import Cost Driver Configuration to vRealize Operations Manager Import Script Usage:./import_costdrivers.sh -i|--import "import_zip_archive" ip_or_fqdnNote: Replace import_zip_archive with the path to the Cost Driver Zip File exported from vRBC, and ip_or_fqdn with the IP address or FQDN of the vRealize Operations appliance's Primary node.Usage: vRealize Operations Manager credentials for the Import script is required to be that of a Local User with permission to modify Cost Drivers. Other authentication mechanisms would fail due to lack of permission to modify Cost Drivers.Specified IP address or hostame must have a running instance of vRealize Operations Manager.Import script will provide a backup file if a revert becomes necessary. Script outputs to Console: Directories for exported file paths is created in the same directory path as the export script: ./vrops_costdrivers/.File paths for log file and the exported data files are written to Console Standard Out.Error log messages are also written to Console Standard Out.Any other directives are also printed to Console Standard Out. Log Messages: INFO logs occur when there are general messages regarding status of script, or successful completion of a process in script.WARNING logs occur when additional processing is required in order to import the exported data into vRealize Operations Manager. The data may be manipulated to be accepted by vRealize Operations Manager as valid. May require manual intervention if modifed values are not desired.ERROR logs occur due to error in user input, such as incorrect credentials; or if the data could not be imported into vRealize Operations Manager at all. Requires manual import of the specific Cost Driver Configuration in this case.Log messages will also have the usual course of action for resolution, if it is not immediately apparent. Assumptions regarding Cost Driver Configuration: Currency Configuration for vRealize Business for Cloud and vRealize Operations Manager must match for Import to be feasible.Datacenter Additional Cost in vRealize Business for Cloud distributed among all hosts under Datacenter in vRealize Operations Manager.Individual rates that are modified by the user in vRealize Operations Manager are not overrriden with the rates exported from vRealize Business for Cloud.Global Additonal Cost in vRealize Business for Cloud distributed among vCenters in vRealize Operations Manager.Server Hardware batches’ number of servers is capped to the maximum number of servers of the Server Group in vRealize Operations Manager. Newer batches omitted once cap is reached.Depreciation Configuration exported from vRealize Business for Cloud is not actually imported by the Import script into vRealize Operations Manager. Hence, it is to be imported manually. Revert imported Cost Driver Configuration in vRealize Operations Manager Revert Script Usage:./import_costdrivers.sh -r|--revert "revert_json_file" ip_or_fqdnNote: Replace revert_json_file with the path to the Cost Driver Backup file obtained after Import into vRealize Operation, and ip_or_fqdn with the IP address or FQDN of the vRealize Operations appliance's Primary node.Usage: vRealize Operations Manager credentials for the Revert script is required to be that of a Local User with permission to modify Cost Drivers. Other authentication mechanisms would fail due to lack of permission to modify Cost Drivers.Specified IP address or hostame must have a running instance of vRealize Operations Manager. The Cost Driver Configuration will be reverted with the backup file obtained after Import. Script outputs to Console: File paths for log file and the exported data files are written to Console Standard Out.Error log messages are also written to Console Standard Out.Any other directives are also printed to Console Standard Out. Log Messages: INFO logs occur when there are general messages regarding status of script, or successful completion of a process in script.ERROR logs occur due to error in user input, such as incorrect credentials; or if the data could not be reverted in vRealize Operations Manager at all. Requires manual revert of the specific Cost Driver Configuration in this case.Log messages will also have the usual course of action for resolution, if it is not immediately apparent. Assumptions regarding Cost Driver Configuration: Individual rates modified by user after an Import will be overwritten by the values that were present before Import for the modified Cost Driver.