Environments in the CMDB Part 2.
How to best model "environments" in the CDMB?
We have a bit of a conundrum with our CMDB implementation. One of our critical pieces of data is the environment each server, database and application/application system participates in. Example environments might be "dev", "sys test", "uat", "prod". One challenge we have is that a CI might participate in multiple environments. This is especially true with servers which may host dev, and sys test for example.
We have come up with two options. 1.) Create a CI which represents the environment and create a "is member of" relationship between the CI for the servers, applications and databases to the environment CI. OR 2.) Create an attribute on each server, application, or database CI which would be populated with one or more environments (e.g. prod, or dev:sys test).
The major downside of the attribute is it doesn't do a very good job of managing the one to many relationship. The downside of the CI approach is it creates a monster relationship between every server, application and database and one of the environment CI instances. This relationship keeps showing up in the CI viewer.
Any thoughts from the experts?
Bailouts 2.0 and 3.0
Now that bailout 1.0 is behind us it is time to start thinking about the future:
Bailout 2.0: Healthcare
We need a healthcare solution in the US which is cost effective for end users, and is available to all citizens regardless of their preexisting conditions, or financial situation. Perhaps the government can bail out the healthcare system next?
Bailout 3.0: The Environment
The environment, needs a bailout plan. We need to infuse capital into technology which can reduce our reliance on fossil fuels. This will help the US become a global leader in clean technology and will create new research and manufacturing jobs.
Sounds to me like these might be some great ways to spend our tax dollars? 1.2 Trillion to bail out the financial services industries. How much could bailout 2.0 and 3.0 cost?
0 Comments