GRIDtoday Logo Intel

DAILY NEWS AND INFORMATION FOR THE GLOBAL GRID COMMUNITY /

   ( Table of Contents )   

Special Features:

EXPLORING COLLABORATION SCENARIOS
By K.S.Venkatram

This article will describe the specification that extends effectiveness in working with remote file systems. We will look at basic interfaces and platforms known to enable file systems across various mappings and connection points. As we step through the requirements for agents and services in the Remote File System Infrastructure, the usage of the Smart Neighborhood design proposes to connect and access the file systems with sensor based definitions, options & extensibility.

For any reference, the URLs for the "Defining a concept for extending the Remote Network File System Services" articles are available as

1. http://www.gridtoday.com/03/1124/102291.html

2. http://www.gridtoday.com/03/1117/102265.html

3. http://www.gridtoday.com/03/1110/102235.html

4. http://www.gridtoday.com/03/1103/102205.html

Publications And Articles For Related Analysis

Previous 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.

For any review of the sensor-controlled network or interest in understanding the sensor and the Simple Model, the URLs for the "sensor-controlled network and connection point services" articles are:

1. http://www.gridtoday.com/03/0602/101487.html

2. http://www.gridtoday.com/03/0609/101511.html

3. http://www.gridtoday.com/03/0616/101543.html

4. http://www.gridtoday.com/03/0623/101584.html

Statement For The Proposed Article

The "new conceptual model" proposes implementation for agents called the Enterprise AccessNConnectDecision Management Agents. The sensor conceives a solution that interfaces with these management agents to extend remote file system services. In the "sensor-controlled network and connection point services" there will be a connection point for each of these management agents on a network computer.

As I am with limited time availability, planning needs this article to be made available shortly, the next article will complete the review for requirements, guidelines and algorithms.

The AccessNConnectDecision Management Agent Services

To develop the AccessNConnectDecision Management Agent services, we propose to look at the algorithms or network services that the AccessNConnectDecision Management Agent will need to conceive and support services.

Like any management agent, the AccessNConnectDecision Management Agent will propose to gather information and make this information available for management requirements. With the information available, the management plan or access to Remote File System resources will be extended by the information and support of the AccessNConnectDecision architecture.

For the enterprise, the AccessNConnectDecision Management Agent will then support algorithms and network services that associate Smart Neighborhood specifications to the Remote File System resources.

Planning The AccessNConnectDecision Management Agent

First Phase Of Development

For any product planning, the AccessNConnectDecision Management Agent will need to be developed through a set of requirements and guidelines. The first phase of the development could develop the interfaces needed to extend the Remote File System on the network computer.

If we focus on Windows platforms or Remote File System services that are accessable from Windows platforms, the first phase will need to develop the following interfaces:

  1. Interfaces invoked by specific Explorer infrastructure services.

    Requirement: Will be published in the next article

    Guideline: Will be published in the next article

    Algorithms: Will be published in the next article

  2. Interfaces invoked by specific Marshalling services to write/read/align with various file formats, images.

    Requirement: Will be published in the next article

    Guideline: Will be published in the next article

    Algorithms: Will be published in the next article

  3. Interfaces to manage using virtual folders explicitly created for the Neighborhood Assistant Decision Support and Information services.

    Requirement: Will be published in the next article

    Guideline: Will be published in the next article

    Algorithms: Will be published in the next article

If we focus on Interoperability and Connection extensions through an Enterprise Resource Service Provider, we will need to conceive services for enterprise definitions, concepts and thus support storing, locating and managing Smart Neighborhood Assistant resources.

For any Management Information Service (ERFSS_IS) on a network computer, the architecture extensions will need implementation of the services that enable network and connection point results for file systems. The second phase will need to develop the following extensions and service interfaces:

Second Phase Of Development

  1. The Interoperability and Connection extensions phase will need to design and conceive Management Information interfaces and services with the ERFSS_IS association, to these interfaces and services the Smart Neighborhood Assistant will associate AccessNConnectDecision Management Index Information Services (ERFSS_IIS) and AccessNConnectDecision services for the ERFSS_IS.

    Requirement: Will be published in the next article

    Guideline: Will be published in the next article

    Algorithms: Will be published in the next article

    The Management Information Services will interact with collaboration support on the network computer, the collaboration, support model published for the Smart Neighborhood is that of an Enterprise Provider. The URLs for the "sensor-controlled network and connection point services" articles are defined in this article for reference and review. On understanding the collaboration services proposed, the third phase will need to design the "sensor-controlled network and connection point services" collaboration support for the network computer.

