February 28, 2009
CMDB/CI Relationship Types
Here are some relationship types:-
parent descriptor
Connects to
Contains
Depends on
DR provided by
Exchanges data with
Hosted on
In rack
Instantiates
IP Connection
Located in Zone
Located in
Members
Powers
Received data from
Runs on
Virtualised by
child descriptor
Connected by
Contained by
Used by
Provides DR for
Exchanges data with
Hosts
Rack contains
Instances of
IP Connection
Zone contains
Contains Room / Houses
Member of
Powered by
Sends data to
Runs
Virtualises
November 13, 2008
CI table attributes
Physically capturing CIs is a separate task all by itself, but we shall look at the attributes you can consider for your CMDB.
In no particular order:
- name
- description
- location
- system
- sub-class
- owner
- team allocated
- financial allocation
- catalogue #
- network name
- supplier model
- serial #
- maintenance method
- updated
Added 20th November 2008:
Depending on the granularity of your CI selection, you may want to include the following:-
- location
- responsible owner
- IP address*
* you should consider wheather you want a fixed or variable definition of the CI data within your CMDB.
I shall explain ‘fixed’ and ‘variable’ in another article shortly.
Primary reasons for separate CIs
- critical, new or modified designs;
- independent end use functions;
- need for separate configuration control;
- components common to several systems;
- interfaces to other systems, equipment or software;
- level at which interchangeability must be maintained;
- separate delivery or installation requirement
- separate definition of performance and test requirements;
- high risk and critical components.