Connector Applicability
|
Applies to Source Connectors |
VMware vSphere |
|---|---|
|
Applies to Destination Connectors |
All |
Assumptions
These instructions assume you have already setup a source connection in CI Sync for VMware vSphere using the CI Sync instructions here: Add VMware vSphere.
Pre-Read
Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.
Locating and Amending the Connection Setting in the CI Sync UI
-
Navigate to the Settings page
-
Under the Source Connections heading (list), locate your VMware vSphere connection.
-
Click the Update link on the right hand side of the VMware vSphere connection.
-
Scroll down and locate the Section Heading and view the Individual Settings.
The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.
-
Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.
|
Setting |
Type |
Additional Notes |
|
Reverse Instantiated by Relationship |
Slider |
When this setting is disabled, CI Sync applies applies the following relationship:
When this setting is enabled, CI Sync applies applies the following relationship:
Additional Information Topic #1 - Overview of conflicting relationship documentation about VM Instances and Computer CIs ServiceNow’s has published conflicting documentation about the relationship hierarchy to be used between Virtual Machine Instances and the associated Computer CIs. Some ServiceNow documentation recommends treating the Virtual Machine Instance as the parent, and the Computer CI as the child. In this case the resulting relationship would be as follows:
Other ServiceNow documentation recommends treating the reverse (i.e. the Computer CI is treated as the parent, and the Virtual Machine Instance as the child. In this case the resulting relationship would be as follows:
Topic #2 - Detailed explanation about Virtual Machine Instances and Computer CIs and how CI Sync builds relationships between each Syncfish recommend the following FAQ article that explains the difference between Virtual Machine Instance objects/CIs and Virtual Machine objects/CIs. The FAQ explains each object type, why the exist as separate objects, where they exist in the CMDB and how they relate to one another (i.e. the standard CI-to-CI Relationships or Dependencies created for these objects. We suggest you read FAQ - Overview of Virtual Machine Instance objects and Virtual Machine objects and the associated CIs.
|
-
After modifying the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.
-
You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.
Importantly
Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).
For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.
Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.