|
You could use persistence that would (maybe) allow you to do that during
some time... But I think that's not the way to go:
What you describe is work for something like a bewolf cluster or a mosix
one, and not for a cluster farm with a LB in front....
> Hmmm. I'm not sure I understood how you would implement how a session
> state in my case. Specificly, I would like to have it so that a user
> ssh's into the cluster, runs a process, logs out, than when they log back
> in they are able to get to the job that they ran to monitor it's progress
> with ps, top, etc. If this isn't possible in LVS than it's true that LVS
> isn't for me but this is what I want to clarify.
>
> Thanks again,
> Cere
>
> >
> > It kind of defeats the object of the cluster to require a client to
> > connect to the same physical server in order to ensure a maintenance
> > of state - you both bypass the load balancing and the redundancy the
> > cluster provides.
> >
> > This sort of information (state, session) should be maintained in a
> > service available to all machines in the cluster - a database, a
> > session service - each of which should support replication to ensure
> > redundancy once again.
> >
> > If this is not feasible for your service, I don't believe LVS is what
> > you are looking for.
> >
> > Nick
> >
> >
> > >Hi,
> > >
> > >I am considering building a LVS for the purposes of a computing cluster
> > >but I am not sure it will work for our purposes because I cannot see how
> > >LVS would allow a user to connect to the same machine from one session to
> > >the next so that s/he could monitor her processes, etc. Is there a way
> > >for LVS to do this? Thanks.
> > >
> > >-Cere
> > >
> > >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > > Cere Davis
> > > Unix Systems Administrator - CSDE
> > > cere@xxxxxxxxxxxxxxxx ph: 206.685.5346
> > > https://staff.washington.edu/cere
> > >
> > >GnuPG Key http://staff.washington.edu/cere/gpgkey.txt
> > >Key fingerprint = B63C 2361 3B9B 8599 ECC9 D061 3E48 A832 F455 9E7FA
> > >
> > >
> > >
> > >_______________________________________________
> > >LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > >Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > >or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> >
> > _______________________________________________
> > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> >
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Cere Davis
> Unix Systems Administrator - CSDE
> cere@xxxxxxxxxxxxxxxx ph: 206.685.5346
> https://staff.washington.edu/cere
>
> GnuPG Key http://staff.washington.edu/cere/gpgkey.txt
> Key fingerprint = B63C 2361 3B9B 8599 ECC9 D061 3E48 A832 F455 9E7FA
>
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
