<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"><head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="keywords" content="9p, 9p2000, research, Plan 9, Inferno, Unix, Open Source, Bell Labs" /> <meta name="description" content="Open source distributed operating system Plan 9 from Bell Labs." /> <link rel="stylesheet" href="/wiki-style.css" media="all" type="text/css" /> <title>9grid (Diff)</title></head><body><h1><a name="top"></a>9grid <i>-Diff-</i></h1> <div class='body'> <!-- ***************************** --> <hr /><div class='diff_head'><a href="index.html">Sun Jul 20 03:28:52 EDT 2014</a>, glenda</div><hr /><span class='old_text'>Thename9gridhasbeenusedfortwoseparatebutrelatedprojects.<p class='para'>AnearlygridofPlan9serversatBellLabsandtheUniversityofCalgarywascalled<a href="http://plan9.bell-labs.com/9grid/index.html">9grid</a>.Itisgenerallyclosedandnotverymuchused.</p> <p class='para'>Morerecently,privateindividualsandorganizationshavecreatedahandfulofpublic-accessserversandalsousethename9grid.</p> <p class='para'>Noactiveserversareknownatthemoment.Pleaselistthemhereiftheybecomeavailable.</p> <p class='para'>Eachoftheseserversrunsitsownauthenticationdomain.Foraccounts,seethedetailsontheabovewebsites.</p> <a name="OPEN_PROBLEMS" /><h3>OPEN PROBLEMS</h3> <p class='para'>Openresearchproblemsremaininturningtheloosely-associatedcollectionofmachinesaboveintoatruegridofmachines,withcross-domainauthentication,accesscontrols,resourcediscovery,andperhapsevenloadbalancing.</p> <p class='para'>Therestofthispagesketchesproposedsolutionstosomeoftheseproblems.</p> <a name="AUTHENTICATION" /><h3>AUTHENTICATION</h3> <p class='para'>Weneedtoestablishaconsensusonhowagridusershouldbeauthenticatedonagridnode.</p> <ul> <li>Proposal1:<a href="http://www.r-36.net/multidomauth.tgz">multiauthdom</a>by20h</li> <li>Proposal2:<a href="http://www.tip9ug.jp/who/nashi/9grid/p9sk1.c">factotumpatch</a>bytip9ug.</li> <li>Proposal3:implementingSPKI</li></ul> <p class='para'>Proposal1and2seeminglyagreedonassigninggridusers'nameintheformof"username@authdom".Plan9kernelsurprisinglyacceptsthisnotation.ThesamenotationcouldbeusedonProposal3tooonceimplemented.</p> <a name="LOCAL_FILESTORE" /><h3>LOCAL FILESTORE</h3> <p class='para'>Ongridnodes,accessesbyagriduseraretreatedasnoneaccesstothelocalfilesystemunlesstheuserisregisteredtothefilesystem.Weneedtoofferasecurewaytograntgriduserstherighttostorefilesonthegridnode.<a href="http://plan9.bell-labs.com/magic/man2html/1/ramfs"><i>ramfs</i>(1)</a>canbeusedinmanycases,butyoumightwanttorememberthatPlan9hasthe1.8GBlimitationofinstallablememory,andalso,itcouldbehardtodoquotainramfs.</p> <p class='para'>Thefollowingproposalsaretoprovidegridusersawaytostoretheirfilesonafossilongridnodes.Quotaontheseproposalscanbedonebyrunningsomeinstanceoffossilonapartitionotherthan/dev/sdC0/fossiloronanordinaryfileonthefossilfromwhichthegridnodebootedfrom.</p> <ul> <li>Proposal1:createa"rwxrwxrwxsyssys"directorynamedbyarandomstringandpassthesecretpathnametoagriduser.</li> <li>Proposal2:makea<a href="http://www.tip9ug.jp/who/nashi/9grid/mkgdir.c">helperprogram</a>whichwilladdthegriduseronafossilandcreatea"rwx------gridusersys"directoryinthefossil.</li></ul> <a name="LIMITING_NETWORK_ACCESS" /><h3>LIMITING NETWORK ACCESS</h3> <p class='para'>SomeadminswouldwanttorestrictthegriduserstoaccessnetworkfromthegridnodeconsideringDDoS.Weneedtoprovideawaytogivegridnodes'adminsthechoiceiftheywanttogiveornottogivetheaccesstothelocalnetworkinterface.</p> <ul> <li>Proposal1:Lines 1–500 of 1891. Load more
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="keywords" content="9p, 9p2000, research, Plan 9, Inferno, Unix, Open Source, Bell Labs" /> <meta name="description" content="Open source distributed operating system Plan 9 from Bell Labs." /> <link rel="stylesheet" href="/wiki-style.css" media="all" type="text/css" /> <title>9grid (Diff)</title> </head> <body> <h1><a name="top"></a> 9grid <i>-Diff-</i></h1> <div class='body'> <!-- ***************************** --> <hr /><div class='diff_head'> <a href="index.html">Sun Jul 20 03:28:52 EDT 2014</a>, glenda </div><hr /><span class='old_text'>The name 9grid has been used for two separate but related projects. <p class='para'> An early grid of Plan 9 servers at Bell Labs and the University of Calgary was called <a href="http://plan9.bell-labs.com/9grid/index.html">9grid</a>. It is generally closed and not very much used. </p> <p class='para'> More recently, private individuals and organizations have created a handful of public-access servers and also use the name 9grid. </p> <p class='para'> No active servers are known at the moment. Please list them here if they become available. </p> <p class='para'> Each of these servers runs its own authentication domain. For accounts, see the details on the above web sites. </p> <a name="OPEN_PROBLEMS" /><h3>OPEN PROBLEMS</h3> <p class='para'> Open research problems remain in turning the loosely-associated collection of machines above into a true grid of machines, with cross-domain authentication, access controls, resource discovery, and perhaps even load balancing. </p> <p class='para'> The rest of this page sketches proposed solutions to some of these problems. </p> <a name="AUTHENTICATION" /><h3>AUTHENTICATION</h3> <p class='para'> We need to establish a consensus on how a griduser should be authenticated on a gridnode. </p> <ul> <li> Proposal 1: <a href="http://www.r-36.net/multidomauth.tgz">multiauthdom</a> by 20h </li> <li> Proposal 2: <a href="http://www.tip9ug.jp/who/nashi/9grid/p9sk1.c">factotum patch</a> by tip9ug. </li> <li> Proposal 3: implementing SPKI </li> </ul> <p class='para'> Proposal 1 and 2 seemingly agreed on assigning gridusers' name in the form of "username@authdom". Plan 9 kernel surprisingly accepts this notation. The same notation could be used on Proposal 3 too once implemented. </p> <a name="LOCAL_FILESTORE" /><h3>LOCAL FILESTORE</h3> <p class='para'> On gridnodes, accesses by a griduser are treated as none access to the local filesystem unless the user is registered to the filesystem. We need to offer a secure way to grant gridusers the right to store files on the gridnode. <a href="http://plan9.bell-labs.com/magic/man2html/1/ramfs"><i>ramfs</i>(1)</a> can be used in many cases, but you might want to remember that Plan 9 has the 1.8GB limitation of installable memory, and also, it could be hard to do quota in ramfs. </p> <p class='para'> The following proposals are to provide gridusers a way to store their files on a fossil on gridnodes. Quota on these proposals can be done by running some instance of fossil on a partition other than /dev/sdC0/fossil or on an ordinary file on the fossil from which the gridnode booted from. </p> <ul> <li> Proposal 1: create a "rwxrwxrwx sys sys" directory named by a random string and pass the secret pathname to a griduser. </li> <li> Proposal 2: make a <a href="http://www.tip9ug.jp/who/nashi/9grid/mkgdir.c">helper program</a> which will add the griduser on a fossil and create a "rwx------ griduser sys" directory in the fossil. </li> </ul> <a name="LIMITING_NETWORK_ACCESS" /><h3>LIMITING NETWORK ACCESS</h3> <p class='para'> Some admins would want to restrict the gridusers to access network from the gridnode considering DDoS. We need to provide a way to give gridnodes' admins the choice if they want to give or not to give the access to the local network interface. </p> <ul> <li> Proposal 1: