Novell Cluster Services,. for Linux. and Netware

Total Page:16

File Type:pdf, Size:1020Kb

Novell Cluster Services,. for Linux. and Netware Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines 53 Install Applications on the Shared Disk 53 Execute NCF and Script Files from the Load and Unload Scripts 54 Clustering Without Shared Storage 55 Prepare the Cluster 55 CHAPTER 4: Installation and Configuration 59 Installing NCS on OES NetWare 59 Exploring eDirectory After Cluster Installation 64 Adding a NetWare Node to a NetWare Cluster 65 Installing NCS on Linux 66 Adding a NetWare Node to a Linux Cluster 69 Manually Starting and Stopping NCS 69 Adding a License to Existing Cluster Nodes 70 iv Contents Removing Nodes from a Cluster 70 Removing an OES NetWare Node from the Cluster 70 Removing an OES Linux Node from the Cluster 72 Installing NCS in VMware 73 What VMware Is 73 VMware Usage Scenarios 73 VMware Clustering Requirements 74 VMware Clustering Configuration 74 CHAPTER 5: Creating Cluster Resources 81 Creating Clustered Volumes 81 Creating Clustered Volumes on OES Linux and NetWare 82 Choosing the Right File System Type for Cluster Volumes on Linux 89 Creating Cluster Resources 98 Clustering a Simple Application on OES NetWare 98 Clustering a Simple Application on OES Linux 106 Cluster Script Syntax 112 Summary 113 CHAPTER 6: Cluster Management 115 Cluster Resources Management Applications 115 Managing Cluster Resources with iManager 115 Managing Cluster Resources on OES NetWare with Remote Manager 126 Managing Novell Cluster Services from the Command Line 127 Starting and Stopping Novell Cluster Services on Linux 128 Starting and Stopping Novell Cluster Services on NetWare 129 Managing Novell Cluster Services from the Command Line 129 Logging, Event History, and Alerting 132 Summary 135 Novell Cluster Services for Linux and NetWare CHAPTER 7: iSCSI 137 iSCSI Introduction 137 iSCSI Advantages 139 How iSCSI Works 140 iSCSI Naming Guidelines 142 Using iSCSI in an Open Enterprise Server Environment 142 iSCSI as a Server OS—Independent Storage Platform 143 iSCSI as a Low-Cost Shared Storage Solution 144 iSCSI for Remote Storage 144 iSCSI for Offsite Storage Mirroring 145 iSCSI Design Guidelines 146 iSCSI Target Requirements 147 iSCSI Initiator Requirements 148 iSCSI Target Configuration on OES NetWare 148 Installing the iSCSI Target Software 148 Creating the iSCSI Target 149 NetWare iSCSI Command Overview 151 iSCSI Initiator Configuration on OES NetWare 152 Assigning Rights for Initiators in the Same Tree 153 Assigning Rights for Initiators in Different Trees 153 Starting the Initiator Connection 154 iSCSI Initiator Configuration on OES Linux 156 Installing the iSCSI Software on Linux 157 Setting Up Access Control 158 Configuring the Initiator Software 158 Connecting to the iSCSI Target 158 Building an Open Enterprise Server Cluster with Shared iSCSI Storage 159 Advanced iSCSI Topics 161 Monitoring iSCSI Sessions 161 Solving iSCSI LDAP Problems 163 vi Contents CHAPTER 8: Cluster-Enabled Applications 165 Cluster-Enable or Not? 165 Clustering GroupWise 166 General GroupWise Clustering 167 Clustering GroupWise on NetWare 169 Clustering GroupWise on Linux 178 Clustering iFolder 3 on OES Linux 190 Linux Cluster Preparations for iFolder 190 Installing iFolder 3 Software on All Nodes 193 Configuring iFolder 3 on the First Node 193 Configuring the Cluster Resource 196 Testing the Cluster Resource 197 Configuring the Other Cluster Nodes 198 Clustering the Squid Web Proxy on Linux 199 DNS Round Robin Configuration 199 Squid High-Availability Design Considerations 200 Creating the Squid Cluster Resource 201 Clustering the Samba Server on OES Linux 202 Creating the Shared File System 203 Creating Mount Points to Mount the Shared File System on All Servers 205 Installing Samba on All Servers 206 Configuring the smb . conf File 206 Creating the Samba Clustered Resource 206 Making a Share Available from the Samba Clustered Resource. 208 Summary 209 CHAPTER 9: Advanced Clustering Topics, Maintenance, and Troubleshooting 211 Advanced Configuration and Maintenance 211 Creating Cluster Documentation 211 Changing the Master IP Address 212 Changing the Heartbeat IP Address 212 vii Novell Cluster Services for Linux and NetWare Troubleshooting Your Cluster Environment 214 Troubleshooting Resources 214 Re-creating the SBD Partition 215 Cluster Services Backup 218 Cluster Backups Explained 218 Storage Management Services 219 Novell's Backup Software 222 Syncsort Backup Express 223 CHAPTER 10: Upgrading Clusters 231 Upgrade Methods Explained 232 Upgrading Existing Hardware and Software 232 Migrating to New Hardware and Software 233 Installing New Cluster Hardware and Software from Scratch 235 Technical Upgrade Methods Explained 236 Upgrading a NetWare 5.1 Cluster to NetWare 6.5 236 Upgrading a NetWare 6 Cluster to NetWare 6.5 239 Upgrading a NetWare 6.5 Cluster to Open Enterprise Server Linux 242 Migrating to a New Cluster 247 CHAPTER 11: Using SUSE Linux Enterprise Server Clustering Options 253 Heartbeat Versus Novell Cluster Services 253 Installing SUSE Linux High-Availability Components 254 Configuring the Shared Storage with a DRBD 255 Clustering the NFS Server with Heartbeat 259 Edit the Sample Configuration Files 260 Use Authentication Keys to Ensure Secure Communications 260 Tune the Main Configuration File ha. cf on Both Nodes 261 Create Shared Resources by Editing the ha resou rces File 262 Start the Heartbeat Software on Both Nodes 264 Configure NFS for Use in the Heartbeat Cluster 265 viii Contents Managing the Shared Resource 266 Avoiding Split Brain 267 Summary 268 CHAPTER 12: Introduction to Business Continuity Clustering 269 Business Continuity Clustering Overview 269 High Availability Between Clusters 270 Using BCC to Create a Cluster of Clusters 271 BCC Usage Scenarios 272 Building Your Own BCC Test Environment 272 Setup and Installation of NetWare and NCS 273 Install Identity Manager 2,0 275 Business Continuity Cluster Services Installation 277 Configure the Identity Manager eDirectory Drivers 279 Start the Identity Manager Drivers, NCS, and BCC 283 Configuring BCC 284 Summary 290 INDEX 291 ix.
Recommended publications
  • OES 2 SP3: Novell CIFS for Linux Administration Guide 9.2.1 Mapping Drives from a Windows 2000 Or XP Client
    www.novell.com/documentation Novell CIFS Administration Guide Open Enterprise Server 2 SP3 May 03, 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Service Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • SUCCESS STORY. Security Software Porting from Netware to Novell Linux
    SUCCESS STORY. >_ >_ Security Software Porting From Netware To Novell >_ Linux About the The Client is a leader in the development of real-time monitoring, auditing and computer forensics Client technologies for Windows and Novell networks. Its ⧄agship product is used to secure the assets of the world’s largest corporations, banks, and government agencies, educational and healthcare institutions. Business The Client had a signi⣴cant install base for its ⧄agship software on Novell Netware OS. Novell’s Challenge adoption of Linux as the migration path for Netware OS created both an opportunity and a challenge for the Client. To continue supporting its Netware user base through Linux migration, the client wanted to port its monitoring and auditing solution to support SUSE Linux, Novell eDirectory and NSS (Novell Storage Services). The Client did not have in-house Linux Systems programming expertise, especially with ⣴le systems & security knowledge and approached Silicus. Silicus The software had two parts – the agent (client) and the server. The agent was a module that was Solution installed on the PC’s to be audited, and sends information on PC activities to a server installed at a centralized location. Termination of Netware required the agent to be re-developed/ported to Linux. Silicus commenced a feasibility study to address a few unknowns in the project: • Identify the auditing modules available on SuSE Linux • XML libraries that could be used • Multi-threading architecture to be used for agent development Silicus created a software architecture and design for the remote management agent. The agent was developed leveraging 3rd party tools to perform the auditing, monitoring of the Linux systems and communication with the remote server.
    [Show full text]
  • Shared Resource Matrix Methodology: an Approach to Identifying Storage and Timing Channels
    Shared Resource Matrix Methodology: An Approach to Identifying Storage and Timing Channels RICHARD A. KEMMERER University of California, Santa Barbara Recognizing and dealing with storage and timing channels when performing the security analysis of a computer system is an elusive task. Methods for discovering and dealing with these channels have mostly been informal, and formal methods have been restricted to a particular specification language. A methodology for discovering storage and timing channels that can be used through all phases of the software life cycle to increase confidence that all channels have been identified is presented. The methodology is presented and applied to an example system having three different descriptions: English, formal specification, and high-order language implementation. Categories and Subject Descriptors: C.2.0 [Computer-Communication Networks]: General--se- curity and protection; D.4.6 ]Operating Systems]: Security and Protection--information flow controls General Terms: Security Additional Key Words and Phrases: Protection, confinement, flow analysis, covert channels, storage channels, timing channels, validation 1. INTRODUCTION When performing a security analysis of a system, both overt and covert channels of the system must be considered. Overt channels use the system's protected data objects to transfer information. That is, one subject writes into a data object and another subject reads from the object. Subjects in this context are not only active users, but are also processes and procedures acting on behalf of the user. The channels, such as buffers, files, and I/O devices, are overt because the entity used to hold the information is a data object; that is, it is an object that is normally viewed as a data container.
    [Show full text]
  • Shared Resource
    Shared resource In computing, a shared resource, or network share, is a computer resource made available from one host to other hosts on a computer network.[1][2] It is a device or piece of information on a computer that can be remotely accessed from another computer transparently as if it were a resource in the local machine. Network sharing is made possible by inter-process communication over the network.[2][3] Some examples of shareable resources are computer programs, data, storage devices, and printers. E.g. shared file access (also known as disk sharing and folder sharing), shared printer access, shared scanner access, etc. The shared resource is called a shared disk, shared folder or shared document The term file sharing traditionally means shared file access, especially in the context of operating systems and LAN and Intranet services, for example in Microsoft Windows documentation.[4] Though, as BitTorrent and similar applications became available in the early 2000s, the term file sharing increasingly has become associated with peer-to-peer file sharing over the Internet. Contents Common file systems and protocols Naming convention and mapping Security issues Workgroup topology or centralized server Comparison to file transfer Comparison to file synchronization See also References Common file systems and protocols Shared file and printer access require an operating system on the client that supports access to resources on a server, an operating system on the server that supports access to its resources from a client, and an application layer (in the four or five layer TCP/IP reference model) file sharing protocol and transport layer protocol to provide that shared access.
    [Show full text]
  • Resource Management in Multimedia Networked Systems
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science May 1994 Resource Management in Multimedia Networked Systems Klara Nahrstedt University of Pennsylvania Ralf Steinmetz University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Klara Nahrstedt and Ralf Steinmetz, "Resource Management in Multimedia Networked Systems ", . May 1994. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-94-29. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/331 For more information, please contact [email protected]. Resource Management in Multimedia Networked Systems Abstract Error-free multimedia data processing and communication includes providing guaranteed services such as the colloquial telephone. A set of problems have to be solved and handled in the control-management level of the host and underlying network architectures. We discuss in this paper 'resource management' at the host and network level, and their cooperation to achieve global guaranteed transmission and presentation services, which means end-to-end guarantees. The emphasize is on 'network resources' (e.g., bandwidth, buffer space) and 'host resources' (e.g., CPU processing time) which need to be controlled in order to satisfy the Quality of Service (QoS) requirements set by the users of the multimedia networked system. The control of the specified esourr ces involves three actions: (1) properly allocate resources (end-to-end) during the multimedia call establishment, so that traffic can flow according to the QoS specification; (2) control resource allocation during the multimedia transmission; (3) adapt to changes when degradation of system components occurs.
    [Show full text]
  • Novell Management Tools
    04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 91 CHAPTER 3 Novell Management Tools Using ConsoleOne ConsoleOne is a Java-based tool for managing your network and its resources. It can be launched by running CONSOLEONE.EXE from where it was installed (default: SYS:PUBLIC\MGMT\CONSOLEONE\1.2\BIN). By default, it lets you manage Novell eDirectory objects, schema, parti- tions, and replicas and NetWare server resources. If you install other Novell products, the appropriate management capabil- ities are automatically snapped into the version of ConsoleOne installed on that server. ConsoleOne is installed during the NetWare 6.5 installation, but can also be re-installed or installed locally from the Novell client’s CD. ConsoleOne also supports remote server console access through a Java applet called RConsoleJ. To access the NetWare 6.5 server console remotely, launch ConsoleOne and browse to the desired server. Select Tools, and then Remote Console. Accessing Web Manager Web Manager is a Web-based “home page” for accessing most of the NetWare 6.5 Web-based tools and services. To access Web Manager, open your Web browser and enter your Web server’s domain name or IP address, followed by a colon and the Web Manager port, which by default is 2200. For example: 04 0789729849_ch03.qxd 11/10/03 12:43 PM Page 92 92 PART I Getting Started https://www.quills.com:2200 or https://137.65.192.1:2200 Accessing iManager iManager provides role-based management of your NetWare network, together with a nearly comprehensive set of administrative tools.
    [Show full text]
  • Novell® Platespin® Recon 3.7.4 User Guide 5.6.4 Printing and Exporting Reports
    www.novell.com/documentation User Guide Novell® PlateSpin® Recon 3.7.4 September 2012 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Characterizing Peer-Level Performance of Bittorrent
    Characterizing Peer-level Performance of BitTorrent DRP Report Amir H. Rasti ABSTRACT 1. INTRODUCTION BitTorrent is one of the most popular Peer-to-Peer During the past few years, peer-to-peer appli- (P2P) content distribution applications over the cations have become very popular on the In- Internet that significantly contributes in network ternet. BitTorrent in one of the most popu- traffic. lar peer-to-peer applications providing scalable peer-to-peer content distribution over the In- In BitTorrent, a file is divided into segments ternet. Some recent studies [8] have shown that and participating peers contribute their outgoing BitTorrent is accountable for approximately bandwidth by providing their available segments 35% of the Internet traffic. BitTorrent is a to other peers while obtaining their missing peers scalable peer-to-peer content distribution sys- from others. Characterization of BitTorrent is use- tem that enables one-to-many distribution of ful in determining its performance bottlenecks as large files without requiring a large access link well as its impact on the network. bandwidth at the source. Similar to other peer- In this study, we try to address the following two to-peer systems, it uses resources of participat- key questions through measurement: (i) What are ing peers to increase the capacity of the system. the main factors that affect observed performance The main shared resource in BitTorrent is the by individual peers in BitTorrent?, and (ii) What up-link bandwidth of individual peers. The file are the contributions of these factors on the per- being distributed is divided into a large number formance of individual peers? To address these of segments.
    [Show full text]
  • Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM Eserver I/O IBM Systems Group, Austin, Texas [email protected]
    Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM eServer I/O IBM Systems Group, Austin, Texas [email protected] Abstract • Low latency - the total time required to transfer the first bit of a message from the local application to the remote appli- Enterprise and technical customers place a diverse set of cation, including the transit times spent in intermediate requirements on server I/O networks. In the past, no single switches and I/O adapters. network type has been able to satisfy all of these requirements. As • High throughput - the number of small block transactions a result several fabric types evolved and several interconnects performed per second. The size and rate of small block I/O emerged to satisfy a subset of the requirements. Recently several depends on the workload and fabric type. A first level technologies have emerged that enable a single interconnect to be approximation of the I/O block size and I/O throughput rates required for various I/O workloads can be found in used as more than one fabric type. This paper will describe the “I/O Workload Characteristics of Modern Servers” [4]. requirements customers place on server I/O networks; the various • High bandwidth - the number of bytes per second sup- fabric types and interconnects that have been used to satisfy those ported by the network. Typically, used to gauge perfor- requirements; the technologies that are enabling network mance for large block data transfers. Peek bandwidth convergence; and how these new technologies are being deployed describes the bandwidth provided by a given link; whereas on various network families.
    [Show full text]
  • NFS Gateway for Netware 6 Administration Guide October 22, 2003
    Novell Confidential Manual (99a) 11 September 2003 Novell * NFS Gateway for NetWare® 6 www.novell.com ADMINISTRATION GUIDE October 22, 2003 Novell Confidential Manual (99a) 11 September 2003 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903;5,633,931; 5,652,859; 5,671,414;
    [Show full text]
  • DR DOS for the Zfx86
    DR DOS for the ZFx86 Cost Effective, Reliable, Rapid Deployment of Embedded Systems w DR DOS on the ZFx86 gets products to market quickly at the lowest development and ownership cost. w Thousands of compatible applications, drivers and utilities available free or at minimal cost. w Full documentation available. DR DOS 7.03 Key Features of DR DOS Online Manual - DRDOS is supplied with a complete The ideal embedded DOS system, online manual that contains detailed information about all designed for out-of-the-box of the features of the operating system including the basic implementation into ROM or Flash commands, and the advanced utilities. It also has online ROM with tools and associated help available for all its commands. documents available in the DRDOS Memory Management - Memory management features OEM Documentation Kit. include a set of device drivers and commands that enable w 100% MS-DOS 6.22 compatible.. you to manage memory efficiently and make as much memory as possible available to your applications. w Comprehensive DOS utility set DOS Protected Mode Services - DOS Protected Mode w Multitasking, with API for developers Services (DPMS) interface allows specially-implemented w DPMS memory manager in addition to DPMI device drivers and TSRs to operate in extended memory. w Stacker disk compression This makes more memory within the first megabyte w NWCACHE - disk caching program available to applications and other conventionally-written drivers and TSRs. Both Stacker* (the disk compression w EMM386 memory manager program), and NWCACHE (the disk cache) use DPMS. w DOS Protected Mode Services (DPMS) Disk Compression - The disk compression component w Multitasking enables you to store more information by compressing the w DR-DOS provides a full multitasking environment data.
    [Show full text]
  • Casual Resource Sharing with Shared Virtual Folders
    MASTER THESIS IN COMPUTER SCIENCE Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 FACULTY OF SCIENCE Department of Computer Science University of Tromsø, N-9037 Tromsø Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 ___________________ University of Tromsø 2007 Abstract Proliferation of wireless networks has been a major trigger behind increased mobility of computing devices. Along with increased mobility come requests for ad-hoc exchange of resources between computing devices as an extension of humans interacting. We termed it casual resource sharing where resources in this thesis have been narrowed down to files only. We have named our casual resource sharing model for shared virtual folders (SVF). SVFs can be looked upon as a common repository much in the same way as the tuplespace model. The SVF members perceive the repository similarly to a common file directory on a server, while in reality all participating devices stores their own contribution of files. All types of files could be added to the repository and shared. To become a SVF member one needs to be invited by another member or initiate a SVF oneself. All members are free to withdraw their SVF membership whenever they wish. They are also free to log on to the SVF and log out as they please. The SVF cease to exist when the last member has drawn his membership. The SVF implements a simple versioning detection system to alert members when a file has been modified by another member. Feasibility of the model is demonstrated in a prototype implementation based on Java and the JXTA middleware, a peer-to-peer (P2P) infrastructure middleware supporting the Internet protocol.
    [Show full text]