Tuesday September 14, 2004 | Tobin Coziahr's blog notes from an insomniac engineer |
|
SMF/Predictive Self Healing Overview Predictive Self Healing is an architectural framework made up of several pieces. The one that I've been working on is SMF, or Service Management Facility. It's an infrastructure that provides several functions: 1) Defining services for Solaris, which can be the state of a device, a running application, or a set of other services. Each service is referred to by a unique identifier. 2) A formal relationship between services, with explicit dependencies. 3) Automatic starting and restarting of services. 4) A repository to store service state and configuration properties (negating the need for dozens of configuration files scattered throughout the system. The "thousand mile view" of SMF is that the system is managed by a master "restarter" named Let's look at the pieces of SMF a little closer. Services A service is the fundamental unit of SMF. Each service can have one or more instances, which is a specific configuration of a service. For example, Apache is a service. An Apache daemon configured to serve www.sun.com on port 80 would be an instance of that service. Apache could have several instances, all with different configurations. The service holds basic configuration properties that are inherited by each of its instances, but each instance can override configuration properties, as needed. There are also special services called milestones. These are a service that correspond to a specific system state, such as "basic networking" or "local filesystems available". They are basically a list of other services, and they're considered to be online when each of their component parts is online. Each service is identified with an FMRI, or Fault Management Resource Identifier. It's the unique identifier representing a service, or instance. For example, the FMRIs can be a bit of a handful to type, so you'll find that most SMF commands will accept the "shortened" versions of a service's FMRI, given that it only has one instance. For example, most utilities will accept You will have noticed that telnet is preceded with the word network. SMF contains several categories for services, to provide organization and uniqueness of naming. The standard categories are:
States Each service on the machine is always in one of seven discrete states, observable by the SMF CLI tools. The possible states of each service are:
That's about enough typing for me tonight. Next time we'll start to look at how services are described, and how you administer the system using SMF. As usual, if you have any questions, please feel free to ask them in the comments section. (2004-09-14 01:49:18.0) Permalink Comments [1] Post a Comment: Comments are closed for this entry. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Posted by c0t0d0s0.org on September 14, 2004 at 02:18 AM PDT #