Third Phase Of Development

  1. For the collaboration support, we will need to design and conceive the services that gather information about connection point services & Enterprise Location System resources and parameters. This will be done with the help of the connection point infrastructure interfaces with components called "PlugNPlaySensorServices". The collaboration services will be termed as EnterpriseLocationSystem_ERFSS_Monitoring and Discovery Services(ERS_ERFSS_MDS).

    Requirement: Will be published in the next article

    Guideline: Will be published in the next article

    Algorithms: Will be published in the next article

  2. For the infrastructure support the third phase could also design collaboration and ELRS or ELRFSS model services with the help of Microsoft's Active Directory solution. The Active Directory infrastructure will be used in the ELRS or ELRFSS for updating, synchronizing resource definitions and AccessNConnectDecision information available on the sensor's network computer.

    Requirement: Will be published in the next article

    Guideline: Will be published in the next article

    Algorithms: Will be published in the next article

    As the proposal is about the AccessNConnectDecision architecture, the phases will need to develop component services for the AccessNConnectDecision services. The phase could develop the design and functionality to extend the SMBIOS to collaborate and support structures that set expectations for the Remote File System resources and set SMBIOS parameters for the AccessNConnectDecision conceptualization, interoperability and content services.

Phases That Develop The AccessNConnectDecision Conceptualization

When focusing on Monitoring and Discovery Services for using the SMBIOS component services, the design effort will need to develop SMBIOS_ERFSS_Monitoring and Discovery Services(SMBIOS_ERFSS_MDS), that gathers information about SMBIOS Interoperable Remote File System resources and parameters by means of the AccessNConnectDecision Management Information Service (SMBIOS_ERFSS_IS).

For the AccessNConnectDecision Management Information Service (SMBIOS_ERFSS_IS), the plan will need implementation of the services that enable network and connection point results for the SMBIOS component services. When this is implemented the Smart Neighborhood Assistant will conceive Management Information interfaces and services with the ERFSS_IS association.

Requirement: Will be published in the next article

Guideline: Will be published in the next article

Algorithms: Will be published in the next article

The phase that develops the SMBIOS Interoperable Remote File System resources and parameters would need to design and implement structures with requirements for these structures to conceptualize AccessNConnectDecision parameters in the enterprise.

Requirement: The requirement summary is that we will need to develop structures and services that extend the SMBIOS for the architecture proposed. In the previous article, we did discuss the SMBIOS structures and for common understanding this article will include the recommendations till the next article closure.

  1. Interoperable Remote File System Parameters (Type 110) Recommendations A new structure for the Interoperable Remote File System Parameters. We could call this structure the Interoperable System Parameters and associate a DMIType 110 with this structure.

  2. Remote File System AccessNConnectDecision (Type 111) Recommendations A new structure for the Remote File System AccessNConnectDecision conceptualization, interoperability and content services. We could call this structure AccessNConnectDecision services and associate a DMIType of 111 with this structure.

  3. Remote File System Connector Information (Type 111-2) Recommendations A new structure for the Connector Information to these Remote File System AccessNConnectDecision content services. We could call this Remote File System Connector Information and associate a DMIType of 112 with this structure.

Guideline: Will be published in the next article

Algorithms: Will be published in the next article

Phase That Develops Event Support And Synchronization

For the AccessNConnectDecision Management Information Service (SMBIOS_ERFSS_IS), the design would need to scope the event support and synchronization planned. In SMBIOS scope, we could look at the well defined SMBIOS structure definitions for the design and implementation of the event support and synchronization.

For structure definition synchronization, content services, events, notifications the phase will need to design and develop the AccessNConnectDecision Management Index Information Service (SMBIOS_ERFSS_IIS).

Requirements: Will be published in the next article

Guideline: Will be published in the next article

Algorithms: Will be published in the next article

For delivering events, notifications, the phase could conceive implementations that use the System Event Log structure from the SMBIOS specification.

Requirements: As defined in the SMBISO specification, the System Event Log structure with OEM-specific Access Methods that can be defined, added standard log header definitions,and a mechanism to allow the log entry's variable data formats to be described.

Guideline: Will be published in the next article

Algorithms: Will be published in the next article

For change notification, the phase development could use the SMBIOS structures and work with the SMBIOS specifications for functions to notify or get the structure change.

Requirements: Will be published in the next article

Guideline: Will be published in the next article

Algorithms: Will be published in the next article

Phase That Designs And Conceptualizes The Smart Neighborhood Enterprise

For developing the Smart Neighborhood Assistant to conceptualize AccessNConnectDecision parameters in the enterprise, the design and development effort will need to decide or conceive the various component services that are interoperable with the help of the Enterprise specification for the Smart Neighborhood Assistant.

Requirements: Will be published in the next article

Guideline: Will be published in the next article

Algorithms: Will be published in the next article

About The Author

K.S.Venkatram is a computer engineer from the University Of Poona.

( Top of Page )

   ( Table of Contents )