Definitive Media Library - Wikipedia
I can not, somehow, think of webob.info file being a CI in a CMDB. So, what is the relationship between CI of CMDB/ITIL and CI of SCM Plan?. Indeed, this relationship between information and decisions spans far In SCM, a type of CMDB is called the Definitive Software Library (DSL). One clearly needs to understand the relation between the three so that (CMDB) for the change logs, RFCs, definitive software library (DSL).
Unless you know the CI relationships involved, you can spend a great deal of time investigating the wrong problem.
An accurate CMDB can help you avoid solving or expending to many resources on the wrong problem. We cannot do a true change impact analysis without an accurate CMDB. Without some form of a CMDB Change Management is extremely difficult to do as we cannot necessarily identify what it is we are changing or what the implications of those changes will be.
Changes are there is no CMDB of note in use in these circumstances. Knowing which applications are resident where, how much compute, memory, and storage the servers have, the network zones, network connections, the SANs and how they are used, which COTS products are installed where, etc.
A good CMDB with good reporting can help educate them rather nicely. No matter how much availability data you collect, without a CMDB to tie it all together, you cannot easily obtain much real value from it.
It also becomes, when combined with Change and Release Management, the mechanism by which the IT Service Continuity plan is kept current and relevant. There is no danger that obsolete version s of CIs that are incorrectly assumed to be unchanged will be used within the Release.
There is less temptation to short-circuit testing of supposedly unchanged CIs and of the interface s from changed CIs to unchanged ones. Any problems are therefore more likely to be detected and rectified before entry into the live environment.
Definitive Media Library
The disadvantage is that the amount of time, effort and computing resources needed to build, test, distribute and implement the Release will increase. Although in some circumstances the testing of a delta release see below may need to be as extensive as that for an equivalent full Release, the amount of building effort required to test a delta Release is normally less than for a full Release.
Regression testing as part of the process of implementing a full Release allows a large number of components to be retested to ensure that there is no degradation in system function or behaviour. An example of a Full Release could consist of the complete Release of a new version of client desktop software, or client desktop hardware, or both. Delta Release A delta, or partial, Release is one that includes only those CIs within the Release unit that have actually changed or are new since the last full or delta release.
For example, if the Release unit is the program, a delta Release contains only those modules that have changed, or are new, since the last full Release of the program or the last delta Release of the modules.
There may be occasions when Release of a full unit cannot be justified. In such cases, a delta Release may be more appropriate. A decision should be made on whether delta Releases are allowed, and under what circumstances.
It is recommended that delta Releases be allowed, with the decision being taken case by case. In each case the Change advisory board CAB should make a recommendation, based upon all the relevant facts, on whether the Release unit stipulated in the Release policy is appropriate or whether a delta Release is preferable. In making its recommendation, the CAB should take into account: For example, Changes to one system or suite will often require Changes to be made to others.
If all these Changes have to be made at the same time, they should be included in the same package Release.
A package can, for example, contain an initial version of a new TP service, several new versions of batch programs, a number of new and initial versions of individual modules, together with the Release of a complete new desktop system both hardware and software. Both full and delta Releases may be included.
A CMDB Runs Through IT
The use of package Releases can reduce the likelihood of old or incompatible software being wrongly kept in use. It can encourage organisations to ensure that all Changes that should be made concurrently, in different suites and systems, are actually made concurrently.
It can also encourage organisations to test the interworking of these suites and systems fully. Care should be taken, however, not to exceed, in any particular package Release, the amount of Change that can be handled comfortably. When making a decision on what to include in the package, care should be taken to ensure that the full impact of all individual parts on each other part is understood and has been properly assessed. This one storage area may in reality consist of one or more software libraries or file-storage areas that should be separate from development, test or live file-store areas.
It contains the master copies of all controlled software in an organisation. The DSL should include definitive copies of purchased software along with licence documents or informationas well as software developed on site.
Master copies of controlled documentation for a system will also be stored in the DSL in electronic form. The exact configuration of the DSL that is required for Release Management should be defined before development commences. The definition should include: The only way to keep track of the complex nature of these systems was through technology.
This technology came in the form of a CMDB, or what most people called an asset database. More notably, these complex systems had become inextricably bound to business execution.
A CMDB runs through
Prior to the s, computers were either isolated, well-defined islands that ran the back office of the business or they were intellectual tools.
By the late s, it became clear that the state of IT had a direct impact on the state of the business, and the state of IT was not good. The s saw the rise of distributed computing as the central nervous system of the business, and a mechanism was needed to bring discipline to the operation of this wily beast.
Although it grew across Europe in the late s, its worldwide appeal finally exploded on the scene in when North American adoptions reached critical mass. The chart in Figure 2.