When I think about an ITIL toolset, or any IT toolset, I look at open and not so open tools...
Service Desk -- phone system + ticketing system integrated with email -- I don't know about the open source space here
Incident Management -- a non-technology system like ICS is very helpful, but then using a general tracking/ticketing system to record stuff is crucial - remedy, bugzilla, rt... they all work
Configuration Management -- you just need a database - excel can perform the function sometimes, but later mysql, oracle, heck, even ldap can be useful Release Management -- to me, this is mainly documentation, for which wikis, html, and yes, even word documents can be useful. This ties in with financial management strongly - it is an asset database too, or close to it.
Service Level Management -- Making sure the other tools you use let you track this is about all you generally need. On the reporting front, well, you need integration of tools - more on that later...
Capacity Management -- mrtg/cacti let you look at how much your systems are getting used, and you need some method to load up your systems to your mrtg/cacti, in a test environment, can tell you how much capacity you have
Problem Management -- use the same tracking for incident and problem management to make it easy... bugzilla or rt for example
Change Management -- 2 main bits - have a policy - that's documentation (wiki, html with apache, heck, even word docs can work) with plans and docs about the changes to be made.
Continuity Management -- planning (docs)
Availability Management -- ties strongly to SL management - monitoring is a big part of this - nagios is a great open source monitoring tool with a little help to have it handle different kinds of escalations you might wanna do.
Financial Management -- I generally take this back to configuration management, some documentation about policy...
Security Management -- configuration management database is a biggie here of course, but further than that there are myriads of tools (snort with extra stuff for intrusion prevention, for example)
The biggie in the end open source or purchased, is work-flow and tying it all together. Do your systems get in your way or help you out? If they get in your way for the most part, then that is all wrong! If people using the systems hate them, that's a clear sign that it is all wrong, even if some managementy folks like aspects of them.
You have to do custom work with any of these systems, purchased, open source, or home-grown, to tie them together and help you do what you need done.
ITIL is just a framework to make sure you don't forget anything. If you do anything often enough, you need to proceduralize, document, and automate it so you don't have to any more or so it is easy.
This tying together helps connect other bits - like for reporting. You have to get reports using your monitoring with load generation tools to see about capacity reporting. SLA reporting comes from monitoring reports, but outages and tracking for problem management requires looking at, categorizing those incidents...
没有评论:
发表评论