Background
A finding of Yale's pilot of Discovery is that a CMDB project needs to be created, and that the resulting database will have to be integrated with multiple authoritative sources, requiring new integration code to be written.
Another finding is that SSH discovery was less desirable than SNMP discovery for UNIX, due to security and architectural concerns. This means that existing SSH probes and sensors in Discovery will have to be ported for use with SNMP.
As a result of these findings, it will be necessary for Fruition to estimate additional work for the related integrations.
Scope
- Implement a CMDB ACLs scheme to support ownership of CMDB data by the appropriate departements/groups.
- Port a subset of SSH discovery probes to SNMP for UNIX server discovery. This would be in support of two separate UNIX groups using the same CMDB schema.
- Custom integrations to existing CMDB repositories
- Changes to stock integrations (e.g. SCCM) to support desired set of fields, custom fields
Yale Inputs
CMDB Field Matrix
- Data center equipment (racks, UPS, HVAC, server rooms, PDUs, etc)
- UNIX servers
- Storage devices (SAN, NAS)
- Windows servers
- Network devices (switch, router, concentrators, access points)
- Software assets
- Database assets
- Desktop assets
Integration/Import Specs
- Spec for one-time import of data from Aperture (data center) ODBC source
- Spec of SNMP OIDs and output formats for each required SNMP UNIX probe/sensor pair w/ CMDB schema mapping
- Spec of SNMP OIDs and output formats for each required storage probe/sensor pair w/ CMDB schema mapping
- Spec for additional CMDB mappings for SCCM Windows Server integration
- (ODBC, SOAP or XML) schema for NetMRI w/ CMDB schema mapping
- Spec for (one-time, many-time) import of data from SSG (software catalog) QuickBase source
- Spec for one-time import of data from Yhoda (DBA) ODBC source
- XML schema for Tivoli desktop asset integration w/ CMDB schema mapping