View Single Post
Old 2006-07-05, 15:01   #3
RMAC9.5's Avatar
Jun 2003

100110012 Posts

Two years ago this design document initially captured the v5 system concept and objectives, though it's now woefully outdated and lacks details for feature-level implementation. However, the v5 GIMPS client web API specification is current for the system in development and describes data-level dependencies that hint at how the system works and what will be available for users on the web site.

A single web interface (a set of forms/pages) will manage all the computers of an account, as a whole or specific computers, and its operating options and preferences. Another set will manage all the resources of a team, which is created and managed by a teamleader. An important design philosophy of v5 is allowing users to manage distributed computing resources across multiple projects and on various workloads without having to physically revisit their computers once they have installed the v5 client.

Before you can install your first v5 client program, you normally need to create an account on the web site. This sets up an account summary page you can optionally make public and to which you can link or frame-embed from elsewhere, and enables your access to manage your account, computers and workload. It also provides an account binding the v5 client expects when you install it, though it's also possible to install a v5 client with an anonymous account binding that is instead managed by the project admin (in GIMPS' case, that's big GW).

When you install a v5 client, you give it just your account name, an optional computer name, and nothing else! This can be setup for batch installs, too. Once installed the v5 client does not need to keep a record of who owns it or its name, just its identity key. From that point forward the v5 server tells the client, when it asks, who owns it and what its name is.

Installed v5 clients will appear on your personal admin web page. You can still manage the client directly at the computer to some degree (including changing its account owner and local options and work preferences), but for the vast majority of the time you will select your project and work-type preference options on the web and your group (or cloud) of computers will simply perform your wishes on their own, collectively, or even individually or even as different CPUs on a computer if you want to fine-tune them. You will also be able to rename computers and transfer them between accounts. The local v5 client settings, however, will always have the ability to over-ride your web account (or team) settings.

You choose your optional team on your admin web page and can change it as often as you wish - your computers ride along with you. We haven't finalized decisions about team-level computer control, but we are carefully thinking it through. The current plan for crediting work in teams is that whatever team-level credit you earn while you are part of a team stays with the team. The same plan applies to computers on accounts - you can give away or lose the computer but the work credit it earned for your account stays on your account.

Much of the alpha & beta test phases will be focused upon these web management tasks, teams, and stats reporting rather than the v5 client and server. For alpha in particular we don't need a ton of computers per person - only enough to work out the kinks until beta. At first the v5 web site will be a little rough around the edges until the functionality is firm, but we'll pretty it up later. Get it working, then tune it up.

The italicized text above was copied from a February 06 entry in the v5 PrimeNet alpha and beta testing thread in the PrimeNet section. Hopefully your concerns will be addressed by the v5 data base software upgrade which is on the "horizon".
RMAC9.5 is offline   Reply With Quote