To: Nancy McKinney who wrote (25908 ) 2/1/2000 10:57:00 PM From: J Fieb Read Replies (2) | Respond to of 29386
Nancy, Here are a few things that should go on one page... How do you like them beans? How long do you have to cook an Infinite Disc Bean B4 it's done? In our storage example, we'll need Management Facades for the disks, volume manager, and filesystem. If the disks were in a storage network, we would additionally benefit from a Management Facade for a fabric switch. We'll create two FederatedBeans components for this example. The first component maintains a pool of spare disks that can be used for multiple applications and hosts in the storage network. It is capable of allocating these disks on demand and controlling their connection to a host by using the fabric switch's Management Facade. We will call this component the Storage Pool Bean. The second FederatedBeans component will monitor filesystem utilization and try to predict when the filesystem will run out of space. This process could use a method as simple as a high-water mark, or as complex as an analysis of previous usage patterns. We will call this component the Infinite Disk Bean. The relationship of the FederatedBeans components to the Management Facades is shown in Figure 3. Figure 3. Infinite disk management example The Storage Pool Bean The Storage Pool Bean handles the allocation of disks between the various hosts in the storage network. It exposes an interface that allows other FederatedBeans components to request allocation of a disk to a given host for use by storage software or applications. When new disks are added to the storage network, the bean notices the new disks and adds them to its pool. It will keep its pool of disks in a special zone on the storage network by controlling the fiber channel fabric switch through its Management Facade. Finally, it exposes an interface that allows disks to be returned to the pool. Infinite Disk BeanThe Infinite Disk Bean sees to it that an application never runs out of space. This adds to application availability without overprovisioning. Its job is to tune the capacity of the available storage to the application's need. It accesses usage information from the filesystem's Management Facade and tracks its usage over time. After predicting an out-of-space condition based on the history of past usage, it then calls the Storage Pool Bean to get a disk from its pool. When the Storage Pool Bean gets the request for the disk, it calls the switch's Management Facade to change the zone of the newly allocated disk to that of the host. It next creates a device driver entry for the disk on that host and instantiates a Disk Management Facade as a single point of control for the new disk. The bean then returns a reference to the new Management Facade back to the Infinite Disk Bean. The Infinite Disk Bean next calls the Volume Manager Management Facade to add the new disk to the RAID stripe used by the filesystem. Lastly, the bean causes the filesystem to grow to its new size through the filesystem Management Facade. The bean could also implement a policy for reclaiming disks based on usage as well. Conclusion The above example shows how Jiro makes possible software that can increase availability and help reduce the cost and complexity of management. The FederatedBeans components that are created are also dynamic Jini services that are available throughout the network. The new paradigm for management software is multiple-vendor creation and reuse of these FederatedBeans components. The Storage Pool bean in our example could also be used by a component that consumes disks due to failure predictions, for example. Next month, we'll see some code examples of FederatedBeans components, and look at some information on how to use some of the static base services in a Jiro management domain. Page 1. Page 2. From monolithic applications to components Printer-friendly (all-in-one) version -------------------------------------------------------------------------------- We are excited about the arrival of the Jiro Technology Developer's Release and what it will mean to our business," said Ben Preece, lead engineer of Ancor Communications. "Jiro technology will make it possible for Ancor's switches to interoperate with other components on heterogeneous SANs." Yahoo's Viangio on who wants the beans..... Any SAN software or management vendor that wants to provide intelligent policy based SAN management solutions. One example is Sun itself as noted by another poster, Sun is in the process of rewriting its entire enterprise management framework in Java using services from Jiro, DMTF CIM (see www.dmtf.org). Where will this be used? - all over the Internet. If I'm a user of an Internet Mail, Application or File Storage Services provider, I never want to see an out of disk space error when I'm trying to send stuff up to the Internet. The Infinite disk space bean is how a Data Center can provide this on demand policy based management 7 x 24. Further, disk failures will automatically cause a back up job to kick in or more disks to be zoned in to replace the lost capacity. All this makes for an Intelligent SAN. I don't think we would expect to see Dell or Compaq demonstrate this vision. This kind of vision is what made Sun the Internet leader. People have short memories. Sun is not about to go away: it's inventing the new Internet storage philosophy by laying foundation stones in place in the form of Jiro, switched ANCR fabrics etc. This stock caught a Winter flu but it's alive and kicking now... Technocrat, George D., others.....Can the Fibre Alliance use beans if they wanted to? Will they want to? Will this speed up the evolution of the data center? Pretty high end stuff!