Feature Requests item #844849, was opened at 2003-11-18 20:08 Message generated for change (Comment added) made by jenos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=359368&aid=844849&group_id=9368
Category: None Group: Future Status: Open Resolution: None Priority: 5 Submitted By: Benoit des Ligneris (bligneri) Assigned to: Jason Brechin (brechin) Summary: The number of nodes should be dynamic Initial Comment: It should not be necessary to add the number of node the cluster beforehand. This is a _variable_ This step should be skipped and a command line/step called add/delete nodes should be created. ---------------------------------------------------------------------- >Comment By: Jeremy Enos (jenos) Date: 2004-03-01 12:28 Message: Logged In: YES user_id=270124 It's not a request for *always* allowing it... so nothing to worry about there. The auto-define-node feature will satisfy this request completely. ---------------------------------------------------------------------- Comment By: Jason Brechin (brechin) Date: 2004-02-24 13:11 Message: Logged In: YES user_id=274641 This will be implemented in the new wizard... as long as the node management window is open. I'm not sure we should always allow any collected MAC to be added to the cluster at any time. ---------------------------------------------------------------------- Comment By: Jason Brechin (brechin) Date: 2003-12-09 12:29 Message: Logged In: YES user_id=274641 Clarification in FR summary ---------------------------------------------------------------------- Comment By: Jeff Squyres (jsquyres) Date: 2003-11-22 07:27 Message: Logged In: YES user_id=11722 This is from conversations at SC, and it could have used a little better description here. :-) The point is that it would be nice to be able to have the functionality in the OSCAR wizard to say "any machine that you see a MAC address for [and/or I click on specifically] is an OSCAR client node. I don't know how many there will be yet, so just keep doing it until I say we're done." Specifically, just start capturing nodes until the user says we're done. Rich Libby gave a good example of a case where this is useful: he had 64 nodes to bring up and typed 64 in the define clients screen. But then a bunch of them failed to boot (hardware problems), so OSCAR was still stuck waiting for (64-num_good_booted) machines before it would continue. Clearly, this is not useful for *all* cases. But it's a nice convenience for some cases (perhaps even the optimized common case). As we discussed at SC, it would be nice to offer this kind of capture/assign model *in addition to* the current model (e.g., "basic" install vs. "advanced" install). Specifically: I don't think there's anything wrong with the current model. But I do see the value-added for the simplistic model described here for at least some users. ---------------------------------------------------------------------- Comment By: Jason Brechin (brechin) Date: 2003-11-19 09:51 Message: Logged In: YES user_id=274641 Umm... we've had an add/delete nodes step for quite a while now... since 2.0. Maybe I'm missing something? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=359368&aid=844849&group_id=9368 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
