Content deleted Content added
m Task 13: Fix deprecated |registration= in cs1|2 templates; |
don't link titles, move DMTF content/ref to target article |
||
(41 intermediate revisions by 37 users not shown) | |||
Line 1:
{{Short description|ITIL database used by an organization to store information about hardware and software assets}}
{{
A '''
| url=https://doc.objectgears.cz/vcd/en-US/a_models_it
| title=Configuration items layers}}</ref> This database acts as a [[data warehouse]] for the organization and also stores information regarding the relationships among its assets.<ref>{{Cite web
| url=https://searchdatacenter.techtarget.com/definition/configuration-management-database
| title=What is CMDB (configuration management database)?
Line 11 ⟶ 13:
| date=2015-11-10
| work=[[Axios Systems]]
| url-access=registration
| accessdate=2019-01-14
| archive-date=2019-12-06
| archive-url=https://web.archive.org/web/20191206124426/https://info.axiossystems.com/cmdb-improvement-whitepaper
| url-status=dead
}}</ref>
== Purpose and benefits ==
The CMDB is a fundamental component of
CMDB implementations often involve federation – the inclusion of data into the CMDB from other sources – such as asset management, in such a way that the source of the data retains control of the data. Federation is usually distinguished from ETL (extract, transform, load) solutions in which data is copied into the CMDB.
Line 24 ⟶ 30:
| quote=There are many points of integration that can be used to extend Ansible, including: (...) inventory data retrieved from CMDB systems or cloud sources.
|url-access=registration
| publisher=[[Ansible (software)]]
| accessdate=2019-01-14}}</ref> impact analysis for change management,<ref>{{cite book
| last1=Sauvé
Line 49 ⟶ 55:
== Contents ==
{{Main|Configuration item}}
The CMDB contains and records data that are also called '''configuration items''' ('''CI'''). It also provides details about the important attributes of CIs and the relationships between them.
=== CI attributes and data ===
Line 70 ⟶ 76:
CI types are:
* [[Electronic hardware|Hardware]]
* [[Software]]
* Communications/Networks
* Location
Line 80 ⟶ 86:
==Schematic representations==
CMDB schematic structures, also known as [[database schema]]s, take on multiple forms. Two of the most common forms are those of a [[
[[
[[Semantic data model]]s typically rely on the [[resource description framework]] that maps the relation between a number of things through the use of relationship descriptors, giving context to how things are related to each other.
== Challenges ==
{{unreferenced section|date=July 2024}}
There are three specific core challenges to creating and maintaining a Configuration Management
* '''Relevance''': Collecting data throughout each record's or CI's life cycle is necessary.{{whom|date=July 2024}} This means putting in processes and tools to collect the most recent changes to data as they occur.▼
* '''Maintenance''': Companies face constant change. Data about CIs and the relationships between them are constantly changing. This maintenance is a significant undertaking that is often not planned for or expected.{{or|date=July 2024}} Organisations often find this the greatest challenge.{{fact|date=July 2024}}▼
* '''Usability''': Most CMDBs are just databases. This means they have no traits, features, or benefits of more complex applications. They lack tools to view data via complex
Because of the above reasons, companies usually choose to purchase their CMDBs, rather than designing, building, delivering, and supporting them themselves.{{fact|date=July 2024}}▼
▲* '''Relevance''': Collecting data throughout each record's or CI's life cycle is necessary. This means putting in processes and tools to collect the most recent changes to data as they occur.
▲* '''Maintenance''': Companies face constant change. Data about CIs and the relationships between them are constantly changing. This maintenance is a significant undertaking that is often not planned for or expected. Organisations often find this the greatest challenge.
▲* '''Usability''': Most CMDBs are just databases. This means they have no traits, features, or benefits of more complex applications. They lack tools to view data via complex visualisations or tools for advanced discovery. This means that most companies need to invest in an application layer that adds such constructs to their CMDB, which adds a layer of complexity and cost that most companies do not plan for or expect. However, implementing features that ensure the database is up to date or allow it to interact with systems to run commands, apply updates, or deploy new applications extends the functionality and usefulness of the CMDB.
== See also ==
▲Because of the above reasons, companies usually choose to purchase their CMDBs, rather than designing, building, delivering, and supporting them themselves.
* [[Distributed Management Task Force]] (DMTF) – CMDBf
== References ==
Line 99 ⟶ 109:
==External links==
* [https://tumblr.github.io/collins/ Collins: Infrastructure management for engineers]
* [https://www.objectgears.cz/files/guide-to-cmdb-solution-design Guide to CMDB solution design]
[[Category:Information technology management]]
|