| Table of Contents |
|---|
Open Items
- repoint data sources once FW rules in place (developing w/ SSH tunnels)
- create a read-only role in MS SQL (currently the credential is too privileged)
Overview
Aperture is an application that provides a configuration data store for data center infrastructure. It's a primary source of practically undiscoverable physical metadata about configuration items:
- racks
- data center spaces/rooms
- UPS/HVAC equipment
- physical servers
- network devices
- cards
Most of this data is in the "VISTA" database underneath Aperture. This data can be imported and transformed into ServiceNow using MID Server (on Yale premises proxy)
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
VISTA Database Views
For the purposes of this integration, DC Operations is working with Avocent via a professional services contract to provide and maintain views for exposing configuration data to ServiceNow. At first this will be a one-way (SN read-only) integration, so Aperture will remain the canonical source of information, while SN will be used to plan & detect changes under the rubric of ITIL Change & Configuration management.
Servers
- APERDB (prod)
- APERDB-T (test)
Data Source + Credentials
Data Source (SN Name) | Staging Table | Credentials | Source DB | View |
|---|---|---|---|---|
CMDB Locations (Dev) | u_cmdb_location_import | [CMDB (Dev) Credentials | jdbc:sqlserver://aperdb-t.its.yale.edu:1433;databaseName=VISTA | SN_Space_Info |
CMDB Spaces (Dev) | u_cmdb_space_import | [CMDB (Dev) Credentials | jdbc:sqlserver://aperdb-t.its.yale.edu:1433;databaseName=VISTA | SN_Space_Info |
CMDB Racks (Dev) | u_cmdb_rack_import | [CMDB (Dev) Credentials | jdbc:sqlserver://aperdb-t.its.yale.edu:1433;databaseName=VISTA | SN_Racks |
Views
View | Description |
|---|---|
SN_Blade_Chassis | |
SN_Blade_Servers | |
SN_Cards | |
SN_Network_Devices | |
SN_Physical_Servers | |
SN_Racks | physical racks |
SN_Space_Info | |
SN_Storage |
Transform Logic
Type | Mapping/Logic |
|---|---|
Locations | BUILDING->name, ADDRESS_1->street, STATE->state, ZIP->zip, VOB_ID->vob_id (extend) |
Floors | FLOOR->name, VOB_ID->parent (reference) |
Data Centers | VOB_ID->location w/ VOB_ID (relationship), VOB_ID->vob_id (extend) |
Racks | RACK_NAME -> name, VOB_ID -> vob_id (extend), GRID_LOCATION -> grid_location (extend), SPACE_VOB_ID -> space (CI relationship) |
Here's an overview of how the views are related:
