DAILY NEWS AND INFORMATION FOR THE GLOBAL GRID COMMUNITY /    ( Table of Contents )

Special Features:

MOVING PAST LIMITATIONS IN REMOTE FILE SYSTEM INFRASTRUCTURE
By K.S. Venkatram

This article will describe the specification that extends effectiveness in working with remote file systems. We will look at holes in the Remote File System infrastructure and start the smarter interest for resolving and modeling to recycle past these infrastructure limitations.

Publications And Articles For Related Analysis

Development plans, interoperability and extensibility from this article is published as part of the series about "Defining a concept for a Smart Neighborhood" in the Grid Today. The article is not a published solution. Rather, they introduce the reader to a concept for a smarter neighborhood and guide the user through a comparative analysis and extensibility of a sensor-controlled network in enterprise scenarios.

Conceptual Specification

To present the specification we will first address the analysis shared in the previous article.

1. What exactly is the Remote File System AccessNConnectDecision Model and how do I use it?

Today, interoperability is core for any network connectivity solution. The Remote File System AccessNConnectDecision Model will base it's specification on the principle of using network connectivity to access or use remote files, storage and remote services.

The Remote File System AccessNConnectDecision Model proposes integrating and supporting the following services, these services expect to support new mechanisms of remote file system access.

• Interfaces, Basic services.
• Neighborhood Assistant Interfaces invoked by specific Platforms.
• Interfaces invoked by specific Platform connectivity services.
• Interfaces invoked by specific Platform File System services.
• Interfaces invoked by specific Explorer infrastructure services.
• Interfaces invoked by specific Marshalling services to write/read/align with various file formats, images.
• Interfaces to manage using virtual folders explicitly created for the Neighborhood Assistant Decision Support and Information services.

2. What exactly is meant by Remote File System AccessNDecision services and how do I use it?

The solution proposes services and concepts that can be used to write, read, report and manage the new virtual folders. These virtual folders will then be available for Assistant-Enabled connectivity decisions and neighborhood services for remote file system information.

These Remote File System AccessConnectNDecision services will model a grammatical set of rules and these rules will expect to enable the extensible network user experience or interoperate with multiple remote file systems.

This new architectural experience would smarten the manageability and effectiveness while administering remote file system access in many capabilities. From this service understanding we review the "Services and Interfaces" proposed by a new concept called the Smart Neighborhood Assistant. The Smart Neighborhood Assistant designs the support for Assistant-Enabled concepts and the new Decision Support and Information services for the remote file system. The Smart Neighborhood Assistant integration in turn would help network users or solutions to manage the remote file system access in connectivity and other effective ways.

3. What exactly is extended by Smart Neighborhood Assistant services and how do I use it?

The new remote file system support integrates a concept called the "Smart Neighborhood Assistant". The services proposed by the Smart Neighborhood Assistant set guidelines to assist, enable smart decision support while working with the remote file system.

For any interest, the Smart Neighborhood Assistant will be designed with components that extend the interfaces of the Remote File System AccessNDecision proposal from support today to support for updates or newer releases of the Operating System itself. Today we depend on the company developing the Operating System and File System infrastructure to manage the remote file system services, this proposal does extend the scope to smarten the manageability and effectiveness while administering remote file system access in many versions or capabilities.

We change our focus from just installing Operating System Support and Network Capabilities in the form of services, clients, connectivity support. We look at the extensible model to support file access and neighborhood functionality without the experience of waiting for patches or updates or new software release for network capabilities.

The model makes it possible to separate the support provided by the company delivering the Operating System and File System infrastructure to experiences where players delivering products for the Operating System and File System infrastructure can extend the Remote File System AccessNDecision proposal.

The AccessNConnectDecision components expect to support services that help remember, manage and realize extensibility of users and network experiences while working with files. The components propose to interface with the network and remote file systems, with the help network client services, shell/explorer services, and relevant marshalling services to access files and control access.

3.1 The Smart Neighborhood Assistant, AccessNConnectDecision components and introduction

We could term the first component of the Smart Neighborhood Assistant as "NetworkServerSensorServices", this component interfaces with the host, remote server and supported remote file systems to enable services.

We could term the second component of the Smart Neighborhood Assistant as "PlugNPlaySensorServices", this component interfaces with the host, remote server and remote file system to enable services. PlugNPlay in this conceptualization is what we experience today with resources, new hardware, drivers, services that are activated, managed and relied on without any explicit functionality enhancement in the infrastructure running the new services.

Similar factors conceive a model in which any network user could effectively rely on "PlugNPlaySensorServices" for dynamic administration and decision support using the specification of these resources. The "PlugNPlaySensorServices" for a particular platform will first expect the "NetworkServerSensorServices" to resolve initial requirements and expectations for defining the network components that the network resource is available in.

After defining the network components, the interaction with the network resource or any new remote server, new remote file system(s) can be supported by describing the network resource or new remote server or new remote file system information in a grammatical but extensible model that assists and manages the remote file system administration.

We could term the third component of the Smart Neighborhood Assistant as "InterceptionSensorServices", this component interfaces with the infrastructure and file system by intercepting file access. There are many solutions today that intercept the file or file system access, the Smart Neighborhood Assistant proposal and design introduces a new mechanism of intercepting file or file system access. The Smart Neighborhood Assistant proposal and design coceptualization will manage the interception, administration and explore network options with enhanced connectivity.

We could term the fourth component of the Smart Neighborhood Assistant as "PlugNPlayServices", this component interfaces with the host, remote server and remote file system by reading the grammatical extensible model that describes functionality and procedures to enable extensible connectivity. With the interception, read, model resource conceptualization done, the file system will be conceptually assisted to manage, extend neighborhood functionality and capabilities.

4. What binds the Remote File System services in the network today and what is extensible through the Model proposal?

Today we work with Remote File Systems with explorer interfaces, client services to map drives to remote machines. With these interfaces and services we access and interact with the remote file system. The effectiveness of the solution today is incomplete for many service expectations in infrastructure and extension.

Microsoft today is publishing information about it's new file system called the WinFS, which is supposed to rely on a different model for access and interactive proposals. For any interest in the WinFS, the msdn site can be accessed for information from Microsoft.

Keeping in mind that companies like Microsoft will support newer specifications and manageability in their file systems, we could look at what the network extensibility means for any infrastructure. We will look at some model extensions to the remote file system that could value add to the extensibility and interactive services. As the Smart Neighborhood Assistant designs a solution to deal with the extensibility and interactive limitations of accessing network file systems, we preview some interesting expectations in this proposal.

5. What does it mean to connect and access with definitions, options and extensibility ? In the Neighborhood or domain, remote file system connectivity is more enabled by extensibility in "Network Infrastructure".

When the connectivity and extensibility is past what companies support as part of their Operating System, factors that conceive many options are "interoperable natures of services as we work with them and associate services with many solutions". We can extend interoperable services, if the definitions and concepts of accessing a remote file system is supported with various component interfaces.

When we talk about component interfaces we need to understand the architectural options. To achieve this we look at the architectural services in the remote file system and services domain and then associate their bindings with definitions and concepts.

• UIServices -- these are architectural services that help users to interface with the Remote File System services.
• RoleModelServices -- these are architectural services that help users work in security or network user involvements. As rules decide services in the "RoleModelServices" architecture, if the rules are supported for the remote resource, then the architectural services could support extensible network administration.
• ConnectivityModelServices -- these are architectural services that help users or network solutions to connect onto remote file systems in any network access.
• CaptureInferenceTool -- these are architectural services that help users or clients or different network interfaces to capture the file system access and infer principles that guide the file system and administration support. Decisions for the remote file system are possible by capturing the experience, if the experience is captured then the model enables information, extensible rules, connectivity decisions to support decisions for infrastructure dependencies or effectiveness.
• BackEndServices -- these are architectural services that help network file system services. The BackEndService will exist locally or as remote services, these services interface with the file system to develop and extend the scope. Today we need to connect to a remote file system and then run an explorer to interact with a regular view of the remote file system. With the help of this regular view, the user actively works with the file system.

There is nothing secure or decision dependent in this view. We can make any number of remote updates or attempt any number of remote updates. The remote file system does not interoperate with principles that enable extensibility. This simple option could be addressed by running a BackEndService for a Network Infrastructure. The BackEndService interoperates with the help of CaptureInferenceTool mechanisms, Interactive Services and FrameWork services. This BackEndService administration changes the view of the remote file system administration with the help of the Smart Neighborhood Assistant.

• FrameWorkServices -- these are architectural services that help solutions in different sets of involvements, Microsoft expects the .NET or Developments using the .NET to provide the framework. Today the framework for Remote File System Services is a market set by what we need as infrastructure, we will realize this through the "Remote File System Access Decision Model".

6. What binds the Network extensibility in the Application proposal? The Network extensibility in the Application proposal is dependent on ApplicationModelServices, UIServices and FrameWorkServices. The Application market is impacted as much effort is needed to align with dependencies are for specific clients or principles. In this article, the continuous effort we find in the Application proposal will be revised relying on design as one of the options.

7. What binds the Network extensibility in the Connectivity proposal? The Network extensibility in the Connectivity proposal is dependent on RoleModelServices, UIServices, ConnectivityModelServices, CaptureInferenceTool and BackEndServices. The effort spent in the Connectivity today, is working for client version support and inter-related alignment to access remote network computers or access the network. As we are interested in network extensibility for the Connectivity proposal, we will review how the same connections can integrate assistant extensions for extensible network principles.

8. What is the Extensibility in the Network Infrastructure proposal? This can be described as supporting Network Infrastructure principles with the help of RoleModelServices, UIServices, ConnectivityModelServices, CaptureInferenceTool, BackEndServices and FrameWork services.

The Decision model is designed with the help of different services, each of these services interface with the network and remote file system to enable the Smart Neighborhood Assistant proposal.

9. In the conceptual preview, we look at descriptions first and then specifications for these different services.

• Describing "NetworkServerSensorServices": With these component interfaces the Smart Neighborhood Assistant expects to understand the remote services or network support or remote file systems. We expect to use the NetworkServerSensorService to describe the remote file system or server for infrastructure principles and modeling.

The Neighborhood Assistant will extend services for new network hardware, disk hardware, network driver or disk driver and service as flexible support. The Neighborhood Assitant model's extensibility for flexible support will be conceived and extended by what is termed as the RoleModelService infrastructure.

If the new network hardware, disk hardware, network driver or disk driver and service associates model rules with the infrastructure, these rules will model the network component and go on to extend assisted and flexible experiences for this network component when it is accessed for network or remote file system information.

For any reader concern, we do not expect to override the need to install drivers for new hardware or for new resources but will fix support through the RoleModelService assistance and model.

What Does This Mean?

With the modeling complete using the RoleModelService, the Neighborhood Assistant will start supporting the newer hardware, disks, drivers, services or extensions for the infrastructure principles and modeling needed to provide the new specification.

• Describing "PlugNPlaySensorServices": With PlugNPlaySensor component interfaces the Smart Neighborhood Assistant expects to plug-into or extend by flexible interfaces, any revision in understanding the remote services or network support or remote file systems. This is done by implementing a PlugNPlaySensorService for that support. If we deal with the winFS, then the NetworkServerSensorService and the PlugNPlaySensorService implementation will relook at the winFS infrastructure to extend these remote file system services etc.
• Describing "InterceptionSensorServices": With these component interfaces the Smart Neighborhood Assistant and client will be active in intercepting file access using the decision model functionality and procedures. This interception at the file system level will manage and enable what we are proposing as assistance in connectivity.

While discussing "InterceptionSensorServices", the extensibility needs the specification to align for specific component interfaces. We today deal with neighborhoods that are made up of different support expectations for different network scenarios. This means that the component interfaces that marshall or manage using virtual folders for Neighborhood Assistant Decision Support and Information services will need to reviewed as the expectations for the infrastructure changes.

• Describing "PlugNPlayServices": This PlugNPlay support design with the grammatical model and procedures will enable multiple services and the much needed file system scope. With this extension, the Neighborhood assisted solution will be functional as flexible interfaces for infrastructure changes, network solutions, network file system interception and other expectation in diverse frameworks.

With PlugNPlay component interfaces, the Smart Neighborhood Assistant will enable newer file system infrastructure services and support. The extension is possible by interfacing with the file system usign grammatical rules. When the grammatical rules integrate with the file system, we have a Smart Neighborhood Assistant solution and alignment. When this is complete the alignment can use the descriptions, roles for functionality and procedures to enable the experience of extensible remote file system access and connectivity.

About The Author: K.S.Venkatram

His professional qualification is Computer Engineer from the University Of Poona. He holds a Microsoft Certified Professional certificate in Windows 2000 Networking Infrastructure.