 |
|
DAILY NEWS AND INFORMATION
FOR THE GLOBAL GRID COMMUNITY /
|
Special Features:
EXPLORING COLLABORATION
SCENARIOS
By K.S. Venkatram
This article will describe the specification that extends effectiveness in
working with remote file systems.
For any reference, the URLs for the "Defining a concept for extending the
Remote Network File System Services" articles are available as
1. www.gridtoday.com/
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. www.gridtoday.com/03/0602/101487.html
2. www.gridtoday.com/03/0609/101511.html
3. www.gridtoday.com/03/0616/101543.html
4. 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.
Innovation is conceived mostly by analysis for effectiveness and smarter
plans. With model concepts and planning, specifications and analysis could
guide concepts to deliver enterprise services and systems. In this article I
review the SMBIOS and effectiveness for comparative analysis and
extensibility.
Innovation And Effectiveness
The Remote Network File System Services could interoperate with the help of
"sensor-controlled network" and services like the SMBIOS. Importantly for
extensibility in the neighborhood, the Remote Network File System Services
could interoperate with the "connection point services described in the
sensor-controlled network".
For readers, the "new conceptual model" presented in this article develops
file system fortification and interoperable execution. The "new conceptual
model" will resultantly design for new neighborhood effectiveness with the
help of interoperable implementations. In summary the reader will be
introduced to the following interoperable implementations:
a. The AccessNConnectDecision Management Agent Services
b. The Enterprise Remote File System Server (ERFSS) Services
c. The Enterprise LDAP Resource Server (ELRS) Services
d. The Enterprise Services for the Remote File System with Algorithm
Value
e. The Enterprise Services for the Remote File System & Interoperable
Remote
File System Resources
Understanding The Implementation Of The Accessnconnectdecision Management
Agent In This New Conceptual Model
The proposal for the new conceptual model defines connection point
interfaces
like the "Tracking_Submit" and "Tracking_Receive" functions that must be
implemented by any resource service extension integrated with the
sensor-controlled network. Invocation of the "Tracking_Submit" and
"Tracking_Receive" functions will be stringently verified for parameters and
op-codes. Parameters are passed to the "Tracking_Submit"and "Tracking_Receive"
functions by passing arguments in a formatted string such as "contributor=",
"contribution= ", "response= success or failure or response file" The op-codes
are required for the functions to execute certain services in resource
reporting and access.
Configuration for a typical AccessNConnectDecision management agent node
supporting connection points to a Remote File System - Illustration I of
II
Illustration I
<application>
<directory 1>SMBIOS</directory 1>
<directory 2>AccessNConnectDecision</directory 2>
<global identifier format>
<refresh_global_identifier>
Disabled
</refresh_global_identifier>
<include_directory>
Enabled
</include_directory>
<refresh_include_directory>
Enabled
</refresh_include_directory>
<include_global_time>
Disabled
</include_global_time>
</global identifier format>
<global identifier>
SENSOR_2-WAY_SMBIOS-AccessNConnectDecision_REMOTEFILESYSTEM-NODE
</global identifier>
</application>
1. In order to publish resources in an ERDb, the sensor will use the
Enabled
or Disabled setting in the application section. When this setting is enabled,
the sensor will use the connection point to describe the resources available
and create an industry conformant schema file for these resources. The schema
file will be used in processing the resource xml files and publishing the
resources in the required ERDb after suitable schema updates.
Like regular databases, Enterprise Resource Databases will be installed on
Enterprise Remote File System Servers. The Enterprise Remote File System
Server (ERFSS) is an Enterprise Location Server (ELS) that helps collect the
list of AccessNConnectDecision definitions, SMBIOS_AccessNConnectDecision
definitions and remote file system resource definitions from the various
network computers and adds the same to an Enterprise Resource Database.
2. Enterprise Resource Databases (ERDb) will host a set of tables to store
and
track information about various resources available in an enterprise grid. The
proposed ERFSS solution uses information publishing and information
synchronization services to guide, report and architect the network mechanism
of extending remote file system services, enterprise definitions and
management resources irrespective of their location in the enterprise
grid.
3. The Enterprise Remote File System Server (ERFSS) will store and
synchronize
resource definitions across other Enterprise Remote File System Servers
(ERFSS) and Enterprise Resource Databases (ERDb). An Enterprise Resource
Server will use a distribution service to synchronize resource definitions,
thus enabling tracking resources in an enterprise grid with mixed platform
support.
The functionality on an ERFSS will update, synchronize resource definitions
and information available on the sensor's network computer into an Enterprise
Resource Database.
4. The schema for the Enterprise Resource Database (ERDb) is a Simple Model
to
store and report information of any resource on the network. To understand the
Simple model, the following guidelines are presented:
+ In the Enterprise Remote File System Server (ERFSS), resources are
described
as AccessNConnectDecision definitions, SMBIOS_AccessNConnectDecision
definitions and remote file system resource definitions. All resources will
have an Enterprise identifier.
+ In the ERFSS, all resources will have a resource class. Commonly known
classes are Hardware class, or Software class, or Performance Indicator class
or Extension Resource class. In this case the Extension Resource class is the
"Enterprise AccessNConnectDecision services for interoperable Remote File
Systems".
+ In the ERFSS, all resources will have an Object-Collection
identifier.
+ In the ERFSS, an Object-Collection model will define resource class and
the
various attributes associated with the class. All resources in the
Object-Collection model will have attributes like a resource identifier, a
description, value and units for the value.
+ In the ERFSS, all resources will have attributes that track the resource
on
the basis of the timestamps. The variety of timestamps in the ERS are:
a. Timestamp when the resource was configured or described first in the
enterprise network.
b. Timestamp when the resource was tracked or accessed or updated in the
enterprise network.
c. Timestamp when the resource was deleted or exposed to lifecycle updates
in
the enterprise network.
+ In the ERFSS, all resources will have attributes like lifetime signing
and
criticality that determine the lifecycle of a resource in the enterprise
network.
+ In the ERFSS, all the attributes will focus on manageability and
strategizing focus for resource lifecycles in the enterprise network.
5. The Management Agent Service settings include a server section will
along
other configuration options, the server configuration will describe the
identity of the Enterprise Remote File System Server (ERFSS) and the identity
of the Enterprise LDAP Resource Server (ELRS) or Enterprise Remote File System
Server (ELRFSS).
The functionality on an ELRS or ELRFSS will update, synchronize resource
definitions and information available on the sensor's network computer into a
LDAP Directory.
The Active Directory solution could be reviewed for updating, synchronizing
resource definitions and information available on the sensor's network
computer. In the next article we will focus on the collective alignment for
the Active Directory ELRS or ELRFSS model.
6. Looking at domains and capabilities for Windows platforms, the
sensor-controlled network could be planned with a Windows platform Enterprise
Resource Server (WindowsERS) with future interest focusing on Enterprise
Resource Databases or the winFS database.
7. Looking at domains and capabilities for NetWare platforms, the
sensor-controlled network could be planned with a NetWare platform Enterprise
Remote File System Server (NetWareERFSS) with any Enterprise Resource
Database. The sensor-controlled network proposes interoperability and
Enterprise Resource Database services to work effectively in a mixed grid.
8. Understanding The Implementation Of The Enterprise Remote File System
Experience
a. In the proposed Enterprise Remote File System infrastructuture,
AccessNConnectDecision design specifications direct the scope and guidelines
recommended to implement the solution.
b. The AccessNConnectDecision design requires the implementation of
specific
functions, input and output parameter formats and published op-codes for mixed
grids and management grids.
c. The Enterprise Resource Server (ERS) revises interfaces and experiences
to
become the Enterprise Remote File System Server (ERFSS), this proposes support
to extend the file system; the ERFSS will store and synchronize Remote File
System resource definitions across other Enterprise Remote File System Servers
and Enterprise Resource Databases to extend support through the
AccessNConnectDecision parameters for network services, interfaces, sensor
based definitions and sensor based lifecycles.
Enterprise Location System - Sensor Configuration for the
AccessNConnectDecision management agents - Illustration II of II
Illustration II
<application>
<service>
<wellknown
<parameter name="mode" value="Singleton"/>
<parameter name="type" value="AccessNConnectDecision"/>
<parameter name="lifetime" value="extension"/>
<parameter name="algorithm" value="ERFSS"/>
<parameter name="objectURI" value="Custom_AccessNConnectDecision"/>
/>
<channel
<parameter name="ref" value=""/>
<parameter name="port" value=""/>
/>
<handler
<parameter name="arguments" value="contributor,contribution,response"/>
<parameter name="responsefile" value="AccessNConnectDecision.int"/>
<parameter name="submit" value="Custom_AccessNConnectDecision_Submit"/>
<parameter name="receive" value="Custom_AccessNConnectDecision_Receive"/>
/>
<filesystem
<parameter name="schema" value="xml"/>
<parameter name="schemafile" value="AccessNConnectDecision.scm"/>
<parameter name="resourcefile" value="AccessNConnectDecision.xml"/>
<parameter name="rulesfile" value="AccessNConnectDecision.rul"/>
<parameter name="contentdirectory"
value="c:\\sensor\\content\\Custom_AccessNConnectDecision"/>
<parameter name="cache" value="enabled"/>
/>
</service>
</application>
9. The AccessNConnectDecision Specification
9.1. Description for the
The algorithms parameter for the Enterprise Remote File System
infrastructuture, define the support for the experience proposed as
infrastructure support.
Algorithm Parameter a. We could have ERFSS_Monitoring and Discovery
Services(ERFSS_MDS), that gathers information about Remote File System
resources by means of the AccessNConnectDecision Management Information
Service (ERFSS_IS) and the AccessNConnectDecision Management Index Information
Service (ERFSS_IIS)".
Algorithm Parameter b. We could have 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) and
the AccessNConnectDecision Management Index Information Service
(SMBIOS_ERFSS_IIS)".
Algorithm Parameter c. We could have EnterpriseResources_ERFSS_Monitoring
and
Discovery Services(ERS_ERFSS_MDS), that gathers information about connection
point services & Enterprise Resource Databases for the Remote File System
resources and parameters by means of the AccessNConnectDecision Management
Information Service (ERS_ERFSS_IS) and the AccessNConnectDecision Management
Index Information Service (ERS_ERFSS_IIS)". Enterprise Resource Databases
(ERDb) will support means for reporting ERFSS definitions, options &
extensibility.
Algorithm Parameter d. We could have
EnterpriseLocationSystem_ERFSS_Monitoring
and Discovery Services(ERS_ERFSS_MDS), that gathers information about
connection point services & Enterprise Location System resources and
parameters by means of the AccessNConnectDecision Management Information
Service (ERS_ERFSS_IS) and the AccessNConnectDecision Management Index
Information Service (ERS_ERFSS_IIS)".
9.2. SMBIOS_ERFSS_Monitoring and Discovery Services
In this design conceptualization, the SMBIOS_ERFSS_Monitoring and Discovery
Services (SMBIOS_ERFSS_MDS) will validate the infrastructure support for the
extensible capabilites that make up the much needed enterprise functionality
or Smart Neighborhood Assistant resources.
AccessNConnectDecision Management Information Services (SMBIOS_ERFSS_IS)
gather information about these SMBIOS Interoperable Remote File System
resources and parameters by means of the and the AccessNConnectDecision
Management Index Information Service (SMBIOS_ERFSS_IIS)".
9.2.1. What this means for any validation for the SMBIOS_ERFSS
services?
Validation will deal with communicating from a network computer or
interoperable resource to the sensor-connection points. The communication in
querying the SMBIOS_ERFSS service availability will be in the
contributor,contribution,response format and specification.
With the request from the contributor intent reviewed, the
sensor-connection
point will respond in the contributor,contribution,response format with the
SMBIOS_ERFSS service availability and then help any network access of the
extensible remote file system and AccessNConnectDecision management agent
node.
In this design conceptualization, the interfaces with the SMBIOS could
provide
Enterprise Remote File System database interoperability, database
synchronization of schema updates, content updates across the network. The the
AccessNConnectDecision Management Index Information Service (SMBIOS_ERFSS_IIS)
develops the database required for the interoperability, database
synchronization of schema updates, content updates across the network.
9.2.2. What does this design focus on as SMBIOS Interoperable Remote File
System resources and parameters?
Relating to my personal interests months ago, for any reader in this
article,
the design focus is extend the SMBIOS to collaborate as structures that set
expectations for the Remote File System resources and set SMBIOS parameters
for the AccessNConnectDecision conceptualization, interoperability and content
services.
9.2.3. What are the possible new structures that help interoperability
with
the SMBIOS Interoperable Remote File System resources and parameters?
The new structures expect to conceptualize AccessNConnectDecision in the
enterprise as contributor,contribution,response parameters & syntaxes. The
content for these new structures will be sampled with brief description in
this article.
9.2.4. Interoperable Remote File System Parameters (Type 110) 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.
9.2.5. Remote File System AccessNConnectDecision (Type 111) 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.
9.2.6. Remote File System Connector Information 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.
The structure evolution will rely on SMBIOS specification and Usage
Guidelines
for the industry to interoperate with the AccessNConnectDecision
conceptualization. Recommendations today for any structure evolution, are
engineers should ensure that the evolution occurs in a nondestructive fashion.
Additionally few guidelines must be followed: i. If a new field is added to an
existing structure, that field is added at the end of the formatted area of
that structure and the structure's Length field is increased by the new
field's size.
ii. Any software which interprets a structure shall use the structure's
Length
field to determine the formatted area size for the structure rather than
hard-coding or deriving the Length from a structure field.
iii. Each structure shall be terminated by a double-null (0000h), either
directly following the formattted area (if no strings are present) or directly
following the last string. This includes system- and OEM-specific structures
and allows upper-level software to easily traverse the structure table.
iv. The dynamic section of the structure is used for passing variable data
such as text strings.
v. When an enumerated field's values are controlled by the DMTF, new values
can be used as soon as they are defined by the DMTF without requiring an
update to this specification.
vi. Starting with v2.3, each SMBIOS structure type has a minimum length —
enabling the addition of new, but optional, fields to SMBIOS structures.
In no case shall a structure's length result in a field being less than
fully
populated. Software that interprets a structure field must verify that the
structure's length is sufficient to encompass the optional field; if the
length is insufficient, the optional field's value as Unknown.
Like regular SMBIOS implementations, the Inactive (Type 126) and
End-of-Table
(Type 127) SMBIOS structures will be used while interpreting and following the
headers of the structures for remote file system information.
The structure evolution will rely the SMBIOS for the event support and
synchronization, we look at the well defined SMBIOS structure definitions
like:
i. 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.
Like personal expectations, we rely on the System Event Log structure to
dynamically experience events and notifications for these
AccessNConnectDecision services. The AccessNConnectDecision services will use
the change notification structures and rally around the functions supported to
get the structure change.
10. Interoperability and Connection extensions through an Enterprise
Resource
Service Provider
The Service Provider will integrate support for the enterprise to associate
Smart Neighborhood Assistant & remote file system bindings with definitions,
concepts and thus support storing, locating and managing Smart Neighborhood
Assistant resources.
10.a Exploring Collaboration scenarios
The Remote File System AccessNConnectDecision Model proposes integrating &
supporting the following services, these services expect to support new
mechanisms of remote file system access.
i. Interfaces, Basic services.
ii. Neighborhood Assistant Interfaces invoked by specific
Platforms.
iii. Interfaces invoked by specific Platform connectivity services.
iv. Interfaces invoked by specific Platform File System services.
v. Interfaces invoked by specific Explorer infrastructure
services.
vi. Interfaces invoked by specific Marshalling services to
write/read/align with various file formats, images.
vii. Interfaces to manage using virtual folders explicitly created for
the
Neighborhood Assistant Decision Support and Information services.
The next articles in the series will connect with the collaboration support
and design the AccessNConnectDecision Model as a complete infrastructure
neighborhood.
11. The proposal for the AccessNConnectDecision Model will further the
connection point experience for network services, interfaces, sensor based
lifecycles in the enterprise network and design ways to extend the file
system. For the AccessNConnectDecision Management agents, the connection point
infrastructure interfaces with components called
"PlugNPlaySensorServices".
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.
These AccessNConnectDecision management agents will rely on Enterprise
Remote
File System Server (ERFSS) support to extend the file system. The ERFSS
infrastructure or BackEndServices will exist othe remote server & remote
file system, these services interface with the file system to develop and
extend the scope for any network access.
About The Author
K.S.Venkatram is a computer engineer from the University Of Poona.
|