1. HA LVS Coda - Devjani Sinha

2. High Availability-HA n critical commercial applications move on the Internet n An elegant highly available system may have a reliable group communication sub-system, membership management, concurrent control sub-system and so on.

3. HA of LVS

4. Coda Solution n Coda is an advanced networked file system. n It has been developed at CMU since 1987 by the systems group of M. Satyanarayanan. in the SCS department. Coda makes a distinction between servers, which are relatively few in number, and clients, which are far more numerous

5. Features of Coda n Coda has several features not found elsewhere. 1. disconnected operation for mobile computing 2. is freely available under a liberal license 3. high performance through client side persistent caching 4. server replication and security model for authentication,encryption and access control 5. continued operation during partial network failures in server network 6. network bandwith adaptation 7. good scalability 8. well defined semantics of sharing, even in the presence of network failures n

6. Distributed file systems A distributed file system stores files on one or more computers called servers, and makes them accessible to other computers called clients, where they appear as normal files The files are more widely available since many computers can access the servers, and sharing the files from a single location is easier than distributing copies of files to individual clients. n Backups and safety of the information are easier to arrange since only the servers need to be backed up

7. Coda on a client. n typing mount will show that a file system --of type ``Coda'' -- under /coda n A client connects to ``Coda'' and not to individual servers n cat /coda/tmp/devjani'' to display the contents of a Coda file n Coda cache manager, called Venus

8. Client/Venus/Vice

9. Coda with LVS n Coda read-write operations take place at the same speed as those to local files n Directory files (remember: a directory is just a file) as well as all the attributes (ownership, permissions and size) are all cached by Venus, and Venus allows operations to proceed without contacting the server if the files are present in the cache. If file has been modified and it is closed, then Venus updates the servers by sending the new file.

10. Volumes, Servers and Server Replication n Files on Coda servers are not stored in traditional file systems n Each volume has a directory structure like a file system Coda holds volume and directory information, access control lists and file attribute information in raw partitions A single volume enjoys the privilege of being the root volume, that is the volume which is mounted on /coda at startup time. n For example, to mount the volume u.cs526 under on /coda/usr/cs526 the command cfs makemount u.cs526 /coda/usr/cs526 is issued

11. Disconnected Operation n If all of the servers that an object resides on become inaccessible, then the client will use the cached copy of the object (if present) as a valid replica. n Coda allows you to mark or hoard files with caching priorities to help keep the ones you want in the cache. n Coda adapts easily to low bandwidth connections like (PPP or SLIP modem links). n Reintegrate-% tail -f /usr/coda/etc/console

12. n Concept of hoarding files n --Updating the hoarded files is called a hoard walk Resolution and Repair.

13. Conclusion n server replication and disconnected operation n Unix applications without recompilation or relinking n degradation due to replication is relatively small significant improvements are been made as Coda is refined